Skip to content

Suggestions for new message format guidance article#14473

Draft
nickwalkmsft wants to merge 1 commit into
luywang-message-format-guidancefrom
nickwalk/luywang-message-format-guidance-revisions
Draft

Suggestions for new message format guidance article#14473
nickwalkmsft wants to merge 1 commit into
luywang-message-format-guidancefrom
nickwalk/luywang-message-format-guidance-revisions

Conversation

@nickwalkmsft

Copy link
Copy Markdown
Collaborator

A few editorial suggestions, TOC inclusion, and metadata

A few editorial suggestions, TOC inclusion, and metadata
@learn-build-service-prod

Copy link
Copy Markdown
Contributor

PoliCheck Scan Report

The following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans.

✅ No issues found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

@learn-build-service-prod

Copy link
Copy Markdown
Contributor

Learn Build status updates of commit 878c726:

✅ Validation status: passed

File Status Preview URL Details
msteams-platform/agents-in-teams/agent-message-format-guidance.md ✅Succeeded View
msteams-platform/assets/images/agents-in-teams/teams-message-format-decision-tree-wide-v2.png ✅Succeeded n/a (file deleted or renamed)
msteams-platform/assets/images/agents-in-teams/teams-message-format-decision-tree-wide.png ✅Succeeded View
msteams-platform/TOC.yml ✅Succeeded View

For more details, please refer to the build report.

**Use for:**
- "What time is the team sync?" → "Your team sync is at 2 PM Pacific today."

- Simple answers to questions: "Your team sync is at 2 PM Pacific today."

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The scenario: example structure is good, see if you can make that parallel all the way down.

@@ -78,10 +86,7 @@ Use for rich, stateful, interactive experiences beyond what a card can offer —

**Avoid when:** The experience fits in a card (use Adaptive Cards instead), or the UI is too rich to belong in a Teams message at all — a full analytics suite, an interactive CAD viewer, or any app-scale UI should live on the web and be linked to, not embedded. Widgets occupy the middle ground: richer than a card, scoped enough to feel native, but they do not replace the rich experience of a full app. Widgets have higher latency, require extra infrastructure, and have limited support on mobile / classic Teams. Default to Adaptive Cards; escalate to Widget only when cards hit a hard ceiling.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Consider moving some of this to the paragraph right under the heading.

Comment thread msteams-platform/TOC.yml
- name: Format the bot messages
href: bots/how-to/format-your-bot-messages.md
displayName: cross-platform support
- name: Format the bot messages

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is just the most appropriate place for this currently. Soon most everything here is going to move up to the "agents" section that is much more prominently placed in the overall TOC.

@nickwalkmsft nickwalkmsft self-assigned this Jul 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant