Get started guide for Confluence administrator
In this guide, you will find step-by-step instructions to set up Azure DevOps Connector for Confluence integration for the entire Confluence instance.
Please ensure your organization permits OAuth for APIs.
If you are not a Confluence administrator, you need to pass this guide to the Confluence administrator and follow the Get Started guide for the end-user.
Getting the personal access token from Azure DevOps
You can follow How to create Microsoft Azure DevOps personal access token
Connect
Navigate to the Global Configuration page to configure the integration and default settings for all users and spaces in Confluence.
On the global navigation menu, click on Apps and select Manage Apps section.
Find our app in the user-installed apps list or click on Azure DevOps in the left-hand sidebar.
Copy your Azure DevOps base URL (it could be an On-Premise URL, but it should be accessible from the Internet). The example below shows the base URL, which starts with https://dev.azure.com and is followed by the organization. You can have multiple domains.
Follow this guide to create a new integration: How to setup Azure DevOps integration with Confluence Cloud
For security reasons, the Confluence administrator can change everything at once only, no partial changes are available.
Settings
Managing personal settings
Personal settings allow Confluence users to link their personal Azure DevOps accounts to set up the integration. This ensures that each team member can view the Azure DevOps information accessible to them on the Azure DevOps side.
How to connect personal Azure DevOps account for integration setup?
Confluence admin can manage personal settings usage within the global configuration page on Settings tab.
Personal settings are enabled by default for all Conflunce users with Use personal settings if they are set mode selected.
Use personal settings if they are set
In this mode, personal settings are used if a user has configured them. If a user connects their Azure DevOps account through personal settings, this connection will be used for rendering Azure DevOps macros within Confluence pages. However, if a user hasn’t set up their personal Azure DevOps integration, global or space-level settings will be used instead.
Use Case: This option is ideal when organizations want to provide users with the flexibility to manage their own personal integrations but also ensure that macros still work for users who haven’t set up their own personal connections. Users without personal settings can still view macros based on the global or space settings.
Use only personal settings
In this mode, only personal settings are used for Azure DevOps macros. If a user has not set up their personal Azure DevOps integration, they will not be able to see or render Azure DevOps macros within Confluence pages. In this case, global and space-level configurations are completely ignored, and macros will only render for users who have set up their own personal Azure DevOps integration.
Use Case: This option is useful for organizations that want tighter control over Azure DevOps data access, ensuring that only users who have authorized their Azure DevOps accounts can access and view the relevant macros.
Potential use cases
Please review Use cases
Integrate Azure DevOps with Jira
If you are looking for a way to bring Azure DevOps commits, builds, branches, and deployment information to the Jira issue screen, check out the Azure DevOps for Jira Atlassian Marketplace application.
Updated: