It sounds like you're having a tough time with Microsoft Purview and Microsoft Fabric, especially around data quality and access policies in your Key Vault. Let's tackle your issues one at a time.
Data Profiling and Quality in Purview:
- Make sure that your Lakehouse tables are discoverable in the Data Map with the correct schema.
- Verify that you're using a Service Principal Name (SPN) for the Data Map scan and Managed Service Identity (MSI) for the Data Quality (DQ) scan.
- Check if you've configured the DQ connection correctly with MSI.
- Ensure that the Purview MSI has contributor access to your Fabric workspace.
- If applicable, enable the OneLake setting which allows users to access data stored in OneLake with apps external to Fabric.
- It might be helpful to follow the troubleshooting guide for data quality for more detailed steps.
Access Policies in Key Vault:
- For the Key Vault issues, ensure you've correctly set up the Key Vault access policies. If secrets aren't showing, it could be due to insufficient permissions or incorrect settings.
- Make sure the identity you're using has the necessary access granted in the Key Vault settings.
- You can refer to Key Vault documentation for further assistance on setting up access policies.
To better help you, could you provide a bit more detail?
- Are you seeing any specific error messages when you attempt to do data profiling or access the Key Vault?
- Do you have the necessary permissions set up in both Microsoft Purview and the Key Vault?
- Can you confirm if the integration between Purview and Fabric is set up correctly in your tenant?