fix: add missing 'Microsoft' prefix to bare 'Entra ID' references in Azure Monitor fundamentals docs#259
Conversation
…Azure Monitor fundamentals docs
|
Learn Build status updates of commit 8fe7a81: ✅ Validation status: passed
For more details, please refer to the build report. |
|
reopen for CLA check |
|
Learn Build status updates of commit 8fe7a81: ❌ Validation status: errorsPlease follow instructions here which may help to resolve issue.
For more details, please refer to the build report. Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them. |
|
Thank you for your contribution. Would you take a moment to sign the Contributor License Agreement (CLA)? After the CLA is signed, someone can review your pull request. Thanks! label:"aq-pr-triaged" |
|
@microsoft-github-policy-service agree |
|
@EoinTrial : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit eff520e:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| articles/azure-monitor/fundamentals/whats-new.md | Details | ||
| articles/azure-monitor/fundamentals/overview.md | ✅Succeeded |
articles/azure-monitor/fundamentals/whats-new.md
- Line 160, Column 1: [Warning: merge-conflict - See documentation]
File contains merge conflict markers. - Line 165, Column 1: [Warning: multiple-h1s - See documentation]
Multiple H1s(H1 '|Subservice | Article | Description |
|---|---|---|
|Alerts|Customize log search alert email subjects (preview)|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|Classic API SDK fundamentals for both ASP.NET and ASP.NET Core are now merged in one place.|
|Application-Insights|Metrics in Application Insights|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|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|We published a query to discover deprecated URL ping tests with Azure Resource Graph Explorer.|') are not allowed. You can only have one top-level heading.
- Line 166, Column 1: [Suggestion: table-syntax-invalid - See documentation]
Table syntax is invalid. Ensure your table includes a header and is surrounded by empty lines.
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
|
Learn Build status updates of commit 33fc22b: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
There was a problem hiding this comment.
Pull request overview
This PR aims to align Azure Monitor fundamentals documentation with Microsoft naming guidance by changing bare “Entra ID” references to “Microsoft Entra ID”.
Changes:
- Updated the Azure Monitor overview to refer to “Microsoft Entra ID”.
- Updated the “What’s new” entry text related to Application Insights endpoint authentication terminology (but currently via duplicated table rows).
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| articles/azure-monitor/fundamentals/whats-new.md | Attempts to update “Entra ID” wording in the July 2025 changelog table, but introduces duplicated rows and leaves one bare “Entra ID” instance behind. |
| articles/azure-monitor/fundamentals/overview.md | Replaces “Entra ID” with “Microsoft Entra ID” in the “Monitor your cloud resources” section. |
Comments suppressed due to low confidence (1)
articles/azure-monitor/fundamentals/whats-new.md:167
- The July 2025 table now contains duplicate rows for the same Application Insights articles (asp-net, metrics-overview, missing-telemetry, availability). This looks like the PR added new entries instead of editing the existing ones, which makes the changelog confusing and inconsistent. Consider updating the existing rows in-place (or removing the older duplicates) so each article appears once with a single description.
|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).|
|
Learn Build status updates of commit 1c3a42e: ✅ Validation status: passed
For more details, please refer to the build report. |
|
This pull request has been inactive for at least 14 days. If you are finished with your changes, don't forget to sign off. See the contributor guide for instructions. |
What does this PR change?
Adds the missing "Microsoft" prefix to two instances of bare "Entra ID" in the Azure Monitor fundamentals documentation.
overview.md
Before: > including audit logs from Entra ID
After: > including audit logs from Microsoft Entra ID
whats-new.md
Before: > the application must also authenticate with Entra ID or telemetry will be rejected
After: > the application must also authenticate with Microsoft Entra ID or telemetry will be rejected
Why?
Per Microsoft's naming guidance, the correct product name is always "Microsoft Entra ID", never "Entra ID" alone. Both surrounding sentences already use the full "Microsoft Entra ID" name correctly. These were the two remaining inconsistent references.
References
https://learn.microsoft.com/en-us/entra/fundamentals/new-name