Guia: Azure Bot Service, App Registration, SSO e Teams App Manifest
Ambiente: Staging (homologação) Pré-requisitos: Azure CLI instalado e autenticado (
az login), acesso de Application Administrator e ao Teams Admin Center do tenant piloto.
1. Criar App Registration (Azure AD)
Via Portal Azure
portal.azure.com→ Azure Active Directory → App registrations → New registration- Preencha:
- Name:
bi-agent-staging - Supported account types: Accounts in this organizational directory only
- Redirect URI: deixar em branco por ora
- Name:
- Copie e guarde:
- Application (client) ID →
BOT_APP_ID - Directory (tenant) ID
- Application (client) ID →
Criar Client Secret
- Certificates & secrets → New client secret
- Descrição:
bi-agent-staging-secret, expiração: 12 ou 24 meses - Copie o valor imediatamente →
BOT_APP_PASSWORD
Configurar API permissions (SSO)
- API permissions → Add a permission → Microsoft Graph → Delegated
- Adicionar:
User.Read,openid,profile,email - Grant admin consent (requer Global Admin)
2. Criar Azure Bot Service
portal.azure.com→ Create a resource → Azure Bot → Create- Preencha:
- Bot handle:
bi-agent-staging - Pricing tier:
F0(staging gratuito),S1(produção) - Type of App: Use existing app registration
- App ID:
Application (client) IDdo passo 1
- Bot handle:
Configurar Messaging Endpoint
- Azure Bot → Configuration → Messaging endpoint
- Valor:
https://<api-gateway-url>/api/messages- URL de staging: saída do
serverless deploy→ outputHttpApiUrl
- URL de staging: saída do
Habilitar canal Microsoft Teams
- Azure Bot → Channels → Microsoft Teams → Apply
3. Configurar GitHub Secrets
Após criar a App Registration, cadastre no GitHub environment staging:
| Secret | Valor |
|---|---|
BOT_APP_ID | Application (client) ID |
BOT_APP_PASSWORD | Client secret |
gh secret set BOT_APP_ID --env staging --repo <org>/bi_agent --body "<value>"
gh secret set BOT_APP_PASSWORD --env staging --repo <org>/bi_agent --body "<value>"