Im having problems selling Azure AD - mostly because its so good. Its so good it sets in a wave of creepiness in many a person whose job depends on keeping membership and association management issues propriety. Yes, controlling membership is often that only ting keeping some US industry from becoming open and commodity - and the membership is used as protectionism (nothing new there!)
I'm countering the arguments by saying that Microsoft, compared to Google, is sensitive to its partner channels - knowing they have to add some 20% of value. In the case of Azue AD's graph, being odata/atom-based, this means that such as CRM will also offer an odata endpoint which, by the magic of ATOM references points to Azure AD entities in the inheritance relationships underying the now-extended schema, enables an Azure AD "User" to become a RealtyUser (say), when CRM adds/extends the User record with strange realty IDs (due to the crazy way such are managed by 50 different US states, each different). Or, CRM adds an authorization property relating User to an realty authorization relation (that has funky realty authorization controls, unique to realty).
An ODATA client getse one atom stream, which references to 2 endpoints, one of which is Azure AD Graph, and the oauth token(s) address both guards. Of course, the guards may have difference security policies, which non-toy oauth needs to address.
Does anyone have sample of ANY of this kind of thing?
It doenst have to be CRM adding value. Its anything that showcases 1 odata client talking to multiple endpoints as ATOM references are followed, and oauth token issuing/handling supports this model.