You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/container-instances/container-instances-managed-identity.md
-4Lines changed: 0 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,10 +39,6 @@ Azure Container Instances supports both types of managed Azure identities: user-
39
39
40
40
To use a managed identity, the identity must be granted access to one or more Azure service resources (such as a web app, a key vault, or a storage account) in the subscription. Using a managed identity in a running container is similar to using an identity in an Azure VM. See the VM guidance for using a [token](../active-directory/managed-identities-azure-resources/how-to-use-vm-token.md), [Azure PowerShell or Azure CLI](../active-directory/managed-identities-azure-resources/how-to-use-vm-sign-in.md), or the [Azure SDKs](../active-directory/managed-identities-azure-resources/how-to-use-vm-sdk.md).
41
41
42
-
### Limitations
43
-
44
-
* Currently you can't use a managed identity in a container group deployed to a virtual network.
Copy file name to clipboardExpand all lines: articles/container-instances/container-instances-virtual-network-concepts.md
+1-2Lines changed: 1 addition & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,7 +41,6 @@ Container groups deployed into an Azure virtual network enable scenarios like:
41
41
* Currently, only Linux containers are supported in a container group deployed to a virtual network.
42
42
* To deploy container groups to a subnet, the subnet can't contain other resource types. Remove all existing resources from an existing subnet prior to deploying container groups to it, or create a new subnet.
43
43
* To deploy container groups to a subnet, the subnet and the container group must be on the same Azure subscription.
44
-
* You can't use a [managed identity](container-instances-managed-identity.md) in a container group deployed to a virtual network.
45
44
* You can't enable a [liveness probe](container-instances-liveness-probe.md) or [readiness probe](container-instances-readiness-probe.md) in a container group deployed to a virtual network.
46
45
* Due to the additional networking resources involved, deployments to a virtual network are typically slower than deploying a standard container instance.
47
46
* Outbound connection to port 25 is not supported at this time.
@@ -88,4 +87,4 @@ In the following diagram, several container groups have been deployed to a subne
**Azure CLI**: The command-line examples in this article use the [Azure CLI](/cli/azure/) and are formatted for the Bash shell. You can [install the Azure CLI](/cli/azure/install-azure-cli) locally, or use the [Azure Cloud Shell][cloud-shell-bash].
22
22
23
23
## Limitations
24
-
* Container groups running in Azure Virtual Networks don't support managed identity authentication image pulls with ACR.
25
-
26
24
* Windows containers don't support managed identity-authenticated image pulls with ACR.
27
25
28
26
* The Azure container registry must have [Public Access set to either 'Select networks' or 'None'](../container-registry/container-registry-access-selected-networks.md). To set the Azure container registry's Public Access to 'All networks', visit ACI's article on [how to authenticate with ACR with service principal based authentication](container-instances-using-azure-container-registry.md).
![prmerger-automator[bot]](https://avatars.githubusercontent.com/u/22479449?v=4&size=40){kind=avatar}
0 commit comments