Networks

Create and manage the virtual networks — VNets and VLANs — that connect virtual machines and firewalls within your account.

Back to documentation

Networks

Purpose

  • View every VNet and VLAN in your account from a single list.
  • Create a VNet to give VMs and firewalls a private virtual network.
  • Create a VLAN (root accounts only) mapped to a physical host NIC.
  • Attach one subnet to each network to define its IP range.

Prerequisites

  • Minimum permission to view: networking.vnets.read
  • Permission to create a VNet: networking.vnets.create
  • Permission to edit a VNet: networking.vnets.update
  • Permission to delete a network: networking.vnets.delete
  • VLANs are root-only — create: networking.vlans.create, edit: networking.vlans.update, view: networking.vlans.read
  • A compute quota must already exist before you can create a VNet.

View networks

The Networks list combines both VNets and VLANs.

  1. Open Networking → Networks.
  2. Review each row: Name, Type (VNet or VLAN), attached Subnets, and last Updated date.
  3. Select a network name to open its details; VNet details open under /networks, VLAN details under /vlans.
  4. On the details page, review the summary (name, description, type, and VLAN number for VLANs), the attached subnet, attached VMs and firewalls, and resource tags.
  5. Expected result: the selected network's configuration and attached resources are displayed.

Create a VNet

  1. Open Networking → Networks, then select Create VNet.
  2. Enter a Name for the VNet.
  3. Select a Compute Quota.
  4. Configure the subnet: choose Create new subnet (enter subnet name, CIDR, and optional default gateway) or Assign existing subnet (pick an unassigned subnet). One subnet maps to one network.
  5. Optionally leave Inherit tags ticked, and add a resource group and tags.
  6. Select Save.
  7. Expected result: the VNet and its subnet are queued for creation and you return to the Networks list.

Create a VLAN (root only)

  1. Open Networking → Networks, then select Create VLAN (root accounts only).
  2. Enter a Name for the VLAN.
  3. Enter a VLAN Number between 1 and 4094; the number must be unique across existing VLANs.
  4. Select a NIC function (external-traffic uplink).
  5. Configure the subnet: create a new subnet or assign an existing unassigned one.
  6. Optionally add a resource group and tags.
  7. Select Save.
  8. Expected result: the VLAN and its subnet are queued for creation and you return to the Networks list.

Edit or delete a network

  1. Open Networking → Networks.
  2. Select a network name, then choose Edit on the summary card. Editing a VNet needs networking.vnets.update; editing a VLAN is root-only and needs networking.vlans.update.
  3. To delete, select one or more rows in the list and choose Delete, then confirm in the dialog.
  4. Expected result: edits are queued for update, and deleted networks are removed from the list.
  5. Note: shared networks assigned from a parent account cannot be deleted.

Best Practices

  • Keep VLAN numbers unique across the platform.
  • Attach exactly one subnet per network (the mapping is 1-to-1).
  • Leave subnets set to inherit the network's tags to keep grouping consistent.
  • Use VNets for tenant-scoped virtual networks; reserve VLANs (root only) for physical-uplink segments.

Ready to rethink private cloud?

Lower costs. Simplify operations. Deliver more.