How customers first run AI Fabrix — from Azure Marketplace through tenant activation to optional first integration.
Why it matters
Enterprise AI Fabrix value depends on a trusted platform foundation. Architects and operators need a clear path: deploy the stack, activate the tenant, assign access, then let integrators make systems AI-ready.
How it works
Azure Marketplace deploy
→ Controller URL and outputs
→ Tenant activation wizard (until ACTIVE)
→ First session checklist (admin + optional developer login)
→ Build path (external systems, governance, certification)
Marketplace deployment provisions infrastructure. The tenant activation wizard configures identity, sizing, access model, and validation inside the controller portal. Integration developers start workstation setup in the Build path only after the platform admin confirms tenant ACTIVE.
Who does what
| Role | Focus |
|---|---|
| Cloud / procurement | Marketplace purchase and deploy |
| Platform admin | Wizard completion, environments, access |
| Integration developer | Developer workstation setup after ACTIVE |
| Architect | Operating model, adoption roadmap |
Example
A enterprise deploys AI Fabrix in Azure West Europe, completes tenant activation with Entra ID, confirms tenant ACTIVE, assigns an integration developer role, then starts the quickstart external system path in a dev environment.
After onboarding
Once the tenant is active, architects align pillar READMEs with pilot scope while integrators model one sandbox system end-to-end. Operators define who may upload protection rules and who approves certification reports before Role Assistant pilots.
Procurement and platform teams should archive Marketplace deployment outputs — controller URL, environment names, and admin contacts — alongside the first certification report for audit readiness.
Phased outcomes
| Phase | Done when… |
|---|---|
| Deploy | Marketplace stack reachable; admin can open controller portal |
| Activate | Tenant status ACTIVE; identity and environments configured |
| First session | Operators verified login, assigned roles, handed off to integrators |
| First integration | One external system certified in sandbox (see Build path) |
Executives track business readiness by phase — not by counting connected APIs. Each phase should produce artifacts operators can review without reading integration source code.
Sponsors should expect the first integration pilot to take longer than deploy alone — modeling, protection, and certification are part of trustworthy AI readiness, not optional integration polish.
Communication between admin and developer paths matters: platform admins should confirm tenant ACTIVE and environment names before integrators upload manifests or run certification in shared environments.
Include security and identity teams in the first-session checklist so Entra assignments and environment boundaries are agreed before any AI exposure discussion.
Business value
A single documented onboarding path reduces failed pilots, security gaps from skipping identity steps, and integrator confusion about when CLI and upload are supported.
Limits
Detailed Azure parameter names and internal resource topology vary by marketplace offer version — use the configure guides for step-by-step actions.