Comment 3 for bug 1849677

Thanks for the clarification; I understand the code change now.

It seems that in create_user() even if the user already exists (as in your disk-reuse scenario) create_user continues to make "new" user modifications. We can't really know if the specified user already existed in the image, or is a case of previously booted instance, which means that having Azure Datasource ensure the user account isn't locked is likely the best course of action here.