Purview - DLP license question
Hi all, I’m a little confused about the difference in features between M365 E3 and M365 E5. If I’m on E3, and I’m looking to monitor and stop PII date such as credit card information or bank account numbers from being sent out via email, will this data need to be manually labelled? Or can i add those sensitive data types as a conditional filter in my DLP policy? e.g. my DLP conditions will be to check for credit card data and block the action. Will this work with E3? Does DLP scan for PII during transit or is that an E5 feature. Secondly, my encrypted emails ask me to download the information protection viewer. Is that all E3 feature? I’m looking to get the encryption which lets user authenticate via One time code. Is that e5? thanks!
Azure Purview Self-Service Access policy not working.
Using this https://learn.microsoft.com/en-us/purview/how-to-policies-self-service-storage we created a Workflow for self-service data access policy. When a consumer submits a request for a Read access to a data asset, it successfully sends the request to the data owner of the asset. Data Owner approves the request, and after approval, a policy gets successfully auto generated. But the consumer still does not have Read access to the data asset via Azure Portal or Azure Storage Explorer. According to following official documentations and a video from Purview teams, the consumer should have a Read access to the data asset. Question: What we may have been missing and how the issue can be resolved? Remarks: We have verified all the prerequisites described in the above link, as follows: Ran the short PowerShell script: # Install the Az module Install-Module -Name Az -Scope CurrentUser -Repository PSGallery -Force # Login into the subscription Connect-AzAccount -Subscription <SubscriptionID> # Register the feature Register-AzProviderFeature -FeatureName AllowPurviewPolicyEnforcement -ProviderNamespace Microsoft.Storage Data Asset: ADLSGen2 Storage Account [This was created after the above script run] Purview Collection: Collection1 (subcollection of root collection) Data Owner roles on the storage account: IAM Owner, Storage Blob Data Contributor Data Owner roles on Collection1: Data Curator, Data Reader Consumer role on Collection1: Reader A screenshot of the policy auto-generated after an approval from data owner: Ref: https://learn.microsoft.com/en-us/purview/concept-self-service-data-access-policy https://learn.microsoft.com/en-us/purview/how-to-workflow-self-service-data-access-hybrid https://learn.microsoft.com/en-us/purview/how-to-enable-data-policy-enforcement https://www.youtube.com/watch?v=CFE8ltT19Ss
Custom Attributes in Term Templates
We are running into what appears to be an issue with custom attributes in Purview. Once they have been saved and the template updated it doesn't appear to be possible to modify the selections that have been added for a multiple choice field type. We are able to add new choices but not able to delete existing choices or modify the text in them. Is this a limitation of the software or an access level issue? I've attached a screen shot of what it looks like normally. Description is greyed out as well because I expired the attribute.
Auto label based on content matching by Information protection scanner
I have on premises repository in TBs. I have already configured information protection scanner and added repository where files are placed and my scanner is scanning the files also. I want to auto label them based on content matching. for example: Auto label files as "Confidential" when there is a match of world "budget" Auto label files as "Internal use only" when there is a match of word "leave request form" I know auto labeling is available for M365 for example exchange, ondrive and sharepoint. but How can I achieve above using information protection scanner. Please help. Thanks
Azure SQL Database's Primary Key and Foreign Key is not missing Azure Purview
Azure Purview can scan the Primary Key and Foreign Key constraints from Azure non-native software like Salesforces. But Azure Purview is not scanning the Primary Key and Foreign Key constraints from Azure native software like Azure SQL DB. Refer below screenshot Please refer above screenshot, ID columns is Primary key in Azure SQL Database. But Primary key icon is not shown in Azure Purview. Could you please help us in this issue?
