Skip to content

Commit

Permalink
Merge pull request #6102 from MicrosoftDocs/main
Browse files Browse the repository at this point in the history
12/16/2024 AM Publish
  • Loading branch information
Taojunshen authored Dec 16, 2024
2 parents 98bc44b + a933190 commit 959bec0
Show file tree
Hide file tree
Showing 8 changed files with 10 additions and 10 deletions.
6 changes: 3 additions & 3 deletions docs/ready/landing-zone/design-area/management-monitor.md
Original file line number Diff line number Diff line change
Expand Up @@ -43,13 +43,13 @@ The following subsets of Azure components have one or more alerts defined:
- Azure Virtual Machine
- Azure Storage account

For more information, see [Alert details](https://aka.ms/alz/monitor/alertdetails).
For more information, see [Alert details](https://azure.github.io/azure-monitor-baseline-alerts/patterns/alz/Getting-started/Alerts-Details/).

To ensure that your organization's resources are properly monitored and secured, you also need to properly configure alerts and implement appropriate processes to respond to alerts. Configure action groups with the appropriate notification channels and test the alerts to ensure that they work as expected. In accordance with the Cloud Adoption Framework principle of subscription democratization, configure at least one action group for each subscription so that relevant staff is notified of alerts. As a minimum form of notification, the action group should include an email notification channel. If you use Azure Monitor alert processing rules to route alerts to one or more action groups, note that service health alerts don't support alert processing rules. Configure service health alerts directly with the action group.

In accordance with [Azure landing zone principles for policy-driven governance](/azure/cloud-adoption-framework/ready/enterprise-scale/dine-guidance#why-use-dine-and-modify-policies), a framework solution is available that provides an easy way to scale alerting by using Azure Policy. These policies use the *DeployIfNotExists* effect to deploy relevant alert rules, alert processing rules, and action groups when you create a resource in your Azure landing zone environment, in both platform services and landing zones.

Azure Policy provides a default baseline configuration, but you can configure the policies to suit your needs. If you require alerting on different metrics than what the repository provides, the solution provides a framework for you to develop your own policies for deploying alert rules. For more information, see the [Azure Monitor baseline alerts (AMBA) contributor guide](https://aka.ms/amba/contributing) and [Introduction to an Azure Monitor deployment](https://aka.ms/amba/alz/deploy). The solution is integrated into the Azure landing zone installation experience, so new implementations of Azure landing zone offer you the opportunity to set up baseline alerting at installation time.
Azure Policy provides a default baseline configuration, but you can configure the policies to suit your needs. If you require alerting on different metrics than what the repository provides, the solution provides a framework for you to develop your own policies for deploying alert rules. For more information, see the [Azure Monitor baseline alerts (AMBA) contributor guide](https://aka.ms/amba/contributing) and [Introduction to an Azure Monitor deployment](https://azure.github.io/azure-monitor-baseline-alerts/patterns/alz/HowTo/deploy/Introduction-to-deploying-the-ALZ-Pattern/). The solution is integrated into the Azure landing zone installation experience, so new implementations of Azure landing zone offer you the opportunity to set up baseline alerting at installation time.

Deploy alerts via policies to provide flexibility and scalability, and to ensure that alerts are deployed inside and outside the Azure landing zone scope. Alerts are only deployed when the corresponding resources are created, which avoids unnecessary cost and ensures updated alerts configurations at deployment time. This function coincides with the Azure landing zone principle of policy-driven governance.

Expand Down Expand Up @@ -99,6 +99,6 @@ For more information, see [Testing approach for Azure landing zones](/azure/clou
## Next steps

- [Introduction to deploying Azure Monitor](https://aka.ms/amba/alz/deploy)
- [Introduction to deploying Azure Monitor](https://azure.github.io/azure-monitor-baseline-alerts/patterns/alz/HowTo/deploy/Introduction-to-deploying-the-ALZ-Pattern/)

- [Business continuity and disaster recovery](management-business-continuity-disaster-recovery.md)
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
title: Security, governance, and compliance for Azure Virtual Desktop infrastructure
description: Learn key design considerations and recommendations for security and governance in Azure Virtual Desktop.
author: nataliakon
ms.author: nataliak
ms.author: tozimmergren
ms.date: 05/02/2022
ms.topic: conceptual
ms.custom: think-tank, e2e-avd
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
title: Identity and access management for Citrix on Azure
description: Learn how to use Azure role-based access control for identity and access management in your Citrix virtual desktop infrastructure.
author: BenMartinBaur
ms.author: martinek
ms.author: bebaur
ms.date: 01/06/2023
ms.topic: conceptual
ms.custom: think-tank, e2e-avd
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
title: Management baseline for Citrix on Azure
description: Learn how the management baseline can improve management and monitoring of Citrix on Azure.
author: BenMartinBaur
ms.author: martinek
ms.author: bebaur
ms.date: 01/06/2023
ms.topic: conceptual
ms.custom: think-tank, e2e-avd
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
title: Configure hybrid networking for Citrix on Azure
description: Learn how to use the Cloud Adoption Framework to design networking for your Azure landing zone to support multiple Citrix workloads on Azure.
author: BenMartinBaur
ms.author: martinek
ms.author: bebaur
ms.date: 07/09/2024
ms.topic: conceptual
ms.custom: think-tank, e2e-avd
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
title: Resource organization considerations for Citrix on Azure
description: Learn about the resource organization design area and how to apply it to your Citrix on Azure implementation.
author: BenMartinBaur
ms.author: martinek
ms.author: bebaur
ms.date: 02/06/2023
ms.topic: conceptual
ms.custom: think-tank, e2e-avd
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
title: Security governance and compliance for Citrix on Azure
description: Learn about key design considerations and recommendations for security governance and compliance in Citrix on Azure infrastructure.
author: BenMartinBaur
ms.author: nataliak
ms.author: bebaur
ms.date: 09/17/2024
ms.topic: conceptual
ms.custom: think-tank, e2e-avd
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@ To effectively integrate SAP with Microsoft Power Platform, select the appropria

You need to consider several factors when you select a connector for working with transactional data via the SAP ERP or SAP OData connectors. The decision might depend on the interfaces already available in your SAP system. First, check whether your SAP system exposes RFC/BAPI or OData services. For simplicity, choose the method you're most familiar with. SAP often provides both options for external connectivity.

If your system lacks RFC or OData services for the specific use case, your choice depends on connectivity requirements and what's easier to implement: API Management for OData services or an on-premises gateway for the SAP ERP connector. In general, we recommend that you expose an existing SAP OData service, or develop one if there isn't one, because of its modern architecture and flexibility. See the [SAP Business Accelerator Hub](https://api.sap.com/) to check for existing OData services.
If your system lacks RFC or OData services for the specific use case, your choice depends on connectivity requirements and what's easier to implement: API Management for OData services or an on-premises gateway for the SAP ERP connector. In general, we recommend that you expose an existing SAP OData service, or develop one if there isn't one, because of its modern architecture and flexibility. See the [SAP Business Accelerator Hub](https://api.sap.com) to check for existing OData services.

To help you implement the best solution for your scenario, the next article in this series provides detailed instructions and links to resources for setting up these connectivity options.

Expand Down

0 comments on commit 959bec0

Please sign in to comment.