Hi team
I have configured an OpsGenie to Microsoft Teams V2 integration which is working fine. Because it's a bi-directional integration I get the necessary controls to manipulate the alert from the teams channel.
I'd like to have a second channel which is configured 'for information only' The idea being that the engineers can manipulate the alert from within teams via the first integration but a wider audience just see the notification without the option to change the alert status.
Is this possible and if it is is there any guidance on the settings required?
Regards
Graham
Hello @Graham Lea
Thank you for contacting the Atlassian community. This is Mubeen.
The direct, inbuilt functionality to send alert details in a read-only format without the interactive alert actions (such as acknowledge, close, etc.) through the standard OpsGenie to Microsoft Teams integration is not a feature available. The integration's primary value proposition is around actionable alerts to streamline the response process.
A workaround option could be utilizing OpsGenie's ability to send alert notifications via email. You can setup a channel in MS Teams to receive email notifications and configure OpsGenie to send alerts to that email address. While this method does not use the direct OpsGenie to Teams integration, it achieves the goal of delivering alerts in a read-only format to a Teams channel. This would require validations from your MS teams admin for the ability to get emails for your MS Teams channels.
Thank you for your time and consideration.
Regards
Mubeen Mohammed
Cloud Support Engineer
I tried to follow your workaround option and created a sample Teams channel with email address and ability to receive emails. The problem I am encountering is, I am unable to add this email address anywhere in Opsgenie/JSM.
The reason I believe is, this email address is not an user account and is not part of our Microsoft and Atlassian tenant.
Any guidance or documentation on this will be helpful.
Thank you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Vipeen Sekharan ,
This is Shashwat, jumping in on behalf of Mubeen, as he's currently out of office.
Yes, it's correct that the new email will need to be added as an Opsgenie/JSM user account, before it can be utilised anywhere in the integrations.
Could you please help attach screenshots of any errors that show up when trying to add this email id?
Best,
Shashwat
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for your response. If I am adding/registering a Teams channel email address as an user account in Opsgenie/JSM before using it anywhere, am I required to assign it a proper license?
A sample Teams channel account when I add it directly as a member of a Team (without initially adding it as an user account in Opsgenie/JSM)
A sample Teams channel account when I add it directly as a responder of an alert under integration (without initially adding it as an user account in Opsgenie/JSM)
Thank you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey @Vipeen Sekharan
You are correct.
When you add the Teams email as a User account in Opsgenie, you'll be required to assign it a license by creating a new user in Opsgenie.
Directly adding the Teams email in the Responder would not work, as those fields are searching for Opsgenie Teams and User accounts i.e folks or groups which are part of Opsgenie
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.