A branch curator without domain-admin rights tries to assign their branch's Lakehouse workspace to the network's shared "Collections" domain in the admin portal, but the option is unavailable to them. Why?
Select an answer to reveal the explanation.
Short Explanation
Domains work a bit like a gated group -- you need to be a group admin, or a tenant-level admin, to add a member to it. A curator without that domain-admin role simply doesn't have the key to add their workspace to the group, regardless of how good their data is.
Full Explanation
Assigning a workspace to a Fabric domain is a permission gated to domain admins for that specific domain, or to Fabric admins at the tenant level -- a workspace member or contributor without that role cannot make the assignment, which matches the curator's situation exactly. Capacity assignment is a separate concern entirely: a workspace can sit on any capacity, licensed or trial, independent of whether it belongs to a domain, so a missing capacity assignment would not block a domain assignment attempt for this reason. Item endorsement affects how consumers discover and trust content, not who can group workspaces under a domain. OneLake storage limits affect how much data a workspace can hold, not domain-assignment permissions. A scope note: even a Fabric admin acting on the curator's behalf would need to do it through the admin portal, not the workspace's own settings pane. To confirm, have someone with the domain-admin or Fabric-admin role check the domain's assigned contributors list and add the curator's workspace there.