Hi @mouni2,

Based on your description, your original account was likely a Databricks Community Edition account. Community Edition was retired on January 1, 2026, and existing Community Edition workspaces are no longer accessible. This is the most common cause of the redirect loop you are experiencing: the workspace associated with your old account no longer exists, so the authentication flow completes but has nowhere to land, sending you back to the sign-in page.

The good news is that you have already confirmed the solution by creating a new Databricks Free Edition account that works correctly. Free Edition is the replacement for Community Edition and includes a number of capabilities that were not available in Community Edition, including:

- Serverless compute (no cluster startup wait times)
- Unity Catalog for data governance
- AI/BI Dashboards and Genie for natural-language data exploration
- Lakeflow for building data pipelines
- Built-in AI assistant for coding help

WHAT TO DO NEXT

Since your new Free Edition account is working, you can continue using that going forward. Unfortunately, Community Edition workspaces and any data or notebooks stored in them are not automatically migrated to Free Edition. If you had notebooks or data in your old Community Edition workspace, those would need to be recreated in the new environment.

If you had previously exported notebooks from your Community Edition workspace (as .dbc, .py, or .ipynb files), you can import them into your new Free Edition workspace using the Workspace browser: click the kebab menu (three dots) next to a folder and select "Import."

REFERENCES

- Databricks Free Edition overview: https://docs.databricks.com/aws/en/getting-started/free-edition
- Free Edition limitations: https://docs.databricks.com/aws/en/getting-started/free-edition-limitations
- Free Edition sign-up: https://login.databricks.com/?intent=CE_SIGN_UP

* This reply used an agent system I built to research and draft this response based on the wide set of documentation I have available and previous memory. I personally review the draft for any obvious issues and for monitoring system reliability and update it when I detect any drift, but there is still a small chance that something is inaccurate, especially if you are experimenting with brand new features.

If this answer resolves your question, could you mark it as "Accept as Solution"? That helps other users quickly find the correct fix.