Share via

databricks workspace timed out issue

Trendytech Sumit 5 Reputation points
2026-03-19T19:35:23.4333333+00:00

My azure databricks session is getting timed out every 2-3 minutes.

Azure Databricks
Azure Databricks

An Apache Spark-based analytics platform optimized for Azure.

0 comments No comments

2 answers

Sort by: Most helpful
  1. SAI JAGADEESH KUDIPUDI 1,600 Reputation points Microsoft External Staff Moderator
    2026-03-23T03:40:17.74+00:00

    Hi **Trendytech Sumit,
    **We are aware that several users are encountering the AADSTS90015 (Requested query string too long) error when attempting to sign in to Azure Databricks.

    From the observed behavior—such as intermittent login success, impact across multiple tenants, and session drops—this indicates a service-side authentication issue involving Microsoft Entra ID and the Databricks sign-in flow, rather than a misconfiguration within individual workspaces.

    As interim mitigation, you may try the following:

    Access the workspace using its direct workspace URL instead of regional links or saved bookmarks

    Clear browser cache and cookies, or use an Incognito/Private browsing session

    Ensure only one account session is active during sign-in

    Test with a different browser to rule out session-related inconsistencies

    If the issue persists, collect the Request ID, Correlation ID, and Timestamp from the error page and share them when contacting support. These details will assist the service team in analyzing the backend authentication flow.

    We are actively tracking similar occurrences and will provide updates as more information becomes available.

    Thank you for your understanding.


  2. hossein jalilian 13,360 Reputation points Volunteer Moderator
    2026-03-19T20:18:21.8966667+00:00

    Thanks for posting your question in the Microsoft Q&A forum.

    It's not normal and is not controlled by STATEMENT_TIMEOUT. This usually indicates an issue with authentication, browser session/cookies, or limitations of a free/trial workspace, rather than a configurable timeout.

    To troubleshoot, try a clean browser session, verify if it’s only the UI or also jobs, and test on another device. If it happens in a trial/free environment, there’s typically no way to extend session duration, and moving to a standard workspace is recommended


    Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.