Airtable Sync integration: Azure DevOps

Learn how to use the Airtable Sync integration feature to bring information from Azure DevOps into Airtable as a new table in your base. This integration allows you to sync work items (tasks, epics, bugs, etc.) from your Azure DevOps projects directly into Airtable tables.

Prerequisites

Before setting up Azure DevOps sync, you must ensure that third-party application access via OAuth is enabled in your Azure DevOps organization settings. Additionally, you’ll need to have the appropriate permissions in Azure DevOps to access the projects and work items you want to sync into Airtable.

Setting up an Azure DevOps sync in Airtable

This integration works best when your Azure DevOps instance is organized under a single project for the entire organization, which is one of Microsoft's recommended configurations.

1. Add a new synced table - Start by clicking the + symbol next to your list of tables. Then, under “Add from other sources,” click the XX more sources… option. Finally, select Azure DevOps.

2. Connect to Azure DevOps - Select an existing Azure DevOps account (if you've already connected), or link to a new Azure DevOps account.

   1. Make sure you're signed in to Azure DevOps with the correct account that has access to your organization and projects.

3. Once connected, you'll be able to select:

   1. Your Azure DevOps organization

   2. The project containing the work items you want to sync

4. Configure sync settings - Choose which work items to sync by configuring:

   1. Work item type - Tasks, Epics, Bugs, User Stories, Features, etc.

   2. Query/Filter - Select specific work items based on conditions (similar to Azure DevOps queries)

5. Select fields to sync - You'll be presented with two sync options:

   All fields from Azure DevOps, including any fields added in the future

   Specific fields from Azure DevOps

6. If you choose to sync specific fields, you can toggle individual fields including:

   1. Standard fields: Work Item ID, Title, Description, State, Assigned To, Area Path, Iteration Path, Priority, Tags, Created Date, Changed Date, Work Item Type

   2. Relationship fields: Parent, Related Work Items, Child Items

   3. Custom fields: Any custom fields defined in your Azure DevOps project

7. Create synced table - Before creating your synced table, configure these settings:

   1. Sync frequency: Manual or automatic (as often as every 5 minutes)

   2. Deleted records: Whether to remove records when work items are deleted in Azure DevOps

8. Click Create table to begin the initial sync. The operation will retrieve all work items matching your criteria and generate Airtable records.

Two-way syncing with Azure DevOps

Two-way sync capabilities are available in beta. This allows for:

• Creating new work items in Azure DevOps from Airtable

• Updating existing work items when changes are made in Airtable

Note: Two-way sync requires additional automation actions to be enabled.

It’s important to know that certain fields cannot be edited in ADO two-way syncs. These include Assigned to, Created date, Created by, Node name, Changed date, Authorized as, Authorized date, Watermark, Rev, Changed by, Any field starting in Board, Activated by, Closed by, Resolved by, and any field ending in “count.”

Security and authentication

• OAuth scopes - Airtable requests the following permissions when connecting to Azure DevOps:

  • Read work items and queries

  • Write work items (for two-way sync and automation actions)

  • Access user profile information

• Data security

  • All data is transmitted securely via HTTPS

  • OAuth tokens are stored encrypted at-rest in Airtable's databases

  • Airtable only accesses work items and projects that the connected user has permission to view

Common Azure DevOps troubleshooting

• "Unknown error (401)" during setup - This typically means third-party application access via OAuth needs to be enabled in Azure DevOps:

  • Go to your Azure DevOps organization settings

  • Navigate to Policies

  • Enable Third-party application access via OAuth

• Sync stops working - If the sync stops working, check that:

  • The connected Azure DevOps account is still active

  • The user still has access to the projects and work items

  • OAuth permissions haven't been revoked

• Missing work items - If you find that you have missing work items, then ensure:

  • The connected user (who set up the sync configuration) has permission to view the work items

  • Work items meet the filter/query criteria

  • You haven't exceeded the sync limit (10,000 items)

FAQs