Netforge.ai Docs
Open the app →
Docs/Guide/Azure & Terraform

Azure & Terraform

Azure resource nodes → Terraform, with import and drift checks.

Relevant for:Professional ServicesEnterprise / NetOps

Designing Azure on the canvas#

Where to find itCanvas→Device catalog→Azure→Place resources

Azure resources — VNets, subnets, NSGs, firewalls, gateways, load balancers, VMs, AKS, App Services, storage, SQL — are first-class nodes. Each maintains a synchronized Terraform (AzureRM) block; the design exports as deployable HCL.

Import an existing subscription#

Where to find itCanvas toolbar→Azure→Import wizard

The import wizard authenticates with your subscription (service-principal credentials), walks the resource graph, brings the estate in via terraform import semantics, and lays it out as an editable visual diagram — VNets as containers, resources inside, with their full configuration attached.

Drift checking#

After import, scheduled drift checkscompare the live subscription against the design's Terraform state and surface differences — someone clicked something in the portal, a pipeline changed a SKU — so the diagram remains the truth, not a snapshot.

Why
Cloud estates drift by default: portal edits leave no trace in your IaC. Import-then-drift-check inverts that — the design becomes the reference, changes are made on the canvas, and the regenerated plan applies them. Device management via Ansible follows the same pattern for on-prem gear.
Note
Service-principal secrets are encrypted at rest and never returned to the browser — drift schedules run server-side.