Udostępnij za pośrednictwem

AAD Graph API Version 1.5 is now available

  • Artykuł

A new version of the Graph API has been released and is now available. The MSDN documentation has been updated, documenting the new features. Each graph API version now has a separate section in the MSDN that provides a general overview of the features within each. Below are a few links to the version information available in the MSDN:

Azure AD Graph API Versioning

A new Microsoft Azure Active Directory Graph Client Library 2.0 is now available on Nuget.org.

The Microsoft Azure Active Directory Samples and Documentation links have been updated as well.

For a quick look at the official AAD team blog posts:
Announcing Azure AD Graph API Client Library 2.0

Additional details about the release of Versions 1.5 can be found here:
Announcing the new version of Graph API: api-version=1.5

Graph API version 1.5 introduces the following feature changes:

    • The schema namespace of Graph API has changed from Microsoft.WindowsAzure.ActiveDirectory to Microsoft.DirectoryServices. This affects all entities and complex types exposed by Graph API 
    • Support for directory schema extensions has been added. This allows you to add properties that are required by your application to directory objects. The following entities support schema extensions: user, group, tenant detail, device, application, and service principal. To support directory schema extensions: the ExtensionProperty entity has been added, the extensionProperties navigation property has been added to the Application entity, and a new function, getAvailableExtensionProperties, has been added to return the registered extension properties of supported directory objects. For more information about extending the directory schema, see Azure AD Graph API Directory Schema Extensions.
    • The way in which permissions are represented has changed and is more tightly aligned with OAuth 2.0 concepts as well as with the way permissions are represented in other Azure components. The Permission entity has been removed and has been replaced with the OAuth2PermissionGrant entity. This entity represents delegated OAuth 2.0 permissions scopes that arrive in an OAuth 2.0 access token scope claim. Additionally, the new AppRoleAssignment entity represents application roles that can be assigned to users, groups and service principals. Two related complex types have also been added: AppRole and OAuth2Permission. This change has precipitated renaming some properties and adding others in the following entities: Application, Group, ServicePrincipal, and User.
    • The Role entity is renamed to DirectoryRole. 
    •  The RoleTemplate entity is renamed to DirectoryRoleTemplate.

For more detailed information on the changes, see the links embedded in the blog post or you can visit the Azure AD Graph API MSDN link.

Comments

  • Anonymous
    April 28, 2015
    Hi, I am using Azure AD for user and role management operations from my MVC web application. I am using version of Graph API as 1.5 and Microsoft.Azure.ActiveDirectory.GraphClient .Net library 2.0.6. I need to remove an AppRoleAssignement (Application Role) assigned to user by calling Graph API. I was referring Stackoverflow link. Is there any method available in which I can use in my C# code to delete AppRoleAssignment. When I get users from active directory, the AppRoleAssignement always come null, even if an application role is assigned to a user. Kindly, help me providing a correct version of dll and available method to delete AppRoleAssignment. Thank you.