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»Configure Azure AD SSO for the Samsung Knox portal
    Android

    Configure Azure AD SSO for the Samsung Knox portal

    Peter KlapwijkBy Peter KlapwijkApril 7, 2021Updated:May 12, 202123 Mins Read

    If you are using Samsung Knox Mobile Enrollment to enroll Samsung Android devices into Microsoft Intune, you probably sign in to the Samsung Knox portal with a Samsung account. And probably colleagues also have a Samsung account for which they have to remember a username and password, which needs to be administered by you and the other admins. But it’s also possible to connect Samsung Knox to Azure Active Directory (Azure AD) to get a single sign-on (SSO) experience when using the Azure AD account to sign in to Knox.

    In this article, I show how we can configure Samsung Knox and Azure AD to provide our admins (and ourselves) a better sign-on experience.

    If you enable Azure AD as a sign-in method, you cannot use Samsung Account to sign into Knox services.

    At the moment of writing not all Knox services are supported for Azure AD SSO. Keep an eye on the official documentation for which services are supported.

    Configure Azure AD

    To connect Samsung Knox to Azure AD, we need to create an Enterprise Application in Azure. First we check our Knox tenant if Azure AD SSO is supported and look up the Reply URL which we need later in our Azure Enterprise Application.

    • Sign-in to the Samsung Knox portal
    • Click on the avatar on the top right corner to access your account settings

    If the tenant supports Azure AD SSO, on the left you’ll find a tab Active Directory SSO settings. Op the Azure AD SSO settings tab and copy the Reply URL for later use.

    • Sign in to the Azure portal
    • Open the service Enterprise Applications
    • Click New Application
    • Search for Samsung Knox
    • Select Samsung Knox and Business Services
    • Click create
    • Open the tab Single sign-on
    • Click SAML
    • Click Edit next to Basic SAML Configuration
    • Enter the Reply URL which we found in the Knox portal
    • As Sign on URL enter https://www2.samsungknox.com/en/sso/login/ad
    • Click Save
    • On the Single sign-on tab, under SAML Signing Certificate copy the App Federation Metadata URL and save it for one of the next steps
    • Browse to the Users and Groups tab
    • Click Add user/group
    • Click None selected
    • Select the users (or at least your own account) to who you want to provide access to the Knox portal
    • Click Assign
    • Open the Samsung Knox portal
    • Paste the App federation metadata URL
    • Click Connect to AD SSO
    • Authenticate with your Azure AD account
    • When authentication is successful, the connection is verified
    • A warning is shown, read this carefully!
    • Click Continue

    The AAD SSO Connection is set up! Your Knox admins should now be able to sign-in to Knox with their Azure AD account.

    Some notes

    Unfortunately, automatic user provisioning isn’t supported. This means, you still need to create (sub) admins in the Knox portal and the invited sub-admins must click the Sign up button in the invitation email to complete their registration. And the admins need to be added to the users of the Enterprise Application.

    Although Samsung Knox is shown under all apps of the user in Office, the user needs to provide his UPN. So actually we don’t get a real single sign-on experience. But we don’t have to remember an extra password, so it’s still a step forward.

    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

    Set default Start Menu with Microsoft Intune

    June 5, 2019
    View 2 Comments

    2 Comments

    1. Marc on April 28, 2021 17:03

      I have no idea how you got this working (or where you found that Sign on URL?) The current documentation says it should be https://accounts.samsung.com but that doesn’t work. Your URL does seem to work but I cannot connect the instances because I get https://central.samsungknox.com/?errorCode=AZURE_AD_LOGIN_EXCEPTION which redirects to my account not having permission. Are you logging into the Azure side with the same account on the Samsung side? It’s very confusing as to the account setup on the Samsung side.

      Reply
    2. Marc on April 28, 2021 17:46

      I figured it out finally. When you initiate the “Connect to AD SSO” step you need to be logging into Azure with the same account as you’re working in Samsung with (for example if your super admin is bob@company.com then when you get the log into Azure prompt it needs to be bob@company.com. My issue was I was trying to log in with a different user.

      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}