Upcoming update: Pricelist schema enhancement to support mid‑month republishing

On this page5 sections

1. What is changing
2. What the LastUpdatedDate attribute provides
3. Why this change
4. What partners need to do
5. Learn more

• Date: April 10, 2026
• Effective date: May 1, 2026
• Workspace: Pricing

To improve pricing data clarity and support critical updates, we are enhancing the License-based Current Month Pricelist schema and Software Current Month Pricelist schema to enable mid‑month republishes when required. As part of this update, a new attribute called LastUpdatedDate will be introduced.

What is changing

• The Pricelist schema will support mid‑month republishing in specific scenarios where corrections are required within the same month.
• A new attribute, LastUpdatedDate, will be added at the row level.
• LastUpdatedDate indicates the date and time a pricelist row was added during the current month, helping partners identify when the data was introduced to keep track of the versioning.
• In scope: Current month License-based pricelist and Current month Software pricelist.
• Out of scope: License-based Preview pricelist, License-based End of sale pricelist, License-based EST pricelist, Azure plan consumption pricelist, Azure plan reservations pricelist, Marketplace pricelist.

What the LastUpdatedDate attribute provides

The LastUpdatedDate attribute is designed to help partners more easily manage and interpret pricing changes introduced through mid‑month republishes:

• History is maintained throughout the entire month: Rows introduced earlier in the month remain available, while new or updated rows can be identified.
• Allows partners to easily identify the latest changes: Partners can isolate pricing deltas introduced due to a mid‑month republish without comparing full files.
• Adds additional context to pricing data: The attribute provides clarity on when pricing data was introduced, improving traceability and auditability.

Why this change

Today, certain updates cannot be effectively addressed without waiting for the next monthly publish. This enhancement:

• Improves flexibility to address critical corrections through schema‑driven updates versioning.
• Improves overall pricing accuracy and partner confidence.

Monthly pricelist publishing remains the default behavior. Mid‑month republishes will be used only when critical corrections are required.

What partners need to do

• Partners who want to use the new LastUpdatedDate attribute will need to update their processing logic to ingest and consume this field.
• No immediate action is required if partners choose not to use the attribute; existing workflows will continue to function as they do today.

Learn more

• For new commerce pricelist schema: New commerce price list