This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](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(259.20000000000005, 20%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EHC%3C/text%3E%3C/svg%3E)
I exposed an existing APIM API as a MCP server within Azure API Management service. I have some AI clients that can connect to it, but others fail due to providing a string value for the Id property in the request object. The MCP specs state that a string is supported, but APIM MCP schema validation returns a 400 Bad Request response when a string value(ex. "abc123") is used.
Let me know if you need additional info, but this feels like an Azure bug.
An Azure service that provides a hybrid, multi-cloud management platform for APIs.
That is not the same issue. I am using the "Expose existing API as MCP Server" feature in APIM and it does not allow the id property for the JSON-RPC requests to be set to a string value as shown below, even though it is supported in the spec for MCP.
![](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(19.2, 14.000000000000002%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESD%3C/text%3E%3C/svg%3E)
Can you please provide me the details, I have asked in the Private chat?
Details shared in Private chat.
Can you reproduce the error and provide me the timestamp of the error?
I just recreated a few times. 1:59 PM CST - 2:00 PM CST.
Thank you, I have sent it to the backend engineer.
I have received an update from backend engineer they said, Its a day 0 limitation and is a bug, they have created internal work item to fix this bug. the ETA to fix this bug is 6 months.
Thank you for reaching out to Microsoft Q&A.
I have received an update from backend engineer they said, it's a day 0 limitation and is a bug, they have created internal work item to fix this bug. The ETA to fix this bug is 6 months.
Thanking you for confirming this issue is a bug. I am quite concerned that it would take 6 months to resolve this bug. I imagine it will impact many customers, especially those using Salesforce Agentforce platform, as they use strings for Ids.
If it will take 6 months for Azure to make their features meet the official standard specifications, we will need to consider looking for other platforms to meet our needs. In the world of AI tools, 6 months is an eternity. Please escalate this to get a more appropriate prioritization.
![](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(41.6, 65%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPK%3C/text%3E%3C/svg%3E)
Thank you for sharing your concerns and feedback. We have noted your feedback regarding the timeline and the potential customer impact, and we will make sure to convey this to the engineering team and will keep you informed as soon as we receive an update from the team.
Can you confirm if this bug has been resolved yet?