Teams integration stop to work

[aaleman]

Hello Support Team,

Since August 19, 2026, alerts routed from Opsgenie to Microsoft Teams have stopped being delivered. The alerts continue to arrive in Opsgenie, but they are no longer being forwarded to Teams.

The following error appears in every affected alert:

---

Could not send [sendToChannel] action to MSTeamsV2 [xxxx]. Reason: 400 Bad Request on POST request for "https://login.microsoftonline.com/botframework.com/oauth2/v2.0/token": "{"error":"unauthorized_client","error_description":"xxxxx: Application with identifier 'cxxxxxxx7' was not found in the directory 'dxxxx-dxxxxxxb'. This can happen if the application has not been installed by the administrator of the tenant or consented to by any user in the tenant. You may have sent your authentication request to the wrong tenant. Trace ID: 466dxxxx0 Correlation ID: fe1xxxxxx7603 Timestamp: 2026-08-20 10:19:04Z","error_codes":[700016],"timestamp":"2026-08-20 10:19:04Z","trace_id":"46xxxxx300","correlation_id":"fe1bexxxxx03","error_uri":"https://login.microsoftonline.com/error?code=700016"}"

---

The issue appears to be related to the Microsoft Teams V2 integration.

Could you please confirm the following?

Whether the Microsoft Teams V2 integration has been deprecated or recently changed.

Whether the integration requires reauthorization or reconfiguration.

Whether the application registration, tenant ID, or administrator consent needs to be updated.

What steps are required to restore alert delivery to Microsoft Teams.

Example alert:
https://xxxxxx.app.opsgenie.com/alert/detail/fcaab5ef-2414-405e-a3ae-8fac64d0aedd-1787221144218/logs

Our Opsgenie environment:
https://xxxxx.app.opsgenie.com/

Additionally, I am unable to open a support ticket because our legacy Opsgenie URL is not accepted by the support form. Could you please advise us on how to submit this request through the appropriate support channel?

Thank you in advance for your assistance.

Best regards,

[Thomas Zinckgraf · Accepted solution]

We are facing the exact same issue. I assume that tenant is an OpsGenie tenant. Given that first and last letter, we see the same thing.

[Hufi]

I already raised a P1 ticket for this

[panchaly01]

Hi, we are getting exact same issue. Please update once you receive any feedback on that ticket. Thanks 

[Hufi]

last update was this morning 8 am CEST:

Hello,
You are receiving this as a bulk update, posted to multiple tickets.

Our Engineering teams continue to work with Microsoft to restore connectivity between our Opsgenie Legacy MS Teams Integration and the MS Teams ecosystem. We do not have an ETA for restoration at this time, as we continue to work with our vendor and investigate both restoration and alternative workaround options.

As updates develop, we will endeavour to inform you as our affected customers.

Kind Regards,
Scot Wilson (Senior Support Engineer for Atlassian’s APAC ITSM)

[Kamal Jebelli]

Hello, 

Same issue on our side. All integration with Teams stopped Aug 19 around 10 am EST.

Other integrations are working fine ( with slack etc ).

Hopefully it can be resolved soon... 

[Chris Osborne]

We are having the same issue. We are also hoping for a solution soon.  

[Jeremy Bailey]

Looking for updates

[Tony Wu]

We are having the same issue. We are also hoping for a solution soon.  

[Philippe Mailhot]

Same problem here!  But why isn't the status page showing "degraded" for the OpsGenie product?

[Danny Wedel]

FYI, This issue is recognized and posted here:

https://opsgenie.status.atlassian.com/incidents/2c1bx0zpvmws

[Danny Wedel]

We are experiencing this same issue that also started on Aug 19. I happened upon this thread, which confirmed my suspicion that there is a larger issue at play.

During my troubleshooting, I attempted to reconfigure the integration fresh, deleting the old integration and reinstalling the Opsgenie app, and I still can't get it to work. It seems to be an issue with the Opsgenie bot not responding to any commands.

We use our Teams integration regularly to chat and troubleshoot alerts. PLEASE FIX IT!!

[Joey Willis]

They finally fixed it.  Go to your teams channel that has opsgenie, click on apps, and it has an update button.

[Danny Wedel]

Unfortunately, it's not working for us yet. Perhaps the fix is still propagating or something, but there's no update button on the app. I also tried removing and reinstalling the app, but still no response from the bot using @OpsGenie help

[Joey Willis]

When I searched for the app in the actual apps section it didn't show an update and it wouldn't work for me either.   I finally went to the team or channel it was in, selected apps, and it had an update button at the top.   Then I had to select what channel to allow it in again.  

[Jeremy Bailey]

I couldn't find the Update button either.  It turns out that you need to clear your cache directory in Teams, and restart

1. Quit Teams

2. Delete AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams

3. Start Teams

4. Manage Apps, Find OpsGenie, see Update button

[Chris Osborne]

These steps worked for me, and service has been restored. Thank you for getting this resolved.  Thank you for posting the steps that worked for you, this was helpful.

[Joey Willis]

This shows as solved, but we haven't received a resolution.  Has anyone actually been able to get this working again?   We are rushing to drop Opsgenie completely because of this.   Originally, we were going to migrate to Jira before the deadline, but the lack of support on this issue has pretty much forced us to look outside of Atlassian.   

[Philippe Mailhot]

Nope ... still a problem from what I see.

[Chris Osborne]

I agree, we have not seen a resolution either.  Out of curiosity, would you care to share what you are researching or reviewing as an option?  We may very well be in the same boat.

[Joey Willis]

We will be testing Pager Duty as a potential replacement starting today.  Lack of support before the actual end of support date is not ok. 

[Philippe Mailhot]

we are moving shortly as well.

[Joey Willis]

They finally fixed it.  Go to your teams channel that has opsgenie, click on apps, and it has an update button.

[Abu]

@Joey Willis @Philippe Mailhot , if you're still building the replacement list, check out AlertOps.

Direct Opsgenie replacement, migration is assisted rather than a DIY export.

I work there, so grain of salt, but it's the closest 1:1 swap you'll find: https://alertops.com/compare/opsgenie/

[Joey Willis]

Someone reached out, and another service provider that we work with often suggested this also.   We haven't signed anything with PagerDuty yet so our team will review this.