Roadmap: Anonymous Pull

[mangalorereshmi]

Anonymous Pull is supported today, by opening a support ticket.
This is currently gated as we currently support anonymous for the entire registry. We recognize customers really want anonymous at the repository level. We are investigating group management for repository scoped permissions, and are grouping self-service, repo scoped anonymous support with these capabilities.

For more info:
https://feedback.azure.com/forums/903958-azure-container-registry/suggestions/32517127-enable-anonymous-access-to-registries

[sjuratov]

Hi @mangalorereshmi , I am trying to create support request to enable anonymous pull on my ACR but because my subscription is "Visual Studio Enterprise", I don't have an option to create requests for Technical support. I don't see any other option that would allow me to submit request.

Is there a way for me to be somehow enabled?

[awakecoding]

@mangalorereshmi can you clarify what are the requirements for having anonymous pull support? It's not so clear which kind of subscription is required, or if this is limited to a specific ACR SKU. I'm looking for public registry that supports OCI artifacts for public distribution. ACR would fit the bill because it supports OCI Artifacts, but being able to make the registry public would be a hard requirement for us.

[MXClyde]

@mangalorereshmi I have a support ticket open (#2404100050003286), but have the idea Support does not know what to do with it. Can you help?

[terencet-dev]

Hi @MXClyde, have you tried: https://learn.microsoft.com/azure/container-registry/anonymous-pull-access

[MXClyde]

My mistake, I mixed things up. The instructions you refer to work (I used them too). But I also need custom domain support which is in private preview and MSFT Support is rejecting new customers to it.

[toddysm]

@johnsonshi and @getk12 There are two asks here: anonymous pull and support for custom domain for anonymous pull. We need to look at the experience for both at the same time.

[MXClyde]

@toddysm @johnsonshi @getk12 Anonymous pull works fine on a custom domain after setup. The challenging step is getting custom domain support enabled (which still has private preview status), this can only be done via MS Support with involvement of the customer account team and the product group.