Microsoft Fabric

Microsoft Fabric Domains Explained: Architecture, Governance, and Workspace Assignment

What Microsoft Fabric domains and subdomains are, how they relate to workspaces and capacities, who can create and assign them, and how to design a domain strategy that delegates governance without pretending to be security.

By JaviPublished 16 min readIntermediate

On this page

A Fabric tenant with ten workspaces does not need domains. Everybody knows who owns what. A tenant with two hundred workspaces, five business units and a OneLake catalog that returns forty tables called customers does. At that size the questions change: which of these belongs to Finance? Who decides whether it can be certified? Which default label should it carry? Who do I ask?

Domains are Fabric’s answer to those questions. They are also one of the most misunderstood features in the platform, because the word suggests more than the feature does. A domain does not secure data, does not move it, and does not change which capacity pays for it.

The Fabric governance guide places domains in the wider governance picture, next to lineage, labels, endorsement and Purview. This article goes one level deeper on domains only: what they are, how they relate to workspaces and capacities, who can do what, how to assign existing workspaces, and how to design a domain strategy that survives contact with a real organization.

Every UI label and behaviour below was checked against the Microsoft Learn documentation listed in the references in November 2026. Fabric’s admin experience moves quickly, so check the current docs before you script anything.

Four concepts, four responsibilities

Most domain design mistakes come from mixing up four things that look related but answer different questions:

Concept Answers Who manages it What it changes
Domain Which business area does this data belong to? Who governs it? Fabric admin creates it; domain admins run it A metadata attribute on workspaces and their items; delegated settings; catalog filtering
Subdomain Which finer area inside that business? Fabric admin or the parent domain’s admins A finer grouping; general settings only
Workspace Where do items live, who can build and read them, what is deployed together? Workspace admins Items, roles, Git connection, deployment target
Capacity Which compute pays for and runs the work? Capacity admins Compute (CUs), region, throttling, billing

The key observation is that a workspace sits at the intersection of three independent hierarchies. It belongs to one domain (or none), it is hosted on one capacity, and it has its own role assignments. Changing one of these does not change the others.

  • OrganizationWho governs it
    1. Tenant
    2. MetadataDomainOwners, delegated settings
    3. OptionalSubdomain
    4. Workspace
    5. ItemsInherit the domain
  • ComputeWho runs and pays for it
    1. Tenant
    2. Compute and regionCapacityCUs, throttling, billing
    3. Workspace
    4. ItemsRun on that capacity
  • AccessWho can see or change it
    1. Workspace rolesAdmin, Member, Contributor, Viewer
    2. Item permissions
    3. Data-level securityOneLake, SQL, semantic model
Three independent hierarchies meet at the workspace. Read each column top to bottom. A workspace has one domain, one capacity and its own roles; assigning a domain changes none of the other two columns.

Storage is a fourth axis that domains do not touch either. Item data lives in OneLake under its workspace; assigning that workspace to a domain adds a domain attribute to the metadata. Nothing is copied, moved or re-partitioned.

What a domain actually is

Microsoft Learn describes a domain as a way of logically grouping all the data relevant to one area of the organization, most commonly a business department. You group data by associating workspaces with domains. When a workspace is associated with a domain, every item in it is associated too and receives a domain attribute in its metadata.

That association currently does three useful things:

  1. Discovery. In the OneLake catalog, users can select a domain to see only its items. A domain can have an image or colour that themes the catalog while it is selected, a small but effective reminder of whose data you are browsing.
  2. Delegated governance. Some tenant-level settings can be delegated to the domain, so each business area can configure them for its own needs (see Delegated governance below).
  3. Ownership. Each domain has named domain admins, ideally the business owners or experts for that area. That turns “who owns Finance data?” from tribal knowledge into a setting you can read, audit and query through the admin APIs.

A subdomain refines a domain: Finance might have Accounting, Treasury and Commission. Subdomains have important limits today: they do not have their own domain admins (they use the parent domain’s admins), and their settings pane offers general settings only, so delegated settings, default domain and contributor lists are configured on the parent domain.

Roles and permissions

Three roles are involved in creating and running domains. A fourth, workspace admin, matters because domain contributors must also hold it.

