Skip to main content

Microsoft Azure Active Directory Graph API

Got chance to work with Microsoft Azure Active Directory Graph API (api-version=1.5) to manage users, groups, licenses management etc.

few of the things that I should mention here which could save a developer time to code.

Azure Portal UI and Graph API object properties mapping;

WORK INFO:

JOB TITLE  : jobTitle
DEPARTMENT : department
OFFICE NUMBER: physicalDeliveryOfficeNumber
OFFICE PHONE:telephoneNumber
MOBILE:mobile [a single space between country code and mobile number]
STREET ADDRESS:streetAddress
CITY:city
STATE OR PROVINCE:state
ZIP OR POSTAL CODE:
COUNTRY OR REGION:country


ALLOW THE USER TO SIGN IN AND ACCESS SERVICES?
Account Enabled = false( INACTIVE), true(ACTIVE)  //


LICENSE INFO:

 EXCHANGE_S_STANDARD - Exchange Online (Plan 2)
MCOSTANDARD - Lync Online (Plan 2)
SHAREPOINTENTERPRISE - SharePoint Online (Plan 2)
SHAREPOINTWAC - Office Online
OFFICESUBSCRIPTION - Office ProPlus
RMS_S_ENTERPRISE - Azure Active Directory Rights Management

YAMMER_ENTERPRISE - Yammer

Azure Portal Organizational ROLE and Graph API Role Mapping:

 "Global Administrator"  =   "Company Administrator"
"Billing Administrator" = "Billing Administrator"
"Service Administrator" =  "Service Support Administrator"
"User Administrator" = "User Account Administrator"

"Password Administrator"  = "Helpdesk Administrator"

Comments

Post a Comment

Popular posts from this blog

Experience writing a Java based DirXML Driver

Based on the customer project, I wrote a DirXML driver which provision users through Novell Identity Manager 3.5.1 to their company intranet portal ( A Plone System). The portal exposed the RESTful API interfaces. So I started looking first at the Novell SOAP driver to see if it fit our needs. But while reading the driver documentation i felt it required too much XSLT knowledge + more customization and testing on the driver. And again it used the Apache HttpClient, Which is more a HttpClient rather then it targets to any specific protocol implementation. So If you could build SOAP messages at your own so it would help you in transporting these message back and forth between IDM and Application. The Novell SOAP driver comes up with two built in configurations "SPML and DSML", but in my case none of them were suitable. I had always wished to write my own DirXML driver at my own, so I thought why not just take this opportunity to fulfill my wish and at the same time get s...
1 comment
Read more

NetIQ IDM - Adding operation-data to subscriber command transformaiton custom commands

Recently i had to execute EOL cmdlets using psexecute though new NetIQ azure ad driver, since this operation is fire and forget in nature, i would like to track whole request and response for my own generated commands from subscriber command transofrmaiton policy, so i solved it by following policy: < do-set-dest-attr-value direct = "true" name = "psexecute" > < arg-association > < token-resolve datastore = "src" > < arg-dn > < token-text xml:space = "preserve" > {userref} </ token-text > </ arg-dn > </ token-resolve > </ arg-association > < arg-value type = "string" > < token-local-variable name = "cmdlet" /> </ arg-value > </ do-set-dest-attr-value > < do-append-xml-element expression = "../modify[@direct]" na...
2 comments
Read more