SpecterOps / SpecterOps/AzureHound

Cannot process Subscriptions due to Multi-Factor authentication

Open
#197 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
961
Forks
148
Avg merge
22h 26m
Merged PRs (30d)
4

Description

Hello everyone,

For my Azure lab I have created a user account that is a member of a group called "Subscription Reader". I have granted this group Read permissions on my Azure Subscription.
There is also a VM under that Subscription and I have confirmed in its Access Management that the Read rights get inherited for it from the Subscription.

However when I run AzureHound (I have tried v2.12.1, as well as the rolling release (13th May 2026)) the resulting file will not contain the name of the aforementioned virtual machine.

.\azurehound.exe -r "{Refresh Token of the Subscription Readers Member}" list --tenant "{My Tenant}.onmicrosoft.com" -o azurehound.json

Checking the azurehound output I come across this:

ERR unable to continue processing subscriptions error="map[correlation_id:{removed} error:invalid_grant error_codes:[50076] error_description:AADSTS50076: Due to a configuration change made by your administrator, or because you moved to a new location, you must use multi-factor authentication to access '{removed}'. Trace ID: {removed} Correlation ID: {removed} Timestamp: 2026-05-17 19:29:03Z error_uri:https://login.microsoftonline.com/error?code=50076 suberror:basic_action timestamp:2026-05-17 19:29:03Z trace_id:{removed}>]"

Can anyone please explain, why AzureHound might fail to properly enumerate the objects?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the AzureHound list command with the supplied refresh-token flow and tenant option, then inspect the reported invalid_grant error with code 50076. The issue names no source files or tests, so the first task is to locate subscription processing and determine whether MFA-related authentication prevents VM enumeration.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, go
Domain
authentication, cloud, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.