Merge pull request #235849 from pritamso/Broken-link-fix-tomvcassidy

AnnaMHuff · web-flow · commit 4558d0e185b4 · 2023-04-25T20:30:50.000-07:00
LinkFix: Broken link fixed
diff --git a/articles/container-instances/container-instances-container-groups.md b/articles/container-instances/container-instances-container-groups.md
@@ -113,9 +113,9 @@ Learn how to deploy a multi-container container group with an Azure Resource Man
 [resource-manager template]: container-instances-multi-container-group.md
 [yaml-file]: container-instances-multi-container-yaml.md
 [region-availability]: container-instances-region-availability.md
-[resource-requests]: /rest/api/container-instances/containergroups/createorupdate#resourcerequests
-[resource-limits]: /rest/api/container-instances/containergroups/createorupdate#resourcelimits
-[resource-requirements]: /rest/api/container-instances/containergroups/createorupdate#resourcerequirements
+[resource-requests]: /rest/api/container-instances/2022-09-01/container-groups/create-or-update#resourcerequests
+[resource-limits]: /rest/api/container-instances/2022-09-01/container-groups/create-or-update#resourcelimits
+[resource-requirements]: /rest/api/container-instances/2022-09-01/container-groups/create-or-update#resourcerequirements
 [azure-files]: container-instances-volume-azure-files.md
 [virtual-network]: container-instances-virtual-network-concepts.md
 [secret]: container-instances-volume-secret.md
diff --git a/articles/container-instances/container-instances-custom-dns.md b/articles/container-instances/container-instances-custom-dns.md
@@ -97,7 +97,7 @@ Once you've completed the steps above, you should see an output with a final key
 ## Deploy your container group
 
 > [!NOTE]
-> Custom DNS settings are not currently available in the Azure portal for container group deployments. They must be provided with YAML file, Resource Manager template, [REST API](/rest/api/container-instances/containergroups/createorupdate), or an [Azure SDK](https://azure.microsoft.com/downloads/).
+> Custom DNS settings are not currently available in the Azure portal for container group deployments. They must be provided with YAML file, Resource Manager template, [REST API](/rest/api/container-instances/2022-09-01/container-groups/create-or-update), or an [Azure SDK](https://azure.microsoft.com/downloads/).
 
 Copy the following YAML into a new file named *custom-dns-deploy-aci.yaml*. Edit the following configurations with your values:
 
diff --git a/articles/container-instances/container-instances-faq.yml b/articles/container-instances/container-instances-faq.yml
@@ -25,7 +25,7 @@ sections:
         answer: |
           Because one of the main determinants of deployment times is the image size, look for ways to reduce the size. Remove layers you don't need, or reduce the size of layers in the image (by picking a lighter base OS image). For example, if you're running Linux containers, consider using Alpine as your base image rather than a full Ubuntu Server. Similarly, for Windows containers, use a Nano Server base image if possible. 
           
-          You should also check the list of pre-cached images in Azure Container Images, available via the [List Cached Images](/rest/api/container-instances/location/listcachedimages) API. You might be able to switch out an image layer for one of the pre-cached images. 
+          You should also check the list of pre-cached images in Azure Container Images, available via the [List Cached Images](/rest/api/container-instances/2022-09-01/location/list-cached-images) API. You might be able to switch out an image layer for one of the pre-cached images. 
           
           See more [detailed guidance](container-instances-troubleshooting.md#container-takes-a-long-time-to-start) on reducing container startup time.
           
diff --git a/articles/container-instances/container-instances-managed-identity.md b/articles/container-instances/container-instances-managed-identity.md
@@ -29,7 +29,7 @@ Use a managed identity in a running container to authenticate to any [service th
 
 ### Enable a managed identity
 
- When you create a container group, enable one or more managed identities by setting a [ContainerGroupIdentity](/rest/api/container-instances/containergroups/createorupdate#containergroupidentity) property. You can also enable or update managed identities after a container group is running - either action causes the container group to restart. To set the identities on a new or existing container group, use the Azure CLI, a Resource Manager template, a YAML file, or another Azure tool. 
+ When you create a container group, enable one or more managed identities by setting a [ContainerGroupIdentity](/rest/api/container-instances/2022-09-01/container-groups/create-or-update#containergroupidentity) property. You can also enable or update managed identities after a container group is running - either action causes the container group to restart. To set the identities on a new or existing container group, use the Azure CLI, a Resource Manager template, a YAML file, or another Azure tool. 
 
 Azure Container Instances supports both types of managed Azure identities: user-assigned and system-assigned. On a container group, you can enable a system-assigned identity, one or more user-assigned identities, or both types of identities. If you're unfamiliar with managed identities for Azure resources, see the [overview](../active-directory/managed-identities-azure-resources/overview.md).
 
diff --git a/articles/container-instances/container-instances-quotas.md b/articles/container-instances/container-instances-quotas.md
@@ -14,7 +14,7 @@ All Azure services include certain default limits and quotas for resources and f
 
 Availability of compute, memory, and storage resources for Azure Container Instances varies by region and operating system. For details, see [Resource availability for Azure Container Instances](container-instances-region-availability.md).
 
-Use the [List Usage](/rest/api/container-instances/location/listusage) API to review current quota usage in a region for a subscription.
+Use the [List Usage](/rest/api/container-instances/2022-09-01/location/list-usage) API to review current quota usage in a region for a subscription.
 
 ## Service quotas and limits
 
diff --git a/articles/container-instances/container-instances-resource-and-quota-limits.md b/articles/container-instances/container-instances-resource-and-quota-limits.md
@@ -23,7 +23,7 @@ Values presented are the maximum resources available per deployment of a [contai
 
 All Azure services include certain default limits and quotas for resources and features. This section details the default quotas and limits for Azure Container Instances.  
 
-Use the [List Usage](/rest/api/container-instances/location/listusage) API to review current quota usage in a region for a subscription. 
+Use the [List Usage](/rest/api/container-instances/2022-09-01/location/list-usage) API to review current quota usage in a region for a subscription. 
 
 Certain default limits and quotas can be increased. To request an increase of one or more resources that support such an increase, please submit an [Azure support request][azure-support] (select "Quota" for **Issue type**). 
 
diff --git a/articles/container-instances/container-instances-troubleshooting.md b/articles/container-instances/container-instances-troubleshooting.md
@@ -240,4 +240,4 @@ Learn how to [retrieve container logs and events](container-instances-get-logs.m
 
 <!-- LINKS - Internal -->
 [az-container-show]: /cli/azure/container#az_container_show
-[list-cached-images]: /rest/api/container-instances/location/listcachedimages
+[list-cached-images]: /rest/api/container-instances/2022-09-01/location/list-cached-images
