Pre-release documentation, subject to change before release, blah, blah, but very interesting none the less.
When I look at the application scenario, Creating Enterprise Applications by Using Windows Azure AD Graph, which is described as:
In this scenario you have purchased an Office 365 subscription. As part of the subscription you have purchased the capability to manage users using Windows Azure AD, which is part of Windows Azure. You want to build an application that can access users’ information such as user names and group membership.
OK, so I can access “user names and group membership,” a good thing but a better (read more useful) thing would be to manage other user identifications for access to enterprise applications.
Or to put that differently, to map user identifications together for any single user, so the appropriate identification is used for any particular system. (Thinking of long term legacy systems and applications. Almost everyone has them.)
Certainly worth your attention as this develops towards release.