Intune can launch TeamViewer remote assistance sessions straight from a device's page, and the integration has changed: there's a new connector, and the old one is on its way out. In this post I'll explain how the new integration works, set it up on both the Intune and TeamViewer sides, delegate it with RBAC, fix the usual launch problems and compare it with Remote Help.
Status (October 2026): Microsoft's documentation describes a new TeamViewer connector in Intune; the previous one now appears as TeamViewer connector (old), and both can be enabled side by side. To use the new experience, you set up the new connector. TeamViewer's knowledge base states that the legacy integration will be retired in April 2027 and recommends migrating early; Microsoft's page doesn't give a date of its own. Re-check both pages, because status changes.
How the new integration works#
The new connector (TeamViewer calls it the Intune Connect integration) is deliberately thin. When a helpdesk user starts a session, Intune opens a browser tab to your TeamViewer base URL and passes two identifiers as query parameters: the Microsoft Entra device ID, and the device name as a fallback. From there TeamViewer owns everything: sign-in, finding the device, connecting and the session itself. Three consequences follow:
- The device must be known to TeamViewer: Microsoft states the integration connects to TeamViewer-managed devices with the TeamViewer host or full client installed that are also managed by your Intune tenant.
- Your TeamViewer connection settings, policies and TeamViewer conditional access rules apply to sessions started from Intune.
- Once a session is launched, support for the experience is TeamViewer's; Microsoft supports the setup in the Intune admin center.
Prerequisites#
- TeamViewer licence covering the Intune integration. TeamViewer's Device Sync article names the Microsoft Connect, Microsoft Connect Pro and Enterprise Integration add-ons; confirm with TeamViewer what your licence needs.
- Intune licence for the admin who configures the connector (or use Intune's unlicensed admins option).
- Permissions: Remote assistance connectors/Read and Update, or the Intune Administrator role.
- Platforms: Android (all enrollment options, including BYOD, COBO, COSU, COPE, AOSP and device administrator), iOS/iPadOS, macOS and Windows.
- Cloud: not supported in GCC or GCC High.
Step 1: Prepare TeamViewer#
- Deploy the TeamViewer host or full client with Intune and assign the devices to your TeamViewer company.
- In TeamViewer, open Admin settings › Organization management › Integrations. Select Authorize next to Microsoft Entra ID, then next to Microsoft Intune Device Sync, signing in with an Intune administrator account each time and confirming for your company.
- Under Synchronization › Intune device groups › Add groups, pick the Intune device groups to mirror and choose a one-time or continuous sync. TeamViewer notes that devices without TeamViewer installed aren't placed in their synced groups, so do step 1 first.
- Set up single sign-on between TeamViewer and Microsoft Entra ID, which Microsoft recommends for the best experience.
Step 2: Turn on the Intune connector#
- In the Intune admin center, go to Tenant administration › Connectors and tokens › TeamViewer connector; the old one is listed separately as TeamViewer connector (old).
- Switch Turn on TeamViewer connector to On.
- Leave the base URL at
https://web.teamviewer.com/unless your organization uses a specific TeamViewer region, in which case enter that region's subdomain. - Select Save. A confirmation appears and the connector status updates.
Step 3: Delegate sessions with RBAC#
Helpdesk staff don't need Intune Administrator. Build a custom role from these permission sets and scope it with scope tags:
| Permissions | What the holder can do |
|---|---|
| Remote assistance connectors/Read | View the connector status |
| Remote assistance connectors/Read + Remote Tasks/Offer Remote assistance | View the status and start TeamViewer sessions |
| Remote assistance connectors/Read + Remote assistance connectors/Update | View and change the connector configuration |
Someone with Read but not Update sees the connector but can't edit it; that's by design. Scoping patterns are in Intune RBAC and scope tags.
Step 4: Start a session#
- Go to Devices › All devices and open the device.
- From the device's remote actions, choose New remote assistance session (Microsoft's TeamViewer steps call it Begin a remote assistance session), select TeamViewer and then Continue.
- A new tab opens TeamViewer for that device. Sign in (ideally through SSO) and follow TeamViewer's prompts; close the TeamViewer window to end the session.
Verify#
- A test helpdesk account with the custom role sees TeamViewer as a session option and reaches the right device.
- Tenant administration › Audit logs records connector configuration changes and every session launch, with who started it.
- In TeamViewer, the mirrored Intune groups contain the expected devices.
Common problems and fixes#
| Symptom | Likely cause | Fix |
|---|---|---|
| No TeamViewer option when starting a session | Connector not switched on and saved, or the user lacks Remote Tasks/Offer Remote assistance | Check the connector page and the user's role and scope |
| Two options: TeamViewer (old) and TeamViewer | Both connectors enabled | Train staff on the new option, then turn off the old connector once migrated |
| TeamViewer opens but can't find or reach the device | No TeamViewer client, device not in your TeamViewer company, or no group sync | Deploy the client, assign the device, check Device Sync |
| TeamViewer loads the wrong environment | Base URL changed or wrong regional subdomain | Restore the default URL unless you use a specific region |
| TeamViewer refuses the connection | A TeamViewer policy or conditional access rule | Review the rule in TeamViewer; Intune doesn't override it |
| Connector unavailable | Tenant in GCC or GCC High | Not supported there; use another tool |
TeamViewer or Remote Help?#
| TeamViewer | Remote Help | |
|---|---|---|
| Vendor and licence | TeamViewer, licensed separately | Microsoft; Microsoft's licensing page lists it under Intune Plan 2, which the Intune Suite includes (check what your Microsoft 365 plan covers) |
| Started from | New remote assistance session in Intune | The same action |
| Identity | TeamViewer account, SSO with Entra ID recommended | Microsoft Entra ID for helper and user |
| Who supports the session | TeamViewer | Microsoft |
TeamViewer makes sense when it's already your helpdesk standard or you need its broad Android coverage; Remote Help keeps the whole flow in Microsoft's stack. Setup and troubleshooting for Remote Help are in Remote Help in Intune.
Tips & gotchas#
- Plan the move off the old connector now: run both briefly while a few helpdesk agents pilot the new option, then disable the old one.
- Intune passes only the Entra device ID and device name; everything else, such as access policies and conditional access rules, lives in TeamViewer.
- The device name is only a fallback for when the Entra device ID is unavailable; unique device names keep that fallback unambiguous.
References#
- Use the TeamViewer integration in Microsoft Intune (Microsoft Learn)
- Device action: new Remote Assistance session (Microsoft Learn)
- Synchronize your Intune environment with the Intune Device Sync integration (TeamViewer)
- Intune Integration: Installation and User Guide, legacy integration (TeamViewer)
