Azure User Sync

Updated at August 11th, 2025

+ More

ProSpend can sync user details from Azure using SCIM Provisioning. The client needs to create an app in Azure. ProSpend will provide instructions on how to do this.

Once provisioning is enabled, every 40 minutes Azure will send user details for all the users updated in the previous 40 minutes.

New Users

If a user profile is active in Azure, the block sign in field is set to No and is present in the provisioning app, Azure pushes that user information into ProSpend and ProSpend will create new user profiles.

Below mapping is user when creating new users.

From Azure

Azure Field (Attribute)	ProSpend Field
userPrincipalName	Login ID
mail	Email Address
givenName	First Name
surname	Last Name
employeeId	Employee No

Configurable Per Site

Below fields can be configured per site but will be the same for all the users. These are part of the details that will be obtained from the client before setting up the app in Azure.

Default Approver
Default Cost Centre
Expense Workflow
Invoice Workflow

Hardcoded Values

Below fields are hardcoded which means they cannot be changed for each site.

User Permissions - the system will tick Expense Category permission and tick all the categories which means users can code expenses or lines to all the categories.
Default Currency - all the users will be set to AUD.
Force single sign on (SSO) login - this will be enabled which means users will only be able to login via SSO.
Send welcome email - this will be enabled too which means all the users will receive a welcome email immediately.

Disabling users

A user profile will be disabled in ProSpend if one of the below is done in Azure -

User profile is removed from the provisioning app.
User profile is disabled in Azure.
User profile is deleted in Azure.
User profile block sign in field is set to Yes.

If a user profile has been created manually in ProSpend before setting up Azure provisioning, the system will still disable that profile if any of the above is done to the corresponding user profile in Azure. The system uses login ID as the match.

In ProSpend, the system will always disable a user profile. It will never be deleted.

When disabling an approver, the system will set the reassigned approver field to be same as the default approver.

The system clears all the values in the user profile when disabling it.

Re-enabling users

If a user profile was disabled by provisioning in the past and if that user has been enabled in Azure again, the system will re-enable that user profile in ProSpend too. However, if a user profile was disabled manually in the past and if that user has been re-enabled in Azure, the system will not re-enable that user profile in ProSpend. The admins need to enable this profile manually.

Also, because the system clears all the settings and fields in the user profile when it has been disabled by provisioning, if that user is re-enabled by provisioning, the system will use the default values.