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»Android»Setup Samsung Knox Mobile Enrollment to enroll Android devices in Microsoft Intune
    Android

    Setup Samsung Knox Mobile Enrollment to enroll Android devices in Microsoft Intune

    Peter KlapwijkBy Peter KlapwijkJune 25, 2019Updated:May 12, 202136 Mins Read

    After writing a few blog articles last April about Android (Enterprise) management with Microsoft Intune, it`s now time to take a look at Samsung Knox Mobile Enrollment (KME). Samsung KME provides a solution which is familiar to Android Zero Touch Deployment, but (off course) fully focused on Samsung Devices;
    The admin or the reseller registers the Android devices in the Samsung KME portal. The end-user switches on the (new) Android device, connects it to the internet and the Android device downloads the configuration profile from KME. In combination with Microsoft Intune, the device is enrolled in Intune after the end-user authenticates with the Azure AD credentials and receives the assigned configuration policies and applications and is ready to start using the device without the admin touching the device.

    In this blog article I will describe how to setup Samsung Knox Mobile Enrollment to enroll the devices in Microsoft Intune as (Android Enterprise) Corporate-owned, Fully managed user device. I will not describe in further detail how to link your Managed Google Play account with Intune, you can read those steps in a previous article. In this example I enroll the device in Intune as Corporate-owned, Fully managed user device, the steps involved to set this up in Intune can be found here.

    Setup Samsung Knox Mobile Enrollment

    I assume you have already created a Samsung account, if not go to this portal and create one.

    Sign-in to the Samsung Knox portal. There are a lot of options on the dashboard, but for now we are only interested in Knox Mobile Enrollment. If you haven`t already applied for KME, click Apply now.

    1. Check I have read and agree…
    2. Click Submit application

    Now you need to wait until the registration for KME is approved. My approval was done within the hour, but sometimes it could take a few days and you even might be contacted by phone to discuss why you need KME.
    When registration is finished, go back to the Samsung Knox portal and under Knox Mobile Enrollmend click Launch Console.
    Because it`s the first time we open the KME console, we need to take some steps to setup KME.

    1. Click Start

    1. Select Server URI not required for MDM
    2. Click Continue

    On this page we setup our first MDM Profile. With this profile we make sure our devices are enrolled in Intune as a Corporate-owned, Fully managed user device.

    1. Give the enrollment profile a Name
    2. Give the profile a Description (optional)
    3. Click Add support contact

    1. Enter your Company Name
    2. Enter your Company Address (optional)
    3. Enter Support Phone Number
    4. Enter Support Email Address
    5. Click Save

    1. Back at the profile page click Add MDM Applications

    Here we need to enter the URL to the APK which needs to be downloaded during enrollment. For enrollment in Intune as Android Enterprise device that URL is https://aka.ms/intune_kme_deviceowner.

    1. Enter https://aka.ms/intune_kme_deviceowner
    2. Click Save

    After providing the APK URL we get some more options.

    1. Check Enable this app as Google Device Owner
    2. Choose Microsoft Intune as Supported MDM
    3. Make you decision to Leave all system apps enabled (or remove them)

    The last part of setting up our enrollment profile is to fill in the custom JSON data on the right site of the page. By filling in this configuration, we make sure our devices are directed to the correct enrollment profile in Intune. When you don`t fill in this information, your users need to scan the QR code from the corresponding Intune enrollment profile during enrollment.

    The format for Intune, Android Enterprise is:
    {“com.google.android.apps.work.clouddpc.EXTRA_ENROLLMENT_TOKEN”: “Enter Intune enrollment token string”}
    Replace Enter Intune enrollment token string with the token you find in Intune above to QR Code (located under Device Enrollment, Android enrollment, Corporate-owned, Fully managed user devices).
    When you use the token from a Corporate-owned, dedicated device, the device is enrolled as dedicated device.

    When finished click Save profile.

    On the next page you can fill in information about your reseller. This allows you reseller to register devices at Samsung Knox which you purchased and assign it a default enrollment profile. I highly advise to give your reseller these right to register your devices, so you as an admin don`t have to register the devices yourself. You can setup a reseller at a later moment.

    1. Click Skip

    1. Click Next

    You are presented the Knox Mobile Enrollment dashboard. It`s now time to ask your reseller to register your purchased Samsung devices to your account. Or you can register the devices yourself as I will show you next.

    Manually register devices with the Knox Deployment app

    When you have existing devices which cannot be registered by a reseller to your Samsung account, you have the option to register the devices manually using the Samsung Knox Deployment app.
    To get started with this process, download the app from the Google Play Store on a Android device and sign-in.
    Sorry for the Dutch printscreens.

    1. Select the enrollment Profile we just created in the KME portal
    2. Click Deployment mode

    We have three deployment modes; Bluetooth, NFC and Wi-Fi Direct. In my example I used NFC as I found that the easiest way. Select the Deployment mode of choice.

    Click Start deployment

    If you have chosen to use NFC, you only have to ‘ bump’ both devices to get the profile deployed to the device which needs to be registered. Acknowledge the enrollment on the existing Samsung device.
    When the deployment is finished, switch back to the KME portal. On the Devices tab, you see the device is registered and the profile is assigned.

    End-user experience

    Now that everything is setup in the Samsung Knox portal and maybe you have also created a Android Enterprise configuration profile in Intune, it`s time to have a look at the end-user experience.
    After connecting the device to the internet, the device will check for updates.

    It will show a message the device will be setup. You have to accept the Terms and conditions and click Next.

    The device setup is started.

    The device is downloading the Google Play Store.

    Click Accept & Continue to accept the terms of Chrome.

    Now it`s time to authenticate with your Azure AD username and password.

    Setting up device

    Click Please click here to continue

    By default the Microsoft Authenticator and Microsoft Intune apps are installed when the device is enrolled as Corporate-owned, Fully managed user device.

    The last step is applying policies.

    When the last step is finished, the user is sign-in to the device and enrollment is finished!

    Android EMS Intune Knox MEM Microsoft 365 Microsoft Endpoint Manager Samsung Samsung knox
    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

    Windows Autopilot lifecycle automation with Logic Apps

    March 8, 2021

    Microsoft Defender ATP for Mobile

    June 23, 2020

    How to start with Android Enterprise Corporate owned dedicated devices in Microsoft Intune

    April 24, 2019
    View 3 Comments

    3 Comments

    1. Jeremy Bradshaw on January 13, 2021 19:21

      Hi Peter,

      Thanks for this article. I am unable to get a trial for my lab started without a proper company name/URL and contact info, so I’m hoping to check with you on something. Eventually I’ll be doing a trial of KME with a client, but until then this is a mystery.

      Samsung’s guide mentions that the KDA allows us to forego needing to factory reset the devices (https://docs.samsungknox.com/admin/knox-mobile-enrollment/about-kda.htm – 2nd paragraph in the “About” section). However, Microsoft Intune’s documentation says a factory reset is a must (https://docs.microsoft.com/en-us/mem/intune/enrollment/android-samsung-knox-mobile-enroll#frequently-asked-questions – 3rd FAQ). I realize with Android Enterprise device owner enrollment types (Fully Managed, Dedicated, and COPE), the usual answer is that a Factory Reset is required, since it is from the OOBE that we enter afw#setup to get started with enrollment.

      So I feel like Samsung’s statement in the link above is purely referring to Android Device Administrator deployments, which we know are now legacy and Android Enterprise is the proper way to go. Just trying to find out if indeed the KDA can allow devices to enroll into Android Enterprise Fully Managed, without factory resetting. Any idea?

      Thanks in advance.

      Reply
      • Peter Klapwijk on January 19, 2021 21:56

        Hi Jeremy,

        The Android Enterprise configuration types you`re referring to, indeed require a factory reset for existing devices. So does Samsung KME for these types of managed devices. I indeed think the documentation of Samsung refers to Android Device admin.

        Reply
    2. Ilan on October 24, 2023 09:32

      Hello,

      I have a small question about Android Knox Enrollment, checking your two enrollment guides online I see that in the old one you use MS url for the APK : “https://aka.ms/intune_kme_deviceowner”” which is also what is on MS guides, and on this guide using “https://play.google.com/managed/downloadManagingApp?identifier=setup”” e.g. :

      How to easily enroll Android Corporate with Work profile devices with Microsoft Intune and Samsung Knox ME | Peter Klapwijk – In The Cloud 24-7 (inthecloud247.com)
      Setup Samsung Knox Mobile Enrollment to enroll Android devices in Microsoft Intune | Peter Klapwijk – In The Cloud 24-7 (inthecloud247.com)
      ​
      We are enrolling to Intune MDM, using the Company Owned Work Profile,
      I have 2 questions:

      What is difference between these 2 URL for APK, are there any benefits or options one has the other not?
      I am asking this also in regard to the step-in enrollment when the device is installing Work Apps, I know Intune and Authenticator are installed by default but where do I add more apps “Additional Apps” as I have not seen this option in our Knox,

      This might be a Microsoft Question but maybe you know, When Microsoft Authenticator gets installed during enrollment it also automatically configures an Authentication Profile do you from where is that Profile is configured from?
      ​

      Thanks

      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

    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

    Using Visual Studio with Microsoft Endpoint Privilege Management, some notes

    April 8, 2025
    follow me
    • Twitter 4.8K
    • LinkedIn 6.1K
    • YouTube
    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
    • Peter Klapwijk on Using Windows Autopilot device preparation with Windows 365 Frontline shared cloud PCs
    • John M on Using Windows Autopilot device preparation with Windows 365 Frontline shared cloud PCs
    • Christoffer Jakobsen on Connect to Azure file shares with Microsoft Entra Private Access
    • Ludo on How to block Bluetooth file transfer with Microsoft Intune
    • RCharles on Automatically configure the time zone (during Autopilot enrollment)
    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
    © 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}