Ability to Deploy Azure MCP Server as a Remote Server as an Azure Function or in an App Service

[fm0322]

The ability to deploy the Azure MCP server following patterns we have already established would be very beneficial. We already have several MCP servers running as Azure Functions and we have found it to be a great way to host remote MCP servers and Agents particularly when one instance will do.

[vukelich]

Hey @fm0322, thanks for your input. Could you please expand on your request? For example, it'd be helpful to know:

• What other MCP servers are you using that run as Azure Functions? Can you please link to them so our team can compare the implementation and deployment differences?
• What do you mean by "when one instance will do?" Are you referring to some technique of having many disjoint MCP servers sitting within a single Azure resource?
• When you say, "following patterns we have already established," could you please detail those patterns, documentation of those patterns, and examples of meeting those patterns?
• Have you seen our current example templates for deploying the Azure MCP server as a remote MCP server using Streamable HTTP? We've added support for it in our 2.0-beta. See https://github.com/microsoft/mcp/tree/main/servers/Azure.Mcp.Server/azd-templates/aca-foundry-managed-identity. If you have seen this, what are your thoughts? Does this provide a starting point for deploying to Azure that helps you?

[joshfree]

Thanks for the feedback @fm0322. @vukelich had a few more questions, but agreed that we'll support deploying to Azure Functions in the next couple of months.

[joshfree]

@anuchandy can you please link to the MSAL/Identity issue that's blocking .NET Trimming, which is also blocking our ability to deploy to Azure Functions? It will be good to track that here.

[anuchandy]

Linking the blocking MSAL/Identity issue: https://github.com/AzureAD/microsoft-identity-web/issues/3576