![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(310.4, 43%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDJ%3C/text%3E%3C/svg%3E)
Microsoft Copilot | Microsoft 365 Copilot | Development
Building and customizing solutions using Microsoft 365 Copilot APIs and tools
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(291.2, 38%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMP%3C/text%3E%3C/svg%3E)
AFAIK, the Server URL itself cannot be dynamically templated within Copilot Studio's base MCP connection. The MCP onboarding wizard uses a static host/base URL for the orchestrator to route traffic. You should be able though to pass dynamic parameters at the tool level via Prompt Templates or by defining URI-addressable dynamic content for Resources. If you need dynamic routing, consider wrapping your MCP server in an API Gateway or Reverse Proxy that handles path resolution based on the user's context.
Regarding your second question, my understanding is that Copilot Studio requires static Client IDs and Secrets for manual OAuth 2.0 connection configurations. The credentials are tied directly to an identity provider's app registration. Dynamic Client Registration is not natively supported for manual MCP tool setups.
To avoid hardcoding or exposing these secrets in manifests, use Azure Key Vault to store and rotate your MCP server credentials.
If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.
hth
Marcin