PinPole User Guide — Azure supplement
Version 2.0 · New in the split guide structure (no Azure chapter in v1.0)
Read Shared features first. This page is Azure-specific.
1. Azure on the canvas
- Workspaces targeting Microsoft Azure show an Azure service palette (compute, networking, data, AI, integration, security, etc.).
- Connections and validation follow Azure-flavoured architectural patterns analogous to the AWS rules engine.
- Node configuration uses Azure concepts — e.g. VNet naming, region / availability selectors, subnet type (private, public, gateway) inside Infrastructure placement.
Catalogue: Azure catalog lists every Azure service, node ID, panel sections, and quick actions from PinPole’s specs.
2. Simulation (Azure)
Simulation models Azure-shaped throughput, latency, and quota pressure. As with any provider:
- Set realistic SKUs, tiers, and limits in each node.
- Use multiple traffic patterns (steady, ramp, spike) to stress different limits.
- Treat $/mo estimates in history as comparative design-time signals, not Azure invoices.
Shared workflow: Run simulation, Interpret results.
3. Infrastructure code and export (Azure)
PinPole’s direction is parity with AWS for export and IaC hand-off:
| Target | Status |
|---|---|
| JSON architecture / graph | Use Export where surfaced; suitable for tooling and backup. |
| Terraform | Aligns with ARM-equivalent resources over time — confirm current panel labels in-app. |
| Bicep / ARM | May appear on roadmap as first-class export; watch release notes. |
| PNG / GIF | Same canvas tooling as other providers — Canvas tools. |
Shared detail: Shared features — §10–11.
4. Deploy to Cloud — Coming soon (Azure)
Deploy to Cloud from PinPole into a live Azure subscription is not yet generally available. Today you should:
- Design and simulate in PinPole.
- Export definitions or Terraform-oriented artefacts as exposed.
- Apply in Azure using your standard pipeline (ARM, Bicep, Terraform, Portal).
The Roadmap tracks cross-cloud deploy maturity; AWS has the reference live deploy flow today.
5. Cloud Terminal (Azure context)
Cloud Terminal is confirmed for Azure workspaces: use it during or around simulation to explore quota, topology, and configuration questions in natural language against the modelled architecture — same interaction pattern as AWS and GCP.
Details: Cloud Terminal.
6. Identity and governance
When PinPole adds first-party Azure deploy, expect Microsoft Entra ID (Azure AD)-backed auth patterns, least-privilege deployment principals, and clear separation between design-time simulation and subscription writes. Until then, follow your organisation’s policies for any manual deploy from exported artefacts.
7. Related docs
| Topic | Link |
|---|---|
| Shared workflows | Shared features |
| Canvas & agent | Canvas overview, AI Architect |
| Enterprise | Enterprise workflows |
Return to User guide overview · Shared features · AWS · GCP