Forum Discussion
Purview Unified Catalogue Gov Domains Numeric Prefixing
Has Anyone Tried Numeric Prefixing for Governance Domains in Purview?
Context:
We introduced a structured numeric prefixing system for governance domains in Microsoft Purview to make hierarchical sorting more intuitive.
What we did:
Parent domains use a base prefix ending in .00 (e.g., 02.00 Group).
Child domains are numbered sequentially (e.g., 02.01 Directorate, 02.01.01 Team).
Why:
Purview sorts domains alphabetically, which caused child domains (e.g., 02.01) to appear above their parent (02 Group). Adding .00 ensures parents always sort before children, creating a clear hierarchy.
How it works:
All already have 01.00-
Top-level groups: 02.00
Directorates: 02.01, 02.02
Teams/Units: 02.01.01
This approach guarantees correct sorting, clear hierarchy, and scalability for future additions?
Question for the community:
Has anyone else implemented a similar numeric prefixing approach in Purview?
Do you think this is a good idea for maintaining clarity and scalability?
Any alternative strategies you’ve found effective?
Hello sashakorniakUK,
This is great strategy for naming the domains and helps identifying the parent/child relationship seamlessly. However, if domain names are used for search and filtering, to make domains meaningful and easy to find, include descriptive names after the numeric prefix, like<Prefix>.<MeaningfulName>[.<Environment>]
(Eg: 01.00.HR, 01.01.HRdev, 01.01.01.HRdev.Payroll, etc.,)
Hope this helps!
Please mark as solution, if you find the answer helpful. This will assist others in the community who encounter a similar issue, enabling them to quickly find the solution and benefit from the guidance provided
1 Reply
Prathista IlangoMicrosoft
Hello sashakorniakUK,
This is great strategy for naming the domains and helps identifying the parent/child relationship seamlessly. However, if domain names are used for search and filtering, to make domains meaningful and easy to find, include descriptive names after the numeric prefix, like<Prefix>.<MeaningfulName>[.<Environment>]
(Eg: 01.00.HR, 01.01.HRdev, 01.01.01.HRdev.Payroll, etc.,)
Hope this helps!
Please mark as solution, if you find the answer helpful. This will assist others in the community who encounter a similar issue, enabling them to quickly find the solution and benefit from the guidance provided