Issue with SCIM Provisioning Retry Behavior for Duplicate Users

We have implemented automatic user provisioning using the SCIM protocol. During the provisioning process, when a POST request is made to create a user who already exists in another Azure AD tenant, our SCIM endpoint returns a 409 Conflict status code. As expected, this indicates a uniqueness constraint violation. To further clarify the nature of the conflict, we also included the scimType attribute with the value "uniqueness" in the response. However, despite this, Entra ID continues to retry the provisioning request at regular intervals, which is not the desired behavior in this scenario. We have attempted several alternative approaches to prevent the retries, including: Returning a 200 OK response. Returning a 400 Bad Request. Returning a 201 Created response with an empty body. Unfortunately, none of these approaches have stopped the retries. Our goal is to prevent Entra ID from retrying the provisioning request when the user already exists in another organization/tenant, as this is a known and non-recoverable condition. Could you please advise on the correct way to handle this scenario so that Entra ID does not continue to retry the request unnecessarily?