Treat the Model as Configuration
Which model reasons about a given task is a setting we choose — never a separate platform you have to stand up.
Microsoft Foundry's model catalog is built around exactly this idea — that the model is a swappable component, not a platform decision made once and lived with forever. The catalog lists more than 10,000 models, with roughly 50 new ones published every month, spanning Microsoft's own models, Azure OpenAI's lineup, and models from partners including Anthropic, Meta, Mistral, Cohere, DeepSeek, and Hugging Face. Anthropic's Claude family — with text and image input, text output, multilingual support, and vision — sits in that catalog alongside Azure's own OpenAI models, deployed and billed through the same Azure identity and compliance boundary rather than a separate account with a separate vendor. With Foundry's newer "instant access" option, some catalog models can even be called by name and used immediately, with no deployment step at all.
The other half of treating the model as configuration is how it reaches your systems. The Model Context Protocol (MCP) is an open standard for connecting a model to external tools and data — instead of writing a one-off integration for every tool a model might need, an MCP-compatible client (Foundry Agent Service among them) can connect to any MCP server and use whatever tools it exposes. Some MCP servers — Microsoft's own Azure DevOps MCP Server among them — can be added directly from Foundry's tool catalog, using the same approval and auditing controls as everything else running inside the platform.
How EWO 360° treats the model as configuration
Claude runs inside Microsoft Foundry under the same identity, billing, and compliance boundary as Azure's own OpenAI models, and reaches a client's systems through MCP rather than a bespoke integration per tool. That means the model doing the reasoning for a given engagement — Claude, an Azure OpenAI model, or something else in the catalog — is a choice we make in configuration, evaluated against the task, and changeable later without touching the rest of what we built.
Want to talk through your systems with us directly?
No account managers, no hand-offs — you'll be talking to the person who's actually going to architect the work.