mirror of
https://github.com/openclaw/openclaw.git
synced 2026-10-10 21:41:43 +00:00
Close the mechanically decidable half of the open i18n audit findings. English source (r3-0996, partial): - Two page titles were referenced under two spellings. Inbound link labels now match the target page's own frontmatter title: "Channel Routing" -> "Channel routing" (22 files) and "Multi-Agent Sandbox and Tools" -> "Multi-agent sandbox and tools" (3 files). No heading text changed, so no anchor changed. - docs/maturity/** is excluded. Its link labels are generated from the route slug by familyTitle() in scripts/qa/render-maturity-docs.ts. zh-CN glossary (r3-0995, partial): - "troubleshooting" now maps to the same target as "Troubleshooting". - "Multi-agent sandbox and tools" now maps to the same target as "Multi-Agent Sandbox and Tools". Both targets were chosen from the file's own dominant usage, not by translation judgement. Entries are edited in place; none is removed, added or reordered. zh-Hans navigation overlay (r3-0992, r3-0993 partial): - Remove 16 page anchors that have no file on disk and the duplicate help/scripts entry. The overlay carries labels only, so the published sidebar is byte-identical before and after this removal. - Label 6 more English groups using targets that already exist in glossary.zh-CN.json. Untranslated top-level groups: 14 -> 8. Publish sync and README (r3-0991 partial, r3-1001): - composeLocaleNav warns when an expected navigation overlay is absent instead of silently publishing the English sidebar. - README records the ClawHub tab exclusion, the starter-file coverage, and the case-sensitivity rule for glossary sources.
14 KiB
14 KiB
| summary | read_when | title | |
|---|---|---|---|
| Microsoft Teams bot support status, capabilities, and configuration |
|
Microsoft Teams |
Status: text + DM attachments are supported; channel/group file sending requires sharePointSiteId + Graph permissions (see Sending files in group chats). Polls and approval prompts are sent via Adaptive Cards. Message actions expose explicit upload-file for file-first sends.
What each page covers
- Microsoft Teams setup — install the plugin, register the bot and Teams app, and run against a dev tunnel.
- Microsoft Teams access control — DM and group policy, team and channel allowlists, and conversation IDs.
- Microsoft Teams authentication — certificate and managed identity auth instead of a client secret.
- Microsoft Teams manifest and permissions — the app manifest, RSC permissions, and the Graph permissions each capability needs.
- Microsoft Teams configuration —
channels.msteamskeys, environment variables, and history limits. - Microsoft Teams message behavior — session routing, reply style, attachments, and file sending.
- Microsoft Teams cards and actions — approvals, polls, presentation cards, member info, and target formats.
- Microsoft Teams troubleshooting — known limitations, common failures, and reference links.
Where each section moved
Every section heading from the previous single-page version keeps its anchor here, so an existing link such as /channels/msteams#reply-style-threads-vs-posts still resolves. Each entry points at the page that now holds the content.
- Bundled plugin
- Quick setup
- Goals
- Config writes
- Access control (DMs + groups)
- Access control (DMs + groups)
- How it works
- Step 1: Create Azure Bot
- Step 1: Create Azure Bot
- Step 2: Get credentials
- Step 2: Get credentials
- Step 3: Configure messaging endpoint
- Step 3: Configure messaging endpoint
- Step 4: Enable Teams channel
- Step 4: Enable Teams channel
- Step 5: Build Teams app manifest
- Step 5: Build Teams app manifest
- Step 6: Configure OpenClaw
- Step 6: Configure OpenClaw
- Step 7: Run the gateway
- Step 7: Run the gateway
- Federated authentication (certificate plus managed identity)
- Federated authentication (certificate plus managed identity)
- Option A: Certificate-based authentication
- Option A: Certificate-based authentication
- Option B: Azure Managed Identity
- Option B: Azure Managed Identity
- AKS Workload Identity setup
- Auth type comparison
- Local development (tunneling)
- Local development (tunneling)
- Testing the bot
- Environment variables
- Member info action
- History context
- Current Teams RSC permissions (manifest)
- Current Teams RSC permissions (manifest)
- Example Teams manifest (redacted)
- Example Teams manifest (redacted)
- Manifest caveats (must-have fields)
- Manifest caveats (must-have fields)
- Updating an existing app
- Capabilities: RSC only vs Graph
- Capabilities: RSC only vs Graph
- With Teams RSC only (app installed, no Graph API permissions)
- With Teams RSC only (app installed, no Graph API permissions)
- With Teams RSC + Microsoft Graph Application permissions
- With Teams RSC + Microsoft Graph Application permissions
- RSC vs Graph API
- Graph-enabled media + history
- Graph-enabled media + history
- Channel/group file recovery (
graphMediaFallback) - Channel/group file recovery (
graphMediaFallback) - Known limitations
- Webhook timeouts
- Teams cloud and service URL support
- Formatting
- Configuration
- Routing and sessions
- Reply style: threads vs posts
- Reply style: threads vs posts
- Resolution precedence
- Thread context preservation
- Attachments and images
- Sending files in group chats
- Why group chats need SharePoint
- Setup
- Sharing behavior
- Fallback behavior
- Files stored location
- Native approval cards
- Polls (Adaptive Cards)
- Polls (Adaptive Cards)
- Presentation cards
- Target formats
- Proactive messaging
- Team and Channel IDs (Common Gotcha)
- Team and Channel IDs (Common Gotcha)
- Private channels
- Troubleshooting
- Common issues
- Manifest upload errors
- RSC permissions not working
- References