SKILL.md
Configure the Embedded Agentforce Employee Agent in Microsoft Teams
Make the embedded Agentforce agent ("IT Service Employee Agent") actually reply inside the
Microsoft Teams ITSM custom client ("Salesforce Employee Assist" → "Ask AI Agent"). The Teams
custom client loads a Messaging-in-App-and-Web (MIAW) deployment at runtime by its
esDeveloperName, which is hard-wired to Teams_AgentForce in committed Core config
(service-cloud-requestor-agent-miaw.configuration.json / the Teams app manifest) — so the
Embedded Service Deployment must be named exactly Teams_AgentForce and cannot be renamed
per-org.
This is the hardest, most under-documented part of Teams ITSM. The full build-from-scratch recipe — verified live against a real org — lives in:
→ references/teams-embedded-employee-agent.md
Execute one step at a time. These steps make real, state-changing API calls. Run a single operation, show its result, confirm it succeeded, then proceed — do not batch multiple setup calls into one parallel block.