Microsoft (MSFT ) is pushing its newly generally available Fireworks AI integration at the startup segment, publishing a deployment blueprint on August 4, 2026 that pairs a reference architecture for running open models on Microsoft Foundry with a billing perk: members of the Microsoft for Startups program can apply their Azure credits to Fireworks model deployments, and the program advertises up to $150,000 in credits.
The Fireworks integration itself has reached general availability, putting open-weight models from DeepSeek, Moonshot AI, Z.ai, MiniMax, Qwen, Google, and OpenAI’s open-weight gpt-oss line inside Azure’s model catalog with Azure-side governance and billing. Fireworks AI, the inference provider serving the models behind the catalog, handles inference; Foundry supplies the control plane. The blueprint is Microsoft’s bid to make that combination the default starting stack for AI-native companies building on Azure.
What the Fireworks blueprint has startups build
The reference architecture runs entirely inside a startup’s own Azure subscription. A containerized application on Azure Container Apps calls a Fireworks model endpoint deployed through Foundry, with Azure Container Registry holding images and Azure Key Vault storing credentials. From there, the blueprint scales in stages: route traffic through Azure API Management for rate limits, add Azure Cache for Redis to cut redundant inference calls, and track latency, error rate, and token consumption in Azure Monitor.
The docs’ own framing is that inference is one of the largest controllable costs for an AI-native company, and the architecture is designed so a team starts with a single serverless model endpoint and adds components only when measured traffic demands them. Model discovery, governance, and billing stay in one control plane, so a startup never stands up or manages GPU clusters of its own.
26 models in the catalog, and the billing comes with carve-outs
The Foundry catalog now lists 26 Fireworks-served models, including Moonshot AI’s Kimi K2.5, DeepSeek V3.2, MiniMax M2.5, OpenAI’s gpt-oss-120b, and a DeepSeek V4 Pro described as a 1.6-trillion-parameter flagship. Six of them, including Kimi K2.6 and Z.ai’s GLM-5.1, are available on pay-per-token serverless billing; the rest run on provisioned throughput units, Azure’s reserved-capacity pricing. Teams can also import custom or fine-tuned weights through a bring-your-own-weights workflow, with LoRA adapter support in public preview.
The startup credit terms carry a real limit: credits apply only to pay-per-token Data Zone Standard usage, and provisioned throughput units are excluded. The compliance boundaries are narrower still. Serverless deployments are confined to six US Azure regions, and the service sits outside Microsoft’s EU Data Boundary commitments, carries no FedRAMP authorization, and cannot touch payment-card data. Microsoft’s own transparency note adds that it does not evaluate the safety or behavior of Fireworks-served models and leaves that assessment to the customer.
One near-term dated item: pay-per-token billing for GLM-5.1 and MiniMax M2.5 is deprecated effective August 7, 2026, though both models remain available on provisioned throughput, and pay-per-token offerings for four other catalog models are already deprecated.
Microsoft has been stocking Foundry’s catalog for months
The Fireworks blueprint is one move in a longer catalog build-out. Microsoft widened its Mistral arrangement in July 2026 to court regulated buyers, as Unite.AI reported, and it has been shifting some of its own Office AI workloads across model providers to manage costs, per earlier coverage. The Fireworks integration extends that multi-vendor posture to open models, with the inference layer outsourced to a specialist rather than built in-house.
For startups weighing their options, the comparison Microsoft itself publishes is telling: the docs pit Fireworks on Foundry against self-hosted vLLM on a GPU fleet, against frontier closed-source APIs, and against generic cloud AI services, and position it for companies whose AI is the core product differentiator. The general-availability milestone, the credit eligibility, and the deprecation notices now appearing in the catalog docs all say the same thing: this is a production offering with terms attached, and Microsoft wants the next wave of AI-native companies reading them before their architecture hardens.
