Microsoft Purview account 'xxxxxx' failed to provision. Error: Unknown internal exception

Abdelrahman Eid 20 Reputation points
2025-04-23T10:05:05.51+00:00

Good day

We have set up a Purview account and made it the tenant level account for POC and testing purposes.

When we recently tried to change the Firewall settings for the Public network access to "Disabled for ingestion only", the process took long time to save (longer than what we have seen with other accounts) and then we noticed that the Fabric scans were failing with the following error message:

Error: (3818) Account demo-account cannot get managed identity cred when it is in Failed

Then we tried to revert the Firewall changes back to "Enabled from all networks", it took longer to save as well (few minutes) but the scans were still failing with the same erro.

When we checked the Purview account in the Azure portal, we found this error message:

The Microsoft Purview account 'xxxxxx' failed to provision. Error: Unknown internal exception. Please contact support with the correlationId and timestamp.

We have tried to search online for a solution but the only community question we found did not provide an actual solution other than stating:

The issue has been fixed. 3 days of fertile tries deleting it and this morning if finally worked and fast!!!!!

We hope someone here would be able to help guide us towards a solution for this issue.

PS: The account does not have support plan and hence we are unable to submit a ticket.

Thanks in advance.

Microsoft Purview
Microsoft Purview
A Microsoft data governance service that helps manage and govern on-premises, multicloud, and software-as-a-service data. Previously known as Azure Purview.
1,532 questions
0 comments No comments
{count} votes

Accepted answer
  1. Venkat Reddy Navari 1,270 Reputation points Microsoft External Staff
    2025-04-23T12:50:19.33+00:00

    @Abdelrahman Eid The error message “Microsoft Purview account 'xxxxxx' failed to provision. Error: Unknown internal exception” generally indicates an issue with the backend provisioning process, potentially triggered by the firewall configuration changes.

    Here are a few things you can try:

    1. Wait and Monitor: Sometimes, changes to firewall or network settings can cause temporary inconsistencies in the account’s state. We've seen cases where the error clears up after a few hours or a day. Keep checking the provisioning state in the Azure portal.
    2. Use Azure CLI to Force Configuration Reset: Try reapplying the public network access setting using Azure CLI to ensure the changes are properly submitted:
         az purview account update \
           --name <your-account-name> \
           --resource-group <your-resource-group> \
           --public-network-access Enabled
      
      Replace with your actual values. This can help if the portal UI change didn’t apply cleanly.
    3. Check Provisioning State Manually: Run the following to verify current status
         az purview account show \
           --name <your-account-name> \
           --resource-group <your-resource-group>
      
      Look for the provisioningState field — if it's still in “Failed”, the system may still be attempting to recover.

    I hope this information helps. Please do let us know if you have any further queries.

    Kindly consider upvoting the comment if the information provided is helpful. This can assist other community members in resolving similar issues.

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.