Configure pool settings

Choose the Dev Center project for your Managed DevOps Pool. During pool creation, you can create a Dev Center and Dev Center project if you don't have one.

The dev center project is specified by the devCenterProjectResourceId property.

    "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
    "contentVersion": "1.0.0.0",
    "resources": [
        {
            "name": "fabrikam-managed-pool",
            "type": "microsoft.devopsinfrastructure/pools",
            "location": "eastus",
            "tags": {},
            "properties": {
                ...
                "devCenterProjectResourceId": "/subscriptions/subscription_id_placeholder/resourceGroups/fabrikam-managed-devops-pools/providers/Microsoft.DevCenter/projects/fabrikam-dev-center-project"
            }
        }
    ]
}

You can retrieve the devCenterProjectResourceId for your Dev Center project in the Azure portal by using the JSON View from the overview page of your Dev Center project, or you can retrieve it using the Azure CLI to query the project for its id property. In the following example, the devCenterProjectResourceId is retrieved from a Dev Center project named fabrikam-dev-center-project in the fabrikam-managed-devops-pools resource group.

 az devcenter admin project show --name fabrikam-dev-center-project --resource-group fabrikam-managed-devops-pools --query "id"

The dev center project is specified by the devcenter-project-id parameter when creating or updating a pool.

az mdp pool create \
   --devcenter-project-id /subscriptions/aaaa0a0a-bb1b-cc2c-dd3d-eeeeee4e4e4e/resourceGroups/resourceGroupName/providers/Microsoft.DevCenter/projects/devCenterProjectName
   # other parameters omitted for space

You can retrieve the devcenter-project-id for your dev center project in the Azure portal by using the JSON View from the overview page of your dev center project, or you can retrieve it using the Azure CLI to query the project for its id property. In the following example, the devcenter-project-id is retrieved from a dev center project named fabrikam-dev-center-project in the fabrikam-managed-devops-pools resource group.

 az devcenter admin project show --name fabrikam-dev-center-project --resource-group fabrikam-managed-devops-pools --query "id"

If your Managed DevOps Pool is configured for a single Azure DevOps organization, you can specify the organization in pool settings.

If your pool is configured for multiple organizations, the Azure DevOps organization setting is not present in pool settings. To configure your pool for use in multiple organizations, go to Settings > Security, and configure Use pool in multiple organizations.

Azure DevOps organization is configured using the organizations list in the organizationProfile section. In the following example, a Managed DevOps Pool is configured for all projects in a single organization, with a parallelism of 4. For an example of configuring multiple organizations, see Use pool in multiple organizations.

{
    "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
    "contentVersion": "1.0.0.0",
    "resources": [
        {
            "name": "fabrikam-managed-pool",
            "type": "microsoft.devopsinfrastructure/pools",
            "apiVersion": "2024-10-19",
            "location": "eastus",
            "properties": {
                ...
                "organizationProfile": {
                    "organizations": [
                        {
                            "url": "https://dev.azure.com/fabrikam-tailspin",
                            "projects": [],
                            "parallelism": 4
                        }
                    ]
                }
            }
        }
    ]
}

Azure DevOps organization is configured using the organizations list in the organization-profile parameter. In the following example, a Managed DevOps Pool is configured for all projects in a single organization, with a parallelism of 4. For an example of configuring multiple organizations, see Use pool in multiple organizations.

az mdp pool create \
   --organization-profile organization-profile.json
   # other parameters omitted for space

The following example shows the organizations list in the organization-profile.json file.

{
  "AzureDevOps": {
    "organizations": [
      {
        "url": "https://dev.azure.com/fabrikam-tailspin",
        "projects": [],
        "parallelism": 4
      }
    ],
    "permissionProfile": {...}
  }
}

Maximum agents is configured in Pool settings for an existing pool, and on the Basics tab when creating a pool.

Maximum agents is configured using the maximumConcurrency property. In the following example, Maximum agents is set to 4.

{
    "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
    "contentVersion": "1.0.0.0",
    "resources": [
        {
            "name": "fabrikam-managed-pool",
            "type": "microsoft.devopsinfrastructure/pools",
            "apiVersion": "2024-10-19",
            "location": "eastus",
            "properties": {
                ...
                "maximumConcurrency": 4
            }
        }
    ]
}

Maximum agents is configured using the maximum-concurrency parameter when creating or updating a pool. In the following example, Maximum agents is set to 4.

az mdp pool create \
   --maximum-concurrency 4
   # other parameters omitted for space

Choose Change size to view and select an Azure virtual machine size that is available in your Azure region. Agent sizes (SKUs) with available Managed DevOps Pools quotas are marked as Available. You can request more quota for Not Available SKUs. Once a quota request for a Not Available SKU is approved, it will then be listed as Available. Learn more about Managed DevOps Pools quotas.

Agent size is configured using the sku property in the fabricProfile section. In the following example, a Standard_D2ads_v5 VM size is specified.

{
    "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
    "contentVersion": "1.0.0.0",
    "resources": [
        {
            "name": "fabrikam-managed-pool",
            "type": "microsoft.devopsinfrastructure/pools",
            "apiVersion": "2024-10-19",
            "location": "eastus",
            "properties": {
                ...
                "fabricProfile": {
                    "sku": {
                        "name": "Standard_D2ads_v5"
                    }
                }
            }
        }
    ]
}

Agent size is configured using the sku property in the fabricProfile section when creating or updating a pool. In the following example, a Standard_D2ads_v5 VM size is specified.

az mdp pool create \
   --fabric-profile fabric-profile.json
   # other parameters omitted for space

The following example shows the sku section of the fabric-profile.json file.

{
  "vmss": {
    "sku": {
      "name": "Standard_D2ads_v5"
    },
    "images": [...],
    "osProfile": {...},
    "storageProfile": {...}
  }
}

OS disk type is configured in Pool settings for an existing pool, and on the Basics tab when creating a pool.

OS disk type is configured using the osDiskStorageAccountType property in the storageProfile section. In the following example, a Standard OS disk type is specified. Choose Standard, StandardSSD, or Premium.

{
    "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
    "contentVersion": "1.0.0.0",
    "resources": [
        {
            "name": "fabrikam-managed-pool",
            "type": "microsoft.devopsinfrastructure/pools",
            "apiVersion": "2024-10-19",
            "location": "eastus",
            "properties": {
                ...
                "storageProfile": {
                    "osDiskStorageAccountType": "Standard"
                }
            }
        }
    ]
}

In the following example, a Standard OS disk type is specified. Choose Standard, StandardSSD, or Premium.

OS disk type is configured using the osDiskStorageAccountType property in the storageProfile section in the fabric-profile parameter. In the following example, a Standard OS disk type is specified. Choose Standard, StandardSSD, or Premium.

az mdp pool create \
   --fabric-profile fabric-profile.json
   # other parameters omitted for space

The following example shows the storageProfile section of the fabric-profile.json file.

{
  "vmss": {
    "sku": {...},
    "images": [...],
    "osProfile": {...},
    "storageProfile": {
      "osDiskStorageAccountType": "Standard",
      "dataDisks": []
    }
  }
}