Microsoft Purview Data Governance vs SAP Data Hub comparison

"Has a good interface and is reasonably priced."

"It gives you the opportunity to know your data and apply policies around it. If those policies are flouted, you can always track what's happening. You have options such as alerting the person who is committing that action, or you can take automatic action by blocking, for example, an email that is been sent externally. It's very useful."

"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."

"One important feature is data security, which both end users and the organization seek."

"The integration ecosystem with Microsoft Purview is the most valuable aspect."

"From my experience and customer feedback, one of the most valuable features of Microsoft Purview is ease of use, especially for content hosted within Microsoft 365 and Azure. I also like that the pricing model for the solution is reasonable."

"We can prevent, block, or audit however we like."

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

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

"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."

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

"There are some non-Microsoft file formats that are not supported."

"One drawback of Microsoft Purview, though it's beneficial and easy to use, is that when you start plugging in connectors for third-party sources when setting the solution up for data collection, it becomes a bit more tricky."

"Auto-tagging should be available at lower levels of licensing. Right now, a high level of licensing is needed for auto-tagging, and this feature should be made available at a lower license level."

"Running eDiscovery once a day takes quite a long time because it has to fetch your data. I also want the eDiscovery results to be improved. At the same time, I would like to get a centralized page where I could see records management applied to my Office 365 tenant visualized instead of waiting for a custom script to run through the complete tenant."

"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."

"One of the challenges is that Microsoft changes things so quickly that sometimes you're just playing catch-up, and sometimes these changes aren't communicated effectively."

"Purview's data loss prevention for macOS endpoints has some limitations, and the end-user experience of recovering from a failure is lacking."

"The company has everything offshore."

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

"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."

"The price is reasonable because most of our clients already have an E3 license, which makes implementation easy."

"It is cheap. It is based on consumption. If somebody wants to start using it, the price is definitely cheaper than a tool like Collibra."

"The pricing is reasonable because it's part of the 365 E3 or E5 license you buy."

"Some people find the tier licensing system complicated, but it offers a lot of value for money if we use the features."

"The pricing depends on the client's requirements and the number of applications."

"Purview is included in our Microsoft E5 licensing."

"People often and unjustly say that Microsoft product pricing is not in the scope of reality, that it's just too expensive at times. I do not feel that is the case at all... If I'm able to let go of 30 to 70 percent of my IT administration staff, that makes up for a lot of money."

"The categorization within the licensing could be improved. There are a lot of solutions within Microsoft Purview. If the licensing could be a bit clearer and the solutions could be better categorized according to function and across multiple environments, that would be excellent. The licensing is very confusing."

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