Foundry, Read in the Fine Print

The reply came from someone writing as Microsoft, and it read less like a correction than a map. "Foundry Models" is the umbrella term for the product, the model inference platform. "Direct from Azure" covers the models Microsoft hosts and serves, so, the reply said, the relationship is with Microsoft even when the model comes from Cohere, DeepSeek, Meta, Mistral, Moonshot AI or xAI. Read closely, that is a claim about accountability as much as a naming convention: whoever hosts the model owns the relationship, whatever lab trained it.

Elsewhere a commenter drew the family tree in a few lines. Copilot Studio, they said, gives access to GPT or Claude, while Azure AI Foundry also reaches Grok and Gemini, and Copilot is "more of a wrapper/interface to access/interact with LLMs" and "not the AI itself". The first version of Copilot Studio, they added, was Power Virtual Agents reskinned, which was used to build chatbots that were not AI. It is a small act of cartography, and a telling one: the names overlap enough that people end up sorting them out for one another.

The week before, the questions were about which product to pick. One person asked whether anyone else was "stuck choosing between Azure AI Foundry, Copilot Studio, and LangChain right now". Another strung several products together, each with Copilot attached, and asked "Would you still need O365 with copilot?" Compared with the week before, this week's questions assume the choice has been made and ask how the product behaves: what a clause means, which region carries a feature, whether anyone has run it in production.

The region question shows that shift in practice. Someone building an agent for Teams was struggling to find a region that carries every Foundry feature: memory, they wrote, is not available on East US, and in East US 2 they found a different publishing interface where publishing to Teams was not working. Someone else asked whether anyone had set Foundry up in production on a landing zone, and the answer that came back was a pointer rather than an experience: a Microsoft Learn architecture series with a baseline chat reference design whose title, the reply noted, undersells it. "The architecture is more broadly applicable."

The sharpest disagreement was over Foundry Local, the local version. One person called it a missed opportunity: it could be important for secure, local AI, they wrote, could support all the latest models and could be deeply integrated into the OS. "Unfortunately, it is not." Someone else found it "incredibly easy to deploy" for a local model, free, and simple to pair with a retrieval layer trained on your own content. These are less rival verdicts than rival yardsticks. One measures Foundry Local against what Microsoft might have made of it; the other measures it against the job in front of them.

Away from the arguments, Foundry turns up as a line in other people's plans. A study video gives Microsoft Foundry its own chapter, between the Azure and Entra material and the chapters on models and agents, and one person's cost list counts Foundry credit alongside a local model on a Mac Studio and Google's tools. In those places Foundry is a given, a chapter to study and a credit to spend, which is a calmer mood than the clause-by-clause argument elsewhere.

A quieter strand ran under the questions about company data, and it kept landing on the contract. One commenter said companies usually hold a binding tenant subscription that keeps their code siloed from the public, and that Azure OpenAI works the same way: "It is literally in the contract." Another described Azure OpenAI as an isolated instance of the public models, governed by a contractual agreement with Microsoft, then named the price of the arrangement: you are "trusting Microsoft to abide by the contract". The page says what a feature requires; in these accounts the contract says what happens to your data.

A product that lives partly in its wording hands real power to whoever explains the words. When a reply written as Microsoft says what a name covers, it does more than answer a question: it sets the terms of what builders think they bought.