Gather the following information which will be required for the Terraform configuration:

• Azure Subscription ID (GUID format)
• VPC ID (Virtual Network name)
• Two Subnet names:
  • subnet-1
  • subnet-2

Helpful Azure CLI commands:

# List your Virtual Networks
az network vnet list --query "[].{Name:name, ResourceGroup:resourceGroup}" -o table

# List subnets in a specific Virtual Network
az network vnet subnet list --vnet-name <your-vnet-name> --resource-group <your-resource-group> --query "[].{Name:name, AddressPrefix:addressPrefix}" -o table

Contact Cognition to receive:

1. An authentication token for pulling the hypervisor image
2. The Terraform configuration files customized for your environment

Once you share your environment information (from Step 1), we will provide these resources to you.

We can schedule a call to execute this step together. The process involves:

1. Extract the Terraform configuration files to a directory on your local machine:

   mkdir -p ~/devin-terraform && cd ~/devin-terraform
   # Extract files received from Cognition
   

2. Initialize the Terraform environment:

   terraform init
   

3. Review the planned infrastructure changes:

   terraform plan
   

4. Apply the configuration to provision the infrastructure:

   terraform apply
   

5. Confirm the changes when prompted.

After the Terraform script completes successfully, we will work together to:

1. Verify that the resources have been created in your Azure portal
2. Run a first Devin session to ensure connectivity to the required services
3. Debug any issues that arise with the support of Cognition team

Open the following URL in your browser:

https://login.microsoftonline.com/organizations/adminconsent?client_id=854d72e1-0257-44f3-9df1-4ed0cc8b89a7

You can check the permissions with the following command:

az account show
az ad user get-member-groups --id <user@example.com> --security-enabled-only

Once consent is granted, proceed with the following steps. You can check this by viewing applications within your Azure tenant.

az ad sp list --filter "appId eq '854d72e1-0257-44f3-9df1-4ed0cc8b89a7'" --query "[].{Name:displayName, AppId:appId, ObjectId:id}"

Devin requires a host instance to run isolated virtual machines for each session.

​

Instance Requirements

​

Security Group Rules

When Devin sessions are suspended, their state is compressed and stored.

​

2.1 Create an Azure Storage Account

1. In the Azure Portal, search for and select Storage Accounts.
2. Click + Create.
3. Set the following details:

   • Subscription: Choose your subscription

   • Resource Group: Select the resource group

   • Storage Account Name: Enter

     devin${CUSTOMER_NAME}${REGION}
     

     (Replace ${CUSTOMER_NAME} and ${REGION} with actual values)

   • Region: Choose your preferred region

   • Performance: Standard

   • Redundancy: Zone-Redundant Storage (ZRS)

4. Click Review + Create, then Create.

​

2.2 Configure Storage Account Access & CORS

1. Once created, navigate to your Storage Account → Settings → Resource Sharing (CORS).
2. Add a row with the following values:
   • Allowed Origins: *
   • Allowed Methods: GET
   • Allowed Headers: *
3. Click Save.
4. Navigate to the Access Control (IAM) section.
5. Click + Add and select Add role assignment.
6. Select the Storage Blob Data Contributor role.
7. Assign access to User, group, or service principal.
8. Select the Managed Identity created in the next step.
9. Click Review + assign.

​

2.3 Create a Managed Identity

1. Navigate to Managed Identities in the Azure Portal and click + Create.
2. Set the following details:
   • Subscription: Choose your subscription
   • Resource Group: Select the resource group where the Devin VMs were created
   • Region: Select the region containing the Devin VMs
   • Name: devin-vm-identity
3. Click Review + Assign.
4. Visit the resource page for the Devin VMs created above and click Security → Identity in the sidebar.
5. Select the User Assigned tab and click Add User Assigned Managed Identity.
6. Search for devin-vm-identity and click Add.
7. Repeat steps 4-6 for any new VMs created.

Run the following command:

curl -sSL https://api.devin.ai/hypervisor/setup?token=AUTH_TOKEN -o setup.sh && bash setup.sh

If user devices have a firewall, whitelist the following URLs:

• app.devin.ai
• api.devin.ai
• *.devinapps.com
  

Sample Azure WAF Rule