Miscellaneous topics that do not fit into specific categories.
For Microsoft 365 and related services, the initial response time depends on the severity level selected for the incident:
- Severity A (critical business impact): less than 1 hour initial response
- Severity B (moderate business impact): up to 4 hours initial response on a Standard plan (2 hours on ProDirect/Unified)
- Severity C (minimum business impact): up to 8 hours initial response on a Standard plan (4 hours on ProDirect/Unified)
Waiting a bit over two hours can still be within the expected response window for Severity B or C incidents.
If the issue is related to a Microsoft 365 service problem:
- Check Service health in the Microsoft 365 admin center to see if there is an active incident affecting the tenant. If the issue is already listed there, all current updates are posted in that feed and opening or waiting on a separate support case is usually not necessary.
- If the problem is not shown in Service health, use the Report an issue option from the Service health page or open a support request from the Microsoft 365 admin center to ensure the incident is logged correctly.
If continuous 24x7 engagement is required (for example, a Severity A issue), the customer side must also be available around the clock; otherwise, Microsoft may lower the severity to B or C.
For now, if the incident was logged as Severity B or C, a response the next business day can still be within the documented timeframes. If the situation becomes more critical, update the existing case through the admin center to reflect the higher business impact and severity.
References: