Merge pull request #308008 from ProfessorKendrick/metrics-logs-ani

v-shils · web-flow · commit 728b51a732f5 · 2025-12-10T10:42:28.000-08:00
ANI metrics and logs conceptual article
diff --git a/articles/partner-solutions/datadog/create.md b/articles/partner-solutions/datadog/create.md
@@ -3,7 +3,7 @@ title: Create a Datadog resource
 description: Get started with Datadog on Azure by creating a new resource, configuring metrics and logs, and setting up single sign-on through Microsoft Entra ID.
 ms.topic: quickstart
 zone_pivot_groups: datadog-create
-ms.date: 09/04/2025
+ms.date: 12/01/2025
 ms.custom:
   - references_regions
   - ai-gen-docs-bap
@@ -127,7 +127,7 @@ There are required fields (identified with a red asterisk) in each section that
 
 ### Metrics and logs tab (optional)
 
-If you wish, you can configure resources to send metrics/logs to Datadog.
+If you wish, you can configure resources to send metrics/logs to Datadog. For more information, see [Monitor & Observe Azure resources with Azure Native Integrations](../metrics-logs.md).
 
 Enter the names and values for each *Action* listed under Metrics and Logs.
 
@@ -136,17 +136,7 @@ Enter the names and values for each *Action* listed under Metrics and Logs.
 - Select **Send subscription activity logs**.
 - Select **Send Azure resource logs for all defined sources**.
 
-#### Inclusion and exclusion rules for metrics and logs
-
-To filter the set of Azure resources that send logs to Datadog, use inclusion and exclusion rules and set Azure resource tags.
-
-- All Azure resources with tags defined in include rules send logs to Datadog.
-- All Azure resources with tags defined in exclude rules don't send logs to Datadog.
-
-> [!NOTE]
-> If there's a conflict between inclusion and exclusion rules, exclusion takes priority.
-
-Select the **Next** button at the bottom of the page.
+After you finish configuring metrics and logs, select **Next**.
 
 ### Security tab (optional)
 
diff --git a/articles/partner-solutions/datadog/link-to-existing-organization.md b/articles/partner-solutions/datadog/link-to-existing-organization.md
@@ -76,7 +76,7 @@ There are required fields (identified with a red asterisk) in the first two sect
 
 ### Metrics and logs tab (optional)
 
-If you wish, you can configure resources to send metrics/logs to Datadog.
+If you wish, you can configure resources to send metrics/logs to Datadog. For more information, see [Monitor & Observe Azure resources with Azure Native Integrations](../metrics-logs.md).
 
 Enter the names and values for each *Action* listed under Metrics and Logs.
 
@@ -85,17 +85,7 @@ Enter the names and values for each *Action* listed under Metrics and Logs.
 - Select **Send subscription activity logs**.
 - Select **Send Azure resource logs for all defined sources**.
 
-#### Inclusion and exclusion rules for metrics and logs
-
-To filter the set of Azure resources that send logs to Datadog, use inclusion and exclusion rules and set Azure resource tags.
-
-- All Azure resources with tags defined in include rules send logs to Datadog.
-- All Azure resources with tags defined in exclude rules don't send logs to Datadog.
-
-> [!NOTE]
-> If there's a conflict between inclusion and exclusion rules, exclusion takes priority.
-
-Select the **Next** button at the bottom of the page.
+After you finish configuring metrics and logs, select **Next**.
 
 ### Security tab (optional)
 
