<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Namsoo Choi on Medium]]></title>
        <description><![CDATA[Stories by Namsoo Choi on Medium]]></description>
        <link>https://medium.com/@namsoochoi?source=rss-15a0a9072965------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*79mWPOjow_TKNx0UMk2Bfw.png</url>
            <title>Stories by Namsoo Choi on Medium</title>
            <link>https://medium.com/@namsoochoi?source=rss-15a0a9072965------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 20:10:48 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@namsoochoi/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[[SOLVED] Citrix Cloud sign in fails with AADSTS650052]]></title>
            <link>https://medium.com/@namsoochoi/solved-citrix-cloud-sign-in-fails-with-aadsts650052-6b77c775df0c?source=rss-15a0a9072965------2</link>
            <guid isPermaLink="false">https://medium.com/p/6b77c775df0c</guid>
            <category><![CDATA[identity-management]]></category>
            <category><![CDATA[entra-id]]></category>
            <category><![CDATA[identity]]></category>
            <category><![CDATA[citrix]]></category>
            <category><![CDATA[azure-ad]]></category>
            <dc:creator><![CDATA[Namsoo Choi]]></dc:creator>
            <pubDate>Fri, 16 Oct 2026 17:54:33 GMT</pubDate>
            <atom:updated>2026-10-16T17:54:33.240Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*FtObl8AxxfVbs9dBOJIuZA.png" /></figure><h3>Why I’m writing this</h3><p>Over the last two weeks I’ve seen multiple cases with the same symptom: users suddenly can’t sign in to Citrix Cloud through its Microsoft Entra enterprise application. Nothing changed in the customers’ tenants. The cause was a change on the Citrix side. Because it looks like an emerging pattern, I want to share the symptom, the cause, and the fix in one place.</p><h3>Symptom</h3><p>Users fail to sign in to the Citrix Cloud enterprise application. In the Entra sign in logs you see:</p><p><strong>Sign in error code:</strong> 650052</p><p><strong>Failure reason:</strong></p><blockquote><em>The app is trying to access a service ‘{appId}’({appName}) that your organization ‘{organization}’ lacks a service principal for. Contact your IT Admin to review the configuration of your service subscriptions or consent to the application in order to create the required service principal.</em></blockquote><h3>Cause</h3><p>AADSTS650052 means the client app is requesting a token for a resource (API) that has no service principal in your tenant. Entra can’t issue a token for a resource that doesn’t exist in the tenant, so sign in fails.</p><p>Citrix started requiring a new resource app, <strong>Citrix-Workspace-Resource</strong> (3a510bb1-e334-4298-831e-3eac97f8b26c). Tenants that set up Citrix before this change don’t have a service principal for it, so the token request fails with 650052.</p><p>The new app is documented by Citrix here:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZXx-JddjajGNFGT8Iuqatw.png" /></figure><p><a href="https://docs.citrix.com/en-us/citrix-virtual-apps-desktops/install-configure/session-authentication/entra-sso.html">Microsoft Entra single sign-on (Preview) | Citrix Virtual Apps and Desktops 7 2603</a></p><h3>Resolution</h3><p>You need an account with the <strong>Global Administrator</strong> or <strong>Application Administrator</strong> role.</p><h4>Step 1: Create the service principal for Citrix-Workspace-Resource</h4><p>Sign in as an admin and open the admin consent URL from the Citrix documentation:</p><blockquote><a href="https://login.microsoftonline.com/common/adminconsent?client_id=3a510bb1-e334-4298-831e-3eac97f8b26c">https://login.microsoftonline.com/common/adminconsent?client_id=3a510bb1-e334-4298-831e-3eac97f8b26c</a></blockquote><p>Accepting the consent creates the service principal (enterprise application) for Citrix-Workspace-Resource in your tenant.</p><p>To confirm, go to <strong>Entra admin center &gt; Enterprise applications</strong>, clear the application type filter, and search for the app ID 3a510bb1-e334-4298-831e-3eac97f8b26c.</p><p>If you prefer PowerShell, Microsoft Graph PowerShell can also create the service principal:</p><blockquote>Connect-MgGraph -Scopes “Application.ReadWrite.All”<br>New-MgServicePrincipal -AppId “3a510bb1-e334–4298–831e-3eac97f8b26c”</blockquote><h4>Step 2: Grant admin consent to your Citrix client app</h4><p>After Step 1, the 650052 error goes away, but users will likely hit a <strong>consent required</strong> error next. That’s expected: the resource now exists, but your Citrix client app has not been granted consent for the new permission yet.</p><p>Grant admin consent using either option:</p><p><strong>Option A: Entra admin center</strong><br> <strong>Enterprise applications &gt; (your Citrix app) &gt; Permissions &gt; Grant admin consent for {your org name}</strong></p><p><strong>Option B: Admin consent URL</strong> (as documented by Citrix)</p><blockquote><a href="https://login.microsoftonline.com/">https://login.microsoftonline.com/</a>&lt;EntraTenantID&gt;/adminconsent?client_id=&lt;clientAppID&gt;</blockquote><p>Replace &lt;EntraTenantID&gt; with your tenant ID and &lt;clientAppID&gt; with the application (client) ID of your Citrix client app.</p><p>After consent is granted, have users sign in again.</p><h3>Key takeaways</h3><ul><li><strong>650052 is about the resource, not the client.</strong> Look at the app ID inside the error message. That’s the service principal you’re missing.</li><li><strong>Fixing the service principal is only half the fix.</strong> Plan for the follow up consent step so users aren’t hit with a second error.</li><li><strong>Vendor side changes can break SSO without any tenant change.</strong> If several tenants start failing with the same app ID at the same time, check the vendor’s recent documentation first.</li></ul><h3>Reference</h3><ul><li><a href="https://docs.citrix.com/en-us/citrix-virtual-apps-desktops/install-configure/session-authentication/entra-sso.html">Microsoft Entra single sign-on (Preview) | Citrix Virtual Apps and Desktops 7 2603</a></li></ul><p>Happy Troubleshooting!</p><p>Connect with me on LinkedIn:<br><a href="https://www.linkedin.com/in/namsoochoi/">https://www.linkedin.com/in/namsoochoi/</a></p><p>Disclaimer: All postings are provided “AS IS” with no warranties, and confer no rights. All opinions expressed are my own and are not of my employer.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6b77c775df0c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[[SOLVED]AADSTS50194: Two Ways to Solve the /common Endpoint Error in Entra ID]]></title>
            <link>https://medium.com/@namsoochoi/aadsts50194-solved-two-ways-to-solve-the-common-endpoint-error-in-entra-id-0aa3e6e7ef18?source=rss-15a0a9072965------2</link>
            <guid isPermaLink="false">https://medium.com/p/0aa3e6e7ef18</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[authentication]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[microsoft-azure]]></category>
            <category><![CDATA[entra-id]]></category>
            <dc:creator><![CDATA[Namsoo Choi]]></dc:creator>
            <pubDate>Wed, 29 Apr 2026 22:46:27 GMT</pubDate>
            <atom:updated>2026-04-30T21:36:48.843Z</atom:updated>
            <content:encoded><![CDATA[<p><em>A step-by-step guide to fixing the single-tenant /common endpoint mismatch</em></p><p>You just set up your Azure app registration, copied a login URL from a tutorial, opened it in the browser — and got hit with this:</p><blockquote><em>AADSTS50194: Application ‘9a7a15a2–3d5f-4ed2–9d9b-xxxxxxxxxxxx’ (JWT.MS TEST1) is not configured as a multi-tenant application. Usage of the /common endpoint is not supported for such applications created after 10/15/2018. Use a tenant-specific endpoint or configure the application to be multi-tenant.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/814/1*cnkpgc-xUNpNTYrGbq2Bdw.png" /></figure><p>Sound familiar? You are not alone. This error trips up thousands of developers every year, mostly because older Entra ID tutorials and blog posts still use /common in their login URLs. Microsoft changed the rules for apps created after October 15, 2018, and a lot of the internet has not caught up yet.</p><h3>What Is the /common Endpoint?</h3><p>When you build an app that uses Microsoft login, you send users to a Microsoft authorization URL. That URL includes an endpoint telling Microsoft which accounts are allowed to sign in.</p><p>There are two types:</p><ul><li><strong>/common</strong> — Any Microsoft account (personal or work) can sign in</li><li><strong>/&lt;tenant-id&gt;</strong> — Only accounts from your specific organization can sign in</li></ul><p>The /common endpoint sounds convenient, but Microsoft restricted it for single-tenant apps after October 2018 to improve security. If your app is registered as single-tenant but you use /common in the URL, Microsoft blocks the request with AADSTS50194.</p><h3>What Triggered This Error</h3><p>Here is the URL that caused the error:</p><pre>https://login.microsoftonline.com/common/oauth2/v2.0/authorize<br>?client_id=9a7a15a2–3d5f-4ed2–9d9b-xxxxxxxxxxxx<br>&amp;response_type=code<br>&amp;redirect_uri=https://medium.com/@namsoochoi<br>&amp;scope=openid</pre><p>Notice /common in the path. The app (JWT.MS TEST1) is registered as <strong>single-tenant only</strong>, so Microsoft rejected it the moment it saw /common.</p><h3>Two Ways to Fix It</h3><p>You have two options depending on what your app needs to do.</p><h3>Fix Option A: Use a Tenant-Specific Endpoint</h3><p>Best for: apps that only serve users inside your own organization.</p><p>You simply replace /common with either your <strong>tenant ID</strong> or your <strong>registered domain name</strong>. No portal changes needed.</p><p><strong>Step 1.</strong> Go to the <strong>Azure Portal</strong> and navigate to <strong>Microsoft Entra ID → Overview</strong>. Your Tenant ID is listed under Basic information.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/815/1*hT6zRYn4ejrrh4zFleYt3Q.png" /></figure><p><strong>Step 2.</strong> Replace /common in your URL with one of the two options below:</p><pre># Option A-1: Using Tenant ID <br>https://login.microsoftonline.com/YOUR-TENANT-ID/oauth2/v2.0/authorize<br>?client_id=9a7a15a2-3d5f-4ed2-9d9b-xxxxxxxxxxxx<br>&amp;response_type=code<br>&amp;redirect_uri=https://medium.com/@namsoochoi<br>&amp;scope=openid<br><br># Option A-2: Using Registered Domain<br>https://login.microsoftonline.com/namsoochoi.com/oauth2/v2.0/authorize<br>?client_id=9a7a15a2-3d5f-4ed2-9d9b-xxxxxxxxxxxx<br>&amp;response_type=code<br>&amp;redirect_uri=https://medium.com/@namsoochoi<br>&amp;scope=openid</pre><p>Both URLs will work. Here is how to decide which one to use:</p><p><strong>Tenant ID</strong></p><ul><li>Readability: Hard to read</li><li>Stability: Permanent, never changes</li><li>Best for: Production code</li></ul><p><strong>Domain Name (e.g. namsoochoi.com)</strong></p><ul><li>Readability: Easy to read</li><li>Stability: Can change if domain is removed from your tenant</li><li>Best for: Config files and documentation</li></ul><p>The tenant ID is the safer choice for production code since it is permanent. The domain name is more human-friendly and easier to spot in a long config file, but if the domain is ever removed from your tenant the URL will stop working.</p><p>That is it. Just update the URL in your app code or config file. No portal changes needed.</p><h3>Fix Option B: Make Your App Multi-Tenant</h3><p>Best for: SaaS products or apps that need to work across multiple organizations.</p><p>Keep using /common in your URL, but update the app registration to support multiple tenants.</p><p><strong>Step 1.</strong> Go to the <strong>Azure Portal</strong> and open your app registration. Navigate to <strong>Authentication (Preview)</strong> in the left sidebar.</p><p><strong>Step 2.</strong> Click the <strong>Supported accounts</strong> tab. You will see a dropdown currently set to “Single tenant only.”</p><p><strong>Step 3.</strong> Select <strong>“Multiple Entra ID tenants”</strong> from the dropdown and save your changes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/829/1*X2ztU4IIA-msaqxZfDQT1w.png" /></figure><p>After saving, the /common endpoint will work and users from any Microsoft Entra ID organization will be able to sign in.</p><h3>Which Fix Should You Choose?</h3><ul><li><strong>App is only for your own company or team</strong> → Fix A: Use tenant-specific endpoint</li><li><strong>App is a SaaS product used by multiple orgs</strong> → Fix B: Enable multi-tenant</li><li><strong>Following an old tutorial and just testing</strong> → Fix A is faster</li><li><strong>Need to support personal Microsoft accounts too</strong> → Fix B, then select “Any Entra ID Tenant + Personal Microsoft accounts”</li></ul><h3>Why Does This Happen So Often?</h3><p>Most tutorials written before 2018 use /common as a one-size-fits-all shortcut. Back then, it worked for single-tenant apps too. Microsoft changed this as part of a broader push to enforce clearer security boundaries between tenant types. The official documentation was updated, but most third-party blog posts and YouTube tutorials were never revised.</p><p>If you searched for “Entra ID login URL example” today, there is a good chance the top result still has /common in it.</p><h3>Quick Summary</h3><ul><li>AADSTS50194 means your single-tenant app is trying to use the /common endpoint</li><li>Fix A: Replace /common with your tenant ID in the URL — no portal changes needed</li><li>Fix B: Change your app registration to support multiple tenants in the Azure Portal → Authentication → Supported accounts</li><li>Choose based on whether your app serves one organization or many</li></ul><p><em>Have questions or ran into a different variation of this error? Drop a comment below.</em></p><p><em>Reference: Microsoft Entra authentication and authorization error codes</em> <a href="https://learn.microsoft.com/en-us/entra/identity-platform/reference-error-codes"><em>https://learn.microsoft.com/en-us/entra/identity-platform/reference-error-codes</em></a></p><p>Happy Troubleshooting!</p><p>Connect with me on LinkedIn:<br><a href="https://www.linkedin.com/in/namsoochoi/">https://www.linkedin.com/in/namsoochoi/</a></p><p>Disclaimer: All postings are provided “AS IS” with no warranties, and confer no rights. All opinions expressed are my own and are not of my employer.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0aa3e6e7ef18" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why You Can’t Rename Certain Enterprise Applications in Microsoft Entra (Even If You Used…]]></title>
            <link>https://medium.com/@namsoochoi/why-you-cant-rename-certain-enterprise-applications-in-microsoft-entra-even-if-you-used-e5209b160c7f?source=rss-15a0a9072965------2</link>
            <guid isPermaLink="false">https://medium.com/p/e5209b160c7f</guid>
            <category><![CDATA[entra]]></category>
            <category><![CDATA[app-registration]]></category>
            <category><![CDATA[enterprise-apps]]></category>
            <dc:creator><![CDATA[Namsoo Choi]]></dc:creator>
            <pubDate>Tue, 06 May 2025 20:59:32 GMT</pubDate>
            <atom:updated>2025-05-06T21:03:41.781Z</atom:updated>
            <content:encoded><![CDATA[<h3>Why You Can’t Rename Certain Enterprise Applications in Microsoft Entra (Even If You Used PowerShell)</h3><p>When working with external applications in Microsoft Entra, you might find that you can’t rename an Enterprise Application — even if you added it yourself using PowerShell. In this post, I’ll walk through a scenario using “HubSpot” as an example, explain the reason why the display name is locked, and share what options are available if you need customization.</p><h3>🔍 Symptom</h3><p>You’re in the “Microsoft Entra admin portal”, navigating to “Enterprise Applications &gt; Properties”, attempting to rename the app “HubSpot”. However, the “Name” field is “greyed out” and cannot be modified.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/934/1*t4wNSk_fWkebC5UI0dcs-g.png" /><figcaption>Grayedout</figcaption></figure><h3>⚙️ How the App Was Added</h3><p>In this case, the application was “manually added using PowerShell” via a command like:</p><pre>New-MgServicePrincipal -AppId &quot;0493df14-0cd5-4c89-b413-e0b9b90bbb17&quot;</pre><p>This command creates a “service principal” (Enterprise Application) in your tenant for an app that is registered in a “different (external) tenant” — in this case, “HubSpot’s tenant”.</p><h3>🧠 Root Cause</h3><p>Even though you used PowerShell, the behavior is still expected due to how Entra handles multi-tenant app registrations:</p><ul><li>When you create a “service principal” in your tenant for an app registered elsewhere (like HubSpot), you’re not creating a new App Registration — you’re just establishing a reference to the publisher’s app.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/688/1*C5coZAZXXXKfzaVhlzdoqQ.png" /></figure><p>📘 <a href="https://learn.microsoft.com/en-us/entra/identity-platform/how-applications-are-added#what-are-application-objects-and-where-do-they-come-from">Learn more about how applications are added</a></p><ul><li>The “display name” (name property) is defined in the &quot;application object&quot; (App Registration) that lives in the publisher’s home tenant.</li><li>Since your tenant does “not own” the App Registration, and only contains a “service principal”, you “cannot modify” the name or branding of the application.</li></ul><h3>🛠️ Solution or Workaround</h3><p>If customizing the application’s name is important to you, here are two alternatives:</p><ul><li>“Option 1: Register a new application in your own tenant”<br>Create an App Registration from scratch. This will let you fully control its name, branding, permissions, and behavior.</li><li>“Option 2: Add a non-gallery application from the Enterprise Applications blade”<br>You can add a non-gallery app by selecting “+ New application” &gt; “Create your own application” in the Enterprise Applications view. From there, choose the “Integrate any other application you don’t find in the gallery (Non-gallery)” option. This allows you to manually configure SAML, OIDC, or other authentication methods, giving you full control over the app’s display name and settings.</li></ul><p>Note: This does require you to manage more of the integration yourself, including endpoints, claims, and any required metadata.</p><h3>🧩 Final Thoughts</h3><p>Even if you’re using PowerShell to create service principals, you’re still bound by the boundaries of application ownership in Microsoft Entra. If the App Registration belongs to another tenant, its core properties — like name — remain locked. Understanding the separation between “application objects” and “service principals” is key to successfully managing SaaS integrations and permissions in Entra.</p><p>Happy Troubleshooting!</p><p>Connect with me on LinkedIn:<br><a href="https://www.linkedin.com/in/namsoochoi/">https://www.linkedin.com/in/namsoochoi/</a></p><p>Disclaimer: All postings are provided “AS IS” with no warranties, and confer no rights. All opinions expressed are my own and are not of my employer.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e5209b160c7f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AADSTS75011: Authentication Method Mismatch in SAML SSO]]></title>
            <link>https://medium.com/@namsoochoi/aadsts75011-authentication-method-mismatch-in-saml-sso-0c0c7cde4ce0?source=rss-15a0a9072965------2</link>
            <guid isPermaLink="false">https://medium.com/p/0c0c7cde4ce0</guid>
            <category><![CDATA[saml]]></category>
            <category><![CDATA[75011]]></category>
            <category><![CDATA[azure-ad]]></category>
            <category><![CDATA[entra-id]]></category>
            <category><![CDATA[saml-sso]]></category>
            <dc:creator><![CDATA[Namsoo Choi]]></dc:creator>
            <pubDate>Wed, 12 Mar 2025 16:59:06 GMT</pubDate>
            <atom:updated>2025-05-06T20:59:54.235Z</atom:updated>
            <content:encoded><![CDATA[<h3>Symptom</h3><p>Customers may encounter the following error during SAML Single Sign-On (SSO) with Microsoft Entra ID:</p><p><strong>Error Message:</strong></p><blockquote>AADSTS75011: Authentication method ‘X509, MultiFactor’ by which the user authenticated with the service doesn’t match requested authentication method ‘Password, ProtectedTransport’. Contact the &lt;App name&gt; application owner.</blockquote><p><em>Note: The authentication methods in the error message (e.g., ‘X509, MultiFactor’ and ‘Password, ProtectedTransport’) may vary depending on the user’s authentication method and the application’s SAML request configuration. However, this is one of the most common cases.</em></p><h3>Cause</h3><p>In this case, the error occurs when the authentication method used by the user does not match the authentication method requested by the SAML application.</p><ul><li>The user signs into Azure AD using <strong>X509, MultiFactor</strong> authentication.</li><li>The SAML application, however, specifies <strong>Password, ProtectedTransport</strong> in the SAML request’s RequestedAuthnContext.</li><li>Since the authentication methods do not match, Azure AD does not proceed with the SAML response and throws the AADSTS75011 error.</li></ul><h3>Solution</h3><p>To resolve this issue, customers should modify the RequestedAuthnContext in the SAML request.</p><h3>Permanent Solution</h3><p><strong>Check with the application vendor or developer</strong></p><ul><li>RequestedAuthnContext is an <strong>optional</strong> value in the SAML request, meaning it <strong>can be removed</strong> without affecting authentication.</li><li>Confirm whether the RequestedAuthnContext value can be <strong>removed</strong> from the SAML request.</li><li>If removal is not possible, request that the value <strong>‘Unspecified’</strong> be added to the RequestedAuthnContext.</li></ul><p><strong>Why this works?</strong></p><ul><li>Since RequestedAuthnContext is optional, removing it allows Azure AD to accept any valid authentication method used by the user.</li><li>Alternatively, setting it to Unspecified allows Entra ID to accept <strong>any authentication method</strong> used by the user, resolving the issue without requiring users to sign in with a specific method.</li></ul><h3>Workaround</h3><p>If the RequestedAuthnContext value cannot be changed immediately, users can try the following:</p><ul><li><strong>Logout and sign in using the authentication method requested by the application.</strong></li><li>For example, if the app requires <strong>Password, ProtectedTransport</strong>, the user should sign out and sign back in using their password instead of certificate-based or multifactor authentication.</li></ul><p><em>Note: This is only a temporary workaround and does not address the root cause. The permanent solution should be implemented to prevent repeated authentication mismatches.</em></p><h3>Additional Resources</h3><p>For further details, refer to the Microsoft documentation:<br> <a href="https://learn.microsoft.com/en-us/troubleshoot/entra/entra-id/app-integration/error-code-aadsts75011-auth-method-mismatch">Error Code AADSTS75011 — Authentication Method Mismatch</a></p><p>Happy Troubleshooting!</p><p>Connect with me on LinkedIn:<br><a href="https://www.linkedin.com/in/namsoochoi/">https://www.linkedin.com/in/namsoochoi/</a></p><p>Disclaimer: All postings are provided “AS IS” with no warranties, and confer no rights. All opinions expressed are my own and are not of my employer.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0c0c7cde4ce0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Can’t Delete an Enterprise App? 3 Possible Reasons]]></title>
            <link>https://medium.com/@namsoochoi/cant-delete-an-enterprise-app-3-possible-reasons-31eca7364610?source=rss-15a0a9072965------2</link>
            <guid isPermaLink="false">https://medium.com/p/31eca7364610</guid>
            <category><![CDATA[azure-ad]]></category>
            <category><![CDATA[enterprise-apps]]></category>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[entra]]></category>
            <category><![CDATA[identity]]></category>
            <dc:creator><![CDATA[Namsoo Choi]]></dc:creator>
            <pubDate>Tue, 11 Mar 2025 19:23:38 GMT</pubDate>
            <atom:updated>2025-03-11T19:23:38.625Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Scenario: </strong><br>As a <strong>Global Administrator</strong>, you discover an unfamiliar <strong>Enterprise application</strong> in <strong>Microsoft Entra ID</strong> and attempt to delete it. However, the <strong>Delete</strong> button is <strong>grayed out</strong>, and you see the following message:</p><blockquote>“You can’t delete this application because you don’t have the right permissions. Learn more.”</blockquote><p><strong>Troubleshooting:</strong><br>In Microsoft Entra ID, the <strong>Delete</strong> button may be disabled for certain applications due to specific restrictions. Here are some possible reasons:</p><ol><li><strong>Insufficient Permissions:</strong></li></ol><ul><li>To delete an <strong>Enterprise application</strong>, you must have one of the following roles:<br>- <strong>Global Administrator<br>- Cloud Application Administrator<br>- Application Administrator<br>- Owner</strong> of the <strong>service principal</strong></li><li>If you are signed in as a <strong>Global Administrator</strong>, this is <strong>not the issue</strong> in your case.</li></ul><p><strong>2. Microsoft-Owned Applications:</strong></p><ul><li>Certain <strong>Microsoft applications</strong> cannot be deleted from the UI, regardless of your role. Deleting Microsoft application is not recommended as it can impact service.</li><li>Typically, these applications display a message:</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6Lf65EmkCtUzk5_ytYi0oQ.png" /></figure><blockquote><em>“You can’t delete this application because it’s a Microsoft first-party application.”</em></blockquote><ul><li>However, <strong>not all</strong> Microsoft-owned applications show this message.</li><li>To confirm whether the application is Microsoft-owned, use <strong>PowerShell</strong> as described in <a href="#">this documentation</a>.</li></ul><p><strong>3. Managed Identities:</strong></p><ul><li>If the application is associated with a <strong>Managed Identity</strong>, you cannot delete its <strong>service principal</strong> from the <strong>Enterprise Apps</strong> blade.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/919/1*-TL3Dq-uhfaDuKTM_mu57A.png" /></figure><ul><li>Instead, you need to manage it at the <strong>Azure resource level</strong>.</li><li>A <strong>Managed Identity</strong> will have an <strong>Azure Resource ID</strong>, formatted like this:</li></ul><blockquote>/subscriptions/11111111-e719-xxxx-zzzz-90f8c9479b40/resourcegroups/Test1/providers/Microsoft.ManagedIdentity/userAssignedIdentities/ManagedIdentityName<br><strong>Subscription ID</strong>: 11111111-e719-xxxx-zzzz-yyyyc9479b40<br><strong>Resource Group</strong>: Test1<br><strong>Managed Identity Name</strong>: ManagedIdentityName</blockquote><ul><li>You <strong>cannot</strong> delete a <strong>Managed Identity</strong> from <strong>Microsoft Entra ID</strong> — it must be <strong>modified or deleted at the subscription level</strong>.</li></ul><h3>Conclusion:</h3><p>If the <strong>Delete</strong> button is disabled, verify the application type and its associated permissions. If it’s a <strong>Microsoft application</strong> or a <strong>Managed Identity</strong>, deletion must be handled differently.</p><p>Happy Troubleshooting!</p><p>Connect with me on LinkedIn:<br><a href="https://www.linkedin.com/in/namsoochoi/">https://www.linkedin.com/in/namsoochoi/</a></p><p>Disclaimer: All postings are provided “AS IS” with no warranties, and confer no rights. All opinions expressed are my own and are not of my employer.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=31eca7364610" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Granting user consent on behalf of a user for an application using PowerShell.]]></title>
            <link>https://medium.com/@namsoochoi/granting-user-consent-on-behalf-of-a-user-for-an-application-using-powershell-4a65a0c81258?source=rss-15a0a9072965------2</link>
            <guid isPermaLink="false">https://medium.com/p/4a65a0c81258</guid>
            <category><![CDATA[admin-consent]]></category>
            <category><![CDATA[entra]]></category>
            <category><![CDATA[identity]]></category>
            <category><![CDATA[user-consent]]></category>
            <dc:creator><![CDATA[Namsoo Choi]]></dc:creator>
            <pubDate>Tue, 25 Feb 2025 22:20:02 GMT</pubDate>
            <atom:updated>2025-03-06T23:10:39.026Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Objective</strong></h3><ol><li>When granting admin consent is not an option, <strong>user consent</strong> becomes an alternative. To grant user consent on behalf of another user for an application, administrators must use PowerShell or the Microsoft Graph API. With PowerShell or Microsoft Graph, admins can grant user consent for permissions requires admin consent such as Application.read.all. This guide provides a step-by-step process to accomplish this.</li></ol><p>Note: The Azure portal UI does not support granting user consent on behalf of another user.</p><h3><strong>Prerequisites</strong></h3><ul><li>Access to Microsoft Entra ID (Azure AD)</li><li>PowerShell installed on your machine</li><li>Microsoft Graph PowerShell module installed (Install-Module Microsoft.Graph)</li><li>A user account with one of the following roles:<br>- Global Administrator<br>- Privileged Role Administrator<br>- Application Administrator<br>- Cloud Application Administrator</li></ul><h3><strong>Before User Consent is granted</strong></h3><p>When a user accesses the application, they will encounter an error message stating “Need admin approval” (if the admin consent workflow is not enabled) or “Approval Required” (if the admin consent workflow is enabled). This occurs because the user cannot grant consent on their own behalf.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/464/1*N83leq5LcJFZO_GUvlWejA.png" /></figure><h3>After User Consent is granted</h3><p>Once user consent is granted by an admin, the error message will no longer appear, and the user will be able to access the application.</p><h3><strong>Required Data</strong></h3><ul><li><strong>Client Application ID:</strong> The Application (client) ID of the app for which you are granting consent.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/684/1*Q1zxL_2113j2xsmS17Q__w.png" /></figure><ul><li><strong>API Permissions:</strong> The permissions the client application requires. In this guide, we will use: “openid”, “profile”, “offline_access”, “User.Read”, “User.ReadBasic.All”.</li><li><strong>User Identifier:</strong> The username (UPN) or object ID of the user on whose behalf consent is granted.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/731/1*EyfrjjnCjRp8bBEg7jJRsw.png" /></figure><h3>Steps</h3><ol><li><strong>Copy the PowerShell Script:</strong><br>Copy the script from the <a href="https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/grant-consent-single-user?pivots=msgraph-powershell#grant-consent-on-behalf-of-a-single-user">Microsoft Learn documentation</a> and paste it into PowerShell ISE.</li></ol><p><strong>2. Modify Script Variables:</strong><br>Replace the placeholders in the script with your values:</p><ul><li>$clientAppId with the client application ID.</li><li>$permissions with the required permissions.</li><li>$userUpnOrId with the user’s UPN or object ID.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7zXMA1dCCk0Y-K-tY4_TPw.png" /></figure><p><strong>3. Run Step 0: Connect to Microsoft Graph:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L4FmXOVHLqr4b78jkeHJRA.png" /></figure><p>Sign in with an account that has the necessary administrative role. If this is your first time using the Microsoft Graph PowerShell module, you may see a consent prompt.</p><ul><li><strong>Granting consent only for your admin account:</strong><br>Click <strong>Accept</strong> without selecting <strong>Consent on behalf of your organization</strong>.</li><li><strong>Granting consent on behalf of your organization (admin consent):</strong><br>Select <strong>Consent on behalf of your organization</strong> and click <strong>Accept</strong>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/564/1*MyfYdufGAOG6ZQ9FE4U8ig.png" /></figure><p><strong>Run Steps 1, 2, and 3:</strong><br>Follow the script instructions to complete the consent process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/822/1*tSb8SXUOgEUkGsGzFTZuEQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HuJHwvL7vLmduMFKeRD0_A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f-eYvECMN5qVyOdsaUGRsQ.png" /></figure><h3>Verifying Consent</h3><p>To confirm the consent was granted successfully, run:</p><pre>New-MgServicePrincipalAppRoleAssignedTo -ServicePrincipalId $clientSp.Id | fl</pre><p>Check the output to verify the correct user and application are listed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U9hwCQpSnmKg-lf6ebT_7Q.png" /></figure><p>You can also verify via the Azure portal:</p><ol><li>Navigate to <strong>Azure Portal</strong> → <strong>Enterprise Applications</strong>.</li><li>Find and select your application.</li><li>Go to <strong>Permissions</strong> → <strong>User Consent</strong>.</li><li>Under <strong>User Consent</strong>, you can view the list of permissions and the users granted consent.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u8_Va1jgBnNFwlfPZPP4zg.png" /></figure><p>5. Click the user count (e.g., <strong>1 total user(s)</strong>) to see the details.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/268/1*V-8-YXGV5ELoRpmPFemETg.png" /></figure><p>I edited permissions to include “Application.read.all” which is requiring admin consent. I was able to grant user consent on behalf of the user.</p><p>$permissions = @(“openid”, “profile”, “offline_access”, “User.Read”, “User.ReadBasic.All”, “Application.read.all”)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D4F8DUfeW4iKPs14Zgwv1g.png" /></figure><h3>Conclusion</h3><p>Granting user consent on behalf of another user using PowerShell is a useful approach when admin consent is not an option. By following this guide, administrators can efficiently manage application permissions while ensuring users have the necessary access. Always verify the granted consent via PowerShell or the Azure portal to confirm successful implementation. If you encounter issues, check permission scopes and administrative roles to troubleshoot.</p><p>This process enhances security and compliance while maintaining smooth user access to essential applications.</p><h3><strong>Reference:</strong></h3><h4><strong>https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/grant-consent-single-user?pivots=msgraph-powershell</strong></h4><p>Happy Troubleshooting!</p><p>Connect with me on LinkedIn:<br><a href="https://www.linkedin.com/in/namsoochoi/">https://www.linkedin.com/in/namsoochoi/</a></p><p>Disclaimer: All postings are provided “AS IS” with no warranties, and confer no rights. All opinions expressed are my own and are not of my employer.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4a65a0c81258" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Managing Expiring Secrets and Certificates in App Registrations (Without Notifications)]]></title>
            <link>https://medium.com/@namsoochoi/how-can-i-set-up-notifications-for-expiring-secrets-or-certificates-in-azure-app-registration-8e073e56019b?source=rss-15a0a9072965------2</link>
            <guid isPermaLink="false">https://medium.com/p/8e073e56019b</guid>
            <dc:creator><![CDATA[Namsoo Choi]]></dc:creator>
            <pubDate>Mon, 10 Feb 2025 20:38:03 GMT</pubDate>
            <atom:updated>2025-06-02T15:48:42.114Z</atom:updated>
            <content:encoded><![CDATA[<h3>Problem Statement</h3><p>Microsoft Entra ID <strong>does not provide a built-in feature</strong> to automatically notify administrators when <strong>client secrets or certificates</strong> on <strong>App Registrations</strong> are about to expire.</p><blockquote><em>Note: Entra ID can send email notifications for </em><strong><em>SAML certificate expiration</em></strong><em> on </em><strong><em>Enterprise Applications</em></strong><em> (60, 30, and 7 days before expiry), but this capability is </em><strong><em>not available</em></strong><em> for App Registration secrets or certificates.</em></blockquote><h3>Workaround Options</h3><h4>1. PowerShell Automation</h4><p>You can use PowerShell to regularly scan and report on expiring credentials.</p><p>Microsoft provides an official script that:</p><ul><li>Retrieves <strong>App Registrations</strong> with secrets and certificates expiring within a specified timeframe</li><li>Optionally includes already expired credentials</li><li>Extracts <strong>application owners</strong> for visibility</li><li>Outputs result to a <strong>CSV file</strong></li></ul><blockquote><a href="https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/scripts/powershell-export-apps-with-expiring-secrets"><em>PowerShell: Export App Registrations with Expiring Secrets or Certificates</em></a></blockquote><p>This script can be integrated with alerting mechanisms (e.g., Logic Apps, email reports, Azure Automation) to proactively monitor credential expirations.</p><h4>2. Microsoft Entra recommendation: Renew expiring application credentials (Preview Feature)</h4><p>This feature is available in the Microsoft Entra Admin Center and appears under <a href="https://learn.microsoft.com/en-us/entra/identity/monitoring-health/overview-recommendations"><strong>Microsoft Entra recommendations</strong></a>. It flags secrets or certificates that belong to an <strong>App Registration</strong> and are <strong>expiring within the next 30 days</strong>. These recommendations help the customer proactively identify and renew expiring credentials before they cause disruptions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/590/1*lA7OKQY3FtjEbjPM2RuPQA.png" /></figure><blockquote><a href="https://learn.microsoft.com/en-us/entra/identity/monitoring-health/recommendation-renew-expiring-application-credential?tabs=microsoft-entra-admin-center"><em>Renew Expiring Application Credentials (Preview)</em></a></blockquote><h3>Summary</h3><p><strong>Built-in Expiry Notifications:</strong></p><ul><li><strong>App Registration Secrets/Certificates</strong>: Not supported</li><li><strong>Service Principal Credentials (e.g., SAML Certs in Enterprise Apps)</strong>: Supported — email sent 60, 30, and 7 days before <strong>SAML certificate</strong> expiry</li></ul><p><strong>PowerShell Monitoring:</strong></p><ul><li>Available for both App Registrations and Service Principals<br> → Use the official <a href="https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/scripts/powershell-export-apps-with-expiring-secrets">PowerShell script</a></li></ul><p><strong>Entra Recommendation (Preview):</strong></p><ul><li>Available in Microsoft Entra Admin Center</li><li>Shows <strong>secrets and certificates expiring within the next 30 days</strong></li><li>Supports both <a href="https://learn.microsoft.com/en-us/entra/identity/monitoring-health/recommendation-renew-expiring-application-credential?tabs=microsoft-entra-admin-center">Application Credentials</a> and <a href="https://learn.microsoft.com/en-us/entra/identity/monitoring-health/recommendation-renew-expiring-service-principal-credential?tabs=microsoft-entra-admin-center">Service Principal Credentials</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8e073e56019b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[[SOLVED] Missing Group Claims in JWT(Id_token or Access token) from Entra ID]]></title>
            <link>https://medium.com/@namsoochoi/solved-missing-group-claims-in-jwt-id-token-or-access-token-from-entra-id-30a3d08e87c1?source=rss-15a0a9072965------2</link>
            <guid isPermaLink="false">https://medium.com/p/30a3d08e87c1</guid>
            <category><![CDATA[oauth]]></category>
            <category><![CDATA[azure-ad]]></category>
            <category><![CDATA[claims]]></category>
            <category><![CDATA[entra]]></category>
            <category><![CDATA[enterprise-application]]></category>
            <dc:creator><![CDATA[Namsoo Choi]]></dc:creator>
            <pubDate>Mon, 10 Feb 2025 18:44:06 GMT</pubDate>
            <atom:updated>2025-02-10T18:58:06.250Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Symptom:</strong></h3><p><strong>Missing ‘groups’ Claim in JWT Tokens. </strong>The expected groups claim is missing from JWT (id_token or access_token), even when group claim is configured.</p><h3>Cause:</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/689/0*wjJKM7M1SZd50ls6.png" /></figure><p>Entra ID imposes a limit on the number of groups it emits in a token — 150 for SAML and 200 for JWT. This limit includes both direct and nested group memberships. If a user is a member of more than 150 groups, Entra ID will not include group claims in the token. Instead, it provides a link to retrieve group information via the Microsoft Graph API. For more details, see the <a href="https://docs.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-fed-group-claims#options-for-applications-to-consume-group-information">Microsoft Documentation</a>.</p><h3>Solution:</h3><p>Updating groupMembershipClaims in the Manifest</p><p>To ensure group claims are included in the JWT token, update the groupMembershipClaims value in the application manifest as follows:</p><h3>Steps to Access the Manifest</h3><ol><li>Go to <strong>Azure portal</strong></li><li>Navigate to <strong>Entra ID</strong></li><li>Select <strong>App registrations</strong></li><li>Search for the specific application</li><li>Open the <strong>Manifest</strong></li><li>Update “groupMembershipClaims” in the Manifest</li></ol><pre>&quot;groupMembershipClaims&quot;: &quot;ApplicationGroup&quot;</pre><p>This setting ensures that only <strong>application-specific</strong> group claims are included in the token, helping to keep the number of groups within the limit.</p><h3>Assign the Required Groups</h3><ol><li>Go to <strong>Azure portal</strong> → <strong>Entra ID </strong>→ <strong>Enterprise Applications</strong></li><li>Select the specific application</li><li>Navigate to <strong>Users and Groups</strong> in the same app settings</li><li>Add the specific groups that should be assigned to the app</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/428/0*1IMbNsSawq9zXJ53.png" /></figure><h3>Additional Reference</h3><p>For further details and other potential workarounds, refer to the Microsoft documentation:<br><a href="https://learn.microsoft.com/en-us/entra/identity/hybrid/connect/how-to-connect-fed-group-claims#configure-the-microsoft-entra-application-registration-for-group-attributes">Configure the Microsoft Entra application registration for group attributes</a>.</p><p>Happy Troubleshooting!</p><p>Connect with me on LinkedIn:<br><a href="https://www.linkedin.com/in/namsoochoi/">https://www.linkedin.com/in/namsoochoi/</a></p><p>Disclaimer: All postings are provided “AS IS” with no warranties, and confer no rights. All opinions expressed are my own and are not of my employer.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=30a3d08e87c1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[[SOLVED] Missing Group Claims in SAML Responses from Entra ID]]></title>
            <link>https://medium.com/@namsoochoi/solved-missing-group-claims-in-saml-responses-from-entra-id-c0329193c204?source=rss-15a0a9072965------2</link>
            <guid isPermaLink="false">https://medium.com/p/c0329193c204</guid>
            <category><![CDATA[saml2]]></category>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[aml]]></category>
            <category><![CDATA[entra]]></category>
            <category><![CDATA[azure-ad]]></category>
            <dc:creator><![CDATA[Namsoo Choi]]></dc:creator>
            <pubDate>Wed, 04 Sep 2024 21:24:01 GMT</pubDate>
            <atom:updated>2024-09-04T21:24:01.446Z</atom:updated>
            <content:encoded><![CDATA[<h3>Symptom:</h3><p>When users authenticate via SAML, the expected “groups” claim is missing from the SAML response. Instead of “groups” claim, there is a link to retrieve group information via the Microsoft Graph API.</p><h3>Cause:</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/689/1*rGnFS3NYqiprevBlAd3ElQ.png" /></figure><p>Entra ID imposes a limit on the number of groups it emits in a token — 150 for SAML and 200 for JWT. This limit includes both direct and nested group memberships. If a user is a member of more than 150 groups, Entra ID will not include group claims in the token. Instead, it provides a link to retrieve group information via the Microsoft Graph API. For more details, see the <a href="https://docs.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-fed-group-claims#options-for-applications-to-consume-group-information">Microsoft Documentation</a>.</p><h3>Solution:</h3><p>To ensure the “groups” claim is emitted, the total number of groups must be less than 150. You can achieve this by configuring the SSO settings in the Azure Enterprise app to either:</p><ul><li>Send only the groups assigned to the application, or</li><li>Apply filtering to the groups that are emitted.</li></ul><h3>How to Send Only Groups Assigned to the Application</h3><ol><li><strong>Navigate to the Application’s SSO Settings</strong>:</li></ol><ul><li>Go to <strong>Azure Portal</strong> → <strong>Azure AD</strong> → <strong>Enterprise Applications</strong>.</li><li>Select the application in question.</li><li>Under <strong>Single Sign-On</strong>, click <strong>User Attributes &amp; Claims</strong>.</li><li>Add a group claim and select the “Groups assigned to the application” option as described in <a href="https://docs.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-fed-group-claims#add-group-claims-to-tokens-for-saml-applications-using-sso-configuration">this documentation</a>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/825/1*L0rCeGJ65WnZBfHq9feg8A.png" /></figure><p><strong>2. Assign the Required Groups</strong>:</p><ul><li>Go to <strong>Users and Groups</strong> in the same app settings.</li><li>Add the specific groups that should be assigned to the app.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/428/1*yTGDCGkKknzm9az2CSdvQQ.png" /></figure><h3>How to Filter Groups</h3><p>You can also configure filters to reduce the number of groups that are emitted by the token:</p><ol><li>In the same <strong>User Attributes &amp; Claims</strong> panel, configure filters on the group’s attributes:</li></ol><ul><li><strong>Prefix</strong>: Matches the start of the selected attribute.</li><li><strong>Suffix</strong>: Matches the end of the selected attribute.</li><li><strong>Contains</strong>: Matches any location in the selected attribute.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/359/1*13Od-7KYVB0FHSv_6aHzVg.png" /></figure><p>For more detailed instructions on filtering, refer to <a href="https://learn.microsoft.com/en-us/azure/active-directory/hybrid/connect/how-to-connect-fed-group-claims#group-filtering">Microsoft’s guide</a>.</p><h3>Conclusion:</h3><p>By sending only the necessary groups or applying appropriate filters, you can ensure that the “groups” claim is included in the SAML response without exceeding the Entra ID limit.</p><p>Happy Troubleshooting!</p><p>Connect with me on LinkedIn:<br><a href="https://www.linkedin.com/in/namsoochoi/">https://www.linkedin.com/in/namsoochoi/</a></p><p>Disclaimer: All postings are provided “AS IS” with no warranties, and confer no rights. All opinions expressed are my own and are not of my employer.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c0329193c204" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[[Solved] “Need admin approval” or “Approval required” AADSTS90094 error during Microsoft sign in]]></title>
            <link>https://medium.com/@namsoochoi/solved-need-admin-approval-or-approval-required-aadsts90094-error-during-microsoft-sign-in-b3fde2ec4523?source=rss-15a0a9072965------2</link>
            <guid isPermaLink="false">https://medium.com/p/b3fde2ec4523</guid>
            <category><![CDATA[azure-ad]]></category>
            <category><![CDATA[admin-consent]]></category>
            <category><![CDATA[need-admin-approval]]></category>
            <category><![CDATA[90094]]></category>
            <category><![CDATA[entra-id]]></category>
            <dc:creator><![CDATA[Namsoo Choi]]></dc:creator>
            <pubDate>Thu, 25 Jan 2024 18:25:49 GMT</pubDate>
            <atom:updated>2024-01-25T18:25:49.451Z</atom:updated>
            <content:encoded><![CDATA[<p>The AADSTS90094 error occurs when a non-administrator user attempts to use an application that requires consent, but the company administrator has turned off the ability for users to consent to applications.</p><p>In this blog, we will discuss the reasons behind this error and how to resolve it. Stay tuned!</p><h3>SYMTOM:</h3><p>Users will see this error message saying “Need admin approval” when admin consent workflow is disabled.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mvwQHJ3IHa9vht5rDfs5eA.png" /><figcaption>“Need admin approval” admin consent error</figcaption></figure><p>Users will see this error message saying “Approval required” when admin consent workflow is enabled. The prompt shows permissions requested from the app to Entra ID during the sign-in.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/979/1*g6PPZrtqT5mw9dtHc4awyg.png" /></figure><p>If you review the sign in log, you will see error code 90094 which means</p><blockquote><em>“Admin consent is required for the permissions requested by this application.”</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/756/1*TYiSvYDcOMbGFUGeIOOacQ.png" /></figure><p>There are 2 most common causes.</p><p>You will need to get a URL of a sign-in page to determine the cause.<br>Either users are redirected as a whole page or with a popup, users can see a URL starting with https://login.microsoftonline.com”. If the app skips the page automatically, collecting log with F12(.har) or fiddler will be helpful. We will check 2 parameters — ‘prompt’ and ‘scope’.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zJVGIjirTTuVtX55izP9kA.png" /></figure><blockquote><em>EXAMPLE: “https://login.microsoftonline.com/common/oauth2/v2.0/authorize?client_id={AppID}&amp;response_type=code&amp;redirect_uri={RedirectURI}&amp;response_mode=fragment&amp;</em><strong>scope=openid profile email user.read mail.read</strong><em>&amp;state=12345&amp;nonce=12345&amp;</em><strong>prompt=consent</strong><em>”</em></blockquote><blockquote>NOTE: You can replace {AppID} with the appID(clientID) of the app shown on Entra ID-App registration-Overview. You can replace {RedirectURI} with any redirectURI of the app shown on Entra ID-App registration-Authentication.</blockquote><h3>CAUSE 1:</h3><p>The request from the app to Entra ID includes “prompt=consent”.</p><h3>SOLUTION for the cause 1:</h3><p>In this case, Entra ID will honor “prompt=consent” and prompt consent even when admin consent is already granted. The soluiton is asking the app vendor/owner to remove “prompt=consent” in the request from the app to Entra ID.<br>Reference:<br><a href="https://learn.microsoft.com/en-us/entra/identity-platform/v2-oauth2-implicit-grant-flow">https://learn.microsoft.com/en-us/entra/identity-platform/v2-oauth2-implicit-grant-flow</a></p><h3>CAUSE 2:</h3><p>In the ‘scope’ parameter, there is one or more permissions that are NOT admin consented. In this case, users will see the error when they cannot grant consent by themselves.</p><h3>SOLUTION for the cause 2:</h3><p>You will need to grant admin consent to permissions requested but not admin consented.</p><p>Let’s find out how to do that.<br>You can compare permissions requested in the URL and the permissions admin consented to the app.</p><p>When you see the URL above, ‘scope’ parameter includes 5 permissions as below.<br>‘<em>openid profile email user.read mail.read’.</em></p><p>When you go to Azure Portal — Entra ID- Enterprise app — Search the app having issue — Permissions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cGvKBbDkAu4bQlK-enHx_Q.png" /></figure><p>In my case, there are 4 permissions as below are admin consented.<br>‘<em>openid profile email user.read’</em></p><p>Yes, <em>mail.read </em>is NOT admin consented. As the user cannot grant consent to the permission, the user got the error.</p><p>Now, let’s grant admin consent to the app.<br>Mostly, clicking “Grant admin consent &lt;ORG name&gt;” doesn’t resolve the issue. When admin clicks the button, the request goes to /adminconsent endpoint as below.</p><blockquote>https://login.microsoftonline.com/{tenant-id}/adminconsent?client_id={client-id}</blockquote><p>This endpoints pulls permissions that registered in the App Registration of the app. If there is no permission or only a part of permission are registered there, clicking clicking “Grant admin consent &lt;ORG name&gt;” won’t grant admin consent to <em>mail.read </em>and the issue will persist.</p><p>We need to use /authorize endpoint to grant permission dynamically.<br>Reference:<br><a href="https://learn.microsoft.com/en-us/previous-versions/azure/active-directory/azuread-dev/azure-ad-endpoint-comparison#incremental-and-dynamic-consent">https://learn.microsoft.com/en-us/previous-versions/azure/active-directory/azuread-dev/azure-ad-endpoint-comparison#incremental-and-dynamic-consent</a></p><p>Global admin can go to the URL that the user had issue and grant admin consent. <br>NOTE: The global admin MUST check “Consent on behalf of your organization”, and click Accept. If it is not checked, consent will be granted only for the global admin account, the issue will persist for other users.</p><blockquote>“https://login.microsoftonline.com/common/oauth2/v2.0/authorize?client_id={AppID}&amp;response_type=code&amp;redirect_uri={RedirectURI}&amp;response_mode=fragment&amp;<em>scope=openid profile email user.read mail.read</em>&amp;state=12345&amp;nonce=12345&amp;<em>prompt=consent</em>”</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/564/1*6N8PZ6doL4KHnjuRC30zgQ.png" /></figure><p>Then you can go back to Azure Portal — Entra ID- Enterprise app — Search the app having issue — Permissions and confirm if all permissions were successfully admin consented.</p><p>Happy Troubleshooting!</p><p>Connect with me on LinkedIn:<br><a href="https://www.linkedin.com/in/namsoochoi/">https://www.linkedin.com/in/namsoochoi/</a></p><p>Disclaimer: All postings are provided “AS IS” with no warranties, and confer no rights. All opinions expressed are my own and are not of my employer.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b3fde2ec4523" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>