We are looking into Purview for Data Catalog, Data Map capabilities. There were multiple threads ~1 year ago with less positive feedback.  Has things changed since then? Has anyone implemented in recent months and how was your experience. We are looking at data sources such as ADLS, Synapse, Power BI and number of SaaS softwares.

Hi Himanshu,
Although Purview has improved a lot in the last years, we continue to use Collibra as our central data platform to provide a more enhanced usability as well as an agnostic solution. In our particular case Purview would be more limited..

In our experience, Purview is great as long as you work within its limitations. If your use case is limited to security and compliance within the M365 ecosystem (Office, SharePoint Online, OneDrive, Exchange, Copilot) it is quite good. The integration, while not seamless, is as good as it gets. Compliance and security use cases such as DSPM for AI, DRM, Classification and labelling, records management, DLP rules, eDiscovery, Privacy SAR cases is where it shines. You still need to invest in building an operating model around Purview - monitoring alerts, tuning rules, managing sources etc.
As a broader data governance product - catalog, DQ, lineage - OR if your data estate is not wholly in the Microsoft space, I would not recommend Purview.

While running CoE for my previous company I have worked closely with MS Purview team to not only explore the existing capabilities of the product but also enhancing it's capabilities where required with our key use cases.   

It all depends what you want to achieve with the product. It has it's own challenges as Kash mentioned in his comment but at the same time if your Governance , DQ and Lineage use cases are at very high level and limited the product will work for you.

Last but not the least, Purview is mostly works well MS technology stack.  

Purview for Data Catalog is known to have gaps when connecting to technologies outside the Microsoft stack. The bigger challenge is business adoption, most non-technical users find the user experience and navigation less effective. While it works for basic data documentation and integrates well with the MSFT stack, its limitations show quickly when working with non-MSFT technologies. Many leaders pick Purview because of the lower price, but that often comes at the cost of not being able to realize positive ROI.

Here are a few common challenges I’ve heard from people using Purview:

1. Basic documentation, with lots of false positives as the product keeps changing
2. Limited support for non-Microsoft data sources, and weak lineage across systems
3. User experience doesn’t meet the needs of business users, layout isn’t fit for daily ops
4. Search isn’t intuitive, hard to connect and surface meaningful insights across data

Be mindful of its integration capabilities with other data platforms. If you need to build a complete end-to-end picture and establish data lineage across platforms like MDM, Data Modeling, etc., you might run into some roadblocks.