A unified data governance solution that helps manage, protect, and discover data across your organization
Hello Sam,
The behavior you are seeing is expected with the current Governance Domain hierarchy model.
A parent Governance Domain does not automatically inherit or roll up the Data Products, Glossary Terms, or other catalog assets assigned to its child Governance Domains. The hierarchy primarily provides an organizational structure rather than an inherited asset-membership model.
For organizations using several levels of Governance Domains, I would recommend keeping the hierarchy relatively shallow where possible and assigning assets to the Governance Domain in which they are actually governed. For discovery, users can then navigate to the relevant child domain rather than relying on the parent domain to display all descendant assets.
For example:
Enterprise
└── Finance
├── Accounts Payable
├── Accounts Receivable
└── Financial Reporting
A Data Product governed by Accounts Payable should remain associated with that domain rather than being duplicated in Finance simply to make it discoverable from the parent.
If parent-level discovery of all descendant assets is an important requirement, I would recommend submitting or upvoting this as a Microsoft Purview product feature request, specifically requesting descendant-asset roll-up for Governance Domains. This would also allow the product team to distinguish between simple navigation and actual inherited governance ownership.
Until such functionality is available, avoiding unnecessarily deep hierarchies and using consistent asset naming, descriptions, glossary relationships, and other catalog metadata can help compensate for the lack of automatic roll-up.
I would not recommend manually duplicating the same business concepts across parent and child domains, as that can introduce ownership and governance ambiguity.