Search

Please login in for more filter options

Kickstart your project with AVM templates.

AVM Bicep Modules
AVM Terraform Modules

network-virtualnetwork

avm-terraform

report
Report Package network-virtualnetwork

If you believe that this package or its contents contain harmful information, please inform us.
Please be aware that we will never share your credentials.

Please let us know what this package contains.
Please enter a valid email address.

This Terraform Azure Verified Module deploys: terraform-azurerm-avm-res-network-virtualnetwork

ipm add --package avm-terraform/network-virtualnetwork --version 0.22.1

Published: 29-08-2026

Project URL: https://ipmhub.io/avm-terraform

Package Type: Terraform

License: MIT

No readme file uploaded for this version

Release History

Version 0.22.1 - 2026-08-11

What's Changed

πŸ› Bug Fixes

Role assignments are no longer replaced on upgrade (#148, closes #137)

When upgrading from a version that migrated role assignments from azurerm to azapi (v0.19.0), the moved-in role assignment's GUID name was not yet known to the upstream random_uuid resource, causing name to resolve to (known after apply). Because name is part of the AzAPI resource identity, this forced a destroy-and-recreate of the role assignment β€” tearing down the RBAC binding during the apply and risking a transient access outage.

azapi_resource.role_assignments (root and subnet modules) now sets lifecycle { ignore_changes = [name] }. Role assignment names are immutable GUIDs in Azure (never renamed, only replaced), so ignoring name changes is safe and eliminates the forced replacement.

  • No-op for existing consumers β€” once random_uuid is in state, plans remain idempotent.
  • Only benefits mid-migration upgraders β€” those moving from a version predating the stable random_uuid name.
  • Validated on real Azure via an upgrade simulation: before the fix, plan = 2 add / 1 destroy (RBAC binding torn down); after, plan = 1 add / 0 destroy, and re-plan reports no changes.

πŸ”§ Maintenance

  • Synced repository with the latest AVM governance templates (relocated agent skills to .github/skills, added .github/agents, regenerated example footers).

Full Changelog: https://github.com/Azure/terraform-azurerm-avm-res-network-virtualnetwork/compare/v0.22.0...v0.22.1

Version 0.22.0 - 2026-08-10

What's Changed

✨ Features

  • CIDR format validation on network inputs (#144, closes #136 & #133) β€” address_space, subnet address_prefix/address_prefixes, and all peering address-space inputs are now validated at plan time with can(cidrhost(...)), across the root module and the subnet/peering submodules. Malformed prefixes (typos, missing mask, non-CIDR strings) now fail fast with a clear, actionable message instead of surfacing as an opaque Azure API error deep in the apply.

πŸ› Fixes

  • Out-of-band subnet drift is now detected (#145, closes #62) β€” both subnet resources set ignore_missing_property = false, so when an external controller (an AVNM ManagedOnly routing configuration, or an Azure Policy DeployIfNotExists assignment) removes a module-managed body property such as properties.routeTable or properties.networkSecurityGroup, Terraform now surfaces the change as drift and offers to restore it rather than silently swallowing it.
    • Validated end-to-end against real Azure AVNM: clean idempotency (the flip introduces zero plan noise) β†’ out-of-band routeTable removal detected as a restore diff β†’ suppression confirmed.
    • When you intend an external controller to own a path, pair this with the existing ignore_body_changes escape hatch (shipped in v0.21.0 / TFFR8) to suppress that single path only β€” every other managed property keeps its drift protection.

πŸ§ͺ Test reliability

  • Example region-picker hardening (#145) β€” stops spurious LocationNotAvailable e2e failures:
    • Direct-picker examples now exclude Azure canary/EUAP regions (eastus2euap, centraluseuap) via region_name_regex.
    • The IPAM examples' hardcoded allowlist drops 7 access-restricted secondary regions (australiacentral, australiacentral2, brazilsoutheast, germanynorth, norwaywest, switzerlandwest, uaecentral), leaving ~40 generally-available regions.

⚠️ Upgrade notes

  • Behavioral change (drift detection): if you have subnets whose routeTable/networkSecurityGroup (or other managed body properties) are currently being changed out-of-band, the next plan after upgrading may show a restore diff that was previously hidden. This is the intended fix. If an external controller is meant to own that property, set ignore_body_changes = ["properties.routeTable"] (per-subnet) β€” or the module-wide ignore_body_changes.virtual_networks_subnets slot β€” and leave the corresponding dedicated input unset. See the subnet module README ("Out-of-band changes and drift detection").
  • No provider or Terraform version-floor changes in this release (azapi ~> 2.12, Terraform >= 1.9, unchanged from v0.21.0).

Full Changelog: https://github.com/Azure/terraform-azurerm-avm-res-network-virtualnetwork/compare/v0.21.0...v0.22.0

Version 0.21.0 - 2026-08-10

What's Changed

✨ Features

  • New ignore_body_changes interface (#142, closes #61) β€” a spec-conformant way to suppress out-of-band drift on VNet, subnet, and peering resources. Implements AVM spec TFFR8.
    • Root-level ignore_body_changes object keyed by resource type (virtual_networks, virtual_networks_subnets, virtual_networks_virtual_network_peerings), plus a per-subnet override that takes precedence.
    • Resolves the AVNM / Azure Policy DINE route-table (and other server-side) infinite-drift problem.
    • Validated in CI and live against real AVNM IPAM pools (apply β†’ idempotency, zero drift β†’ destroy).

πŸ“ Docs

  • Corrected stale peerings variable documentation (#135).

⚠️ Upgrade notes

  • azapi provider minimum is now ~> 2.12 β€” ignore_body_changes is a write-only argument introduced in azapi v2.12.0.
  • Terraform required_version floor stays >= 1.9. Per TFFR8, supplying a non-empty ignore_body_changes value requires Terraform β‰₯ 1.11; the empty default emits null, so consumers on 1.9/1.10 who don't use the feature are unaffected.
  • Note: because the value lives in provider-private state, a change to ignore_body_changes only takes effect after an apply.

πŸ™ Credits

Thanks to @martinopedal for surfacing the drift issue and the original PR #70.

Full Changelog: https://github.com/Azure/terraform-azurerm-avm-res-network-virtualnetwork/compare/v0.20.0...v0.21.0

Version 0.20.0 - 2026-07-30

[!WARNING] Breaking change: subnet service endpoints. service_endpoints_with_location is removed and now raises a validation error instead of being silently discarded. Configure subnet service endpoints with names only:

subnets = {
  example = {
    name              = "example"
    address_prefixes  = ["10.0.0.0/24"]
    service_endpoints = ["Microsoft.Storage", "Microsoft.KeyVault"]
  }
}

This affects anyone upgrading from v0.15.0 through v0.19.0, where service_endpoints_with_location was the only available input. Azure expands service-endpoint locations implicitly, so the module no longer manages them. This resolves the repeated-diff and silent endpoint-removal behaviour reported in #22, #39, and #50.

Other notable changes

  • The azapi provider floor is now ~> 2.11, which guarantees the upstream fixes for Missing Resource Identity After Read (#56) and the subnet delegation crash (#63).
  • Subnets can omit privateEndpointNetworkPolicies in regions that do not support it (#46).
  • Reverse peering guards gateway-transit create ordering (#57).
  • The README now documents Migrating from v0.1.x using moved blocks, so the v0.2.0 azurerm to azapi rewrite no longer requires destroying and recreating resources (#111).

Thanks to @mr-scripting, @rdeenen1990, @bronius, @smilnovic-adf, and @deepukumark2119 for the reports behind these fixes.

What's Changed

New Contributors

Full Changelog: https://github.com/Azure/terraform-azurerm-avm-res-network-virtualnetwork/compare/v0.19.0...v0.20.0

Version 0.19.0 - 2026-06-17

What's Changed

⚠️ Breaking Changes

  • Interfaces converted from azurerm to azapi (#52) β€” the resource lock, role assignment, and diagnostic settings interfaces are now implemented with azapi_resource via the Azure/avm-utl-interfaces utility module. The azurerm provider dependency has been removed from the module entirely. (#108)

Input/output compatibility: the lock, role_assignments, and diagnostic_settings variable schemas are unchanged β€” no inputs or outputs were added, removed, or renamed. Existing configurations do not need to change.

Upgrade impact on terraform apply:

  • Locks & diagnostic settings migrate in place via moved blocks β€” no recreation.
  • Role assignments are recreated once. Their underlying resource name changes from the azurerm-generated GUID to the utility module's generated name, so Terraform will destroy and re-create each role assignment on the first apply after upgrading. This is a metadata-only churn β€” the effective access (principal, role, scope) is identical before and after. Plan carefully if you have policies that react to role-assignment lifecycle events.

Why

Aligns the module with the AVM direction of using azapi + shared interface utility modules, reduces provider surface area, and removes the dual-provider (azurerm + azapi) requirement for consumers.

Contributors

  • @kewalaka β€” original implementation (#52 / #108)
  • @haflidif β€” maintainer, takeover & CI
  • @jaredfholgate β€” review

Full Changelog: https://github.com/Azure/terraform-azurerm-avm-res-network-virtualnetwork/compare/v0.18.2...v0.19.0

Version 0.18.2 - 2026-06-17

What's Changed

Bug Fixes

  • Fix extended_location validation (#54) β€” the validation used contains() with a string as its first argument instead of a list, causing it to error at plan time for any non-null extended_location, making the variable unusable. The check is now a direct equality comparison (var.extended_location.type == "EdgeZone") and is covered by a new unit test. (#107)

Maintenance

  • Repository hygiene (#42) β€” removed tracked .DS_Store files and ignored them going forward. (#107)
  • Dependencies β€” consolidated Dependabot bumps for example-only helper modules: Azure/avm-utl-regions/azurerm 0.9.0 β†’ 0.12.0 and Azure/naming/azurerm 0.4.2 β†’ 0.4.3. No impact on the module, its inputs, outputs, or consumers. (#106)

Patch release. The only consumer-facing change is the extended_location validation fix β€” no inputs or outputs were added, removed, or renamed.

Contributors

  • @haflidif β€” maintainer
  • @T0biii β€” repository hygiene (.DS_Store cleanup)
  • @jaredfholgate β€” review

Full Changelog: https://github.com/Azure/terraform-azurerm-avm-res-network-virtualnetwork/compare/v0.18.1...v0.18.2

Version 0.18.1 - 2026-06-15

What's Changed

Documentation

  • Clarify IPAM allocation rules and pool constraints in the module README (#105). Documents the Azure AVNM platform behavior verified against API 2025-09-01:
    • One IPv4 pool + one IPv6 pool per virtual network (and per subnet) β€” the RP rejects duplicate or multiple same-family pools (CannotHaveDuplicatePoolIds, only one association of each IP type is allowed).
    • No mixing of IPAM pool allocation and static address_prefixes in the same VNet/subnet (CannotMixAddressPrefixAndPoolInPayload).
    • Subnet pools must be a subset of the parent VNet's pools (SubnetPoolsMustBeSubsetOfVnetPools).
    • Summarization vs. fragmentation of a single number_of_ip_addresses allocation: Azure resolves one allocation entry into one or more CIDRs depending on contiguity of free space β€” this is read-only and causes no Terraform drift.
  • New "IPAM Allocation Rules and Sizing" section plus expanded IPAM troubleshooting with RP error codes.

Docs-only patch release. No module behavior, inputs, or outputs changed. The validation introduced in v0.18.0 (one IPv4 + one IPv6 pool per VNet) was confirmed correct against the latest Azure API.

Contributors

  • @haflidif β€” maintainer
  • @jaredfholgate β€” review

Full Changelog: https://github.com/Azure/terraform-azurerm-avm-res-network-virtualnetwork/compare/v0.18.0...v0.18.1

Version 0.18.0 - 2026-06-15

What's Changed

Features

  • Pass through number_of_ip_addresses for IPAM pools (root module + subnet submodule), enabling single address-count IPAM allocation. Originally contributed by @timja in #67.

Bug Fixes

  • Require number_of_ip_addresses or prefix_length per IPAM pool (XOR validation), preventing a plan-time crash when neither is set. Contributed by @martinopedal in #67.
  • Fix regex for IPAM pool ID validation. Contributed by @walkerk1980 in #65.
  • Stop emitting the unsupported enabled_metric diagnostic block for virtual networks (interface-compliant: the metric_categories input is retained). Contributed by @deni-cpu and @martinopedal in #69.
  • Align IPv6 IPAM pool validation with IPv4 (full /48–/64 range, null-guarded). By @haflidif.

Tests

  • Add terraform test unit coverage for ipam_pools variable validations (9 runs). By @haflidif.

Issues fixed

  • Closes #66 β€” IPAM allocation by address count
  • Closes #64 β€” regex now allows . in IPAM pool names
  • Closes #43 β€” removes the unsupported dynamic enabled_metric for virtual networks

Contributors

Huge thanks to everyone whose work is included in this release πŸ™

  • @timja β€” #67
  • @martinopedal β€” #67, #69
  • @walkerk1980 β€” #65
  • @deni-cpu β€” #69
  • @jaredfholgate β€” review
  • @haflidif β€” maintainer

Note: External contributions were reimplemented on an owner-controlled release branch (#104) because fork PRs cannot run the AVM CI directly; original authorship is preserved via commit Co-authored-by trailers. Multi-pool IPAM (#102) remains out of scope per the Azure AVNM API constraints discussed in #71 (one IPv4 + one IPv6 pool per VNet, no mixing). #70 is tracked separately.

Full Changelog: https://github.com/Azure/terraform-azurerm-avm-res-network-virtualnetwork/compare/v0.17.1...v0.18.0

Version 0.17.1 - 2026-01-19

What's Changed

New Contributors

Full Changelog: https://github.com/Azure/terraform-azurerm-avm-res-network-virtualnetwork/compare/v0.17.0...v0.17.1

Version 0.17.0 - 2026-01-07

What's Changed

Issues fixed

fixed #48

Full Changelog: https://github.com/Azure/terraform-azurerm-avm-res-network-virtualnetwork/compare/v0.16.0...v0.17.0

Version 0.16.0 - 2025-11-14

What's Changed

New Contributors

Full Changelog: https://github.com/Azure/terraform-azurerm-avm-res-network-virtualnetwork/compare/v0.15.0...v0.16.0

Version 0.15.0 - 2025-10-15

Breaking changes

The deprecated service_endpoints input for subnets has been removed.

We have had to separate the implementation of subnets using IPAM. If you have deployed a subnet with IPAM since that change went out, you'll need to add a moved block to your code into order to migrate the state. E.g.

moved {
  from = module.vnet.module.subnet["subnet01"].azapi_resource.subnet
  to   = module.vnet.module.subnet["subnet01"].azapi_resource.subnet_ipam[0]
}

If you are not using IPAM your state will automatically be migrated.

What's Changed

Full Changelog: https://github.com/Azure/terraform-azurerm-avm-res-network-virtualnetwork/compare/v0.14.1...v0.15.0

Version 0.14.1 - 2025-10-07

What's Changed

Thanks to @Arhughes14 for contributing this change

Full Changelog: https://github.com/Azure/terraform-azurerm-avm-res-network-virtualnetwork/compare/v0.14.0...v0.14.1

Version 0.14.0 - 2025-10-07

πŸŽ‰ Major New Feature: IPAM Support

This release introduces comprehensive IP Address Management (IPAM) support through Azure Virtual Network Manager, enabling centralized IP governance and automatic conflict prevention.

✨ New Capabilities

  • 🏒 VNet IPAM Allocation - Automatically allocate VNet address space from centralized IPAM pools
  • πŸ”— Subnet IPAM Allocation - Dynamic subnet addressing with automatic conflict resolution
  • πŸ”€ Mixed Addressing - Combine IPAM and traditional subnets within the same VNet
  • πŸ”„ Enhanced Subnet Module - Standalone subnet module now supports IPAM allocation
  • ⚑ Retry Logic - Robust conflict resolution with 15-second intervals (300s max timeout)

πŸ“ Regional Availability

IPAM is supported in all Azure regions where Virtual Network Manager is available, except: chilecentral, jioindiawest, malaysiawest, qatarcentral, southafricawest, westindia, westus3

πŸ›  What's New

Core Module

  • Added ipam_pools variable for VNet address space allocation
  • Enhanced subnet configuration with IPAM pool support
  • Integrated retry mechanisms for reliable IPAM operations
  • Maintained full backwards compatibility (zero breaking changes)

Subnet Module

  • Added IPAM allocation capabilities to standalone subnet module
  • Support for dynamic IP assignment from IPAM pools
  • Consistent interface with main module IPAM features

New Examples

  • ipam_basic - Complete IPAM usage with VNet and multiple subnets
  • existing_vnet_ipam_subnets - Adding IPAM subnets to existing IPAM-enabled VNets
  • ipam_vnet_only - IPAM VNet creation with traditional subnet management

πŸ”§ Technical Requirements

  • Azure Virtual Network Manager required for IPAM functionality
  • azapi provider version ~> 2.4
  • Removed time provider dependency (replaced with native azapi retry logic)

πŸ“š Migration Notes

  • No breaking changes - existing configurations work unchanged
  • Optional feature - IPAM can be adopted gradually alongside traditional addressing
  • State compatibility - no state migration required

πŸ› Other Improvements

  • Enhanced error handling and retry mechanisms
  • Comprehensive documentation and troubleshooting guides

πŸ™ Acknowledgments

Special thanks to @ChrisChapman-gh for his initial structure and shell that helped lay the foundation for this IPAM implementation.

What's Changed

New Contributors

Full Changelog: https://github.com/Azure/terraform-azurerm-avm-res-network-virtualnetwork/compare/v0.13.0...v0.14.0

Version 0.13.0 - 2025-10-06

What's Changed

Full Changelog: https://github.com/Azure/terraform-azurerm-avm-res-network-virtualnetwork/compare/v0.12.0...v0.13.0

Version 0.12.0 - 2025-09-29

Breaking Change

This PR removes some of the retry options, but very unlikely they are being used so not expecting much impact.

What's Changed

Full Changelog: https://github.com/Azure/terraform-azurerm-avm-res-network-virtualnetwork/compare/v0.11.0...v0.12.0

Version 0.11.0 - 2025-09-26

Breaking Changes

This release includes a significant breaking change to the module interface.

We have removed the resource_group_name and subscription_id inputs. The resource group ID must now be explicitly provided via the parent_id input.

This change was necessary to align to forthcoming AVM v1 specs as well as fix an underlying idempotency issue with the existing implementation.

We try very hard not to make breaking changes to module interfaces like this and understand the impact it has to consumers of our modules. We do not anticipate any further breaking changes to the interface of this module prior to v1.

What's Changed

Full Changelog: https://github.com/Azure/terraform-azurerm-avm-res-network-virtualnetwork/compare/v0.10.0...v0.11.0

Version 0.10.0 - 2025-08-01

What's Changed

New Contributors

Full Changelog: https://github.com/Azure/terraform-azurerm-avm-res-network-virtualnetwork/compare/v0.9.3...v0.10.0

Version 0.9.3 - 2025-07-24

What's Changed

New Contributors

Full Changelog: https://github.com/Azure/terraform-azurerm-avm-res-network-virtualnetwork/compare/0.9.1...v0.9.3

Version 0.9.2 - 2025-07-03

Full Changelog: https://github.com/Azure/terraform-azurerm-avm-res-network-virtualnetwork/compare/0.9.0...0.9.2

Version 0.9.1 - 2025-07-03

Full Changelog: https://github.com/Azure/terraform-azurerm-avm-res-network-virtualnetwork/compare/0.9.0...0.9.1

Version 0.9.0 - 2025-06-24

Breaking changes

We no longer support azurerm v3 or azapi v1

What's Changed

Full Changelog: https://github.com/Azure/terraform-azurerm-avm-res-network-virtualnetwork/compare/v0.8.1...0.9.0

Version 0.8.1 - 2025-02-06

What's Changed

New Contributors

Full Changelog: https://github.com/Azure/terraform-azurerm-avm-res-network-virtualnetwork/compare/v0.8.0...v0.8.1

Version 0.8.0 - 2025-01-31

What's Changed

Breaking change

  • Update to the version of Terraform CLI support

New Contributors

Full Changelog: https://github.com/Azure/terraform-azurerm-avm-res-network-virtualnetwork/compare/v0.7.2...v0.8.0

Version 0.7.2 - 2025-01-28

What's Changed

Full Changelog: https://github.com/Azure/terraform-azurerm-avm-res-network-virtualnetwork/compare/v0.7.1...v0.7.2

Version 0.7.1 - 2024-11-16

What's Changed

Full Changelog: https://github.com/Azure/terraform-azurerm-avm-res-network-virtualnetwork/compare/v0.7.0...v0.7.1

Version 0.7.0 - 2024-11-15

What's Changed

Releasing as a minor in this dependency change has impact on peering usage.

Full Changelog: https://github.com/Azure/terraform-azurerm-avm-res-network-virtualnetwork/compare/v0.6.0...v0.7.0

Version 0.6.0 - 2024-11-01

What's Changed

This release adds support for v2 of the azapi provider. We have incremented the minor version, but there are no breaking changes and it is backwards compatible with v1 of azapi.

Full Changelog: https://github.com/Azure/terraform-azurerm-avm-res-network-virtualnetwork/compare/v0.5.0...v0.6.0

Version 0.5.0 - 2024-10-29

What's Changed

Added backwards compatible support for v4 of azurerm.

Full Changelog: https://github.com/Azure/terraform-azurerm-avm-res-network-virtualnetwork/compare/v0.4.2...v0.5.0

Version 0.4.2 - 2024-10-11

What's Changed

Full Changelog: https://github.com/Azure/terraform-azurerm-avm-res-network-virtualnetwork/compare/v0.4.1...v0.4.2

Version 0.4.1 - 2024-10-11

What's Changed

New Contributors

Full Changelog: https://github.com/Azure/terraform-azurerm-avm-res-network-virtualnetwork/compare/v0.4.0...v0.4.1

Version 0.4.0 - 2024-07-26

What's Changed

Added the capability to properly peer by subnet and fixed a non-backwards compatible default on peering.

Full Changelog: https://github.com/Azure/terraform-azurerm-avm-res-network-virtualnetwork/compare/v0.3.0...v0.4.0

Version 0.3.0 - 2024-07-17

What's Changed

We added some missing properties and enabled automatic feature enablement for some preview features.

We added the address_prefix singular vartiable to the subnet submodule to support some cases where the address_prefixes variable is not being read by resources that use a subnet.

Full Changelog: https://github.com/Azure/terraform-azurerm-avm-res-network-virtualnetwork/compare/v0.2.4...v0.3.0

Version 0.2.4 - 2024-07-05

What's Changed

Full Changelog: https://github.com/Azure/terraform-azurerm-avm-res-network-virtualnetwork/compare/v0.2.3...v0.2.4

Version 0.2.3 - 2024-05-30

What's Changed

Full Changelog: https://github.com/Azure/terraform-azurerm-avm-res-network-virtualnetwork/compare/v0.2.2...v0.2.3

Version 0.2.2 - 2024-05-29

What's Changed

Full Changelog: https://github.com/Azure/terraform-azurerm-avm-res-network-virtualnetwork/compare/v0.2.1...v0.2.2

Version 0.2.1 - 2024-05-28

What's Changed

Full Changelog: https://github.com/Azure/terraform-azurerm-avm-res-network-virtualnetwork/compare/v0.2.0...v0.2.1

Version 0.2.0 - 2024-05-28

Breaking Changes

v0.2.0 is a re-write of the module, it changes the interface and internal implementation considerably and you will have to update any code and state that is dependent on this module. We try to avoid making updates like this, but in this case we considered the updates valuable enough to make this change. The interface will be stable moving forward.

What's Changed

v0.2.0 moves the module to an AzAPI implementation. The primary driver for this is to support customers that implement common landing zone policies requiring route table and network security groups. You are now able to create a virtual network that meets your policy requirements in one atomic operation avoiding issues with policy blocking deployment.

We have also updated the module to better support common subscription vending scenarios, where application teams manage subnets, but don't managed the virtual network or peering.

We have broken out subnet and peering in sub modules that can be consumed independently. See the documentation and examples for more details on this.

A huge thanks to @kewalaka and @haflidif for all the work on this.

New Contributors

Full Changelog: https://github.com/Azure/terraform-azurerm-avm-res-network-virtualnetwork/compare/v0.1.4...v0.2.0

Version 0.1.4 - 2024-03-20

What's Changed

New Contributors

Full Changelog: https://github.com/Azure/terraform-azurerm-avm-res-network-virtualnetwork/compare/v0.1.3...v0.1.4

Version 0.1.3 - 2023-12-04

What's Changed

New Contributors

Full Changelog: https://github.com/Azure/terraform-azurerm-avm-res-network-virtualnetwork/compare/v0.1.1...v0.1.3

Version 0.1.2 - 2023-10-16

  • changed approach in defining subnets
  • removed ability to create a DDOS plan as this should be a separate module. This module still accepts an existing ddos plan to be integrated to the vnet
  • added capability create a one side peer to another existing vnet

Version 0.1.1 - 2023-10-16

What's Changed

Full Changelog: https://github.com/Azure/terraform-azurerm-avm-res-network-virtualnetwork/compare/v0.1.0...v0.1.1

Version 0.1.0 - 2023-09-29

No release notes were published in the GitHub Release for this version.

 
 {
  "workingFolder": "packages",
  "packages": [
    // packages defined earlier
    {
      "name": "avm-terraform/network-virtualnetwork",
      "version": "0.22.1"
    }
  ]
}

This package has no dependencies

Stats

Selected version:

0.22.1

Downloads this version:

0

Downloads all versions:

48

Latest version:

0.22.2

Latest update:

29-08-2026

avm-terraform

Other versions (42)

0.22.2

0.22.1

0.22.0

0.21.0

0.20.0

0.19.0

0.18.2

0.18.1

0.18.0

0.17.1

Other packages

from avm-terraform

app-containerapp

app-job

apimanagement-service

View all from publisher

Ready to End Infrastructure Code Chaos?

Join infrastructure teams who've moved from scattered repositories to unified package management

Built by infrastructure experts
Who understand your challenges
Complete solutions
No scattered files
See what's deployed where
When it needs updates
Zero vendor lock-in
Packages work without us
Start Free Trial Book Live Demo Schedule Assessment
No setup fees or contracts Free migration assistance Cancel anytime with no penalties
Direct founder access Zero security incidents in 2+ years Works with any cloud, any CI/CD platform