You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-mcp-server/includes/tools/global-parameters-list.md
+22-12Lines changed: 22 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: Learn how to use the Azure MCP Server with Azure Key Vault keys.
4
4
keywords: azure mcp server, azmcp, key vault
5
5
author: diberry
6
6
ms.author: diberry
7
-
ms.date: 05/14/2025
7
+
ms.date: 07/23/2025
8
8
content_well_notification:
9
9
- AI-contribution
10
10
ai-usage: ai-assisted
@@ -13,19 +13,29 @@ ms.custom: build-2025
13
13
---
14
14
## Tool parameters
15
15
16
-
The Azure MCP Server tools define parameters for data they need to complete tasks. For example, these parameters may include the subscription ID, an account name, or a resource group.
16
+
The Azure MCP Server tools define parameters for the data they need to complete tasks. For example, these parameters might include the subscription ID, an account name, or a resource group.
17
17
18
-
The data used for these parameters may be included in the prompt you use to call a tool, or it may be established in the previous conversation context. If the data is available from the conversation context, the Azure MCP Server can use that information without requiring you to repeat it in every prompt. This context creates a more natural conversational experience while still ensuring all necessary data is available for the tools.
18
+
You might include the data for these parameters in the prompt you use to call a tool, or the previous conversation context might establish the data. If the conversation context provides the data, the Azure MCP Server can use that information without requiring you to repeat it in every prompt. This context creates a more natural conversational experience while still ensuring all necessary data is available for the tools.
19
19
20
-
The parameters specific to each tool are documented in the tools reference articles. All of the tools also share the following global parameters.
20
+
The tools reference articles document the parameters specific to each tool. All of the tools also share the following global parameters.
21
21
22
22
| Parameter | Description |
23
23
|-----------------|-------------------|
24
-
| **Subscription** | Azure subscription ID for target resources. Required. |
25
-
| **Tenant Id** | Azure tenant ID for authentication. |
| **Subscription** | [Azure subscription](/azure/cloud-adoption-framework/ready/azure-best-practices/initial-subscriptions) ID or name for target resources. This parameter identifies the Azure subscription that contains the resources you want to manage. You can use either the subscription GUID or the display name. Required for most operations. |
25
+
| **Tenant Id** | [Azure tenant](/azure/cloud-adoption-framework/ready/landing-zone/design-area/azure-ad-define) ID for authentication. This parameter specifies the Microsoft Entra ID tenant to authenticate against. Can be either the GUID identifier or the display name of your Entra ID tenant. Optional - uses default tenant if not specified. |
26
+
| **Authentication method** | [Authentication method](/entra/identity/authentication/concept-authentication-methods) to use for Azure operations. Options include `credential` (Azure CLI/managed identity), `key` (access key), or `connectionString`. Default is `credential`, which uses Azure CLI authentication or managed identity. |
27
+
| **Maximum retries** | Maximum number of retry attempts for failed operations before giving up. Controls how many times the system attempts to retry a failed request. Default is 3 retries. |
28
+
| **Retry delay** | Initial delay in seconds between retry attempts. For exponential backoff, this value is used as the base delay that gets multiplied on each retry. Default is 2 seconds. |
29
+
| **Retry delay maximum** | Maximum delay in seconds between retries, regardless of the retry strategy. This parameter caps the delay time to prevent excessively long waits. Default is 10 seconds. |
30
+
| **Retry mode** | Retry strategy to use when operations fail. `fixed` uses consistent delays between retries, while `exponential` increases the delay between each attempt. Default is `exponential` for better handling of temporary issues. |
31
+
| **Retry network timeout** | Network operation timeout in seconds. When operations take longer than this timeout, they are canceled and might be retried if retries are enabled. Default is 100 seconds. |
32
+
33
+
Example prompts include:
34
+
35
+
- **Set subscription**: "Use subscription 'my-subscription-id' for all operations"
36
+
- **Use tenant ID**: "Authenticate using tenant ID 'my-tenant-id'"
37
+
- **Set authentication method**: "Use 'credential' authentication for this session"
38
+
- **Configure retries**: "Set maximum retries to 5 with a 3-second delay
39
+
- **Set retry mode**: "Use 'fixed' retry mode with a maximum delay of 5 seconds"
40
+
- **Set network timeout**: "Set network timeout to 120 seconds for all operations"
41
+
- **Configure retry parameters**: "Use exponential retry mode with a maximum of 4 retries and a delay of 2 seconds"
![learn-build-service-prod[bot]](https://avatars.githubusercontent.com/in/237442?v=4&size=40){kind=avatar}
0 commit comments