Deleted users are not really "deleted" !

Question

Hello all !
I'm writing an java application to create/read/update/delete users using the GRAPH API. All is going well except one particular use case : If I delete a user, and then later try to create again the same user, I get the following error : "A conflicting
object with one or more of the specified property values is present in the directory"
The detailled use case for one user is :
- Create user with (userPrincipalName, displayName, accountEnabled, mailNickname, password, forceChangePasswordNextLogin properties) : OK
- Query this user to read  his properties: OK
- Delete this user : OK
- Query this user to read his properties : the user does not exist : OK
- Create the user with same properties than first step : Not OK ("A conflicting object with one or more of the specified property values is present in the directory")
It should be noted that this error is returned more and more as I repeat these steps.
What is the problem and what can I do ?
Thanks in advance.

Answer 1

I am able to successfully add and remove the same user using the Azure Portal and via code.
Are you sure the user is actually being deleted?
Have you verified if you are able to see the deleted user in the Azure Portal after you delete it?
I used the code within the Graph API Console Application ( AzureADSamples/ConsoleApp-GraphAPI-DotNet
- https://github.com/AzureADSamples/ConsoleApp-GraphAPI-DotNet- "create a new user" region and "Delete User" region).  I was able to create the same user and
delete the user multiple times without any errors. 
Here is another thing you could verify.  Is you application a member of the "User Account Administrator" role?  You can utilize the MSOL cmdlets ( Manage Azure AD using Windows PowerShell -https://msdn.microsoft.com/en-us/library/azure/jj151815.aspx )
to add your application to this role (add-msolrolemember -RoleName "User Account Administrator" -RoleMemberType ServicePrincipal -Rolememberobjectid <object GUID for application> )
If your application is under  the correct "User Account Administrator" role, it should not have any problems doing this task.  I would verify.
 If you are still having a problem.  You might need to open a support case via the Azure Portal.  I hope this resolves your issue.
~ Michael