InstallationService.cs already supports Managed Identity and Service Principal auth at the service layer (`InstallationService.cs:97-105`, maps to `SqlAuthenticationMethod.ActiveDirectoryServicePrincipal`/`ActiveDirectoryManagedIdentity`), but the CLI's argument parser in Installer/Program.cs never exposes a flag for either -- only `--entra ` exists.
Low urgency: Full Edition's installer doesn't support Azure SQL Database at all (Managed Instance and on-prem only, per README), so this doesn't block Azure SQL DB fleet onboarding -- that path is Lite, which already has full MI/SP support via the GUI and `servers.json`/Credential Profiles. Relevant only for Managed Instance/on-prem installs that want non-interactive Azure AD auth for the installer itself.
Found while researching #1321.
InstallationService.cs already supports Managed Identity and Service Principal auth at the service layer (`InstallationService.cs:97-105`, maps to `SqlAuthenticationMethod.ActiveDirectoryServicePrincipal`/`ActiveDirectoryManagedIdentity`), but the CLI's argument parser in Installer/Program.cs never exposes a flag for either -- only `--entra ` exists.
Low urgency: Full Edition's installer doesn't support Azure SQL Database at all (Managed Instance and on-prem only, per README), so this doesn't block Azure SQL DB fleet onboarding -- that path is Lite, which already has full MI/SP support via the GUI and `servers.json`/Credential Profiles. Relevant only for Managed Instance/on-prem installs that want non-interactive Azure AD auth for the installer itself.
Found while researching #1321.