Integrations
Bring your own Azure
Run agent sandboxes inside your own Azure subscription - connect in a few clicks, with no secrets to hand over and full visibility into what we can access.
By default, managed agents run on Agent Chatham’s own sandbox infrastructure, powered by Daytona.
On the Enterprise plan, you can run every agent sandbox inside your own Azure subscription - you keep full ownership of the compute, the network boundary and data residency. Sandboxes run on Azure Container Apps Sandboxes, Microsoft’s microVM-isolated compute built for AI agents.
Azure BYO is an Enterprise plan feature. On other plans the Azure tile shows the option, but Connect is disabled - talk to us if you need it.
Before you start
In the Azure tenant you want to connect, you’ll need:
-
Cloud Application Administrator (or higher, such as Global Administrator) in Microsoft Entra ID, to accept Agent Chatham in your tenant.
-
Owner on the resource group agents will run in - or on the subscription, if you create a new resource group during the deployment.
-
The Microsoft.App resource provider registered on the subscription. This is a one-time step per subscription. With the Azure CLI:
az provider register -n Microsoft.App --waitOr in the Azure portal: Subscription → Resource providers → Microsoft.App → Register.
You don’t create a service principal, copy a secret or type a tenant ID. Microsoft tells us your tenant when you accept.
Connecting
On the Integrations page, under Infrastructure, open the Azure tile and click Connect.

- Accept Agent Chatham. A new tab opens on Microsoft’s sign-in page. Sign in as a tenant administrator and click Accept. This adds our app to your tenant - you’ll find it as Agent Chatham Sandboxes under Microsoft Entra ID → Enterprise applications. No API permissions are requested or granted.
- Deploy to Azure. The same tab moves on to the Azure portal with our template loaded. Choose the Subscription and Resource group (existing or new), then click Review + create → Create. The resource group’s region is where sandboxes run.
- Connect. Back on the Integrations page, the dialog waits for the deployment. Once Azure gives us access to the resource group - usually within a few minutes, while the role assignments propagate - the account connects on its own and the tile shows the resource group’s name. You can close the portal tab.
The dialog keeps checking for 30 minutes. If Azure takes longer, click Check now. Running Connect again is safe: deploying the template a second time to the same group changes nothing.
What the template does
The template is plain ARM, deployed with your own identity into the one resource group you choose. It creates nothing outside that group and nothing at the subscription level.
| What | Scope | Purpose |
|---|---|---|
Custom role Agent Chatham Sandbox Operator (<group>, …) | Resource group | Read the group, and create, update and delete sandbox groups in it (Microsoft.Resources/subscriptions/resourceGroups/read, Microsoft.App/sandboxGroups/read, write, delete) |
| Assignment of that role to our app | Resource group | Control plane: manage sandbox groups |
Assignment of the built-in Container Apps SandboxGroup Data Owner role to our app | Resource group | Data plane: manage sandboxes and disk images |
Tag agentchatham-org = <your organization id> | Resource group | How we find the group you deployed to. Merged into your existing tags without overwriting them |
Troubleshooting
| Message | What to do |
|---|---|
| “Access was not granted. An administrator of your Microsoft Entra tenant has to accept Agent Chatham.” | Consent was cancelled, or the account that signed in isn’t an administrator. Have a Cloud Application Administrator click Connect again. |
| “Register the Microsoft.App resource provider on the subscription (Subscription → Resource providers), then check again.” | Register the provider as described in Before you start, then click Check now. |
| “That resource group is in a region where Azure Container Apps Sandboxes are not available.” | Deploy the template to a resource group in a region that supports Container Apps Sandboxes. |
| “The template was deployed to more than one resource group.” | More than one group carries the agentchatham-org tag. Remove it from all but one, then click Check now. |
| “We have not found the resource group yet.” | The dialog stopped checking after 30 minutes. Check the deployment in the portal (Resource group → Deployments), then click Check now. |
| “This sign-in did not start from your Integrations page, or took too long.” | The sign-in expired. Start again from Connect on the Integrations page. |
What gets created in your subscription
Nothing is created until an agent launches. Then, inside your resource group:
Microsoft.App/sandboxGroups- one per workspace.- Sandboxes (the agent VMs) and disk images inside those groups.
Sandbox egress policies default to deny all - agents reach only what their configuration allows.
Azure and Daytona together
If your organization also brings its own Daytona, a New agents run on switch under the Infrastructure heading picks which account new agents use - see Azure and Daytona together.
Disconnecting
Disconnect refuses to run while agents are still placed on the account. Once they’re gone, it deletes the workspace resources we created and takes the account out of service. Your resource group is never deleted. If your plan changes, an already-connected account keeps working and can always be disconnected.
To revoke access on the Azure side as well, remove these from your tenant:
- the two role assignments and the Agent Chatham Sandbox Operator custom role on the resource group;
- the
agentchatham-orgtag on the resource group; - the Agent Chatham Sandboxes enterprise application under Microsoft Entra ID → Enterprise applications.