Reputation: 303
I have created a lot of bicep modules and have them published in Azure container registry. I am referring them in applications as private registries.
I have a situation where I want to make these available in a different tenant. I understand there are public registry but of Microsoft and can be contributed to by MS employees. Also while finding how to get this done I came across a solution using Azure lighthouse.
Are these the only two way possible as neither is feasible for me? Do we have any other way to share bicep modules sitting in an ACR in tenant A to be made available in tenant B?
Upvotes: 0
Views: 231
Reputation: 3407
Using B2B (inviting a guest into your AAD tenant from another tenant) does not work unfortunately. Work to support token auth is being planned, and when complete will fulfil your scenario.
The Azure Lighthouse method you mention, or replicating the module versions in multiple tenants will likely the best option for the time being.
The only other option available to you is to enable unauthenticated pull on the registry.... Then not just tenant B could access, but anyone that found it 🤪
Upvotes: 1