Issue Creating Azure AD Users with Connector

[elliotwinonait]

Hello! 

I am running in a difficult issue that my team and I have been struggling to troubleshoot.

Scenario: We are trying to create new employee accounts when a manager submits a Microsoft Form.  The flow will grab the form, create an item in a Onboarding SharePoint List and then create the user in Azure AD.

However, an issue occurs that the Create the User Connector will inconsistently create accounts.

The following two results occurred twenty minutes from each other with very similar information input into the forms and the users not existing in Azure AD:

Test 1: Successful

Test 2: Not Successful

Full Output for Test 2: 

{
    "statusCode": 400,
    "headers": {
        "Transfer-Encoding": "chunked",
        "Vary": "Accept-Encoding",
        "Strict-Transport-Security": "max-age=31536000",
        "request-id": "b8213066-ffce-43ec-a8c1-11df3b608bae",
        "client-request-id": "b8213066-ffce-43ec-a8c1-11df3b608bae",
        "x-ms-ags-diagnostic": "{\"ServerInfo\":{\"DataCenter\":\"West US\",\"Slice\":\"E\",\"Ring\":\"4\",\"ScaleUnit\":\"004\",\"RoleInstance\":\"BY3PEPF0001C17B\"}}",
        "x-ms-resource-unit": "1",
        "Timing-Allow-Origin": "*",
        "x-ms-apihub-cached-response": "true",
        "x-ms-apihub-obo": "true",
        "Cache-Control": "no-cache",
        "Date": "Wed, 14 Sep 2022 20:26:53 GMT",
        "Content-Type": "application/json",
        "Content-Length": "576"
    },
    "body": {
        "error": {
            "code": "Request_BadRequest",
            "message": "Another object with the same value for property userPrincipalName already exists.",
            "details": [
                {
                    "code": "ObjectConflict",
                    "message": "Another object with the same value for property userPrincipalName already exists.",
                    "target": "userPrincipalName"
                }
            ],
            "innerError": {
                "date": "2022-09-14T20:26:54",
                "request-id": "b8213066-ffce-43ec-a8c1-11df3b608bae",
                "client-request-id": "b8213066-ffce-43ec-a8c1-11df3b608bae"
            }
        }
    }
}

We verified that the user in test two did not exist so there is no way the userprincipalname already exists.  

Any advice on how to further troubleshoot this?

Thank you!

E.J.

[fchopo]

Hi @elliotwinonait 

It seems that a user with the same UPN was created before. I mean, that user could be removed from Azure AD but still exists, as mentioned by Microsoft here:  After you delete a user, the account remains in a suspended state for 30 days. During that 30-day window, the user account can be restored, along with all its properties.

Try to permanently delete the user and test thr workflow again.

Hope that helps!

Ferran

[elliotwinonait]

Hi @fchopo !

The issue is that we are creating newly unique accounts when testing each time, so they have not existed in the tenant previously, that is why the error is confusing. For example, I input testuser123@email.com as the new employee, and verify there has never been a user account with that name (no aliases or deleted either) and it gives that error anyways.

Hope that clarifies the scenario.

Thanks!

E.J.