Merge pull request #270942 from JnHs/jh-acr-redirect

remove topic and redirect

Author: v-dirichards

.openpublishing.redirection.container-service.json

@@ -1,5 +1,10 @@
 {
     "redirections": [
+        {
+            "source_path_from_root": "/articles/container-service/container-registry-auth-aci.md",
+            "redirect_url": "/azure/container-service/container-registry-authentication",
+            "redirect_document_id": false
+        },
         {
             "source_path_from_root": "/articles/container-service/dcos-swarm/container-service-application-specific-marathon.md",
             "redirect_url": "/previous-versions/azure/container-service/dcos-swarm/container-service-application-specific-marathon",

.openpublishing.redirection.json

@@ -3909,6 +3909,11 @@
             "redirect_url": "/azure/batch/monitor-batch",
             "redirect_document_id": false
         },
+        {
+            "source_path_from_root": "/articles/container-registry/container-registry-auth-aci.md",
+            "redirect_url": "/azure/container-registry/container-registry-authentication",
+            "redirect_document_id": false
+        },
         {
             "source_path_from_root": "/articles/event-hubs/move-cluster-across-regions.md",
             "redirect_url": "/azure/operational-excellence/relocation-event-hub-cluster",

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

@@ -33,7 +33,7 @@ In this section, you use the Azure CLI to deploy the image built in the [first t
 
 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. 
 
-A best practice for many scenarios is to create and configure a Microsoft Entra 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.
+A best practice for many scenarios is to create and configure a Microsoft Entra service principal with *pull* permissions to your registry. Take note of the *service principal ID* and *service principal password*. You use these credentials to access the registry when you deploy the container.
 
 You also need the full name of the container registry login server (replace `<acrName>` with the name of your registry):
 

articles/container-registry/TOC.yml

@@ -178,8 +178,6 @@
           href: container-registry-authentication-managed-identity.md
         - name: Authenticate with token 
           href: container-registry-repository-scoped-permissions.md
-        - name: Authenticate from Azure Container Instances
-          href: container-registry-auth-aci.md
         - name: Authenticate from Kubernetes
           items:
           - name: Kubernetes scenarios

articles/container-registry/container-registry-auth-aci.md

@@ -29,7 +29,7 @@ For example, configure your web application to use a service principal that prov
 
 You should use a service principal to provide registry access in **headless scenarios**. That is, an application, service, or script that must push or pull container images in an automated or otherwise unattended manner. For example:
 
-* *Pull*: Deploy containers from a registry to orchestration systems including Kubernetes, DC/OS, and Docker Swarm. You can also pull from container registries to related Azure services such as [Azure Container Instances](container-registry-auth-aci.md), [App Service](../app-service/index.yml), [Batch](../batch/index.yml), [Service Fabric](../service-fabric/index.yml), and others.
+* *Pull*: Deploy containers from a registry to orchestration systems including Kubernetes, DC/OS, and Docker Swarm. You can also pull from container registries to related Azure services such as [App Service](../app-service/index.yml), [Batch](../batch/index.yml), [Service Fabric](../service-fabric/index.yml), and others.
 
     > [!TIP]
     > A service principal is recommended in several [Kubernetes scenarios](authenticate-kubernetes-options.md) to pull images from an Azure container registry. With Azure Kubernetes Service (AKS), you can also use an automated mechanism to authenticate with a target registry by enabling the cluster's [managed identity](../aks/cluster-container-registry-integration.md).
@@ -63,8 +63,6 @@ The **Username** value has the format `xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx`.
 
 You can use service principal credentials from any Azure service that authenticates with an Azure container registry.  Use service principal credentials in place of the registry's admin credentials for a variety of scenarios.
 
-For example, use the credentials to pull an image from an Azure container registry to [Azure Container Instances](container-registry-auth-aci.md).
-
 ### Use with docker login
 
 You can run `docker login` using a service principal. In the following example, the service principal application ID is passed in the environment variable `$SP_APP_ID`, and the password in the variable `$SP_PASSWD`. For recommended practices to manage Docker credentials, see the [docker login](https://docs.docker.com/engine/reference/commandline/login/) command reference.