Microsoft Purview Data Governance vs SAP Data Hub comparison

"The data protection feature is vital as it controls who can access data when it moves out of our protected boundary."

"One of the best features is the classification rules, especially the scan rule sets. They are really useful, especially when we need to understand the current data the company has to ensure that all the problematic data can be put under someone's responsibility."

"The documentation is very exhaustive. Anyone can go ahead and try different use cases."

"The most valuable feature is the tracking activity and device onboarding."

"It is pretty early, but the decision to go with this investment was largely driven by the simplification of our information security technology management stack. That is the primary objective. Once you simplify and you have a connected structure, it allows for faster adoption there. It also gives us additional capabilities as we go on using the technology that we are familiar with, and we do not have to depend on outside parties to come in and tell us how to do certain things."

"It starts off with records management, insider risk management, and information protection. And there is the discovery of the clouds, and we can get analytics on that as well, so that we know which user is using which cloud application and for how much time. The Activity explorer tells us which user was transferring out what data at what moment and on which device, including the serial number."

"Microsoft Purview's most valuable feature is its ability to identify content across a number of prescribed regulatory frameworks, including Microsoft, GDPR, PII, and UCC Financial."

"My favorite Purview feature is auto-scanning. Once we set up Purview, we can automatically scan multiple data sources when new data comes into specific databases, like SQL and Oracle. We don't need to rediscover the new data or do anything manually because it automatically happens."

"Its connection to on-premise products is the most valuable. We mostly use the on-premise connection, which is seamless. This is what we prefer in this solution over other solutions. We are using it the most for the orchestration where the data is coming from different categories. Its other features are very much similar to what they are giving us in open source. Their push-down approach is the most advantageous, where they push most of the processing on to the same data source. This means that they have a serverless kind of thing, and they don't process the data inside a product such as Data Hub. They process the data from where the data is coming out. If it is coming from HANA, to capture the data or process it for analytics, orchestration, or management, they go to the HANA database and give it out. They don't process it on Data Hub. This push-down approach increases the processing speed a little bit because the data is processed where it is sitting. That's the best part and an advantage. I have used another product where they used to capture the data first and then they used to process it and give it. In Data Hub, it is in reverse. They process it first and give it, and then they put their own manipulations. They lead in terms of business functions. No other solution has business functions already implemented to perform business analysis. They have a lot of prebuilt business functions for machine learning and orchestration, which we can use directly to get an analysis out from the existing data. Most of the data is sitting as enterprise data there. That's a major advantage that they have."

"SAP is one of the most seamless ERPs that have integrated SAP archiving within Excel. I have not seen this with any other database."

"The most valuable feature is the S/4HANA 1909 On-Premise"

"One area for improvement is better documentation on what is working and what is not, as well as what features are allowed depending on your licensing model. It's essential to know if a feature isn't working due to missing licenses."

"Non-Microsoft use cases are not very high. It's limited for now."

"There are differences when looking at an incident in the M365 portal versus Purview, and the main one is the advanced hunting. In the M365 portal, you can write KQL queries and fetch data. If that was available in Purview, it would be very good."

"There are negatives to the compliance aspect of Purview in that you get a lot of false positives with some of the native scanning and rules in the platform. A lot of them need tweaking to get a more realistic handle on what data there is."

"While Purview's data connector platform can ingest information from non-Microsoft data sources, it is slow to do so and the information may become outdated."

"I would like to have complete video documentation for training."

"There should be more clarity about the costing, particularly how the cost is calculated, especially when utilizing health reports and quality features."

"Setting up Purview in a production tenant proved challenging due to a lack of clear documentation on permission requirements."

"In 2018, connecting it to outside sources, such as IoT products or IoT-enabled big data Hadoop, was a little complex. It was not smooth at the beginning. It was unstable. It took a lot of time for the initial data load. Sometimes, the connection broke, and we had to restart the process, which was a major issue, but they might have improved it now. It is very smooth with SAP HANA on-premise system, SAP Cloud Platform, and SAP Analytics Cloud. It could be because these are their own products, and they know how to integrate them. With Hadoop, they might have used open-source technologies, and that's why it was breaking at that time. They are providing less embedded integration because they want us to use their other products. For example, they don't want to go and remove SAP Analytics Cloud and put everything in Data Hub. They want us to use SAP Analytics Cloud somewhere else and not inside the Data Hub. On the integration part, it lacks real-time analytics, and it is slow. They should embed the SAP Analytics Cloud inside Data Hub or support some kind of analysis. They do provide some analysis, but it is not extensive. They are moreover open source. So, we need a lot of developers or data scientists to go in and implement Python algorithms. It would be better if they can provide their own existing algorithms and give some connections and drop-down menus to go and just configure those. It will make things really quick by increasing the embedded integrations. It will also improve the process efficiency and processing power. Its performance needs improvement. It is a little slow. It is not the best in the market, and there are other products that are much better than this. In terms of technology and performance, it is a little slow as compared to Microsoft and other data orchestration products. I haven't used other products, but I have read about those products, their settings, and the milliseconds that they do. In Azure Purview, they say that they can copy, manage, or transform the data within milliseconds. They say that they can transform 100 gigabytes of data within three to five seconds, which is something SAP cannot do. It generally takes a lot of time to process that much amount of data. However, I have never tested out Azure."

"Nowadays there are some inconsistencies in data bases, however, they upgrade and release the versions to market."

"The company has everything offshore."

"Currently, the licensing differs for the governance side compared to the risk and compliance side."

"Aside from the complexity of the pricing model, the price itself is realistic. Features like AI components and automatic classification require additional licenses. Still, anyone can start using Purview with a basic E3 license if they're using Microsoft 365 and grow with additional licenses as needed. Overall, we're satisfied with the price."

"Microsoft Purview is priced in the middle. It isn't the cheapest, but it isn't the most expensive. It's affordable compared to other public cloud services."

"Microsoft Purview Data Loss Prevention is not cheap."

"Microsoft Purview is a subscription-based service, so we need either an E3 or E5 license to use it."

"Microsoft Purview requires a Microsoft 365 license and is included with an E5 license."

"The pricing is moderate. It's not too expensive, but it's not the most competitive."

"I would rate the cost of Microsoft Purview a six out of ten with ten being the most expensive."

"The Cloud is very expensive, but SAP HANA previous service is okay."