Role How you get it Can do Cannot do
Fabric admin (or higher) Tenant role Create, edit and delete domains; name domain admins and contributors; assign any workspace; see every domain on the Domains tab —
Domain admin Named by a Fabric admin in the domain’s Admins settings See and edit only their own domains on the Domains tab; edit the description and image; name contributors; create subdomains; assign workspaces; set a default domain; override delegated settings Delete the domain, rename it, or add or remove other domain admins
Domain contributor Named by a domain admin or Fabric admin in Contributors Assign workspaces they administer to the domain, or change their current assignment, from the workspace itself Open the Domains tab; assign workspaces where they are not workspace Admin
Workspace admin Admin role on the workspace Manage workspace settings and roles; reassign the workspace to another capacity Assign the workspace to a domain unless they are also a contributor of that domain

Three details are easy to miss:

  • Contributors default to everyone. The Contributors tab offers three choices: everyone in the organization (the default), specific users and groups, or only tenant admins and the domain’s admins. If you leave the default, any workspace admin can put their workspace in the domain. For a domain that will carry a default sensitivity label or certification rules, narrow it deliberately.
  • Contributor plus workspace Admin. A contributor can only assign workspaces in which they hold the workspace Admin role. Member is not enough.
  • Moving capacity is a different permission. Reassigning a workspace to another capacity requires the workspace admin role, the capacity admin role, or the capacity contributor role. Domain roles grant nothing on capacities.

When domains are worth it, and when they are not

Domains carry an ongoing cost: someone has to keep assignments current, name owners, and review delegated settings. They pay for themselves when they answer a question your organization is actually asking.

Domains are worthwhile when:

  • Several business areas publish data in the same tenant and consumers struggle to find the right source in the OneLake catalog.
  • Different areas need different governance: their own certifiers, their own certification documentation, a different default sensitivity label.
  • You are moving toward a federated or data mesh operating model, where business areas own their data products and the platform team owns the platform.
  • Auditors or data owners need a reliable answer to “which workspaces belong to this business area?”.
  • You want new workspaces created by a team to land in the right place automatically (the default domain feature).

Domains are unnecessary, or premature, when:

  • One team builds and consumes everything. Workspace names and roles already answer every ownership question.
  • The tenant is a proof of concept or a learning environment.
  • Nobody on the business side will accept the domain admin role. A domain without a business owner is just a folder with extra admin overhead.
  • The real problem is access or isolation. That is a workspace, item permission, OneLake security or capacity problem; a domain does not solve it.

A useful rule: create a domain when you can name its owner, at least one setting it will configure differently from the tenant, or a consumer group that will filter by it. If you can name none of the three, wait.

Example architecture: Sales, Finance, Tracking and Commission

Consider a distribution company with four data areas:

  • Sales owns orders, customers and pipeline data, consumed by sales managers and the executive dashboard.
  • Finance owns invoices, the general ledger and margin reporting. Its data is confidential and its numbers are audited.
  • Tracking owns shipment and delivery events from the logistics platform, landing in near real time.
  • Commission calculates sales representatives’ commissions from closed orders, delivery confirmations and finance rules. It feeds payroll.

The design question that matters is where Commission belongs. It consumes Sales data, but the people who decide whether a commission number is correct, and who answer for it to auditors and payroll, are in Finance. So Commission becomes a subdomain of Finance, not a fifth domain and not part of Sales. If the commission rules were owned by a Sales Operations team with its own certifiers, the right answer would be a subdomain of Sales instead. The data flow is identical; ownership decides.

  1. Fabric tenant
    • domain
      SalesSales data owner
      • sales-dev
      • sales-test
      • sales-prod
    • domain
      TrackingLogistics owner
      • tracking-ingest
      • tracking-prod
    • domain
      FinanceFinance controller
      • finance-dev
      • finance-prod
    • subdomain
      Under FinanceCommissionShares Finance's domain admins
      • commission-dev
      • commission-prod
Example domain layout for a distribution company. Three domains and one subdomain, each holding one workspace per environment. The branches are siblings, not a sequence; Commission sits under Finance because Finance owns the correctness of its numbers.

How the decisions break down:

