Scoping Microsoft Purview: Five Key Questions for a Successful Implementation (Part 2)

Scoping Microsoft Purview: Five Key Questions for a Successful Implementation (Part 2) 

Implementing Microsoft Purview is a critical step toward establishing robust data governance to enable better visibility and control over organizational data assets. However, due to the broad business areas and volume of stakeholders involved, many Purview projects are undersold in scope, leading to missed deadlines, unforeseen costs, and underwhelming adoption. Sullexis recommends a ‘start-small’ approach to implementing Purview, designed to help organizations accurately scope and deploy it from the start, building out domains one by one, eating this elephant one bite at a time!   

In this blog series, we are covering five key questions that will help to enable a well-planned and successful Purview deployment. In today’s blog we are discussing the second question: Does your governance plan extend to the domain and subdomain levels? 

 Does Your Governance Plan Extend to the Domain and Subdomain Levels? 

Effective data governance extends beyond high-level domains and requires careful consideration of subdomains and the people responsible for managing them. Understanding this hierarchy is key to ensuring proper oversight and adoption. Most organizations have defined data domains (e.g., Finance, HR, Sales), but subdomains (e.g., Payroll within HR, Accounts Payable within Finance) add depth and complexity.  

Let’s say you have a handle on your sub domains (good for you!). Have you thought about the impact on your organization when you start to build out governance working groups for each subdomain? We typically see working groups of anywhere from 5 to 20 people for each subdomain so if you have 30 subdomains you have A LOT of people who are going to have a hand in your governance strategy. 

Without clear domain and subdomain governance, Purview implementations often face scope creep, budget overruns, and poor adoption. By defining your governance structure at the domain and subdomain levels, you set the foundation for a scalable and structured Purview implementation. 

 * This visual shows the just how expansive a company’s domains and subdomains can be 

And remember, one bite at a time! We’ll cover this further in a future blog, but we strongly suggest starting with a single subdomain rather than trying to tackle everything at once.  

Can’t wait for more? Read the full blog.