Using MACC to fund an AI deployment you already need

Many organisations with a Microsoft Azure Consumption Commitment (MACC) reach the final year of the agreement with committed spend still to use. At the same time, AI projects sit in the queue waiting for budget. For some of them, the two problems can solve each other.

How it works

According to Microsoft's guidance, purchases of Marketplace offers marked "Azure benefit eligible" count toward a MACC at 100% of the pre-tax amount. The purchase has to be made through the Azure portal, against a subscription tied to your organisation's agreement. Card purchases made directly on the Marketplace website do not count, and nor do purchases paid from Azure prepayment.

The condition that matters

Microsoft's guidance also says the benefit applies only to licences used exclusively in Azure. A licence bought through the Marketplace and deployed on premises or in a hybrid estate does not count. For K-Lake, that means the MACC route fits organisations that will run it inside their own Azure tenant, close to data already held in Azure Blob, SharePoint or OneDrive.

Your perimeter can be your Azure tenant, and the zero egress position holds there just as it does on your own hardware.

Why it suits procurement

Buying through the Marketplace puts K-Lake on the Azure bill you already pay. There is no new supplier to onboard and no separate contract to negotiate for the public plans, which are priced on indexed capacity rather than per seat. Larger estates are handled as a private offer.

What to check before you rely on it

Confirm the offer shows the Azure benefit eligible badge at checkout. Check whether your agreement predates the benefit, since Microsoft notes exclusions for some older agreements. Ask your Microsoft account team how much commitment remains and when the term ends. We are happy to join that conversation.