How to fix issues with macro rendering?
This guide will help you troubleshoot common issues that may arise if macro rendering fails.
“Connect to Azure DevOps”
Sometimes, you may come across an Azure DevOps macro created by another team member, but it might not render due to the following reasons:
The macro was set up at a personal level, with access restricted to its creator.
The integration is not set up on a space or global level.
The existing integration is broken due to an expired token or another issue or doesn’t cover the specific macro.
To complete the integration setup, connect the Azure DevOps instance to Confluence.
To resolve
If you are a space admin, you can set up the integration for a specific Confluence space. Go to “Space Settings” and provide a personal access token to connect your Azure DevOps instance. More details can be found here.
If you are a Confluence global admin, you can configure the integration and default settings for all users and spaces in Confluence. Find our app in the user-installed apps list and navigate to the global configuration page. More details can be found here.
If you are a Confluence user and want to setup the integration for your needs, ask your Confluence admin to enable personal settings within the global configuration page. Once enabled, click on your user avatar and pick Azure DevOps in the menu and connect your Azure DevOps account.
“No Access”
This message informs that the integration created with Azure DevOps (using a personal access token or login) doesn’t have access to the Azure DevOps entity.
There can be several reasons for this:
restricted access to Azure DevOps organisations or projects where this entity is located;
personal access token you are using doesn’t have the minimal scope of access;
the personal access token you are using has expired;
while logging in to Azure DevOps from Confluence, the user didn’t accept the permissions necessary to render a particular Azure DevOps macro.
To resolve
If you connected your Azure DevOps account via personal settings:
Ensure you are granted access to the Azure DevOps organisation or projects to which the Azure DevOps entity belongs. If required, request that the Azure DevOps organization or project admin provide you with access.
We may ask you to accept additional permissions if we release new macros. Disconnect and reconnect your account again to provide the required access.
If you use a personal access token for connection:
Ensure the Confluence or space administrator has configured the app using the valid Azure DevOps personal access token.
Check the personal access token’s scope of access; if the required scope is missing, update the token on the Azure DevOps side.
Check whether the personal access token you are using has access to the organisation where the Azure DevOps entity is located. If it doesn’t have access, create a new integration with access to the necessary Azure DevOps organisation on the space or global level.
Check your token's expiration date. Extend the expiration date on the Azure DevOps side if it has expired.
Updated: