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.

Tenant activation wizard

Prev Next

After Marketplace deployment, complete the tenant activation wizard in the controller portal. Until the tenant is ACTIVE, main product routes stay gated.

Prerequisites

Where it happens

The wizard runs entirely in the controller web portal in your Azure deployment. It configures tenant consent, enterprise identity, capacity preset, access model, endpoints, and final platform validation.

Integration developers begin workstation setup after activation — see Developer workstation setup.

Steps

Work through the wizard in order:

  1. Tenant consent — Accept terms and confirm your organization owns this deployment.
  2. Identity setup — Connect enterprise identity (Entra ID) required for your access model.
  3. Size selection — Choose a capacity preset aligned with expected load (see Platform sizing).
  4. Access model — Configure how users and applications reach the platform.
  5. Access endpoint — Confirm URLs clients and integrations will use.
  6. Validation and deployment — Run platform validation; wait until activation reports success.

When finished, tenant status becomes ACTIVE and the main portal unlocks.

What done looks like

Wizard step Business outcome
Consent Tenant claimed by your organization
Identity Enterprise sign-in path ready
Size Capacity preset selected
Access model Who may authenticate and how
Endpoint Stable URLs for users and integrations
Validation Platform services healthy

If activation fails, note the step and error text — fix prerequisites (identity registration, DNS) and retry from that step.

Validate

  • Portal shows tenant status ACTIVE
  • Admin can open main portal routes without onboarding redirect
  • Optional: First session checklist

Limits

Wizard step labels may vary slightly by offer version — map portal text to the sequence above.

Common mistakes

Mistake Fix
Closing wizard before validation Complete the final validation step
Wrong identity permissions Fix identity inputs; re-run validation
Starting integration work before ACTIVE Finish wizard; developers use Build path after activation