Can you elaborate more on what you mean by "nothing works" and what you've tried? The sample image you include in your post does have a couple of issues. First, you're using the Office 365 connector, not the Azure Active Directory connector. The O365 connector will only return users with O365 licenses, which may be fine if you know that all users have an O365 license assigned. Just pointing out it's not technically AAD.
Second, the results in either case will be limited to what the user connecting to AAD has rights to see. If the user flow doesn't have rights to see everything, your results will be incomplete.
Third, the connector is limited to a maximum of 1000 results for each call (set in the config of the action) for the O365 connector. I think the AAD connector is similar, but I don't recall off hand. If your domain has more users than that, you will have to make use of the links returned in the results to get the next page of results and on through each page until there aren't more.
The next issue you're going to hit is that you're making a call to get the users, then 3 separate calls for each user to get their profile, their manager, and then their reports. This will be extremely slow. If you have a lot of users (i.e. several hundred or thousands), it will take hours to run. And it's possible you'll hit against rate limits on calls to the AAD API, which limits the number of calls per minute you can make to the AAD endpoint. So you'll have to include logic to watch for throttled error messages and have a timed retry.
It definitely can be done, as I have written a flow to do almost exactly this for a client. My flow didn't retrieve direct reports, but otherwise was the same. I'd share it if I was allowed, but it was proprietary work for them. I'm just saying it's likely going to end up being far more complicated than the start you have above by the time you account for everything.
