Google Meet Goes Android – Now What About MDEP?

by David Danto

 

Google announced that it is moving its Google Meet room hardware strategy from ChromeOS to Android/AOSP, working with hardware partners including Logitech, Neat, and others. Existing ChromeOS systems will continue to be supported through their expected lifecycles, but Google has made clear that Android is where its Meet room hardware strategy is headed.

At first glance, that may sound like big news: Google Meet has discovered Android – except that Android in the meeting room is hardly new.

Poly helped launch Zoom Rooms on Android with the Studio X platform at Zoomtopia in 2019. Since then, Android has become the foundation for much of the purpose-built meeting-room appliance market. Microsoft Teams, Zoom and other services have embraced Android-based room systems, while manufacturers increasingly designed essentially the same hardware platforms to support different meeting services. Google itself has already been moving in this direction, supporting Meet on Android-based hardware from Logitech and Neat.

So the interesting part isn’t really that Google Meet can run on Android hardware. That horse left the barn years ago. What is interesting is that Google has now selected Android/AOSP as the foundation of its native Meet room hardware strategy and is gradually bringing the ChromeOS hardware era to an end.

But even that isn’t the real story.

 

The real story may be a tale of two AOSPs.

When Android began emerging as a meeting-room platform, the logic was compelling. The meeting platform vendors already had Android expertise and applications. Android could run on purpose-built appliances without the cost and complexity of a Windows PC, and manufacturers could build integrated video bars and room systems instead of assembling multiple components.

The problem was that every manufacturer effectively had its own Android implementation, its own update practices, and its own security lifecycle. Some did that very well. Others did not. For the major meeting platform providers, that created a legitimate enterprise security and management problem.

Microsoft initially had an obvious answer: Windows.

Eventually, it acknowledged what the hardware market had already figured out. Android had significant advantages for purpose-built collaboration devices. If Microsoft was going to embrace Android for Teams Rooms, it needed more control over the security, management and lifecycle of the underlying platform.

Its answer was MDEP – the Microsoft Device Ecosystem Platform.

MDEP was never conceived simply as an operating system for Teams Rooms. Microsoft built it as a broader AOSP-based device platform, with security and management capabilities intended to extend across multiple kinds of purpose-built devices and experiences. Teams Rooms on Android was simply its first major deployment inside Microsoft.

That distinction was important.

Because Teams is such a dominant meeting-room platform, its transition to MDEP seemed likely to have much broader consequences. Once MDEP was running on the hardware, it made sense to consider using that same secure Android foundation for Zoom and other meeting services as well.

Microsoft itself has explicitly built MDEP to accommodate non-Teams VaaS scenarios such as Zoom, including controls for what Microsoft telemetry is collected when another meeting service is running. Conceptually, this is no different than, say, Windows. Cisco, meanwhile, is now building its next generation of Microsoft Teams devices on MDEP. Hardware vendors could build an Android endpoint, use MDEP as the secure enterprise Android foundation, and potentially support Teams, Zoom and other meeting applications on that same underlying platform.

Google was the holdout.

There was never much reason to expect Google to put Meet on Microsoft’s version of Android. And now Google has formally selected conventional AOSP as the future foundation of its own meeting-room hardware strategy.

That changes the equation considerably.

If a manufacturer wants to support Google Meet, it now needs an AOSP implementation suitable for Google Meet while continuing to support MDEP for Microsoft Teams.

If that same manufacturer had begun moving, or had planned to move, Zoom onto MDEP as well, an obvious question emerges:

Why?

If the device already needs a conventional AOSP implementation for Google Meet, why add the additional MDEP environment and its associated requirements for Zoom unless there is a compelling reason?

AOSP is already there. Zoom has historically been comfortable running on manufacturer-managed Android platforms, and Zoom continues to support appliances running AOSP implementations owned and managed by the hardware vendors.

Only six months ago, MDEP looked like it had the potential to become the security-focused Android foundation for much of the enterprise video endpoint market. Now, the market may be heading toward two Android paths: conventional AOSP for Google Meet and Zoom, with MDEP primarily required for Microsoft Teams. MDEP’s future as the industry-wide Android room system looks less certain.

That could actually simplify life for manufacturers. If they already need a conventional AOSP stack to support Google Meet, there may no longer be much reason to port Zoom onto the more restrictive MDEP environment. That also avoids placing Zoom on a platform whose security, management and telemetry architecture is fundamentally controlled by Microsoft, one of Zoom’s largest competitors.

None of this means MDEP is failing. Microsoft may broaden its appeal. Manufacturers may find ways to simplify or converge their software stacks. Zoom may see enough security or management advantages in MDEP to justify supporting it anyway. And the relationships among these platforms could evolve considerably over the next few years.

Instead of one Android platform bringing the industry together, we may wind up with two competing versions of AOSP dividing it again.

Grab the popcorn and stay tuned.

Subscribe now

Up Next

Over the next few weeks, the Daves will be all over the world, reporting from CEDIA Expo, a Logitech briefing, Zoomtopia, NAB New York, Webex One, a Nureva briefing, and a Neat briefing. The busy analyst season has begun.

This week, Dave Michels is in Phoenix for Alianza Navigate, and David Danto is home licking his wounds after the cancellation of his Hawaiian vacation (and praying for everyone on Kauai). Next week, Dave is in London for Five9 CX Connect, and David is in Palo Alto for a Logitech analyst briefing.


This was originally published via our Substack.