Closed skeeler closed 3 years ago
Thank you for reporting this - we haven't seen this behavior previously. Couple questions to try to figure this out:
Sorry you're running into this and hope we can figure it out.
Had the same problem with this Tool when tried to log into Azure with account with MFA (Authenticator App) enabled.
Next was greyed out and unavailable + no notification on Authenticator App
Workaround for me was to create an additional account without MFA. Tool run with this account correctly and I was able to move to another section.
Thank you @skeeler for reporting this issue and @TomaszWRutkowski for the workaround you used - possibly this is some issue with using device code authentication and some MFA setups (I know it is not universal, which can make it harder to pin down - my primary account uses MFA including with Authenticator App and has not had this issue). We will keep an eye out for this type of behavior going forward - closing this issue for now due to lack of recent activity - if others are encountering this please do feel free to open a new issue to get our attention and add any additional details of your type of account/auth setup to help pin-down or rule out the MFA angle here!
Running the App Migration tool locally, discovered a web app (IIS) and resolved all Errors, allowing me to progress to the "Login to Azure" step. I then authenticate successfully (using https://microsoft.com/DeviceLogin) and close the browser window as instructed. At this point, the "Next" button in the App Migration tool is not enabled, and I cannot proceed any further in the process.
Investigative information
Please provide the following:
Repro steps
Provide the steps required to reproduce the problem:
Expected behavior
Provide a description of the expected behavior.
After I authenticate, the "Next" button on the "Login to Azure" page should be enabled.
Actual behavior
Provide a description of the actual behavior observed.
After I authenticate, the "Next" button on the "Login to Azure" page IS NOT enabled, blocking further progress.
Known workarounds
Provide a description of any known workarounds.
N/A