Last updated: November 18, 2026
By ZapAI Team
Dynamics 365 SLAs turn a support promise into a timer on every case, with warnings before a miss and a record when one happens. Our Dynamics 365 Customer Service consultants design SLAs and entitlements for mid-market US support teams, and this guide covers SLA KPIs, items, Power Automate actions, pause and resume, calendars, entitlements, the timer, reporting and licensing, checked against Microsoft Learn on November 18, 2026.
A Dynamics 365 SLA is a set of SLA items, each tracking one KPI such as first response or resolve by. Items set when they apply, what counts as success, warning and failure times, business hours and pause rules.
Here’s a hypothetical. A support director promises platinum customers a one-hour first response. Six weeks later a platinum account escalates to the CEO. The case sat for three hours over a holiday weekend, and no alert fired.
Nobody broke anything. The SLA had no holiday schedule, the warning flow was turned off, and the case carried the default SLA because the customer’s entitlement had quietly expired two weeks before the holiday. Our Dynamics 365 Customer Service guide covers the product as a whole. This post goes one level down, into the SLA and entitlement design that decides whether that timer tells the truth.
What Is an SLA in Dynamics 365 Customer Service?
It’s a rule set that measures time against a promise. Microsoft’s SLA configuration guide, updated November 6, 2026, lays out the build order. Create SLA KPIs, create SLAs with SLA items, configure actions, then apply them.
| Building block | What it holds | Where you set it |
|---|---|---|
| SLA KPI | The thing you measure, such as first response by or resolve by, plus the table, KPI field and Applicable From date | Service terms, SLA KPIs |
| SLA | A named container tied to one primary table | Service terms, Service-level agreements |
| SLA item | One KPI with Applicable When, Success Conditions, warning and failure durations, business hours and pause settings | Inside the SLA |
| Actions | A Power Automate flow with branches for nearing noncompliance, succeeded and noncompliant | Configure Actions on the item |
| SLA KPI instance | The runtime record per KPI per case, with status, warning time and failure time | Created automatically |
| Customer service schedule | Work hours, breaks, time zone and holiday schedule | Operations, Calendar |
A few prerequisites trip teams up. Admins need the CSR Manager role or equivalent privileges, and Microsoft says users who activate or manage the SLA flows need global read and write privileges on SLA KPI instances as well. Want a KPI the case table doesn’t ship with, like an escalated-by timer? You add a lookup field to SLA KPI Instance first.
Skip customizing the SLA, SLA KPI and SLA item admin forms. Microsoft asks for that. Leave them alone.
Are Legacy Standard SLAs Still Supported?
They still run, but they’re on borrowed time. Microsoft’s Customer Service deprecations list says standard SLAs, where the SLA Type field is Standard, are deprecated and will be removed in a future major release, and we found no removal date on that page as of November 18, 2026. Plan anyway.
Older changes matter too. SLAs in the web client were deprecated on October 1, 2020. Contracts, contract lines and contract templates lost support on April 1, 2022, with entitlements named as the replacement.
Today’s model is the one you build in Copilot Service admin center, which Microsoft’s docs still call enhanced SLAs in places. A migration tool sits under Miscellaneous, then ARC and SLA migration, and it can run more than once, tags migrated rules with a _migrated suffix, and leaves legacy rules running until you turn them off. Microsoft’s SLA limitations page adds that orgs with more than 1,000 legacy SLAs might fail the premigration check.
Our advice? Don’t migrate rule by rule. Rebuild the design first, then migrate only what still fits it.
Which Records Can Carry an SLA?
Cases, mostly. But not only cases. Per Microsoft’s guide to enabling tables for SLAs, you can turn on SLAs for account, contact, order, invoice, quote, opportunity, lead, activities like email and phone call, and custom tables.
Hard limits come from the same page.
- Active SLAs on seven tables at most.
- No more than five SLA KPIs per table, as Microsoft’s recommendation.
- Up to 100 SLA items per SLA table, with fewer than 15 recommended.
Fifteen items sounds like plenty until someone builds one item per product per priority per tier. We’ve seen that grid. It’s unmaintainable within a quarter.
What about SLAs for conversations?
Here’s the gap. The conversation table isn’t on Microsoft’s list of SLA-enabled tables, and we found no Learn page that documents SLA KPIs on chat or messaging conversations. What exists for live chat is the live conversation counter, a workstream setting that shows reps how long a customer has waited without a reply, with Warning and Urgent thresholds you define.
Live chat only, though. For queue wait targets on chat and voice, the overflow wait thresholds in our unified routing guide do more work, and our Dynamics 365 Contact Center post covers the channel side. When a conversation becomes a case, the case SLA takes over.
How Do You Configure SLA KPIs and SLA Items?
Start with the KPI. Pick the table, the KPI field (for example FirstResponseByKPI) and an Applicable From field such as Created On, which is the moment the clock starts for every case the SLA touches. Microsoft says Applicable From, warning time and failure time must be datetime fields, not date fields. Easy to miss.
Next comes the SLA and its items. Each item ties to one KPI and carries five decisions.
- Applicable When. The conditions that must stay true for the item to apply.
- Success Conditions. What ends the clock as a success, such as first response sent equals yes.
- Warn and fail durations. Warning is optional and can be left empty.
- Business hours. A customer service schedule. Leave it blank and the clock runs all day, every day.
- Allow Pause and Resume. You can’t change this after the item’s first save.
Applicable When is the setting that bites. Microsoft says the SLA triggers only while the condition stays met, and if it stops being met after the SLA starts, the KPI instance is canceled and the clock you were relying on simply disappears. So don’t build conditions on fields reps change all day. Status is the classic trap.
Microsoft’s SLA limitations page adds sharper edges. Conditions on related tables work only the first time they’re met, and a success condition placed on a related table never turns true, so the instance sits in progress or noncompliant forever. You can’t create two items with the same Applicable When and KPI. Modified On makes a poor condition or start field. And nobody can manually edit SLA time.
Those related-table rules matter for B2B teams. If tier lives on the account, copy it onto the case and condition on the case field.
How Do SLA Warning and Failure Actions Work?
Through Power Automate. Select Configure Actions on an item and a predefined flow opens with a switch for three outcomes, Is Nearing Non-Compliance, Is Succeeded and Is Non-compliant. You add steps under each, such as sending an email from a template with the msdyn_SendEmailFromTemplate action.
Microsoft warns against editing the predefined parts of that flow. Add actions inside the branches and leave the scaffolding alone.
One flow does the real work behind every timer. If SLAWarningAndExpiryMonitoringFlow is turned off, KPI instances never reach nearing noncompliance or noncompliant, and the timer shows a warning that the instances might be incorrect until an admin turns the workflow back on. Check it after every deployment.
Volume matters too. Microsoft notes SLAs are subject to Power Automate platform limits, and exceeding them can slow your flows. Our Power Automate use cases post shows escalation patterns that hold up at volume.

How Do SLAs Get Applied to a Case?
Four ways, with a fixed order. Microsoft’s apply SLAs guide lists automatic logic (workflow, flow or plug-in), the entitlement on the case, manual selection in the SLA field, and a default SLA that catches everything else.
Precedence runs automatic first, entitlement second, default last. Order matters. The default SLA for cases covers every case without an entitlement SLA, which suits customers who expect service but never bought a contract.
Three rules shape the design.
- Only one SLA applies to a record. Apply another and the first is canceled.
- The SLA is reapplied when a field used in an Applicable When condition changes, and warning or failure actions can fire again if time has already passed.
- KPI instances in a terminal state aren’t reevaluated unless you turn on Recalculate SLA on terminal status. Noncompliant stays noncompliant either way.
That first rule is why we put all tiers in one SLA with tier-specific items rather than one SLA per tier. Swapping SLAs mid-case throws away history. History matters in disputes.
Bulk imports deserve a pause. A system administrator can switch SLAs off in system settings during maintenance or data loads, so thousands of migrated closed cases don’t wake up as fresh breaches on the first morning.
How Do SLA Pause and Resume Work?
At three levels, and the most specific wins. Per Microsoft’s pause conditions guide, you set default pause statuses per table under Other SLA Settings, override them on an SLA KPI, and override both on an SLA item.
| Level | Where | Use it for |
|---|---|---|
| Table | Service terms, Other SLA Settings, Service Configuration Settings | Statuses like waiting on customer that pause every SLA on cases |
| SLA KPI | Pause Conditions with Override Criteria on the KPI | A KPI that should keep running when others pause, such as overall resolve time |
| SLA item | Pause Configurations on the item | One tier or product line with its own pause rules |
Two behaviors surprise people. Resuming cancels the current KPI instance and creates a new one, so any report that simply counts instances will double-count paused cases unless you filter canceled rows out of the data first. And if a rep puts a case on hold after its warning time, Microsoft says the warning time isn’t updated on resume.
Pause invites gaming, too. If reps can set waiting on customer without contacting the customer, your compliance rate means less than it looks.
How Do Business Hours and Holiday Schedules Affect SLAs?
They decide what an hour means. A customer service schedule sets work days, hours that are the same each day or vary by day, or 24×7 support. It also handles breaks, a time zone that follows daylight saving, and an observed holiday schedule.
Holidays live in their own record. Microsoft’s holiday schedule guide shows the current year’s holidays by default, and you can’t import or export a holiday schedule in Excel format. Someone has to add next year’s dates before January. Put it on a calendar.
Multi-region teams have two options. Both work. Build one SLA item per region with its own schedule, or keep one item and use custom time calculation, which Microsoft supports only through a plug-in that picks the calendar at runtime. We’d pick the items until the count nears 15.
Try a quick sanity check. A two-business-day email promise on a Friday afternoon before a long weekend should land on Wednesday. If your test case says Monday, the holiday schedule isn’t observed.
How Do Entitlements Work With SLAs?
An entitlement says how much support a customer bought, and it can carry the SLA that governs it. That link is optional. Microsoft’s entitlements guide covers the fields below.
| Setting | What it does | Watch for |
|---|---|---|
| Allocation type | Number of hours or number of cases | Hours-based terms decrement only when the case is resolved, per Microsoft’s troubleshooting guidance |
| Decrease remaining on | Case creation or case resolve | On creation, canceling a case gives the term back |
| Total and remaining term | The pool and what’s left | Remaining can go negative |
| Restrict based on entitlement terms | Blocks new cases when remaining terms drop below zero | No means cases still save and the balance goes negative |
| SLA | The SLA applied through this entitlement | Beats the default SLA, loses to automatic logic |
| Entitlement channels | Separate terms per channel, such as 80 phone hours and 20 email hours | Add after the first save |
| Products and contacts | Limit coverage to listed products or named contacts | Blank means all products and all contacts |
Lifecycle rules matter. An entitlement with future dates sits in Waiting and goes Active on its start date. An active entitlement can’t be edited until you deactivate it. Renew creates a new Draft record with the same length, starting today.
Default entitlements apply automatically on case create or update, depending on system settings, and reps can tick Do not decrement entitlement terms for goodwill cases they don’t want charged against the customer’s balance. Entitlement templates prefill dates, SLA, allocation type, total term and channels, so sales can’t invent a fourth tier by accident.
What Does a Good SLA Design Look Like?
Simple enough that a supervisor can explain any timer. Keep it boring. The table below is an example structure for a B2B support team with three paid tiers. It’s an illustration, not a benchmark, so set your own numbers from your own case history.
| Tier (example) | First response by | Resolve by | Warning at | Schedule | Pause on |
|---|---|---|---|---|---|
| Standard | 8 business hours | 5 business days | 75% of the target | Weekday business hours, US holidays observed | Waiting on customer |
| Priority | 4 business hours | 3 business days | 75% | Extended weekday hours | Waiting on customer |
| Premium, severity 1 | 1 hour | 1 calendar day | 50% | 24×7 | None for first response |
| Premium, other severities | 2 business hours | 2 business days | 75% | Extended weekday hours | Waiting on customer |
That’s one SLA with eight items across two KPIs. It fits Microsoft’s guidance with room left. Tier and severity both live on the case, so no condition reaches into a related table.

How Do You Add the SLA Timer to the Case Form?
As a subgrid with a custom component. Per Microsoft’s timer control guide, add a subgrid on the Case for interactive experience form, point it at SLA KPI Instances (Regarding) with the All SLA KPI Instances view, then add the SLA Timer component.
Three settings deserve attention.
- Update frequency defaults to 30 minutes. Shorter feels live but costs performance.
- Turn on negative countdown so reps see how far past failure a case is.
- Filter the view to KPIs reps act on. Six timers on one form get ignored.
Only SLAs built in Unified Interface appear on the timer, and it reads No Applicable SLA when nothing applies. Seeing that on a premium case? Check the entitlement first. Our sister post on Dynamics 365 case management covers the rest of the case form.
How Do You Report on SLA Compliance?
Not from the out-of-box dashboards alone. Microsoft’s Customer Service dashboards page lists Summary and Agent reports in historical analytics. They refresh once every 24 hours with no way to trigger a refresh on demand, keep 24 months of data, and draw on tables like incident, queue item and survey responses. SLA KPI instances aren’t on that table list.
So reporting is usually custom. Microsoft’s data model customization guide lets you extend the historical Power BI model with your own Dataverse tables. It publishes to a Microsoft Fabric workspace and embeds up to 40 custom reports back into Copilot Service workspace.
Setup isn’t trivial. You need an Entra ID security group with the Dynamics 365 Analytics service account, several Fabric tenant settings turned on by a Power BI admin, and up to 24 hours of provisioning before anything appears. Microsoft says it applies to Customer Service and Contact Center standalone only, and that specific licensing requirements apply to report users and authors.
We build four metrics first. Compliance rate by KPI and tier, breach count by queue, warning-to-breach conversion, and time paused per case. Exclude canceled instances or the numbers inflate. Our sister post on Dynamics 365 Customer Service analytics covers the dashboards, and how Power BI helps businesses make better decisions covers report design.
Which Licenses Do SLAs and Entitlements Need?
The core features ride with the Customer Service plans. Microsoft’s Customer Service pricing page on November 18, 2026 lists Professional at $50, Enterprise at $105 and Premium at $195 per user per month. It doesn’t list SLAs or entitlements as rows at all.
| Capability | Professional | Enterprise | Premium |
|---|---|---|---|
| Case management | Included | Included | Included |
| SLAs and entitlements | Our reading is included, confirm in the licensing guide | Included, per our reading | Included, per our reading |
| Analytics and KPI reporting | Not included | Included | Included |
| Unified routing | Not included | Included | Included |
| Copilot in Customer Service | Not included | Included | Included |
Two caveats. Learn says specific licenses apply to users who create actions on SLA KPI instance statuses, which points at the Power Automate side. The pricing page also footnotes that embedded Power BI content might need a separate Power BI license. Confirm both against the current Dynamics 365 licensing guide before you buy, and see our Dynamics 365 overview for where Customer Service sits next to Sales, Field Service and the rest of the lineup.
Which AI and Copilot Features Touch SLAs in 2025 and 2026?
Fewer than you’d expect. We found no generally available feature in Customer Service that predicts SLA breach risk per case.
| Item | What it does with SLAs | Status we found |
|---|---|---|
| Customer Service plugin for Copilot Cowork (roadmap RM576851) | Briefs reps at intake with customer, history, prior cases and an SLA snapshot | Listed as launched, GA June 2026, admin must enable it |
| Intraday Agent (roadmap RM577184) | Autonomous agent for intraday operations like staffing adjustments | In development, preview listed for September 2026, GA March 2027 |
| Conversation orchestration playbooks | Dynamic priority and overflow on voice and messaging, which affect wait time | Covered in our unified routing guide |
Roadmap dates move. Treat the intraday agent as a pilot candidate, not a plan. Agents also answer better from clean articles, which our knowledge management post covers.
What Mistakes Break Dynamics 365 SLAs?
In our experience, these cause most bad SLA reports.
- No customer service schedule, so business-hour promises run on 24×7 clocks.
- Stale holiday schedules.
- A disabled monitoring flow.
- Applicable When built on status or owner, so instances cancel when cases move.
- Tier conditions on the account table instead of the case.
- One SLA per tier, swapped mid-case, wiping history.
- Expired entitlements quietly dropping premium customers to the default SLA.
- Reports that count canceled instances from pause and resume.
- Testing as System Administrator instead of a real rep role.
That last one hides gaps. Our Dataverse security roles guide explains why, and our Dynamics 365 implementation checklist shows where SLA testing fits before go-live.

What Belongs on an SLA Setup Checklist?
Twelve steps, in order.
- Write the promises in plain English per tier, with business owner sign-off.
- Pull last year’s case data to test whether the targets are reachable.
- Create holiday schedules and customer service schedules for every time zone you serve.
- Copy tier and severity onto the case if they live elsewhere.
- Enable SLAs on any table beyond case and add lookup fields for custom KPIs.
- Create SLA KPIs with datetime Applicable From fields.
- Build one SLA per table with items per tier and severity.
- Set pause statuses at table level, then override only where needed.
- Configure warning and failure actions and confirm the monitoring flow is on.
- Set the default SLA. Then build entitlement templates and entitlements.
- Add the timer to the case form and test with non-admin rep accounts across a weekend and a holiday.
- Build the compliance report before go-live, not after the first complaint.
ZapAI Decision Rules for SLAs and Entitlements
These are our practice opinions from projects, not Microsoft guidance. Treat them as starting defaults.
| Situation | Our rule |
|---|---|
| Under about five tiers and severities | One case SLA with items per combination. No custom time calculation |
| Customers sell or renew support contracts | Entitlements with templates and Restrict set to Yes for prepaid hours |
| Customers with no contract | Default SLA with Standard targets |
| Multiple US time zones | One schedule per support hub, not per customer |
| Warning timing | Around 75% of the target, 50% for one-hour promises |
| Live chat wait targets | Live conversation counter plus routing overflow, not case SLAs |
| Leadership wants AI breach prediction | Build clean compliance data first. Revisit at the next release cycle |
One rule outranks the rest. If a supervisor can’t explain why a timer shows red, the design is too clever.
Wrapping Up
Get the clock right before the alerts. Calendars, pause statuses and Applicable When decide whether a timer is true, entitlements decide which promise applies, and flows only report what the clock already says after the fact. Build the compliance report early and test across a holiday.
ZapAI is a Microsoft Dynamics 365, Power Platform, Fabric and AI consulting firm in Irving, Texas, working with businesses across Dallas-Fort Worth and nationwide. Our Customer Service team designs SLAs and entitlements for mid-market support teams. Want a second look? Ask for an SLA design review, and we’ll walk through your KPIs, calendars and entitlements with you.
Questions Support Leaders Ask About Dynamics 365 SLAs
Can one case have more than one SLA?
No. Only one SLA applies to a record. One SLA can track several KPIs through its items, so first response and resolve by run side by side.
Why didn’t my SLA warning email fire?
Check SLAWarningAndExpiryMonitoringFlow first. Start there. When it’s off, instances never reach nearing noncompliance and the timer shows a warning. Then check the action flow and the warning duration on the item.
Does pausing an SLA create a new KPI instance?
Yes. Microsoft says resuming cancels the current instance and creates a new one. Filter canceled instances out of compliance reports.
Do SLAs work on chat conversations?
We found no Learn documentation for SLA KPIs on the conversation table. Live chat has a live conversation counter with Warning and Urgent thresholds, and cases created from conversations carry normal case SLAs.
What happens when an entitlement runs out?
With Restrict based on entitlement terms set to Yes, reps can’t create cases against it. With No, cases save and remaining terms go negative.
Are standard SLAs being removed?
Microsoft lists them as deprecated, to be removed in a future major release. We found no date. Plan the move to SLAs built in Copilot Service admin center now.
Is SLA reporting included out of the box?
Partly. Historical analytics covers case and rep metrics, but SLA KPI instances aren’t in its table list. Most teams extend the Power BI data model or build a separate report.
