Retirement of Office 365 connectors within Microsoft Teams

[younes_sebti]

Dear community.

I'm reacting to the announcement Microsoft did

https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-microsoft-...

We are actively using today the flow designer actions under Microsoft Teams

Webooks > Post a Message

Webooks > Post Alert Notifications

Webooks > Post Change Details

Webooks > Post Incident Details

Webooks > Post Problem Details

These actions are failing to run on the new solution (the Microsoft Workflows app).

Is ServiceNow support planning to deliver new flow designer actions for Teams?

I'm asking because it isn't obvious. The new solution will have to generate an adaptive card.

https://adaptivecards.io/designer/

[younes_sebti]

I decide to raise the question to HI.

There's a KB article about this issue

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1650148

Shortly said you are encourage to install Microsoft Teams Graph Spoke (Store , Documentation)

This product requires you purchase the license to benefit the integrationHub as it relies on it.

I will try it on a non production instance and provide a feedback

[Niclas]

Via the Microsoft Graph API "Send chatMessage in a Channel" you need to connect to an Azure/Entra App registration having delegated permission to the channel, meaning the User who is initiating the API Call needs to be part of the MS Teams Channel. Thus, if ServiceNow Flow is triggered by another user, which is a common Use Case, it won't work: For instance, you want to send a notification to an MS Teams Channel when Incident is created for specific Assignment Group. The Flow would be triggered by the Incident Caller, which is not part of the Assignment Group and their related MS Teams Channel, so the Flow won't be able to successfully complete the Microsoft Graph API call.

• In this term, switching Flow Action to Microsoft Graph API is not as straight forward as the Knowledge Article is implying.
• It might work with application permission, but from security perspective it's unlikely Azure Admins will approve an App with access to send message to all private channels.
• Another Option may be to have a specific Service User, which is setting up the technical connection, and added to the MS Teams Channels. 

Another alternative to Graph API would be to create an Azure Bot, and a Teams Manifest App, that Teams Owners can add to a Channel, and receive Notifications via Azure Bot Framework APIs.  Interestingly this approach is already supported by ServiceNow for Slack Spoke, but not for MS Teams Integrations. While ServiceNow supports sending Notification to MS Teams through an Azure Bot (Virtual Agent Bot) via ServiceNow for Teams Integration, that Integration unfortunately is limited to personal scope (conversation between Bot and User), and cannot be extended to Channel Scope. Technically you can twist the Teams Manifest so that it will be able to be added to a Channel, and send Notification via Bot to those Channels, but it would mix it up with personal notifications use case. 

In conclusion all the alternatives are way more complex to set up than Webhooks. I understand the drive of moving away from Webhooks, given they were callable without any Auth they weren't the most secure one in the first place, but the alternatives are way more complex to set up and having out of box support for interactive integration to Channels - not only informal but also actionable notifications; like ServiceNow already covered with the Slack Spoke; would be of great value.