-
-
Notifications
You must be signed in to change notification settings - Fork 41
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
Comments
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 |
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. |
So it doesn't seem that bad I used: Did small configuration where/from, saved, and used URL that it provided. |
It seems the date has been postponed to December 2025:
|
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/
The text was updated successfully, but these errors were encountered: