<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D54z00007HXHiuCAHOkta Classic EngineIntegrationsAnswered2026-05-28T22:33:05.000Z2021-11-08T10:31:21.000Z2026-05-28T22:33:05.000Z

e9cw7 (e9cw7) asked a question.

Automatic provisioning of user _ failed. Effy: Freshservice Provisioning

Prerequisites: 

user accounts are created manually in AD

they sync to Okta from AD

set up Effy: Freshservice Provisioning app in Okta as per Freshservice advice (sync user info from Okta to Freshservice + other things)

the app assigns by the group Everyone

 

Every user in our tenant that syncs from AD to Okta automatically should get an assignment of Effy: Freshservice Provisioning app. Looks like users do sync properly from AD to Okta but sometimes we're getting the following error:

An error occurred while provisioning Effy: Freshservice Provisioning

Automatic provisioning of user ____ to app Effy: Freshservice Provisioning failed: Error while creating user user@domain.com: Bad Request. Errors reported by remote server: Please fix this on the Tasks Page

 

It doesn't show what is the exact issue.

Was able to solve this issue for 2 other users just by adding Department in AD (previously there was a - dash sign). After it synced from AD to Okta, was able to assign the app. Sometimes several attempts to assign help.

 

For the current user (new account) tried multiple times to assign the app from Tasks, and info looks OK

Are there any mandatory fields that have to be added?

 

We also have some service accounts that do have a similar issue but it's not necessary for them to be assigned with this app.

Tried comparing it with other new users and it looks almost the same (the affected user has no primaryPhone attribute but I don't think that is the issue)

 

 

 


  • e9cw7 (e9cw7)

    in short, I've contacted Effy Support (support@effy.co.in) and figured out that it's a Timezone that affects auto-assignment. Basically, it was a GMT prefix - it should be Eastern Time (US & Canada) instead of (GMT-05:00) Eastern Time (US & Canada) so once I removed (GMT-05:00) it begins to work

    Selected as Best
This question is closed.
Loading
Automatic provisioning of user _ failed. Effy: Freshservice Provisioning