Symptom
When creating an Azure Bot resource for the Microsoft Teams (Fleet) integration, the "Type of App" step only offers Single Tenant and User-Assigned Managed Identity. There is no Multi Tenant option, even though Fleet's setup guide instructs you to select it.
If you pick User-Assigned Managed Identity instead, the Azure "Manage" view for the Microsoft App ID has no Client Secret option, so there's no way to get the App ID / App Password / Tenant ID values that Fleet's "Add Teams App" form asks for.
Cause
Microsoft ended support for creating new Multi Tenant Azure bots. New Azure Bot resources can only be Single Tenant or use a user-assigned managed identity. Fleet's published Teams integration guide predates this change and still tells customers to select Multi Tenant, and it documents the "Azure Tenant ID" field as optional (to be left blank for multi-tenant bots).
The missing Client Secret option under Managed Identity is expected: a managed identity's credentials are controlled by Azure itself and are never exposed as a client secret you can copy out.
Fleet's Teams integration authenticates using a tenant-specific client secret and an explicit tenant ID. It does not support managed-identity authentication for this flow, so Managed Identity bots can't be used here regardless of the missing-secret issue above.
Resolution
Use a Single Tenant Azure Bot backed by a Microsoft Entra app registration:
Reuse an existing Single Tenant bot if you have one, or create a new Azure Bot resource with Single Tenant as the app type. Open its associated Entra app registration, go to Certificates & secrets → New client secret, and copy the secret value right away. It's only shown once.
In Fleet's Integrations → Add Teams App form, fill in all three credential fields:
Azure App ID: the app registration's Application (client) ID.
Azure App Password: the client secret value you copied (not the secret ID).
Azure Tenant ID: the Directory (tenant) ID for that app registration. Fill this in even though it's labeled optional. Don't leave it blank.
Set the Azure Bot's Messaging endpoint to the webhook URL Fleet returns after registration.
Managed-identity authentication isn't a supported path for this integration. Use the Single Tenant plus client-secret flow above instead.