Microsoft Intune announces device-only subscription for shared resources

Published 11-01-2018 03:28 AM 141K Views
The meaning of “devices” has evolved in the modern workplace, with IT expected to support not only corporate PCs and bring-your-own (BYO) devices, but also manage kiosks, shared single-purpose devices, phone-room resources, collaboration devices such as Surface Hub, and even some IoT devices. Microsoft Intune is the most comprehensive unified endpoint management platform to manage and secure this proliferation of endpoints in your organization. We are excited to share a licensing update today that further lowers your total cost of ownership (TCO).
Microsoft Intune is pleased to announce a new device-only subscription service that helps organizations manage devices that are not affiliated with specific users. The Intune device SKU is licensed per device per month. 
It is worth noting that device-based subscription does not allow you to take advantage of any user-based security and management features, including but not limited to email and calendaring, conditional access, and app protection policies. Device SKU also cannot be used for shared device scenarios where the device is managed through the user(s) on the device. Shared devices that are not affiliated with any user identity can leverage this license, for example, certain Android Enterprise purpose-build devices and kiosks as well as Windows kiosks. This license may provide compelling value for devices using enrollment methods such as Windows Autopilot self-deploying mode, Apple Business Manager or Google zero touch enrolment, where the devices are not associated with a user and no user targeted features are required, such as user-based enrollment, Intune Company Portal, conditional access, and such. 
For more information, please contact your Microsoft representative and review the Microsoft Licensing Terms
(Updated 12/20 to clarify the self-deploying use-case for Windows Autopilot)
New Contributor

How can the Intune for Devices licenses be purchased through the Office/Microsoft 365 admin portal?

New Contributor

Is it possible to describe the prerequisites for these subscription model? 

Not applicable
Senior Member

So this license can be used to for a self deploying autopilot Kiosk? I am in a project where we want to build a public use multi app Kiosk and self deploy with autopilot. 

Occasional Contributor

Please make the auto MDM enrollment from AAD P1 a part of this license - so we can use Autopilot to provision KIOSK devices.


Senior Member

Link in article does not work anymore. Was content moved or did MSFT have second thoughts on the topic?


Hi Daniel, both links seem to be working fine within the article. Which one did you mean?

Senior Member

Hi Mayunk, thanks for following up. It's the link at the end of your article: I believe the embedded URL contains a trailing space which leads to an 404 error.


Hi @Daniel Sidler thanks for calling out. I've fixed it now. Let me know if it is still broken

Senior Member

I have built and deployed self deploying autopilot kiosks without a device license assigned - is this expected   ?

Occasional Visitor

Hi, we orderes the following license: "Microsoft Intune Device". Further we assigned that license as the only license to a new user. Now we want to register a brand new HP Elitebook with Win 10 Pro on it with that new user. Eventually it leaves us with the Error-No. 0x80180003 (Server error, please try again). According to the Microsoft-Docs, this Error-No implies, that this user may have exceeded the allowed amount of devices to be registered (wo do not have any registered devices in intune/AzureAD yet). Also Microsoft says, that you will have to have Win 10 Pro as your OS, which we have (Win 10 Pro 1809).


We really dont know, how to move on from that point. We have to register and manage 30+ Win 10 Pro devices. And we are not willing to buy Hard-/Software and Licensing for a on-premise-DC.


Thank you so much.

kind regards,


