Azure Purview Self-Service Access policy not working.
Using this official Purview document, 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 onCollection1:Data Curator, Data Reader Consumer role on Collection1: Reader A screenshot of the policy auto-generated after an approval from data owner: Ref: Microsoft Purview Self-service data discovery and access Self-service access workflows for hybrid data estates Enable data policy enforcement on your Microsoft Purview sources Short video: Microsoft Purview data owner provisioning with Azure Storage
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!
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 thePrimary Key and Foreign Key constraints from Azure non-native software like Salesforces. But Azure Purview is not scanning thePrimary 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?
New Blog Posts | Azure Purview at Spring Ignite 2021
Azure Purview at Spring Ignite 2021 - Microsoft Tech Community Author:Gaurav Malhotra The reception to Azure Purview since launch has been tremendous! We are thrilled to announce that over 14.5 Billion data assets were discovered by customers across their hybrid environments! And today, we are happy to announce that we have some great new features to help our customers do more with Azure Purview. Discover and govern your data in AWS Simple Storage Service (S3) with Azure Purview - Microsoft Tech Community Author: Oded Bergman At the launch in early December, we gave you a sneak peek of the ability to manage multicloud data sources with Azure Purview. Today, I'm happy to announce, that you can now use Azure Purview to discover, manage and govern data residing in Amazon Web Services S3, in public preview. Organize Business glossary terms using hierarchies. - Microsoft Tech Community Author: Naga Yenamandra Azure Purview aims to enable effortless discovery of data by data consumers from across the organization. But for data consumers to meaningfully reason over the data, it must be consistently defined. This is where a business glossary can help. Manage data sources at scale with Azure Purview: Azure Multiple Source registration and scans - Microsoft Tech Community Author: Vishal Anil At the Azure Purview launch, we announced the ability to register and scan individual sources. At Ignite, we announced that we are now making it even easier to register and scan your Azure data at scale, with the Azure multiple source registration feature, now in public preview. This capability allows you to register an entire Azure subscription or resource group in Azure Purview. Purview now supports Non-Microsoft sources - Teradata, Oracle DB, SAP S/4HANA and SAP ECC - Microsoft Tech Community Author: Kavya Chandra Azure Purview expands on the Non-Microsoft Connectors supportability. In addition to the numerous Azure sources supported today, customers can now register and scan from various databases likeTeradataandOracle. Azure purview also supports ERP sources likeSAP S/4HANAandSAP ECC.
