Exploring #MDEP with Microsoft’s Ilya Bukshteyn #MicrosoftTeams
Recently, we had the opportunity to meet with Ilya Bukshteyn, Vice President for Teams Calling, Devices, Events, and Teams Premium at Microsoft, to delve into the Microsoft Device Ecosystem Platform (MDEP). This conversation provided valuable insights into the evolution, purpose, and future of MDEP. Here are some key takeaways (but do check out the video here.)
The Microsoft Device Ecosystem Platform, or MDEP is essentially a version of the Android Open Source Project (AOSP) distribution that Microsoft has customized and will make available to its partners for various devices. The idea behind MDEP was to create a unified, Microsoft-controlled version of Android to enhance device interoperability and security.
Ilya explained that Microsoft’s partners originally pushed for an Android-based system due to the complexities and costs associated with Windows.
At this (pre-MDEP) point, Teams on Android represent about half of MS Teams Room users. Microsoft realized that supporting multiple, inconsistent versions of Android across different OEMs was unsustainable. MDEP addresses three main challenges:
- Upgradability: Unlike Windows, where updates were controlled centrally, each OEM was responsible for Android updates, which was costly and inefficient. MDEP allows Microsoft to manage updates centrally, ensuring all devices stay current.
- Security: Microsoft’s internal IT and security teams initially hesitated to deploy Android devices due to security concerns. MDEP addresses this by ensuring all devices meet Microsoft’s security standards.
- Interoperability: With multiple OEMs creating different versions of Android, ensuring consistent peripheral support was challenging. MDEP will standardize this, making it easier for partners and providing a better experience for users.
A key benefit of MDEP is that it reduces the Android investment for OEM partners, but that’s a double-edged sword as many partners consider their investments in Android as a competitive advantage. Ilya focused on the global supportability of the MTR solution from a Microsoft perspective.
Looking ahead, MDEP will play a crucial role in the certification process for Microsoft Teams devices. Ilya foresees that MDEP will eventually become a requirement for Microsoft Teams certification. This means that – at some unspecified future point – any device seeking certification will need to run on MDEP to ensure consistency, security, and upgradability across all certified devices. This move will streamline the certification process and provide users with a more reliable and cohesive ecosystem of Teams-compatible devices.
When we asked Ilya whether it was worth the effort for existing, mature Android partners to transition to MDEP given there would be no immediate gain in features, his response was insightful. He acknowledged the challenge but emphasized the long-term benefits. The transition to MDEP, while not offering immediate new features, would provide a more stable, secure, and upgradable platform. The centralized control over updates and security enhancements would lead to a more consistent user experience and reduced maintenance efforts for partners in the long run. This strategic shift, although demanding initially, was designed to ensure a more sustainable and efficient ecosystem.
Addressing Microsoft’s Security Record
Security is a perennial concern, and we didn’t shy away from discussing Microsoft’s historical security record with Ilya. He candidly addressed the issue, acknowledging past challenges while highlighting the significant strides Microsoft has made in recent years. With MDEP, security is a top priority, and Microsoft has implemented rigorous standards to ensure all devices meet stringent security requirements. The centralized update mechanism within MDEP also plays a crucial role in maintaining security across all devices, allowing Microsoft to promptly address vulnerabilities and push updates seamlessly. This proactive approach aims to build trust and reliability in Microsoft’s commitment to security.
Competing Platforms and Reluctance
We also explored the potential reluctance of competing platforms to adopt a Microsoft-controlled version of Android. Ilya understood the apprehensions but stressed the collaborative nature of MDEP would parallel that of Windows – where many Teams competitors are present today. By creating a standardized platform, Microsoft aims to enhance interoperability and simplify the development process for partners. He noted that while some competitors might initially be hesitant, the long-term benefits of a unified platform – such as reduced fragmentation, consistent updates, and enhanced security – would outweigh the concerns. The goal of MDEP is not to dominate but to create a cohesive and efficient ecosystem that benefits all stakeholders.
Conclusion
The thought of a Microsoft-approved version of Android may seem odd at first, but it makes sense. Microsoft is, after all, an operating system company. Windows has its place, but so does Android.
There’s also a recurring theme where Google innovates and Microsoft perfects. Google was first with a web-based office productivity suite. Office 365 came years better and offers far more functionality. Google reinvented the web browser with Chrome, and Microsoft took the open-source project to create Edge with more enterprise-needed features. Google was way ahead of Azure on cloud compute, but Microsoft has better addressed the needs of enterprises.
Google created the open-source version of Android but only controls its implementation on Play Store-ready mobile devices. With MDEP, Microsoft has taken the project and turned it into an enterprise-ready alternative to Windows. It is conceptually similar to what Red Hat did with Linux. Microsoft adopted Android in meeting rooms long before Google did, but is accepting it graciously into the MTR family with its own implementation.
This chat with Ilya provided a clearer picture of MDEP and its benefits and challenges than we had heard to date. As we move forward, I look forward to seeing how MDEP evolves and continues to shape the landscape of collaboration technology.
Stay tuned for more updates and conversations as we continue to explore how this will affect Microsoft customers, partners, and competitors.
To hear this detailed conversation for yourself, listen to the podcast here