Azure-docs: Incorrect limit info

[toddjeaton]

East US / East West regions appear to allow for successful creation of Linux containers / container groups with 4 vCPU and 16 GB RAM in both standard (Public) deployments and preview VNet deployments. I have not tested other regions.

(Edit: Specified "Linux" as the OS.)

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 4153e809-a854-ff58-3d1e-31770c36a1f9
• Version Independent ID: e37b5834-9174-5ea2-567c-7b2628ed9eeb
• Content: Azure Container Instances resource availability
• Content Source: articles/container-instances/container-instances-region-availability.md
• Service: container-instances
• GitHub Login: @dlepow
• Microsoft Alias: danlep

[mimckitt]

Thanks for the feedback! We are currently investigating and will update you shortly.

[toddjeaton]

This is definitely not a bad observation - it's just not a match to the documentation.
Example bash CLI creating a single East US public ACI with 4 vCPU / 16 GBI:
az container create --resource-group [insert-your-RG-name] --name nginx-pub --image nginx --location eastus --cpu 4 --memory 16 --ip-address Public --os-type Linux --no-wait

Example bash CLI creating a single East US private ACI with 4 vCPU / 16 GB:
az container create --resource-group [insert-your-RG-name] --name nginx-priv --image nginx --location eastus --cpu 4 --memory 16 --os-type Linux --vnet [insert-your-VNet-name] --subnet [insert-your-ACI-Subnet-name] --no-wait

Get similar results deploying a multi container group via json template.

[mimckitt]

@toddjeaton just to confirm, you are referring to this section

and this section

correct?

[toddjeaton]

Yes, correct.

[mimckitt]

Thanks for confirming!

@dlepow if these two sections are out of date, it is quite possible the other numbers need updating as well. Can you take a look? Or if you know who I can get this checked with I can make any edits as needed.

[dlepow]

@toddjeaton - Thanks for the heads up. I confirmed your observation with the List Capabilities REST API, which is a good source for up to date info on region capabilities and limitations. I'll submit an update soon to the ACI region availability article and confirm data also with our engineering team.

in-progress

[toddjeaton]

@dlepow Thanks for the update, Dan. That's good info! There's also some of the same data shown at https://docs.microsoft.com/en-us/azure/container-instances/container-instances-vnet under the
_Regions and resource availability_ section.

[dlepow]

Documentation updated with current regional availability/limits. @toddjeaton - thanks again for letting us know.

please-close