Microsoft resolves an overlap deterministically and does not show you the reasoning. This is that reasoning, for the groups in your register — groups only, never a person.
Copilot — whole org wins for All employees — per-user limit 50 credits.
Why: Only one spending policy scopes this group, so there is nothing to resolve — per-user limit 50 credits.
Microsoft's rule for spending policies: the highest per-user limit first, then the largest overall policy limit, then the most recently created policy — policies do not combine and do not inherit the tenant default.
A member can spend today: 50 credits ≈ $0.50 — the per-user limit on “Copilot — whole org”. This is an alert, not a cap — the cap lives in your spending policy.
A limit, never anybody's usage: it is the ceiling Microsoft would apply to any one member of this group.
Legacy Copilot-Credits billing attributes to Copilot Credits — original billing policy.
Only one legacy billing policy scopes this group, so its usage attributes there (configured 20 August 2025).
Microsoft's words: “If a user is covered by multiple billing policies, this report attributes the usage to the oldest configured billing policy.” — a different rule from the spending tie-break above, for a different mechanism.
Copilot pilots — higher limit wins for Copilot pilots — per-user limit 200 credits.
Why: It has the highest per-user limit (200 credits), and Microsoft's first step is the highest per-user limit.
Microsoft's rule for spending policies: the highest per-user limit first, then the largest overall policy limit, then the most recently created policy — policies do not combine and do not inherit the tenant default.
In Microsoft's resolution order: Copilot pilots — higher limit → Copilot — whole org
A member can spend today: 200 credits ≈ $2.00 — the per-user limit on “Copilot pilots — higher limit”. This is an alert, not a cap — the cap lives in your spending policy.
A limit, never anybody's usage: it is the ceiling Microsoft would apply to any one member of this group.
Legacy Copilot-Credits billing attributes to Copilot Credits — original billing policy.
Only one legacy billing policy scopes this group, so its usage attributes there (configured 20 August 2025).
Microsoft's words: “If a user is covered by multiple billing policies, this report attributes the usage to the oldest configured billing policy.” — a different rule from the spending tie-break above, for a different mechanism.
No single spending policy wins for Corporate Strategy.
Why: No spending policy scopes this group.
Microsoft's rule for spending policies: the highest per-user limit first, then the largest overall policy limit, then the most recently created policy — policies do not combine and do not inherit the tenant default.
No spending allowance is recorded for this group.
Legacy Copilot-Credits billing has no single attribution here.
No legacy Copilot-Credits billing policy scopes this group.
Microsoft's words: “If a user is covered by multiple billing policies, this report attributes the usage to the oldest configured billing policy.” — a different rule from the spending tie-break above, for a different mechanism.
No single spending policy wins for Security.
Why: No spending policy scopes this group.
Microsoft's rule for spending policies: the highest per-user limit first, then the largest overall policy limit, then the most recently created policy — policies do not combine and do not inherit the tenant default.
No spending allowance is recorded for this group.
Legacy Copilot-Credits billing has no single attribution here.
No legacy Copilot-Credits billing policy scopes this group.
Microsoft's words: “If a user is covered by multiple billing policies, this report attributes the usage to the oldest configured billing policy.” — a different rule from the spending tie-break above, for a different mechanism.
No single spending policy wins for Facilities.
Why: No spending policy scopes this group.
Microsoft's rule for spending policies: the highest per-user limit first, then the largest overall policy limit, then the most recently created policy — policies do not combine and do not inherit the tenant default.
No spending allowance is recorded for this group.
Legacy Copilot-Credits billing has no single attribution here.
No legacy Copilot-Credits billing policy scopes this group.
Microsoft's words: “If a user is covered by multiple billing policies, this report attributes the usage to the oldest configured billing policy.” — a different rule from the spending tie-break above, for a different mechanism.
No single spending policy wins for Legal.
Why: No spending policy scopes this group.
Microsoft's rule for spending policies: the highest per-user limit first, then the largest overall policy limit, then the most recently created policy — policies do not combine and do not inherit the tenant default.
No spending allowance is recorded for this group.
Legacy Copilot-Credits billing has no single attribution here.
No legacy Copilot-Credits billing policy scopes this group.
Microsoft's words: “If a user is covered by multiple billing policies, this report attributes the usage to the oldest configured billing policy.” — a different rule from the spending tie-break above, for a different mechanism.
No single spending policy wins for Procurement.
Why: No spending policy scopes this group.
Microsoft's rule for spending policies: the highest per-user limit first, then the largest overall policy limit, then the most recently created policy — policies do not combine and do not inherit the tenant default.
No spending allowance is recorded for this group.
Legacy Copilot-Credits billing has no single attribution here.
No legacy Copilot-Credits billing policy scopes this group.
Microsoft's words: “If a user is covered by multiple billing policies, this report attributes the usage to the oldest configured billing policy.” — a different rule from the spending tie-break above, for a different mechanism.
No single spending policy wins for Research.
Why: No spending policy scopes this group.
Microsoft's rule for spending policies: the highest per-user limit first, then the largest overall policy limit, then the most recently created policy — policies do not combine and do not inherit the tenant default.
No spending allowance is recorded for this group.
Legacy Copilot-Credits billing has no single attribution here.
No legacy Copilot-Credits billing policy scopes this group.
Microsoft's words: “If a user is covered by multiple billing policies, this report attributes the usage to the oldest configured billing policy.” — a different rule from the spending tie-break above, for a different mechanism.
No single spending policy wins for Human Resources.
Why: No spending policy scopes this group.
Microsoft's rule for spending policies: the highest per-user limit first, then the largest overall policy limit, then the most recently created policy — policies do not combine and do not inherit the tenant default.
No spending allowance is recorded for this group.
Legacy Copilot-Credits billing has no single attribution here.
No legacy Copilot-Credits billing policy scopes this group.
Microsoft's words: “If a user is covered by multiple billing policies, this report attributes the usage to the oldest configured billing policy.” — a different rule from the spending tie-break above, for a different mechanism.
No single spending policy wins for Data & Analytics.
Why: No spending policy scopes this group.
Microsoft's rule for spending policies: the highest per-user limit first, then the largest overall policy limit, then the most recently created policy — policies do not combine and do not inherit the tenant default.
No spending allowance is recorded for this group.
Legacy Copilot-Credits billing has no single attribution here.
No legacy Copilot-Credits billing policy scopes this group.
Microsoft's words: “If a user is covered by multiple billing policies, this report attributes the usage to the oldest configured billing policy.” — a different rule from the spending tie-break above, for a different mechanism.
No single spending policy wins for Supply Chain.
Why: No spending policy scopes this group.
Microsoft's rule for spending policies: the highest per-user limit first, then the largest overall policy limit, then the most recently created policy — policies do not combine and do not inherit the tenant default.
No spending allowance is recorded for this group.
Legacy Copilot-Credits billing has no single attribution here.
No legacy Copilot-Credits billing policy scopes this group.
Microsoft's words: “If a user is covered by multiple billing policies, this report attributes the usage to the oldest configured billing policy.” — a different rule from the spending tie-break above, for a different mechanism.
No single spending policy wins for Product.
Why: No spending policy scopes this group.
Microsoft's rule for spending policies: the highest per-user limit first, then the largest overall policy limit, then the most recently created policy — policies do not combine and do not inherit the tenant default.
No spending allowance is recorded for this group.
Legacy Copilot-Credits billing has no single attribution here.
No legacy Copilot-Credits billing policy scopes this group.
Microsoft's words: “If a user is covered by multiple billing policies, this report attributes the usage to the oldest configured billing policy.” — a different rule from the spending tie-break above, for a different mechanism.
No single spending policy wins for Quality Assurance.
Why: No spending policy scopes this group.
Microsoft's rule for spending policies: the highest per-user limit first, then the largest overall policy limit, then the most recently created policy — policies do not combine and do not inherit the tenant default.
No spending allowance is recorded for this group.
Legacy Copilot-Credits billing has no single attribution here.
No legacy Copilot-Credits billing policy scopes this group.
Microsoft's words: “If a user is covered by multiple billing policies, this report attributes the usage to the oldest configured billing policy.” — a different rule from the spending tie-break above, for a different mechanism.
No single spending policy wins for IT.
Why: No spending policy scopes this group.
Microsoft's rule for spending policies: the highest per-user limit first, then the largest overall policy limit, then the most recently created policy — policies do not combine and do not inherit the tenant default.
No spending allowance is recorded for this group.
Legacy Copilot-Credits billing has no single attribution here.
No legacy Copilot-Credits billing policy scopes this group.
Microsoft's words: “If a user is covered by multiple billing policies, this report attributes the usage to the oldest configured billing policy.” — a different rule from the spending tie-break above, for a different mechanism.
No single spending policy wins for Field Services.
Why: No spending policy scopes this group.
Microsoft's rule for spending policies: the highest per-user limit first, then the largest overall policy limit, then the most recently created policy — policies do not combine and do not inherit the tenant default.
No spending allowance is recorded for this group.
Legacy Copilot-Credits billing has no single attribution here.
No legacy Copilot-Credits billing policy scopes this group.
Microsoft's words: “If a user is covered by multiple billing policies, this report attributes the usage to the oldest configured billing policy.” — a different rule from the spending tie-break above, for a different mechanism.
No single spending policy wins for Manufacturing.
Why: No spending policy scopes this group.
Microsoft's rule for spending policies: the highest per-user limit first, then the largest overall policy limit, then the most recently created policy — policies do not combine and do not inherit the tenant default.
No spending allowance is recorded for this group.
Legacy Copilot-Credits billing has no single attribution here.
No legacy Copilot-Credits billing policy scopes this group.
Microsoft's words: “If a user is covered by multiple billing policies, this report attributes the usage to the oldest configured billing policy.” — a different rule from the spending tie-break above, for a different mechanism.
No single spending policy wins for Marketing.
Why: No spending policy scopes this group.
Microsoft's rule for spending policies: the highest per-user limit first, then the largest overall policy limit, then the most recently created policy — policies do not combine and do not inherit the tenant default.
No spending allowance is recorded for this group.
Legacy Copilot-Credits billing has no single attribution here.
No legacy Copilot-Credits billing policy scopes this group.
Microsoft's words: “If a user is covered by multiple billing policies, this report attributes the usage to the oldest configured billing policy.” — a different rule from the spending tie-break above, for a different mechanism.
No single spending policy wins for PMO.
Why: No spending policy scopes this group.
Microsoft's rule for spending policies: the highest per-user limit first, then the largest overall policy limit, then the most recently created policy — policies do not combine and do not inherit the tenant default.
No spending allowance is recorded for this group.
Legacy Copilot-Credits billing has no single attribution here.
No legacy Copilot-Credits billing policy scopes this group.
Microsoft's words: “If a user is covered by multiple billing policies, this report attributes the usage to the oldest configured billing policy.” — a different rule from the spending tie-break above, for a different mechanism.
No single spending policy wins for Finance.
Why: No spending policy scopes this group.
Microsoft's rule for spending policies: the highest per-user limit first, then the largest overall policy limit, then the most recently created policy — policies do not combine and do not inherit the tenant default.
No spending allowance is recorded for this group.
Legacy Copilot-Credits billing has no single attribution here.
No legacy Copilot-Credits billing policy scopes this group.
Microsoft's words: “If a user is covered by multiple billing policies, this report attributes the usage to the oldest configured billing policy.” — a different rule from the spending tie-break above, for a different mechanism.
No single spending policy wins for Customer Success.
Why: No spending policy scopes this group.
Microsoft's rule for spending policies: the highest per-user limit first, then the largest overall policy limit, then the most recently created policy — policies do not combine and do not inherit the tenant default.
No spending allowance is recorded for this group.
Legacy Copilot-Credits billing has no single attribution here.
No legacy Copilot-Credits billing policy scopes this group.
Microsoft's words: “If a user is covered by multiple billing policies, this report attributes the usage to the oldest configured billing policy.” — a different rule from the spending tie-break above, for a different mechanism.
No single spending policy wins for Operations.
Why: No spending policy scopes this group.
Microsoft's rule for spending policies: the highest per-user limit first, then the largest overall policy limit, then the most recently created policy — policies do not combine and do not inherit the tenant default.
No spending allowance is recorded for this group.
Legacy Copilot-Credits billing has no single attribution here.
No legacy Copilot-Credits billing policy scopes this group.
Microsoft's words: “If a user is covered by multiple billing policies, this report attributes the usage to the oldest configured billing policy.” — a different rule from the spending tie-break above, for a different mechanism.
No single spending policy wins for Sales.
Why: No spending policy scopes this group.
Microsoft's rule for spending policies: the highest per-user limit first, then the largest overall policy limit, then the most recently created policy — policies do not combine and do not inherit the tenant default.
No spending allowance is recorded for this group.
Legacy Copilot-Credits billing has no single attribution here.
No legacy Copilot-Credits billing policy scopes this group.
Microsoft's words: “If a user is covered by multiple billing policies, this report attributes the usage to the oldest configured billing policy.” — a different rule from the spending tie-break above, for a different mechanism.
No single spending policy wins for Engineering.
Why: No spending policy scopes this group.
Microsoft's rule for spending policies: the highest per-user limit first, then the largest overall policy limit, then the most recently created policy — policies do not combine and do not inherit the tenant default.
No spending allowance is recorded for this group.
Legacy Copilot-Credits billing has no single attribution here.
No legacy Copilot-Credits billing policy scopes this group.
Microsoft's words: “If a user is covered by multiple billing policies, this report attributes the usage to the oldest configured billing policy.” — a different rule from the spending tie-break above, for a different mechanism.
Coverage — 21 groups have no declared Microsoft spending policy
Corporate Strategy — no Microsoft spending policy is recorded for this group. Budget lights are separate; they watch a budget and do not grant Microsoft access.
Security — no Microsoft spending policy is recorded for this group. Budget lights are separate; they watch a budget and do not grant Microsoft access.
Facilities — no Microsoft spending policy is recorded for this group. Budget lights are separate; they watch a budget and do not grant Microsoft access.
Legal — no Microsoft spending policy is recorded for this group. Budget lights are separate; they watch a budget and do not grant Microsoft access.
Procurement — no Microsoft spending policy is recorded for this group. Budget lights are separate; they watch a budget and do not grant Microsoft access.
Research — no Microsoft spending policy is recorded for this group. Budget lights are separate; they watch a budget and do not grant Microsoft access.
Human Resources — no Microsoft spending policy is recorded for this group. Budget lights are separate; they watch a budget and do not grant Microsoft access.
Data & Analytics — no Microsoft spending policy is recorded for this group. Budget lights are separate; they watch a budget and do not grant Microsoft access.
Supply Chain — no Microsoft spending policy is recorded for this group. Budget lights are separate; they watch a budget and do not grant Microsoft access.
Product — no Microsoft spending policy is recorded for this group. Budget lights are separate; they watch a budget and do not grant Microsoft access.
Quality Assurance — no Microsoft spending policy is recorded for this group. Budget lights are separate; they watch a budget and do not grant Microsoft access.
IT — no Microsoft spending policy is recorded for this group. Budget lights are separate; they watch a budget and do not grant Microsoft access.
Field Services — no Microsoft spending policy is recorded for this group. Budget lights are separate; they watch a budget and do not grant Microsoft access.
Manufacturing — no Microsoft spending policy is recorded for this group. Budget lights are separate; they watch a budget and do not grant Microsoft access.
Marketing — no Microsoft spending policy is recorded for this group. Budget lights are separate; they watch a budget and do not grant Microsoft access.
PMO — no Microsoft spending policy is recorded for this group. Budget lights are separate; they watch a budget and do not grant Microsoft access.
Finance — no Microsoft spending policy is recorded for this group. Budget lights are separate; they watch a budget and do not grant Microsoft access.
Customer Success — no Microsoft spending policy is recorded for this group. Budget lights are separate; they watch a budget and do not grant Microsoft access.
Operations — no Microsoft spending policy is recorded for this group. Budget lights are separate; they watch a budget and do not grant Microsoft access.
Sales — no Microsoft spending policy is recorded for this group. Budget lights are separate; they watch a budget and do not grant Microsoft access.
Engineering — no Microsoft spending policy is recorded for this group. Budget lights are separate; they watch a budget and do not grant Microsoft access.
This is the register your organization declared, not a live access check. Microsoft grants access through membership: a limit of one credit still grants access. Confirm access in the Microsoft 365 admin center.