Articles on: Azure Devops - Onboarding

Possible incorrect permissions

This can happen for a few reasons. Let's narrow them down.

1) Check which account you're authenticated as. Login to Backrightup and click here:

Check which account you have authenticated with

2) Now check that exact account is in the Project Collection Administrators group (under Organisation settings - if you cant see that link in your Azure Devops it means you have incorrect permissions. Your account needs to be in this group. They MUST match)
project collection administrators group
3) Next check your account has repo access. The first image shows an account with repo access. The next shows an account without repo access. Note the left hand menus and the lack of repos menu item. This means that administrators in your organisation have likely broken the inheritance structure of the permissions and given repos different access to the rest of the org.

Repo access

No repo access

4) Next check that you have the following setup under 'Policies':

Conditional Access policies and Third Party apps

a) IP Restrictions (Disable Azure Active Directory Conditional Access Policy)

You can setup IP restrictions on your Azure Devops Tenant by enabling the Azure Active Directory Conditional Access Policy. Please check that you are not restricting access via IP Address otherwise Backrightup may not be able to connect.

b) Third-party application access via OAuth (Enabled)

We connect via oAuth as this is safest for all parties - using rotational keys expiring every hour. Please enable this for Backrightup to work

5) Check your license of your authenticated user is NOT "stakeholder". It should be basic license or above:

If you have done the above steps correctly and you are still receiving the incorrect emails permissions or not seeing new backups occur, please reach out to us so we can do a video call and help you

Updated on: 08/11/2022

Was this article helpful?

Share your feedback


Thank you!