DeviceView vs. TeamViewer for Android + Intune
TeamViewer Doesn't Work With Your Corporate-Owned Android Devices in Intune
If your Android fleet is enrolled in Microsoft Intune as corporate-owned fully managed — the enrollment mode Microsoft recommends for enterprise — TeamViewer's integration doesn't apply. This isn't a rumor. It's on Microsoft's own documentation page.
Does TeamViewer's Intune integration work with Android Enterprise corporate-owned devices?
No. Microsoft's own documentation confirms that TeamViewer's Intune integration works through the Company Portal app and does not support Android Enterprise corporate-owned fully managed devices. DeviceView supports every Intune Android enrollment type (BYOD work profile, corporate-owned fully managed, dedicated, and shared) with one agent.
Last reviewed: · DeviceView editorial
The documentation
What Microsoft's Documentation Actually Says
Microsoft maintains a support article titled "Use TeamViewer to remotely administer Intune devices" on Microsoft Learn. In that article, under the prerequisites and limitations section, Microsoft states that Android Enterprise corporate-owned devices are not supported, and that TeamViewer works with the Company Portal app, not the Intune app.
These are two related constraints that compound into a single outcome: if your organization manages Android devices the way Microsoft tells you to manage them — corporate-owned fully managed, administered through the Intune app — TeamViewer's remote support integration does not function for those devices.
This isn't a configuration issue. It isn't a setting that IT can toggle. It's an architectural limitation of how TeamViewer connects to Intune-managed devices.
The impact
Why This Matters More Than It Sounds
Android Enterprise corporate-owned fully managed is the enrollment mode that enterprises are migrating toward, and that Microsoft actively recommends for organization-owned devices. It gives IT full control over the device: app deployment, security policy enforcement, kiosk mode lockdown, and managed Google Play configuration. It's the mode used for shared devices in healthcare, point-of-sale terminals in retail, rugged handhelds in logistics, and field devices in utilities and construction. For how this limitation compounds with TeamViewer's add-on model, see DeviceView vs. TeamViewer for Android.
The older enrollment methods — device administrator, personally-owned with work profile — are either deprecated or designed for BYOD, not for corporate-owned fleets.
So when an organization standardizes on Intune with Android Enterprise corporate-owned enrollment (which is what Microsoft's own deployment guides recommend), they discover that one of the most widely deployed remote support tools on the market simply doesn't integrate with their device management platform for that device class. The "launch remote session from the Intune console" button that works for Windows devices doesn't work for their corporate-owned Android devices.
At that point, the IT team has three options:
- Maintain a separate remote support workflow outside of Intune for Android devices.
- Downgrade their Android enrollment mode to accommodate TeamViewer's limitations, sacrificing management capabilities.
- Switch to a remote support platform that actually supports their enrollment model.
Root cause
The Company Portal vs. Intune App Gap
The distinction between Company Portal and the Intune app is the technical root of the problem.
Company Portal is Microsoft's app for user-driven enrollment and self-service scenarios. It's what employees use on personally-owned devices to enroll in BYOD programs, install corporate apps, and check compliance status. On corporate-owned fully managed devices, Company Portal is not the management surface — the Intune app is.
TeamViewer's Intune integration hooks into Company Portal. It sends a remote session notification through Company Portal, and the end user accepts it there. On a corporate-owned fully managed device, Company Portal either isn't installed, isn't the active management agent, or doesn't have the notification pathway that TeamViewer depends on.
This means TeamViewer's Intune integration is fundamentally scoped to the BYOD and personally-owned enrollment models — not the corporate-owned model that enterprises use for their managed fleets.
Industry impact
Who This Affects
Healthcare systems
Bedside tablets, patient check-in kiosks, telehealth carts, and mobile clinical devices are typically corporate-owned Android devices enrolled in Intune. When a bedside tablet freezes during patient education or a check-in kiosk goes down at 7 AM in a 40-provider clinic, IT needs to remotely control that device immediately. If their remote support platform doesn't integrate with their enrollment mode, they're dispatching a technician on foot.
Retail and hospitality
Point-of-sale tablets, inventory scanners, and customer-facing displays are corporate-owned. A POS device that can't be remotely recovered during a Saturday rush means lost revenue and a customer experience failure. TeamViewer's Intune integration won't reach these devices.
Logistics and field services
Rugged Android handhelds used by drivers, technicians, and field workers are corporate-owned and enrolled in Intune for security policy enforcement. These devices are often hundreds of miles from the nearest IT staff. Remote control that requires the field worker to interact with a Company Portal notification is unreliable at best.
Education
Shared Android tablets in classrooms and labs are corporate-owned. Students are not going to accept a remote support prompt through Company Portal. IT needs unattended access through the management platform they already use.
Any organization with shared devices
The defining characteristic of a shared device — multiple users, no single "owner" logged in — is exactly the scenario where Company Portal-dependent remote support breaks down. Shared devices don't have a persistent user to receive and accept a TeamViewer session notification.
The right approach
What a Working Integration Looks Like
A working Intune integration for corporate-owned Android devices means the remote support agent is deployed through Intune's managed app configuration. It inherits device-level permissions at enrollment — not user-level permissions granted through a Company Portal notification. The IT admin sees the device in their remote support console the moment it completes enrollment. They can launch a remote view or control session without any action from the person holding the device (if anyone is holding it at all). Session logs feed back into the compliance and audit trail that Intune already maintains. For how DeviceView's security posture compares to TeamViewer overall, see DeviceView vs. TeamViewer Security.
Common questions
Frequently Asked Questions
What IT teams ask about TeamViewer, Intune, and corporate-owned Android devices.