← Back to Jira History
minor✓ Resolved

Degraded performance with Microsoft incoming emails

Jira•
Status
resolved
Duration
1d
Updates
5
Coverage
0 articles

INCIDENT TIMELINE

✓ Resolved
This incident has been resolved.
resolved
Incoming email processing for Microsoft-connected mailboxes in Jira and Jira Service Management has returned to normal. This incident is now resolved. For more details on the service degradation reported by Microsoft, please refer to Microsoft service health status.
monitoring
We continue to see signs of improvement for incoming email processing with lower failure rates. Teams continue to monitor recovery from Microsoft, and we will share the next update when there is a significant change. For more details on the service degradation reported by Microsoft, please refer to https://status.cloud.microsoft/
identified
Incoming email processing is showing signs of improvement, but some failures continue. Teams continue to monitor recovery from Microsoft. We will share the next update if there is any significant change. For more details on the service degradation reported by Microsoft, please refer to -https://status.cloud.microsoft/
investigating
Incoming email processing is still experiencing failures, and teams continue to monitor recovery from Microsoft. We will share the next update if there is any significant change. For more details on the service degradation reported by Microsoft, please refer - https://status.cloud.microsoft/
investigating
Jira and JSM incoming emails are experiencing elevated failures when processing mail, resulting in a reduction in the number of emails handled and a noticeable drop in incoming email processing. The issue is attributed to the ongoing global service degradation with Microsoft 365 services. More details can be referred on their status page - https://status.cloud.microsoft/

📊 TECHNICAL DETAILS

Internal ID
fc947f62-6d5f-4cf9-bdf4-1be069ec844c
External ID
d5393cmcng14
🕐 Started
🔄 Last Updated
✓ Resolved
MINOR
Impact Level
1d
Total Duration
5
Status Updates
Affected Components
Create and edit
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we request generation of one.
0 / 100 requests100 more needed