Skip to main content

Azure: Common integration issues/errors

Running into trouble with your Microsoft Azure integration, this article covers the most common issues and how to fix them

Written by Naomi Purvis

"We couldn't connect your Azure account"

You might see an error that looks something like this:

Why is this happening?

There can be a few reasons for this error, but nothing that can't be rectified. The most common causes are:

  • The credentials might be copied over incorrectly or entered into the wrong section

  • There's an issue with the Secret Key

  • There's an issue with the Reader role

  • There's a conflict in your Azure permissions, which is causing issues with setting up Roles, Secret Keys, new App Registrations, etc.

How can I fix it?

Not to worry, all of these issues can be fixed relatively easily, but it's worth making sure you have the necessary permissions to explore the troubleshooting steps outlined below.


Credential Issues

This is the easiest issue to fix and might seem self-explanatory, but these recommendations are to ensure nothing is missed.

1. Head to App Registrations by searching for app registrations in Azure:



2. Click on the App you set up for Intruder:



3. Copy the names and values of your Application (client) ID and Directory (tenant) ID, and ensure they are correct:



4. Navigate to Certificates & secrets and copy the secret key value:

⬇️

ℹ️ Note: The Secret Key value disappears after the first setup. If you didn't store it securely, you may need to generate a new one.


Role Issues

1. Head to Management groups by searching management groups in the Azure portal and click here:

2. Click the Tenant Root Group:

3. Click Access control (IAM):

4. Ensure the Intruder app has the Reader role:

5. If it's not listed here, you can simply click the + Add button at the top (highlighted above). This will then open a panel to Add role assignments > search Reader in the highlighted search box > click the Reader role > Next:


6. Click + Select Members > search Intruder (or the name of your App service for Intruder), then click on Intruder > Next :

7. Review the Role you're adding and click Assign at the bottom:

This should resolve any issues with Role permissions.


User Permission Issues

If you run into an error at any point in this section, then you might not have sufficient permissions and will need to check with your Azure administrator.

This one is a bit tougher to diagnose as it depends entirely on your organization's Azure configuration.

1. To check, head to Microsoft Entra ID by searching for Microsoft Entra ID in your Azure portal and clicking here:



2. Head to Users:


3. Select yourself (i.e. your own name/account):


4. Clicking into Azure Role Assignments and Assigned Roles will show your current roles, and you'll be able to see the permissions attached; if you're missing admin or have reader-only roles, you'll need to contact your Azure administrator for assistance:

⬇️



Extras

I need to generate a secret key

No worries, you can do so by clicking the buttons shown below:

How do I check if my Secret Key has expired?

If it has expired, you'll see a little warning icon, as shown below:

Did this answer your question?