After upgrading Azure Purview account to new tenant level enterprise account, Purview Data Map is not loading and throwing error.

Question

An existing Azure Purview account is behind the private endpoint. After migrating the account to enterprise account in https://purview.microsoft.com/, data map is not loading and throwing following error:

Some apps are behind a private endpoint. Please access the account from a client in the same virtual network (VNet) that has been configured for the Microsoft Purview account's private endpoint.

We have created the platform endpoint on Purview account as per Microsoft Instruction. It is still throwing error in the Data Map/Source Management/Managed Identities page.

Have you encountered this issue if you have migrated Purview? If yes, it will helpful if you can share few ideas for troubleshooting and resolution.

Answer 1

@Singh, Manjit - Thanks for the question and using MS Q&A platform.

According to the official documentation: FAQ about Microsoft Purview private endpoints and Managed VNets

Can I access the Microsoft Purview governance portal from a public network if Public network access is set to Deny in Microsoft Purview account networking?

No. Connecting to Microsoft Purview from a public endpoint where Public network access is set to Deny results in the following error message:

"Not authorized to access this Microsoft Purview account. This Microsoft Purview account is behind a private endpoint. Access the account from a client in the same virtual network (virtual network) that has been configured for the Microsoft Purview account's private endpoint."

In this case, to open the Microsoft Purview governance portal, either use a machine that's deployed in the same virtual network as the Microsoft Purview portal private endpoint or use a VM that's connected to your CorpNet in which hybrid connectivity is allowed.

Why do I receive the following error message when I try to launch Microsoft Purview governance portal from my machine?

"This Microsoft Purview account is behind a private endpoint. Access the account from a client in the same virtual network (virtual network) that has been configured for the Microsoft Purview account's private endpoint."

It's likely your Microsoft Purview account is deployed by using Private Link and public access is disabled on your Microsoft Purview account. As a result, you have to browse the Microsoft Purview governance portal from a virtual machine that has internal network connectivity to Microsoft Purview.

1. Validate if you can resolve the following addresses through your Microsoft Purview account's private IP addresses.
   • Web.Purview.Azure.com
   • <YourPurviewAccountName>.Purview.Azure.com
2. Verify network connectivity to your Microsoft Purview account by using the following PowerShell command:

      Test-NetConnection -ComputerName <YourPurviewAccountName>.Purview.Azure.com -Port 443
   

3. Verify your cross-premises DNS configuration if you use your own DNS resolution infrastructure.

For more information about DNS settings for private endpoints, see Azure private endpoint DNS configuration.

In case, if you are unable to resolve the issue, please do share the details on how exactly you are trying to connect to Purview account and share the complete steps along with the error message which you are experiencing (Prefered screenshot)?

Hope this helps. Do let us know if you have any further queries.

---

If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.