After a confirmed multi-hour Microsoft 365 outage that breached covered SLA terms, city finance asks what contractual remedy may apply. What is the fundamentals answer?
Select an answer to reveal the explanation.
Short Explanation
When a covered outage blows past the SLA, the money conversation is usually about service credits—not owning Microsoft's source code. Finance asks; the agreement spells out the credit path.
Full Explanation
After a confirmed multi-hour Microsoft 365 outage that breached covered SLA terms, city finance should understand that service credits may compensate for validated SLA breaches according to the agreement. That contractual remedy is the fundamentals answer—not ownership of Microsoft source code or firing individuals named in Service health.
Finance cannot demand Microsoft fire any engineer named in Service health as an SLA remedy. The city does not automatically receive ownership of Microsoft source code. SLA breaches do not permanently disable billing for all future Microsoft products worldwide.
Exam caveat: eligibility, calculation, and claim windows are defined in the SLA and product terms—partners may assist CSP customers. Operational check: assemble outage duration evidence, map it to covered services in the SLA, and file the credit request through the documented channel before deadlines. In municipal Microsoft 365 fundamentals scenarios, map the business need to the named capability, reject distractors from a different pillar, and verify the control or commercial setting in the admin or billing experience before reporting risk closed to leadership. In municipal Microsoft 365 fundamentals scenarios, map the business need to the named capability, reject distractors from a different pillar, and verify the control or commercial setting in the admin or billing experience before reporting risk closed to leadership.