<?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>topic Error AADSTS53011:User Blocked Due to Risk on Home Tenant When Accessing BC API via Fabric Notebook in Data Engineering</title>
    <link>https://community.fabric.microsoft.com/t5/Data-Engineering/Error-AADSTS53011-User-Blocked-Due-to-Risk-on-Home-Tenant-When/m-p/4763872#M10937</link>
    <description>&lt;P&gt;I'm trying to access the Microsoft Dynamics 365 Business Central API through a Microsoft Fabric notebook. The same API works successfully when called using Postman or VS Code with the same credentials and token generation method.&lt;/P&gt;&lt;P&gt;However, when I attempt the same request from within the Fabric notebook, I receive the following error:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="python"&gt;Token request failed:
{
"error": "invalid_request",
"error_description": "AADSTS53011: User blocked due to risk on home tenant. Trace ID: &amp;lt;hidden&amp;gt;, Correlation ID: &amp;lt;hidden&amp;gt;, Timestamp: 2025-07-15T14:12:28Z",
"error_codes": [53011],
"timestamp": "2025-07-15T14:12:28Z",
"trace_id": "",
"correlation_id": "",
"claims": {
"access_token": {
"capolids": {
"essential": true,
"values": [""]
}
}
}
}&lt;/LI-CODE&gt;&lt;P&gt;&lt;BR /&gt;Could you help me understand why this error is triggered only in Fabric and how to resolve it?&lt;/P&gt;</description>
    <pubDate>Tue, 15 Jul 2025 14:40:17 GMT</pubDate>
    <dc:creator>kasun_rumesh</dc:creator>
    <dc:date>2025-07-15T14:40:17Z</dc:date>
    <item>
      <title>Error AADSTS53011:User Blocked Due to Risk on Home Tenant When Accessing BC API via Fabric Notebook</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Engineering/Error-AADSTS53011-User-Blocked-Due-to-Risk-on-Home-Tenant-When/m-p/4763872#M10937</link>
      <description>&lt;P&gt;I'm trying to access the Microsoft Dynamics 365 Business Central API through a Microsoft Fabric notebook. The same API works successfully when called using Postman or VS Code with the same credentials and token generation method.&lt;/P&gt;&lt;P&gt;However, when I attempt the same request from within the Fabric notebook, I receive the following error:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="python"&gt;Token request failed:
{
"error": "invalid_request",
"error_description": "AADSTS53011: User blocked due to risk on home tenant. Trace ID: &amp;lt;hidden&amp;gt;, Correlation ID: &amp;lt;hidden&amp;gt;, Timestamp: 2025-07-15T14:12:28Z",
"error_codes": [53011],
"timestamp": "2025-07-15T14:12:28Z",
"trace_id": "",
"correlation_id": "",
"claims": {
"access_token": {
"capolids": {
"essential": true,
"values": [""]
}
}
}
}&lt;/LI-CODE&gt;&lt;P&gt;&lt;BR /&gt;Could you help me understand why this error is triggered only in Fabric and how to resolve it?&lt;/P&gt;</description>
      <pubDate>Tue, 15 Jul 2025 14:40:17 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Engineering/Error-AADSTS53011-User-Blocked-Due-to-Risk-on-Home-Tenant-When/m-p/4763872#M10937</guid>
      <dc:creator>kasun_rumesh</dc:creator>
      <dc:date>2025-07-15T14:40:17Z</dc:date>
    </item>
    <item>
      <title>Re: Error AADSTS53011:User Blocked Due to Risk on Home Tenant When Accessing BC API via Fabric Notebook</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Engineering/Error-AADSTS53011-User-Blocked-Due-to-Risk-on-Home-Tenant-When/m-p/4764766#M10945</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="javascript:void(0)" data-lia-user-mentions="" data-lia-user-uid="317253" data-lia-user-login="kasun_rumesh" class="lia-mention lia-mention-user"&gt;kasun_rumesh&lt;/a&gt;&amp;nbsp;,&lt;BR /&gt;&lt;BR /&gt;Thank you for reaching out to Microsoft Community.&lt;/P&gt;
&lt;P&gt;Microsoft Fabric notebooks might be triggering a fresh token request that enforces stricter conditional access policies or identity protection policies.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;Check Risky Users Report. Go to Risky Users in Microsoft Entra ID and search for the affected user.&lt;/P&gt;
&lt;P&gt;If listed, you can either dismiss the risk, if it’s a false positive, reset the password to trigger remediation.&lt;BR /&gt;If the user is a guest or federated from another tenant, ensure they’ve completed Multi-Factor Authentication (MFA) and Self-Service Password Reset (SSPR) in their home tenant.&lt;BR /&gt;Review policies in both the home tenant and the resource tenant to ensure they aren’t blocking high-risk users.&lt;BR /&gt;In Microsoft Entra, go to Sign-in logs to get detailed info on why the sign-in was blocked.&lt;/P&gt;
&lt;P&gt;Please refer to these documents which helps you to troubleshoot the issue based on the cause.&lt;BR /&gt;&lt;A href="https://learn.microsoft.com/en-us/entra/id-protection/concept-identity-protection-b2b" target="_blank"&gt;Microsoft Entra ID Protection for B2B Users - Microsoft Entra ID Protection | Microsoft Learn&lt;/A&gt;&lt;BR /&gt;&lt;A href="https://learn.microsoft.com/en-us/entra/id-protection/howto-identity-protection-remediate-unblock" target="_blank"&gt;Remediate risks and unblock users - Microsoft Entra ID Protection | Microsoft Learn&lt;/A&gt;&lt;BR /&gt;&lt;A href="https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/troubleshoot-app-publishing" target="_blank"&gt;Your sign-in was blocked - Microsoft Entra ID | Microsoft Learn&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;I hope this will help.&lt;BR /&gt;Best Regards,&lt;BR /&gt;Chaithra E.&lt;/P&gt;</description>
      <pubDate>Wed, 16 Jul 2025 07:15:36 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Engineering/Error-AADSTS53011-User-Blocked-Due-to-Risk-on-Home-Tenant-When/m-p/4764766#M10945</guid>
      <dc:creator>v-echaithra</dc:creator>
      <dc:date>2025-07-16T07:15:36Z</dc:date>
    </item>
  </channel>
</rss>

