Azure AD - Orch - Office Location (physicalDeliveryOfficeName)

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.

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}}
}

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.