Why exactly is Microsoft offering its ‘version’ of Android? And how exactly will it impact AV? Hurrairah bin Sohail explores how MDEP is being approached by end users and manufacturers.
Android has occupied a complicated position within the professional AV landscape. It serves as the backbone for countless devices, both consumer and commercial, from smartphones, tablets, to touchpanels, compute products, and many more. However, its acceptance in professional and enterprise environments where AV operates has often been tepid at best.
In many organisations, especially those with stringent InfoSec policies, Android has effectively been a ‘dirty’ word. Whether users are permitted to connect Android devices via BYOD in a commercial or enterprise environment is not a forgone conclusion. Contrast this with the wider level of acceptance for iOS devices as BYOD end points and it is easy to deduce that Android comes with ‘security concerns’. The core of the issue lies in the open-source nature of the Android operating system, which is its strength and weakness. A major concern for enterprise is the uncertainty regarding exactly what flavour of Android a device is running. Following on from that, version control is also a major factor, and support remains a challenge due to the myriad Android versions available on the market.
In recent times, end user preferences have started to lean heavily towards Windows-based solutions due to the rise in popularity of Teams. Windows-based architecture comes with its own set of challenges but provides a pathway to Microsoft certifications that put end users’ minds at ease. However, manufacturers still find value in the Android operating system when creating and designing products.
This friction is what Microsoft Device Ecosystem Platform (MDEP) aims to address. The platform is an Android-based solution from Microsoft that enables device manufacturers and software developers to create products, backed by Microsoft’s reputation. Built on the Android Open Source Project (AOSP), the platform is designed to be extended and customised for both hardware and software solutions.
AV products incorporating MDEP are already on the market, and our prediction is that more will be launched at ISE 2026. James Ware, APAC alliances lead, Neat, explains that Neat officially joined the MDEP programme in September 2025. He elaborates: “From Neat’s perspective, we remain focused on delivering innovative meeting experiences. That is our vision and we are going to continue towards it. We are very much aligned with the MDEP promise. If Microsoft is going to deliver on simple deployment, streamlined device management, seamless updates, and easy pairing across devices, customers will essentially be able to move faster with better security.”
The first product from Neat using MDEP has launched already. The Neat Board 32 was announced in 2025 and is the manufacturer’s first MDEP device. Ware notes that it is still early in the platform lifecycle to report back on the full impact regarding the switch to MDEP and the goals Microsoft is trying to deliver for customers. However, one of the unique aspects is not just the MDEP platform itself, but the opportunity for Neat to innovate around that platform.
Ware says: “It is important to have that differentiation. It is not just a vanilla Microsoft Teams Room or MDEP solution. It is Microsoft plus Neat delivering on the vision of what we are trying to provide for the customer. If you think about what MDEP is promising around easier manageability and better security, it aligns with our vision of providing a simpler, more intuitive meeting room experience.”
However, incorporating MDEP into products is not necessarily an easy task. Mavis Leung, manager, technical sales Asia, Crestron, suggests that MDEP is quite resource intensive. She expands: “When OEMs are designing hardware, they might not have initially provisioned for MDEP in the specifications due to its relative infancy. We need to think through how the OS updates will be accommodated in general and having these considerations be addressed through R&D takes time.”
Currently, Crestron devices running Android OS include room booking panels, control touch screen, the Videobar 70, and more.
Leung shares her thoughts on the pros and cons of operating systems, noting that clients, especially in enterprise or government who utilise Teams and the cloud, are looking for security which Microsoft is great at addressing. She says: “Android is beneficial because OEMs get more control over revisions of the application, rather than the auto-updates experienced with Windows OS. But Android OS is still pretty new in the enterprise environment. Unlike the IT environment where we all know the standard security compliance protocols, such as consistent security patching and hardening methods, on Android, as an open ecosystem, no one is entirely sure what standards are being followed yet. Someone needs to step up, and perhaps MDEP could address this, but it is a journey that everybody needs to learn from.”
Looking ahead, MDEP products from Crestron are on the way with plans to launch them at ISE 2026. Based on our conversations, Crestron’s strategy will be to continue offering Windows-based devices for existing customers with the additional option alongside them on Android OS and MDEP. Leung elaborates: “We want to ensure that if they choose a path, we have the entire new lineup available for them. MDEP is a really good initiative that we should embrace. We will keep it in mind when designing products, and those will be kept in line with Microsoft’s requirements. 2026 will be the year we rapidly adopt MDEP into our products.”
From an end user perspective, the reception towards MDEP is cautious. There is a sense of ‘wait and see’ regarding the platform. When a player of Microsoft’s calibre makes a move, end users must take notice. But enterprise is not a speedboat, it is a cruise liner and changing course takes time. Decisions around the adoption of new products and new platforms take time.
More specifically, the lifecycle of devices is a critical consideration. If you consider MTR or VC devices, the lifecycle of these products in deployment is longer purely because they are attached to a physical space. Enterprise cannot realistically upgrade the hardware in spaces every three to five years from a CapEx or management point of view simply because new products have been launched. In addition, enterprise requires assurances that new products and platforms will be supported. If MDEP is not here to stay, that represents a big risk for adopters. The success of MDEP will likely hinge on its ability to prove that it is not just a temporary bridge, but a long-term foundation for the future of enterprise AV.