Occasional Contributor
Hey @dmnksgrs, which of the enrollment methods ( did you use?
Occasional Visitor

Hello, how it is possible to license Windows 10 Enterprise tablets as kiosk devices without assigned users with collaboration of Intune and Microsoft Defender ATP?

Senior Member

Hi Mayunk, I am deploying a self-deploying Autopilot profile to multiple shared PC's with Windows 10. The enrolment should be zero touch and while it does automate part of the setup steps it unfortunately still prompts for privacy settings during the OOBE. In this situation, could the issue relate to the devices not having device based Intune licenses assigned ?  I have read elsewhere that despite a device based license being a pre-requisite it doesn't stop Autopilot and OOBE from functioning the way it should. Are you able to confirm either way please.


Hi Andy, this is not related to device-based licensing. Per my understanding, Windows Autopilot should always suppress the privacy page in OOBE.  If this isn’t happening, please open a support case. 

Regular Visitor

How can I check that status of device-based licensing within a tenant? Is it possible to see how many licenses have already been procured and used? The documentation on this point seems to be pretty cryptic thus far...

Occasional Visitor

Hi Mayunk,

Apologies if this has been answered elsewhere but how/where do I buy Intune Device licenses from?




I actually have a significant issue with this. I've been looking at using self-deploying as it fits our business model better than bulk or others as they do not work with auto-pilot. 


The automatic $2 a month charge, when we have a significant number of M365 E5 licensing is extremely problematic, and is making me consider dropping Intune as our MDM provider.


Hi @Lynn Towle 


Thanks for being an Intune customer and for sharing your feedback. 

To clarify, if you already have sufficient M365 E5 or EMS/Intune user licenses to cover all your self-deploying devices, you may not need additional device-only SKU. This device license is useful when customers have, say, 100 kiosks that are not going to be associated with users but they only want to manage the device itself from Intune. If these kiosks will not have user-identity or apps such as Office 365 on them, some customers may save costs by choosing device-only subscription for these 100 kiosks instead of extending their full M365/ EMS. As mentioned above, if you do have user-association (i.e. AAD users login/ logout) on the devices, even if they are shared, then you still require the M365 or EMS/Intune licenses. 
Hope this helps. Please feel free to contact your account representative if you have more questions, and we'll be happy to address them.   

@Mayunk Jain, thank you for the additional clarification!    

Not applicable

@Mayunk Jain 


Can you clarify how Azure AD P1 licenses come into play here?


If there are 5 Azure AD users, but 25 Kiosk devices would this license count be accurate?

  • 5x Azure AD P1 licenses
  • 5 Intune user licenses
  • 25 Intune device-only licenses

Hi @Deleted 


It is recommended that you work with your account team to confirm licensing, since they will have most complete understanding of your situation. See my response above w.r.t scenario where additional device-only licenses may be needed. Based on your information, 25 device-only licenses are sufficient to deploy 25 kiosks and your existing AADP1 licenses cover the use of Windows Autopilot self-deploying mode as well. 

Frequent Visitor

Hi @Mayunk Jain 


A customer (non-profit org) is needing Intune device-only subscription.

I have found the license on my CSP platform but :


- Does the SKU exists for non-profit organizations ?
I only found the license for commercial organizations.


- How can the device-only subscription is affected to the devices ?
I cannot find where to get a list of licensed and unlicensed devices to view the status of them.





Occasional Visitor

Hi @Mayunk Jain 


I have two questions:



If you have Enterprise Mobility + Security Licenses, then do you need to purchase Intune Device Based licenses when you want to use Kiosk mode with Automatic Logon? 


I ask this because I have scenario where I'm unable to use Autopilot Self-Deploying mode (due to lack off TPM 2.0). So I'd need to first sign into the device using an Azure AD user that has an Intune license. After a while the device will receive the Kiosk Device Configuration Policy, then it will reboot and automatically sign on using the local Kiosk account.   So in this scenario, would a user-based license be sufficient?



If you're using Autopilot Self-Deploying mode to deploy Kiosks, and you only have User-based licenses (like EMS E3, Microsoft 365 E3, etc.), then how do you assign those licenses to those devices? Or is it sufficient to just have them in possession. And if it is sufficient, does that mean that you need to make sure that you "reserve" an activation for that device? For instance: you have one user who has licensed 4 Windows devices, and has 1 license left for a Kiosk device, then that person must make sure not to use the remaining license on another pc, correct?


Thanks in advance.





New Contributor

How does this compare with using a Device Enrollment Management account?

Occasional Contributor

I have a few devices configured using the Kiosk mode, However, my licenses are still not being used.

Version history
Last update:
‎Apr 02 2020 08:19 AM
Updated by: