Microsoft recently announced unattended support with remote sign-in for Windows devices in Intune Remote Help, allowing authorized support personnel to connect to eligible devices without an end user to start or accept the session. For many IT teams, this closes the gap that kept Remote Help, Microsoft’s cloud-based remote support solution, out of serious consideration.
Unattended Remote Help allows authorized technicians to access eligible Windows devices without requiring an end user to initiate or approve the session.
It is a Remote Help session that starts without a person at the device to accept it. The support technician signs in with either a local, Active Directory, or Entra ID account. They then work in a separate Windows session while the device user’s session stays locked and preserved. If someone is signed in, a prompt gives them 30 seconds to respond before the unattended session begins. Sessions end automatically after 12 hours.
Unattended support removes the dependency on user availability, allowing IT teams to resolve issues faster and perform maintenance on their schedule.
Attended-only support creates friction whenever IT needs to:
Unattended support removes that dependency, helping IT teams resolve issues faster and work on their schedule rather than the user’s. Many organizations liked Remote Help during Intune Suite evaluations, but the lack of unattended access often prevented adoption. That objection is gone. With clipboard passthrough, file transfer, and multi-monitor support, Remote Help now reads like a real support tool rather than a screen-share utility.
This is a meaningful improvement, but there is still room for growth. Mixed or server-heavy estates will keep leaning on their existing consoles for a while, so plan for coexistence rather than a rip-and-replace.
Unattended support is available through Intune Suite, the Remote Help standalone add-on, and eligible Microsoft 365 E3 and E5 licenses. Business Premium tenants sit outside that today, a gap worth naming to smaller organizations before excitement gets ahead of the invoice.
The device requirements narrow the field further:
How Should Security Teams Scope It?
Treat unattended sign-in as privileged access, because it is. Here are some example guardrails:
Over-privileged Intune roles have shown up in real-world intrusions, so this is not a theoretical concern. Scope tightly at first and then expand when necessary.
Organizations should treat unattended access as privileged access and implement layered controls including role-based access, MFA, device restrictions, and auditing.
No. The technician works in a separate session. The signed-in user sees a lock screen and takes back control by signing in again.
Not at this stage. Windows and Android support unattended control today.
For Intune-managed corporate Windows fleets, it closes the largest gap. Mixed or server-heavy environments should plan on coexistence.
Since unattended access with file transfer, clipboard passthrough, and a credible audit trail is now available, Remote Help has become a more complete support option for organizations standardizing on Microsoft Intune. The remaining ask is broader licensing reach. Until then, this is a solid reason for Intune Suite customers to revisit support tooling spend.
Thinking through unattended Remote Help and the RBAC design behind it? Our team is happy to walk through it.