Decision Choice in this example Why
Domains Sales, Finance, Tracking Three distinct owners with different rules
Subdomain Commission under Finance Finance owns correctness; inherits Finance’s domain admins
Workspaces One per environment per area Environments need different roles and deployment targets
Capacities cap-prod and cap-nonprod, shared by all domains Isolation by environment, not by department; capacity is a cost and workload decision
Default label Finance domain sets Confidential Delegated setting; applies to new items, and to unlabeled items when they are updated
Certification Finance and Sales each name their own certifiers Delegated certification settings per domain

Domains do not grant cross-domain access

The Commission calculation needs Sales Gold orders and Tracking delivery confirmations. Being in the Finance domain gives it neither. Access is set up exactly as it would be with no domains at all:

    • Sales domainGold orderssales-prod
    • Tracking domainDelivery eventstracking-prod
    • Finance domainCommission rulesfinance-prod
  1. shortcut + granted read
    Commission Lakehousecommission-prod
  2. Commission statementsCertified by Finance certifiers
Commission reads other domains through explicit access. Each input is an access grant made by the producing workspace's owners, through workspace roles, item permissions or OneLake security. Domain membership grants nothing.

The domain structure still helps: everyone can see that the Gold orders table belongs to Sales, the Sales domain admins are the people to ask for access, and lineage across workspaces shows Finance which Sales items its numbers depend on. The security architecture guide covers how to grant that cross-workspace read safely.

Why not one capacity per domain?

Capacity-per-department is a valid pattern, especially for chargeback, and Fabric supports it well: it is exactly what Assign by capacity is built for. But it is a cost and workload-isolation decision, not a governance one. In this example a single production capacity serves all three domains because the workloads are small and the company wants Dev experiments isolated from production more than it wants Finance isolated from Sales. The capacity guide explains when isolation pays off. Whatever you choose, the domain structure does not depend on it.

Step by step: create domains and assign existing workspaces

The steps below follow the current Microsoft Learn procedure. No screenshots are included: the article describes the documented UI labels rather than a captured tenant.

  1. 1Plan ownersOne accountable owner per domain
  2. 2Create domainsFabric admin
  3. 3Create subdomainsOnly where a finer grouping is needed
  4. 4Name admins and contributors
  5. 5Assign workspacesName, admin, capacity or workspace settings
  6. 6Delegate settingsCertification, default label
  7. 7Verify in the catalog
Rolling out domains in an existing tenant. Plan ownership first, create structure second, assign workspaces third, delegate settings last.

1. Create a domain (Fabric admin)

  1. Sign in to Fabric with a Fabric admin account.
  2. Open the OneLake catalog, then select Govern > Domains.
  3. On the Domains tab, select Create new domain.
  4. In the New domain dialog, enter a name (required) and, optionally, the domain admins. You can add admins later.
  5. Select Create.

Repeat for Sales, Finance and Tracking.

2. Create a subdomain (Fabric admin or domain admin)

  1. Open the Finance domain and select New subdomain.
  2. In the New subdomain dialog, enter Commission and select Create.

Remember that Commission now shares Finance’s domain admins.

3. Configure admins and contributors

Open the domain and select Domain settings, or hover over the domain on the Domains tab, select More options (…) and choose Settings. The Domain settings side pane has these tabs: General settings, Image, Admins, Contributors, Default domain and Delegated settings.

  • Admins (Fabric admin only): add the business owners, preferably as a security group. Select Apply.
  • Contributors (Fabric admin or domain admin): choose everyone in the organization, specific users or groups, or only tenant admins and this domain’s admins. Select Apply.
  • Image: select Select an image and choose an image or colour for the catalog.

4. Assign existing workspaces (Fabric admin or domain admin)

  1. Open the domain or subdomain page and select Assign workspaces.
  2. In the Assign workspaces to this domain side pane, choose one of the three methods described in the next section.
  3. Confirm. If a workspace already belongs to another domain, a warning appears and you can continue to override it, as long as the tenant setting described below allows it.

To remove workspaces, select them in the domain’s workspace list and select Unassign.

5. Or assign from the workspace (domain contributor)

A domain contributor who is Admin of a workspace assigns it from the workspace side instead: in the Create a workspace pane when creating it, or later in the workspace’s settings. Contributors cannot open the Domains tab.

6. Verify

Open the OneLake catalog, select the domain in the domain filter and check that the expected items appear. The domain page in Govern > Domains lists the assigned workspaces, and the admin REST API’s List Domain Workspaces operation gives the same answer in a form you can schedule and compare.

