Directory switch, Windows Auth and local folders issues

[v-kmahajani]

Investigative information

Please provide the following:

• UTC Timestamp: 19th June 2023 0830
• Migration Tool App version : 1.0.8
• OS Version: Windows 11

1. Issues –
   a. Tool sometimes does not detect Windows Authentication set on the application
   b. On the “Azure Migrate Hub” step, tool allows user to switch the Azure directory. If user has access to multiple directories, it selects the first one in the list. If we change it to some other directory, on the next screen, it still shows list of subscriptions from first directory and does not allow selection of required subscription in different directories
   c. Tool does not allow going back to previous step. If we click on the step from left side, it by default goes to first step.

2. Suggestions –
   a. If the application configuration has some local folder paths mentioned for any reason (E.g., File upload path or Log file path etc.) tool should show it as a warning since post migration, application should not refer to any local file system paths in app service. As a remediation, tool should suggest using Azure file share mounts.

[krolson]

Hi @v-kmahajani, thank you for posting about these issues here.

Especially for the first issue, could you give a bit more detail (like an example of a web.config that has Windows Auth enabled but is not detected)?
I'm adding a bug tag to this issue related to this and not respecting / allowing changing the directory.

For the navigation we have considered the ability to navigate backward at a step-by-step level, and this would be a potential future enhancement - for now what you have described is the expected behavior to restart at the beginning of the process.

Thank you for the suggestion about warning on seeing any local folder path in the configuration. This is something we might incorporate into the PowerShell scripts, but this may be more complicated to do for the App Service Migration Assistant as we only use anonymized information for the assessment (and thus with current implementation we would not be able to tell if any generic configuration value was a local full file path vs a relative file path in the application vs some other random string).

[v-kmahajani]

Thanks for your response @krolson. I will provide more details about windows authentication related issue. Also, will I get some kind of alert when enhanced version of tool/scripts is released?

[v-kmahajani]

Hi @krolson, below is the entry in the web.config which was not detected by ASMA tool.