Data Quality/Data Profiling Scan issue in Purview
Hi Everyone, Hope you are doing great !! I tried to run Data Quality/Data profiling scan in Purview, Scan got failed with an error "DataQualityInternalError Internal service error occurred. Please retry or contact Microsoft support" Could you please help me how can I resolve it. Want to ensure did I have provided right access to Purview : Currently I am using Purview MSI as an authentication option to integrate (Fabric and Purview) and provided Purview MSI with "Contributor" role access to our required Fabric Workspace. Also I am having "Contributor" role access to the required Workspace. Kindly help me to understand: if we want to run data quality scan on Fabric Workspace, User (Myself) should assign with which level of access Member or Contributor in Fabric To run Data quality/Data profiling scan on Fabric Lakehouse delta tables in Purview , Which authentication should I have use (MSI or Service Principal) Could you please help me to resolve it, It will help us to do Data Quality and Profiling. Thanks in advance. Regards, Banumathi
Purview Account
Just started using Purview and can see that data in my MS cloud has already been categorised and when I create new files they are categorised too. But I do not have a Purview Account - do I need one ? I do not see the Data Map menu despite reading articles about putting my account in various groups but now wandering if its because we do not have a Purview Account. If i created a new SIT I would have to go to each SharePoint site and have re-index it which I would prefer to have it done to all sites at once which I believe you can do in the Data Map which we cannot see.Auto-label cannot scope to Synapse Analytics Database
After testing some Purview functionality I have discovered that any Synapse Analytics Serverless SQL Database cannot be handled by Purview when scoped to the individual database. You get the following error: As the "AppliedScope" is just a tick box for the user, I am presuming there is a long FQDN in the Azure backend causing this error. The synapse workspace name and database name are not particularly long as well. We were testing this for a customer and know that their own Synapse workspace names and database names will be more characters than our test scenario. The scenario was an Auto-Label policy for a sensitivity label against a data source in data map. This data source was a single Synapse Workspace with a single serverless SQL database. All names for these were around 8-10 characters. Can anyone in the Purview team confirm if this is a known error at all and if there is a fix incoming anytime soon?
