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
• Resource group creation rights in the target subscription
• Marketplace offer access for your organization (procurement may approve the plan first)
• Global Administrator (or equivalent) later, for Microsoft admin consent in the tenant activation wizard
• Application Administrator (or Cloud Application Administrator) later, if identity setup in the wizard requires it

Where it happens

Deployment runs in your Azure subscription. When it succeeds, open the controller portal (URL in Step 3), then continue to tenant activation. See Azure services created for what was provisioned, including the enterprise application.

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. Typical time is about 20 minutes.

Azure creates a managed resource group (typically {name}-miso-rg). Details: Azure services created.

Step 2 — Enterprise application (automatic)

Azure creates the enterprise application automatically during Marketplace deployment. Do not open Entra ID to configure SSO, SCIM, or app assignments at this step. See Azure services created for names and typical resources. Everyday SSO consent is in the tenant activation wizard.

Step 3 — First login (emergency admin)

1. Open the controller portal. Prefer the URL in deployment outputs. If you construct it, start from the managed resource group that ends in -miso-rg: drop the -rg suffix, then add -miso before .azurewebsites.net.

You can also open the -miso-rg resource group in Azure and browse the App Service named *-miso-miso.

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 until the tenant is ACTIVE (about 10 minutes). Do not start integrations before that. If sign-in fails after logout, wait about 20 minutes — services may still be installing and URLs can change.

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 wait until activation completes. Developers then use Developer workstation setup.

What this shows: Marketplace deploy, automatic enterprise application, bootstrap login, tenant activation, then everyday SSO admin access.

What this is not: Integrator CLI or Role Assistant activation — those follow tenant ACTIVE. Manual Entra SSO is not an install step.

What done looks like

Validate

• Azure portal: deployment Succeeded
• Browser: controller portal loads at https://{name}-miso-miso.azurewebsites.net when the resource group is {name}-miso-rg
• Tenant status: ACTIVE before integration work
• SSO sign-in works for the personal admin after the wizard

Limits

Detailed Azure resource names and parameter labels vary by marketplace offer version. Confirm the App Service name in your -miso-rg resource group if the URL pattern above does not match. Deploy (~20 minutes) and tenant activation (~10 minutes) times are typical, not guaranteed.

Common mistakes