{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-416-distinguish-the-new-teamviewer-connector-from-its-retained-predecessor/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260909-416-distinguish-the-new-teamviewer-connector-from-its-retained-predecessor/", "slug": "dse-20260909-416-distinguish-the-new-teamviewer-connector-from-its-retained-predecessor", "url": "https://update.dsesecurity.com/updates/dse-20260909-416-distinguish-the-new-teamviewer-connector-from-its-retained-predecessor/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260909-416-distinguish-the-new-teamviewer-connector-from-its-retained-predecessor.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-416-distinguish-the-new-teamviewer-connector-from-its-retained-predecessor/" }, "title": "Distinguish the new TeamViewer connector from its retained predecessor", "summary": "Does an existing Intune TeamViewer configuration automatically enable the newer remote-assistance experience?", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "cyber-defense", "label": "Cyber defense", "alt": "Layered glass and metal cyber-defense structure with controlled blue and gold signal paths.", "card_url": "https://update.dsesecurity.com/assets/editorial/cyber-defense-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/cyber-defense-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/cyber-defense-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "cybersecurity", "name": "Cybersecurity", "url": "https://update.dsesecurity.com/topic/cybersecurity/" }, { "slug": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-09-10T00:25:00+00:00", "modified_at": "2026-09-10T02:04:57+00:00", "reviewed_on": "2026-09-09", "reading_minutes": 2, "word_count": 257, "potentially_affected": "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.", "primary_source": { "name": "Use the latest TeamViewer integration in Microsoft Intune - Microsoft Intune | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/intune/device-management/tools/setup-teamviewer", "published_on": null, "authority": "Microsoft Learn" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

Source facts

\n

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.

\n

Applicability

\n

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.

\n

DSE recommendation

\n

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.

\n

Verification

\n

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.

\n

Official references

\n

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

", "content_text": "Source facts\nIntune 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.\nApplicability\nReview 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.\nDSE recommendation\nMake 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.\nVerification\nOn 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.\nOfficial references\nMicrosoft Learn: Use the latest TeamViewer integration in Microsoft Intune.", "content_markdown": "## Source facts\n\nIntune 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](https://learn.microsoft.com/en-us/intune/device-management/tools/setup-teamviewer).\n\n## Applicability\n\nReview 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.\n\n## DSE recommendation\n\nMake 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.\n\n## Verification\n\nOn 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.\n\n## Official references\n\n[Microsoft Learn: Use the latest TeamViewer integration in Microsoft Intune](https://learn.microsoft.com/en-us/intune/device-management/tools/setup-teamviewer)." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/dse-20260909-416-distinguish-the-new-teamviewer-connector-from-its-retained-predecessor/", "url": "https://update.dsesecurity.com/updates/dse-20260909-416-distinguish-the-new-teamviewer-connector-from-its-retained-predecessor/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-09" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260909-416-distinguish-the-new-teamviewer-connector-from-its-retained-predecessor/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Distinguish the new TeamViewer connector from its retained predecessor", "item": "https://update.dsesecurity.com/updates/dse-20260909-416-distinguish-the-new-teamviewer-connector-from-its-retained-predecessor/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260909-416-distinguish-the-new-teamviewer-connector-from-its-retained-predecessor/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260909-416-distinguish-the-new-teamviewer-connector-from-its-retained-predecessor/", "url": "https://update.dsesecurity.com/updates/dse-20260909-416-distinguish-the-new-teamviewer-connector-from-its-retained-predecessor/", "headline": "Distinguish the new TeamViewer connector from its retained predecessor", "description": "Does an existing Intune TeamViewer configuration automatically enable the newer remote-assistance experience?", "abstract": "Does an existing Intune TeamViewer configuration automatically enable the newer remote-assistance experience?", "articleBody": "Source facts\nIntune 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.\nApplicability\nReview 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.\nDSE recommendation\nMake 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.\nVerification\nOn 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.\nOfficial references\nMicrosoft Learn: Use the latest TeamViewer integration in Microsoft Intune.", "datePublished": "2026-09-10T00:25:00+00:00", "dateModified": "2026-09-10T02:04:57+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260909-416-distinguish-the-new-teamviewer-connector-from-its-retained-predecessor/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/dse-20260909-416-distinguish-the-new-teamviewer-connector-from-its-retained-predecessor/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/cyber-defense-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/cyber-defense-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Distinguish the new TeamViewer connector from its retained predecessor" }, "articleSection": [ "Cybersecurity", "IT" ], "keywords": [ "Cybersecurity", "IT", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "Cybersecurity", "url": "https://update.dsesecurity.com/topic/cybersecurity/" }, { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "wordCount": 257, "timeRequired": "PT2M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "Use the latest TeamViewer integration in Microsoft Intune - Microsoft Intune | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/intune/device-management/tools/setup-teamviewer" } } ] } }