Share via

This registry is configured with private endpoints and public access is disabled. You may be browsing from a disallowed IP address. To browse the registry, try accessing it from an IP in the configured private network.

Karishram B 20 Reputation points
2026-02-09T09:36:43.67+00:00

Im not able to see repos in ACRUser's image

Azure Container Registry
Azure Container Registry

An Azure service that provides a registry of Docker and Open Container Initiative images.

0 comments No comments
{count} votes

Answer accepted by question author
  1. Jilakara Hemalatha 10,200 Reputation points Microsoft External Staff Moderator
    2026-02-09T11:38:17.9233333+00:00

    Hello Karishram B,

    Thank you for reaching out.

    The Azure Container Registry (ACR) is configured with a Private Endpoint, and public network access is disabled. With this configuration, the Azure Portal can list or display repositories only when the request originates from within the configured private network (VNet or a connected network).

    When the registry is accessed from outside the private network, the request comes from a public IP address, which is blocked by the registry’s network rules. As a result, repositories are not visible in the Azure Portal. This behavior is expected and by design when private endpoints are used exclusively.

    Recommended Access Method:

    1.Please access the ACR from within the private network, for example:

    • An Azure VM in the same VNet

    A client machine connected via VPN or ExpressRoute

    Repositories can also be listed using Azure CLI from within the private network:

    az acr repository list --name <registry-name>

    1. Temporary public access (if permitted by security policy): For temporary testing purposes only (not recommended for production environments):

    Go to the Azure Container Registry in the Azure Portal

    Navigate to Settings > Networking

    • Set Public network access to Selected networks or All networks

    3.Using a Private Endpoint: If your setup uses a private endpoint, ensure that:

    • Your virtual network is correctly configured.
    • The DNS settings are pointing correctly to resolve the ACR FQDN.

    4.Verify that NO NSG rules are blocking outbound traffic to your ACR endpoints. Make sure port 443 is open.

    Documentation for reference

    https://learn.microsoft.com/en-us/azure/container-registry/container-registry-access-selected-networks

    https://learn.microsoft.com/en-us/azure/container-registry/container-registry-private-link

    Hope this helps! Please let me know if you have any queries in comments.

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful

Your answer

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