Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How about a clear explanation of MessageCard supportability at this point? #1025

Open
breakpoint7 opened this issue Apr 5, 2024 · 0 comments
Labels
Needs: triage 🔍 New issue, needs PM on rotation to triage asap

Comments

@breakpoint7
Copy link

Documentation issue

Source: https://learn.microsoft.com/en-us/outlook/actionable-messages/message-card-reference

This documentation seems out of date as it's not clearly spelled out anywhere where MessageCard can still be used.
The docs state that "However, if you are sending actionable messages via an Office connector, or to a Microsoft Teams connector, you must continue to use the message card format", however, the Teams Connector appears to require Adaptive Cards at this point.
Some Graph API's still seem to honor MessageCards and the Teams "messages" REST API also seems to allow you use them if properly escaped in the content. Teams WebHooks also work.
There's no clear deprecation communication around the use of MessageCard and the supportability matrix isn't very helpful:
https://learn.microsoft.com/en-us/microsoftteams/platform/task-modules-and-cards/what-are-cards
https://learn.microsoft.com/en-us/microsoftteams/platform/task-modules-and-cards/cards/cards-reference

Related: MicrosoftDocs/msteams-docs#5706

@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs: triage 🔍 New issue, needs PM on rotation to triage asap label Apr 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs: triage 🔍 New issue, needs PM on rotation to triage asap
Projects
None yet
Development

No branches or pull requests

1 participant