AADSTS90015: Requested query string is too long.

Question

Hello, I’m having a problem with Databricks.

After working within the platform, I’m logged out and asked to log in again. I do so, but I get the message shown in the attached image. I’ve already cleared my browser’s cache and tried three different web browsers, but to no avail. I’ve switched computers, but the result is the same.

Has anyone else had the same problem? And how did you sort it out?

Answer 1

Hi @Jhony Valderrama
Thanks for sharing the details - we were able to reproduce similar behavior earlier.

As a temporary workaround, some users were able to avoid the repeated session timeouts by:

• Creating a new user in Microsoft Entra ID
• Granting that user required access (for example, Owner on the subscription)
• Logging into the same Azure Databricks workspace using the new user

This helped in cases where the session was getting invalidated repeatedly.

That said, we’ve now checked with our internal team, and the underlying issue has been addressed from the service side.

Could you please try again and confirm if the issue still persists on your end?

If you continue to see the same behavior, let us know along with:

• Browser and version
• Whether it happens in incognito/private mode as well

Happy to take a closer look if needed. Thanks!

Answer 2

AADSTS90015 indicates that the sign-in request URL sent to Microsoft Entra ID is too long, typically because the browser is sending an oversized header (often due to accumulated cookies) or an invalid/looping redirect.

Given that the issue persists across browsers and machines, the problem is likely with the Azure Databricks → Entra ID sign-in flow for this tenant, not with a local browser profile.

Actionable steps:

1. Verify it is not a generic browser/cookie issue
   • Completely sign out of all Microsoft accounts in the browser.
   • Close all tabs, reopen a private/incognito window, and try to access the Azure Databricks workspace URL directly from there.
   • If it works in a private window but not in normal mode, clear all cookies for microsoftonline.com, login.microsoftonline.com, and the Databricks workspace domain.
2. Check for tenant-wide access blocks or sign-in issues
   • Confirm that other Azure services (for example, Azure portal, Outlook, Teams) can be accessed with the same account. If they also intermittently fail or show tenant-blocked messages, the issue may be a temporary tenant or policy problem that the Microsoft 365/Azure admin must resolve.
3. Engage the Azure Databricks / Entra ID administrator
   • Provide the admin with the full error details from the Microsoft sign-in page (Correlation ID, Timestamp, and Error code AADSTS90015). These details are specifically called out on the error page as what admins should use when opening a support case.
   • Ask the admin to:
     • Check Conditional Access and authentication policies that might be causing repeated redirects or oversized requests.
     • Confirm the Databricks enterprise application configuration in Entra ID is not misconfigured (for example, custom redirect URLs or non-standard parameters).
4. If the problem continues for multiple users
   • This points to a service-side issue. The admin should open a support ticket with Microsoft, attaching the error details and timestamps from several affected users.

Because this is an Entra ID sign-in error surfaced during Databricks authentication and not a Databricks workspace configuration error, resolution will typically require tenant admin or Microsoft support intervention rather than changes inside Databricks itself.

---

References:

• "Header Field Too Long" error when accessing a SharePoint Online site
• Troubleshoot Azure subscription sign-in issues