no longer returns all domains after Microsoft update

[massimiliano-dalcero]

Hello,
first of all, thank you for your work on this project.

After the recent Microsoft change to the Get-FederationInformation cmdlet in Exchange Online (see: https://techcommunity.microsoft.com/blog/exchange/important-update-to-the-get-federationinformation-cmdlet-in-exchange-online/4410095), the command now only returns the domain passed as a parameter, instead of all accepted domains as it did before.

This breaks existing scripts that relied on the previous behavior.

Is there any plan to release a new version or implement a workaround to restore the old functionality?

Thanks in advance, and best regards.

[kmsec-uk]

Thank you for the kind words and for raising the issue, I didn't know about this breaking change! I will take a look into this later next week to see if there is a feasible fix, apologies for the loose timeline as I am on holiday.

In the meantime, AADInternals OSINT page is working as expected so I encourage you to use that while this project is broken in the meantime!

[massimiliano-dalcero]

Thank you for your reply, and no worries at all about the timeline; much appreciated, especially while you're on holiday!

Just a quick note: the OSINT tool on the AADInternals page had actually stopped working a few days ago, returning only a single domain (the one passed as input). Interestingly, it started working again recently, as if something was adjusted behind the scenes to handle the change.
Not sure if it's a workaround or a temporary behavior, but definitely curious!

Thanks again, and enjoy your time off!

[kmsec-uk]

I had a look into this today. I am unable to identify a feasible fix for now but I am keeping this issue open.

In the meantime, the project has been updated with a banner to emphasise this broken feature, both on the README on GitHub and a warning on the site.

The original workaround at AADInternals didn't apply to this tool as the user agent for azure-osint.kmsec.uk was already set correctly, which is probably why I didn't personally notice any issues up until your comment here.

I'm hopeful that there is some workaround. An issue is open at AADInternals and I am tracking it for feasible workarounds. I will also keep exploring other options myself.