Skip to content

Notifications: Native MSFT Teams target #14741

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

Closed
stirby opened this issue Sep 19, 2024 · 2 comments · Fixed by #14781
Closed

Notifications: Native MSFT Teams target #14741

stirby opened this issue Sep 19, 2024 · 2 comments · Fixed by #14781
Assignees
Labels
customer-requested Features requested by enterprise customers. Only humans may set this.

Comments

@stirby
Copy link
Collaborator

stirby commented Sep 19, 2024

Our notifications currently support SMTP and Webhook as delivery targets. We want to add native support for Teams workspaces as many customers use this as their internal messaging platform.

The native Teams integration should allow administrators to direct notifications towards a Teams workspace. Users should receive notifications via an app in that workspace, not a single channel. This way they have individual control of their inbox.

This product work should include server flags to set the Teams target and a new option in the deployment notifications settings UI for the delivery target. This should be paired with adding docs explaining how to connect our notifications with a teams workspace.

The Slack + teams integration docs can be a single guide.

Related: #14740

Note: We'll only be adding MSFT Teams and Slack as natively supported delivery methods.

@stirby stirby added feature customer-requested Features requested by enterprise customers. Only humans may set this. labels Sep 19, 2024
@mtojek
Copy link
Member

mtojek commented Sep 23, 2024

Hi @stirby!

I spent some time researching our opportunities. It seems that Teams Connectors are deprecated now, and it is advised to switch to Workflow.

I can't say yet whether Workflow, embedded in Teams, is sufficient, or if we need to depend on Power Automate as the deprecation guide suggests. I'm working on the PoC with the endpoint.

Notice: Power Automate may require an additional license fee as it is not part of the Office 365 plan, and we may need a bot license.

I can give you more information once I build the notification workflow for Coder 👍 . I hope we don't need to build a dedicated app.

@mtojek
Copy link
Member

mtojek commented Sep 24, 2024

Hello again!

It looks like we have a breakthrough:

Screenshot 2024-09-24 at 13 16 52 Screenshot 2024-09-24 at 13 17 13

This means we can go with a doc page for MS Teams, and let users customize the notification look including the logo. I will prepare a docs PR with instructions on how to achieve this result.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
customer-requested Features requested by enterprise customers. Only humans may set this.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants