A futuristic cloud computing infographic shows a robot, secure code containers, connected databases, and analytics.
Microsoft has added two things to hosted MCP servers in Azure Connector Namespace. A hosted MCP server in Connector Namespace normally runs a prebuilt server image on dedicated compute that the platform provisions. The new preview adds two options: bring your own container image, and a prebuilt Azure Cosmos DB MCP server. According to the Azure Integration Services Blog post by Lily Ma, dated November 17, 2026, both are in public preview in select Azure regions. In short, Azure will now host an MCP server you built yourself, and it ships a ready-made one for Cosmos DB for NoSQL.

A futuristic cloud computing infographic shows a robot, secure code containers, connected databases, and analytics. What hosted MCP means​

Model Context Protocol (MCP) is the standard that lets AI agents discover and call external tools and data. Running an MCP server remotely means more than deploying code. Microsoft's post says developers must also provision compute, configure authentication, manage scaling and monitor the server.

Connector Namespace takes over that work. Microsoft lists four areas the namespace handles:

  • Infrastructure and scaling: it provisions and manages the compute.
  • Authentication and access control: endpoints are secured with Microsoft Entra ID authentication and access policies.
  • Monitoring: Application Insights integration for server activity and troubleshooting.
  • Server lifecycle: deployed servers are managed as resources in the namespace.

Microsoft's own comparison of hosted versus self-hosted MCP says the self-hosted route leaves you to configure OAuth, managed identity or on-behalf-of authentication end to end, and to run your own logging and alerting.

Bring-your-own container image​

Until now, the hosted catalog was a curated set of servers during the preview. The blog says hosted servers were limited to the prebuilt options in the catalog. BYO image support lifts that restriction. You can deploy your own MCP server implementation through the same managed hosting experience.

Microsoft names three use cases:

  • Reusing an MCP server you have already built and packaged as a container image.
  • Exposing proprietary APIs, internal systems or business-specific tools to AI agents.
  • Avoiding the work of managing hosting infrastructure while you keep developing the server itself.

How the deployment works​

The announced flow is short:

  1. In the Connector Namespace portal, open the MCP catalog.
  2. Select Bring your own MCP server.
  3. Provide a few configuration details.
  4. Click Create.

Connector Namespace then deploys and hosts the server. A deployed custom server gets the same authentication, access control, scaling and monitoring as catalog servers. You keep control of the code, tools and dependencies. The platform manages the hosting layer.

The post does not list the configuration fields. It also doesn't cover image registry requirements, supported protocols or resource limits. Check the portal experience and current documentation before planning around any of those. Some existing Learn pages still describe hosted servers as prebuilt images from a curated catalog. That wording predates this announcement, so read it as older context rather than the current state of the feature.

Azure Cosmos DB MCP server​

The second addition is a prebuilt catalog server for Azure Cosmos DB for NoSQL. Microsoft says agents can use its MCP tools to:

  • Discover the databases and containers available in the account.
  • Inspect the structure of documents to understand the available data.
  • Retrieve documents and query data in Cosmos DB for NoSQL.

To deploy it, open the MCP server catalog in the Connector Namespace portal. Find Cosmos DB MCP Server under the Hosted category, supply your database's endpoint and create the server.

The announcement describes discovery, retrieval and querying only. It doesn't mention write operations, tool names, query-language details or other Cosmos DB APIs, so don't assume any of them.

Authentication and security​

Hosted MCP servers have two authentication boundaries. Inbound authentication secures the connection between MCP clients and the hosted server. Outbound authentication secures the connection between the hosted server and the downstream service it uses.

For outbound access, Microsoft's developer guide describes a managed identity assigned to the namespace. It can be created automatically with the namespace or be a standalone resource you assign. The guide also covers access policies, which you reach by opening the server under the MCP Connectors tab and selecting Access Policies.

The announcement doesn't say which outbound method the Cosmos DB server uses. Before you point an agent at production data, confirm the identity and the permissions it needs. Give it the narrowest Cosmos DB access that works. An agent that can query documents can also read whatever those documents contain.

Preview caveats​

  • Not for production: Azure's "In preview" label means availability for non-production use and testing. Microsoft Learn also says hosted MCP is a preview capability, so expect possible breaking changes.
  • Billing: The Learn overview says hosted MCP servers are still in preview with no billing enabled, and Microsoft will give notice before billing begins. That is a general Connector Namespace statement. The announcement gives no pricing, performance figures or general-availability date for these two features.
  • Regions: Availability is "select Azure regions". Check your target region before you design around it.
  • Tooling: At last report, the CLI extension on GitHub is marked Early Access. Its README says hosted-MCP-server discovery is portal-only, so expect to use the portal. I couldn't confirm whether that still holds for these new features.

Analysis​

This is a sensible step, and it was probably unavoidable. A curated catalog is a good on-ramp, but most teams with real agent projects have their own MCP servers. Those servers wrap internal APIs and line-of-business systems that no Microsoft catalog will ever include. BYO image lets them use Azure's hosting, Entra-based auth and Application Insights telemetry without running the plumbing themselves.

There is a trade-off. With a bring-your-own image, the platform manages the runtime, but you own the server's code, tools and dependencies. A badly written tool is still your problem, and so are its vulnerabilities. Managed hosting doesn't make a custom server safe.

The Cosmos DB server suits teams already holding document data in Azure. The sensible way to start is a test account with non-sensitive data, a tightly scoped identity, and a look at what the agent actually queries through Application Insights.

Bottom line​

  • Hosted MCP in Connector Namespace now accepts your own container images, in public preview.
  • A prebuilt Cosmos DB for NoSQL MCP server is available in the catalog for discovery, structure inspection and querying.
  • Both are preview features in select regions, and Microsoft doesn't recommend preview features for production workloads.
  • Several details are still unspecified: image requirements, Cosmos DB tool names and write capability, and the outbound auth method for the Cosmos DB server. Verify them in the portal before committing.
 

References

  1. (In preview) Public Preview: Bring-your-own image and Cosmos DB MCP server in Azure Connector Namespace hosted MCP Azure Updates 2026-11-17T20:00:32Z
  2. Bring-your-own image and Azure Cosmos DB MCP server in Connector Namespace hosted MCP (preview) | Microsoft Community Hub techcommunity.microsoft.com
  3. Hosted MCP Servers in Connector Namespace learn.microsoft.com