How DCR-based platform logs simplify the telemetry collection for organizations managing 1,000+ resources.
The Challenge of Platform Log Collection at Scale
For many platform teams, Azure resource platform log collection starts simple—but becomes difficult to manage at enterprise scale. Imagine a team responsible for more than 8,000 Azure resources across 14 subscriptions. Every new resource needs a diagnostic setting that must be:
- Configured consistently
- Audited continuously
- Monitored for configuration drift
- Re-enabled when settings are changed or disabled
That complexity grows quickly when the same process must scale across:
- Multiple engineering teams
- Dozens of Azure regions
- Ongoing compliance and security audits
That is the reality of collecting Azure resource platform logs today with diagnostic settings.
What should be a centralized observability strategy can become a fragmented, time-consuming operational burden—driven by resource-by-resource configuration at massive scale.
Today, we’re changing that. We’re excited to announce the public preview of Data Collection Rules (DCRs) for Azure Resource Platform Logs—a centralized, secure, policy-driven way to collect platform telemetry across thousands of resources with a single rule. DCRs provide a standard model for defining data collection across Azure Monitor, including platform telemetry, metrics, logs, agents, and PaaS data sources.
If you’ve ever stared at a sprawl of Diagnostic Settings and wished for a simpler way to manage platform logs at scale, this preview is for you.
Configure once. Govern centrally. Scale infinitely
Here's how the customer pain shows up today—and how DCRs change the operating model:
|
Area |
Pain with Diagnostic Settings today |
How DCRs change it |
|
Configuration |
Configure each resource one at a time. Inconsistent coverage. Drift goes unnoticed. |
Define one DCR. Associate it with thousands of resources via DCRA. Standards stay consistent. |
|
Cost |
No way to filter or shape log data before ingestion. |
Filter and transform at ingestion time (Log Analytics destination). Send only what matters. |
|
Security |
No modern managed-identity-first pattern across all destinations. Security/Audit gaps. |
Managed identity (system- or user-assigned) with least privilege RBAC for Storage and Event Hubs. |
|
Operations |
Slow onboarding. Manual repetitive work. Hard to audit and roll back. |
Onboard at scale with ARM, Bicep, Terraform, or Azure Policy. Version-controlled like your IaC. |
|
Governance |
Fragmented workflows. Different patterns for different telemetry types. |
One declarative model. Auditable associations. Aligned with your existing rollout mechanisms. |
What can you do now
With DCRs for platform logs in public preview, your team can shift from per-resource toil to platform-scale operations:
- Define once. Apply everywhere.
Author a single DCR for the log categories you care about, then associate it with thousands of resources using ARM, Bicep, Terraform, or Azure Policy. No more per-resource configuration.
- Cut ingestion costs by filtering noise before it lands.
Shape and filter data at ingestion time when routing to Log Analytics. Only the signal you need reaches your workspace, everything else is dropped before billing.
ⓘ Transformations supported only for Log Analytics destination during preview.
- Integrate new workloads using DCR policies
Create a new subscription, apply your usual DCR through policy, and observability will be set up automatically. There’s no need for manual diagnostic settings, or concerns about drift.
- Route logs to the destination that fits each scenario.
Send analytics-grade logs to Log Analytics, archival to Storage, real-time streams to Event Hubs, and ecosystem flows to Partner Solutions—from the same management model.
- Govern with modern identity & security by default.
Managed identity (system- or user-assigned) for Storage and Event Hubs—no shared keys. Azure Policy for enforcement. Full visibility into every association.
What's next
We're continuing to invest in the DCR-based platform logs experience. On the near-term roadmap:
- More resource types expanding coverage across Azure services.
- Additional destinations including more Partner Solutions in Marketplace.
- Broader transformation support beyond Log Analytics.
- Deeper IaC and Policy integration with built-in policy definitions and reference templates.
Set up once, manage centrally, and Scale infinitely.
That's the new model for Azure platform telemetry.
References
- Platform log collection with data collection rules (Preview) - Azure Documentation
- Platform logs supported resource types and regions (Preview) - Azure Documentation
- Data collection rules in Azure Monitor — overview and concepts on Microsoft Learn
- Diagnostic Settings in Azure Monitor — for context on the current per-resource model
- Resource logs in Azure Monitor — definitions and categories