Skip to content

[Doc Feature][Feature gaps for O365 connector deprecation][3937634] #11569

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.

Sign up for GitHub

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

Merged
surbhigupta12 merged 11 commits into from
Sep 24, 2024
Merged

[Doc Feature][Feature gaps for O365 connector deprecation][3937634] #11569

Changes from 1 commit
Commits
Show all changes
11 commits
Select commit Hold shift + click to select a range
fdf2d6f
[Doc Feature][Feature gaps for O365 connector deprecation][3937634]
v-bvishnu Sep 10, 2024
580c7e1
Update.
v-bvishnu Sep 10, 2024
fffc3c0
Update deprecation-note.md
v-bvishnu Sep 11, 2024
6bf9e22
Updated included file.
v-bvishnu Sep 11, 2024
25c7e07
Update deprecation-note.md
v-bvishnu Sep 11, 2024
1f1055b
Update deprecation-note.md
v-bvishnu Sep 11, 2024
13a5f28
review comment fixes
v-preethah Sep 12, 2024
7ee2b81
Review fixes
v-preethah Sep 14, 2024
c34edd1
Merge branch 'main' into feature-gaps-for-O365-connector
v-preethah Sep 16, 2024
beacac6
review fixes
v-preethah Sep 16, 2024
5d3dc42
Merge branch 'main' into feature-gaps-for-O365-connector
v-bvishnu Sep 24, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Update deprecation-note.md
  • Loading branch information
@v-bvishnu
v-bvishnu committed Sep 11, 2024
commit 1f1055b95db791ef4472d9cd230749567680ecc5
4 changes: 2 additions & 2 deletions msteams-platform/includes/deprecation-note.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,12 +12,12 @@
>
> * Create a Power Automate connector: Power Automate enhances the widely used **Workflows** apps in Teams. It's the scalable and secure approach to transmit data programmatically into and out of Teams. If you adopt this method, you can create one or two workflow templates for posting alerts from your product to Teams channels. This approach simplifies user adoption of the new method. For more information, see [Power Automate for enterprise developers, ISVs, and partners.](/power-automate/developer/dev-enterprise-intro)
>
> * Update your Teams app: You can enhance your current Teams app. For example, you can enable users to set up proactive messages based on trigger events within your system. For more information, see [how bots can post to channels through proactive messages.](../resources/bot-v3/bot-conversations/bots-conversations.md#proactive-messages)
> * Update your Teams app: You can enhance your current Teams app. For example, you can enable users to set up proactive messages based on trigger events within your system. For more information, see [how bots can post to channels through proactive messages.](../bots/how-to/conversations/send-proactive-messages.md#send-the-message)
>
> **Known issues**
>
> * Workflows app can't post in private channels.
> * Workflows can't post messages using the payload or format of O365 Connectors. Workflows support only Adaptive Cards and don't support the older message card format.
> * Workflows can't post messages using the payload or format of O365 Connectors. Workflows support only Adaptive Cards and don't support the older message card format. For more information, see [how to convert connector message card format to Adaptive Card.](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/tools/message-card-to-ac-transformation)
> * Workflows aren't available in Government community cloud (GCC) High.
> * Workflows don't include connectors such as, Jenkins, DataDog, and so on.
> * Workflows can only be created in your default environment.
Expand Down