Closed ricohomewood closed 2 years ago
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @armleads-azure.
Author: | ricohomewood |
---|---|
Assignees: | - |
Labels: | `Service Attention`, `question`, `ARM - Tags`, `customer-reported`, `needs-triage` |
Milestone: | - |
@dingmeng-xue Is there any update on this issue?
No idea whether @armleads-azure will respond to this issue or not. @ricohomewood , If it is urgent, please raise ticket to Azure support.
According to service response, service changes its behavior. It's not an Azure PowerShell issue.
@dingmeng-xue It has been confirmed by Microsoft:
This is a bug in our control plane's PATCH validation logic.
2019-12-01 listed which will work.
@ricohomewood I see that you are in touch with Microsoft Support for this issue. Hence would like to check with you if this issue can be closed?
Thanks
Yes, MSFT confirmed this was an API regression and fix has been released.
@ricohomewood Thanks for confirming. We will now proceed to close this thread.
Thank you
Description
When attempting to set a Azure Tag using New-AzTag on an Azure Container Instance that is connected to a vNET and thus has a NetworkProfileId populated, you get an error stating:
##[error]{"error":{"code":"NetworkProfileNoLongerSupported","message":"Network profile is no longer supported after API version '2021-07-01'. Please use subnet ID instead."}}
Steps to reproduce
Environment data
Module versions
Debug output
Error output