Distinguish the new TeamViewer connector from its retained predecessor

Source facts

Intune retains previous settings under TeamViewer connector (old). Microsoft requires configuring the new TeamViewer connector to use the newer experience. If both remain enabled, helpdesk agents see both session options. The configured TeamViewer base URL determines the environment launched, and TeamViewer takes over authentication and session management after launch. Intune records configuration changes and session launches in its audit logs. This integration is not supported in GCC or GCC High. Microsoft Learn.

Applicability

Review an Intune tenant evaluating the newer TeamViewer integration. Identify the intended vendor environment and the devices managed by both Intune and TeamViewer with the required client installed; confirm the source’s current prerequisites before changing the connector.

DSE recommendation

Make connector choice and destination environment explicit in the helpdesk transition. Record which experience is approved, who owns each retained connector and why both might temporarily remain available. Have support staff identify the correct option before starting a real session. Review the configured base URL with the TeamViewer administrator rather than relying on a familiar label. Keep any decision to retire the previous configuration separate from the initial test.

Verification

On an authorized test device, launch the intended option and confirm the expected TeamViewer environment and device identity. Complete the vendor’s authentication and session checks, then review the Intune launch audit record. If both options are visible, verify staff guidance differentiates them. Do not treat a successful browser launch as proof that the remote session or its access policy was accepted.

Official references

Microsoft Learn: Use the latest TeamViewer integration in Microsoft Intune.