Why is MDEP Taking So Long?
Listening to the “TalkingPointz Chatz” podcast featuring Dave Michels and David Danto about the current state of Microsoft’s MDEP was an enlightening experience. Two key insights stood out to me: that MDEP is taking far longer than expected to come to market, and there are several reasons that might explain why.
MDEP’s Development is Dragging On
David and Dave didn’t mince words – MDEP’s launch is taking far longer than anticipated. Microsoft’s ambitious plan to unify device ecosystems under one platform has hit several delays. Originally intended to create a unified version of Android for all Microsoft Teams Room (MTRoA) devices, the rollout has so far been non-existent, raising some eyebrows. As Dave Michels pointed out, “We’ve been hearing about MDEP for a year and a half now, but it’s still nowhere near where it needs to be.”
David Danto added that this lag is causing frustration across the industry. Manufacturers and users alike are waiting for clarification on a number of key issues – certification requirements, end-of-certification dates, and more – but the timeline keeps stretching. The longer this takes, the more doubt creeps in about whether MDEP will deliver what was initially promised.
Multiple Factors are Slowing Progress
One of the key takeaways from the discussion was that several factors are slowing MDEP’s progress. Dave and David highlighted a few in particular. First, the sheer complexity of trying to unify so many different devices and platforms is a monumental task. Microsoft is juggling demands from hardware manufacturers and software developers, each with their own priorities and challenges.
Another issue is the reluctance of key players in the industry to fully commit to MDEP. Many of Microsoft’s manufacturing partners have invested heavily in their own version of Android ecosystems, which they perceive as giving them a market advantage. They’re not rushing to embrace a Microsoft-led platform that could diminish that advantage. As David mentioned, “Convincing major players that invested time and money in their own Android ecosystems to buy into this vision is a lot harder than just building the tech.”
There’s also the issue that devices running on the MDEP operating system currently cannot be managed by Microsoft’s Intune platform. Intune needs to switch to an AOSP model that has not yet been rolled out. As David explained, “It makes no sense for Jabra to ship its Panacast 50 VBS on MDEP if that means it can’t be managed by enterprises.”
Dave and David speculated about when we might actually see MDEP in general availability (GA). David believed it could still happen later this year, but Dave was less optimistic, suggesting it may drag into next year as the AOSP version of Intune is just now entering the Microsoft TAP program.
Leave a Comment