Repository navigation
Add Azure CLI support for First Party Service Tags #34034
Description
Preconditions
- No need to upgrade Python SDK or the Python SDK is ready.
Related command
az network first-party-service-tag create
az network first-party-service-tag update
az network first-party-service-tag show
az network first-party-service-tag list
az network first-party-service-tag delete
az network first-party-service-tag wait
az network public-ip create
az network public-ip update
az network public-ip prefix create
az network public-ip prefix update
az vm create
az vm update
az vmss create
az vmss update
Resource Provider
Microsoft.Network/firstPartyServiceTags
Description of Feature or Work Requested
Add Azure CLI support for managing First Party Service Tag resources and associating them with supported public IP configurations.
The requested work includes:
- Add commands to create, update, retrieve, list, delete, and wait on Microsoft.Network/firstPartyServiceTags resources.
- Support referencing a First Party Service Tag from Public IP Address and Public IP Prefix IP-tag configurations.
- Support the firstPartyServiceTagId property in VM and VMSS implicit public IP configurations.
- Support asynchronous create, update, and delete operations through --no-wait and a corresponding wait command where applicable.
The command group should preferably be generated using AAZ and initially marked Preview.
Minimum API Version Required
2025-09-01
Swagger PR link / SDK link
Network First Party Service Tag resource and Public IP/Public IP Prefix integration:
• Azure/azure-rest-api-specs#44870
• Azure/azure-rest-api-specs#45082
Compute VM and VMSS integration:
• Azure/azure-rest-api-specs#43752
Request Example
• Create a First Party Service Tag
• Get a First Party Service Tag
• List First Party Service Tags in a resource group
• List all First Party Service Tags
• Update First Party Service Tag tags
• Delete a First Party Service Tag
• Create a Public IP Address with a First Party Service Tag
• Create a Public IP Prefix with a First Party Service Tag
There is a known Swagger schema discrepancy for resourceGuid. The 2025-09-01 service response returns resourceGuid at the root of the First Party Service Tag resource, while the published specification currently defines it under properties.
The PowerShell implementation applies an AutoRest transform that moves resourceGuid from FirstPartyServiceTagPropertiesFormat to the root FirstPartyServiceTag model. The CLI implementation may require an equivalent AAZ customization.
Target Date
2026-09-01
PM Contact
Engineer Contact
Additional context
Corresponding Azure PowerShell PRs:
• First Party Service Tag management and Public IP integration: Azure/azure-powershell#29970
• Follow-up fixes: Azure/azure-powershell#30041
• VM and VMSS integration: Azure/azure-powershell#30069
There is a known Swagger schema discrepancy for resourceGuid . The 2025-09-01 service response returns resourceGuid at the root of the First Party Service Tag resource, while the published specification currently defines it under properties .
The PowerShell implementation applies an AutoRest transform that moves resourceGuid from FirstPartyServiceTagPropertiesFormat to the root FirstPartyServiceTag model. The CLI implementation may require an equivalent AAZ customization. Swagger specification will be fixed in next release.
The Network resource operations require API version 2025-09-01 . The separate VM/VMSS firstPartyServiceTagId integration is defined in the Compute API version 2026-04-01.
Activity
yonzhan commentedon Sep 5, 2026
Thank you for opening this issue, we will look into it.
microsoft-github-policy-service commentedon Sep 7, 2026
🔔 Routing this issue to @Azure/act-observability-squad.
microsoft-github-policy-service commentedon Sep 7, 2026
🔔 Routing this issue to @Azure/act-observability-squad.
microsoft-github-policy-service commentedon Sep 7, 2026
🔔 Routing this issue to @Azure/act-quality-productivity-squad.
microsoft-github-policy-service commentedon Sep 7, 2026
🔔 Routing this issue to @Azure/act-quality-productivity-squad.
william051200 commentedon Sep 15, 2026
Based on Azure CLI existing behavior, public IP settings are configured through the
az network public-ipcommands, and the resulting public IP is then attached to the VM usingaz vm create --public-ip-address.To remain consistent with this established command design and avoid duplicating Network configuration arguments under
az vm, We will be keeping the same workflow for this feature rather than adding a new VM argument.cc Julie Zhu (@yanzhudd)