Does Azure require a specific attribute name and external namespace like Okta?

Yes, fields are mapped according to a selectable dropdown, but custom attributes can be added to the Freshservice, if I know the name of them:

It’s probably using the same properties as Okta.  See the attached doc and test the mapping with that.

Thanks, Jeremy. I’ll test that tomorrow.

Do you have something on the other fields as well, especially interested in the Secondary Email field.

Here is the complete list I got from Effy.

That got the location sorted. Will reach out to support for the secondary email thing.

Thank you, Jeremy.

I am also trying to get a location field to map from AAD during user provisioning on a new FreshService setup.  Based on the Excel in the thread it looks like I should be using:

urn:ietf:params:scim:schemas:core:2.0:User:Location 

But that doesn’t seem to be doing it.  Screen shot of my attribute mapping below.  What am I missing?

Could also settle for a custom AAD attribute instead, but I haven’t had any success there either.  Any help is appreciated.  Thank you!

I am also trying to get a location field to map from AAD during user provisioning on a new FreshService setup.  Based on the Excel in the thread it looks like I should be using:

urn:ietf:params:scim:schemas:core:2.0:User:Location 

But that doesn’t seem to be doing it.  Screen shot of my attribute mapping below.  What am I missing?

 

 

Could also settle for a custom AAD attribute instead, but I haven’t had any success there either.  Any help is appreciated.  Thank you!

Actually, you should just write to the “location” attribute in Freshservice. Below are the 3 custom mappings I have added, the second one should take care of the location.

I added the other two mappings to get over the complete address in the address field as well, and for users with mismatched email and UPNs, I want their UPN as a secondary email address.

If you are missing the some of the target attributes, you have to go add them in the Advanced settings:

Hope this helps. :-)

I swear I tried that yesterday.  That is working now.  Thank you a ton!!

So after a little more troubleshooting, I have determined that the Location field does not sync on the initial user provisioning, which is why I thought it wasn’t working yesterday.  The second time the provisioning service runs it updated the location field on existing users.  Little odd behavior, but at least it works.

I am also trying to get a location field to map from AAD during user provisioning on a new FreshService setup.  Based on the Excel in the thread it looks like I should be using:

urn:ietf:params:scim:schemas:core:2.0:User:Location 

But that doesn’t seem to be doing it.  Screen shot of my attribute mapping below.  What am I missing?

 

 

Could also settle for a custom AAD attribute instead, but I haven’t had any success there either.  Any help is appreciated.  Thank you!

 

Actually, you should just write to the “location” attribute in Freshservice. Below are the 3 custom mappings I have added, the second one should take care of the location.

I added the other two mappings to get over the complete address in the address field as well, and for users with mismatched email and UPNs, I want their UPN as a secondary email address.

 

Hope this helps. :-)

Would you mind copy and pasting your address join command? I am looking for something similar, thanks!

Hi, recently switched from the Okta provisioning to Azure, anyone know if there is a fix for this Office>Location not syncing on the initial provisioning of a new user?

The default attribute in the freshservice SCIM Sync is “location”. According to Microsoft, there is a problem when using non full URN syntax, as they might not be included in the first sync.

Took me some time to figure it out, but you need to add a custom attribute using the following URN:

urn:ietf:params:scim:schemas:extension:freshservice:2.0:User:_location

use this attribute instead of “location”. Now the location is synced within the first sync attempt.

Having had issues with syncing “Location” from Entra, enterprise apps this has very much sorted the issue!