---
title: "Discussion on \"Got Only a Databricks Workspace ID? Here's How to Find the Workspace Name\" | Hashnode"
description: "Discussion on \"Got Only a Databricks Workspace ID? Here's How to Find the Workspace Name\". A 5-step Databricks CLI method to turn a workspace ID into a workspace name, when the account console and Azure portal can’t find it."
url: "https://hashnode.com/posts/got-only-a-databricks-workspace-id-here-s-how-to-find-the-workspace-name/6ae7482147d72404f5150e10"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Got Only a Databricks Workspace ID? Here's How to Find the Workspace Name](https://muqtadirmalik.hashnode.dev/got-only-a-databricks-workspace-id-here-s-how-to-find-the-workspace-name?utm_source=hashnode&utm_medium=feed)

A 5-step Databricks CLI method to turn a workspace ID into a workspace name, when the account console and Azure portal can’t find it.

Nov 1 · 3 min read · muqtadirmalik.hashnode.dev  
Read the article

## Written by

[MUQTADIRMALIK QUAZI](https://hashnode.com/@muqtadirmalik)

@muqtadirmalik · Pune, India

  
[View profile](https://hashnode.com/@muqtadirmalik)

Platform Engineer writing about Databricks, Terraform & DevOps, plus honest thoughts on habits, mindset and the psychology of everyday life.

Hi, I’m MuqtadirMalik Quazi, Malik to most people. I’m a Platform Engineer who keeps large data platforms running. Day to day, I administer Azure Databricks at enterprise scale for a global financial services firm: the clusters, networking, identity and governance that data teams rely on without ever thinking about them. If everything works quietly, I’ve done my job. What I write about 🛠 Data platform engineering: Practical guides from an platform admin’s chair, not a data scientist’s. Azure Databricks administration, Unity Catalog, serverless networking, identity with Microsoft Entra ID, and running it all as code with Terraform and GitHub Actions. 🤖 AI governance for platform teams: AI is becoming a shared utility like compute, and someone has to decide who uses which model, how much and at what cost. I write about that side of AI: access, rate limits, budgets, audit. 🧠 Thoughts on mind and life: Short personal reflections on psychology, habits, focus and the quiet struggles of working in tech. Written for myself first, shared in case they help someone else. My background: 6+ years across data platforms and cloud infrastructure: from Hadoop and big data administration, through Azure and Oracle Cloud support, to platform engineering today. My stack: Azure, Databricks, Terraform, GitHub Actions, Linux, and a growing amount of Python. Why I write: I learn by explaining. Every post is something I either struggled with or wish someone had told me earlier. I keep it plain: real-world analogies, no unnecessary jargon. Let’s connect 💼 LinkedIn: https://www.linkedin.com/in/muqtadirmalik 🐦 X: @m.malikquazi ✉️ Substack: https://substack.com/@muqtadirmalikquazi Open to conversations about platform engineering, Databricks and remote or international opportunities.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.