Skip to content

Commit d641cc5

Browse files
committed
PR fixes
1 parent 8416c5c commit d641cc5

File tree

1 file changed

+7
-6
lines changed

1 file changed

+7
-6
lines changed

articles/azure-mcp-server/get-started/tools/visual-studio.md

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ ms.custom: build-2025
1616
In this article, you learn how to complete the following tasks:
1717

1818
- Install and authenticate to the Azure MCP Server
19-
- Connect to Azure MCP Server using using GitHub Copilot agent mode in Visual Studio
19+
- Connect to Azure MCP Server using GitHub Copilot agent mode in Visual Studio
2020
- Run prompts to test Azure MCP Server operations and interact with Azure resources
2121

2222
## Prerequisites
@@ -33,8 +33,8 @@ Visual Studio uses a file named `mcp.json` to check for MCP Server configuration
3333
1. `%USERPROFILE%\.mcp.json`: Serves as a global MCP server configuration for a specific user. Adding an MCP server here would make it load for all Visual Studio solutions.
3434
1. `<SOLUTIONDIR>\.vs\mcp.json`: Specific to Visual Studio and only loads the specified MCP servers for a specific user, for the specified solution.
3535
1. `<SOLUTIONDIR>\.mcp.json`: Works well if you're looking for an MCP configuration that you can track in source control for a repo.
36-
1. `<SOLUTIONDIR>\.vscode\mcp.json`: Scoped to the repository/solution and typically not source controlled.
37-
1. `<SOLUTIONDIR>\.cursor\mcp.json`: Scoped to the repository/solution and typically not source controlled.
36+
1. `<SOLUTIONDIR>\.vscode\mcp.json`: Scoped to the repository/solution and typically not included in source control.
37+
1. `<SOLUTIONDIR>\.cursor\mcp.json`: Scoped to the repository/solution and typically not included in source control.
3838

3939
> [!NOTE]
4040
> Some of these locations require .mcp.json while others require mcp.json.
@@ -106,18 +106,19 @@ Complete the following steps to install Azure MCP Server for a specific director
106106
1. In order to authenticate Azure MCP Server, Copilot prompts you to sign-in to Azure using the browser.
107107

108108
> [!NOTE]
109-
> Copilot won't prompt you to sign-in to Azure if you're already authenticated via other local tooling such as the Azure CLI.
109+
> Copilot doesn't you to sign-in to Azure if you're already authenticated via other local tooling such as the Azure CLI.
110110

111111
1. Copilot requests permission to run the necessary Azure MCP Server operation for your prompt. Select **Allow this time** or use the arrow to select a more specific behavior:
112112
- **Always allow** sets the operation to always run for any GitHub Copilot Agent Mode session or any Visual Studio Code workspace.
113113
- **Allow in this session** always runs the operation in the current GitHub Copilot Agent Mode session.
114114

115-
:::image type="content" source="../../media/github-copilot-run-command.png" alt-text="A screenshot showing how to run Azure MCP Server tools in Visual Studio.":::
115+
:::image type="content" source="../../media/github-copilot-run-command.png" alt-text="A screenshot showing how to run Azure MCP Server tools in Visual Studio.":::
116+
116117
The output for the previous prompt should resemble the following text:
117118

118119
```output
119120
The following resource groups are available for your subscription:
120-
121+
121122
1. **DefaultResourceGroup-EUS** (Location: `eastus`)
122123
2. **rg-testing** (Location: `centralus`)
123124
3. **rg-azd** (Location: `eastus2`)

0 commit comments

Comments
 (0)