co-management licensing?

Copper Contributor

How does Licensing work for Co-Management between ConfigMgr and Microsoft Intune?

4 Replies
Hello! Thank you for your question. EMS license includes Intune license and the rights to use ConfigMgr. This is in addition to rights for Azure AD Premium, Azure Information Protection, Advanced Threat Analytics, and Cloud App Security. Since ConfigMgr license is included in Intune/EMS/Microsoft 365 licenses, you can choose to continue using ConfigMgr or start transitioning the management of all of your devices (Windows, Android, iOS, macOS) to Intune. You can learn more here: https://www.microsoft.com/en-us/cloud-platform/enterprise-mobility-security-pricing As a side note, Microsoft 365 license includes Office 365, Windows 10, and EMS licenses. So many customers are moving from traditional EA to Microsoft 365 as it gives them one license to build a modern workplace. You can learn more: https://www.microsoft.com/en-us/microsoft-365/enterprise/home

What of device-based licensing?  I'm in retail and the overwhelming majority of our devices are not assigned to users.  Our price tag was $7 million per-year to extend InTune to those devices.  I'm told that got negotiated down to two million but even that rate was impossible to rationalize.

Intune has a per-device licensing option. I don't know the details, so I would suggest to reach out to your account/licensing contact at Microsoft and ask about per-device license option with Intune. Intune/EMS user license allows up to 15 devices.

 

You might want to also take a look at Microsoft 365 Firstline: https://www.microsoft.com/en-us/microsoft-365/enterprise/firstline

Yep, that's what our licensing team looked at and got the totals above.  On devices where no user-based apps are required and they don't have O365  because it's not needed for their jobs the math just doesn't work.  Think POS devices, employment kiosks, and scales at deli counters.   For us, and I imagine we're not alone in retail, that's a majority of our devices.  We pushed hard to just do it anyways but got shot down.  MS needs to put together a more financially attractive package for this kind of use case.