Network profile no longer an option

[erndob]

"Deploy to existing virtual network" category has the "Network profile name or ID, which you can obtain using az network profile list" as an option. This option was removed in the latest cli update. az create no longer has --network-profile.

Which also broke our deployment scripts. For whatever reason I can not update my container instance without specifying network profile. If I create a new CI, I can update it specifying vnet and subnet.

But for this CI that used to use network profile property I get "The updates on container group 'xxx' are invalid. If you are going to update the os type, restart policy, network profile, CPU, memory or GPU resources for a container group, you must delete it first and then create a new one." even though identical update script works when ran against newly deployed copy of it.

---

Document Details

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

• ID: 81e00caf-dd95-441b-d2d5-0b3c979cb11b
• Version Independent ID: 83ed8e59-7ae8-332e-9ce0-7d80e8a973f8
• Content: Deploy container group to Azure virtual network - Azure Container Instances
• Content Source: articles/container-instances/container-instances-vnet.md
• Service: container-instances
• GitHub Login: @macolso
• Microsoft Alias: macolso

[GiftA-MSFT]

@erndob we'll review your feedback and get back to you shortly. Thanks.

[Karishma-Tiwari-MSFT]

Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

[tomvcassidy]

Thanks for your dedication to our documentation. Unfortunately, at this time we have been unable to review your issue in a timely manner and we sincerely apologize for the delayed response. Though the scope of our feedback channel here on GitHub covers specific documentation fixes, we can help redirect you to the right support channel to get an answer to your question: [reference to alternative product/service or community endpoint]. Because this issue does not relate to documentation, we are closing this issue. #please-close