Eido Build is installed from the Azure Marketplace into your own Azure subscription. Your work, your code and your credentials stay in your tenant.
What is installed#
The Marketplace offer creates these resources in a resource group you choose.
| Resource | What Eido Build uses it for |
|---|---|
| App Service | Eido Build itself. |
| Azure SQL database | Everything Eido Build stores: work items, documents, conversations, attachments. |
| Key Vault | Keys and secrets. |
| Storage account | Files, such as those passed to and from Cloud PCs. |
| Container registry | The worker image that runs inside agent sandboxes. |
| Application Insights and Log Analytics | Logs and monitoring. |
| Azure AI Foundry (optional) | The models your agents use, in your own tenant. |
Resources are named with a prefix you choose, eidobuild unless you change it, followed by the kind of resource and a unique suffix. You can change any name in the installer.
Who you need#
The installation is done in two parts, and they need different permissions. They can be the same person or two people.
| Step | Who can do it |
|---|---|
| Create the resources from the Marketplace | An Owner or Contributor on the subscription or resource group. |
| Run the short sign-in script in Cloud Shell | Somebody who can register apps in Microsoft Entra: an Application Administrator, Cloud Application Administrator or Global Administrator. They also need Contributor on the resource group. |
The script exists because an Azure deployment can only create Azure resources. Registering the app people sign in through is a Microsoft Entra operation, which needs an Entra role.
Choices to make#
Have answers ready for these before you start.
Region and names. Where the resources go and what they are called.
Size. The size of the App Service and the database.
Networking. Whether the database and Key Vault are reachable only over private endpoints, and whether Eido Build itself is. See Private networking.
Foundry. Whether the installer creates an Azure AI Foundry resource for you. It is ticked to start with. If you untick it you can connect your own afterwards.
What Eido Build needs to reach#
Eido Build must be able to make outbound HTTPS calls to:
| Address | Why |
|---|---|
license.eido.io | Licensing, and downloading updates. See Licensing. |
| Your repository host, GitHub or Azure DevOps | To work on your code. |
| Microsoft Entra | To sign people in. |
| Anthropic’s API | Only if you use Anthropic workbenches. |
| SendGrid | Only if you set up email. |
Nothing outside your network needs to reach Eido Build, apart from your own people’s browsers.