The title probably got your attention, and it should. This finding was reported to Microsoft in April 2022 and has never been picked up. Therefor this is still exploitable in all Azure AD environments using Privileged Access Groups. How it started Well, like most of the time, it all starts with a simple…