What is our primary use case?
Our main use case for Microsoft Purview Communication Compliance is to check data quality with incoming data. For example, if a customer has different kinds of files, they want to know what kind of data needs to be massaged, whether the file is in a good format or bad format, and whether the file contains all the columns required. We perform data quality checks with incoming data, including null checks in the file or null checks in the key table, and we verify date formats. Additionally, we can add business context to that data. For example, if you take a customer and a company with multiple departments, the definition of customer varies. In one department, we might call it a customer ID, while in another department we might call it a customer code. Microsoft Purview Communication Compliance will provide business context to show that overall it is a customer ID at the organizational level.
What is most valuable?
The features I use most in Microsoft Purview Communication Compliance are lineage and data quality.
Microsoft Purview Communication Compliance has impacted my organization positively. It is a good tool that provides an end-to-end business view for a particular organization.
What needs improvement?
The biggest friction point or frustration I have encountered with Microsoft Purview Communication Compliance is cost-wise it is acceptable, but sometimes unexpected errors will occur, though this happens very rarely.
There are features I wish Microsoft Purview Communication Compliance had that it does not provide today. Enterprise-level lineage is one such feature. As of now, if Microsoft were to provide this tool for free when you buy Microsoft Fabric, I feel that would be better. This would also result in lower license costs.
I do not have any changes I would make to Microsoft Purview Communication Compliance at this time.
What do I think about the stability of the solution?
We need formal training for Microsoft Purview Communication Compliance because only people with architect-level knowledge can implement it effectively, as they have an understanding of the business context.
Which solution did I use previously and why did I switch?
Before I adopted Microsoft Purview Communication Compliance, I had not used any tool for this purpose. The previous approach was manual mapping done in Excel sheets. We had to compare the columns and compare the data, which was a tedious task.
How was the initial setup?
When I first implemented Microsoft Purview Communication Compliance, it got up and running in seconds.
What was our ROI?
I can say that with Microsoft Purview Communication Compliance, if you have everything established, my team can save at least eight hours.
Which other solutions did I evaluate?
When evaluating options, I recommend Microsoft Purview Communication Compliance. There are other lineage tools in the market, but I have not worked with them. However, I recommend Microsoft Purview Communication Compliance whenever any company wants to implement a data quality framework.
I chose Microsoft Purview Communication Compliance specifically over those alternatives because my client is on an Azure-based platform, making it easy for them to onboard this tool. Since they are already in Azure Cloud, they do not need to buy another license and can use the Microsoft product instead of going with other hyperscalers such as Google Cloud Platform or Amazon Web Services.
What other advice do I have?
The scope of Microsoft Purview Communication Compliance is a team-wide workflow.
The first thing I do when I open Microsoft Purview Communication Compliance is check how many workspaces are available under it and which departments are involved. I can see the different domains available and view a particular workspace lineage within that. We add rules for each column coming from the source, and this is mostly how we use it.
Adoption of Microsoft Purview Communication Compliance has involved both power users and casual users. There is a hierarchy that allows us to maintain different roles based on who needs larger access levels, and we can maintain security in Microsoft Purview Communication Compliance by controlling who should access it and who should not.
There are features that were launched during implementation of Microsoft Purview Communication Compliance that I am not actually using. Quite a lot of features have been released, but I have not used them, though they are truly useful.
Microsoft Purview Communication Compliance has changed how my team collaborates; we now collaborate effectively.
My advice to someone considering Microsoft Purview Communication Compliance who has a similar workflow to mine is that we have covered our needs quite thoroughly. I would rate this product an eight out of ten.
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Microsoft Azure