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 open the controller portal before integrators connect systems or Role Assistants go live.
Typical resources
Marketplace deployment creates these components. You do not configure them one by one in Entra ID or the Azure portal after the offer succeeds.
| Azure service | Role in AI Fabrix |
|---|---|
| Managed application | Marketplace offer instance in your subscription |
| Resource group | Usually {name}-miso-rg — container for deployed resources |
| Enterprise application | Created automatically in Microsoft Entra ID for the deployment. Do not configure SSO, SCIM, or assignments here at install time. |
| Managed identity | Platform identity App Services use to reach Key Vault and Azure |
| App Service (controller) | Admin portal and tenant activation — named {name}-miso-miso |
| App Service (identity) | Sign-in service for the emergency admin account |
| 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 | Network isolation for App Services and data services |
| Log Analytics / monitoring | Health signals, deployment diagnostics, audit support |
Exact resource counts depend on marketplace offer version and sizing preset. Processing (dataplane) App Service is typically added during tenant activation, not always present immediately after Marketplace deploy.
Controller portal URL
Open the controller from deployment outputs, or form the URL from the managed resource group name: drop the -rg suffix, then add -miso before .azurewebsites.net.
Resource group acme-miso-rg → controller https://acme-miso-miso.azurewebsites.net
In the Azure portal: Resource groups → {name}-miso-rg → App Service {name}-miso-miso → Browse.
What this shows: Which Azure building blocks support the AI Fabrix platform after marketplace deploy, including the automatic enterprise application and how to open the controller.
What this is not: A bill of materials for every SKU variant, and not a manual Entra SSO runbook — confirm names in your Azure portal resource group.
After deployment
- Open the controller portal using the URL pattern above.
- Continue Azure Marketplace installation from first login (emergency admin), then the tenant wizard and personal admin.
- Hand off to integrators only after tenant status is ACTIVE.
Validate
- Azure portal: every resource in the
{name}-miso-rggroup shows Succeeded - Entra: enterprise application exists without a separate post-deploy configuration step
- Browser:
https://{name}-miso-miso.azurewebsites.netloads the controller - Key Vault: secrets accessible to App Services (no misconfigured access policies)
Limits
Private networking, multi-region, and exact App Service plan SKUs vary by offer. Treat this diagram as orientation — not a contractual topology. If your resource group name does not end in -miso-rg, use the App Service named *-miso-miso in that group instead of the URL formula.