Predictika · Microsoft 365 enterprise licensing
An AI sales agent prepares a Microsoft 365 license quote under an Enterprise Agreement: suites, Copilot seats, term, price level, discount. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the enrollment, term, add-on and true-up rules, returns a verdict and every reason, and builds the line-item quote from the same rules.
This validator models Microsoft 365 suite and Copilot quotes under Enterprise Agreement and MCA-E programs, not just the scenarios shown below.
Not covered: Dynamics 365, Azure, Surface and other hardware, Windows 365, CSP resale and other Microsoft 365 plans. Prices are Microsoft's public US list prices per user per month and every amount here is an estimate: negotiated Enterprise Agreement and MCA-E prices are not public. The discount limit (10 percent) is a placeholder, and the program rules come from public licensing guides and have not been confirmed with Microsoft.
7 scenarios in 3 groups · each group runs from the agent’s first attempt to the outcome · click one to switch
Proposing agent: AI sales agent (scripted)
Before sending, the agent must call Recorded run
What this means
Our assessment of what a typical rules-based CPQ (product rules, price rules and validation rules) does with the same cases. It is a judgment about effort and reliability, not a claim that nothing can be built.
| What the validator caught | Typical rules-based CPQ | Predictika |
|---|---|---|
| A price level that Microsoft stopped offering to commercial customers in November 2025, still quoted | Only with care Legacy price books keep the level tiers. A rule has to switch them off by customer type and date, and each policy change means another rule to maintain. | The level is a field on the quote and is checked against the customer type on every call. |
| An add-on that must end with the enrollment, when the end date sits on the existing subscription | Only with workarounds Co-terming reads the remaining months from another record. A quote rule can check it only if that number is copied onto the quote, and the price has to be prorated by hand. | Months remaining travel with the request; the add-on term is compared with them and the price is charged for exactly those months. |
| Rules that differ by program: true-up exists only under the Enterprise Agreement, terms are 36 months for one and 12 to 36 for the other | Only with care One set of product rules per program, each tied to the quote type. Works, but a rule written for one program can quietly fire for the other. | All of it follows from the program field; the findings come back together. |
| Copilot seats need a qualifying suite on each user, including seats already on the enrollment | Only with workarounds The count of existing seats lives in the install base, not on the quote, so a rule needs it copied in and kept current. | Existing seats travel with the request and are added to the quoted suite seats before the check. |
| A quote that states a total or seat count different from what its lines give | Only with care A validation rule can compare a stated figure with a calculated field, but only if the stated figure is a field on the quote, which it rarely is. | The stated total and seat count travel with the quote and are compared with the computed ones on every call. |
| Every problem returned in one answer | Only with workarounds Rules tend to fire as the quote is saved or a step is completed, so a rep often fixes one error and meets the next. | All findings come back together, whatever order the choices arrived in. |
Every rule is checked on every call, in any order the choices arrive; one problem never hides another. Blocking findings stop the quote; approval findings need a person to sign off. N stands for the figure in the quote.
| 1 | A new or renewing Enterprise Agreement needs at least N users and devices for this type of customer (500 commercial, 250 public sector); this enrollment has N. |
| 2 | N Microsoft 365 suite seats (including seats already on the enrollment) exceed the N users in the organization. |
| 3 | N Microsoft 365 Copilot seats are quoted but only N users have a qualifying Microsoft 365 suite; Copilot is an add-on that needs a qualifying base license on each user. |
| 4 | Price level N is quoted for online services to a commercial customer; since November 1, 2025 commercial online services are priced at Level A (list price), so Levels B, C and D no longer apply. |
| 5 | An Enterprise Agreement enrollment runs 36 months; the quote specifies N months. |
| 6 | MCA-E subscriptions run 12 to 36 months; the quote specifies N months. |
| 7 | MCA-E has no annual true-up; seats are added as new subscriptions with their own terms. |
| 8 | An Enterprise Agreement add-on is co-termed to the enrollment; the add-on runs N months but N months remain on the enrollment. |
| 9 | The annual true-up order must reach Microsoft between 60 and 30 days before the anniversary; this order is N days before. |
| 10 | Seat reductions are allowed only at the anniversary of an enrollment or at the end of a subscription term, not mid-term. |
| 11 | The quote states a total of N USD; the validator computes N USD. |
| 12 | The quote states N licensed suite seats; the lines add up to N. |
| 13 | A discount of N percent is above the 10 percent limit this validator allows even with approval (placeholder; Microsoft does not publish negotiation authority). |
| 14 | Price level N is requested for a public-sector customer; public sector was exempt from the November 2025 change but the level thresholds are not public, so a licensing specialist must confirm it. |
| 15 | Online services are priced at list, so a discount of N percent is a negotiated exception and needs approval. |
| 16 | N devices do not have a qualifying Windows Pro license; Windows Enterprise in Microsoft 365 is an upgrade license and needs a Windows Pro base. |