hello :)
So , we need to investigate since it s strange
First if you wanna have menu in english, little trick i use : change in brower language and choose a as primary english (english in not my main language too ^^ i do this before making screenshot :) ) (in Chrome it's language, then web site and language, then "english (US)'')
Second , when you try in teams , you have, later a view of what happen in the agent n in dev screen, you could deep dive and try to see if the tool are called or not :
in my case : something like this
in you'r case we must see the tool call and clic on the tool to see if an error happened or not :)
if the tool are not here, something in you'r trigger is little sensitive too much and make them not beeing call :)
- Main other possibility i just remind ! -> in dev screen you are in a trial mode : Everything is enable for free BUT in teams, if you try some licenced product ine power platform, AI builder, etc etc : the lake of credit will stop to work most likely in most case. so that's probably why you'r tool are not used :)
hope this help, i m adding a "check list" for all case that could made it not working :)
1. Version & Channel
The latest version wasn’t published to Teams.
Teams may still be using a cached build (remove/re-add the app in Teams).
2. Connections & Identity (most common cause)
In dev, Actions run under your maker identity. In Teams, they run under the end user’s identity.
Connection references may not be shared or credentials missing.
For Power Automate flows, check Run-only users settings.
Some connectors require a service principal or admin consent.
3. Licensing & Permissions
Missing Power Platform / M365 / premium licenses.
Dataverse roles not assigned.
SharePoint/OneDrive access not available for the end user.
4. Admin Consent & Teams Policies
Graph/connectors may need admin consent.
Teams policies may block custom apps.
Check SSO/RSC settings in the Teams app manifest.
5. Action Configuration
Action disabled in the published version.
Environment variables or secrets not set.
Long-running APIs or flows timing out.
6. Channel Capabilities
File/attachment handling may not be supported in Teams.
Short conversation context can prevent the Action from being triggered.
7. Environment Differences
Variables or connections may exist in dev but not in prod.
Instructions/settings might not have been re-published.
Quick troubleshooting checklist
Publish the latest version of the agent to Teams
Remove and re-add the app in Teams to clear cache
Verify connection references are correctly set (shared or per-user)
For Power Automate flows, check Run-only users settings and connections
Confirm the user has the right licenses and Dataverse roles
Ensure admin consent is granted for Graph or premium connectors
Verify Teams policies allow custom apps
Test SharePoint or OneDrive access with the end user’s account
Make sure environment variables and secrets are set in the published version
For debugging, add a temporary instruction like “If I say debug, always call Action X” to confirm if Teams can trigger it
