Virtual Network (VNet)
Competitor mapping for Microsoft Azure.
This page is a structured knowledge reference. For step-by-step migration guidance, see the migration guide.
Details
- Provider
- Microsoft Azure
- Service term
- Virtual Network (VNet)
- Provider documentation
- External reference
Behavioral divergences
Virtual Network (VNet)
Quake AI concept: Networks
- Azure VNets are strictly regional Layer 3 overlays scoped to one subscription with no L2 VLAN support ().
- VNets and subnets creation free, but subnets min /29 with Azure reserving 5 IPs per subnet ().
- Managed via ARM REST APIs/PowerShell/CLI vs Neutron REST API.
- Isolated per subscription; peering for cross-VNet connectivity vs OpenStack project networks connected via routers.
Documentation
- →
Build a private network with two virtual machines
deployment
- →
Coming from Azure
evaluation
- →
How to Create a Network
how-to
- →
Migrate from Azure VNet to Quake AI
migration
- →
Network
overview
- →
Network Migration Guides
migration
- →
Network Service API Reference
reference
- →
Network Service CLI Reference
reference
- →
Networks
explanation
- →
Ports API Reference
reference
- →
Ports Console
reference
- →
Routers API Reference
reference
- →
Routers CLI Reference
reference
- →
Routers Console
reference
- →
VPC on Quake AI
explanation
Related
Analog of (incoming)
- Build a private network with two virtual machines→
- Coming from Azure→
- How to Create a Network→
- Migrate from Azure VNet to Quake AI→
- Network→
- Network Migration Guides→
- Network Service API Reference→
- Network Service CLI Reference→
- Networks→
- Ports API Reference→
- Ports Console→
- Routers API Reference→
- Routers CLI Reference→
- Routers Console→
- VPC on Quake AI→
Diverges from (incoming)
Citations
- Microsoft Azure
- Microsoft Azure
These citations record configured source URLs in the knowledge graph. They are not a live platform walk verification date.