Add Azure identity fields to data plane details popup

[jwhartley]

Summary

The data plane detail popup in Admin Settings > Data Planes currently shows Service Account Identity with tabs for AWS (IAM User ARN) and GCP (Service Account Email). We need to add Azure fields so the Azure Blob Storage setup docs can follow the same generic pattern as S3 and GCS — "look up your data plane's identity in the UI" — instead of hardcoding values for specific data planes.

What to add

Add an Azure tab to the Service Account Identity section displaying two fields:

1. Azure Application Name — the Azure AD application name users must search for when granting Storage Blob Data Owner role on their storage account (e.g. Estuary Storage Mappings Prod, data-plane-aws-eu-west-1-c1.dp.estuary-data.com)
2. Azure Consent Link — the OAuth consent URL users click to add the Estuary application to their Azure AD tenant. This link contains the application's client ID and is specific to each data plane's Azure app.

Both fields should have copy buttons consistent with the existing AWS/GCP tabs.

Why

The Azure Blob Storage setup docs currently hardcode application names and consent links for only 2 data planes. As we add more data planes, this doesn't scale. The S3 and GCS docs already solved this by pointing users to the data plane details popup — Azure needs the same treatment.

Acceptance criteria

• Azure tab added to Service Account Identity section in data plane detail popup
• Azure Application Name displayed with copy button
• Azure Consent Link displayed with copy button (or as a clickable link)
• If a data plane has no Azure application configured, either hide the Azure tab or show an appropriate placeholder
• Source: data_planes.azure_application_name (and a new field or derived URL for the consent link — coordinate with backend if needed)

[jwhartley]

Docs changes assuming this ships as described

Once the Azure fields are available in the data plane details popup, the following changes should be made to the Storage setup docs.

1. "Choose a Data Plane" section

Add Azure to the list of available fields. Currently it lists:

• GCS buckets → "GCP Service Account Email"
• S3 buckets → "AWS IAM User ARN"

Add:

• Azure Blob Storage → "Azure Application Name" and "Azure Consent Link"

2. Azure Blob Storage section — consent link

Replace the two hardcoded OAuth consent URLs (one for GCP US Central, one for AWS EU West) with:

Add Estuary's Azure application to your tenant by clicking the Azure Consent Link from your data plane details.

3. Azure Blob Storage section — application name search

Replace the hardcoded application names (Estuary Storage Mappings Prod and data-plane-aws-eu-west-1-c1.dp.estuary-data.com) with:

Search for your data plane's Azure Application Name. You must search for the exact name, otherwise it won't show up.

4. Email step

Keep the "email support@estuary.dev" step — Azure storage mappings still require manual creation.

Question: Is there a plan/timeline for self-serve Azure storage mapping creation? If so, we can remove the email step and simplify this flow further.

[travjenkins]

@aeluce - tagging you as once we're done on our side we'll have a related docs pr opened as well.