Azure Marketplace installation

Deploy AI Fabrix from the Azure Marketplace managed application. This creates the platform in your Azure subscription before the tenant activation wizard runs.

Prerequisites

• Azure subscription with permission to deploy marketplace offers
• Global Administrator or equivalent to approve enterprise application and SSO steps later
• Application Administrator (or delegated admin) for Entra ID enterprise app configuration
• Resource group creation rights in the target subscription
• Marketplace offer access for your organization (procurement may approve the plan first)

Where it happens

Deployment runs in your Azure subscription. It provisions the platform stack your organization will operate — controller portal, processing services, secrets storage, and supporting infrastructure. Names and regions follow the parameters you enter in the offer.

When deployment succeeds, record the controller portal URL and any onboarding outputs your cloud team needs for the next step.

See Azure services created for a diagram of typical resources.

Five-step admin flow

Step 1 — Marketplace deployment

1. Open Azure Marketplace — find the AI Fabrix offer and start Create (or use your organization's private catalog).
2. Choose subscription and region approved by your cloud team.
3. Set deployment parameters — infrastructure name, admin contact, and sizing inputs shown in the offer.
4. Review and deploy — wait until Azure reports deployment Succeeded with no failed resources.
5. Record outputs — save the controller portal URL and deployment notes.

Azure creates a resource group with App Services, database, storage, networking, Key Vault, and monitoring resources. Details vary by offer version — see Azure services created.

Step 2 — Configure enterprise application

In Microsoft Entra ID:

1. Locate the AI Fabrix enterprise application created by deployment.
2. Configure SSO per your identity standards (SAML or OIDC as shown in the offer documentation).
3. Enable SCIM provisioning when your deployment includes automated user sync.
4. Assign initial admin groups who will run tenant activation — not every employee on day one.

Step 3 — First login (emergency admin)

1. Open the controller portal URL from deployment outputs.
2. Sign in with the emergency admin account provided in onboarding materials.
3. Change the mandatory password immediately and store credentials in your enterprise vault.
4. Limit use of the emergency account to break-glass scenarios — personal SSO accounts replace it in Step 5.

Step 4 — Tenant activation wizard

Complete the tenant activation wizard:

• Custom domain and TLS where required
• Capacity / scale preset for your pilot
• Firewall and private networking options per security review
• Confirm tenant reaches ACTIVE before integrators connect systems

Step 5 — Create personal admin user

1. Create a named administrator account tied to corporate identity.
2. Assign platform admin role through Entra group membership.
3. Verify SSO sign-in succeeds for daily operations.
4. Retire routine use of the emergency admin account.

Integrations and Role Assistants wait until tenant activation completes and developers complete Developer workstation setup.

What this shows: The admin path from marketplace deploy through identity setup, bootstrap login, tenant activation, and everyday SSO admin access.

What this is not: Integrator CLI steps or Role Assistant activation — those follow after tenant ACTIVE.

What done looks like

Capacity preset selection may continue in the tenant activation wizard — follow your offer's UI.

Validate

• Azure portal: deployment Succeeded
• Entra: enterprise application assignments include platform admins
• Browser: controller portal URL loads; SSO sign-in works for personal admin
• Tenant status: ACTIVE before integration work

Limits

Detailed Azure resource names and parameter labels vary by marketplace offer version.

Common mistakes