Retirement of Office 365 connectors within Microsoft Teams

[f0oster]

I'm not sure if you are across this, but MS have announced they are retiring Office365 Connectors for Teams.

I'm not sure what this means for this module, and I haven't looked into the recommended alternatives as yet.

See below link:
https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-microsoft-teams/

[PrzemyslawKlys]

I saw this, but I am not sure what's the alternative - the creation of messages/adaptive cards is still valid, so it's more on what should we be doing.

I guess we need to switch to graph chat/channel messages

• https://learn.microsoft.com/en-us/graph/api/chatmessage-post?view=graph-rest-1.0&tabs=http

[f0oster]

It looks like the available alternatives seem to all introduce a requirement to tie things directly to a user account (Graph API only supports delegated scopes, Power Automate flows are tied to users - not sure if there are other alternatives) - so a traditional service account will end up being required here, I guess. Feels very backwards.

[PrzemyslawKlys]

So it doesn't seem that bad

I used:

• https://make.preview.powerautomate.com/galleries/public/templates/d271a6f01c2545a28348d8f2cddf4c8f/post-to-a-channel-when-a-webhook-request-is-received

Did small configuration where/from, saved, and used URL that it provided.

[PrzemyslawKlys]

It seems the date has been postponed to December 2025:

• Update 07/23/2024: We understand and appreciate the feedback that customers have shared with us regarding the timeline provided for the migration from Office 365 connectors. We have extended the retirement timeline through December 2025 to provide ample time to migrate to another solution such as Power Automate, an app within Microsoft Teams, or Microsoft Graph. Please see below for more information about the extension:

• All existing connectors within all clouds will continue to work until December 2025, however using connectors beyond December 31, 2024 will require additional action.
  Connector owners will be required to update the respective URL to post by December 31st, 2024. At least 90 days prior to the December 31, 2024 deadline, we will send further guidance about making this URL update. If the URL is not updated by December 31, 2024 the connector will stop working. This is due to further service hardening updates being implemented for Office 365 connectors in alignment with Microsoft’s Secure Future Initiative
  Starting August 15th, 2024 all new creations should be created using the Workflows app in Microsoft Teams

[dirtydevver]

just a simple query with the deadline close approaching i was wondering if this is something that is possible to be adapted, or if not what maybe a better option/tools to use going forward?

[PrzemyslawKlys]

Whats there to adopt? This works with powerautomate as shown above? Or what do you mean?

[PrzemyslawKlys]

@dirtydevver can you let m,e kknow what you meean and what you expect?

[MSchBAG]

So it doesn't seem that bad

I used:

• https://make.preview.powerautomate.com/galleries/public/templates/d271a6f01c2545a28348d8f2cddf4c8f/post-to-a-channel-when-a-webhook-request-is-received

Did small configuration where/from, saved, and used URL that it provided.

Hi @PrzemyslawKlys ,

i used the powerautomate worklow but i got the following error:
Fehler bei Aktion (translated:Error with action) "Send_each_adaptive_card": The execution of template action 'Send_each_adaptive_card' failed: the result of the evaluation of 'foreach' expression '@triggerOutputs()?['body']?['attachments']' is of type 'Null'. The result must be a valid array.

could you help me?