Azure Databricks session expires after 2–3 minutes of inactivity

Question

Hi everyone,

I’m currently learning Azure Databricks using a Microsoft Azure free trial subscription (with the $200 credit), and I’m running into an issue that’s blocking progress.

I have created an Azure Databricks workspace (Premium tier) within my Azure subscription, so this should be a standard Azure Databricks deployment (not Databricks Free Edition).

However, whenever I access the workspace, the session expires after approximately 2–3 minutes of inactivity. This happens consistently, even with very short pauses.

What I’ve already tried:

• Switching browsers (Chrome, Edge)
• Using incognito/private mode
• Disabling all extensions (no ad blockers or privacy tools active)
• Ensuring cookies are enabled
• Logging out and back in
• Trying different networks (no VPN)

Despite this, the issue persists.

Additional details:

• Personal Microsoft account (not corporate or school)
• Brand new Azure subscription with prepaid $200 credit
• Workspace created with default settings (no custom security or networking configurations)

Clarification:

This is Azure Databricks via Azure subscription, not the standalone Databricks Free Edition.

Question:

• Is a 2–3 minute idle session timeout expected under any circumstances in Azure Databricks?
• Or could this indicate an issue with workspace provisioning, authentication/token refresh, or tenant configuration?

At this point, it does not appear to be a browser or client-side issue.

Any guidance would be greatly appreciated, as this is preventing me from using the platform effectively.

Thanks in advance!

Answer 1

Estou enfrentando o mesmo problema apos 4 minutos so desconectado do azure databricks.

Answer 2

The behavior matches limitations and characteristics of Databricks Free Edition / trial workspaces rather than something that can be fixed with a setting in Microsoft Entra ID or the browser.

Key points from the documented behavior of Databricks Free Edition:

1. Nature of Free Edition / trial workspaces
   • Free Edition is a no‑cost, learning‑oriented offering and explicitly:
     • Does not include guaranteed reliability, support, or SLAs.
     • Is subject to a fair usage policy.
   • When fair usage limits are exceeded, Databricks can shut down compute resources for the rest of the day (and in extreme cases, the rest of the month). While this is described in terms of compute, the overall experience (including UI responsiveness and session stability) is not guaranteed to be stable or long‑lived.
   • Free Edition accounts are meant for non‑commercial use and have multiple administrative and security limitations (no account console, no private networking, limited auth methods). There is no mention of any configurable session timeout or token lifetime for the web UI in this SKU.
2. Why this can look like an aggressive “session timeout”
   • Because there is no SLA and no reliability guarantee, short or unstable sessions can manifest as:
     • Frequent disconnects from the workspace UI.
     • Notebook or compute sessions being torn down quickly when idle or under load.
   • The fair usage policy can also cause compute to be shut down when quotas are hit. From the user’s perspective, this may appear as:
     • Being forced to reconnect frequently.
     • Losing the interactive session after short periods of inactivity.
   • None of these behaviors are controlled by Microsoft Entra ID sign‑in policies in the Free Edition context; they are platform‑side behaviors of Databricks Free Edition.
3. Why this is unlikely to be an Entra ID / browser misconfiguration Based on the scenario:
   • Personal Microsoft account, not a corporate tenant (so no custom tenant‑wide conditional access or idle timeout policies in play).
   • Brand‑new Azure free trial subscription and Databricks workspace with default settings.
   • Reproduced across browsers (Chrome, Edge), with:
     • Extensions disabled.
     • Cookies enabled.
     • Incognito/private mode tested.
   • These steps already rule out the usual browser‑side causes (blocked cookies, extensions, or cached auth state issues).
   • The Databricks Free Edition documentation does not expose any setting for adjusting web session lifetime or token refresh behavior at the workspace level for this SKU.
4. What can realistically be done Within the documented constraints, there is no supported way to extend or tune the Databricks web session timeout for Free Edition / trial workspaces. The options are mainly around how the environment is used and, if necessary, moving to a more fully featured SKU:
   1. Minimize impact of short sessions while learning
   • Keep interactions short and frequent:
     • Run cells or small notebook sections regularly instead of leaving the UI idle for several minutes.
     • Save work frequently (for example, by committing code to a repo or ensuring notebooks are saved in the workspace) so that a forced reconnect doesn’t cause data loss.
   • Expect that compute may be stopped or recycled more aggressively than in paid tiers and plan exercises accordingly (e.g., smaller, self‑contained tasks).
   2. Use the full Databricks platform via trial if stability is critical
   • The documentation explicitly states that Free Edition is limited and that access to the full Databricks platform requires creating a new Databricks account via the Databricks free trial path. The full platform:
     • Is designed for production and long‑running workloads.
     • Is not subject to the same Free Edition constraints and fair‑use behaviors.
   • For someone blocked by 2–3 minute idle disconnects, the practical path is to:
     • Use the Azure free credit to back a standard Databricks workspace (not Free Edition), created via the Databricks trial flow.
     • Perform learning and labs there, where session behavior is more stable and aligned with production use.
   3. When to suspect something else
   • If the same account experiences similar 2–3 minute idle sign‑outs across other Azure services or SaaS apps, that would point more toward an account‑level or device‑level issue. However, the information provided and the Free Edition documentation strongly suggest this is specific to the Databricks Free Edition environment.
5. Summary
   • There is no documented configuration in Databricks Free Edition or a brand‑new Azure free trial workspace that allows increasing the Databricks web session timeout.
   • The behavior is consistent with the lack of reliability/SLA and fair‑usage constraints of Free Edition, not with a misconfigured Entra ID policy.
   • To avoid being blocked, the recommended approach is either to adapt usage patterns (short, frequent interactions) or to move to a standard Databricks workspace created via the Databricks free trial path, which is intended for more stable, continuous use.

---

References:

• Databricks Free Edition limitations