diff --git a/docs/content/patterns/alz/Getting-started/Alerts-Details.md b/docs/content/patterns/alz/Getting-started/Alerts-Details.md index d946470e1..e08f54903 100644 --- a/docs/content/patterns/alz/Getting-started/Alerts-Details.md +++ b/docs/content/patterns/alz/Getting-started/Alerts-Details.md @@ -4,6 +4,13 @@ geekdocCollapseSection: true weight: 30 --- +### In this page + +> [AMBA-ALZ Pattern Metric Alerts Settings](../Alerts-Details#amba-alz-pattern-metric-alerts-settings)
+> [AMBA-ALZ Pattern Activity Log Alerts](../Alerts-Details#amba-alz-pattern-activity-log-alerts)
+> [VM Insights Log Alerts](../Alerts-Details#vm-insights-log-alerts)
+> [Recovery Vault Alerts](../Alerts-Details#recovery-vault-alerts)
+ To download specific alerts for the AMBA-ALZ pattern, click the Download icon (highlighted in red below) in the top right corner of the page. ![Alert-Details Download icon](../../media/AlertDetailsDownloadReference.png) @@ -67,4 +74,3 @@ Security Alerts and Job Failure alerts are summarized in the "[Using Backup Cent | PolicyName | Component | Category | Scope | Support for Multiple Resources | Verified | References | |-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------|-------------------------------------------------------------------------------------------------------|----------|--------------------------------|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | [Deploy RV Backup Health Monitoring Alerts](../../../services/RecoveryServices/vaults/Modify-RSV-BackupHealth-Alert.json) | Microsoft.RecoveryServices/Vaults | Microsoft.RecoveryServices/vaults/monitoringSettings.classicAlertSettings.alertsForCriticalOperations | Resource | No | Y | [Azure Monitor Alerts for Azure Backup](https://learn.microsoft.com/en-us/azure/backup/backup-azure-monitoring-built-in-monitor?tabs=recovery-services-vaults#azure-monitor-alerts-for-azure-backup)
[Move to Azure Monitor Alerts](https://learn.microsoft.com/en-us/azure/backup/move-to-azure-monitor-alerts) | - diff --git a/docs/content/patterns/alz/Getting-started/Monitoring-and-Alerting.md b/docs/content/patterns/alz/Getting-started/Monitoring-and-Alerting.md index 7584776f1..1c7043d32 100644 --- a/docs/content/patterns/alz/Getting-started/Monitoring-and-Alerting.md +++ b/docs/content/patterns/alz/Getting-started/Monitoring-and-Alerting.md @@ -4,6 +4,13 @@ geekdocCollapseSection: true weight: 20 --- +### In this page + +> [AMBA-ALZ Monitor Alert Approach](../Monitoring-and-Alerting#amba-alz-monitor-alert-approach)
+> [AMBA-ALZ Pattern Monitor Alert Policy Definitions](../Monitoring-and-Alerting#amba-alz-pattern-monitor-alert-policy-definitions)
+> [AMBA-ALZ Monitor Alert Processing Rules](../Monitoring-and-Alerting#amba-alz-monitor-alert-processing-rules)
+> [Monitoring Backup (Recovery Services Vaults)](../Monitoring-and-Alerting#monitoring-backup-recovery-services-vaults)
+ ## AMBA-ALZ Monitor Alert Approach The strategy for enabling alerts in the AMBA-ALZ pattern involves using Azure Policy to deploy alerts as resources are created, configuring action groups, and using Alert Processing Rules to activate alerts and link them to the action group. @@ -126,4 +133,3 @@ Azure Backup now provides new and improved alerting capabilities via Azure Monit ### Notifications While alerts are generated by default and cannot be disabled for destructive operations, users have control over the notifications. This allows you to specify the email addresses (or other notification endpoints) to which alerts should be routed. Notifications are configured by an alert processing rule, which is created by default when deploying the AMBA-ALZ pattern. - diff --git a/docs/content/patterns/alz/Getting-started/Policy-Initiatives.md b/docs/content/patterns/alz/Getting-started/Policy-Initiatives.md index 974880043..963d41c14 100644 --- a/docs/content/patterns/alz/Getting-started/Policy-Initiatives.md +++ b/docs/content/patterns/alz/Getting-started/Policy-Initiatives.md @@ -4,6 +4,24 @@ geekdocCollapseSection: true weight: 40 --- +### In this page + +> [Overview](../Policy-Initiatives#overview)
+> [Connectivity Initiative](../Policy-Initiatives#connectivity-initiative)
+> [Management Initiative](../Policy-Initiatives#management-initiative)
+> [Identity Initiative](../Policy-Initiatives#identity-initiative)
+> [Key Management Initiative](../Policy-Initiatives#key-management-initiative)
+> [Load Balancing Initiative](../Policy-Initiatives#load-balancing-initiative)
+> [Network Changes Initiative](../Policy-Initiatives#network-changes-initiative)
+> [Recovery Services Initiative](../Policy-Initiatives#recovery-services-initiative)
+> [Storage Initiative](../Policy-Initiatives#storage-initiative)
+> [VM Initiative](../Policy-Initiatives#vm-initiative)
+> [Web Initiative](../Policy-Initiatives#web-initiative)
+> [Hybrid VM Initiative](../Policy-Initiatives#hybrid-vm-initiative)
+> [Service Health Initiative](../Policy-Initiatives#service-health-initiative)
+> [Notification Assets Initiative](../Policy-Initiatives#notification-assets-initiative)
+> [Landing Zone Initiative (Deprecated)](../Policy-Initiatives#landing-zone-initiative-deprecated)
+ ## Overview This document details the AMBA-ALZ pattern Azure policy initiatives used for deploying the AMBA-ALZ baselines. For references on individual alerts/policies, refer to [Alert Details](../..//Getting-started//Alerts-Details). diff --git a/docs/content/patterns/alz/HowTo/Bring-your-own-Managed-Identity.md b/docs/content/patterns/alz/HowTo/Bring-your-own-Managed-Identity.md index 2488c641f..60eb01be7 100644 --- a/docs/content/patterns/alz/HowTo/Bring-your-own-Managed-Identity.md +++ b/docs/content/patterns/alz/HowTo/Bring-your-own-Managed-Identity.md @@ -4,6 +4,11 @@ geekdocCollapseSection: true weight: 80 --- +### In this page + +> [Overview](../Bring-your-own-Managed-Identity#overview)
+> [How this feature works](../Bring-your-own-Managed-Identity#how-this-feature-works)
+ ## Overview The ***Bring Your Own User Assigned Managed Identity*** (BYO UAMI) feature, introduced in the [2024-06-05 release](../../Overview/Whats-New#2024-06-05), allows both Greenfield and Brownfield customers to create a new User Assigned Managed Identity (UAMI) during or after the deployment of AMBA-ALZ. Brownfield customers who deployed the ALZ pattern before this feature was available can now configure existing UAMIs by setting a few parameters. This feature enables querying Azure Resource Graph (ARG) using Kusto Query Language and enhances log-based search alerts to include ARG queries for resource tags. diff --git a/docs/content/patterns/alz/HowTo/Bring-your-own-Notifications.md b/docs/content/patterns/alz/HowTo/Bring-your-own-Notifications.md index 7d779a92b..f41c67d11 100644 --- a/docs/content/patterns/alz/HowTo/Bring-your-own-Notifications.md +++ b/docs/content/patterns/alz/HowTo/Bring-your-own-Notifications.md @@ -4,6 +4,11 @@ geekdocCollapseSection: true weight: 90 --- +### In this page + +> [Overview](../Bring-your-own-Notifications#overview)
+> [How this feature works](../Bring-your-own-Notifications#how-this-feature-works)
+ ## Overview The ***Bring Your Own Notifications*** (BYON) feature, introduced in the [2024-04-12](../../Overview/Whats-New#2024-04-12) release, enables brownfield customers to utilize their existing Action Groups (AGs) and Alert Processing Rules (APRs) without mandating the use of notification assets deployed by the [Notification Assets](https://raw.githubusercontent.com/Azure/azure-monitor-baseline-alerts/main/patterns/alz/policySetDefinitions/Deploy-Notification-Assets.json) initiative or the [Deploy Service Health Action Group](https://raw.githubusercontent.com/Azure/azure-monitor-baseline-alerts/main/services/Resources/subscriptions/Deploy-ServiceHealth-ActionGroups.json) policy definition in the ALZ pattern. This feature also allows brownfield customers who deployed the ALZ pattern before this feature was available to switch to it. diff --git a/docs/content/patterns/alz/HowTo/Cleaning-up-a-Deployment.md b/docs/content/patterns/alz/HowTo/Cleaning-up-a-Deployment.md index 2478f567d..d4192c1ab 100644 --- a/docs/content/patterns/alz/HowTo/Cleaning-up-a-Deployment.md +++ b/docs/content/patterns/alz/HowTo/Cleaning-up-a-Deployment.md @@ -4,6 +4,10 @@ geekdocCollapseSection: true weight: 52 --- +### In this page + +> [Cleanup Script Execution](../Cleaning-up-a-Deployment#cleanup-script-execution)
+ In some cases, you may need to remove all resources deployed by the AMBA-ALZ solution. The following instructions provide a detailed guide on executing a PowerShell script to delete all deployed resources, including: - Metric Alerts diff --git a/docs/content/patterns/alz/HowTo/Disabling-Policies.md b/docs/content/patterns/alz/HowTo/Disabling-Policies.md index 2d5838d83..edc32097a 100644 --- a/docs/content/patterns/alz/HowTo/Disabling-Policies.md +++ b/docs/content/patterns/alz/HowTo/Disabling-Policies.md @@ -4,6 +4,12 @@ geekdocCollapseSection: true weight: 60 --- +### In this page + +> [AlertState Parameter](../Disabling-Policies#alertstate-parameter)
+> [PolicyEffect Parameter](../Disabling-Policies#policyeffect-parameter)
+> [MonitorDisable Parameter](../Disabling-Policies#monitordisable-parameter)
+ The AMBA-ALZ pattern provides several methods to enable or disable policy effects. 1. **Parameter: AlertState** - Manages the state of alert rules, allowing deployment in a disabled state or disabling existing alert rules at scale through policy. diff --git a/docs/content/patterns/alz/HowTo/Telemetry.md b/docs/content/patterns/alz/HowTo/Telemetry.md index ff1444ab3..f3aea015d 100644 --- a/docs/content/patterns/alz/HowTo/Telemetry.md +++ b/docs/content/patterns/alz/HowTo/Telemetry.md @@ -4,6 +4,11 @@ geekdocCollapseSection: true weight: 100 --- +### In this page + +> [Telemetry Tracking Using Customer Usage Attribution (PID)](../Telemetry#telemetry-tracking-using-customer-usage-attribution-(pid))
+> [Module PID Value Mapping](../Telemetry#module-pid-value-mapping)
+ ## Telemetry Tracking Using Customer Usage Attribution (PID) diff --git a/docs/content/patterns/alz/HowTo/Threshold-Override.md b/docs/content/patterns/alz/HowTo/Threshold-Override.md index 93d635a78..e83737230 100644 --- a/docs/content/patterns/alz/HowTo/Threshold-Override.md +++ b/docs/content/patterns/alz/HowTo/Threshold-Override.md @@ -4,6 +4,14 @@ geekdocCollapseSection: true weight: 70 --- +### In this page + +> [Overview](../Threshold-Override#overview)
+> [How this feature works](../Threshold-Override#how-this-feature-works)
+> [Metrics alerts](../Threshold-Override#metrics-alerts)
+> [Log-search alerts](../Threshold-Override#log-search-alerts)
+> [Which tag do customers need to create](../Threshold-Override#which-tag-do-customers-need-to-create)
+ ## Overview The ***Alert Threshold Override*** feature, introduced in the [2024-09-05 release](../../Overview/Whats-New#2024-09-05), enables both Greenfield and Brownfield customers to customize alert thresholds for specific resources during or after the deployment of AMBA-ALZ. This feature allows the use of a tag with a specific name and value to override the default alert threshold for designated resources. The new threshold value will apply exclusively to the tagged resources, replacing the global threshold specified in the parameter file. @@ -26,7 +34,7 @@ Considering the nature of log-search alerts, where resource information is retri ![Log-search Alerts - Override threshold at work](../../media/LogsearchAlerts-OverrideThresholdAtWork.png) -## Which tag does customers need to create +## Which tag do customers need to create {{< hint type=Info >}} For a comprehensive list of resource type friendly names, resource provider namespaces, and recommended abbreviations, refer to [Abbreviation recommendations for Azure resources](https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/ready/azure-best-practices/resource-abbreviations). diff --git a/docs/content/patterns/alz/HowTo/UpdateToNewReleases/Moving-from-preview-to-GA.md b/docs/content/patterns/alz/HowTo/UpdateToNewReleases/Moving-from-preview-to-GA.md index 1bd4eb05c..ef9f88a85 100644 --- a/docs/content/patterns/alz/HowTo/UpdateToNewReleases/Moving-from-preview-to-GA.md +++ b/docs/content/patterns/alz/HowTo/UpdateToNewReleases/Moving-from-preview-to-GA.md @@ -3,6 +3,12 @@ title: Transitioning from Preview to General Availability (GA) geekdocCollapseSection: true weight: 101 --- + +### In this page + +> [Cleanup Script Execution](../Moving-from-preview-to-GA#cleanup-script-execution)
+> [Next Steps](../Moving-from-preview-to-GA#next-steps)
+ To transition from the preview version to the General Availability (GA) version of the ALZ Monitor solution, you must remove all previously deployed resources. Follow these instructions to execute a PowerShell script that deletes the following resources: - Metric Alerts diff --git a/docs/content/patterns/alz/HowTo/UpdateToNewReleases/Update_to_release_2024-03-01.md b/docs/content/patterns/alz/HowTo/UpdateToNewReleases/Update_to_release_2024-03-01.md index b418ca07a..e6bd797c2 100644 --- a/docs/content/patterns/alz/HowTo/UpdateToNewReleases/Update_to_release_2024-03-01.md +++ b/docs/content/patterns/alz/HowTo/UpdateToNewReleases/Update_to_release_2024-03-01.md @@ -4,6 +4,11 @@ geekdocCollapseSection: true weight: 100 --- +### In this page + +> [Update](../Update_to_release_2024-03-01#update)
+> [Post update actions](../Update_to_release_2024-03-01#post-update-actions)
+ ## Update Complete the activities documented in the [Steps to update to the latest release](../#steps-to-update-to-the-latest-release) page. diff --git a/docs/content/patterns/alz/HowTo/UpdateToNewReleases/Update_to_release_2024-04-12.md b/docs/content/patterns/alz/HowTo/UpdateToNewReleases/Update_to_release_2024-04-12.md index 82501041f..6d661863f 100644 --- a/docs/content/patterns/alz/HowTo/UpdateToNewReleases/Update_to_release_2024-04-12.md +++ b/docs/content/patterns/alz/HowTo/UpdateToNewReleases/Update_to_release_2024-04-12.md @@ -4,6 +4,11 @@ geekdocCollapseSection: true weight: 99 --- +### In this page + +> [Update](../Update_to_release_2024-04-12#update)
+> [Post update actions](../Update_to_release_2024-04-12#post-update-actions)
+ {{< hint type=Important >}} **_No post-update action_** is required if you wish to continue using the notification assets deployed by the ALZ pattern. {{< /hint >}} diff --git a/docs/content/patterns/alz/HowTo/UpdateToNewReleases/Update_to_release_2024-06-05.md b/docs/content/patterns/alz/HowTo/UpdateToNewReleases/Update_to_release_2024-06-05.md index 5528412ab..9ff51fc71 100644 --- a/docs/content/patterns/alz/HowTo/UpdateToNewReleases/Update_to_release_2024-06-05.md +++ b/docs/content/patterns/alz/HowTo/UpdateToNewReleases/Update_to_release_2024-06-05.md @@ -4,6 +4,11 @@ geekdocCollapseSection: true weight: 98 --- +### In this page + +> [Pre update actions](../Update_to_release_2024-06-05#pre-update-actions)
+> [Update](../Update_to_release_2024-06-05#update) + {{< hint type=Important >}} ***The parameter file structure has changed to accommodate a new feature coming soon.*** {{< /hint >}} diff --git a/docs/content/patterns/alz/HowTo/UpdateToNewReleases/Update_to_release_2024-09-02.md b/docs/content/patterns/alz/HowTo/UpdateToNewReleases/Update_to_release_2024-09-02.md index 6a36e2a3b..871dded64 100644 --- a/docs/content/patterns/alz/HowTo/UpdateToNewReleases/Update_to_release_2024-09-02.md +++ b/docs/content/patterns/alz/HowTo/UpdateToNewReleases/Update_to_release_2024-09-02.md @@ -4,6 +4,11 @@ geekdocCollapseSection: true weight: 97 --- +### In this page + +> [Pre update actions](../Update_to_release_2024-09-02#pre-update-actions)
+> [Update](../Update_to_release_2024-09-02#update)
+ {{< hint type=Important >}} ***Updating to release [2024-09-02](../../../Overview/Whats-New#2024-09-02) from previous releases involves a breaking change. To proceed with the update, you must remove previously deployed policy definitions, policy set definitions, policy assignments, and role assignments. A script is provided to facilitate the removal of these items. ***It is highly recommended to thoroughly test the script in a non-production environment before executing it in production. Alert definitions do not need to be removed as they will continue to function.****** {{< /hint >}} diff --git a/docs/content/patterns/alz/HowTo/UpdateToNewReleases/Update_to_release_2024-11-01.md b/docs/content/patterns/alz/HowTo/UpdateToNewReleases/Update_to_release_2024-11-01.md index 49f871fec..a331c266c 100644 --- a/docs/content/patterns/alz/HowTo/UpdateToNewReleases/Update_to_release_2024-11-01.md +++ b/docs/content/patterns/alz/HowTo/UpdateToNewReleases/Update_to_release_2024-11-01.md @@ -4,6 +4,10 @@ geekdocCollapseSection: true weight: 96 --- +### In this page + +> [Update](../Update_to_release_2024-11-01#update)
+ {{< hint type=Info >}} **_No pre-update or post-update actions_** are required. {{< /hint >}} diff --git a/docs/content/patterns/alz/HowTo/UpdateToNewReleases/Update_to_release_2024_12_10.md b/docs/content/patterns/alz/HowTo/UpdateToNewReleases/Update_to_release_2024_12_10.md index 0a2676cff..b283fb41d 100644 --- a/docs/content/patterns/alz/HowTo/UpdateToNewReleases/Update_to_release_2024_12_10.md +++ b/docs/content/patterns/alz/HowTo/UpdateToNewReleases/Update_to_release_2024_12_10.md @@ -4,6 +4,10 @@ geekdocCollapseSection: true weight: 95 --- +### In this page + +> [Update](../Update_to_release_2024-12-10#update)
+ {{< hint type=Info >}} **_No pre-update or post-update actions_** are required. {{< /hint >}} diff --git a/docs/content/patterns/alz/HowTo/UpdateToNewReleases/Update_to_release_2025-01-10.md b/docs/content/patterns/alz/HowTo/UpdateToNewReleases/Update_to_release_2025-01-10.md index 4bb5e8b32..760a657e9 100644 --- a/docs/content/patterns/alz/HowTo/UpdateToNewReleases/Update_to_release_2025-01-10.md +++ b/docs/content/patterns/alz/HowTo/UpdateToNewReleases/Update_to_release_2025-01-10.md @@ -4,6 +4,10 @@ geekdocCollapseSection: true weight: 94 --- +### In this page + +> [Update](../Update_to_release_2025-01-10#update)
+ {{< hint type=Info >}} **_No pre-update or post-update actions_** are required. {{< /hint >}} diff --git a/docs/content/patterns/alz/HowTo/deploy/Customize-Policy-Assignment.md b/docs/content/patterns/alz/HowTo/deploy/Customize-Policy-Assignment.md index d96711a7c..3db7478d2 100644 --- a/docs/content/patterns/alz/HowTo/deploy/Customize-Policy-Assignment.md +++ b/docs/content/patterns/alz/HowTo/deploy/Customize-Policy-Assignment.md @@ -4,6 +4,12 @@ geekdocCollapseSection: true weight: 20 --- +### In this page + +> [Introduction](../Customize-Policy-Assignment#introduction)
+> [Modify initiative assignment](../Customize-Policy-Assignment#modify-initiative-assignment)
+> [Next steps](../Customize-Policy-Assignment#next-steps) + ## Introduction This document provides guidance on customizing policy assignments for the policies and initiatives in this repository. While default configurations are available as described in [Introduction to deploying the AMBA-ALZ pattern](../Introduction-to-deploying-the-ALZ-Pattern), you may need to adjust these settings to meet specific monitoring requirements or to implement alerts incrementally in an existing environment. diff --git a/docs/content/patterns/alz/HowTo/deploy/Deploy-only-Service-Health-Alerts.md b/docs/content/patterns/alz/HowTo/deploy/Deploy-only-Service-Health-Alerts.md index 951d4a801..531709879 100644 --- a/docs/content/patterns/alz/HowTo/deploy/Deploy-only-Service-Health-Alerts.md +++ b/docs/content/patterns/alz/HowTo/deploy/Deploy-only-Service-Health-Alerts.md @@ -4,6 +4,12 @@ geekdocCollapseSection: true weight: 70 --- +### In this page + +> [Quick deployment](../Deploy-only-Service-Health-Alerts#quick-deployment)
+> [Custom deployment](../Deploy-only-Service-Health-Alerts#custom-deployment)
+> [Next Steps](../Deploy-only-Service-Health-Alerts#next-steps)
+ {{< hint type=Important >}} Updating from the _**preview**_ version isn't supported. If you deployed the _**preview**_ version, proceed with [Moving from preview to GA](../../../Resources/Moving-from-preview-to-GA) before continuing. {{< /hint >}} diff --git a/docs/content/patterns/alz/HowTo/deploy/Deploy-via-Azure-Portal-UI.md b/docs/content/patterns/alz/HowTo/deploy/Deploy-via-Azure-Portal-UI.md index 2e02feeb0..9d7dc0019 100644 --- a/docs/content/patterns/alz/HowTo/deploy/Deploy-via-Azure-Portal-UI.md +++ b/docs/content/patterns/alz/HowTo/deploy/Deploy-via-Azure-Portal-UI.md @@ -3,6 +3,13 @@ title: Deploy via the Azure Portal weight: 30 --- +### In this page + +> [Deployment Settings Blade](../Deploy-via-Azure-Portal-UI#deployment-settings-blade)
+> [Management Groups Settings Blade](../Deploy-via-Azure-Portal-UI#management-groups-settings-blade)
+> [Notification Settings Blade](../Deploy-via-Azure-Portal-UI#notification-settings-blade)
+> [Next Steps](../Deploy-via-Azure-Portal-UI#next-steps)
+ [![Deploy to Azure](https://aka.ms/deploytoazurebutton)](https://aka.ms/amba/alz/portal)
diff --git a/docs/content/patterns/alz/HowTo/deploy/Deploy-with-Azure-CLI.md b/docs/content/patterns/alz/HowTo/deploy/Deploy-with-Azure-CLI.md index a4d48ddb1..866c68765 100644 --- a/docs/content/patterns/alz/HowTo/deploy/Deploy-with-Azure-CLI.md +++ b/docs/content/patterns/alz/HowTo/deploy/Deploy-with-Azure-CLI.md @@ -3,6 +3,12 @@ title: Deploy with Azure CLI weight: 30 --- +### In this page + +> [Configuring Variables for Deployment](../Deploy-with-Azure-CLI#3-configuring-variables-for-deployment)
+> [Deploying AMBA-ALZ](../Deploy-with-Azure-CLI#4-deploying-amba-alz)
+> [Next Steps](../Deploy-with-Azure-CLI#next-steps)
+ {{% include "parameterConfiguration.md" %}} ## 3. Configuring Variables for Deployment diff --git a/docs/content/patterns/alz/HowTo/deploy/Deploy-with-Azure-Pipelines.md b/docs/content/patterns/alz/HowTo/deploy/Deploy-with-Azure-Pipelines.md index 0cdab9cbc..0c36cfdd2 100644 --- a/docs/content/patterns/alz/HowTo/deploy/Deploy-with-Azure-Pipelines.md +++ b/docs/content/patterns/alz/HowTo/deploy/Deploy-with-Azure-Pipelines.md @@ -3,6 +3,12 @@ title: Deploy with Azure Pipelines weight: 50 --- +### In this page + +> [Configure and Run the Pipeline](../Deploy-with-Azure-Pipelines#3-configure-and-run-the-pipeline)
+> [Next Steps](../Deploy-with-Azure-Pipelines#next-steps)
+ + {{% include "parameterConfiguration.md" %}} ## 3. Configure and Run the Pipeline diff --git a/docs/content/patterns/alz/HowTo/deploy/Deploy-with-Azure-PowerShell.md b/docs/content/patterns/alz/HowTo/deploy/Deploy-with-Azure-PowerShell.md index 13b3879af..03148849a 100644 --- a/docs/content/patterns/alz/HowTo/deploy/Deploy-with-Azure-PowerShell.md +++ b/docs/content/patterns/alz/HowTo/deploy/Deploy-with-Azure-PowerShell.md @@ -3,6 +3,12 @@ title: Deploy with Azure PowerShell weight: 40 --- +### In this page + +> [Configuring Variables for Deployment](../Deploy-with-Azure-PowerShell#3-configuring-variables-for-deployment)
+> [Deploy Policy Definitions, Initiatives, and Policy Assignments with Default Settings](../Deploy-with-Azure-PowerShell#4-deploy-policy-definitions-initiatives-and-policy-assignments-with-default-settings)
+> [Next Steps](../Deploy-with-Azure-PowerShell#next-steps)
+ {{% include "parameterConfiguration.md" %}} ## 3. Configuring Variables for Deployment diff --git a/docs/content/patterns/alz/HowTo/deploy/Deploy-with-GitHub-Actions.md b/docs/content/patterns/alz/HowTo/deploy/Deploy-with-GitHub-Actions.md index 04ea846d1..fcbd2f3d4 100644 --- a/docs/content/patterns/alz/HowTo/deploy/Deploy-with-GitHub-Actions.md +++ b/docs/content/patterns/alz/HowTo/deploy/Deploy-with-GitHub-Actions.md @@ -3,6 +3,11 @@ title: Deploy with GitHub Actions weight: 60 --- +### In this page + +> [Configure and Run the Workflow](../Deploy-with-GitHub-Actions#3-configure-and-run-the-workflow)
+> [Next Steps](../Deploy-with-GitHub-Actions#next-steps)
+ {{% include "parameterConfiguration.md" %}} ## 3. Configure and Run the Workflow diff --git a/docs/content/patterns/alz/HowTo/deploy/Introduction-to-deploying-the-ALZ-Pattern.md b/docs/content/patterns/alz/HowTo/deploy/Introduction-to-deploying-the-ALZ-Pattern.md index f058cd3d5..726b64067 100644 --- a/docs/content/patterns/alz/HowTo/deploy/Introduction-to-deploying-the-ALZ-Pattern.md +++ b/docs/content/patterns/alz/HowTo/deploy/Introduction-to-deploying-the-ALZ-Pattern.md @@ -3,6 +3,18 @@ title: Introduction to deploying the AMBA-ALZ Pattern weight: 10 --- +### In this page + +> [Background](../Introduction-to-deploying-the-ALZ-Pattern#background)
+> [Prerequisites](../Introduction-to-deploying-the-ALZ-Pattern#prerequisites)
+> [Getting Started](../Introduction-to-deploying-the-ALZ-Pattern#getting-started)
+> [Determining your Management Group Hierarchy](../Introduction-to-deploying-the-ALZ-Pattern#determining-your-management-group-hierarchy)
+> [Customizing Policy Assignments](../Introduction-to-deploying-the-ALZ-Pattern#customizing-policy-assignments)
+> [Customizing the AMBA-ALZ Policies](../Introduction-to-deploying-the-ALZ-Pattern#customizing-the-amba-alz-policies)
+> [Disabling Monitoring](../Introduction-to-deploying-the-ALZ-Pattern#disabling-monitoring)
+> [Cleaning up an ALZ Deployment](../Introduction-to-deploying-the-ALZ-Pattern#cleaning-up-an-amba-alz-deployment)
+> [Next Steps](../Introduction-to-deploying-the-ALZ-Pattern#next-steps)
+ ## Background This guide provides instructions on how to begin implementing alert policies and initiatives in your environment for testing and validation. It assumes that you will use GitHub Actions or manual deployment methods to implement policies, initiatives, and policy assignments in your environment. @@ -50,7 +62,7 @@ While it is recommended to implement the alert policies and initiatives within a - [Manual deployment with Azure CLI](../Deploy-with-Azure-CLI) - [Manual deployment with Azure PowerShell](../Deploy-with-Azure-PowerShell) -### Determining your Management Group Hierarchy +## Determining your Management Group Hierarchy Azure Landing Zones provide a framework of best practices, patterns, and tools for establishing a secure, Well-Architected, and manageable cloud environment. A crucial element of Azure Landing Zones is the use of management groups, which enable the organization and management of subscriptions and resources in a hierarchical structure. Management groups facilitate the application of policies and access controls across multiple subscriptions and resources, simplifying the governance and management of your Azure environment. diff --git a/docs/content/patterns/alz/Overview/ALZ-Pattern.md b/docs/content/patterns/alz/Overview/ALZ-Pattern.md index 150690a4e..d0778e60f 100644 --- a/docs/content/patterns/alz/Overview/ALZ-Pattern.md +++ b/docs/content/patterns/alz/Overview/ALZ-Pattern.md @@ -4,6 +4,17 @@ geekdocCollapseSection: true weight: 10 --- +### In this page + +> [Overview](../ALZ-Pattern#overview)
+> [Feedback](../ALZ-Pattern#-feedback-)
+> [Deployment Guide](../ALZ-Pattern#deployment-guide)
+> [Known Issues](../ALZ-Pattern#known-issues)
+> [Frequently Asked Questions](../ALZ-Pattern#frequently-asked-questions)
+> [Contributing](../ALZ-Pattern#contributing)
+> [Telemetry](../ALZ-Pattern#telemetry)
+> [Trademarks](../ALZ-Pattern#trademarks)
+ ## Overview The Azure Monitor Baseline Alerts (AMBA) for Azure Landing Zones (ALZ) is a best practice collection of alerts for resources commonly deployed in Azure landing zones. It demonstrates how to deploy alerts at scale using Azure Policy. diff --git a/docs/content/patterns/alz/Overview/Whats-New.md b/docs/content/patterns/alz/Overview/Whats-New.md index 65c2d8f88..af33ac4eb 100644 --- a/docs/content/patterns/alz/Overview/Whats-New.md +++ b/docs/content/patterns/alz/Overview/Whats-New.md @@ -4,6 +4,17 @@ geekdocCollapseSection: true weight: 09 --- +### In this page + +> [2025-01-10](../Whats-New#2025-01-10)
+> [2024-12-10](../Whats-New#2024-12-10)
+> [2024-11-01](../Whats-New#2024-11-01)
+> [2024-09-02](../Whats-New#2024-09-02)
+> [2024-06-05](../Whats-New#2024-06-05)
+> [2024-04-12](../Whats-New#2024-04-12)
+> [2024-03-01](../Whats-New#2024-03-01)
+> [2023-11-14](../Whats-New#2023-11-14)
+ For the latest updates, visit the [Releases](https://github.com/Azure/azure-monitor-baseline-alerts/releases) page. To update your deployment with the latest release, refer to the [Update to new releases](../../HowTo/UpdateToNewReleases) guide. diff --git a/docs/content/patterns/alz/Resources/FAQ.md b/docs/content/patterns/alz/Resources/FAQ.md index b3fef5c21..163af480b 100644 --- a/docs/content/patterns/alz/Resources/FAQ.md +++ b/docs/content/patterns/alz/Resources/FAQ.md @@ -4,6 +4,21 @@ geekdocCollapseSection: true weight: 80 --- +### In this page + +> [Do I need to have Azure Landing zones deployed for this to work?](../FAQ#do-i-need-to-have-azure-landing-zones-deployed-for-this-to-work)
+> [Can I deploy to the Tenant Root Group?](../FAQ#can-i-deploy-to-the-tenant-root-group)
+> [Do I need to deploy to each region that I want to monitor?](../FAQ#do-i-need-to-deploy-to-each-region-that-i-want-to-monitor)
+> [Do I need to use the thresholds defined as default values in the metric rule alerts?](../FAQ#do-i-need-to-use-the-thresholds-defined-as-default-values-in-the-metric-rule-alerts)
+> [Why are the availability alert thresholds lower than 100% in this solution when the product group documentation recommends 100%?](../FAQ#why-are-the-availability-alert-thresholds-lower-than-100-in-this-solution-when-the-product-group-documentation-recommends-100)
+> [Do I need to use these metrics or can they be replaced with ones more suited to my environment?](../FAQ#do-i-need-to-use-these-metrics-or-can-they-be-replaced-with-ones-more-suited-to-my-environment)
+> [Can I disable the alerts being deployed for a resource or subscription?](../FAQ#can-i-disable-the-alerts-being-deployed-for-a-resource-or-subscription)
+> [How much does it cost to run the ALZ Baseline solution?](../FAQ#how-much-does-it-cost-to-run-the-alz-baseline-solution)
+> [Can I access the Visio diagrams displayed in the documentation?](../FAQ#can-i-access-the-visio-diagrams-displayed-in-the-documentation)
+> [Can I use AMBA-ALZ without cloning/forking a GitHub repository](../FAQ#can-i-use-amba-alz-without-cloningforking-a-github-repository)
+> [Can I deploy a local template by using -TemplateFile](../FAQ#can-i-deploy-a-local-template-by-using--templatefile)
+> [What characters can I use when creating Azure resources or renaming Azure subscriptions?](../FAQ#what-characters-can-i-use-when-creating-azure-resources-or-renaming-azure-subscriptions)
+ ## Do I need to have Azure Landing zones deployed for this to work? > No, Azure Landing Zones are not required. However, you must use Azure Management Groups. Currently, our focus is on resources commonly deployed as part of Azure Landing Zone implementations. diff --git a/docs/content/patterns/alz/Resources/Known-Issues.md b/docs/content/patterns/alz/Resources/Known-Issues.md index aa8883350..70a84633b 100644 --- a/docs/content/patterns/alz/Resources/Known-Issues.md +++ b/docs/content/patterns/alz/Resources/Known-Issues.md @@ -4,6 +4,16 @@ geekdocCollapseSection: true weight: 100 --- +### In this page + +> [VM Log Alert policies fail to remediate](../Known-Issues#vm-log-alert-policies-fail-to-remediate)
+> [Failed to deploy because of role assignment issue](../Known-Issues#failed-to-deploy-because-of-role-assignment-issue)
+> [Failed to deploy to a different location](../Known-Issues#failed-to-deploy-to-a-different-location)
+> [Failed to deploy because of the limit of 800 deployments per management group has been reached](../Known-Issues#failed-to-deploy-because-of-the-limit-of-800-deployments-per-management-group-has-been-reached)
+> [Failed to deploy because of 'location' property not specified](../Known-Issues#failed-to-deploy-because-of-location-property-not-specified)
+> [Failed to deploy action group(s) and/or alert processing rule(s)](../Known-Issues#failed-to-deploy-action-groups-andor-alert-processing-rules)
+> [Failed to edit action group(s)](../Known-Issues#failed-to-edit-action-groups)
+ ## VM Log Alert policies fail to remediate > ### Error includes diff --git a/docs/content/patterns/alz/media/PortalAccelerator/DeploymentSettings.png b/docs/content/patterns/alz/media/PortalAccelerator/DeploymentSettings.png index 3fe542f1e..5c160e70d 100644 Binary files a/docs/content/patterns/alz/media/PortalAccelerator/DeploymentSettings.png and b/docs/content/patterns/alz/media/PortalAccelerator/DeploymentSettings.png differ diff --git a/docs/content/patterns/alz/media/PortalAccelerator/MGSettings.png b/docs/content/patterns/alz/media/PortalAccelerator/MGSettings.png index edb778324..29725c561 100644 Binary files a/docs/content/patterns/alz/media/PortalAccelerator/MGSettings.png and b/docs/content/patterns/alz/media/PortalAccelerator/MGSettings.png differ diff --git a/docs/content/patterns/alz/media/PortalAccelerator/NotificationSettings.png b/docs/content/patterns/alz/media/PortalAccelerator/NotificationSettings.png index 778b7b8d1..b521f8ced 100644 Binary files a/docs/content/patterns/alz/media/PortalAccelerator/NotificationSettings.png and b/docs/content/patterns/alz/media/PortalAccelerator/NotificationSettings.png differ