i have deployed couple for REST drivers connecting to Microsoft Graph to do following things

1. Create O365 Groups/Teams with owners

2. Create AzureAD Developer Apps client and API apps.

3. Create Security Groups

4.  Update Advanced Authentication Methods

5.  Update extension attributes on the users

6.  more and more

We have automated many internal workflow using REST driers that does most of the things.

Until now it looks like this is the way to go: customized REST driver that makes calls to the MS.Graph.

maqsood  How do you parse the JSON data coming from Azure? Some custom OData parser?

Until now it looks like this is the way to go: customized REST driver that makes calls to the MS.Graph.

maqsood  How do you parse the JSON data coming from Azure? Some custom OData parser?

we use many techniques to parse the json

1. we try to transform incoming response to netiq json "supported format" and then use netIQ onw java code to conver to NDS :-)

2. We also use community netiq json parser shared in community github

3. we use custom ecmasript were it makes more

i think its wise for netiq to build some  "odata" json parser to speed the developer work

This is the path I have also taken. I have modified the Azure JSON to the "supported format" and then used the NetIQ parser to get the XDS. I also built an ECMA functions where it made sense.

Now, in my spare time, I am working on an ECMA parser for oData. If I will endup with something that works well, I will try to open source the code.

For 2) - can you share me the link?

OData is just JSON it can easily be processed in ECMAScript after doing a JSON.parse(response_value).

BTW: Lets keep this thread focused on the enhancement to the AzureAD driver and open a new thread in discussions for evaluating solutions using the REST driver.