Learn how to update user’s attributes in Azure AD using data from Jira fields
Example
You can update user properties in Azure AD directly from the Jira issues. This way, you can let users self-report changes in their data (such as office address, phone number, surname, or position change) and update them automatically in
Active Directory, reducing the Azure AD admin overload.
As is the case of all post-functions, this one also can be combined with validators and conditions, allowing you to secure the whole process by, for example, requiring Manager approval before executing the change.
Configure post function
Steps
Here is how to configure the Update user’s attributes in Azure AD post function:
Navigate to Project settings > Workflow schemes.
Select the workflow you’d like to use and click Edit > Diagram or Edit > Text.
Click on the transition upon which the Update User’s attributes in Azure AD post function should be activated.
Open the Post functions settings and click Add post function.
Select the Update user’s attributes in Azure AD post function.
Click Add.
Add post function to transition
Select the user picker field that contains the user whose data will be updated.
Choose the Jira field that will be the information source.
Pick the Azure AD attribute that will be updated with the data from the selected Jira field.
Also, you can choose the option to automatically add an internal comment on the Jira issue informing about the success or failure of the update by activating the toggle bar.
Jira comment
Click Add.
Administration
You will be moved to the Workflow configuration screen, where you’ll see the Update user’s attributes in Azure AD post-function added to the list, along with the description of what will happen when this post function is triggered.
Click Publish Draft.
Issues
Result
When the post function is triggered, the data taken from the Jira field will overwrite the information in Azure AD.
Note
If you don’t fill out the information on the Jira issue you want to update in Azure AD, the attribute will be
overwritten with an empty value. For example, if you leave the field Address empty in the Jira ticket,
the corresponding value in Azure AD will be overwritten with an empty value.
To avoid this, set the fields used in the post-function as required.
Supported user fields:
Assignee
Reporter
User picker
Supported Jira fields:
Text field (single-line)
Text field (multi-line)
Text field (read-only)
Single user picker
Multi user picker
Single select
Note
Text fields and Single select fields can be mapped to attributes that are collections, for example, Other emails, using semicolons.
They separate the values in a Jira field, meaning Azure AD treats them as individual elements in a given attribute.
