[Azure File Shares][Namespace] Failed to trigger mcp tools
@JasonYeMSFT is already working on this.
Since Sep 5, 2026.
- Dominant language
- C#
- Stars
- 3.7k
- Forks
- 624
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 220
Description
**Description:**
In `Namespace` mode, testing prompts related to [Azure File Shares](https://github.com/microsoft/mcp/blob/main/servers/Azure.Mcp.Server/docs/e2eTestPrompts.md#azure-file-shares), including:
- Check if file share name is available in in subscription
- Is the file share name available in ?
- Verify availability of file share name in
Tool `fileshares_fileshare_check-name-availability` was not triggered successfully in the conversation. Also, these prompts require remediation.
**Steps to Reproduce:**
1. Start mcp server in `Namespace` mode or `All` tools mode.
2. Open GitHub Copilot in VS Code and [switch to Agent mode](https://code.visualstudio.com/docs/copilot/chat/chat-agent-mode).
3. Enter the test prompt.
**Environment:**
- OS: Windows.
- Vscode Version: 1.134
- Large Language Model: **GPT-5.6 Sol**
- Azure MCP Server: **3.0.37**
**Expected Behavior:**
The mcp tools could be triggered successfully in namespace mode.
@RickWinter and @g2vinay for notification
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.