Workspace assignment methods

Fabric offers several ways to associate workspaces with a domain. They differ in who can use them and, importantly, in whether they affect workspaces created later.

Method Who What it assigns Future workspaces?
Assign by workspace name Fabric admin, domain admin The workspaces you search for and select No, one-off
Assign by workspace admin Fabric admin, domain admin Every workspace where the selected users or security groups are admins, excluding My workspaces No, existing workspaces only
Assign by capacity Fabric admin, domain admin Every workspace on the selected capacities, excluding My workspaces No, existing workspaces only
Workspace creation or settings Domain contributor who is workspace Admin That one workspace Applies as the workspace is created
Default domain Fabric admin, domain admin Unassigned workspaces whose admin is a listed user or group member, then every new workspace they create Yes
Admin REST API Admin API caller (check each operation’s required role) By workspace IDs, by principals or by capacities No, but schedulable

By workspace name

Search, select several workspaces at once, confirm. This is the precise method and works best with a naming convention such as finance-commission-prod. An icon marks workspaces already associated with another domain. The workspace guide suggests a naming convention that encodes the domain and environment.

By workspace admin

Select users or security groups; every workspace they administer is assigned. This is efficient when ownership already maps to teams, for example a sg-finance-data-admins group. It is also blunt: a person who administers workspaces for two departments drags all of them into one domain. Check the resulting list before you move on.

By capacity

Select one or more capacities; every workspace on them is assigned. This fits organizations that already run a dedicated capacity per department. It is the wrong tool when capacities are split by environment, as in the example above: assigning cap-prod to Finance would put Sales Prod into Finance.

Default domain: the method that keeps up

The Default domain tab lets a Fabric admin or domain admin list users and security groups. Fabric then scans existing workspaces: an unassigned workspace whose admin is in the list joins the domain, while one already assigned keeps its domain. From then on, every new workspace a listed user creates is assigned to the default domain. Listed users generally become domain contributors for those workspaces.

That makes the default domain the closest thing to “keep this domain current” without a script. Pair it with a security group per business area, and new workspaces arrive in the right domain on creation.

The override tenant setting (preview)

Allow tenant and domain admins to override workspace assignments (preview) lives under OneLake catalog > Govern > Configurations > Tenant settings > Domain management settings. It is enabled by default. When disabled, Fabric and domain admins cannot move a workspace that already has a domain to another domain, and the domain REST APIs respect the same setting. Disable it once your domain map is stable if you want accidental bulk reassignments to fail instead of succeed.

Automating with the admin REST API

Most UI actions are also available in the Fabric Admin REST API for domains: create, update, delete and list domains; assign workspaces by IDs, by principals or by capacities; unassign workspaces; bulk-assign or unassign domain admins and contributors; and sync role assignments to subdomains. Domain create, edit and delete activities are recorded in the Fabric audit log. A scheduled job that compares List Domain Workspaces against your naming convention is a simple way to detect drift.

Delegated governance: what a domain can decide

Domains become more than a catalog filter when tenant admins delegate settings to them. Two delegated settings are documented today.

Certification. Under Delegated settings, expand the certification section and select Override tenant admin selection. The domain can then enable or disable certification for its items, name its own certifiers, and link to its own certification documentation. This is the most practical use of domains: Finance certifiers certify the Finance and Commission semantic models, Sales certifiers certify Sales, and neither needs the other’s approval.

Default sensitivity label (preview). If the tenant setting Domain admins can set default sensitivity labels for their domains (preview) is enabled, a domain admin can open Delegated settings > Information protection and choose a label in Set a default label for this domain. The label is applied when a new item is created in a workspace of the domain, and when an existing unlabeled item is updated and saved. An existing label is never overwritten if it was applied manually; an automatic or policy default label is overwritten only when it has lower priority. Deployment pipelines and Git integration are not currently supported by this feature, so items arriving through CI/CD need another labeling path.

Two practical consequences:

  • Delegation is opt-in from the top. A domain can only override what the tenant has made delegable. Domain admins cannot invent new controls.
  • Delegation needs an owner who will act. A domain admin who never reviews certifiers or labels gives you the overhead of domains with none of the governance.

