Azure Virtual Network now supports updates without subnet property
Azure API supports the HTTP methods PUT, GET, DELETE for the CRUD (Create/Retrieve/Update/Delete) operations on your resources. The PUT operation is used for both Create and Update. For existing resources, using a PUT with the existing resources preserves them and adds any new resources supplied in the JSON. If any of the existing resources are omitted from the JSON for the PUT operation, those resources are removed from the Azure deployment.
Based on customer support cases and feedback, we observed that this behavior causes problems for customers while performing updates to existing deployments. This is a challenge in the case of subnets in the VNet where any updates to the virtual network, or addition of resources (e.g. adding a routing table), to a virtual network require you to supply the entire virtual network configuration in addition to the subnets. To make it easier for customers, we have implemented a change in the PUT API behavior for virtual network updates. This change allows you to skip the subnet specification in a PUT call without deleting the existing subnets. This capability is now available in a Limited Preview in all the EUAP regions, US West Central and US North with API version 2023-09-01.
Previous behavior
The existing behavior has been to expect a subnet property in the PUT virtual network call. If a subnet property isn't included, the subnets are deleted. This might not be the intention.
New PUT VNet behavior
Assuming your existing configuration is as follows:
|
"subnets": [ { "name": "SubnetA", "properties": {...} }, { "name": "SubnetB", "properties": {...} }, { "name": "SubnetC", "properties": {...} }, { "name": "SubnetD", "properties": {...} }
] |
The updated behavior is as follows:
- If a PUT virtual network doesn't include a subnet property, no changes to the existing set of subnets is made.
- If subnet property is explicitly marked as empty, we will treat this as a request to delete all the existing subnets. For example:
|
"subnets": [] |
OR
|
"subnets": null |
- If a subnet property is supplied with specific values as follows:
|
"subnets": [ { "name": "SubnetA", "properties": {...} }, { "name": "Subnet-B", "properties": {...} }, { "name": "Subnet-X", "properties": {...} } ] |
In this case, the following changes are made to the virtual network:
- SubnetA is unchanged. Assuming the supplied configuration is the same as existing.
- SubnetB, SubnetC and SubnetD are deleted.
- Two new subnets Subnet-B and Subnet-X are created with the new configuration.
This behavior remains unchanged from what Azure currently has today.
Next Steps
Test the new behavior in the regions listed above and share your feedback.
Published on:
Learn moreRelated posts
How to Build a Pipeline for Exact Matching in Azure ML Using Python Script
Exact matching is a critical process for identifying precise matches between text data and predefined keywords. In this blog, we’ll walk you t...
Integrate Dataverse Azure solutions – Part 2
Dataverse that help streamline your integrations, such as Microsoft Azure Service Bus, Microsoft Azure Event Hubs, and Microsoft Azure Logic A...
Dynamics 365 CE Solution Import Failed in Azure DevOps Pipelines
Got the below error while importing Dynamics CRM Solution via Azure DevOps Pipeline. 2024-12-18T23:14:20.4630775Z ]2024-12-18T23:14:20.74...
Dedicated SQL Pool and Serverless SQL in Azure: Comparison and Use Cases
Table of Contents Introduction Azure Synapse Analytics provides two powerful SQL-based options for data processing: Dedicated SQL Pools and Se...