Azure AD 'Create Entitlement' Task failing with 400 BadRequest

Chamundeeswari
New Contributor II
New Contributor II

Hi,

We have setup Azure AD using Application Onboarding. So, we have an AzureAD_EXTERNALCONNECTION and AzureAD_PROVISIONINGCONNECTION. I am trying to create an Azure AD Group from Saviynt. On creation, a task of type "Create Entitlement" is created. I have a provisioning job created to execute only "Create Entitlement" type tasks. 

When the job is run, I can see that the logs show 400 BadRequest. But the logs does not give details as of what was the issue that is causing the 400 bad request. However, if I map the values and try from postman manually, I am able to create groups without issues.

Also, the pending task is not at all updated and it stays in "new" state without any comments. 

I have not made any changes to the automatically created AzureAD OOB connection. In Security system, we have OOB connector as "Connection" and REST connector as "Provisioning Connection". The environment is v23.x. 

How can this be resolved ?

Thank you!

Cheers 🙂

4 REPLIES 4

pruthvi_t
Saviynt Employee
Saviynt Employee

Hi @Chamundeeswari ,

Greetings.

REST response code 400 Bad Request is thrown when the operation you're trying to perform is something that cannot be carried on Azure application. So please check why the operation is not being performed on Azure application end.

Thanks,


Regards,
Pruthvi

rushikeshvartak
All-Star
All-Star

Share logs


Regards,
Rushikesh Vartak
If the response is helpful, please click Accept As Solution and kudos it.

Chamundeeswari
New Contributor II
New Contributor II

Hi,

I have attached the logs here. Here is a screenshot of the task:

Chamundeeswari_0-1694522258965.png

cheers,

Chamu 🙂

Chamundeeswari
New Contributor II
New Contributor II

Can someone please help with this issue ? It started working without any changes for sometime and the issue is back now. No matter how many times I run the job, the "task update date" is not updated and the logs just show 400 BadRequest and the job logs show that all tasks are failed.