By: Kara Wang | Product Manager 2, Microsoft Intune & Ingrid Allen | Senior Product Manager, Windows
Support sessions are most effective when your helpdesk team can quickly start with the right device context. In many cases, helpdesk staff still need to confirm key system details with the user before moving into targeted troubleshooting.
In attended Windows support sessions, Diagnostic Data Reports in Remote Help for Windows is now available to help quickly onboard helpdesk staff with device information while maintaining user trust. In this context, attended sessions are sessions where the user participates and grants helpdesk staff access. These sessions support view only access, full control, and optional User Account Control (UAC) elevation. This capability is currently not available for Windows Remote Help unattended sessions.
With this feature, your helpdesk team can request diagnostic data directly in the Remote Help session and generate a Diagnostic Data Report to guide troubleshooting. If updated information is needed, the helpdesk staff can refresh the report during the session. The user decides whether to allow sharing, can view what is shared, and can stop sharing at any time. Helpdesk staff receive practical context for faster, more informed troubleshooting, and the user keeps clear control.
Figure 1: Remote Help session with Diagnostic Data Reports available to helpdesk staff.Why this matters for your support operations
When your team starts with structured diagnostic context, helpdesk staff spend less time on discovery and more time on resolution. That improves first pass troubleshooting and reduces repeat clarifying questions.
You also keep the consent model transparent:
- The user explicitly allows or declines sharing.
- The user can see the shared data.
- The user can stop sharing during the session.
This balance helps you improve support speed while maintaining confidence in your remote support process.
How Diagnostic Data Reports work in Remote Help
- For attended Windows device sessions, the helpdesk staff requests diagnostic data collection by selecting the icon in the Remote Help toolbar.
Figure 2: Helpdesk staff requests a Diagnostic Data Report. - The user sees a request asking permission for the helpdesk staff to view and possibly store their device diagnostic data.
- The user chooses Allow or Decline.
Figure 3: Device user consent prompt for diagnostic data sharing.
If the user selects Allow:
- The helpdesk staff sees a report with collapsible sections with options to Refresh, Copy, and Collapse All.
- A View Shared Data button appears on the user’s toolbar.
- When the user selects View Shared Data, the diagnostic panel appears in the Remote Help app.
- The same diagnostic data report is shown to the helpdesk staff and the user.
If the user selects Decline, helpdesk staff is notified. If the user initially allows the report to be generated and later chooses to turn sharing off, helpdesk staff is notified that the user stopped sharing data.
Demo
What data categories are shared, and how should you use them?
When the user allows sharing, the report organizes data into practical categories. These categories help your helpdesk staff move from collecting context to resolving issues.
| Category | Example data | Admin/helpdesk value |
|---|---|---|
| Device overview | OS edition, build and architecture; device model and manufacturer; whether the device is a virtual machine; display language and system locale; kiosk mode. | Confirms baseline environment and quickly rules out mismatched device context. |
| Hardware | Processor, cores and logical processors; installed memory; disk capacity; neural processing unit (NPU), when reported. | Validates whether hardware limits are contributing to the issue. |
| Network | Maximum speed, link speed, and current send and receive rates. | Helps detect low throughput and unstable connectivity conditions. |
| GPU | Graphics adapter, GPU usage, and dedicated, shared and available GPU memory. | Supports graphics, rendering, and display troubleshooting. |
| Performance | Processor time, memory usage, page file, disk activity, network usage, and uptime. | Identifies current system pressure and likely bottlenecks. |
| Battery | Whether a battery is present, charge level and status, battery health, and design versus full charge capacity. | Useful for mobile device behavior and power-related incidents. |
| Security | Antivirus product, whether it's active and its definition status; firewall status for domain, private and public networks; TLS inspection detection. | Surfaces security controls that may affect app or network behavior. |
| Updates | Windows Update channel, target release version, last check and install dates, counts of pending and failed updates, last restart time, and whether a restart is pending. | Highlights update gaps or pending restart dependencies. |
| Storage | For each disk: model, bus and media type, capacity, free space, percentage used, drive letters, boot or system disk, and health status. | Helps isolate disk health and capacity-related failures. |
| Network interfaces | For each network adapter: type, description, status, speed, whether DHCP is enabled, and whether the adapter is virtual. | Speeds diagnosis of adapter configuration and connectivity issues. |
| Devices | Name and status of cameras, audio devices, displays, printers, keyboards, mice, Bluetooth devices and network adapters. | Validates peripheral availability and health for user-facing issues. |
Figure 4: Diagnostic Data Report categories used for triage.
What to expect from the report during troubleshooting
Diagnostic Data Reports give your helpdesk staff a reliable snapshot of device state to guide each troubleshooting step.
- Diagnostic values are captured as a point in time snapshot.
- Metrics like memory, CPU, and network activity reflect device state at collection time.
- After a change, the helpdesk staff can refresh to collect a current snapshot and validate whether remediation changed the device’s state.
- If a field is missing, this means that the device did not report that value. It does not mean healthy, false, or zero by default.
This gives your helpdesk staff a clearer context for decision making and helps keep troubleshooting steps grounded in current, observable device data.
User control and session behavior
Users can inspect what was shared by selecting View Shared Data after they allow sharing. This helps maintain transparency during the session.
If sharing is turned off, previously collected information remains visible for reference, but refreshing data is unavailable until sharing is turned back on. If the user resumes sharing, the helpdesk staff can refresh to collect a current snapshot.
This model lets you keep troubleshooting continuity while respecting user control.
Real-world support example: Screen share lag despite healthy network
A user reports choppy screen sharing and delayed remote control, even though their connection appears healthy. The helpdesk staff can spend time validating connectivity with separate checks and still struggle to determine whether the issue is network congestion or endpoint resource contention.
With Diagnostic Data Reports in Remote Help, the helpdesk staff requests the report and reviews Network, Performance, and GPU together in real time. The helpdesk staff confirms stable link speed and normal send and receive throughput but also sees elevated CPU and GPU pressure during the session. This indicates an endpoint bottleneck rather than a bandwidth problem. The helpdesk staff guides the user to close high impact apps and reduce display and graphics load, then refreshes the report to confirm improved responsiveness.
The result is faster confirmation of whether lag is network related or endpoint related, fewer unnecessary escalations to network teams, and quicker in session recovery with immediate validation after each fix.
Next steps
Diagnostic Data Reports are rolling out now and expected to be available to all Intune customers by mid-December, so give them a try in your next Windows attended session and see how much time they save you. We'd love to hear how it goes. If you have feedback or questions, drop us a note in the comments below!
Learn more
- Remote Help documentation: https://aka.ms/remotehelpdocs
- Microsoft 365 Roadmap: https://www.microsoft.com/microsoft-365/roadmap
Stay up to date! Bookmark the Microsoft Intune Blog and Intune Customer Success Blog and follow us on LinkedIn or @MSIntune and @IntuneSuppTeam on X to continue the conversation.