Hello Freelancer,
Thanks for posting your question in Microsoft Q&A forum
If you have successfully created an Azure Managed Grafana workspace but can't access the Grafana UI when opening the endpoint URL,
Check provisioning state
If you get a page with an error message such as can't reach this page, stating that the page took too long to respond, follow the process below:
- In the Azure platform, open your workspace and go to the Overview page. Make sure that the Provisioning State is Succeeded and that all other fields in the Essentials section are populated. If everything seems good, continue to follow the process below. Otherwise, delete and recreate a workspace.

- If you saw several browser redirects and then landed on a generic browser error page as shown above, then it means there's a failure in the backend.
- If you have a firewall blocking outbound traffic, allow access to your workspace, to your URL ending in grafana.azure.com, and Microsoft Entra ID.
When public access is disabled and a private endpoint is created, the Grafana workspace is only accessible from within the virtual network (VNet) or networks that can resolve the private DNS zone.
The default public DNS name (sso.wcde.grafana.azure.com) will not resolve outside the private network unless you have configured a private DNS zone or DNS forwarding to resolve the private endpoint's FQDN.
Recommended Approach:
Configure Private DNS Zone
- Create a private DNS zone in Azure for
grafana.azure.comand link it to your VNet. Add an A record in the private DNS zone that maps the Grafana workspace's FQDN to the private IP address of the private endpoint. This ensures that when you access the Grafana URL from within the VNet, it resolves to the private endpoint IP.
Verify Private Endpoint Configuration
- In the Azure portal, go to your Grafana workspace > Networking > Private Endpoint. Confirm that the private endpoint is properly created and linked to your VNet. Check the network interface associated with the private endpoint for the correct FQDN and private IP.
Test DNS Resolution
- From a VM within the VNet, try to resolve the Grafana workspace's FQDN using
nslookupordigto confirm it resolves to the private IP. If it does not resolve, double-check the private DNS zone configuration and ensure the VNet is linked to the zone.
Access from On-Premises or Other Networks
- If you need to access Grafana from outside the VNet (e.g., on-premises), configure DNS forwarding or use a VPN/ExpressRoute to connect to the VNet and resolve the private DNS zone. If you are using Entra ID (Azure AD) for authentication, ensure that the authentication endpoints (like
login.microsoftonline.com) are also accessible from your network, as authentication flows may require outbound internet access or DNS resolution for those domains.
If you are testing, you can temporarily add an entry in your local hosts file to map the Grafana FQDN to the private IP, but this is not recommended for production.
By following these steps, you should be able to resolve the DNS issue and access your Azure Managed Grafana workspace via the private endpoint.
Refer document:
- https://learn.microsoft.com/en-us/azure/private-link/private-endpoint-dns
- https://learn.microsoft.com/en-us/azure/managed-grafana/troubleshoot-managed-grafana#user-cant-access-their-managed-grafana-instance
I hope the provided answer is helpful, do let me know if you have any further questions on this Please accept as Yes & upvote if the answer is helpful so that it can help others in the community.