Azure API and tokens issued by azure AD

Question

anyone know of a sample that showcases the azure API management/delivery feature consuming (access) tokens issued by Azure AD?
is there a reasons why its not even a sensible thing to conceive? (it seems obvious...but perhaps I have a disconnect somewhere)

Answer 1

perhaps a useful comment flows from this:
The documentation (at github, on AAD samples) is very engineering centric. Its very correct; very precise, overly so. It embeds best practices within (without teaching how to think about which of the 10 flows are proper, for different scenarios); and sometimes
calls things opened connect, sometimes oauth2. Distinguishing the differences is the subtle art of interpreting Microsoft engineering speak.
I learned 10 years not to program Microsoft apps in a way that is not demonstrated by an official sample. Thus the lack of a AAD sample of Azure API is problematic. I don't know (having been burned 100 times) that the OAUTH2 mentioned in the API docs is
compatible with one of the oauth2 flows of AAD sample land.
call me over thinker, if you like. But, this is what its like to be on the en d of the fragmented, drip drip, ALL change EVERY  3 years, communications style in windows/azure/win32 comsec.
i suspect the fix is another attempt at a best practices document - with best practice teaching samples - similar to those that so excellently rounded out WIF work, in the last generation of efforts.