Growth margin API seat-expansion multiplier changes to decimal on November 23
Growth margin API integrations must accept decimal values for seatIncreaseMultiplier from November 23, 2026. Microsoft is changing the field’s data type from integer to decimal to support more precise seat-expansion configurations.
The change affects Get growth margins, Get growth margin by ID and the Growth margin eligibility API’s SeatExpansionGrowthMarginConstraintsNotMet error response. Partners consuming the field should check parsing logic before the effective date.
Microsoft explicitly states that no other fields or behaviors change as part of this update.
Update parsers to accept decimal seatIncreaseMultiplier values in Get growth margins, Get growth margin by ID and the SeatExpansionGrowthMarginConstraintsNotMet error response. No other fields or behaviors change.
Partner briefing
- What it is
A data-type update to growth margin APIs.
- What’s changing
seatIncreaseMultiplier changes from integer to decimal effective November23,2026.
- Why it matters
Whole-number-only parsing must be updated to accept decimal responses.
- Who it affects
Partners integrating growth margin and eligibility APIs.