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

Retirement of Office 365 connectors within Microsoft Teams #59

Open
f0oster opened this issue Jul 10, 2024 · 4 comments
Open

Retirement of Office 365 connectors within Microsoft Teams #59

f0oster opened this issue Jul 10, 2024 · 4 comments
Labels
important question Further information is requested

Comments

@f0oster
Copy link

f0oster commented Jul 10, 2024

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
Copy link
Member

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

@PrzemyslawKlys PrzemyslawKlys pinned this issue Jul 10, 2024
@f0oster
Copy link
Author

f0oster commented Jul 10, 2024

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
Copy link
Member

So it doesn't seem that bad

image

I used:

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

@PrzemyslawKlys PrzemyslawKlys added the question Further information is requested label Jul 10, 2024
@PrzemyslawKlys
Copy link
Member

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
important question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants