Booth 6452 We’re sponsoring Microsoft Ignite San Francisco · 17–20 November See what we’re showing
Get started Contact sales
Get started

Install Eido Build in your Azure subscription

Eido Build runs in your own Azure subscription and installs from Azure Marketplace. It takes three steps, and one or two people.

Open in Azure Marketplace Watch a demo

One plan at $100 per user per month: see pricing. Need a private offer? Contact sales.

  1. 1

    Deploy from Azure Marketplace

    Choose a subscription, resource group and region, then Create.

  2. 2

    Open the installer link

    When the deployment finishes, copy installerLink from its Outputs.

  3. 3

    Finish on the installer page

    Register, run one command in Azure Cloud Shell, and sign in.

Before you start

You needWhy
An Azure subscriptionEido Build is deployed into it.
Owner on the subscription or resource group (or Contributor plus User Access Administrator)To press Create. The deployment gives Eido Build access to the resources it creates, and Contributor alone can’t assign access.
Application Administrator, Cloud Application Administrator or Global Administrator in Microsoft Entra, plus Contributor on the resource groupTo run the installer command in step 3, which sets up how your people sign in to Eido Build.

This can be one person or two. If it’s two, the second person takes over at step 3.

1 Deploy from Azure Marketplace

  1. Open Eido Build in Azure Marketplace and select Create.
  2. Basics. Choose the subscription, a resource group (we recommend a new one, just for Eido Build) and a region.
  3. Resource names. Leave the defaults unless you have a naming standard.
  4. Sizing. Keep the recommended P1v3 App Service plan and S1 database.
  5. Microsoft Foundry. Leave it ticked. Untick it only if you already have a Foundry you want Eido Build to use.
  6. Networking. Leave it off unless your database and Key Vault must be private. If you also restrict the App Service, you’ll need to be on that network (VPN, ExpressRoute or Bastion) to finish the install.
  7. Select Review + create, then Create.

2 Wait for the installer link

Everything after this starts from one link in the deployment’s Outputs, installerLink. Don’t close the page until you have it.

  1. Stay on the deployment page until it says Your deployment is complete.
  2. Select Outputs on the left.
  3. Copy the installerLink value and open it in your browser.

The installer link contains a key unique to your deployment. Only share it with whoever is finishing the install. It stops working 90 days after you deploy.

Clicked away from the deployment?

Nothing is lost. To get back to it:

  1. In the Azure portal, open Resource groups and select the one you chose in step 1.
  2. Under Settings, select Deployments.
  3. Select the Eido Build deployment.
  4. Select Outputs and copy installerLink. If it still says Deploying, wait for it to finish.

3 Finish on the installer page

The installer page walks you through the rest. Keep it open until it opens Eido Build for you.

  1. Check your Azure environment. The page shows the organisation, tenant, subscription, resource group and App Service it found. Check they’re right.
  2. Register with Eido. Enter your company, name, email and (optionally) phone, then select Register. Eido uses these to license this installation and to contact you about it. Note the install id it shows: support will ask for it.
  3. Run the installer in Azure Cloud Shell. This must be done by the person with the Entra role from Before you start. Select Copy, then Open Azure Cloud Shell (choose PowerShell if it asks), paste the command and press Enter. When it says Done, go back to the installer page. The page fills in your values; the command looks like this: 
    Invoke-RestMethod https://license.eido.io/install.ps1 -OutFile install-eidobuild.ps1; ./install-eidobuild.ps1 -SubscriptionId '<subscription>' -ResourceGroup '<resource group>' -AppServiceName '<app service>'
  4. Sign in. The installer page installs Eido Build, shows Installed, and opens Eido Build when it’s ready. Sign in as the person who ran the command: they are Eido Build’s first admin.
What the installer command does, and doesn’t do

It downloads Eido’s install script from license.eido.io and runs it in your Cloud Shell, as you. It sets up how your people sign in to Eido Build, and nothing else. It talks only to Azure and Microsoft Entra, never to Eido, and it’s safe to run again.

  • Creates an app registration called Eido Build (<App Service name>), for sign-in with Microsoft Entra ID. Your organisation’s accounts only, with no secret or certificate.
  • Turns on Assignment required and assigns you, so only people you assign can sign in.
  • Makes you an owner of the app registration, so you can manage it later.
  • Grants admin consent for five delegated Microsoft Graph permissions (openid, profile, email, offline_access, User.Read), which only ever act as the signed-in person, on their own profile.

It does not create or change any Azure resources or role assignments, grant any application permissions, or create any secrets, passwords or certificates.

What gets created in Azure

Everything goes into the resource group you chose. The App Service has its own managed identity, with roles scoped to just the resources it needs: nothing outside the resource group, and no passwords or keys.

ResourceWhy
App Service plan and App ServiceThe Linux server Eido Build runs on, and the app itself. HTTPS only.
SQL server and databaseEido Build’s data. Microsoft Entra sign-in only, no SQL passwords, and 35 days of point-in-time restore.
Key VaultKeeps Eido Build’s secrets.
Storage accountEido Build’s files. No shared keys or public access.
Container registryHolds the image Eido Build’s AI agents run in.
Microsoft Foundry and projectWhere the agents run, if you leave it ticked. No models are deployed: you add them later.
Log Analytics and Application InsightsLogs for 30 days, plus performance and error telemetry.
Managed identitySet aside for Windows 365, if you set it up later. It has no access to anything.

If you turn on private endpoints, it also creates a virtual network with two subnets, private endpoints for the SQL server and Key Vault (and the App Service, if you restrict it), and private DNS zones unless you choose ones you already have.

Once you’re in

Add your people

Each person needs both of these:

  1. In the Microsoft Entra admin center, open Enterprise applications, then Eido Build (<App Service name>), then Users and groups, and assign them.
  2. In Eido Build, add them under Admin > Users with the same email.

Next steps

  • AI models. Add them from Eido Build’s Foundry screen.
  • Windows 365 (optional). Admin > Windows 365 > Setup. This needs a Global Administrator, because it grants permissions to Eido Build’s identity.
  • Updates. Never automatic. An admin applies them from Admin > Updates.

The rest is in the documentation. docs.eidobuild.com has the user guide, the administration guide, and installing, updating and licensing in full.

If something goes wrong

What you seeWhat to do
The installer page says it’s locked.Open the full installerLink again from the deployment’s Outputs (step 2).
The installer page says it’s expired.It lasts 90 days after you deploy. Contact support.
The script says to switch directory.Switch Cloud Shell to the tenant Eido Build is in, then run the command again.
The installer page says “The installer stopped”.Select Try again.
“There is no Eido Build user with that email”.Add the person under Admin > Users, and assign them in Enterprise applications.
Anything else.Email support@eido.io with your install id.

Want to see it working before you install? Watch a demo: a feature built, a bug fixed and a project set up with its guard rails.