ASR Replication appliance AADSTS165000: Invalid Request:

@AdamTyler-3590 Sorry for the inconvenience this must have caused you!

It seems like you are unable to log in to the Microsoft Azure Appliance Configuration Manager web-based app after changing the password for the replication appliance "Administrator" account.

Please follow the suggestions below:

1. Ensure that the new password for the "Administrator" account is correct and that you are entering it correctly when logging in to the Microsoft Azure Appliance Configuration Manager.
2. Ensure that the network connectivity between the replication appliance and the machine running the Microsoft Azure Appliance Configuration Manager is stable and there are no network issues that could be causing the problem.
3. Check the replication appliance logs to see if there are any errors or warnings that could be causing the problem. You can find the replication appliance logs in the following location: C:Program Files (x86)\Microsoft Azure Site Recovery\home\svsystems\logs.
4. Try restarting the replication appliance and see if that resolves the issue. To restart the replication appliance, open the VMware vSphere Client console, locate the replication appliance VM, and click on the Restart Guest OS button.
5. f none of the above steps resolve the issue, you can try resetting the "Administrator" account password using the following steps: a. Open the VMware vSphere Client console and log in to the replication appliance VM. b. Press Ctrl+Alt+Delete to open the Windows Security dialog box. c. Click on the Change a password option and follow the prompts to reset the "Administrator" account password. d. Try logging in to the Microsoft Azure Appliance Configuration Manager again with the new password.

If none of the above steps resolve the issue, you can contact Azure support for further assistance. They can help you troubleshoot the issue and provide you with a solution.

Hope this helps. Please reply if you have any questions!

If the response helped, do "Accept Answer" and up-vote it

Thank you @SadiqhAhmed-MSFT ..

1. Ensure that the new password for the "Administrator" account is correct and that you are entering it correctly when logging in to the Microsoft Azure Appliance Configuration Manager.

Yes, the password is correct. The process that fails is just after this screen, see screenshot.

1. Ensure that the network connectivity between the replication appliance and the machine running the Microsoft Azure Appliance Configuration Manager is stable and there are no network issues that could be causing the problem.

I am running this Configuration Manager from the same appliance. I have tried running it remotely too with no success. Network connectivity is fine.

1. Check the replication appliance logs to see if there are any errors or warnings that could be causing the problem. You can find the replication appliance logs in the following location: C:Program Files (x86)\Microsoft Azure Site Recovery\home\svsystems\logs.

This path you've provided does not exist on the replication appliance.

1. Try restarting the replication appliance and see if that resolves the issue. To restart the replication appliance, open the VMware vSphere Client console, locate the replication appliance VM, and click on the Restart Guest OS button.

I've restarted the appliance, tried rolling back recent Microsoft updates, and reset the Administrator password back to original. Now I am seeing this in the Portal and I am unable to add new systems to replication.

I'm completely stuck and we were just about to wrap up our migration to ASR. Dead end. I am in the process of contacting Azure support.

@AdamTyler-3590 Not sure if your device is registered to any other identity through which the device is code authenticated. If you are not sure, then I recommend you contact Azure technical support. Thanks!

Hello AdamTyler-3590,I got the same problem. When i first installed my appliance, I could log in but i missed some Key Vault access on Azure. I tried again a week later after giving the role assignements, and I have the exact same Invalid Request now. Did you get any solutions from Support ?

Have you tried refreshing that error page and input device code again?