Skip to content

Commit ee63373

Browse files
committed
link fixes
1 parent e51d64b commit ee63373

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/iot-edge/production-checklist.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -135,19 +135,19 @@ Before you deploy modules to production IoT Edge devices, ensure that you contro
135135

136136
In the tutorials and other documentation, we instruct you to use the same container registry credentials on your IoT Edge device as you use on your development machine. These instructions are only intended to help you set up testing and development environments more easily, and should not be followed in a production scenario. Azure Container Registry recommends [authenticating with service principals](../container-registry/container-registry-auth-service-principal.md) when applications or services pull container images in an automated or otherwise unattended manner, as IoT Edge devices do.
137137

138-
To create a service principal, run the two scripts as described in [Create a service principal](../container-registry/container-registry-auth-aci#create-a-service-principal). These scripts do the following tasks:
138+
To create a service principal, run the two scripts as described in [Create a service principal](../container-registry/container-registry-auth-aci#create-a-service-principal.md). These scripts do the following tasks:
139139

140140
* The first script creates the service principal. It outputs the `Service principal ID` and the `Service principal password`. Store these values securely in your records.
141141

142-
* The second script creates role assignments to grant to the service principal, which can be run subsequently if needed. We recommend applying the **acrPull** or **arcPush** user roles for the `--role` parameter. For a list of roles, see [Azure Container Registry roles and permissions](../container-registry/container-registry-rolesmd)
142+
* The second script creates role assignments to grant to the service principal, which can be run subsequently if needed. We recommend applying the **acrPull** or **arcPush** user roles for the `--role` parameter. For a list of roles, see [Azure Container Registry roles and permissions](../container-registry/container-registry-roles.md)
143143

144144
To authenticate using a service principal, provide the service principal ID and password that you obtained from the first script. Provide the credentials as follows:
145145

146146
* For username or client ID, specify the service principal ID.
147147

148148
* For the password or client secret, specify the service principal password.
149149

150-
For an example of launching Azure Container instances using a service principal, see [](../container-registry/container-registry-roles/container-registry-auth-aci.md#authenticate-using-the-service-principal).
150+
For an example of launching Azure Container instances using a service principal, see [](../container-registry/container-registry-auth-aci.md#authenticate-using-the-service-principal).
151151

152152
### Use tags to manage versions
153153

0 commit comments

Comments
 (0)