Content reviewed: 12 October 2026
Do not choose a kiosk licence solely by counting people who touch the screen. Eligible enrolment, user affinity and actual features determine the design. A single-purpose screen with a required app differs from a shared tablet running personal Outlook. Describe the workflow first, then count licences.
Device-only has a defined scope
Microsoft Learn describes device-only subscriptions for eligible devices without specific user affiliation. Device-targeted policies, apps and actions are supported with appropriate enrolment. It explicitly excludes Intune App Protection Policies, Conditional Access and user-based management such as email and calendaring.
| Platform or method | Confirm before deployment |
|---|---|
| Windows Autopilot self-deploying | Actual enrolment mode and device targeting |
| Apple DEP / School Manager / Configurator without user affinity | Userless option and required features |
| Android Enterprise dedicated | Dedicated mode and apps actually used |
| Device Enrollment Manager | Eligibility and limitations of the specific enrolment |
This is not a procedure for relabelling an existing user enrolment as a kiosk. Keep deployment instructions and the policy inventory for each type. Removing the primary user in the admin interface does not itself change the apps, their data or licensing terms.
Working policies do not prove every entitlement
Current Learn guidance says an unlicensed signed-in user does not prevent device-targeted policies or apps from processing on a properly managed device-only device. This technical statement does not add rights to unsupported user features. Neither “any sign-in stops management” nor “everything works, so licensing is covered” follows from it.
MCA Product Terms restrict Intune for Devices to devices without specific user affiliation, excluding optional app installation and typical user applications such as Outlook and OneDrive. General assignment guidance lists device licensing or licences for all users as alternatives on shared devices; read that statement alongside the actual product restrictions. Use the applicable programme and terms for the contractual assessment.
Primary user is a technical property
Primary-user documentation distinguishes the primary user, enrolling account and Entra device owner. Company Portal labels devices without a primary user as shared and can technically offer available-app installation. That interface capability does not override the device-only restriction on optional apps.
Audit three records together: enrolment method, actual workflow and app/policy targeting. An empty primary-user field is just one item. If records disagree, repeat the pilot and confirm the licensing model before scaling.
Assess the actual features
| Requirement | Assessment |
|---|---|
| Required business app targeting an eligible device | Can fit device-only; check enrolment and features |
| Personal Outlook or OneDrive | Do not rely on Intune for Devices; assess user and service rights |
| App Protection Policies | Qualifying user Intune entitlement required |
| Conditional Access | Not covered by device-only; check Entra and associated user requirements |
| Optional Company Portal apps | Technical availability is not device-only permission |
Licence assignment guidance also requires an Intune licence for users receiving an App Protection Policy without enrolling their device. In a user-licensed design, one enrolling account cannot replace all user entitlements. Check each person’s actual service plan and dependent apps.
Specialty and Teams devices have additional rules
Specialty device management is a separate capability with further prerequisites. Microsoft requires the relevant quantity of user entitlements for specialty devices in Entra Shared Device Mode: its example of ten users sharing one device needs ten corresponding entitlements. This is not a universal rule that every ordinary kiosk requires Plan 2.
Assess Teams phones and rooms under their specific Teams licensing model. A generic Intune device licence does not replace the telephone or meeting-service licence. Check related Intune coverage in existing packages before purchasing another licence.
Example: a kiosk’s use changes
A hypothetical reception screen deploys automatically without user affinity and runs a required booking app. Device-only may fit. Later, receptionists start opening personal email and independently installing available apps. The screen count is unchanged; the service scope has changed. Reassess licensing even if the device continues receiving its policies.
Build an auditable record
- 01
Describe one kiosk type
Platform, enrolment, site, actual users and accounts
- 02
Separate the features
Required device apps, optional installs, personal services, App Protection and access
- 03
Check entitlements
Actual product and contract programme; existing user and additional rights
- 04
Test a representative device
Enrolment, targeting, installation, sign-in, data and removal after a session
- 05
Set reassessment triggers
Changes to apps, enrolment, user features or security policies
For a broader comparison, see Intune: user or device licensing. This procedure focuses on verifying an actual kiosk and separating technical state from licensed scope.
Frequently asked questions
Does an empty primary-user field prove device-only licensing?
No. Check enrolment, apps, targeting and contractual rights. Primary user is one technical property.
Does an unlicensed sign-in stop device policies?
Microsoft says sign-in alone does not prevent device-targeted processing in a supported device-only scenario. It does not grant user-feature rights.
Does device-only cover App Protection and Conditional Access?
No. Microsoft explicitly excludes them. Assess the required Intune and Entra user entitlements.
Does every shared device need a specialty licence?
Not automatically. Specialty device management is a specific capability with its own prerequisites; check the device, usage and included rights.








