Getting generic "Error Occurred" when accessing Azure AD or assigning license

Question

Hello everyone,

I've been running into an issue where whenever I try accessing Azure AD or assigning a license, Azure will give me a notification just saying "Error Occurred" with no additional information. I first noticed in it an AAD tenant we were using for a side business we've been starting up after we downgraded our M365 licensing from Business Premium to Starter, but it seems to have carried over into my personal tenant. I'm not sure what could be causing it and nothing else is showing up in the Activity Logs. It's been making it very difficult to try out different Azure prototypes on my own.

Here are some examples of what I've been seeing:

For the side business, I had tried upgrading the AAD tenant back to P1, but it wouldn't take after assigning licenses in the M365 admin center (it wouldn't let me anywhere else). Also, I tried making a whole new personal Azure account as well with the same issue. Anyone have any ideas on what I else I could try? Any help is greatly appreciated!

Answer 1

Check the Audit logs, you might be able to get some additional details therein. https://learn.microsoft.com/en-us/azure/active-directory/reports-monitoring/concept-audit-logs

As a workaround, you can try performing the corresponding action via one of the PowerShell modules, or the Graph explorer tool.

Answer 2

Hi,

I am having the same issue with my own personal account on Azure. Whenever I open Azure AD, I get this "Error occurred" pop-up and many blades are just not available (example: I can't click on Licenses, Custom Domain Names etc).

I tried Vasil's suggestion above, the Audit Logs is clickable (not disabled) however, I get this error:

Unable to complete due to service connection error. Please try again later.

It happens to be somehow random: some days it works, some other days it doesn't.

Any suggestions are welcome.

Answer 3

Hi,

Seems like the problem is the PC that I use. Whenever I access the portal through my employer's laptop, I get the error.

If I use another PC, like a VM, there's no error - hence the problem is with some of the security aspects of the PC you're using I would say.

Answer 4

Perhaps this issue is solved already, but I encountered the exact same behaviour. It turned out that my local DNS sinkhole (Pihole) was blocking requests to main.iam.ad.ext.azure.com which made half of the AAD admin portal unavailable. After adding that specific hostname to the whitelist of Pihole, everything worked as it should.