Visit Freshworks.com Visit Freshworks
Question

Azure AD - Orch - Office Location (physicalDeliveryOfficeName)

  • 6 July 2022
  • 3 replies
  • 441 views
J
Rank
Userlevel 1
Badge

Hello,

I’m designing a workflow using Azure AD Orch that will Create Users. The action Create Users does not have a default payload field for Office Location, which I find bizarre because they even mention this field as an Output in their instructions. How can I successfully populate this payload? I’ve tried the following in custom attributes:

{{ticket.onboarding_request.actor_1.cf_location}}

{{A1.officeLocation}}

I’ve even tried using the extension_json for my Azure AD Orch_ physicalDeliveryOfficeName

Thanks!

 

3 replies

zachary.king
Rank
Userlevel 7
Badge +16

I think we are referencing a similar question in the following thread:

My guess is that the same issue is present in both cases, missing a necessary attribute as a default field. I would suggest raising this with the support team using support@freshservice.com to get this to the product team for assessment.

- Zach / ITSM Solutions Engineer
R
Rank

HI,

 

I know this is very late, but this info might help someone else.

We ended up using this under custom attributes which worked a treat as it was failing in the default set.

Adjacent to this issue, we needed officeLocation as well, it didn’t like it if we had special characters in the source data.

{
"officeLocation": {{ticket.onboarding_request.actor_1.cf_location}},
"CompanyName":{{ticket.onboarding_request.actor_1.cf_company}}
}

 

For example, if we had an officeLocation of ‘Vista, London’ - it failed due to the comma.

So by putting quotes around the placeholder, it formatted properly. Hope this helps somebody else.

{
"officeLocation": “{{ticket.onboarding_request.actor_1.cf_location}}”,
"CompanyName":{{ticket.onboarding_request.actor_1.cf_company}}
}

Q
Rank

I think you can use the `extensionAttributes` field in your payload. Since the default Create User action does not include Office Location, you need to add it as a custom attribute, a simple example of how to include it in your JSON payload:

```json
{
  "displayName": "{{ticket.onboarding_request.actor_1.name}}",
  "mailNickname": "{{ticket.onboarding_request.actor_1.email}}",
  "userPrincipalName": "{{ticket.onboarding_request.actor_1.username}}",
  "accountEnabled": true,
  "passwordProfile": {
    "password": "{{ticket.onboarding_request.actor_1.password}}",
    "forceChangePasswordNextSignIn": false
  },
  "extensionAttributes": {
    "physicalDeliveryOfficeName": "{{ticket.onboarding_request.actor_1.cf_location}}"
  }
}
```

Make sure to replace `{{ticket.onboarding_request.actor_1.cf_location}}` with the correct variable from your workflow that holds the Office Location data.

Reply


Terms of Use