Troubleshooting for the Okta and Azure integrations

If you have the Okta or Azure integration enabled on TravelPerk, you can download the Sync Log, which outlines the updates and errors that occurred during the sync.

For solutions to the different errors that may occur, see the Solutions table below. 

Download the Sync Log

1. Go to Account settings
2. Select Integrations
3. Find the Okta or Azure integration and click Manage
4. Go to the History section and from the dropdown list, select the time period for the Sync Log you want to download. We recommend selecting Last 7 days. 
5. Click Download CSV
6. Open the CSV log and check the errors

For Azure, updates happen every 40 minutes. For Okta, updates happen as soon as the user is updated in Okta. 

Solutions

Once you find the errors that are impacting your sync, use the solutions in the table below to resolve them: 

Error	Solutions
Value ____ not valid for attribute '___'.	The object with that name does not exist. It means that there is a mismatch between the names on TravelPerk and Okta or Azure for company, payment profile, cost centers or travel policies. There are 2 options to resolve this error: Create the object on TravelPerk with the exact same name. Modify the name of the company, payment profile, cost center, travel policy on TravelPerk to match the value they are mapping.
No valid phone number found in ___	Phone numbers must be in a specific format: they must be country code followed by the phone number.
A user is not being synced, and doesn’t show up in the CSV export	It’s possible that the user is not assigned to the TravelPerk app in Okta or Azure. If they are, there may be an error on Okta or Azure. You can try the following: Check if the user is active and assigned to the TravelPerk app on Okta or Azure Check the Okta or Azure logs for any additional information If there is no information, contact Okta or Azure support for more help
Greyed-out fields that cannot be edited	The fields are greyed out because there is an active integration with Okta or Azure and the user is managed through the integration. To update the values, they need to be updated directly in Okta or Azure.

If you disable the integration, provisioned users will remain in TravelPerk. It will only stop the creation of new users, and existing users will no longer be updated if there are changes.