Default user-assigned identity creation to Function App context in Identity Connections flow

[Copilot]

In Add Function App Identity Connections, choosing Create new user-assigned identity opened a creation flow without useful prefilled context. This change seeds the wizard with the selected Function App’s resource group/location so identity creation starts with sensible defaults (including generated identity name behavior tied to RG context).

• Wizard context defaults (Identity Connections flow)

  • In addRemoteMIConnectionsInternal, derive defaults from the selected Function App site.
  • Prepopulate wizardContext.resourceGroup with { name, location } from functionapp.site.
  • Set default location via LocationListStep.setAutoSelectLocation(...) before UserAssignedIdentityListStep runs.

• Refactor for explicit default derivation

  • Added getDefaultResourceGroupForIdentityCreation(...) helper to isolate/clarify default selection logic.

• Focused test coverage

  • Added unit test for default derivation helper:
    • returns undefined when Function App/site context is missing
    • returns expected { name, location } when site data exists

const defaultResourceGroup = getDefaultResourceGroupForIdentityCreation(wizardContext);
if (defaultResourceGroup) {
    wizardContext.resourceGroup ??= defaultResourceGroup;
    await LocationListStep.setAutoSelectLocation(wizardContext, defaultResourceGroup.location);
}

[!WARNING]

[Matthew Fisher (MicroFish91)]

Copilot Prefer using LocationListStep.setAutoSelectLocation over LocationListStep.setLocation

[Copilot]

Copilot Prefer using LocationListStep.setAutoSelectLocation over LocationListStep.setLocation

Updated in 414e9e8 to use LocationListStep.setAutoSelectLocation(...) instead of setLocation(...) in addRemoteMIConnectionsInternal.

Screenshot: unable to capture from this sandbox due Playwright browser profile lock (mcp-chrome in use), but no UI text/layout changed—only the location defaulting method call.