Hi @dghatuary ,
Recent changes in Azure security compliance (specifically, restrictions on app registrations and the use of client secrets) have indeed impacted the traditional approach for integrating Fabric Data Agent into Teams via custom bots.
Current situation:
- Many organizations now enforce policies that block the creation of new app registrations and/or prohibit the use of client secrets for authentication (requiring certificates or managed identities instead).
Possible workarounds and directions:
Use Azure Managed Identities:
- If your environment allows, consider leveraging Azure Managed Identities for authentication instead of client secrets. This avoids storing secrets and complies with stricter security postures.
- The bot/service running in Azure can be assigned a managed identity and granted the necessary permissions to interact with Fabric and Teams APIs.
Certificate-Based Authentication:
- If managed identities are not an option, certificate-based auth (instead of client secrets) is usually permitted. Register the app using a certificate, and configure your bot/service to use it for authentication.
Admin-Initiated App Registrations:
- In some organizations, regular users are blocked from registering apps, but Azure AD admins can do so. You may need to work with your Azure AD admin to have the app registered and credentials provisioned securely.
Check for Native Integrations:
- Microsoft is actively evolving Fabric and Teams integrations. Check if there are new, native connectors or “app templates” that do not require custom bot registration.
References:
Summary:
The best path forward is to avoid client secrets and move toward managed identities or certificate-based authentication. If you’re blocked by tenant security settings, coordinate with your Azure admin team for approved solutions.
If you share more about your environment or what’s specifically blocked, I can try to provide a more targeted workaround!
Hope this helps!
