Repository navigation
[Azure Backup] [All & Namespace] Several prompts were rejected because the prompt does not define the required input schema #3773
Description
Description:
Using prompts related to Azure Backup:
-
Prompt: Attach user-assigned managed identity <identity_id> to Recovery Services vault <vault_name> in resource group <resource_group> by setting identity type to UserAssigned
Rejected byazurebackup_vault_updatebecause it does not have an input schema similar toidentity-id. -
Prompt: Disable public network access on Recovery Services vault <vault_name> in resource group <resource_group>
Rejected byazurebackup_vault_updatebecause it does not have an input schema similar topublic-network-access. -
Prompt: Create Private Endpoint <pe_name> for vault <vault_name> in resource group <resource_group> in subnet <subnet_id> and link it to private DNS zone <dns_zone_id>
Rejected byazurebackup_vault_privateendpoint_createbecause it does not have an input schema similar toprivate-dns-zone.
Steps to Reproduce:
- Start mcp server in
Namespacemode orAlltools mode. - Open GitHub Copilot in VS Code.
- Enter the test prompt.
Environment:
- OS: Windows.
- Vscode Version: 1.138
- Large Language Model: GPT-5.6 Sol
- Azure MCP Server: 3.0.45
Expected Behavior:
The mcp tools can run successfully with above prompts.
Rick Winter (@RickWinter) and Vinay Gera (@g2vinay) for notification
Activity
github-actions commentedon Sep 24, 2026
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @microsoft/azure-mcp.
github-actions commentedon Sep 24, 2026
Triaged as bug because documented Azure Backup prompt flows are failing at tool invocation time: the tool rejects required inputs because those schema fields are not defined.
Added tools-AzureBackup to route it to the relevant tool area and customer-reported because this came from an external user report. Set Issue Type to Bug and Priority to Medium: the impact is clear and customer-facing, but the report does not indicate a repo-wide blocker or release-stopping incident.
Owner recommendation: left blank for now because the issue clearly maps to Azure Backup, but I do not have high-confidence ownership evidence beyond the notification mentions in the issue body.
[-][Azure Backup] [All & Namespace] Several prompts were rejected because the tool does not define the required input schema[/-][+][Azure Backup] [All & Namespace] Several prompts were rejected because the prompt does not define the required input schema[/+]alzimmermsft commentedon Sep 28, 2026
Closing as resolved by #3703