<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>article How To: Configure Qlik Sense Enterprise SaaS to use Azure AD as an IdP. Now with Groups! in Official Support Articles</title>
    <link>https://community.qlik.com/t5/Official-Support-Articles/How-To-Configure-Qlik-Sense-Enterprise-SaaS-to-use-Azure-AD-as/ta-p/1704442</link>
    <description>&lt;P&gt;This article provides step-by-step instructions for implementing Azure AD as an identify provider for Qlik Cloud. We cover configuring an App registration in Azure AD and configuring group support using MS Graph permissions.&lt;/P&gt;
&lt;P&gt;It guides the reader through adding the necessary application configuration in Azure AD and Qlik Sense Enterprise SaaS identity provider configuration so that Qlik Sense Enterprise SaaS users may log into a tenant using their Azure AD credentials.&lt;/P&gt;
&lt;P&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Content:&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;LI-TOC indent="15" liststyle="none" maxheadinglevel="4"&gt;&lt;/LI-TOC&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H2&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Prerequisites&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H2&gt;
&lt;UL class="lia-list-style-type-circle"&gt;
&lt;LI&gt;An Microsoft Azure account&lt;/LI&gt;
&lt;LI&gt;A Microsoft Azure Active Directory instance&lt;/LI&gt;
&lt;LI&gt;A Qlik Sense Enterprise SaaS tenant&lt;/LI&gt;
&lt;LI&gt;The BYOIDP feature in your Qlik license is set to &lt;STRONG&gt;YES&lt;/STRONG&gt;. Contact customer support to find out if you are entitled to bring your own identity provider to your tenant.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H2&gt;&lt;STRONG&gt;&lt;FONT color="#339966"&gt;Helpful vocabulary&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/H2&gt;
&lt;P&gt;Throughout this tutorial, some words will be used interchangeably.&lt;/P&gt;
&lt;UL class="lia-list-style-type-circle"&gt;
&lt;LI&gt;Qlik Sense Enterprise SaaS: Qlik Sense hosted in Qlik’s public cloud&lt;/LI&gt;
&lt;LI&gt;Microsoft Azure Active Directory: Azure AD&lt;/LI&gt;
&lt;LI&gt;Tenant: Qlik Sense Enterprise SaaS tenant or instance&lt;/LI&gt;
&lt;LI&gt;Instance: Microsoft Azure AD&lt;/LI&gt;
&lt;LI&gt;OIDC: Open Id Connect&lt;/LI&gt;
&lt;LI&gt;IdP: Identity Provider&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H2&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Considerations when using Azure AD with Qlik Sense Enterprise SaaS&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H2&gt;
&lt;UL class="lia-list-style-type-circle"&gt;
&lt;LI&gt;Qlik Sense Enterprise SaaS allows for customers to bring their own identity provider to provide authentication to the tenant using the Open ID Connect (OIDC) specification (&lt;A href="https://openid.net/connect/" target="_blank" rel="noopener"&gt;https://openid.net/connect/&lt;/A&gt;)&lt;/LI&gt;
&lt;LI&gt;Given that OIDC is a specification and not a standard, vendors (e.g. Microsoft) may implement the capability in ways that are outside of the core specification. In this case, Microsoft Azure AD OIDC configurations do not send standard OIDC claims like email_verified. Using the Azure AD configuration in Qlik Sense Enterprise SaaS includes an advanced option to set email_verified to true for all users that log into the tenant.&lt;/LI&gt;
&lt;LI&gt;The Azure AD configuration in Qlik Sense Enterprise SaaS includes special logic for contacting Microsoft Graph API to obtain friendly group names. Whether those groups originate from an on-premises instance of Active Directory and sync to Azure AD through Azure AD Connect or from creation within Azure AD, the friendly group name will be returned from the Graph API and added to Qlik Sense Enterprise SaaS.
&lt;P&gt; &lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;H2&gt;&lt;STRONG&gt;&lt;FONT color="#339966"&gt;Configure Azure AD&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/H2&gt;
&lt;H3&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Create the app registration&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;OL&gt;
&lt;LI&gt;Log into &lt;STRONG&gt;Microsoft Azure&lt;/STRONG&gt; by going to &lt;A href="https://portal.azure.com" target="_blank" rel="noopener"&gt;https://portal.azure.com&lt;/A&gt;.&lt;/LI&gt;
&lt;LI&gt;Click on the &lt;STRONG&gt;Azure Active Directory&lt;/STRONG&gt; icon in the browser Or search for "Azure Active Directory" in the search bar on the top. The overview page for the active directory will appear.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Azure Active Directory Overview.png" style="width: 999px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/109389i30099C7CEA6E153D/image-size/large?v=v2&amp;amp;px=999" role="button" title="Azure Active Directory Overview.png" alt="Azure Active Directory Overview.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;
&lt;LI&gt;Click the &lt;STRONG&gt;App registrations&lt;/STRONG&gt; item in the menu to the left.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="App Registration.png" style="width: 488px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/109390i26BFC051FB23B1E8/image-size/large?v=v2&amp;amp;px=999" role="button" title="App Registration.png" alt="App Registration.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;
&lt;LI&gt;Click the &lt;STRONG&gt;New registration&lt;/STRONG&gt; button at the top of the detail window. The application registration page appears.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="New Registration.png" style="width: 999px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/109391i3702D57C8B5963B2/image-size/large?v=v2&amp;amp;px=999" role="button" title="New Registration.png" alt="New Registration.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;
&lt;LI&gt;Add a name in the &lt;STRONG&gt;Name&lt;/STRONG&gt; section to identify the application. In this example, the name of the hostname of the tenant is entered along with the word OIDC.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="New Name for OIDC.png" style="width: 999px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/109392iB6962271A2744EBD/image-size/large?v=v2&amp;amp;px=999" role="button" title="New Name for OIDC.png" alt="New Name for OIDC.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="agree to platform policies.png" style="width: 764px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/109393iBAFD6D87530BDDE7/image-size/large?v=v2&amp;amp;px=999" role="button" title="agree to platform policies.png" alt="agree to platform policies.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;
&lt;LI&gt;The next section contains radio buttons for selecting the Supported account types. In this example, the default – Accounts in this organizational directory only – is selected.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Supported account types.png" style="width: 995px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/109545iEA88C9C22C552CC8/image-size/large?v=v2&amp;amp;px=999" role="button" title="Supported account types.png" alt="Supported account types.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;
&lt;LI&gt;The last section is for entering the redirect URI. From the dropdown list on the left select “web” and then enter the callback URL from the tenant. Enter the URI https://&amp;lt;tenant hostname&amp;gt;/login/callback.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Redirect URI.png" style="width: 999px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/109546i34B00BD73D75B1CA/image-size/large?v=v2&amp;amp;px=999" role="button" title="Redirect URI.png" alt="Redirect URI.png" /&gt;&lt;/span&gt;&lt;BR /&gt;
&lt;BLOCKQUOTE class="quote"&gt;The tenant hostname required in this context is the original hostname provided to the Qlik Enterprise SaaS tenant.&lt;/BLOCKQUOTE&gt;
&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="tenant hostname.png" style="width: 999px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/109547iABB86307E5877593/image-size/large?v=v2&amp;amp;px=999" role="button" title="tenant hostname.png" alt="tenant hostname.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;Using the Alias hostname will cause the IdP handshake to fail.&lt;/LI&gt;
&lt;LI&gt;Complete the registration by clicking the Register button at the bottom of the page.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Agree to Microsoft Policy.png" style="width: 763px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/109683i514EA42B004BABF6/image-size/large?v=v2&amp;amp;px=999" role="button" title="Agree to Microsoft Policy.png" alt="Agree to Microsoft Policy.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;
&lt;LI&gt;Click on the Authentication menu item on the left side of the screen.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Authentication.png" style="width: 328px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/109684iFC2A7BFC9F0C3E76/image-size/large?v=v2&amp;amp;px=999" role="button" title="Authentication.png" alt="Authentication.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;
&lt;LI&gt;On the middle of the page, the reference to the callback URI appears. There is no additional configuration required on this page.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Redirect URIs callback.png" style="width: 999px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/109685i69C260AA692AE9BA/image-size/large?v=v2&amp;amp;px=999" role="button" title="Redirect URIs callback.png" alt="Redirect URIs callback.png" /&gt;&lt;/span&gt;&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Create the client secret&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;OL&gt;
&lt;LI&gt;Click on the Certificates and secrets menu item on the left side of the screen.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Certificiates and Secrets.png" style="width: 336px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/109687i370BFAD84A7A504A/image-size/large?v=v2&amp;amp;px=999" role="button" title="Certificiates and Secrets.png" alt="Certificiates and Secrets.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;
&lt;LI&gt;In the center of the Certificates and secrets page, there is a section labeled Client secrets with a button labeled New client secret. Click the button.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="New Client Secret.png" style="width: 999px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/109688i69D664D9AAA8919A/image-size/large?v=v2&amp;amp;px=999" role="button" title="New Client Secret.png" alt="New Client Secret.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;
&lt;LI&gt;In the dialog that appears, enter a description for the client secret and select an expiration time. Click the Add button after entering the information.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Adding Client Secret.png" style="width: 401px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/109689i9EFF3BE343D2975D/image-size/large?v=v2&amp;amp;px=999" role="button" title="Adding Client Secret.png" alt="Adding Client Secret.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;
&lt;LI&gt;Once a client secret is added, it will appear in the Client secrets section of the page. &lt;BR /&gt;
&lt;BLOCKQUOTE class="quote"&gt;Copy the "value of the client secret" and paste it somewhere safe.&lt;/BLOCKQUOTE&gt;
After saving the configuration the value will become hidden and unavailable.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="List of Client Secrets.png" style="width: 999px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/109690i7DA3E955D9AC0EDA/image-size/large?v=v2&amp;amp;px=999" role="button" title="List of Client Secrets.png" alt="List of Client Secrets.png" /&gt;&lt;/span&gt;&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Add claims to the token configuration&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;OL&gt;
&lt;LI&gt;Click on the Token configuration menu item on the left side of the screen.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Token Configuration.png" style="width: 335px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/109691i8E5025B8784D841D/image-size/large?v=v2&amp;amp;px=999" role="button" title="Token Configuration.png" alt="Token Configuration.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;
&lt;LI&gt;The Optional claims window appears with two buttons. One for adding optional claims, and another for adding group claims. Click on the Add optional claim button.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Optional Claims.png" style="width: 999px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/109692i06F4A4E81743A139/image-size/large?v=v2&amp;amp;px=999" role="button" title="Optional Claims.png" alt="Optional Claims.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;
&lt;LI&gt;For optional claims, select the ID token type, and then select the claims to include in the token that will be sent to the Qlik Sense Enterprise SaaS tenant. In this example, ctry, email, tenant_ctry, upn, and verified_primary_email are checked. None of these optional claims are required for the tenant identity provider to work properly, however, they are used later on in this tutorial.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Adding Optional Claim Settings.png" style="width: 840px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/109693i32183184F88FC35A/image-size/large?v=v2&amp;amp;px=999" role="button" title="Adding Optional Claim Settings.png" alt="Adding Optional Claim Settings.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;
&lt;LI&gt;Some optional claims may require adding OpenId Connect scopes from Microsoft Graph to the application configuration. Click the check mark to enable and click Add.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Turn on the Microsoft Graph email and profile permission.png" style="width: 999px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/109694i533194E0098BA5B5/image-size/large?v=v2&amp;amp;px=999" role="button" title="Turn on the Microsoft Graph email and profile permission.png" alt="Turn on the Microsoft Graph email and profile permission.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;
&lt;LI&gt;&amp;nbsp;The claims will appear in the window.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Optional Claims overview.png" style="width: 999px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/109695iF6F7A7CE10A86241/image-size/large?v=v2&amp;amp;px=999" role="button" title="Optional Claims overview.png" alt="Optional Claims overview.png" /&gt;&lt;/span&gt;&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Add group claim&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;OL&gt;
&lt;LI&gt;Click on the API permissions menu item on the left side of the screen.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="API permissions.png" style="width: 328px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/109696iA547D585FB3B757C/image-size/large?v=v2&amp;amp;px=999" role="button" title="API permissions.png" alt="API permissions.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;
&lt;LI&gt;Observe the configured permissions set during adding optional claims.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Configured Permissions.png" style="width: 999px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/109697i325F5E31B90C35BC/image-size/large?v=v2&amp;amp;px=999" role="button" title="Configured Permissions.png" alt="Configured Permissions.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;
&lt;LI&gt;Click the Add a permission button and select the Microsoft Graph option in the Request API permissions box that appears. Click on the Microsoft Graph banner.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Request API permissions.png" style="width: 999px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/109698i2E5FBB32D06AE005/image-size/large?v=v2&amp;amp;px=999" role="button" title="Request API permissions.png" alt="Request API permissions.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;
&lt;LI&gt;Click on Delegated permissions. The Select permission search and the OpenId permissions list appears.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Request API permissions Microsoft Graph.png" style="width: 999px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/109699iF82EFD3A042A82FF/image-size/large?v=v2&amp;amp;px=999" role="button" title="Request API permissions Microsoft Graph.png" alt="Request API permissions Microsoft Graph.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Request API permissions Users.png" style="width: 833px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/109803i2D4D5B8E80E97F45/image-size/large?v=v2&amp;amp;px=999" role="button" title="Request API permissions Users.png" alt="Request API permissions Users.png" /&gt;&lt;/span&gt;&lt;BR /&gt;
&lt;BLOCKQUOTE class="quote"&gt;In the &lt;STRONG&gt;OpenID permissions&amp;nbsp;&lt;/STRONG&gt;section, check &lt;STRONG&gt;email&lt;/STRONG&gt;, &lt;STRONG&gt;openid&lt;/STRONG&gt;,&amp;nbsp;and &lt;STRONG&gt;profile&lt;/STRONG&gt;. In the&amp;nbsp;&lt;STRONG&gt;Users&amp;nbsp;&lt;/STRONG&gt;section, check &lt;STRONG&gt;user.read&lt;/STRONG&gt;.&lt;/BLOCKQUOTE&gt;
&lt;/LI&gt;
&lt;LI&gt;In the Select permissions search, enter the word &lt;EM&gt;group&lt;/EM&gt;. Expand the GroupMember option and select&amp;nbsp;&lt;STRONG&gt;GroupMember.Read.All&lt;/STRONG&gt;. This will grant users logging into Qlik Sense Enteprise SaaS through Azure AD to read the group memberships they are assigned.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Select Permissions.png" style="width: 999px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/109700i58777C8730DE6424/image-size/large?v=v2&amp;amp;px=999" role="button" title="Select Permissions.png" alt="Select Permissions.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;
&lt;LI&gt;After making the selection, click the Add permissions button.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="confirm by adding permissions.png" style="width: 499px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/109701i87B1D0C59FCCAEBE/image-size/large?v=v2&amp;amp;px=999" role="button" title="confirm by adding permissions.png" alt="confirm by adding permissions.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;
&lt;LI&gt;The added permissions will appear in the list. However, the GroupMember.Read.All permission requires admin consent to work with the app registration. Click the Grant button and accept the message that appears.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Configured Permissions overview.png" style="width: 999px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/109702i8C3A72194AE679AA/image-size/large?v=v2&amp;amp;px=999" role="button" title="Configured Permissions overview.png" alt="Configured Permissions overview.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="grant consent.png" style="width: 772px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/109703iA6DBD5E893A9E926/image-size/large?v=v2&amp;amp;px=999" role="button" title="grant consent.png" alt="grant consent.png" /&gt;&lt;/span&gt;&lt;/LI&gt;
&lt;/OL&gt;
&lt;BLOCKQUOTE class="quote"&gt;Failing to grant consent to &lt;STRONG&gt;GroupMember.Read.All&lt;/STRONG&gt; may result in errors authenticating to Qlik using Azure AD. Make sure to complete this step before moving on.&lt;/BLOCKQUOTE&gt;
&lt;H3&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Collect Azure AD configuration information&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;OL&gt;
&lt;LI&gt;Click on the Overview menu item to return to the main App registration screen for the new app. Copy the Application (client) ID unique identifier. This value is needed for the tenant’s idp configuration.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Application ID unique identifier.png" style="width: 999px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/109705i16389160E588CAE1/image-size/large?v=v2&amp;amp;px=999" role="button" title="Application ID unique identifier.png" alt="Application ID unique identifier.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;
&lt;LI&gt;Click on the Endpoints button in the horizontal menu of the overview.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="OIDC Endpoints.png" style="width: 983px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/109706i7CFBC8E66041FF42/image-size/large?v=v2&amp;amp;px=999" role="button" title="OIDC Endpoints.png" alt="OIDC Endpoints.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;
&lt;LI&gt;Copy the OpenID Connect metadata document endpoint URI. This is needed for the tenant’s IdP configuration.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Copy OpenID Connect medatdata.png" style="width: 999px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/109707iCA7681F46B698855/image-size/large?v=v2&amp;amp;px=999" role="button" title="Copy OpenID Connect medatdata.png" alt="Copy OpenID Connect medatdata.png" /&gt;&lt;/span&gt;&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H2&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Configure Qlik Sense Enterprise SaaS IdP&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H2&gt;
&lt;OL&gt;
&lt;LI&gt;With the configuration complete and required information in hand, open the tenant’s management console and click on the Identity provider menu item on the left side of the screen.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Qlik Cloud Identity Provider.png" style="width: 496px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/109709i1826A9493116A388/image-size/large?v=v2&amp;amp;px=999" role="button" title="Qlik Cloud Identity Provider.png" alt="Qlik Cloud Identity Provider.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;
&lt;LI&gt;Click the Create new button on the upper right side of the main panel.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Create New.png" style="width: 221px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/109710iDE8BF850220F9AF0/image-size/large?v=v2&amp;amp;px=999" role="button" title="Create New.png" alt="Create New.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;
&lt;LI&gt;Select &lt;STRONG&gt;OIDC&amp;nbsp;&lt;/STRONG&gt;from the Type drop-down menu item, and select&amp;nbsp; &lt;STRONG&gt;Microsoft Entra ID (Azure AD)&lt;/STRONG&gt;&amp;nbsp;from the Provider drop-down menu item.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="OIDC Azure AD.png" style="width: 352px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/165922i87B5A029AFBBF1E2/image-size/large?v=v2&amp;amp;px=999" role="button" title="OIDC Azure AD.png" alt="OIDC Azure AD.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;
&lt;LI&gt;Scroll down to the Application credentials section of the configuration panel and enter the following information:
&lt;OL class="lia-list-style-type-lower-alpha"&gt;
&lt;LI&gt;ADFS discovery URL: This is the endpoint URI copied from Azure AD.&lt;/LI&gt;
&lt;LI&gt;Client ID: This is the application (client) id copied from Azure AD.&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;Client secret: This is the value copy and pasted to a safe location from the Certificates &amp;amp; secrets section from Azure AD.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;The Realm is an optional value used if you want to enter what is commonly referred to as the Active Directory domain name.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Application Credentials.png" style="width: 861px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/109712i80C235372E1CE04E/image-size/large?v=v2&amp;amp;px=999" role="button" title="Application Credentials.png" alt="Application Credentials.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;
&lt;/OL&gt;
&lt;/LI&gt;
&lt;LI&gt;Scroll down to the Claims mapping section of the configuration panel. There are five textboxes to confirm or alter.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Claims mapping.png" style="width: 844px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/109713iF5CB62EB3C1B18F8/image-size/large?v=v2&amp;amp;px=999" role="button" title="Claims mapping.png" alt="Claims mapping.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;
&lt;OL class="lia-list-style-type-lower-alpha"&gt;
&lt;LI&gt;The sub field is the subject of the token sent from Azure AD. This is normally a unique identifier and will represent the UserID of the user in the tenant. In this example, the value “sub” is left and appid is removed. To use a different claim from the token, replace the default value with the name of the desired attribute value.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="sub.png" style="width: 836px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/109714iA9FF3756D7A82BD3/image-size/large?v=v2&amp;amp;px=999" role="button" title="sub.png" alt="sub.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;
&lt;LI&gt;The name field is the “friendly” name of the user to be displayed in the tenant. For Azure AD, change the attribute name from the default value to “name”.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="name.png" style="width: 837px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/109715i25089525D7AA7DF6/image-size/large?v=v2&amp;amp;px=999" role="button" title="name.png" alt="name.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;
&lt;LI&gt;In this example, the groups, email, and client_id attributes are configured properly, therefore, they do not need to be altered.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="groups.png" style="width: 834px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/109716i7909D31B00C37A05/image-size/large?v=v2&amp;amp;px=999" role="button" title="groups.png" alt="groups.png" /&gt;&lt;/span&gt;&lt;BR /&gt;
&lt;BLOCKQUOTE class="quote"&gt;In this example, I had to change the email claim to upn to obtain the user's email address from Azure AD. Your results may vary.&lt;/BLOCKQUOTE&gt;
&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="email.png" style="width: 871px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/109717i14594619EDA12ADD/image-size/large?v=v2&amp;amp;px=999" role="button" title="email.png" alt="email.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;
&lt;/OL&gt;
&lt;/LI&gt;
&lt;LI&gt;Scroll down to the Advanced options and expand the menu. Slide the Email verified override option&amp;nbsp;&lt;STRONG&gt;ON &lt;/STRONG&gt;to ensure Azure AD validation works. Scope does not have to be supplied.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="advanced options email verification override.png" style="width: 880px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/109718i62BC478A189BE0DD/image-size/large?v=v2&amp;amp;px=999" role="button" title="advanced options email verification override.png" alt="advanced options email verification override.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;
&lt;LI&gt;The Post logout redirect URI is not required for Azure AD because upon logging out the user will be sent to the Azure log out page.&lt;/LI&gt;
&lt;LI&gt;Click the Save button at the bottom of the configuration to save the configuration. A message will appear confirming intent to create the identity provider. Click the Save button again to start the validation process.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="configure update of identity provider.png" style="width: 999px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/109719i5E6397F0403900FC/image-size/large?v=v2&amp;amp;px=999" role="button" title="configure update of identity provider.png" alt="configure update of identity provider.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;
&lt;LI&gt;The validation procedure begins by redirecting the person configuring the IdP to the login page for the IdP.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Sign in to Microsoft Account.png" style="width: 752px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/109720i858C5E15B8DE4633/image-size/large?v=v2&amp;amp;px=999" role="button" title="Sign in to Microsoft Account.png" alt="Sign in to Microsoft Account.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;
&lt;LI&gt;After successful authentication, Azure AD will confirm that permission should be granted for this user to the tenant. Click the Accept button.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Accept requested permissions.png" style="width: 756px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/109722iBAC243ED6F784448/image-size/large?v=v2&amp;amp;px=999" role="button" title="Accept requested permissions.png" alt="Accept requested permissions.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;
&lt;LI&gt;If the validation fails, the validation procedure will return a window like the following.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Authentication Failed Error.png" style="width: 821px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/109723iC63BC575A526812B/image-size/large?v=v2&amp;amp;px=999" role="button" title="Authentication Failed Error.png" alt="Authentication Failed Error.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;
&lt;LI&gt;If the validation succeeds, the validation procedure will return a mapped claims window. If the validation states it cannot map the user's email address, it is most likely because the email_verified switch has not been turned on. Go ahead and confirm, move through the remaining steps, and update the configuration as per the previous step. Re-run the validation to map the email.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Login Successful.png" style="width: 589px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/109724i5516C3B2A0CAE9E8/image-size/large?v=v2&amp;amp;px=999" role="button" title="Login Successful.png" alt="Login Successful.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;
&lt;LI&gt;After confirming the information is correct, the account used to validate the IdP may be elevated to a TenantAdmin role. It is strongly recommended to do make sure the box is checked before clicking continue.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Promote User to Tenant Admin.png" style="width: 730px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/109725iAE729BCD57F28F04/image-size/large?v=v2&amp;amp;px=999" role="button" title="Promote User to Tenant Admin.png" alt="Promote User to Tenant Admin.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;
&lt;LI&gt;The next to last screen in the configuration will ask to activate the IdP. By activating the Azure AD IdP in the tenant, any other identity providers configured in the tenant will be disabled.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Activate the idP.png" style="width: 945px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/109726iC1CDEB78DDAC3F18/image-size/large?v=v2&amp;amp;px=999" role="button" title="Activate the idP.png" alt="Activate the idP.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;
&lt;LI&gt;Success.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Success Message.png" style="width: 795px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/109727i7A087837CB31930E/image-size/large?v=v2&amp;amp;px=999" role="button" title="Success Message.png" alt="Success Message.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;
&lt;LI&gt;Please log out of the tenant and re-authenticate using the new identity provider connection. Once logged in, change the url in the address bar to point to &lt;FONT face="courier new,courier"&gt;https://&amp;lt;tenanthostname&amp;gt;/api/v1/diagnose-claims&lt;/FONT&gt;. This will return the JSON of the claims information Azure AD sent to the tenant. Here is a slightly redacted example.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="diagnose claims.png" style="width: 999px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/109728iF0E2C8A19EF1CCF0/image-size/large?v=v2&amp;amp;px=999" role="button" title="diagnose claims.png" alt="diagnose claims.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;
&lt;LI&gt;Verify groups resolve properly by creating a space and adding members. You should see friendly group names to choose from.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Create a new space.png" style="width: 996px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/109729iEE27CD54C6CEC148/image-size/large?v=v2&amp;amp;px=999" role="button" title="Create a new space.png" alt="Create a new space.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Space Members.png" style="width: 417px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/109730i1A6266FAA7EEC017/image-size/large?v=v2&amp;amp;px=999" role="button" title="Space Members.png" alt="Space Members.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Add members.png" style="width: 259px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/109733i6FE1D7AEE70BA493/image-size/large?v=v2&amp;amp;px=999" role="button" title="Add members.png" alt="Add members.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Add members to content-admins.png" style="width: 993px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/109735i6E6FA7C725C0B837/image-size/large?v=v2&amp;amp;px=999" role="button" title="Add members to content-admins.png" alt="Add members to content-admins.png" /&gt;&lt;/span&gt;&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt; &lt;/P&gt;
&lt;H2&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Recap&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H2&gt;
&lt;P&gt;While not hard, configuring Azure AD to work with Qlik Sense Enterprise SaaS is not trivial. Most of the legwork to make this authentication scheme work is on the Azure side. However, it's important to note that without making some small tweaks to the IdP configuration in Qlik Sense you may receive a failure or two during the validation process.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H2&gt;&lt;STRONG&gt;&lt;FONT color="#339966"&gt;Addendum&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/H2&gt;
&lt;P&gt;For many of you, adding Azure AD means you potentially have a bunch of clean up you need to do to remove legacy groups. Unfortunately, there is no way to do this in the UI but there is an API endpoint for deleting groups. See&amp;nbsp;&lt;A href="https://community.qlik.com/t5/Support-Knowledge-Base/Deleting-guid-group-values-from-Qlik-Cloud-Services/ta-p/1774867" target="_self"&gt;Deleting guid group values from Qlik Sense Enterprise SaaS&lt;/A&gt;&amp;nbsp;for a guide on how to delete groups from a Qlik Sense Enterprise SaaS tenant.&lt;/P&gt;
&lt;H2&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Related Content (VIDEO)&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H2&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&lt;A href="https://www.youtube.com/watch?v=d3WpPGTmmC0" target="_self"&gt;Qlik Cloud: Configure Azure Active Directory as an IdP&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 10 Apr 2026 10:29:25 GMT</pubDate>
    <dc:creator>Jeffrey_Goldberg</dc:creator>
    <dc:date>2026-04-10T10:29:25Z</dc:date>
    <item>
      <title>Re: How To: Configure Qlik Sense Enterprise SaaS to use Azure AD as an IdP</title>
      <link>https://community.qlik.com/t5/Official-Support-Articles/How-To-Configure-Qlik-Sense-Enterprise-SaaS-to-use-Azure-AD-as/tac-p/1709363#M1442</link>
      <description>&lt;P&gt;Hi Jeff,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I hope all is well. Awesome guide, we set this up a couple of months ago and got it to work. We intended to sync multicloud to a onprem solution (where we have SAML auth). In general, works fine, but when we use the QSEoCS at x.eu.qlikcloud.com there is no identity mapping from the on-prem solution. So users exists with the same credentials (sub) as DOMAIN\user@domain.com on both on-prem and cloud, but when deploying apps to a cloud environment the apps don't get any ownership, which is a bit annoying. When setting up the idp on QSEoCS it actually says &lt;EM&gt;"The email claim is not valid. The identity mapping feature will not work for the users in the tentant"&lt;/EM&gt; which would explain the behavior. Any idea of a workaround to actually hard-core/manually add the claim "email_verified" as true? It appears to be the only thing missing.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Erik&lt;/P&gt;</description>
      <pubDate>Tue, 09 Jun 2020 12:03:14 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Official-Support-Articles/How-To-Configure-Qlik-Sense-Enterprise-SaaS-to-use-Azure-AD-as/tac-p/1709363#M1442</guid>
      <dc:creator>ergustafsson</dc:creator>
      <dc:date>2020-06-09T12:03:14Z</dc:date>
    </item>
    <item>
      <title>Re: How To: Configure Qlik Sense Enterprise SaaS to use Azure AD as an IdP</title>
      <link>https://community.qlik.com/t5/Official-Support-Articles/How-To-Configure-Qlik-Sense-Enterprise-SaaS-to-use-Azure-AD-as/tac-p/1718356#M1443</link>
      <description>&lt;P&gt;Very similar issue as&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/35422"&gt;@ergustafsson&lt;/a&gt;&amp;nbsp;...&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are working through changing a customer from one Azure AD tenant to another. Changing IdP in QSEoCS is apparently fairly seamless as long as the email addresses of the new &amp;amp; old users match. However with this config, the email addresses, whilst passed in the authentication process, don't show in the user list and this seems to be a problem.&amp;nbsp; I assume this must be to do with the missing email_verified field. Is there any way to manually add a mapping for this like you would with SAML or similar? I find it weird there's no box to map a claim to that field - although perhaps since it's part of the underlying OpenID Connect spec it's meant to be included by default.&lt;/P&gt;</description>
      <pubDate>Fri, 12 Jun 2020 15:53:00 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Official-Support-Articles/How-To-Configure-Qlik-Sense-Enterprise-SaaS-to-use-Azure-AD-as/tac-p/1718356#M1443</guid>
      <dc:creator>AlexOmetis</dc:creator>
      <dc:date>2020-06-12T15:53:00Z</dc:date>
    </item>
    <item>
      <title>Re: How To: Configure Qlik Sense Enterprise SaaS to use Azure AD as an IdP</title>
      <link>https://community.qlik.com/t5/Official-Support-Articles/How-To-Configure-Qlik-Sense-Enterprise-SaaS-to-use-Azure-AD-as/tac-p/1723220#M1444</link>
      <description>&lt;P&gt;Does anyone was able to retrieve users email and picture from the azure AD?&lt;/P&gt;</description>
      <pubDate>Mon, 29 Jun 2020 18:57:12 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Official-Support-Articles/How-To-Configure-Qlik-Sense-Enterprise-SaaS-to-use-Azure-AD-as/tac-p/1723220#M1444</guid>
      <dc:creator>sfbi</dc:creator>
      <dc:date>2020-06-29T18:57:12Z</dc:date>
    </item>
    <item>
      <title>Re: How To: Configure Qlik Sense Enterprise SaaS to use Azure AD as an IdP</title>
      <link>https://community.qlik.com/t5/Official-Support-Articles/How-To-Configure-Qlik-Sense-Enterprise-SaaS-to-use-Azure-AD-as/tac-p/1723442#M1445</link>
      <description>&lt;P&gt;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/115854"&gt;@sfbi&lt;/a&gt;&amp;nbsp;No - I wasn't able to get email address or picture. The email address appears to be to do with the lack of email_verified field coming from Azure. I haven't managed to figure out if it's possible to send a static value as part of the auth process for this, so email addresses can show in QSE SaaS... As for pictures, I haven't looked but assume it's a similar issue with it not being passed by Azure.&lt;/P&gt;</description>
      <pubDate>Tue, 30 Jun 2020 10:05:16 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Official-Support-Articles/How-To-Configure-Qlik-Sense-Enterprise-SaaS-to-use-Azure-AD-as/tac-p/1723442#M1445</guid>
      <dc:creator>AlexOmetis</dc:creator>
      <dc:date>2020-06-30T10:05:16Z</dc:date>
    </item>
    <item>
      <title>Re: How To: Configure Qlik Sense Enterprise SaaS to use Azure AD as an IdP</title>
      <link>https://community.qlik.com/t5/Official-Support-Articles/How-To-Configure-Qlik-Sense-Enterprise-SaaS-to-use-Azure-AD-as/tac-p/1723453#M1446</link>
      <description>&lt;P&gt;I wasn't either. I added a support case but nothing they could do, so I added an idea. Feel free to upvote it:&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.qlik.com/t5/Ideas/Modify-claims-in-Identity-Mapping/idi-p/1723386" target="_blank"&gt;https://community.qlik.com/t5/Ideas/Modify-claims-in-Identity-Mapping/idi-p/1723386&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you have any input on the actual "idea", please let me know.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;</description>
      <pubDate>Tue, 30 Jun 2020 10:49:29 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Official-Support-Articles/How-To-Configure-Qlik-Sense-Enterprise-SaaS-to-use-Azure-AD-as/tac-p/1723453#M1446</guid>
      <dc:creator>ergustafsson</dc:creator>
      <dc:date>2020-06-30T10:49:29Z</dc:date>
    </item>
    <item>
      <title>Re: How To: Configure Qlik Sense Enterprise SaaS to use Azure AD as an IdP</title>
      <link>https://community.qlik.com/t5/Official-Support-Articles/How-To-Configure-Qlik-Sense-Enterprise-SaaS-to-use-Azure-AD-as/tac-p/1723466#M1447</link>
      <description>&lt;P&gt;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/35422"&gt;@ergustafsson&lt;/a&gt;&amp;nbsp; and&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/18018"&gt;@AlexOmetis&lt;/a&gt;&amp;nbsp; I've been trying to figure out if there is a way in Azure to add an email_verified claim. And I found one! But... it adds a prefix in the claim name "extn." Here's the document:&amp;nbsp;&lt;A href="https://docs.microsoft.com/en-us/powershell/azure/active-directory/using-extension-attributes-sample?view=azureadps-2.0" target="_blank"&gt;https://docs.microsoft.com/en-us/powershell/azure/active-directory/using-extension-attributes-sample?view=azureadps-2.0&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/35422"&gt;@ergustafsson&lt;/a&gt;&amp;nbsp; I commented on your idea and it's a good place to put it.&lt;/P&gt;&lt;P&gt;This issue along with groups is aggravating for me as much as I know it is for you. We are researching what the art of the possible is without a large amount of customization per IdP.&lt;/P&gt;&lt;P&gt;I hate to say stay tuned so I'll say "keep a sharp eye". If you see something that may work let me know!&lt;/P&gt;</description>
      <pubDate>Tue, 30 Jun 2020 11:14:29 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Official-Support-Articles/How-To-Configure-Qlik-Sense-Enterprise-SaaS-to-use-Azure-AD-as/tac-p/1723466#M1447</guid>
      <dc:creator>Jeffrey_Goldberg</dc:creator>
      <dc:date>2020-06-30T11:14:29Z</dc:date>
    </item>
    <item>
      <title>Re: How To: Configure Qlik Sense Enterprise SaaS to use Azure AD as an IdP</title>
      <link>https://community.qlik.com/t5/Official-Support-Articles/How-To-Configure-Qlik-Sense-Enterprise-SaaS-to-use-Azure-AD-as/tac-p/1723527#M1448</link>
      <description>&lt;P&gt;Email:&lt;BR /&gt;I was able to get the email with "email" claim. Still, IDP config won't create user with the current email. All auth user emails are set as null.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="sfbi_1-1593518751218.png" style="width: 400px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/36569i526F4BA00620D5CE/image-size/medium?v=v2&amp;amp;px=400" role="button" title="sfbi_1-1593518751218.png" alt="sfbi_1-1593518751218.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Profile Picture:&lt;BR /&gt;It look likes azure ad doesn't support profile picture as claim.&lt;BR /&gt;&lt;A href="https://stackoverflow.com/questions/39936877/microsoft-openid-login-flow-picture-access" target="_blank"&gt;https://stackoverflow.com/questions/39936877/microsoft-openid-login-flow-picture-access&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;picturePhoto is supported using MicrosoftGraph only:&lt;BR /&gt;&lt;A href="https://graph.microsoft.com/v1.0/me/photo/$value" target="_blank"&gt;https://graph.microsoft.com/v1.0/me/photo/$value&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;have no idea on how to get it working on IDP...&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 30 Jun 2020 13:29:19 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Official-Support-Articles/How-To-Configure-Qlik-Sense-Enterprise-SaaS-to-use-Azure-AD-as/tac-p/1723527#M1448</guid>
      <dc:creator>sfbi</dc:creator>
      <dc:date>2020-06-30T13:29:19Z</dc:date>
    </item>
    <item>
      <title>Re: How To: Configure Qlik Sense Enterprise SaaS to use Azure AD as an IdP</title>
      <link>https://community.qlik.com/t5/Official-Support-Articles/How-To-Configure-Qlik-Sense-Enterprise-SaaS-to-use-Azure-AD-as/tac-p/1723643#M1449</link>
      <description>&lt;P&gt;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/45015"&gt;@Jeffrey_Goldberg&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;I suggest you to add at the top of this How To, the advise about SESSION ACCESS... it is an important step that is described on help, but some people (like myself) might ignore prior to implement the IdP.&lt;/P&gt;</description>
      <pubDate>Tue, 30 Jun 2020 17:05:22 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Official-Support-Articles/How-To-Configure-Qlik-Sense-Enterprise-SaaS-to-use-Azure-AD-as/tac-p/1723643#M1449</guid>
      <dc:creator>sfbi</dc:creator>
      <dc:date>2020-06-30T17:05:22Z</dc:date>
    </item>
    <item>
      <title>Re: How To: Configure Qlik Sense Enterprise SaaS to use Azure AD as an IdP</title>
      <link>https://community.qlik.com/t5/Official-Support-Articles/How-To-Configure-Qlik-Sense-Enterprise-SaaS-to-use-Azure-AD-as/tac-p/1723706#M1450</link>
      <description>&lt;P&gt;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/115854"&gt;@sfbi&lt;/a&gt;&amp;nbsp;if I play it back you mean changing the SUB to something a bit more friendly than the actual subject. Like Email or something else.&amp;nbsp; Good feedback to add to the considerations section.&lt;/P&gt;&lt;P&gt;thanks,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;jg&lt;/P&gt;</description>
      <pubDate>Tue, 30 Jun 2020 20:53:24 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Official-Support-Articles/How-To-Configure-Qlik-Sense-Enterprise-SaaS-to-use-Azure-AD-as/tac-p/1723706#M1450</guid>
      <dc:creator>Jeffrey_Goldberg</dc:creator>
      <dc:date>2020-06-30T20:53:24Z</dc:date>
    </item>
    <item>
      <title>Re: How To: Configure Qlik Sense Enterprise SaaS to use Azure AD as an IdP</title>
      <link>https://community.qlik.com/t5/Official-Support-Articles/How-To-Configure-Qlik-Sense-Enterprise-SaaS-to-use-Azure-AD-as/tac-p/1724084#M1451</link>
      <description>&lt;P&gt;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/45015"&gt;@Jeffrey_Goldberg&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;Here is an example on Users MC page. The first line is the new user create from the Azure AD IdP (no email) and the second line is the "old" QlikID user created before implement the IdP...&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="sfbi_0-1593607460933.png" style="width: 735px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/36709iE1FBB82A336B2D84/image-dimensions/735x68?v=v2" width="735" height="68" role="button" title="sfbi_0-1593607460933.png" alt="sfbi_0-1593607460933.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;It's not affecting the usability, but when you need to add a lot of users, it might get a lit bit complicated to manage it by users Names instead users Emails.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;What I don't understand is why I'm getting the email from the email claim, and its not been set as user email on the MC User page.&lt;BR /&gt;&lt;BR /&gt;Also, I added the folowing API permissions at Azure AD.&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="sfbi_0-1593609395158.png" style="width: 646px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/36760iFB5F7BB4A780353A/image-dimensions/646x138?v=v2" width="646" height="138" role="button" title="sfbi_0-1593609395158.png" alt="sfbi_0-1593609395158.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;</description>
      <pubDate>Wed, 01 Jul 2020 13:18:17 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Official-Support-Articles/How-To-Configure-Qlik-Sense-Enterprise-SaaS-to-use-Azure-AD-as/tac-p/1724084#M1451</guid>
      <dc:creator>sfbi</dc:creator>
      <dc:date>2020-07-01T13:18:17Z</dc:date>
    </item>
    <item>
      <title>Re: How To: Configure Qlik Sense Enterprise SaaS to use Azure AD as an IdP</title>
      <link>https://community.qlik.com/t5/Official-Support-Articles/How-To-Configure-Qlik-Sense-Enterprise-SaaS-to-use-Azure-AD-as/tac-p/1724103#M1452</link>
      <description>&lt;P&gt;The email isn't mapping because Azure AD does not send a specific claim named "email_verified". This is a claim Qlik Sense SaaS is expecting and not getting, therefore, no mapping your email to the user account created.&lt;/P&gt;&lt;P&gt;We are working on adding the ability to specify the claim that represents "email_verified" so the mapping will work properly. No timeframes of course but I do have an appreciation for the urgency to implement this in SaaS.&lt;/P&gt;&lt;P&gt;The other thing is from your screenshot is you are showing permissions, but not the optional claims you are sending. You need to send the email as an optional claim AND the "primary_verified_email" claim as an optional claim. Once we have the customization in platform (described above) you will be able to tell Qlik Sense IdP config to look for "primary_email_verified" as the claim for email_verified.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;jg&lt;/P&gt;</description>
      <pubDate>Wed, 01 Jul 2020 13:40:01 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Official-Support-Articles/How-To-Configure-Qlik-Sense-Enterprise-SaaS-to-use-Azure-AD-as/tac-p/1724103#M1452</guid>
      <dc:creator>Jeffrey_Goldberg</dc:creator>
      <dc:date>2020-07-01T13:40:01Z</dc:date>
    </item>
    <item>
      <title>Re: How To: Configure Qlik Sense Enterprise SaaS to use Azure AD as an IdP</title>
      <link>https://community.qlik.com/t5/Official-Support-Articles/How-To-Configure-Qlik-Sense-Enterprise-SaaS-to-use-Azure-AD-as/tac-p/1724111#M1453</link>
      <description>&lt;P&gt;ok now I got it... all claims are set correctly and I'm geeting it at the diagnose&lt;/P&gt;&lt;PRE&gt;"verified_primary_email":["henrique@....."]&lt;/PRE&gt;&lt;P&gt;as&amp;nbsp;&lt;A href="https://sfbi.us.qlikcloud.com/api/v1/diagnose-claims" target="_blank"&gt;&amp;nbsp;...api/v1/diagnose-claims&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 01 Jul 2020 13:49:30 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Official-Support-Articles/How-To-Configure-Qlik-Sense-Enterprise-SaaS-to-use-Azure-AD-as/tac-p/1724111#M1453</guid>
      <dc:creator>sfbi</dc:creator>
      <dc:date>2020-07-01T13:49:30Z</dc:date>
    </item>
    <item>
      <title>Re: How To: Configure Qlik Sense Enterprise SaaS to use Azure AD as an IdP</title>
      <link>https://community.qlik.com/t5/Official-Support-Articles/How-To-Configure-Qlik-Sense-Enterprise-SaaS-to-use-Azure-AD-as/tac-p/1725476#M1454</link>
      <description>&lt;P&gt;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/45015"&gt;@Jeffrey_Goldberg&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;is it on the roadmap to allow anonymous user on SaaS?&lt;/P&gt;</description>
      <pubDate>Mon, 06 Jul 2020 17:43:03 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Official-Support-Articles/How-To-Configure-Qlik-Sense-Enterprise-SaaS-to-use-Azure-AD-as/tac-p/1725476#M1454</guid>
      <dc:creator>sfbi</dc:creator>
      <dc:date>2020-07-06T17:43:03Z</dc:date>
    </item>
    <item>
      <title>Re: How To: Configure Qlik Sense Enterprise SaaS to use Azure AD as an IdP</title>
      <link>https://community.qlik.com/t5/Official-Support-Articles/How-To-Configure-Qlik-Sense-Enterprise-SaaS-to-use-Azure-AD-as/tac-p/1737949#M1455</link>
      <description>&lt;P&gt;Did anybody figure out a workaround or a solution?&lt;/P&gt;</description>
      <pubDate>Sun, 23 Aug 2020 09:48:29 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Official-Support-Articles/How-To-Configure-Qlik-Sense-Enterprise-SaaS-to-use-Azure-AD-as/tac-p/1737949#M1455</guid>
      <dc:creator>ergustafsson</dc:creator>
      <dc:date>2020-08-23T09:48:29Z</dc:date>
    </item>
    <item>
      <title>Re: How To: Configure Qlik Sense Enterprise SaaS to use Azure AD as an IdP</title>
      <link>https://community.qlik.com/t5/Official-Support-Articles/How-To-Configure-Qlik-Sense-Enterprise-SaaS-to-use-Azure-AD-as/tac-p/1742585#M1456</link>
      <description>&lt;P&gt;Updated configuration now enables to set the email_verified on the IDP config.&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="email_verified" style="width: 366px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/40324i56846A875D97BCC4/image-dimensions/366x72?v=v2" width="366" height="72" role="button" title="emailv.JPG" alt="email_verified" /&gt;&lt;span class="lia-inline-image-caption" onclick="event.preventDefault();"&gt;email_verified&lt;/span&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;PS:&lt;BR /&gt;for current users to get the appropriate email address at the users table (MC) and be able to be notified by emails, you'll need to exclude the current users and ask them to login again as a new user after updating the IDP config. After you'll need to allocate again spaces authorizations.&amp;nbsp; (at least that was the only way for me).&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="user tab MC" style="width: 1077px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/40325i3CFC2D7E48CB3592/image-dimensions/1077x90?v=v2" width="1077" height="90" role="button" title="useremail.JPG" alt="user tab MC" /&gt;&lt;span class="lia-inline-image-caption" onclick="event.preventDefault();"&gt;user tab MC&lt;/span&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;That's not a good idea if you need to exclude app owners as you'll need to reset app ownership on the MC (App Tab) and republish all apps on manage spaces as you can't change it's ownership within the MC. So if you do, do it carefully.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Users IDP Entity remains the same after the new login, so you won't need to update any table used on section access (if its the case).&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 09 Sep 2020 21:45:56 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Official-Support-Articles/How-To-Configure-Qlik-Sense-Enterprise-SaaS-to-use-Azure-AD-as/tac-p/1742585#M1456</guid>
      <dc:creator>sfbi</dc:creator>
      <dc:date>2020-09-09T21:45:56Z</dc:date>
    </item>
    <item>
      <title>Re: How To: Configure Qlik Sense Enterprise SaaS to use Azure AD as an IdP</title>
      <link>https://community.qlik.com/t5/Official-Support-Articles/How-To-Configure-Qlik-Sense-Enterprise-SaaS-to-use-Azure-AD-as/tac-p/1743054#M1457</link>
      <description>&lt;P&gt;Nice!&lt;/P&gt;&lt;P&gt;I noticed that too. But using "verified_primary_email" still doesn't make Azure AD provide proper identity mapping. I belive "email_verified": true needs to be in the claims. I can verify at&amp;nbsp;&lt;A href="https://xx.eu.qlikcloud.com/api/v1/diagnose-claims" target="_blank"&gt;https://xx.eu.qlikcloud.com/api/v1/diagnose-claims &lt;/A&gt;that there no such attribute. Any ideas?&lt;/P&gt;</description>
      <pubDate>Fri, 11 Sep 2020 09:10:07 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Official-Support-Articles/How-To-Configure-Qlik-Sense-Enterprise-SaaS-to-use-Azure-AD-as/tac-p/1743054#M1457</guid>
      <dc:creator>ergustafsson</dc:creator>
      <dc:date>2020-09-11T09:10:07Z</dc:date>
    </item>
    <item>
      <title>Re: How To: Configure Qlik Sense Enterprise SaaS to use Azure AD as an IdP</title>
      <link>https://community.qlik.com/t5/Official-Support-Articles/How-To-Configure-Qlik-Sense-Enterprise-SaaS-to-use-Azure-AD-as/tac-p/1743175#M1458</link>
      <description>&lt;P&gt;your are not getting the email_verified claim on the diagnose?&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;I'm getting both email and primary and&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;"email_verified":["henrique@xxxxxxx"]&lt;/PRE&gt;&lt;PRE&gt;"verified_primary_email":["henrique@xxxxxxxx"]&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 11 Sep 2020 13:21:16 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Official-Support-Articles/How-To-Configure-Qlik-Sense-Enterprise-SaaS-to-use-Azure-AD-as/tac-p/1743175#M1458</guid>
      <dc:creator>sfbi</dc:creator>
      <dc:date>2020-09-11T13:21:16Z</dc:date>
    </item>
    <item>
      <title>Re: How To: Configure Qlik Sense Enterprise SaaS to use Azure AD as an IdP</title>
      <link>https://community.qlik.com/t5/Official-Support-Articles/How-To-Configure-Qlik-Sense-Enterprise-SaaS-to-use-Azure-AD-as/tac-p/1743193#M1459</link>
      <description>&lt;P&gt;I do. And that works to add, but it doesn't help with the identity mapping for Azure AD. Tried to sync an app and it loses the owner.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 11 Sep 2020 13:51:02 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Official-Support-Articles/How-To-Configure-Qlik-Sense-Enterprise-SaaS-to-use-Azure-AD-as/tac-p/1743193#M1459</guid>
      <dc:creator>ergustafsson</dc:creator>
      <dc:date>2020-09-11T13:51:02Z</dc:date>
    </item>
    <item>
      <title>Re: How To: Configure Qlik Sense Enterprise SaaS to use Azure AD as an IdP</title>
      <link>https://community.qlik.com/t5/Official-Support-Articles/How-To-Configure-Qlik-Sense-Enterprise-SaaS-to-use-Azure-AD-as/tac-p/1743243#M1460</link>
      <description>&lt;P&gt;understood... same here, no idea on how to manage it too...&lt;/P&gt;</description>
      <pubDate>Fri, 11 Sep 2020 18:16:17 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Official-Support-Articles/How-To-Configure-Qlik-Sense-Enterprise-SaaS-to-use-Azure-AD-as/tac-p/1743243#M1460</guid>
      <dc:creator>sfbi</dc:creator>
      <dc:date>2020-09-11T18:16:17Z</dc:date>
    </item>
    <item>
      <title>Re: How To: Configure Qlik Sense Enterprise SaaS to use Azure AD as an IdP</title>
      <link>https://community.qlik.com/t5/Official-Support-Articles/How-To-Configure-Qlik-Sense-Enterprise-SaaS-to-use-Azure-AD-as/tac-p/1743282#M1461</link>
      <description>&lt;P&gt;Hi folks, allow me to chime in here. You've stumbled upon the first phase of addressing the email_verified problem some identity providers have with Qlik Sense SaaS configuration. Qlik requires email_verified as a claim in the OIDC handshake because we want to make sure the email is indeed unique and the email intended to be supplied with the credential sent from the IdP.&lt;/P&gt;&lt;P&gt;The email_verified input has been added to the configuration to help you point to a custom claim that you would create in your IdP that would map the custom claim to the email_verified attribute required by Qlik's OIDC implementations.&lt;/P&gt;&lt;P&gt;With respect to Azure AD, just because we've added the input doesn't mean Azure AD will now surface this attribute. In fact, Azure AD will not because Azure AD does not have this claim to send, full stop.&amp;nbsp;&lt;/P&gt;&lt;P&gt;What you can do is add what is called an extension attribute to your app registration (link:&amp;nbsp;&lt;A href="https://docs.microsoft.com/en-us/powershell/azure/active-directory/using-extension-attributes-sample?view=azureadps-2.0" target="_blank"&gt;https://docs.microsoft.com/en-us/powershell/azure/active-directory/using-extension-attributes-sample?view=azureadps-2.0&lt;/A&gt;) and then send this as an optional claim using the optional claims configuration in the app registration. You would then map this custom claim to the email_verified input in the Qlik Sense SaaS IdP config for Azure AD.&lt;/P&gt;&lt;P&gt;screenshot of azure ad:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Jeffrey_Goldberg_0-1599853285382.png" style="width: 400px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/40416i38A68459DF7B2160/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Jeffrey_Goldberg_0-1599853285382.png" alt="Jeffrey_Goldberg_0-1599853285382.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;While doable, it's an inelegant solution.&lt;/P&gt;&lt;P&gt;I feel this is a bit clunky, so I've asked our R&amp;amp;D team to investigate implementing a toggle that will set email_verified to true when using AzureAD.&lt;/P&gt;&lt;P&gt;This toggle, in addition to adding group resolution from AzureAD object ids from an Azure AD menu item in the IdP config will be available in the not too distant future.&lt;/P&gt;&lt;P&gt;When it becomes available, I will update the document.&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Jeff G&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 11 Sep 2020 19:52:13 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Official-Support-Articles/How-To-Configure-Qlik-Sense-Enterprise-SaaS-to-use-Azure-AD-as/tac-p/1743282#M1461</guid>
      <dc:creator>Jeffrey_Goldberg</dc:creator>
      <dc:date>2020-09-11T19:52:13Z</dc:date>
    </item>
  </channel>
</rss>

