It sounds like you've covered the essential configurations, but the missing login button often indicates an issue with Teams channel authentication and token handling. Here are some specific areas to double-check:
1. OAuth Connection Name in Omnichannel and Teams:
Ensure that the OAuth connection name in both Teams and Dynamics Omnichannel matches exactly. In Teams, go to your bot's settings, find the "OAuth Connection" configuration, and confirm it’s consistent with what’s set up in Dynamics.
2. Scope Permissions:
Double-check that your Azure AD permissions (e.g., User.Read, openid) apply both in the Bot Registration and App Registration sections. The Bot Channel Registration may sometimes need additional permissions separately applied if you’re using Teams and Dynamics in parallel.
3. Session Initiation Policy:
Microsoft Teams bots occasionally need an initiation message or conversation update event to trigger the authentication. Try setting up a proactive message in Copilot Studios that prompts users in Teams, as this might kickstart the conversation and trigger the login button.
4. Bot Framework Authentication Setting in Omnichannel:
In Dynamics 365 Omnichannel, navigate to the Bot Framework Authentication settings and ensure you’ve selected the correct OAuth Provider and Authentication Settings. Any discrepancy here can cause issues in token negotiation between Teams and Dynamics.
5. AAD Redirect URI:
Check the redirect URIs in Azure AD for the bot to ensure Teams-specific URIs are included. Add https://token.botframework.com/.auth/web/redirect if it’s missing.
6. Browser Cache/Cookies in Teams:
In some cases, Teams users need to clear their cache or cookies. This can also be done by signing out fully and back into Teams.
Finally, to isolate further, since you mentioned removing manual authentication in Copilot Studios resolved the issue, it could suggest that Copilot’s manual authentication settings are clashing with Teams.
