Connecting an external model to Microsoft Teams is usually a custom app or agent-integration project, not a universal one-click installation. The architecture must define the Teams surface, hosting, identity, permissions, model endpoint, data path, approvals, logging, and support lifecycle.
Current as of 2026-08-15
Microsoft’s Teams platform overview describes current app capabilities. Microsoft’s SDK guidance notes that older TeamsFx and Teams AI Library paths have been deprecated, so implementation guidance must be checked before coding.
Decision summary
- Choose a supported Teams app or agent architecture for the exact use case.
- Give the integration its own scoped identity and least-privilege permissions.
- Verify data retention and training terms for the exact model endpoint.
- Require human approval for consequential writes and test denied paths.
Define the interaction and trust boundaries
Decide whether users interact through personal chat, channel, message extension, tab, meeting, or workflow. Map Teams, Microsoft Entra ID, the app host, model provider, tools, storage, logs, administrators, and users. A diagram should show where tenant data leaves a Microsoft boundary and what returns.
Build on supported components
Validate the current Microsoft development stack and lifecycle before implementation. Register the app and identity through approved administration. Keep secrets in managed secret storage, use short-lived credentials where possible, verify token audience and tenant, and separate development from production. Do not grant broad Graph or channel access as a convenience.
Review model data handling
For OpenAI endpoints, review the current OpenAI endpoint data controls. For Claude, review Anthropic’s commercial terms together with the exact product privacy documentation. Product, plan, endpoint, opt-in, retention, and abuse-monitoring choices can differ; record the exact contract and configuration rather than generalizing from the brand.
Test behavior and operations
- Normal and malformed prompts.
- Unauthorized tenant, user, channel, and resource requests.
- Prompt injection and sensitive-data retrieval.
- Timeout, model outage, tool failure, and duplicate delivery.
- Human approval, cancellation, audit, revocation, and removal.
- Privacy, accessibility, records, and support workflows.
Next step for your environment
Create a one-workflow architecture packet with exact Teams capability, identity, permissions, data classes, endpoint, approval gates, logs, failure behavior, and uninstall plan. If you need a documented baseline before changing production systems, start with an ITECS technology and security assessment.
Record the accountable owner, current baseline, source date, decision, exceptions, acceptance evidence, and review trigger. Test consequential changes in a bounded environment, maintain a rollback path, and verify the real result before closing the work. Product names, model availability, pricing, legal requirements, and security guidance can change; recheck the primary sources whenever the decision is renewed or the environment changes.
Sources and update trigger
- Microsoft — Teams platform overview
- Microsoft — Current Teams SDK guidance
- OpenAI — Data controls by endpoint
- Anthropic — Commercial terms
Review trigger: Review after any Teams SDK, app capability, Entra permission, model endpoint, vendor term, or information-flow change.