Ownership and discovery

Domains work when they are anchored in people.

  • One accountable owner per domain. Make the domain admins a security group led by the business owner, not the platform engineer who happened to create it. Microsoft’s planning guidance recommends involving the centre of excellence, business and technical architects, and security and compliance officers in the design.
  • Platform team as Fabric admin, not domain admin. The platform team creates domains and sets tenant policy; the business governs inside its domain.
  • Describe the domain. The description in General settings is where you say what belongs in the domain and who to contact. Domain admins can edit it.
  • Use the image. A distinct domain image in the catalog is a cheap way to reduce “I was looking at the wrong Finance table” mistakes.
  • Combine with endorsement. Domains say whose data it is; endorsement says how much to trust it. A consumer filtering the catalog by Finance and then by Certified is asking the right two questions. The governance guide explains the trust model.

Common design mistakes

  • Treating a domain as a security boundary. Putting HR workspaces in an HR domain hides nothing. Access is controlled by workspace roles, item permissions and data-level security. Review those, not the domain list.
  • Expecting a domain to move or isolate compute. Domain assignment does not change a workspace’s capacity, region or OneLake location. If Finance needs isolated compute, move its workspaces to a separate capacity.
  • Mapping domains to capacities by reflex. When capacities are split by environment, Assign by capacity puts every department’s production workspaces into one domain.
  • Mapping domains to environments. “Dev”, “Test” and “Prod” are not business areas. Environments are workspaces; the same domain contains all three.
  • Too many domains, too early. Twenty domains with no owners make the catalog filter longer, not more useful. Start with the areas that have owners and differing rules.
  • Using subdomains for things that need their own admins. Subdomains inherit the parent’s admins and have general settings only. If an area needs its own certifiers or default label, it is a domain.
  • Leaving contributors as “everyone” on a governed domain. Any workspace admin can then pull a workspace into the domain and inherit its default label and certifiers.
  • Running bulk assignment once and calling it done. Bulk methods do not affect future workspaces. Use default domains, a contributor process or a scheduled API check.
  • Ignoring the override setting. With the default override behaviour, a careless bulk assignment can silently reshuffle workspaces that were placed correctly.

A checklist for your domain strategy

Use this before creating the first domain, and again at each quarterly review.

Scope

  • Need: we can name, for each proposed domain, an owner, a setting it will configure differently, or a consumer group that will filter by it.
  • Structure: domains follow how the business is organized (function, product, process, region, or a mix), not how capacities or environments are split.
  • Subdomains: used only for finer grouping that shares the parent’s admins and settings.

Ownership

  • Owners: every domain has domain admins, assigned as a security group with a named business lead.
  • Contributors: each domain has a deliberate contributor choice; “everyone” is a decision, not a default.
  • Description: every domain says what belongs in it and who to contact.

Assignment

  • Naming: workspace names encode domain and environment, so assignment by name and drift checks are easy.
  • Method: the bulk method chosen (name, admin, capacity) matches how the tenant is actually organized.
  • New workspaces: default domains or a contributor process place new workspaces automatically.
  • Override: the override tenant setting is set deliberately once the domain map is stable.
  • Drift: unassigned workspaces are reviewed on a schedule, by API or the Domains page.

Governance

  • Certification: each domain that certifies has its own certifiers and documentation URL.
  • Labels: default sensitivity labels are set where required, with a separate path for items deployed through Git or pipelines.
  • Access: access is still designed per workspace and item; nobody believes the domain secures anything.
  • Capacity: capacity assignment is decided on cost and workload grounds, independently of domains.

Conclusion

Domains are the organizational layer of a Fabric tenant. They put a business owner’s name on a group of workspaces, make the OneLake catalog navigable by business area, and let each area run its own certification and default labeling. They are cheap to create and easy to misuse.

Keep three facts in mind and most of the design follows. A domain is metadata, so it does not grant access, move storage or change compute. Ownership decides the structure, not data flow, capacity or environment. And bulk assignment is a snapshot, so the strategy needs a mechanism that keeps up with new workspaces.

More guides on ownership, access and trust are collected in the Data Governance & Security hub.

References

Tags

  • Microsoft Fabric
  • Data Governance
  • Fabric Workspace
  • Capacity
  • Data Architecture