We’ve checked from our end and the server containers are healthy. Could you please check and confirm whether the server is now visible from your end?
cannot see my Postgresql flexible server in the portal but it is visible via az cli
Hi there,
I have a very weird problem.
I created a Postgresql flex server via terraform.
It said that everything was fine but I cannot see it in the Azure.
After some research I found it via az cli with the command
az postgres flexible-server list -o table
Cannot really understand why cannot find it in the portal. Tried in Private mode and nothing change. I am using Firefox
Azure Database for PostgreSQL
-
Manoj Kumar Boyini 7,585 Reputation points Microsoft External Staff Moderator
2026-01-27T20:54:08.9033333+00:00
1 additional answer
Sort by: Most helpful
-
Q&A Assist2026-01-28T13:13:38.6933333+00:00 AI generated content. This question contains an answer created with AI from Q&A Assist. Learn moreIt sounds like you are experiencing an issue where your PostgreSQL flexible server is not appearing in the Azure portal, despite being visible via the Azure CLI. Here are a few potential reasons and troubleshooting steps you can consider:
- Refresh the Portal: Sometimes, the Azure portal may not refresh automatically. Try refreshing the page or logging out and back in to see if the server appears.
- Check Resource Group: Ensure that you are looking in the correct resource group in the Azure portal. The server should be listed under the same resource group you specified when creating it with Terraform.
- Permissions: Verify that your user account has the necessary permissions to view the resources in the Azure portal. If you have limited permissions, you might not see all resources.
- Region Mismatch: Make sure that you are checking the correct region in the Azure portal. The server may have been created in a different region than the one you are currently viewing.
- Browser Issues: Since you mentioned using Firefox, try accessing the Azure portal using a different browser or clearing your browser cache to see if that resolves the issue.
If none of these steps work, you might want to check the Azure service health for any ongoing issues or reach out to Azure support for further assistance.
References: