Get-MgSlaCreditEstimate
SYNOPSIS
Estimates the Microsoft 365 SLA service credit for one or more Service Health incidents and prepares the claim.SYNTAX
Estimate (Default)
List
DESCRIPTION
Reads the incidents from Microsoft 365 Service Health, merges the incident windows of each service (two overlapping incidents on the same service are counted once), splits them per calendar month (the SLA measures uptime per month) and returns, for each service and month, the downtime, the uptime percentage, the credit tier and the estimated credit. The credit tiers are the ones of the Microsoft Online Services SLA for the 99.9% services: below 99.9% uptime 25%, below 99% 50%, below 95% 100% of the monthly fee of the affected service. The affected users are the enabled users with an active service plan of the affected service (Exchange Online, SharePoint Online and OneDrive, Microsoft Teams). Use -AffectedUserCount when only part of the tenant was affected, or for a service the function cannot map to a service plan. The credit is computed on the price of the affected service, not on the whole licence: for a suite licence (Microsoft 365 E3, Business Premium…), pass the share of the price that Microsoft assigns to the service with -ServicePrice. Without -ServicePrice for a service, the public list price of its standalone plan is used (Private/Assets/Get-MgSlaCreditEstimate-list-prices.json, excluding VAT, annual commitment: Exchange Online Plan 1 and Plan 2 in EUR and USD, Teams Essentials and SharePoint Plan 1 in EUR) when its currency matches -Currency. For Exchange Online, each licensed user is priced at the plan of their service plan (EXCHANGE_S_STANDARD = Plan 1, EXCHANGE_S_ENTERPRISE = Plan 2, also held by suites such as Microsoft 365 E3), one row per plan; other Exchange plans (Kiosk, F3…) are priced as Plan 1. The Plan and PriceSource columns say which price was used. Without any price, the credit percentage is returned and EstimatedCredit stays empty. With -OutputFolder, the function also writes the incidents, the estimate, the affected users per country, the post-incident reports that are already published, an incident report in Markdown (incident-report.md: timeline, impact, Microsoft updates and estimate) and a claim text to paste into the support request (claim-request.txt, Microsoft 365 admin center > Support > New service request). The function assumes every affected user was affected for the whole incident window: the estimate is a ceiling, Microsoft computes the final credit from its own user-minute measurements.EXAMPLES
EXAMPLE 1
EXAMPLE 2
EXAMPLE 3
EXAMPLE 4
EXAMPLE 5
EXAMPLE 6
PARAMETERS
-AffectedUserCount
Number of affected users per service, keyed by the Service Health service name, when it differs from the licensed users (e.g. @{ 'Exchange Online' = 250 }).
-Currency
Currency of the prices, shown in the output and in the claim text. Default: EUR.-ExportToExcel
Exports the estimate to an Excel file in the user profile instead of returning it, with a second worksheet for the licensed users per country (when the users are counted from the tenant, not from -AffectedUserCount).-IncidentId
One or more Service Health issue IDs (e.g. EX1550543, MO1550821).-IncludeAdvisory
With -ListIncidents, also lists the advisories (minor issues, usually not eligible for a credit).-KnownIncident
Name of a major outage listed in the module (e.g. Exchange-2026-11-12): its Service Health IDs are used, they are the same in every tenant. Press Tab after -KnownIncident to see the names. Can be combined with -IncidentId.-ListIncidents
Lists the Service Health incidents that started since -Since, with their service and duration, to pick the IDs to pass to -IncidentId. Advisories are left out unless -IncludeAdvisory is set.-OutputFolder
Folder for the CSV files, the post-incident reports and the claim text. Created when missing.-ServicePrice
Monthly price per user of each affected service, keyed by the Service Health service name (e.g. @{ 'Exchange Online' = 4; 'Microsoft Teams' = 3.2 }).
Overrides the public list price of the service.