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 integration developer have appropriate roles for your environments (Platform developer access explains the difference between platform roles and business roles).
- 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 and they may start the Build path.
What done looks like
| Role | Minimum ready signal |
|---|---|
| Platform admin | Tenant ACTIVE; environments visible; access assigned |
| Integration developer | Notified to start Developer workstation setup |
| Security / governance | Identity and activation steps documented for audit |
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 |