Backend Issue with Active Directory API Driven Provisioning App ?

Question

I am trying to use this JSON to push a user to the on premise active directory using the Enterprise Application called:

API-driven provisioning to on-premises Active Directory

When pushing any JSON to Provisioning API Endpoint, I will get this error:

{
    "error": {
        "code": "UnknownError",
        "message": "",
        "innerError": {
            "date": "2023-10-05T14:28:10",
            "request-id": "d00940ff-5eac-4c0f-97e0-5ca1610f4dfd",
            "client-request-id": "cc5c39e0-2caa-20a1-610a-4e6e5779dc5e"
        }
    }
}

Schema on the App are the default schema. My expectations would be that the user would be created. There are No provisioning logs whatsoever.

Here is an example of the body:

{ "schemas": [ "urn:ietf:params:scim:api:messages:2.0:BulkRequest" ], "failOnErrors": null, "Operations": [ { "bulkId": "86bdc432-c34e-44ab-8bcb-3e9f8a1fb409", "data": { "externalId": "400", "schemas": [ "urn:ietf:params:scim:schemas:extension:enterprise:2.0:User" ], "urn:ietf:params:scim:schemas:extension:enterprise:2.0:User": { "employeeNumber": "400" } }, "method": "POST", "path": "/Users" } ] }

But even only specifying {} as the body will give the same error.
It seems that the ingestion doesn't work at all for the service.

The Provisioning agent is running on version: 1.1.1367.0

I've reinstalled the agent, created a new application. application has the neccesary API permissions. It actually worked two days ago and i've pushed around 20 users, exactly the same way. Microsoft says its in Private preview, and not supported.

Hopefully the community can help thanks a lot!

Answer 1

The above issue is now resolved. Please validate if the request now works in your tenant.

Answer 2

Hi,

I'm stuck with same "UnknownError" in my deployment. I have configured Automatic provisioning, status of my On-premises provisioning agent is "active", test connection is successful with "The supplied credentials are authorized to enable provisioning".

I have configured App Registration with AuditLog.Read.All and SynchronizationData-User.Upload permissions. Using default attribute mapping with sample payload from Microsoft documentation.

No success to test Endpoint via Powershell or Postman, any ideas what's wrong?

Thanks for helping.

Answer 3

Hello,

I am facing this exact same issue from past couple of days. Before that it was working fine.

Any fix identified? Please let me know. Thanks in advance.