Separate calls by provisioning Guest User in Azure AD

[JPMac]

In our environment, we need to provision Guest User in Azure AD.
However, the URL (https://graph.microsoft.com/v1.0/invitations) that creates Guest User does not allow us to edit detailed properties, so we have written an API in call2 to update attribute.

===

{

    "accountIdPath": "call1.message.invitedUser.id",

    "dateFormat": "yyyy-MM-dd'T'HH:mm:ssXXX",

    "responseColsToPropsMap": {

    "displayName": "call1.message.invitedUserDisplayName~#~char",

    "name": "call2.message.userPrincipalName~#~char"

    },

    "call": [

    {

    "name": "call1",

    "connection": "userAuth",

    "url": "https://graph.microsoft.com/v1.0/invitations",

    "httpMethod": "POST",

    "httpParams": "{\"invitedUserEmailAddress\":\"${user.email}\",\"invitedUserDisplayName\":\"${user.firstname}\", \"inviteRedirectUrl\":\"https://portal.azure.com\", \"invitedUserType\": \"Guest\", \"sendInvitationMessage\":\"true\"}",

    "httpHeaders": {

    "Authorization": "${access_token}",

    "Content-Type": "application/json"

    },

    "httpContentType": "application/json",

    "successResponses": {

    "statusCode": [

    200,

    201,

    204,

    205

    ]

    },

    "unsuccessResponses": {

    "error.code": [

    "Request_BadRequest",

    "Authentication_MissingOrMalformed",

    "Request_ResourceNotFound",

    "Authorization_RequestDenied",

    "Authentication_Unauthorized",

    "BadRequest"

    ]

    }

    },

    {

        "name": "call2",

        "connection": "userAuth",

        "url": "https://graph.microsoft.com/v1.0/users/${response.call1.message.invitedUser.id}",

        "httpMethod": "PATCH",

        "httpParams": "{\"givenname\":\"${user.firstname}\",\"surname\":\"${user.lastname}\",\"displayName\":\"${user.lastname}, ${user.firstname}\",\"city\":\"${user.startdate}/${user.enddate}\",\"streetaddress\":\"${user.startdate}/${user.enddate}/0\",\"officelocation\":\"${user.customer.displayname}\",\"CompanyName\":\"${user.startdate}/${user.enddate}/0\",\"department\":\"${user.startdate.format('yyyy/MM/dd')}\",\"state\":\"${user.customproperty12}\",\"country\":\"SAVI\"}",

        "httpHeaders": {

            "Authorization": "${access_token}"

        },

        "httpContentType": "application/json",

        "successResponses": {

            "statusCode": [

                200,

                201,

                204,

                205

            ]

        }

    }

    ]

    }

===

When we use this create account JSON to provision, call2 changes the attribute, but it updates the attribute with ${} still.

Where should I change to edit the attribute properly with Saviynt's user property?

[Amit_Malik]

Hi @JPMac ,

This could happen because of Azure side sync where in the ID is returned but the object is still not created and synced fully. I can't guarantee the root cause analysis is correct but to solve this problem we did : 

We used to see this issue intermittently (Only for GUEST accounts), after waiting for a min or two , it used to work. So we invited the user via create account JSON and created an Analytic report to find such entries and update account. Here is the sample :

select distinct a.name,a.accountkey as acctKey, endpointkey, 'updateAccount' as Default_Action_For_Analytics from accounts a,user_accounts ua,users u,arstasks at where ua.userkey=u.userkey and ua.accountkey=a.accountkey and a.endpointkey='2' and a.endpointkey=at.endpoint and u.customproperty10 in ('Workday(S)','Workday(IRA)') and at.userkey=u.userkey and u.userkey in (select userkey from arstasks at where at.tasktype=3 and at.status =3 and endpoint=2) and u.userkey not in (select userkey from arstasks at where at.tasktype in (12) and at.status in (1,3,4));

Good Luck !!

Kind Regards,

Amit

If it solved your challenge, please ACCEPT SOLUTION.

If informative enough hit Kudos

[Dhruv_S]

Hi @Amit_Malik @JPMac 

Could you please confirm if the above JSON works for the call2 (without using any workarounds like analytics). Could you please share the working JSON if there are any changes done in the same.

Regards,

Dhruv Sharma

[rushikeshvartak]

You are setting account name from call2

[JPMac · Accepted solution]

It's working by using this json.

{

    "accountIdPath": "call1.message.invitedUser.id",

    "dateFormat": "yyyy-MM-dd'T'HH:mm:ssXXX",

    "responseColsToPropsMap": {

    "displayName": "call1.message.invitedUserDisplayName~#~char",

    "name": "call2.message.userPrincipalName~#~char"

    },

    "call": [

    {

    "name": "call1",

    "connection": "userAuth",

    "url": "https://graph.microsoft.com/v1.0/invitations",

    "httpMethod": "POST",

    "httpParams": "{\"invitedUserEmailAddress\":\"${user.email}\",\"invitedUserDisplayName\":\"${user.firstname}\", \"inviteRedirectUrl\":\"https://portal.azure.com\", \"invitedUserType\": \"Guest\", \"sendInvitationMessage\":\"true\"}",

    "httpHeaders": {

    "Authorization": "${access_token}",

    "Content-Type": "application/json"

    },

    "httpContentType": "application/json",

    "successResponses": {

    "statusCode": [

    200,

    201,

    204,

    205

    ]

    },

    "unsuccessResponses": {

    "error.code": [

    "Request_BadRequest",

    "Authentication_MissingOrMalformed",

    "Request_ResourceNotFound",

    "Authorization_RequestDenied",

    "Authentication_Unauthorized",

    "BadRequest"

    ]

    }

    },

    {

        "name": "call2",

        "connection": "userAuth",

        "url": "https://graph.microsoft.com/v1.0/users/${response.call1.message.invitedUser.id}",

        "httpMethod": "PATCH",

        "httpParams": "{\"givenname\": \"${user.firstname}\",\"surname\":\"${user.lastname}\",\"displayName\":\"${user.lastname}, ${user.firstname}\",\"city\":\"${user.startdate}/${user.enddate}\",\"country\": \"SAVI\"}",

        "httpHeaders": {

            "Authorization": "${access_token}"

        },

        "httpContentType": "application/json",

        "successResponses": {

            "statusCode": [

                200,

                201,

                204,

                205

            ]

        }

    }

    ]

    }

[gokul]

Hi @JPMac, I'm also facing the same issue. What is the root cause of that issue? and inorder to fix this do we have to pass only limited attributes? what is the fix you have done in the above json.
Your assistance in this would be highly appreciated.