Content reviewed: 12 October 2026
In a regular Remote Help session, both the helper and the person sharing their session need entitlement. Enabling the service or successfully connecting does not replace this requirement. The Microsoft plan distinguishes licensing, roles, support scope and devices. A narrow exception applies to supported Samsung and Zebra Android Dedicated Device (COSU) devices: without a signed-in user, they do not require a sharer licence, but the helper still does.
What to check before purchase
| Layer | Check | Common mistake |
|---|---|---|
| Licensing | Entitlement source for each helper and supported user | A helpdesk licence covers every recipient |
| Enablement | Remote Help is enabled in the tenant | A visible menu grants usage rights |
| RBAC | Permissions and scope for the specific helper | An Intune Administrator can automatically assist anyone |
| Device | Platform, enrolment, ownership and required mode | Every mode works on every supported operating system |
| Operation | Consent, audit, network and session ownership | A successful connection completes testing |
Remote Help is disabled by default. Enabling it configures the service; it does not assign licences. An administrator role similarly grants permissions rather than user entitlement. During an incident, separate licence verification from authentication, RBAC and network failures.
Where entitlement can come from
The current Intune guide lists Remote Help in Microsoft 365 E3 from July 2026 alongside Intune Plan 2 and Advanced Analytics. E5/E7 include that layer and further capabilities. For other plans, check a separate add-on or qualifying Suite. Do not confuse Microsoft 365 E3 with Office 365 E3 or assume equivalent F3 coverage merely because core Intune is present.
In a hypothetical company with ten helpers and 120 users, reconcile entitlement on both sides. Where users already have Remote Help in their suite, do not automatically buy another add-on. Also include contractors, support accounts and new employees that an IT-department export may miss.
Windows now supports unattended access too
Older guides limiting unattended support to Android are no longer accurate. Microsoft now describes Windows unattended remote sign-in, where the helper starts a separate authenticated session. This is not silent control of an active user session. The current Remote Help overview and deployment plan explain its conditions.
| Scenario | Scope | What to verify |
|---|---|---|
| Attended Windows support | Supported viewing, control and elevation modes | App, permissions and consent |
| Unattended Windows support | Physical corporate-owned x64 device, Intune-managed and Entra joined or hybrid joined | IME, AVD agent and bootloader, Remote Desktop, power, network and dedicated RBAC permission |
| Windows 365 / AVD / BYOD | Not supported targets for Windows unattended control | Assess the appropriate attended support mode |
| Android Dedicated Device | Supported Samsung and Zebra models have specific requirements | Model, enrolment and capabilities; do not extend the sharer exception to Windows |
Windows unattended mode also has a regional restriction: Microsoft lists it as unavailable for tenants in the Switzerland North datacenter region. Check the current matrix for your cloud and platform before purchase. The operating plan must also account for sleeping or powered-off devices, which cannot receive unattended requests.
External helpdesk and RBAC
Remote Help does not support a direct session between two tenants. Treat an outsourced helper account and device as more than another email address. If support will operate inside the customer tenant, design identity, access governance, entitlement and devices around the supported model. The Remote Help plan explains this requirement.
For each helper, check the relevant session permission and scope groups. A licensed helper with the correct role can still be outside the scope of a particular user or device. Test unenrolled devices separately: All Devices is not a universal scope for every person who may need support.
A pilot that catches failures before rollout
- 01
Define people and modes
Record helpers, supported groups, platforms and required functions
- 02
Verify entitlement
Check exact SKUs and assigned service plans on both sides; assess the Android exception separately
- 03
Restrict permissions
Grant only required RBAC roles and scope groups; limit unattended access to a defined group
- 04
Run a real session
Verify sign-in, consent, required mode, session records and a rejected-access scenario
- 05
Hand over the operating procedure
Assign ownership, client updates, new-user checks and failed-support handling
Session audit information is not a video recording. Microsoft describes 30-day retention for selected metadata and states in its planning overview that the service does not store session recordings. If your organisation requires recording or longer internal records, include that requirement in tool selection and operating policies before deployment.
Frequently asked questions
Is a licence for the helper enough?
Not for a regular user session. The supported user also needs entitlement. The sharer exception applies to specific supported Samsung/Zebra Android Dedicated Device scenarios without a signed-in user.
Does Remote Help support unattended Windows assistance?
Yes. Current documentation describes a separate mode for supported physical corporate-owned x64 PCs managed by Intune. Additional technical, regional and RBAC conditions apply.
Can the same unattended mode be used for Windows 365?
No. Microsoft does not include Windows 365 or AVD as targets for Windows unattended control. Assess attended support separately.
Can sessions connect directly across tenants?
No. Direct Remote Help sessions between two tenants are unsupported.








