Senior technical consultant at a computer software company with 501-1,000 employees
Consultant
Top 20
2023-11-28T10:01:00Z
Nov 28, 2023
The Endpoint DLP engine has a lot of delays. The just-in-time protection feature does not always work as expected, mainly when working with network files in a more classic environment.
I currently work in the financial domain, and we have very strict regulations from national banks and the group side. Domain-related improvements could be really useful for organizations and banks. For example, sensitive information types are the basic level of information protection, similar to the Purview model. We start with creating or duplicating sensitive insights and editing them. I am talking about more sensitive information types that align with European regulations, especially in the financial sector. Having more variety would be beneficial. All of the EU considers sensitive information types in finance, but we need more variety, especially as a Ukrainian company. We face a lack of attention to our region, despite having the same strict regulations as EU companies. One point of improvement is related to organization and language issues. For instance, we use different sensitive information types for France, the UK, and other countries where we have offices. Unfortunately, Microsoft doesn't support the Ukrainian language, unlike Chinese and Japanese languages, which have deeper layers of understanding of information. It would be helpful to add support for Ukrainian. However, I understand that we are essentially bilingual, using both English and Ukrainian in our companies, and we are a minority in terms of languages. Other solutions, like ERP systems, offer localization for Ukraine and have partnerships with companies. Microsoft 365 also supports the Ukrainian language from a user perspective. However, unfortunately, Defender and Azure lack deeper settings. They do not provide language options beyond the ones already available, so our language option is missing. Purview includes sensitive info types covering a wide range of languages and country specifications. For instance, it includes passport numbers for Ukraine, but we also need a sensitive input type for our tax numbers. Currently, there is no option for our tax numbers, which forces us to duplicate the data. In contrast, they include all sorts of options such as driver's license numbers and insurance policy numbers for EU companies. It would be beneficial to have those presets available for us as well.
Solution Architect : Corporate wide systems at a healthcare company with 10,001+ employees
Real User
Top 5
2023-07-11T17:12:00Z
Jul 11, 2023
A site can have different containers where you store data. We have always wanted to apply compliance, labels, and policies at the container level, rather than to an outer shell or at the site level. That is something we have been looking forward to and I believe Microsoft is already planning something like that.
Cyber Security Engineer at a manufacturing company with 10,001+ employees
Real User
Top 20
2022-11-11T20:15:00Z
Nov 11, 2022
There is no AIP for Linux systems. That's a setback. Another thing it's lacking is libraries to work with Python. It has libraries for C# and C++, for example, but not for Python and, these days, Python is very useful. Power Automate can be improved as well. You can do plenty of things with it but it still doesn't do everything that you have in a full development language. It doesn't have that flexibility. I would also like more integrations in Power Automate. Because so many things are a premium with Power Automate, you cannot do everything. There are a bunch of integrations that you have to pay more to use. That's not very good.
Lead Cloud Solution Architect at a energy/utilities company with 51-200 employees
Real User
Top 10
2022-10-09T18:47:00Z
Oct 9, 2022
I would like Microsoft Purview Data Loss Prevention to be on the source code or SQL databases. It is difficult to do classification and labeling when you have a third-party source code or a third-party Oracle database. It is seamless when it comes to Microsoft documents but is not so with third-party source codes. Microsoft needs to work on it a little bit more. Everybody wants information protection, but not all of them can afford the M365 license. I would like Purview to be a standalone product or solution.
Learn what your peers think about Microsoft Purview Data Loss Prevention. Get advice and tips from experienced pros sharing their opinions. Updated: April 2024.
VM people say you cannot use just one product; you need multiple products across the network and you have to deploy to the backups. The DLP could always be better. Overall, they should make their Hyper-V and the clustering more stable. VMware offers very good clustering, for example. Microsoft needs to improve a lot in terms of stability. Technical support is awful.
There is a lot of ambiguity when you are setting up labels, such as sensitive information labels. It is a little daunting at first if you don't have prior knowledge, and there is a little bit of a learning curve for setting up the labels. Some of the setup wizards could be more helpful from an AI perspective. They can streamline the setup through more AI technologies so that you don't have to jump through so many hoops and different menus and dropdowns. It would be useful to have a setup wizard that is more hands-off and engaging for setting up the information type labels. If you tell them this is what we're trying to protect, it should basically start to lead you down that path of best practices. Such a feature would be great.
At Microsoft, our mission is to empower every person and every organization on the planet to achieve more. Our mission is grounded in both the world in which we live and the future we strive to create. Today, we live in a mobile-first, cloud-first world, and the transformation we are driving across our businesses is designed to enable Microsoft and our customers to thrive in this world.
The Endpoint DLP engine has a lot of delays. The just-in-time protection feature does not always work as expected, mainly when working with network files in a more classic environment.
I currently work in the financial domain, and we have very strict regulations from national banks and the group side. Domain-related improvements could be really useful for organizations and banks. For example, sensitive information types are the basic level of information protection, similar to the Purview model. We start with creating or duplicating sensitive insights and editing them. I am talking about more sensitive information types that align with European regulations, especially in the financial sector. Having more variety would be beneficial. All of the EU considers sensitive information types in finance, but we need more variety, especially as a Ukrainian company. We face a lack of attention to our region, despite having the same strict regulations as EU companies. One point of improvement is related to organization and language issues. For instance, we use different sensitive information types for France, the UK, and other countries where we have offices. Unfortunately, Microsoft doesn't support the Ukrainian language, unlike Chinese and Japanese languages, which have deeper layers of understanding of information. It would be helpful to add support for Ukrainian. However, I understand that we are essentially bilingual, using both English and Ukrainian in our companies, and we are a minority in terms of languages. Other solutions, like ERP systems, offer localization for Ukraine and have partnerships with companies. Microsoft 365 also supports the Ukrainian language from a user perspective. However, unfortunately, Defender and Azure lack deeper settings. They do not provide language options beyond the ones already available, so our language option is missing. Purview includes sensitive info types covering a wide range of languages and country specifications. For instance, it includes passport numbers for Ukraine, but we also need a sensitive input type for our tax numbers. Currently, there is no option for our tax numbers, which forces us to duplicate the data. In contrast, they include all sorts of options such as driver's license numbers and insurance policy numbers for EU companies. It would be beneficial to have those presets available for us as well.
A site can have different containers where you store data. We have always wanted to apply compliance, labels, and policies at the container level, rather than to an outer shell or at the site level. That is something we have been looking forward to and I believe Microsoft is already planning something like that.
The solution should provide better integration with other systems.
There is no AIP for Linux systems. That's a setback. Another thing it's lacking is libraries to work with Python. It has libraries for C# and C++, for example, but not for Python and, these days, Python is very useful. Power Automate can be improved as well. You can do plenty of things with it but it still doesn't do everything that you have in a full development language. It doesn't have that flexibility. I would also like more integrations in Power Automate. Because so many things are a premium with Power Automate, you cannot do everything. There are a bunch of integrations that you have to pay more to use. That's not very good.
I would like Microsoft Purview Data Loss Prevention to be on the source code or SQL databases. It is difficult to do classification and labeling when you have a third-party source code or a third-party Oracle database. It is seamless when it comes to Microsoft documents but is not so with third-party source codes. Microsoft needs to work on it a little bit more. Everybody wants information protection, but not all of them can afford the M365 license. I would like Purview to be a standalone product or solution.
VM people say you cannot use just one product; you need multiple products across the network and you have to deploy to the backups. The DLP could always be better. Overall, they should make their Hyper-V and the clustering more stable. VMware offers very good clustering, for example. Microsoft needs to improve a lot in terms of stability. Technical support is awful.
There is a lot of ambiguity when you are setting up labels, such as sensitive information labels. It is a little daunting at first if you don't have prior knowledge, and there is a little bit of a learning curve for setting up the labels. Some of the setup wizards could be more helpful from an AI perspective. They can streamline the setup through more AI technologies so that you don't have to jump through so many hoops and different menus and dropdowns. It would be useful to have a setup wizard that is more hands-off and engaging for setting up the information type labels. If you tell them this is what we're trying to protect, it should basically start to lead you down that path of best practices. Such a feature would be great.