I am getting an issue connecting the new portal for Data Quality as MSFT is forcing the use of a Managed Identify (MSI), even though i have already connected the data source with SQL Authentication for the scanning. I a unable to connect as Purview is confused in the purview resource name, as there is another Azure resource with same name. I think I have to recreate my purview instance to resolve this managed identity lock. 

It would be preferable if MSFT would allow the same credentials for DQ as it does for scanning. 

​I am getting an issue connecting the new portal for Data Quality as MSFT is forcing the use of a Managed Identify (MSI), even though i have already connected the data source with SQL Authentication for the scanning. I a unable to connect as Purview is confused in the purview resource name, as there is another Azure resource with same name. I think I have to recreate my purview instance to resolve this managed identity lock.  It would be preferable if MSFT would allow the same credentials for DQ as it does for scanning.   Read More

​