Platform admin checklist after Marketplace install and tenant activation. Confirms the tenant is ready for governed work — portal and access only (no developer workstation steps on this page).
Prerequisites
- Azure Marketplace installation succeeded
- Tenant activation wizard completed — tenant ACTIVE
- Admin credentials for the controller portal
Where it happens
Checks use the controller portal and your operating model for environments and roles. Integration developers use a separate workstation setup guide after you confirm this checklist.
Steps
- Sign in to the controller portal with your admin account.
- Confirm tenant ACTIVE — no redirect to the onboarding wizard.
- Review environments — development, test, and production (or your naming) exist or can be created per policy.
- Assign platform access — ensure at least one Platform Admin and one Developer (or equivalent) have appropriate Role catalog bindings for your environments. See AI Fabrix roles for what each role gives, and Platform developer access for integrator CLI work.
- Confirm planned catalogs are present — the tenant does not start empty. In the Controller, open Roles, Dimensions, Resource types, and Evidence kinds. You should see AI Fabrix roles (including Everyone), domain values, resource-type categories, and Evidence kinds already seeded. Extend them for your enterprise; do not invent a parallel model from blank.
- Map Everyone for consume access — ensure the AI-Fabrix-Everyone group (or your IdP equivalent) includes authenticated users who need enterprise LLM and platform search. Everyone is consume-only — not admin and not CRM RBAC.
- Record environment URLs — note which URL and environment integrators should use for first connections (share with developers; do not run integration tools from this admin checklist).
- Communicate readiness — tell integration leads that tenant is ACTIVE, catalogs are seeded, and they may start the Build path.
- Plan channel activation — when business roles are ready for AI, continue to Connect assistant channels (conversation channels first).
What done looks like
| Role | Minimum ready signal |
|---|---|
| Platform admin | Tenant ACTIVE; environments visible; AI Fabrix roles assigned; catalogs visible |
| Integration developer | Notified to start Developer workstation setup |
| Security / governance | Identity and activation steps documented; Everyone group plan for LLM/search |
| End users (later) | Reach Assistants in conversation channels after Connect assistant channels |
Validate
- Portal: tenant ACTIVE; admin navigation works
- Environments visible and named consistently
- Integration lead assigned and notified
Limits
Exact role names in the controller UI depend on your edition and identity configuration.
Common mistakes
| Mistake | Fix |
|---|---|
| Integrators start before ACTIVE | Complete tenant wizard |
| Shared admin only, no developer access | Assign integration developer platform roles |
| Skipping environment scoping | Document dev vs prod before any upload |
| Admin tries to install Node or CLI | Use developer workstation guide in Build path |