Read Before you install first, so you have the right people and the answers the installer asks for.
Install#
-
Create it from the Marketplace
Find Eido Build in the Azure Marketplace and press Create. The wizard asks for the subscription, resource group and region, then for names, sizes, networking and tags.
The deployment creates Eido Build’s resources and starts the App Service on a small installer.
-
Open the installer link
When the deployment has finished, open its Outputs and follow the installerLink.
The link contains a key that is unique to your deployment. Only people who can see the resource group can see it. Opening it unlocks the installer for your browser.
-
Register
The installer shows the Azure environment it is in and your organisation as Azure has it. Fill in your company, name, email and phone, and register.
This registers the installation with Eido and gives it an install id.
-
Run the script in Cloud Shell
The installer shows a command for Azure Cloud Shell, with your subscription, resource group and App Service already filled in.
Somebody who can register apps in Entra, and who is a Contributor on the resource group, runs it.
-
Wait for Eido Build to deploy
When the installer sees that sign-in is in place, it downloads the current release of Eido Build, checks it, and deploys it over itself. The page follows this live.
-
Sign in
Eido Build replaces the installer. Whoever ran the script is its first admin. Sign in with your Microsoft work account.
What the script does#
The script does the Microsoft Entra work, and nothing else:
- it creates the app registration people sign in through
- it makes the person running it the registration’s owner and Eido Build’s first admin
- it gives admin consent for signing in
The app registration is used only to sign people in. Eido Build never calls anything as it, so it has no client secret, no certificate, and no credential of any kind.
The script never touches the database or the Key Vault, so with private endpoints there is nothing it has to open up.
If something goes wrong#
The deployment failed. The installer page says why, and offers Try again.
The installer says it is locked. You opened the site without the key. Go back to the deployment’s Outputs in the Azure portal and use the installerLink.
The installer link has stopped working. An installer that nobody finishes locks for good 90 days after the deployment. Delete the resource group and install again.
The script is refused. The person running it needs an Entra role that can register apps, and Contributor on the resource group. See Before you install.
For anything else, contact support with your install id.
Next#
After you install covers connecting your repository and setting up your first project.