12 months ago, we learned how to access the managed API of Exchange Online – in order that our WPF application might show a screen with the associated office 365 user’s emails.
Now, we can dump all those “ancient” ideas (and at least 90% of the reason why we even needed to implement our own oauth2 endpoints, in an office 365 integrated world).
Folks have released an oauth2-powered version of the office 365 APIs. What is more, they have release tooling for visual studio that builds out the SP record in an AAD tenant suited to accessing those APIs, with their various permissions.
We make a web app, using MVC wizard in visual studio 2013 (update 1, augmented with extension for office 365 APIs). We use the most basic starter project, since the extension is going to rewrite it all anyways. We see the developer-time tooling, above, requiring that we logon to the AAD instances that will manage this application.
The tooling has us use the discovered APIs to pick ports…
and permission to access particular operations on those ports
Once we push the code to an azure website, we see the samples viewer of the APIs:
In the Auzre console, for our AAD, we see what got registered behind the scenes:
To this we add our azure website published API redirect URI
over https even (not shown).
This allows us to see our office365 mailbox:
Bit easier than using the OLDER “managed API” of Exchange: