Support for Azure AD Single-Tenant Authentication in Supabase CLI

[Frame1910]

Describe the bug Azure AD auth provider doesn't take in a tenant url, and therefore cannot suport single-tenant applications. In order to authenticate with a single tenant application in Azure, the auth provider must hit the tenant-specific URL: "https://login.microsoftonline.com/<tenant_id>" rather than the /common endpoint (which is only for multi-tenant applications)

To Reproduce Steps to reproduce the behavior:

1. Setup local development for supabase as per docs
2. Create app registration in Azure portal as per docs, except pick the single tenant option for supported account types:

3. Add config options to config.toml as per docs:

[auth.external.azure]
enabled = true
client_id = "env(SUPABASE_AZURE_CLIENT_ID)"
secret = "env(SUPABASE_AZURE_CLIENT_SECRET)"
redirect_uri = "https://localhost:3000"

4. Try to login

Expected behavior You should be authenticated with Azure AD and the normal login flow continues. When you want to login to an internal, company-only application, single tenant is necessary for security (ie. only people with a company email address can authenticate), which is actually one of the main reasons people use Azure AD in the first place, rather than other OAuth providers.

Supabase proper already implements the tenant url: I've verified that when using the "live" credentials that it works as expected.

Screenshots

Desktop (please complete the following information):

• OS: Windows 11
• Browser: Chrome (however this issue persists across browsers)
• Version of CLI: 1.77.9
• Version of supabase-js: 2.26.0
• Version of Node.js: 20.2.0

Additional context N/A