Set up Single Sign-on for Microsoft Defender for IoT Sensor Console
In brief
The Defender for IoT SSO article now identifies Microsoft Graph User.Read as the required permission and states that an administrator must grant tenant-wide consent. Wording, headings, metadata, and related-content formatting were also updated.
What Defender admins need to know
When configuring SSO, ensure the application has User.Read and obtain tenant-wide admin consent so users can sign in without individual approval prompts.
Summaries are generated from the documentation change itself.
Documentation change
The comparison below shows only the changed extract. Use the full-page view for complete context.
Set up single sign-on for the sensor console
In this article, you learnThis article shows how to set up single sign-on (SSO) for the Defender for IoT sensor console usingconsole. SSO uses Microsoft Entra ID. With SSO,ID so your organization's users can simply sign into the sensor console, andin once. They don't need multiple loginseparate credentials across different sensors and sites.for each sensor or site.
Using Microsoft Entra ID simplifies the onboardingmakes it easier to add or remove users, reduces admin work, and offboarding processes, reduces administrative overhead, and ensures consistentkeeps access controls consistent across theyour organization.
Add outbound allow rules to your firewall, proxy server, and so on. You can access the list of required endpoints from the Sites and sensors page.
If you don't have existing Microsoft Entra ID user groups to use for SSO authorization, work with your organization's identity manager to create relevant user groups.
Verify that you have the following permissions:
- A Member user on Microsoft Entra ID.
- Admin, Contributor, or Security Admin permissions on the Defender for IoT subscription.
Ensure that each user has a First name, Last name, and User principal name.
If needed, set up Multifactor authentication (MFA).
- Under Name, type a name for your application.
- Under Supported account types, select Accounts in this organizational directory only (Microsoft only - single tenant).
- Under Redirect URI, add an IP or hostname for the first sensor on which you want to enable SSO. You continue to add URIs for the other sensors in the next step, Add your sensor URIs.
:::image type="content" source="media/set-up-sso/register-application.png" alt-text="Screenshot of registering an application on Microsoft Entra ID." lightbox="media/set-up-sso/register-application.png":::
- Select Register.
- Under Redirect URIs, the URI for the first sensor, added in Create application ID on Microsoft Entra ID, is displayed under Redirect URIs. To add the rest of the URIs:
Select Add URI to add another row, and type an IP or hostname.
Repeat this step for the rest of the connected sensors.
When Microsoft Entra ID adds the URIs successfully, a "Your redirect URI is eligible for the Authorization Code Flow with PKCE" message is displayed.
:::image type="content" source="media/set-up-sso/authentication.png" alt-text="Screenshot of setting up URIs for your application on the Microsoft Entra ID Authentication page." lightbox="media/set-up-sso/authentication.png":::
- Select Save.
Grant the application requiredAPI permissions
GrantYour registered application needs the required API permissions for your application:default Microsoft Graph User.Read permission to sign in users. An admin must grant tenant-wide consent so that all users can use SSO without individual approval prompts.
In your new application, select API permissions.
Next toAdd a permission, selectSelect Grant admin consent for <Directory name>.:::image type="content" source="media/set-up-sso/api-permissions.png" alt-text="Screenshot of setting up API permissions in Microsoft Entra ID." lightbox="media/set-up-sso/api-permissions.png":::
Test sign-in with SSO
To test signing in with SSO:
Open Defender for IoT on the Azure portal, and select SSO Sign-in.
:::image type="content" source="media/set-up-sso/sso-sign-in.png" alt-text="Screenshot of the sensor console login screen with SSO.":::
For the first sign in, in the Sign in page, type your personal credentials (your work email and password).
:::image type="content" source="media/set-up-sso/sso-first-sign-in-credentials.png" alt-text="Screenshot of the Sign in screen when signing in to Defender for IoT on the Azure portal via SSO.":::
The Defender for IoT Overview page is displayed.
Next stepsRelated content
For more information, see:
@@ -1,18 +1,18 @@ ----title: Set up single sign-on for Microsoft Defender for IoT sensor console+title: Set up Single Sign-on for Microsoft Defender for IoT Sensor Console description: Configure single sign-on (SSO) for the Microsoft Defender for IoT sensor console using Microsoft Entra ID in the Azure portal.-ms.date: 06/12/2026+ms.date: 07/03/2026 ms.topic: how-to ai-usage: ai-assisted-ms.custom: msecd-doc-authoring-1014+ms.custom: msecd-doc-authoring-1016 #customer intent: As a security operator, I want to set up SSO for my users so that they can log in to the sensor console easily to multiple applications. --- # Set up single sign-on for the sensor console -In this article, you learn how to set up single sign-on (SSO) for the Defender for IoT sensor console using Microsoft Entra ID. With SSO, your organization's users can simply sign into the sensor console, and don't need multiple login credentials across different sensors and sites. +This article shows how to set up single sign-on (SSO) for the Defender for IoT sensor console. SSO uses Microsoft Entra ID so your users can sign in once. They don't need separate credentials for each sensor or site. -Using Microsoft Entra ID simplifies the onboarding and offboarding processes, reduces administrative overhead, and ensures consistent access controls across the organization.+Microsoft Entra ID makes it easier to add or remove users, reduces admin work, and keeps access controls consistent across your organization. > [!NOTE] > Signing in via SSO is currently in PREVIEW. The [Azure Preview Supplemental Terms](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) include other legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.@@ -25,8 +25,8 @@ Before you begin: - Add outbound allow rules to your firewall, proxy server, and so on. You can access the list of required endpoints from the [Sites and sensors page](how-to-manage-sensors-on-the-cloud.md#endpoint). - If you don't have existing Microsoft Entra ID user groups to use for SSO authorization, work with your organization's identity manager to create relevant user groups. - Verify that you have the following permissions:- - A Member user on Microsoft Entra ID. - - Admin, Contributor, or Security Admin permissions on the Defender for IoT subscription.+ - A Member user on Microsoft Entra ID. + - Admin, Contributor, or Security Admin permissions on the Defender for IoT subscription. - Ensure that each user has a **First name**, **Last name**, and **User principal name**. - If needed, set up [Multifactor authentication (MFA)](/entra/identity/authentication/tutorial-enable-azure-mfa). @@ -44,10 +44,10 @@ To create an application ID in Microsoft Entra ID, perform the following steps: - Under **Name**, type a name for your application. - Under **Supported account types**, select **Accounts in this organizational directory only (Microsoft only - single tenant)**. - Under **Redirect URI**, add an IP or hostname for the first sensor on which you want to enable SSO. You continue to add URIs for the other sensors in the next step, [Add your sensor URIs](#add-your-sensor-uris).- + > [!NOTE] > Adding the URI at this stage is required for SSO to work. - + :::image type="content" source="media/set-up-sso/register-application.png" alt-text="Screenshot of registering an application on Microsoft Entra ID." lightbox="media/set-up-sso/register-application.png"::: 1. Select **Register**.@@ -61,7 +61,7 @@ Add the redirect URIs for each sensor to your registered application: 1. Under **Redirect URIs**, the URI for the first sensor, added in [Create application ID on Microsoft Entra ID](#create-application-id-on-microsoft-entra-id), is displayed under **Redirect URIs**. To add the rest of the URIs: 1. Select **Add URI** to add another row, and type an IP or hostname. 1. Repeat this step for the rest of the connected sensors. - + When Microsoft Entra ID adds the URIs successfully, a "Your redirect URI is eligible for the Authorization Code Flow with PKCE" message is displayed. :::image type="content" source="media/set-up-sso/authentication.png" alt-text="Screenshot of setting up URIs for your application on the Microsoft Entra ID Authentication page." lightbox="media/set-up-sso/authentication.png"::: @@ -69,12 +69,13 @@ Add the redirect URIs for each sensor to your registered application: 1. Select **Save**. <a name="grant-access-to-application"></a>-## Grant the application required permissions+<a name="grant-the-application-required-permissions"></a>+## Grant API permissions -Grant the required API permissions for your application:+Your registered application needs the default Microsoft Graph `User.Read` permission to sign in users. An admin must grant tenant-wide consent so that all users can use SSO without individual approval prompts. 1. In your new application, select **API permissions**.-1. Next to **Add a permission**, select **Grant admin consent for \<Directory name\>**.+1. Select **Grant admin consent for \<Directory name\>**. :::image type="content" source="media/set-up-sso/api-permissions.png" alt-text="Screenshot of setting up API permissions in Microsoft Entra ID." lightbox="media/set-up-sso/api-permissions.png"::: @@ -114,7 +115,7 @@ Create the SSO configuration in Defender for IoT to enable single sign-on for yo ## Test sign-in with SSO To test signing in with SSO:-+ 1. Open [Defender for IoT](https://portal.azure.com/#view/Microsoft_Azure_IoT_Defender/IoTDefenderDashboard/%7E/Getting_started) on the Azure portal, and select **SSO Sign-in**. :::image type="content" source="media/set-up-sso/sso-sign-in.png" alt-text="Screenshot of the sensor console login screen with SSO.":::@@ -122,12 +123,10 @@ To test signing in with SSO: 1. For the first sign in, in the **Sign in** page, type your personal credentials (your work email and password). :::image type="content" source="media/set-up-sso/sso-first-sign-in-credentials.png" alt-text="Screenshot of the Sign in screen when signing in to Defender for IoT on the Azure portal via SSO.":::- -The Defender for IoT **Overview** page is displayed. --## Next steps -For more information, see:+The Defender for IoT **Overview** page is displayed.++## Related content - [Azure user roles for OT and Enterprise IoT monitoring with Defender for IoT](roles-azure.md) - [Create and manage on-premises users for OT monitoring](how-to-create-and-manage-users.md) 