Forum Discussion
Intune Licensing - Device Enrolment
If you're assigning a single primary user to each device then its the USER that carries the licence for intune management. MS365 BusPremium as a minimum includes Intune.
If its going to be a shared device then an intune device licence is required, but there are other caveats to that too i believe.
Edit: Why are you manually doing it all through your DEM. Would autopilot not be better? Hand the new (or repurposed) device to the users, when they turn it on and log in with their licenced account it configures it accordingly to what group they are in?
Autopilot would be better, and we have tested that for a few devices. Unfortunately, we are in Hybrid Azure AD Join, and from all the research I have done, I can see that HAADJ is a nightmare to configure with pre-logon VPN, etc.
Also, I was under the assumption that our Microsoft Entra ID P1 allows Autopilot deployment without a device using an Intune license, but as per the excellent and detailed response, we need some type of Intune device license to leverage Autopilot deployment.
Basically, our IT supplier/vendor can register devices to our Azure tenant for Autopilot deployment. Those devices get delivered to our office, and the IT team then deploys them via Autopilot, with no need to manually register devices/hardware hash via PowerShell command.
But it seems that the fact that we can do it doesn't necessarily mean we are allowed to do it?! as we could potentially break some type of licensing agreement by deploying Devices using a single DEM account and leverage Autopilot deployment and Deployment profiles, which include Domain Join and Apps installations.
Basically, we don't require any other Intune add-ons, simply using Autopilot rather than MDT for device deployment.
Hopefully, the above makes some sort of sense.