In our Scenario AD and ENtra are in Hybrid model, we are trying to create the Entra Account. But ENtra Account creation sometimes failing with Error: [“sailpoint.connector.ConnectorException: Exception occurred. Error message - HTTP not ended OK. Response Code - 404 Error - Resource \u0027\u0027 does not exist or one of its queried reference-property objects are not present.”,“sailpoint.connector.ConnectorException: Exception occurred. Error message - HTTP not ended OK. Response Code - 404 Error - Resource \u0027\u0027 does not exist or one of its queried reference-property objects are not present.”]
Because ObjectId is coming as null in the plan.
Please advise
This usually happens in hybrid Microsoft AD/Entra setups when ISC tries to provision to Entra before Azure AD Connect sync creates the cloud object, so objectId is still null.
Best fix is to:
provision only to on-prem AD first
wait for AAD Connect sync + aggregation
then trigger Entra updates/licensing in a second step/workflow.
@Vinita72 the account you are trying to provision or add some groups does the client credentials have the relevant permissions .You can also check the if you have the right permissions to do the task
This is classic case of Hybrid Architecture for sure where you have AD and Entra in scope where Entra account gets created through backend sync.
My question is, as follows.
Do you have this flow in place where first AD account for the user gets created and then, through backend sync, ENTRA account also gets created?
If yes, then, you can halt the ENTRA ACCOUNT CREATION PROCESS till the ENTRA account is created for the user in TARGET and is aggregated back into ISC. In birthright criteria where you are adding new set of groups to the user, you can add some identity attribute specific assignment criteria.
To conclude, do not send CREATE ACCOUNT request to ENTRA. Make sure your birthright roles for ENTRA are configured with respective criteria.