From 8fe7a815301a1306f592158f16b0e5e7192a6956 Mon Sep 17 00:00:00 2001 From: Eoin Shaughnessy Date: Sat, 4 Apr 2026 21:22:00 +0100 Subject: [PATCH 1/3] fix: add missing 'Microsoft' prefix to bare 'Entra ID' references in Azure Monitor fundamentals docs --- articles/azure-monitor/fundamentals/overview.md | 2 +- articles/azure-monitor/fundamentals/whats-new.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/articles/azure-monitor/fundamentals/overview.md b/articles/azure-monitor/fundamentals/overview.md index df5dcec95b..ab1de31992 100644 --- a/articles/azure-monitor/fundamentals/overview.md +++ b/articles/azure-monitor/fundamentals/overview.md @@ -14,7 +14,7 @@ In addition to supporting Azure Monitor features, the Azure Monitor data platfor :::image type="content" source="media/overview/overview.png" alt-text="Diagram that shows an overview of Azure Monitor with data sources sending data, and Azure Monitor features using the collected data." border="false" lightbox="media/overview/overview.png"::: ## Monitor your cloud resources -Azure Monitor collects logs and metrics from all the resources across the different Azure services that you use, including audit logs from Entra ID. This monitoring data is integrated into the Azure portal experience for each service. View a summary of the health and performance of your resources and then drill down into more detailed monitoring data and analysis tools to investigate and troubleshoot issues. Some services also provide dedicated monitoring experiences called Azure Monitor insights that deliver deep visibility into the performance and operation of your cloud resources. +Azure Monitor collects logs and metrics from all the resources across the different Azure services that you use, including audit logs from Microsoft Entra ID. This monitoring data is integrated into the Azure portal experience for each service. View a summary of the health and performance of your resources and then drill down into more detailed monitoring data and analysis tools to investigate and troubleshoot issues. Some services also provide dedicated monitoring experiences called Azure Monitor insights that deliver deep visibility into the performance and operation of your cloud resources. See [Monitor Azure resources](../platform/monitor-azure-resource.md). diff --git a/articles/azure-monitor/fundamentals/whats-new.md b/articles/azure-monitor/fundamentals/whats-new.md index 0ee755f9a3..72516dce39 100644 --- a/articles/azure-monitor/fundamentals/whats-new.md +++ b/articles/azure-monitor/fundamentals/whats-new.md @@ -146,7 +146,7 @@ This article lists significant changes to Azure Monitor documentation. |Alerts|[Customize log search alert email subjects (preview)](../alerts/alerts-customize-email-subject-how-to.md)|Log search alert email subjects can now be customized.| |Application-Insights|[Application Insights for ASP.NET and ASP.NET Core applications](../app/asp-net.md)|Classic API SDK fundamentals for both ASP.NET and ASP.NET Core are now merged in one place.| |Application-Insights|[Metrics in Application Insights](../app/metrics-overview.md)|The documentation now clarifies that Azure Monitor Metrics and Workspaces ingest custom metrics at a fixed 60-second interval, regardless of how often they're sent, while Log Analytics records them at the actual send interval. We also introduced the OTEL_METRIC_EXPORT_INTERVAL environment variable, allowing configuration of the OpenTelemetry metric export interval, with a default of 60 seconds.| -|Application-Insights|[Troubleshoot missing application telemetry in Azure Monitor Application Insights](/troubleshoot/azure/azure-monitor/app-insights/telemetry/investigate-missing-telemetry)|Clarified that when using Microsoft Entra ID for the Application Insights data collection endpoint, the application must also authenticate with Entra ID or telemetry will be rejected.| +|Application-Insights|[Troubleshoot missing application telemetry in Azure Monitor Application Insights](/troubleshoot/azure/azure-monitor/app-insights/telemetry/investigate-missing-telemetry)|Clarified that when using Microsoft Entra ID for the Application Insights data collection endpoint, the application must also authenticate with Microsoft Entra ID or telemetry will be rejected.| |Application-Insights|[Application Insights availability tests](../app/availability.md)|We published a query to discover deprecated URL ping tests with [Azure Resource Graph Explorer](/azure/governance/resource-graph/first-query-portal).| |Application-Insights|[Sampling in Azure Monitor Application Insights with OpenTelemetry](../app/opentelemetry-sampling.md)|All sampling links from the Azure portal now go directly to our OpenTelemetry guidance.| |Platform|[Azure Monitor activity log](../platform/activity-log.md)|Rewritten for clarity and to consolidate articles.| From 33fc22b3c6cfb058d89111d6a029ac6cb8043aa8 Mon Sep 17 00:00:00 2001 From: Eoin Shaughnessy <45000144+EoinTrial@users.noreply.github.com> Date: Mon, 6 Apr 2026 19:11:59 +0100 Subject: [PATCH 2/3] Remove stray conflict markers from merge resolution --- articles/azure-monitor/fundamentals/whats-new.md | 3 --- 1 file changed, 3 deletions(-) diff --git a/articles/azure-monitor/fundamentals/whats-new.md b/articles/azure-monitor/fundamentals/whats-new.md index f18eae6de5..cbb27a8edf 100644 --- a/articles/azure-monitor/fundamentals/whats-new.md +++ b/articles/azure-monitor/fundamentals/whats-new.md @@ -157,17 +157,14 @@ This article lists significant changes to Azure Monitor documentation. |Subservice | Article | Description | |---|---|---| |Alerts|[Customize log search alert email subjects (preview)](../alerts/alerts-customize-email-subject-how-to.md)|Log search alert email subjects can now be customized.| -<<<<<<< fix/azure-monitor-bare-entra-references |Application-Insights|[Application Insights for ASP.NET and ASP.NET Core applications](../app/asp-net.md)|Classic API SDK fundamentals for both ASP.NET and ASP.NET Core are now merged in one place.| |Application-Insights|[Metrics in Application Insights](../app/metrics-overview.md)|The documentation now clarifies that Azure Monitor Metrics and Workspaces ingest custom metrics at a fixed 60-second interval, regardless of how often they're sent, while Log Analytics records them at the actual send interval. We also introduced the OTEL_METRIC_EXPORT_INTERVAL environment variable, allowing configuration of the OpenTelemetry metric export interval, with a default of 60 seconds.| |Application-Insights|[Troubleshoot missing application telemetry in Azure Monitor Application Insights](/troubleshoot/azure/azure-monitor/app-insights/telemetry/investigate-missing-telemetry)|Clarified that when using Microsoft Entra ID for the Application Insights data collection endpoint, the application must also authenticate with Microsoft Entra ID or telemetry will be rejected.| |Application-Insights|[Application Insights availability tests](../app/availability.md)|We published a query to discover deprecated URL ping tests with [Azure Resource Graph Explorer](/azure/governance/resource-graph/first-query-portal).| -======= |Application-Insights|[Application Insights for ASP.NET and ASP.NET Core applications](../app/asp-net.md)|[Classic API](/previous-versions/azure/azure-monitor/app/classic-api) SDK fundamentals for both ASP.NET and ASP.NET Core are now merged in one place.| |Application-Insights|[Metrics in Application Insights](../app/metrics-overview.md)|The documentation now clarifies that Azure Monitor Metrics and Workspaces ingest custom metrics at a fixed 60-second interval, regardless of how often they're sent, while Log Analytics records them at the actual send interval. Introduced the OTEL_METRIC_EXPORT_INTERVAL environment variable, allowing configuration of the OpenTelemetry metric export interval, with a default of 60 seconds.| |Application-Insights|[Troubleshoot missing application telemetry in Azure Monitor Application Insights](/troubleshoot/azure/azure-monitor/app-insights/telemetry/investigate-missing-telemetry)|Clarified that when using Microsoft Entra ID for the Application Insights data collection endpoint, the application must also authenticate with Entra ID or telemetry is rejected.| |Application-Insights|[Application Insights availability tests](../app/availability.md)|Published a query to discover deprecated URL ping tests with [Azure Resource Graph Explorer](/azure/governance/resource-graph/first-query-portal).| ->>>>>>> main |Application-Insights|[Sampling in Azure Monitor Application Insights with OpenTelemetry](../app/opentelemetry-sampling.md)|All sampling links from the Azure portal now go directly to our OpenTelemetry guidance.| |Platform|[Azure Monitor activity log](../platform/activity-log.md)|Rewritten for clarity and to consolidate articles.| |Platform|[Resource logs in Azure Monitor](../platform/resource-logs.md)|Rewritten for clarity and to consolidate articles.| From 1c3a42e1ffe430a5f802768325d969b9af151814 Mon Sep 17 00:00:00 2001 From: Eoin Shaughnessy Date: Mon, 6 Apr 2026 21:40:37 +0100 Subject: [PATCH 3/3] fix: remove duplicate rows and fix bare Entra ID reference in whats-new --- articles/azure-monitor/fundamentals/whats-new.md | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/articles/azure-monitor/fundamentals/whats-new.md b/articles/azure-monitor/fundamentals/whats-new.md index cbb27a8edf..7b899ae9df 100644 --- a/articles/azure-monitor/fundamentals/whats-new.md +++ b/articles/azure-monitor/fundamentals/whats-new.md @@ -157,13 +157,9 @@ This article lists significant changes to Azure Monitor documentation. |Subservice | Article | Description | |---|---|---| |Alerts|[Customize log search alert email subjects (preview)](../alerts/alerts-customize-email-subject-how-to.md)|Log search alert email subjects can now be customized.| -|Application-Insights|[Application Insights for ASP.NET and ASP.NET Core applications](../app/asp-net.md)|Classic API SDK fundamentals for both ASP.NET and ASP.NET Core are now merged in one place.| -|Application-Insights|[Metrics in Application Insights](../app/metrics-overview.md)|The documentation now clarifies that Azure Monitor Metrics and Workspaces ingest custom metrics at a fixed 60-second interval, regardless of how often they're sent, while Log Analytics records them at the actual send interval. We also introduced the OTEL_METRIC_EXPORT_INTERVAL environment variable, allowing configuration of the OpenTelemetry metric export interval, with a default of 60 seconds.| -|Application-Insights|[Troubleshoot missing application telemetry in Azure Monitor Application Insights](/troubleshoot/azure/azure-monitor/app-insights/telemetry/investigate-missing-telemetry)|Clarified that when using Microsoft Entra ID for the Application Insights data collection endpoint, the application must also authenticate with Microsoft Entra ID or telemetry will be rejected.| -|Application-Insights|[Application Insights availability tests](../app/availability.md)|We published a query to discover deprecated URL ping tests with [Azure Resource Graph Explorer](/azure/governance/resource-graph/first-query-portal).| |Application-Insights|[Application Insights for ASP.NET and ASP.NET Core applications](../app/asp-net.md)|[Classic API](/previous-versions/azure/azure-monitor/app/classic-api) SDK fundamentals for both ASP.NET and ASP.NET Core are now merged in one place.| |Application-Insights|[Metrics in Application Insights](../app/metrics-overview.md)|The documentation now clarifies that Azure Monitor Metrics and Workspaces ingest custom metrics at a fixed 60-second interval, regardless of how often they're sent, while Log Analytics records them at the actual send interval. Introduced the OTEL_METRIC_EXPORT_INTERVAL environment variable, allowing configuration of the OpenTelemetry metric export interval, with a default of 60 seconds.| -|Application-Insights|[Troubleshoot missing application telemetry in Azure Monitor Application Insights](/troubleshoot/azure/azure-monitor/app-insights/telemetry/investigate-missing-telemetry)|Clarified that when using Microsoft Entra ID for the Application Insights data collection endpoint, the application must also authenticate with Entra ID or telemetry is rejected.| +|Application-Insights|[Troubleshoot missing application telemetry in Azure Monitor Application Insights](/troubleshoot/azure/azure-monitor/app-insights/telemetry/investigate-missing-telemetry)|Clarified that when using Microsoft Entra ID for the Application Insights data collection endpoint, the application must also authenticate with Microsoft Entra ID or telemetry is rejected.| |Application-Insights|[Application Insights availability tests](../app/availability.md)|Published a query to discover deprecated URL ping tests with [Azure Resource Graph Explorer](/azure/governance/resource-graph/first-query-portal).| |Application-Insights|[Sampling in Azure Monitor Application Insights with OpenTelemetry](../app/opentelemetry-sampling.md)|All sampling links from the Azure portal now go directly to our OpenTelemetry guidance.| |Platform|[Azure Monitor activity log](../platform/activity-log.md)|Rewritten for clarity and to consolidate articles.|