Merge pull request Azure#451 from Brunoga-MS/New-Releases

Updating broken links

docs/content/patterns/alz/HowTo/Cleaning-up-a-Deployment.md

@@ -27,7 +27,7 @@ It is strongly advised to **thoroughly** test the script in a non-production env
 
 To download the cleanup script file, follow these steps. Alternatively, you can clone the repository from GitHub and ensure you are working with the latest version by fetching the latest `main` branch.
 
-1. Navigate to the [AMBA project on GitHub](https://github.com/Azure/azure-monitor-baseline-alerts).
+1. Navigate to the [AMBA project on GitHub](https://aka.ms/amba/repo).
 2. Browse to the `patterns/alz/scripts` directory.
 3. Open the **Start-AMBA-ALZ-Maintenance.ps1** script file.
 4. Click the **Raw** button.

docs/content/patterns/alz/HowTo/Threshold-Override.md

@@ -6,7 +6,7 @@ weight: 85
 
 ## Overview
 
-The ***Alert Threshold Override*** feature, introduced in the [2024-09-05 release](../../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.
+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.
 
 ## How this feature works
 

docs/content/patterns/alz/HowTo/UpdateToNewReleases/Moving-from-preview-to-GA.md

@@ -26,7 +26,7 @@ It is strongly recommended to **thoroughly** test the script in a non-production
 
 Follow these steps to download the cleanup script file. Alternatively, you can clone the repository from GitHub and ensure you have the latest version by fetching the `main` branch.
 
-1. Navigate to the [AMBA project on GitHub](https://github.com/Azure/azure-monitor-baseline-alerts).
+1. Navigate to the [AMBA project on GitHub](https://aka.ms/amba/repo).
 2. Browse to the `patterns/alz/scripts` directory.
 3. Locate and open the **Start-ALZMonitorCleanup.ps1** script file.
 4. Click on the **Raw** button to view the raw content of the script.
@@ -62,8 +62,9 @@ Follow these steps to download the cleanup script file. Alternatively, you can c
 
 ## Next Steps
 
-- For customizing policy assignments, refer to [Customize Policy Assignment](../../HowTo/deploy/Customize-Policy-Assignment).
-- For deployment using GitHub Actions, refer to [Deploy with GitHub Actions](../../HowTo/deploy/Deploy-with-GitHub-Actions).
-- For deployment using Azure DevOps Pipelines, refer to [Deploy with Azure Pipelines](../../HowTo/deploy/Deploy-with-Azure-Pipelines).
-- For deployment using Azure CLI, refer to [Deploy with Azure CLI](../../HowTo/deploy/Deploy-with-Azure-CLI).
-- For deployment using Azure PowerShell, refer to [Deploy with Azure PowerShell](../../HowTo/deploy/Deploy-with-Azure-PowerShell).
+- For customizing policy assignments, refer to [Customize Policy Assignment](../../deploy/Customize-Policy-Assignment).
+- For deplyment using Azure Portal, refer to [Deploy via the Azure Portal (Preview)](../../deploy/Deploy-via-Azure-Portal-UI)  (recommended method)
+- For deployment using GitHub Actions, refer to [Deploy with GitHub Actions](../../deploy/Deploy-with-GitHub-Actions).
+- For deployment using Azure DevOps Pipelines, refer to [Deploy with Azure Pipelines](../../deploy/Deploy-with-Azure-Pipelines).
+- For deployment using Azure CLI, refer to [Deploy with Azure CLI](../../deploy/Deploy-with-Azure-CLI).
+- For deployment using Azure PowerShell, refer to [Deploy with Azure PowerShell](../../deploy/Deploy-with-Azure-PowerShell).

docs/content/patterns/alz/HowTo/UpdateToNewReleases/Update_to_release_2024-03-01.md

@@ -6,11 +6,11 @@ weight: 100
 
 ## Update
 
-Complete the activities documented in the [Steps to update to the latest release](.._index#steps-to-update-to-the-latest-release) page.
+Complete the activities documented in the [Steps to update to the latest release](../#steps-to-update-to-the-latest-release) page.
 
 ## Post update actions
 
-Updating to release [2024-03-01](../../../Whats-New#2024-03-01) will require running a post update script to remove the old Service Health action group(s) no longer in use.
+Updating to release [2024-03-01](../../../Overview/Whats-New#2024-03-01) will require running a post update script to remove the old Service Health action group(s) no longer in use.
 
 To execute the script, follow these steps:
 

docs/content/patterns/alz/HowTo/UpdateToNewReleases/Update_to_release_2024-04-12.md

@@ -10,7 +10,7 @@ weight: 99
 
 ## Update
 
-Complete the activities documented in the [Steps to update to the latest release](.._index#steps-to-update-to-the-latest-release) page.
+Complete the activities documented in the [Steps to update to the latest release](../#steps-to-update-to-the-latest-release) page.
 
 ## Post update actions
 

docs/content/patterns/alz/HowTo/UpdateToNewReleases/Update_to_release_2024-06-05.md

@@ -41,4 +41,4 @@ In particular, the new parameter file includes the following changes:
 
 ## Update
 
-Complete the activities documented in the [Steps to update to the latest release](.._index#steps-to-update-to-the-latest-release) page.
+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/UpdateToNewReleases/Update_to_release_2024-09-02.md

@@ -65,4 +65,4 @@ To execute the script, follow these steps:
 
 ## Update
 
-Complete the activities documented in the [Steps to update to the latest release](.._index#steps-to-update-to-the-latest-release) page.
+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/UpdateToNewReleases/Update_to_release_2024-11-01.md

@@ -10,4 +10,4 @@ weight: 96
 
 ## Update
 
-Complete the activities documented in the [Steps to update to the latest release](.._index#steps-to-update-to-the-latest-release) page.
+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/UpdateToNewReleases/_index.md

@@ -6,7 +6,7 @@ weight: 71
 
 ## What is included in the latest release
 
-The list of enhancement, additions and fixed bugs contained in every release can be seen by navigating to corresponding page linked in the home page of the [azure-monitor-baseline-alerts](https://github.com/Azure/azure-monitor-baseline-alerts) repository.
+The list of enhancement, additions and fixed bugs contained in every release can be seen by navigating to corresponding page linked in the home page of the [azure-monitor-baseline-alerts](https://aka.ms/amba/repo) repository.
 
 On the center-right side of the page, there's a specific section indicating the latest release. Click on the release number to see the release content.
 
@@ -73,7 +73,7 @@ Within the code editor of your choice, make sure you pull the changes from your
 
 Check the content of the page corresponding to the release you are updating to, to see if there's any pre or post deployment action required. For instance, if you're updating to release **2024-04-12**, check the page called ***Updating to release 2024-04-12***
 
-  ![Updating from release](../media/UpdatingToRelease.png)
+  ![Updating from release](../../media/UpdatingToRelease.png)
 
 ### Update the parameter file with any new parameter and configuration
 
@@ -84,6 +84,7 @@ For this reason, based on what documented in the [What's new](../../Overview/Wha
 
 Once you reached this stage, you are ready to deploy the latest release. You can deploy using a method of your choice among the allowed one:
 
+- To deploy with Azure Portal, please proceed with [Deploy via the Azure Portal (Preview)](../deploy/Deploy-via-Azure-Portal-UI)  (recommended method)
 - To deploy with GitHub Actions, please proceed with [Deploy with GitHub Actions](../deploy/Deploy-with-GitHub-Actions)
 - To deploy with Azure Pipelines, please proceed with [Deploy with Azure Pipelines](../deploy/Deploy-with-Azure-Pipelines)
 - To deploy with Azure CLI, please proceed with [Deploy with Azure CLI](../deploy/Deploy-with-Azure-CLI)
@@ -92,5 +93,3 @@ Once you reached this stage, you are ready to deploy the latest release. You can
 ### Start the policy remediation (always required)
 
 To remediate non-compliant policies, continue with Policy remediation documented at [Remediate Policies](../deploy/Remediate-Policies)
-
-[Back to top of page](.)

docs/content/patterns/alz/HowTo/deploy/Introduction-to-deploying-the-ALZ-Pattern.md

@@ -193,7 +193,7 @@ If you have suggestions or feature requests, consider submitting a pull request.
 
 ## Cleaning up an AMBA-ALZ Deployment
 
-In certain situations, you may need to remove all resources deployed by the AMBA-ALZ solution. For detailed instructions on how to clean up an AMBA-ALZ deployment, refer to the [Cleaning up an AMBA-ALZ Deployment](../../Cleaning-up-a-Deployment) guide.
+In certain situations, you may need to remove all resources deployed by the AMBA-ALZ solution. For detailed instructions on how to clean-up an AMBA-ALZ deployment, refer to the [Clean-up an AMBA-ALZ Deployment](../../Cleaning-up-a-Deployment) guide.
 
 ## Next Steps
 

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

@@ -1,5 +1,5 @@
 ---
-title: Deploying the ALZ pattern
+title: Deploy the AMBA-ALZ pattern
 geekdocCollapseSection: true
 weight: 50
 ---

docs/content/patterns/alz/Overview/ALZ-Pattern.md

@@ -80,7 +80,7 @@ Details on contributing to this repository can be found in the [Contributor Guid
 
 When you deploy the IP located in this repository, Microsoft can identify the installation with the deployed Azure resources. Microsoft collects this information to provide the best experiences with their products and to operate their business. The telemetry is collected through customer usage attribution and governed by [Microsoft's privacy policies](https://www.microsoft.com/trustcenter).
 
-If you do not wish to send usage data to Microsoft or need more details, refer to the [Disable telemetry tracking](../../Howto/Telemetry) guide.
+If you do not wish to send usage data to Microsoft or need more details, refer to the [Disable telemetry tracking](./../../../../Howto/Telemetry) guide.
 
 ## Trademarks
 

docs/content/patterns/alz/Resources/Known-Issues.md

@@ -69,7 +69,7 @@ weight: 100
 >
 > ### Cause
 >
-> When attempting to deploy to a different region, such as "uksouth", after a previous deployment in another region, an error may occur. This issue persists even after performing a cleanup (refer to [Cleaning up a Deployment](../../HowTo/Cleaning-up-a-Deployment) for more details). The error arises because deployment entries from the previous operation still exist, causing a region conflict that prevents the new deployment.
+> When attempting to deploy to a different region, such as "uksouth", after a previous deployment in another region, an error may occur. This issue persists even after performing a cleanup (refer to [Clean-up AMBA-ALZ Deployment](../../HowTo/Cleaning-up-a-Deployment) for more details). The error arises because deployment entries from the previous operation still exist, causing a region conflict that prevents the new deployment.
 >
 > ### Resolution
 >