Close Menu
Peter Klapwijk – In The Cloud 24-7Peter Klapwijk – In The Cloud 24-7
    Facebook X (Twitter) Instagram
    Peter Klapwijk – In The Cloud 24-7Peter Klapwijk – In The Cloud 24-7
    • Home
    • Intune
    • Windows
      • Modern Workplace
    • macOS
    • Android
    • iOS
    • Automation
      • Logic Apps
      • Intune Monitoring
      • GitHub
    • Security
      • Passwordless
      • Security
    • Speaking
    • About me
    Peter Klapwijk – In The Cloud 24-7Peter Klapwijk – In The Cloud 24-7
    Home»Intune»Prevent personal Windows 10 devices from enrolling to Microsoft Intune
    Intune

    Prevent personal Windows 10 devices from enrolling to Microsoft Intune

    Peter KlapwijkBy Peter KlapwijkMarch 19, 2019Updated:December 3, 201923 Mins Read

    Sometimes you see a lot of personally owned devices show up in your Intune dashboard. If you want to prevent this from happening you can use Device enrollment restrictions in Intune to block personal devices. In this post I will show you how to prevent personally owned Windows 10 devices from enrolling in Microsoft Intune.

    When blocking personally owned devices, we have below options to enroll in Intune:

    • The enrolling user is using a device enrollment manager account.
    • The device enrolls through Windows AutoPilot.
    • The device is registered with Windows Autopilot but is not an MDM enrollment only option from Windows Settings.
    • The device’s IMEI number is listed in Device enrollment > Corporate device identifiers. (Not supported for Windows Phone 8.1.)
    • The device enrolls through a bulk provisioning package.
    • The device enrolls through GPO, or automatic enrollment from SCCM for co-management.

    Setup enrollment restriction

    In Intune we have the option to set device enrollment restrictions for Android (work profile), iOS, macOS and Windows. But we focus in this post on Windows.

    1. Open the Device Management portal and click Device enrollment – Enrollment Restrictions
    2. Click Create restriction

    1. Give the enrollment restriction policy a Name
    2. Select Device Type Restriction in the dropdown list
    3. Click Select Platforms
    4. Switch on all required platforms

    1. Click Configure platforms
    2. Set Windows (MDM) to Block to prevent personal Windows devices to enroll in MDM
    3. Click OK and Create

    Now we need to assign the policy to a security group. In my example I assign it to a group with all my Intune licensed users.

    End-user experience

    Now let`s have a look at the end-user experience. We have blocked the option to enroll personally owned Windows 10 devices.
    When the users tries to manually enroll the device in MDM from Settings is looks like this.

    With the error: There was a problem.
    Your organization does not support this version of Windows (0x80180014)

    When the user tries to manually join Azure AD with automatic MDM enrollment from Settings.

    Image title

    Your subtitle here

    We see this error: Something went wrong.
    This feature is not supported. Contact your system administrator with the error code 80180014.

    When we try to enroll the devices during the Out-of-the-box-experience as part of an Azure AD join, this is how it looks.

    We are presented below error:
    Something went wrong.
    This feature is not supported. Contact your system administrator with the error code 80180014.

    We have blocked the enrollment of personally owned devices. Keep in mind when you set this up, you have blocked the option to access corporate data when using Windows Information Protection like I described in my previous blog.

    Azure AD Conditional Access Data Loss Prevention EMS Microsoft 365 Security Windows10
    Share. Facebook Twitter LinkedIn Email WhatsApp
    Peter Klapwijk
    • Website
    • X (Twitter)
    • LinkedIn

    Peter is a Security (Intune) MVP since 2020 and is working as Modern Workplace Engineer at Wortell in The Netherlands. He has more than 15 years of experience in IT, with a strong focus on Microsoft technologies like Microsoft Intune, Windows, and (low-code) automation.

    Related Posts

    Configure Microsoft Defender SmartScreen to block potentially unwanted apps with Microsoft Intune

    February 27, 2020

    Enable passwordless authentication to Windows 10 with Yubico security keys

    November 6, 2019

    Set default Start Menu with Microsoft Intune

    June 5, 2019
    View 2 Comments

    2 Comments

    1. Freddie on May 27, 2020 19:49

      Very good work, pointed me in the right direction. Thanks a lot

      Reply
    2. Tijs Bouwmans on September 8, 2020 01:49

      We need exactly this, but keep the option for users to Azure AD join a device during either during OOBE or from settings.

      Reply
    Leave A Reply Cancel Reply

    Peter Klapwijk

    Hi! Welcome to my blog post.
    I hope you enjoy reading my articles.

    Hit the About Me button to get in contact with me or leave a comment.

    Awards
    Sponsor
    Latest Posts

    Update Windows Defender during Windows Autopilot enrollments

    May 16, 2025

    Hide the “Turn on an ad privacy feature” pop-up in Chrome with Microsoft Intune

    April 19, 2025

    How to set Google as default search provider with Microsoft Intune

    April 18, 2025

    Using Windows Autopilot device preparation with Windows 365 Frontline shared cloud PCs

    April 13, 2025
    follow me
    • Twitter 4.8K
    • LinkedIn 6.1K
    • YouTube
    • Bluesky 1.5K
    Tags
    Administrative Templates Android Automation Autopilot Azure Azure AD Browser Conditional Access Edge EMS Exchange Online Feitian FIDO2 Flow Google Chrome Graph Graph API Identity Management Intune Intune Monitoring iOS KIOSK Logic Apps macOS MEM MEMMonitoring Microsoft 365 Microsoft Edge Microsoft Endpoint Manager Modern Workplace Office 365 OneDrive for Business Outlook Passwordless PowerApps Power Automate Security SharePoint Online Teams Windows Windows 10 Windows10 Windows 11 Windows Autopilot Windows Update
    Copy right

    This information is provided “AS IS” with no warranties, confers no rights and is not supported by the authors, or In The Cloud 24-7.

     

    Copyright © 2025 by In The Cloud 24-7/ Peter Klapwijk. All rights reserved, No part of the information on this web site may be reproduced or posted in any form or by any means without the prior written permission of the publisher.

    Shorthand; Don’t pass off my work as yours, it’s not nice.

    Recent Comments
    • Adam on Get notified on expiring Azure App Registration client secrets
    • Peter Klapwijk on Update Windows Defender during Windows Autopilot enrollments
    • Rob van de Ven on Add a certificate to the Trusted Publishers with Intune without reporting errors
    • Carl on Update Windows Defender during Windows Autopilot enrollments
    • Peter Klapwijk on The next step in a passwordless Windows experience
    most popular

    Application installation issues; Download pending

    October 1, 2024

    Restrict which users can logon into a Windows 10 device with Microsoft Intune

    April 11, 2020

    How to change the Windows 11 language with Intune

    November 11, 2022

    Update Microsoft Edge during Windows Autopilot enrollments

    July 9, 2024
    Peter Klapwijk – In The Cloud 24-7
    X (Twitter) LinkedIn YouTube RSS Bluesky
    © 2025 ThemeSphere. Designed by ThemeSphere.

    Type above and press Enter to search. Press Esc to cancel.

    Manage Cookie Consent
    To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.
    Functional Always active
    The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
    Preferences
    The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
    Statistics
    The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
    Marketing
    The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
    Manage options Manage services Manage {vendor_count} vendors Read more about these purposes
    View preferences
    {title} {title} {title}