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/application-gateway/private-link.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,6 +33,9 @@ You may also choose to block inbound public (Internet) access to Application Gat
33
33
34
34
All features supported by Application Gateway are supported when accessed through a private endpoint, including support for AGIC.
35
35
36
+
> [!NOTE]
37
+
> If your client application connects to App Gateway via a private IP, requires an idle timeout greater > than 4 minutes, and the client application does not send TCP keep-alive packets, contact > [email protected] to request initiation of keep‑alive from Application Gateway.
38
+
36
39
## Private Link components
37
40
38
41
Four components are required to implement Private Link with Application Gateway:
+ When you use the SSE transport, the MCP extension relies on Azure Queue storage provided by the [default host storage account](./storage-considerations.md) (`AzureWebJobsStorage`). When using identity-based connections, make sure that your function app has at least the equivalent of these role-based permissions in the host storage account: [Storage Queue Data Reader](/azure/role-based-access-control/built-in-roles#storage-queue-data-reader) and [Storage Queue Data Message Processor](/azure/role-based-access-control/built-in-roles#storage-queue-data-message-processor).
30
+
+ When you use the SSE transport, the MCP extension relies on Azure Queue storage provided by the [default host storage account](./storage-considerations.md) (`AzureWebJobsStorage`). When using identity-based connections, make sure that your function app has at least the equivalent of these role-based permissions in the host storage account: [Storage Queue Data Contributor](/azure/role-based-access-control/built-in-roles/storage#storage-queue-data-contributor) and [Storage Queue Data Message Processor](/azure/role-based-access-control/built-in-roles/storage#storage-queue-data-message-processor).
31
31
+ When running locally, the MCP extension requires version 4.0.7030 of the [Azure Functions Core Tools](functions-run-local.md), or a later version.
32
32
::: zone pivot="programming-language-csharp"
33
33
+ Requires version 2.1.0 or later of the `Microsoft.Azure.Functions.Worker` package.
Replace `<TENANT_ID>` with your actual tenant ID value.
150
+
Replace `<TENANT_ID>` with your actual tenant ID value. Save these values for later.
151
+
152
+
1. Select **Manage** > **Certificates & secrets**. Create a new client secret if there's not already one and copy its value for use later.
151
153
152
154
1. Select **Manage** > **Expose an API** and copy the existing scope.
153
155
@@ -282,13 +284,11 @@ When you use OAuth identity passthrough, the agent prompts the user to sign in a
282
284
|**Remote MCP Server endpoint**| The URL endpoint for your MCP server. |`https://contoso-mcp-tools.azurewebsites.net/runtime/webhooks/mcp`|
283
285
|**Authentication**| The authentication method to use. |`OAuth Identity Passthrough`|
284
286
|**Client ID**| The client ID of your function app Entra registration |`00001111-aaaa-2222-bbbb-3333cccc4444`|
287
+
|**Client secret**| The client secret of your function app Entra registration |`abcEFGhijkLMNopqRST`|
285
288
|**Token URL**| The endpoint your server app calls to exchange an authorization code or credential for an access token. |`https://login.microsoftonline.com/aaaabbbb-0000-cccc-1111-dddd2222eeee/oauth2/v2.0/token`|
286
289
|**Auth URL**| The endpoint where users are redirected to authenticate and grant authorization to your server app. |`https://login.microsoftonline.com/aaaabbbb-0000-cccc-1111-dddd2222eeee/oauth2/v2.0/authorize`|
287
290
|**Refresh URL**| The endpoint used to obtain a new access token when the current one expires. |`https://login.microsoftonline.com/aaaabbbb-0000-cccc-1111-dddd2222eeee/oauth2/v2.0/token`|
288
-
|**Scopes**| The specific permissions or resource access levels your server app requests from the authorization server |`api://00001111-aaaa-2222-bbbb-3333cccc4444`|
289
-
290
-
>[!NOTE]
291
-
>A **Client secret** value isn't needed, so leave this field blank.
291
+
|**Scopes**| The specific permissions or resource access levels your server app requests from the authorization server |`api://00001111-aaaa-2222-bbbb-3333cccc4444/user_impersonation`|
292
292
293
293
1. Select **Connect** to create a connection to your MCP server endpoint.
294
294
@@ -358,4 +358,4 @@ These additional articles can help you build your agent and function app capabil
358
358
359
359
-[Register your MCP server in the organizational tool catalog](./register-mcp-server-api-center.md)
Copy file name to clipboardExpand all lines: articles/azure-functions/scenario-blob-storage-events.md
+1-21Lines changed: 1 addition & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -331,27 +331,7 @@ Use the `azd up` command to create the function app in a Flex Consumption plan a
331
331
332
332
The Event Grid blob trigger processes files within seconds of upload. This speed demonstrates the near real-time capabilities of this approach compared to traditional polling-based blob triggers.
333
333
334
-
## Redeploy your code
335
-
336
-
Run the `azd up` command as many times as you need to both provision your Azure resources and deploy code updates to your function app.
337
-
338
-
>[!NOTE]
339
-
>Deployed code files are always overwritten by the latest deployment package.
340
-
341
-
Your initial responses to `azd` prompts and any environment variables generated by `azd` are stored locally in your named environment. Use the `azd env get-values` command to review all of the variables in your environment that were used when creating Azure resources.
342
-
343
-
## Clean up resources
344
-
345
-
When you're done working with your function app and related resources, use this command to delete the function app and its related resources from Azure. This action helps you avoid incurring any further costs:
346
-
347
-
```console
348
-
azd down --no-prompt
349
-
```
350
-
351
-
>[!NOTE]
352
-
>The `--no-prompt` option instructs `azd` to delete your resource group without a confirmation from you.
353
-
>
354
-
>This command doesn't affect your local code project.
0 commit comments