Documentation Index

Fetch the complete documentation index at: https://docs.aifabrix.ai/llms.txt

Use this file to discover all available pages before exploring further.

Azure services created

Prev Next

When you deploy AI Fabrix from Azure Marketplace, Azure provisions a managed application stack in your subscription. Resource names and SKUs follow the parameters you enter during deployment — this page describes the typical components platform admins should expect.

Why it matters

Cloud and security teams need a shared map of what was created, which resources hold secrets, and where to monitor health before integrators connect systems or Role Assistants go live.

Typical resources

Azure service Role in AI Fabrix
Resource group Container for all deployment resources
App Service (controller) Admin portal, authentication entry, tenant activation
App Service (dataplane / processing) Integration runtime, governed capabilities, MCP compilation
Azure Database for PostgreSQL Platform metadata, integration config, operational records
Storage account Documents, sync artifacts, backup payloads as configured
Key Vault Secrets, certificates, connection strings resolved at runtime
Virtual network / subnets Private connectivity when enabled in the offer
Application Gateway or Front Door Public HTTPS entry when the offer includes edge routing
Log Analytics / monitoring Health signals, deployment diagnostics, audit support

Exact resource counts depend on marketplace offer version and sizing preset.

What this shows: Which Azure building blocks support the AI Fabrix platform after marketplace deploy.

What this is not: A bill of materials for every SKU variant — confirm names in your Azure portal resource group.

Mermaid diagram

After deployment

  1. Record the controller portal URL from deployment outputs.
  2. Complete Azure Marketplace installation Steps 2–5 (Entra, emergency admin, tenant wizard, personal admin).
  3. Hand off to integrators only after tenant status is ACTIVE.

Validate

  • Azure portal: every resource in the deployment resource group shows Succeeded
  • Key Vault: secrets accessible to App Services (no misconfigured access policies)
  • Monitoring: workspace receives logs from controller and dataplane apps

Limits

Private networking, multi-region, and exact App Service plan SKUs vary by offer. Treat this diagram as orientation — not a contractual topology.