Microsoft 365 service-impact investigation

When to use

Use this guide when you need to determine the scope and likely cause of a Microsoft 365 service problem.

What you need

Replace these bracketed values before you copy the prompt.

• symptomRequired

  Observed Microsoft 365 symptom or service failure.

• affected usersOptional

  Optional affected users or population.

• time windowOptional

  Optional bounded incident window.

Information used

Stackyapper uses only the Apps and permissions available to the current user.

• User directoryRequired
• Identity securityIf available
• LicensingIf available
• Mailbox settingsIf available
• Identity configurationIf available
• Service ticketsIf available

Expected output

• Impact scope
• Tenant evidence
• Likely fault domain
• Confidence
• Recommended response

Steps

1. Resolve affected identities and determine whether impact is isolated or widespread.
2. Review security, licensing, mailbox, and configuration evidence relevant to the symptom.
3. Correlate existing reports and prior resolutions.
4. State the affected scope, likely fault domain, confidence, and next diagnostic or escalation step.