Skip to content

Commit bc57a3a

Browse files
authored
Merge pull request #95178 from dlepow/aciacr
[ACI] Clarify ACR access in tutorial
2 parents 892d70f + 60da4ca commit bc57a3a

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

articles/container-instances/container-instances-tutorial-deploy-app.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,9 @@ In this section, you use the Azure CLI to deploy the image built in the [first t
3333

3434
### Get registry credentials
3535

36-
When you deploy an image that's hosted in a private container registry like the one created in the [second tutorial](container-instances-tutorial-prepare-acr.md), you must supply credentials to access the registry. As shown in [Authenticate with Azure Container Registry from Azure Container Instances](../container-registry/container-registry-auth-aci.md), a best practice for many scenarios is to create and configure an Azure Active Directory service principal with *pull* permissions to your registry. See that article for sample scripts to create a service principal with the necessary permissions. Take note of the service principal ID and service principal password. You use these credentials when you deploy the container.
36+
When you deploy an image that's hosted in a private Azure container registry like the one created in the [second tutorial](container-instances-tutorial-prepare-acr.md), you must supply credentials to access the registry.
37+
38+
A best practice for many scenarios is to create and configure an Azure Active Directory service principal with *pull* permissions to your registry. See [Authenticate with Azure Container Registry from Azure Container Instances](../container-registry/container-registry-auth-aci.md) for sample scripts to create a service principal with the necessary permissions. Take note of the *service principal ID* and *service principal password*. You use these credentials to access the registry when you deploy the container.
3739

3840
You also need the full name of the container registry login server (replace `<acrName>` with the name of your registry):
3941

0 commit comments

Comments
 (0)