diff --git a/articles/partner-solutions/datadog/manage.md b/articles/partner-solutions/datadog/manage.md
@@ -187,3 +187,7 @@ You can also request support in the Azure portal from the [resource overview](#r
 
 Select **Support + Troubleshooting** > **New support request** from the service menu, then choose the link to [log a support request in the Datadog portal](https://www.datadoghq.com/support). 
 
+## Related content
+
+- [Monitor & Observe Azure resources with Azure Native Integrations](../metrics-logs.md)
+
diff --git a/articles/partner-solutions/datadog/overview.md b/articles/partner-solutions/datadog/overview.md
@@ -31,31 +31,9 @@ Datadog provides the following capabilities:
 - **Unified billing** - Datadog costs are reported through Azure monthly bill.
 - **Single sign-on to Datadog** - You don't need a separate authentication for the Datadog portal.
 - **Log forwarder** - Enables automated forwarding of subscription activity and resource logs to Datadog.
-- **Metrics collection** - Automatically send all Azure resource metrics to Datadog.
+- **Metrics collection** - Automatically send all Azure resource metrics to Datadog. For more information, see [Monitor & Observe Azure resources with Azure Native Integrations](../metrics-logs.md).
 - **Datadog agent deployment** - Provides a unified management experience of Datadog agents. Install and uninstall Datadog agents as extensions on Virtual Machines and Azure App Services.
 
-## Metrics and logs
-
-There are three types of logs that you can send from Azure to Datadog.
-
-- **Subscription level logs** - Provide insight into the operations on your resources at the [control plane](../../azure-resource-manager/management/control-plane-and-data-plane.md). Updates on service health events are also included. Use the activity log to determine the what, who, and when for any write operations (PUT, POST, DELETE). There's a single activity log for each Azure subscription.
-
-- **Azure resource logs** - Provide insight into operations that were taken on an Azure resource at the [data plane](../../azure-resource-manager/management/control-plane-and-data-plane.md). For example, getting a secret from a Key Vault is a data plane operation. Or, making a request to a database is also a data plane operation. The content of resource logs varies by the Azure service and resource type.
-
-- **Microsoft Entra logs** - As an IT administrator, you want to monitor your IT environment. The information about your system's health enables you to assess potential issues and decide how to respond.
-
-The Microsoft Entra admin center gives you access to three activity logs:
-
-- [Sign-in](../../active-directory/reports-monitoring/concept-sign-ins.md) – Information about sign-ins and how your resources are used by your users.
-- [Audit](../../active-directory/reports-monitoring/concept-audit-logs.md) – Information about changes applied to your tenant like users and group management or updates applied to your tenant's resources.
-- [Provisioning](../../active-directory/reports-monitoring/concept-provisioning-logs.md) – Activities performed by the provisioning service, like the creation of a group in ServiceNow or a user imported from Workday.
-
-The types of Azure resource logs are listed in [Azure Monitor Resource Log categories](/azure/azure-monitor/essentials/resource-logs-categories). To filter the set of Azure resources sending logs to Datadog, use Azure resource tags.
-
-You can request your IT Administrator to route Microsoft Entra logs to Datadog. For more information, see [Microsoft Entra activity logs in Azure Monitor](../../active-directory/reports-monitoring/concept-activity-logs-azure-monitor.md).
-
-Azure charges for the logs sent to Datadog. For more information, see the [pricing of platform logs](https://azure.microsoft.com/pricing/details/monitor/) sent to Azure Marketplace partners.
-
 ## Subscribe to Datadog
 
 [!INCLUDE [subscribe](../includes/subscribe.md)] *Datadog*.
diff --git a/articles/partner-solutions/dynatrace/create.md b/articles/partner-solutions/dynatrace/create.md
@@ -3,7 +3,7 @@ title: Create Azure Native Dynatrace Service resource
 description: This article describes how to use the Azure portal to create an instance of Dynatrace.
 
 ms.topic: quickstart
-ms.date: 03/13/2025
+ms.date: 12/01/2025
 
 ---
 
@@ -62,13 +62,13 @@ There are required fields (identified with a red asterisk) that you need to fill
 
 ### Metrics and logs tab (optional)
 
-If you wish, you can configure resources to send metrics/logs to Dynatrace. 
+If you wish, you can configure resources to send metrics/logs to Dynatrace. For more information, see [Monitor & Observe Azure resources with Azure Native Integrations](../metrics-logs.md).
 
 - Select **Enable metrics collection** to set up monitoring of platform metrics.
 - Select **Subscription activity logs** to send subscription-level logs to Dynatrace.
 - Select **Azure resource logs** to send Azure resource lots to Dynatrace. 
 
-Select the **Next** button at the bottom of the page.
+After you finish configuring metrics and logs, select **Next**.
 
 ### Single sign-on tab (optional)
 
diff --git a/articles/partner-solutions/dynatrace/manage.md b/articles/partner-solutions/dynatrace/manage.md
@@ -148,4 +148,5 @@ Select **Support + Troubleshooting** from the service menu, then choose the link
 ## Related content
 
 - [Get started with infrastructure monitoring](https://www.dynatrace.com/support/help/how-to-use-dynatrace/hosts/basic-concepts/get-started-with-infrastructure-monitoring)
+- [Monitor & Observe Azure resources with Azure Native Integrations](../metrics-logs.md)
 
diff --git a/articles/partner-solutions/dynatrace/overview.md b/articles/partner-solutions/dynatrace/overview.md
@@ -31,7 +31,7 @@ Azure Native Dynatrace Service provides the following capabilities:
 - **Seamless onboarding** - Easily onboard and use Dynatrace as natively integrated service on Azure.
 - **Unified billing** - Get a single bill for all the resources you consume on Azure, including Dynatrace.
 - **Single-Sign on to Dynatrace** - You need not sign-up or sign in separately to Dynatrace. Sign in once in the Azure portal and seamlessly transition to Dynatrace portal when needed.
-- **Log monitoring** - Enables automated monitoring of subscription activity and resource logs to Dynatrace
+- **Log monitoring** - Enables automated monitoring of subscription activity and resource logs to Dynatrace. For more information, see [Monitor & Observe Azure resources with Azure Native Integrations](../metrics-logs.md).
 - **Manage Dynatrace OneAgent on VMs and App Services** - Provides a single experience to install and uninstall Dynatrace OneAgent on virtual machines and App Services.
 
 ### Billing
diff --git a/articles/partner-solutions/elastic/create.md b/articles/partner-solutions/elastic/create.md
@@ -3,7 +3,7 @@ title: Create Elastic application
 description: This article describes how to use the Azure portal to create an instance of Elastic, including Elastic Search, Elastic Observability, and Elastic Security.
 ms.topic: quickstart
 zone_pivot_groups: elastic-resource-type
-ms.date: 07/15/2025
+ms.date: 12/01/2025
 ms.custom: sfi-image-nochange
 #customer intent: As an Azure developer, I want to create Elastic resources to use search, log analytics, and security monitoring functions for Azure environments.
 
@@ -106,7 +106,7 @@ Select **Elastic Observability**.
 
 ### Logs & metrics tab (optional)
 
-You can configure resources to send metrics and logs to Elastic.
+You can configure resources to send metrics and logs to Elastic. For more information, see [Monitor & Observe Azure resources with Azure Native Integrations](../metrics-logs.md).
 
 - Select **Send subscription activity logs**.
 - Select **Send Azure resource logs for all defined sources** (default).
diff --git a/articles/partner-solutions/elastic/manage.md b/articles/partner-solutions/elastic/manage.md
@@ -469,4 +469,4 @@ You can also request support in the Azure portal from the [resource overview](#r
 ## Related content
 
 - [What is Azure private link?](../../private-link/private-link-overview.md)
-
+- [Monitor & Observe Azure resources with Azure Native Integrations](../metrics-logs.md)
diff --git a/articles/partner-solutions/elastic/overview.md b/articles/partner-solutions/elastic/overview.md
@@ -33,7 +33,7 @@ The Elastic integration with Azure includes the following technical capabilities
 - **Integrated onboarding** – Deploy Elastic resources directly from Azure portal using the Microsoft.Elastic resource provider.
 - **Azure billing integration** – Track Elastic resource consumption and charges through the Azure billing system.
 - **Azure Active Directory authentication** – Access Elastic services using Azure AD credentials for single sign-on.
-- **Log forwarding** – Route Azure subscription activity and resource logs to Elastic for indexing and analysis.
+- **Log forwarding** – Route Azure subscription activity and resource logs to Elastic for indexing and analysis. For more information, see [Monitor & Observe Azure resources with Azure Native Integrations](../metrics-logs.md).
 - **Centralized management** – Configure and monitor log shipping from Azure services to Elastic through a unified interface.
 - **Flexible deployment options** – Choose between serverless projects for usage-based scaling and cloud-hosted projects for dedicated, managed clusters.
 - **Elastic Agent deployment** – Deploy and manage Elastic Agents on Azure virtual machines using integrated workflows.
diff --git a/articles/partner-solutions/metrics-logs.md b/articles/partner-solutions/metrics-logs.md
@@ -0,0 +1,79 @@
+---
+title: Azure Native Integrations monitoring overview
+description: "Overview of metrics and logs for Azure Native Integrations and key operational considerations."
+ms.topic: overview
+ms.date: 12/01/2025
+ai-usage: ai-assisted
+
+#customer intent: As a cloud operator, I want to understand what telemetry partner integrations collect so that I can plan monitoring and governance.
+
+---
+
+# Monitor & Observe Azure resources with Azure Native Integrations
+
+Monitoring and observability are essential for managing modern cloud environments. Azure integrates with leading partner solutions to provide comprehensive metrics and logs collection. These integrations enable centralized visibility, actionable insights, and streamlined troubleshooting across your Azure resources. 
+
+## Metrics
+
+Quantitative data that reflects the performance and health of your Azure resources.
+
+For metrics, the system automatically creates a system managed identity and assigns it the Monitoring Reader role, which is required for data collection. If you remove this identity or role assignment, metric collection stops.
+
+You can enable your partner resource to collect metrics for all Azure resources within any linked subscriptions. Optionally, you can limit metric collection for Azure Virtual Machines and App Service plans by attaching Azure tags to your resources.
+
+For metrics, the system automatically creates a system managed identity and associates it with the resource on Azure. The setup process provides the Monitoring Reader role to the system managed identity. This role gives the partner service the ability to pull metrics for resources in your subscription from Azure Monitor.
+
+> [!WARNING]
+> If you remove the system managed identity or the Monitoring Reader role assignment, the partner can't collect metrics from your Azure resources.
+
+### Tag rules for sending metrics
+
+Virtual machines, Virtual Machine Scale Sets, and App Service plans with include tags send metrics to the partner.
+
+If there's a conflict between inclusion and exclusion rules, exclusion takes priority. You can't limit metric collection for other resource types.
+
+For example, if you configure a tag rule in which only virtual machines, Virtual Machine Scale Sets, and App Service plans tagged with True are included, only resources with this tag send metrics to the partner. All other virtual machines, Virtual Machine Scale Sets, and App Service plans are excluded from metrics collection.
+
+## Logs
+
+Logs provide detailed records of activity and events within your Azure environment. These logs provide valuable insights for monitoring, troubleshooting, and auditing. With Azure Native Integrations, you can collect and forward various types of logs from your Azure resources directly to the partner service based on configurable tag-based rules. For a complete list of supported log categories, see [Supported Resource log categories for Azure Monitor](/azure/azure-monitor/reference/logs-index).
+
+The inclusion and exclusion tags determine which logs for all defined sources are sent to partner resources. By default, you collect logs for all resources.
+
+The tag rules match the tags that are available on Azure resources in your subscription. If you select Include and add tags that match resources for your subscription, they're in scope for monitoring. By default, platform resource logs are enabled.
+
+### Tag rules for sending logs
+
+- Azure resources with include tags send logs.
+- Azure resources with exclude tags don't send logs.
+
+If there's a conflict between inclusion and exclusion rules, exclusion takes priority.
+
+### Azure activity logs
+
+Azure activity logs, or subscription-level logs, capture operations performed at the [control plane](/azure/azure-resource-manager/management/control-plane-and-data-plane) of your Azure subscription. These logs provide a comprehensive record of management events, such as resource creation, modification, and deletion, and service health notifications. By analyzing subscription-level logs, you can answer important questions like who made changes, what actions (PUT, POST, DELETE) were taken, and when they occurred. This information is essential for auditing, governance, and understanding overall activity within your Azure environment. It helps you maintain security, track changes, and ensure compliance across your cloud resources. There's a single activity log for each Azure subscription.
+
+### Azure resource logs
+
+Azure resource logs capture detailed operations performed at the [data plane](/azure/azure-resource-manager/management/control-plane-and-data-plane) of individual Azure resources. These logs record interactions that are specific to each resource. For example, reading data from a storage account, querying a database, or accessing secrets in Azure Key Vault. The content and structure of resource logs vary depending on the Azure service and resource type. By collecting and analyzing resource logs, you gain deeper visibility into application behavior and can troubleshoot issues at the resource level and monitor how your services are being used. This level of insight is valuable for performance optimization, security monitoring, and ensuring the reliability of your Azure workloads.
+
+### Microsoft Entra Logs
+
+Microsoft Entra logs provide detailed insights into identity and access management activities within your Azure environment. These logs help you monitor user sign-ins, authentication attempts, and changes to users, groups, or roles. This monitoring enables you to track access patterns, detect suspicious activity, and maintain compliance with security policies.
+The Microsoft Entra admin center offers three main types of activity logs:
+
+- [Sign-in logs](/entra/identity/monitoring-health/concept-sign-ins): Track user sign-ins and resource usage.
+- [Audit logs](/entra/identity/monitoring-health/concept-audit-logs): Record changes to your tenant, such as user and group management or updates to resources.
+- [Provisioning logs](/entra/identity/monitoring-health/concept-provisioning-logs): Capture activities performed by the provisioning service, like creating groups in external systems or importing users.
+
+For instructions on how to send Microsoft Entra ID logs to a partner, see [Integrate Microsoft Entra logs with Azure Monitor logs](/entra/identity/monitoring-health/howto-integrate-activity-logs-with-azure-monitor-logs).
+
+
+## Enabling and managing integration
+
+Each service provides step-by-step instructions for setup and management:
+
+- [QuickStart: Get started with Datadog](datadog/create.md)
+- [Quickstart: Get started with Dynatrace](dynatrace/create.md)
+- [QuickStart: Get started with Elastic](elastic/create.md)
+- [Quickstart: Get started with New Relic](new-relic/create.md)
diff --git a/articles/partner-solutions/new-relic/create.md b/articles/partner-solutions/new-relic/create.md
diff --git a/articles/partner-solutions/new-relic/manage.md b/articles/partner-solutions/new-relic/manage.md
diff --git a/articles/partner-solutions/new-relic/overview.md b/articles/partner-solutions/new-relic/overview.md
diff --git a/articles/partner-solutions/toc.yml b/articles/partner-solutions/toc.yml

Original file line number	Diff line number	Diff line change
`@@ -148,4 +148,5 @@ Select Support + Troubleshooting from the service menu, then choose the link`
`148`	`148`	`## Related content`
`149`	`149`
`150`	`150`	`- [Get started with infrastructure monitoring](https://www.dynatrace.com/support/help/how-to-use-dynatrace/hosts/basic-concepts/get-started-with-infrastructure-monitoring)`
	`151`	`+- [Monitor & Observe Azure resources with Azure Native Integrations](../metrics-logs.md)`
`151`	`152`