As of November 14, 2026, Microsoft’s Windows 365 What’s New page lists one new Cloud PC operations feature: Azure Monitor export for connection, connection-error, and network logs. The capability is in Public Preview and supports Azure Storage, Azure Event Hubs, or Log Analytics as destinations, according to Microsoft.
For Windows 365 administrators, the signal is clear: Cloud PC telemetry can move into established Azure monitoring workflows, but the preview label requires controlled evaluation rather than immediate production dependency.
1. Azure Monitor Log Export Enters Public Preview
What changed: Microsoft says Windows 365 can now export Cloud PC connection, connection-error, and network logs to Azure Monitor destinations. Administrators can send the data to Azure Storage, Azure Event Hubs, or Log Analytics.
Microsoft positions the export capability for longer retention, custom analysis, and troubleshooting. This is not a new Cloud PC management plane. It is a telemetry-routing option for operational data.
Why this matters: Longer retention can give support teams more historical context when investigating connection failures or network behavior. Export also allows Windows 365 data to enter the Azure destination selected by your operations team, reducing the need to treat Cloud PC diagnostics as an isolated workflow.
The operational value depends on execution. A destination without defined ownership, retention objectives, or validation criteria merely relocates the logs.
Microsoft’s entry does not establish common applicability across Windows 365 Enterprise, Business, Frontline, or other editions. Your team should not infer edition coverage from the feature name alone.
Admin action: Review Microsoft’s named guidance, “Send Windows 365 log data to Azure Storage, Event Hub, or Log Analytics,” before configuration. Confirm that the preview is available to your tenant, identify which destination aligns with your operational objective, and test whether the expected log categories arrive before relying on the export during an incident.
For endpoint architects, this creates an architecture decision: determine whether Windows 365 telemetry belongs in the same retention and analysis workflow as other endpoint and infrastructure data. For service owners, it creates an ownership decision: assign responsibility for destination access, validation, and troubleshooting.
What Cloud PC Admins Should Do Next
Confirm preview eligibility. Verify tenant availability, edition scope, prerequisites, and supported configuration through Microsoft’s implementation guidance.
Choose one operational objective. Define whether the evaluation targets longer retention, custom analysis, troubleshooting, or a combination of those outcomes.
Pilot one destination. Test Azure Storage, Azure Event Hubs, or Log Analytics in a controlled scope before expanding the configuration.
Validate all three log categories. Confirm that connection, connection-error, and network logs arrive as expected and can support the intended workflow.
Keep the current support path. Do not make a public-preview export the sole dependency for production incident response.
Until next time, keep your Cloud PCs secure and operational.