For repositories stored on Azure, the azure backend allows CMS users to log in directly with their Azure account. Note that all users must have write access to your content repository for this to work.

In order to get Decap CMS working with Azure DevOps, you need a Tenant Id and an Application Id.

  1. If you do not have an Azure account, create one here and make sure to have a credit card linked to the account.
  2. If you do not have an Azure Active Directory Tenant Id, set one up here.
  3. Register an application with Azure AD. Configure it as a Single tenant Web application and add a redirect URI (e.g. http://localhost:8080/)
  4. Add the Azure DevOps->user_impersonation permission for the created application.
  5. Grant admin consent for the application.
  6. Under Authentication->Implicit grant enable Access tokens for the application and click Save.
  7. Verify your Azure DevOps organization is connected to the same directory as your tenant under:<organization>/_settings/organizationAad
  8. Add the following lines to your Decap CMS config.yml file:
  name: azure
  repo: organization/project/repo # replace with actual path
  tenant_id: tenantId # replace with your tenantId
  app_id: appId # replace with your appId


  1. Pagination is not supported so some endpoints might return missing data

  2. Nested collection are partially supported as Azure doesn't allow renaming and editing in a single operation

Decap CMS

Maintained with care by PM TechHub and amazing contributors