yasoon Outage History

We are currently experiencing degraded performance in Microsoft Teams for Jira & JSM due to rate limiting imposed by the Atlassian API. This may result in delayed notifications, slower response times, or temporary failures of certain app features. We are actively monitoring the situation and working to minimize the impact. We apologize for the inconvenience and will provide updates as more information becomes available.

We have identified an issue with missing channel message automation triggers. It seems Microsoft is currently not sending webhooks for all incoming channel messages, so we are currently unable to send out triggers for missing webhooks. We are looking at potential fixes, but hope that the affected Microsoft upstream service will be restored soon.

We have identified an incident where a subset of users will see error messages when trying to login with their Microsoft account. Upon investigation we discovered that Microsoft seems to be rolling out a set of changed browser headers which are causing issues. We are working on a fix - in the meantime, re-trying to login for a few times seems to solve the issue for most users.

We have identified an issue with the Microsoft Teams platform that affects apps on a certain feature/schema version. We are trying to fast-track an app update to a previous version which is apparently not affected by this bug. We are also trying to escalate the bug within Microsoft.

We are currently seeing a bug affecting the Atlassian Forms API, regarding to the new conditional section logic. Please refrain from updating Forms until the bug is fixed, otherwise the conditions will not be evaluated correctly in our Microsoft Teams portal app.

We are in active contact with Atlassian to get the bug fixed as soon as possible, please refrain from updating your Forms, if possible, until this issue is resolved.

Atlassian is working on a fix for this issue, please let us know in case you are affected, Atlassian has the ability to roll back the change temporarily on a case by case basis.

We got an update from Atlassian engineering and they expect the bug to be fixed in "a weeks time". We'll update the incident accordingly once the fix is available.

We are seeing a re-occurrence of the issue that happened a few weeks ago. We are currently seeing an increased amount of errors in the chat functionality, coming from the Microsoft Graph API. We'll provide an update once we have more information.

We are continuing to work with Microsoft on the issue and hope to have an update soon. If you see errors when creating chats, please try to create the chat again. It's also possible that the chat is created in Teams, despite an error being shown in Jira.

We have identified an issue where the Outlook add-in currently does not load, due to a Microsoft CDN not being available. Please also track the following issue: https://github.com/OfficeDev/office-js/issues/6249

The issue has been identified and a fix is being implemented.

We are continuing to work on a fix for this issue.

We have identified the issue and a fix will be rolling out shortly.