Merge pull request #519 from Brunoga-MS/New-Releases

New 2025-02-05 AMBA-ALZ release

docs/content/patterns/alz/HowTo/Exclude-Logical-Volumes.md

@@ -1,7 +1,7 @@
 ---
 title: Exclude logical volumes
 geekdocCollapseSection: true
-geekdocHidden: true
+geekdocHidden: false
 weight: 80
 ---
 

docs/content/patterns/alz/HowTo/UpdateToNewReleases/Update_to_release_2025-02-05.md

@@ -0,0 +1,20 @@
+---
+title: Updating to release 2025-02-05
+geekdocCollapseSection: true
+weight: 93
+---
+
+### In this page
+
+> [Pre update actions](../Update_to_release_2025-02-05#pre-update-actions) </br>
+> [Update](../Update_to_release_2025-02-05#update)
+
+# Pre update actions
+
+In this release, we have resolved an issue where a missing role assignment was preventing the successful completion of the remediation task for the Web Initiative. However, addressing this problem introduces a breaking change that does not allow an in-place update of an existing environment because the additional role assignment also requires an update of an existing assignment, generating a conflict that makes the update unsuccessful. To resolve this issue and successfully update an existing deployment, you need to remove both the current policy and role assignment. This can be accomplished using the [Start-AMBA-ALZ-Maintenance.psi](patterns\alz\scripts\Start-AMBA-ALZ-Maintenance.ps1) script. For instructions on running the script, refer to the documentation available on the [Clean-up AMBA-ALZ Deployment](../../Cleaning-up-a-Deployment) page, ensuring that you enter **PolicyAssignments** as the value for the ***-cleanItems*** script parameter:
+
+  ![Remove policy and role assignments](../../../media/Remove-Policy-And-Role-Assignments.png)
+
+## Update
+
+Complete the activities documented in the [Steps to update to the latest release](../#steps-to-update-to-the-latest-release) page.

docs/content/patterns/alz/HowTo/deploy/Customize-Policy-Assignment.md

@@ -22,7 +22,7 @@ To adjust alert thresholds for one or more metric alerts, specify the relevant p
 
 Two versions of the parameter file are available:
 
-1. [alzArm.param.json](https://github.com/azure/azure-monitor-baseline-alerts/blob/2024-12-10/patterns/alz/alzArm.param.json) aligned with the latest release.
+1. [alzArm.param.json](https://github.com/azure/azure-monitor-baseline-alerts/blob/2025-02-05/patterns/alz/alzArm.param.json) aligned with the latest release.
 2. [alzArm.param.json](https://github.com/azure/azure-monitor-baseline-alerts/blob/main/patterns/alz/alzArm.param.json) aligned with the main branch.
 
 ### Applying Changes to the Parameter File

docs/content/patterns/alz/HowTo/deploy/Deploy-only-Service-Health-Alerts.md

@@ -29,7 +29,7 @@ In this example we will deploy the Service Health Policy Set Definition via Azur
 
 To start, you can either download a copy of the parameter file according the version of AMBA-ALZ you are going to deploy or clone/fork the repository.
 
-- [alzArm.param.json](https://github.com/azure/azure-monitor-baseline-alerts/blob/2024-12-10/patterns/alz/alzArm.param.json) aligned to the latest release
+- [alzArm.param.json](https://github.com/azure/azure-monitor-baseline-alerts/blob/2025-02-05/patterns/alz/alzArm.param.json) aligned to the latest release
 - [alzArm.param.json](https://github.com/azure/azure-monitor-baseline-alerts/blob/main/patterns/alz/alzArm.param.json) aligned to the main branch
 
 The following changes apply to all scenarios, whether you are aligned or unaligned with ALZ or have a single management group.
@@ -259,7 +259,7 @@ The ```location``` variable refers to the deployment location. Deploying to mult
 Using your preferred command-line tool (Windows PowerShell, Cmd, Bash or other Unix shells), if you closed your previous session, navigate again to the root of the cloned repo and log on to Azure with an account with at least Resource Policy Contributor access at the root of the management group hierarchy where you will be creating the policies and Policy Set Definitions.
 
 ```bash
-az deployment mg create --template-uri https://raw.githubusercontent.com/Azure/azure-monitor-baseline-alerts/2024-12-10/patterns/alz/alzArm.json --name "amba-GeneralDeployment" --location $location --management-group-id $pseudoRootManagementGroup --parameters .\patterns\alz\alzArm.param.json
+az deployment mg create --template-uri https://raw.githubusercontent.com/Azure/azure-monitor-baseline-alerts/2025-02-05/patterns/alz/alzArm.json --name "amba-GeneralDeployment" --location $location --management-group-id $pseudoRootManagementGroup --parameters .\patterns\alz\alzArm.param.json
 ```
 
 </br>

docs/content/patterns/alz/HowTo/deploy/Deploy-with-Azure-CLI.md

@@ -50,7 +50,7 @@ If you have customized the policies as described in [How to modify individual po
 {{< /hint >}}
 
 ```bash
-az deployment mg create --name "amba-GeneralDeployment" --template-uri https://raw.githubusercontent.com/Azure/azure-monitor-baseline-alerts/2024-12-10/patterns/alz/alzArm.json --location $location --management-group-id $pseudoRootManagementGroup --parameters ".\patterns\alz\alzArm.param.json"
+az deployment mg create --name "amba-GeneralDeployment" --template-uri https://raw.githubusercontent.com/Azure/azure-monitor-baseline-alerts/2025-02-05/patterns/alz/alzArm.json --location $location --management-group-id $pseudoRootManagementGroup --parameters ".\patterns\alz\alzArm.param.json"
 ```
 
 ## Next Steps

docs/content/patterns/alz/HowTo/deploy/Deploy-with-Azure-Pipelines.md

@@ -8,7 +8,6 @@ weight: 60
 > [Configure and Run the Pipeline](../Deploy-with-Azure-Pipelines#3-configure-and-run-the-pipeline) </br>
 > [Next Steps](../Deploy-with-Azure-Pipelines#next-steps) </br>
 
-
 {{% include "parameterConfiguration.md" %}}
 
 ## 3. Configure and Run the Pipeline

docs/content/patterns/alz/HowTo/deploy/Deploy-with-Azure-PowerShell.md

@@ -57,7 +57,7 @@ New-AzManagementGroupDeployment -Name "amba-GeneralDeployment" -ManagementGroupI
 {{< /hint >}}
 
 ```powershell
-New-AzManagementGroupDeployment -Name "amba-GeneralDeployment" -ManagementGroupId $pseudoRootManagementGroup -Location $location -TemplateUri "https://raw.githubusercontent.com/Azure/azure-monitor-baseline-alerts/2024-12-10/patterns/alz/alzArm.json" -TemplateParameterFile ".\patterns\alz\alzArm.param.json"
+New-AzManagementGroupDeployment -Name "amba-GeneralDeployment" -ManagementGroupId $pseudoRootManagementGroup -Location $location -TemplateUri "https://raw.githubusercontent.com/Azure/azure-monitor-baseline-alerts/2025-02-05/patterns/alz/alzArm.json" -TemplateParameterFile ".\patterns\alz\alzArm.param.json"
 ```
 
 ## Next Steps

docs/content/patterns/alz/HowTo/deploy/parameterConfiguration.md

@@ -11,7 +11,7 @@ Updating from the _**preview**_ version is not supported. If you deployed the _*
 
 To begin, either download the appropriate parameter file for the version of AMBA-ALZ you are deploying or clone/fork the repository.
 
-- [alzArm.param.json](https://github.com/azure/azure-monitor-baseline-alerts/blob/2024-12-10/patterns/alz/alzArm.param.json) for the latest release.
+- [alzArm.param.json](https://github.com/azure/azure-monitor-baseline-alerts/blob/2025-02-05/patterns/alz/alzArm.param.json) for the latest release.
 - [alzArm.param.json](https://github.com/azure/azure-monitor-baseline-alerts/blob/main/patterns/alz/alzArm.param.json) for the main branch.
 
 The following instructions apply universally, regardless of your alignment with ALZ or if you have a single management group.

docs/content/patterns/alz/Overview/Whats-New.md

@@ -6,6 +6,7 @@ weight: 09
 
 ### In this page
 
+> [2025-02-05](../Whats-New#2025-02-05) </br>
 > [2025-01-10](../Whats-New#2025-01-10) </br>
 > [2024-12-10](../Whats-New#2024-12-10) </br>
 > [2024-11-01](../Whats-New#2024-11-01) </br>
@@ -19,6 +20,38 @@ For the latest updates, visit the [Releases](https://github.com/Azure/azure-moni
 
 To update your deployment with the latest release, refer to the [Update to new releases](../../HowTo/UpdateToNewReleases) guide.
 
+## 2025-02-05
+
+### New Features
+
+- Exclusion of logical volumes from the following alerts for both ***Azure*** and ***Hybrid*** Virtual Machines:
+  - Operating System Disk Free space
+  - Operating System DiskRead latency
+  - Operating System DiskWrite latency
+  - Data Disks Free space
+  - Data Disks Read latency
+  - Data Disks Write latency
+
+  Detailed information on how to use this new feature can be found in the [Exclude logical volumes](../../HowTo/Exclude-Logical-Volumes) page.
+
+- Optimization of calls to Azure Resource Graph inside log-search alert queries. This optimization should reduce and mitigate the throttling issue.
+
+### Bug Fixes
+
+- Resolved [[#508](https://github.com/Azure/azure-monitor-baseline-alerts/issues/508)]: [General workload issue]: deploy-amba-web assignment missing Managed Identity Operator role on UAMI
+- Resolved [[#499](https://github.com/Azure/azure-monitor-baseline-alerts/pull/499)]: fix: ALZ Pattern add missing `/` to fix regression introduced by PG
+
+### Documentation Updates
+
+- The [Policy Initiatives](../../Getting-started/Policy-Initiatives.md) page has been aligned with the alerts.
+- The [Bring Your Own User Assigned Managed Identity](../../HowTo/Bring-your-own-Managed-Identity) page has been updated to list the policy initiatives that makes use of Managed Identity for log-search alerts.
+- An ***In this page*** section with links to contained paragraphs has been added at top of each page to increase the navigation experience.
+- Broken links fixed.
+
+### Tools
+
+- NONE
+
 ## 2025-01-10
 
 ### New Features
@@ -35,10 +68,10 @@ To update your deployment with the latest release, refer to the [Update to new r
 
 ### Bug Fixes
 
-- Resolved [[#455](https://github.com/Azure/azure-monitor-baseline-alerts/pull/455)]: Property name case consistency and remediation script rename
-- Resolved [[#460](https://github.com/Azure/azure-monitor-baseline-alerts/pull/460)]: Portal accelerator bug
-- Resolved [[#465](https://github.com/Azure/azure-monitor-baseline-alerts/pull/465)]: Fix policyDefinitionId format
-- Resolved [[#475](https://github.com/Azure/azure-monitor-baseline-alerts/pull/475)]: [Bug]: Unable to cleanup AMBA deployment - Property "Id" cannot be found
+- Resolved [[#455](https://github.com/Azure/azure-monitor-baseline-alerts/issues/455)]: Property name case consistency and remediation script rename
+- Resolved [[#460](https://github.com/Azure/azure-monitor-baseline-alerts/issues/460)]: Portal accelerator bug
+- Resolved [[#465](https://github.com/Azure/azure-monitor-baseline-alerts/issues/465)]: Fix policyDefinitionId format
+- Resolved [[#475](https://github.com/Azure/azure-monitor-baseline-alerts/issues/475)]: [Bug]: Unable to cleanup AMBA deployment - Property "Id" cannot be found
 
 ### Documentation Updates