Troubleshooting for the Okta and Microsoft Entra ID integrations

Only available for Premium and Pro accounts.
Only account admins can perform this task.

If you have the Okta or Microsoft Entra ID (formerly Azure Active Directory) integration enabled on Perk, 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, go to the Solutions table. 

Download the Sync Log

  1. Go to Settings and select Integrations.
  2. Find the Okta or Microsoft Entra ID integration and click Manage.
  3. Go to the History section and from the dropdown list, select the time period for the Sync Log you want to download. It's recommended to select Last 7 days. 
  4. Click Download CSV.
  5. Open the CSV log and check the errors.

Tip: For Microsoft Entra ID, updates happen every 40 minutes. For Okta, updates happen as soon as the person is updated in Okta. 

Solutions

Once you find the errors that are impacting your sync, use the following solutions to resolve them.

Error Solution
Value ____ not valid for attribute '___'. 

The object with that name does not exist.

It means that there is a mismatch between the names on Perk and Okta or Microsoft Entra ID for company, payment profile, cost objects or travel policies.

There are two options to resolve this error:

  • Create the object on Perk with the exact same name.
  • Modify the name of the company, payment profile, cost object, travel policy on Perk 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 person is not assigned to the Perk app in Okta or Microsoft Entra ID.

If they are, there may be an error on Okta or Microsoft Entra ID.

You can try the following:

  1. Check if the person is active and assigned to the Perk app on Okta or Microsoft Entra ID.
  2. Check the Okta or Microsoft Entra ID logs for any additional information.
  3. If there is no information, contact Okta or Microsoft Entra ID 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 Microsoft Entra ID and the user is managed through the integration.

To update the values, they need to be updated directly in Okta or Microsoft Entra ID.

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

Was this article helpful?