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-cache-for-redis/cache-whats-new.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,6 +15,10 @@ appliesto:
15
15
16
16
Find out what's new in Azure Redis.
17
17
18
+
## April 2026
19
+
20
+
### Tooling to migrate Azure Cache for Redis instance to Azure Managed Redis (preview)
21
+
Tooling to aid migration from Azure Cache for Redis (Basic, Standard, and Premium) is now available in Public Preview. When migration is initiated using the tooling, your Azure Cache for Redis endpoint is updated to point to your precreated Azure Managed Redis. For more information, see [Migration using tooling](/azure/redis/migrate/migrate-basic-standard-premium-with-tooling).
Copy file name to clipboardExpand all lines: articles/azure-functions/scenario-custom-remote-mcp-server.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Build a custom remote MCP server using Azure Functions
3
3
description: "Learn how to create and deploy a custom Model Context Protocol (MCP) server using Azure Functions. This quickstart uses the Azure Developer CLI to deploy an MCP server project that enables AI clients to access custom tools hosted on Azures Flex Consumption plan."
4
-
ms.date: 12/01/2025
4
+
ms.date: 04/06/2026
5
5
ms.update-cycle: 180-days
6
6
ms.topic: quickstart
7
7
ai-usage: ai-assisted
@@ -85,7 +85,7 @@ Use the `azd init` command to create a local Azure Functions code project from a
This command pulls the project files from the [template repository](https://github.com/Azure-Samples/remote-mcp-functions-dotnet) and initializes the project in the current folder. The `-e` flag sets a name for the current environment. In `azd`, the environment maintains a unique deployment context for your app, and you can define more than one. It's also used in the name of the resource group you create in Azure.
88
+
This command pulls the project files from the [template repository](https://github.com/Azure-Samples/remote-mcp-functions-dotnet) and initializes the project in the current folder. The `-e` flag sets a name for the current environment. In `azd`, the environment maintains a unique deployment context for your app, and you can define more than one. It's also part of the name of the resource group you create in Azure.
89
89
::: zone-end
90
90
::: zone pivot="programming-language-java"
91
91
2. In your local terminal or command prompt, run this `azd init` command:
@@ -94,7 +94,7 @@ Use the `azd init` command to create a local Azure Functions code project from a
This command pulls the project files from the [template repository](https://github.com/Azure-Samples/remote-mcp-functions-java) and initializes the project in the current folder. The `-e` flag sets a name for the current environment. In `azd`, the environment maintains a unique deployment context for your app, and you can define more than one. It's also used in names of the resources you create in Azure.
97
+
This command pulls the project files from the [template repository](https://github.com/Azure-Samples/remote-mcp-functions-java) and initializes the project in the current folder. The `-e` flag sets a name for the current environment. In `azd`, the environment maintains a unique deployment context for your app, and you can define more than one. It's also part of the names of the resources you create in Azure.
98
98
::: zone-end
99
99
::: zone pivot="programming-language-typescript"
100
100
2. In your local terminal or command prompt, run this `azd init` command:
@@ -103,7 +103,7 @@ Use the `azd init` command to create a local Azure Functions code project from a
This command pulls the project files from the [template repository](https://github.com/Azure-Samples/remote-mcp-functions-typescript) and initializes the project in the current folder. The `-e` flag sets a name for the current environment. In `azd`, the environment maintains a unique deployment context for your app, and you can define more than one. It's also used in names of the resources you create in Azure.
106
+
This command pulls the project files from the [template repository](https://github.com/Azure-Samples/remote-mcp-functions-typescript) and initializes the project in the current folder. The `-e` flag sets a name for the current environment. In `azd`, the environment maintains a unique deployment context for your app, and you can define more than one. It's also part of the names of the resources you create in Azure.
107
107
::: zone-end
108
108
::: zone pivot="programming-language-python"
109
109
2. In your local terminal or command prompt, run this `azd init` command:
@@ -112,7 +112,7 @@ Use the `azd init` command to create a local Azure Functions code project from a
This command pulls the project files from the [template repository](https://github.com/Azure-Samples/remote-mcp-functions-python) and initializes the project in the current folder. The `-e` flag sets a name for the current environment. In `azd`, the environment maintains a unique deployment context for your app, and you can define more than one. It's also used in names of the resources you create in Azure.
115
+
This command pulls the project files from the [template repository](https://github.com/Azure-Samples/remote-mcp-functions-python) and initializes the project in the current folder. The `-e` flag sets a name for the current environment. In `azd`, the environment maintains a unique deployment context for your app, and you can define more than one. It's also part of the names of the resources you create in Azure.
116
116
::: zone-end
117
117
::: zone pivot="programming-language-csharp,programming-language-java,programming-language-python,programming-language-typescript"
118
118
## Start the storage emulator
@@ -198,9 +198,9 @@ You can view the complete project template in the [Azure Functions Java MCP Serv
198
198
::: zone pivot="programming-language-python"
199
199
The function code for the MCP server tools is defined in the `src/function_app.py` file. The MCP function annotations expose these functions as MCP Server tools:
You can view the complete project template in the [Azure Functions Python MCP Server](https://github.com/Azure-Samples/remote-mcp-functions-python) GitHub repository.
Copy file name to clipboardExpand all lines: articles/azure-functions/scenario-mcp-apps.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Build an MCP Apps server using Azure Functions
3
3
description: "Learn how to create and deploy an MCP App that returns interactive UI using Azure Functions. This quickstart uses the Azure Developer CLI to deploy an MCP App project that enables AI clients to access tools with rich interactive interfaces hosted on Azure's Flex Consumption plan."
4
-
ms.date: 02/25/2026
4
+
ms.date: 04/06/2026
5
5
ms.update-cycle: 180-days
6
6
ms.topic: quickstart
7
7
ai-usage: ai-assisted
@@ -248,17 +248,17 @@ The `GetWeatherWidget` function serves the bundled HTML file at that URI using `
248
248
You can view the complete project template in the [Azure Functions .NET MCP Server](https://github.com/Azure-Samples/remote-mcp-functions-dotnet) GitHub repository.
249
249
::: zone-end
250
250
::: zone pivot="programming-language-python"
251
-
The function code for the MCP Apps weather tool is defined in the `src/function_app.py` file. In this function, the `metadata` parameter on `@app.mcp_tool()` adds UI metadata to the `get_weather` tool.
251
+
The function code for the MCP Apps weather tool is defined in the `src/McpWeatherApp/function_app.py` file. In this function, the `metadata` parameter on `@app.mcp_tool()` adds UI metadata to the `get_weather` tool.
The `TOOL_METADATA` constant declares a `ui.resourceUri` that tells the MCP host to fetch the interactive UI from `ui://weather/index.html` after the tool runs.
| Dublin Metro | Equinix DB3 <br>Digital Realty DUB02 | 1 | North Europe |✓| Colt<sup>1</sup><br>Equinix<br>Megaport<sup>1</sup> |
53
-
| Frankfurt Metro | Digital Realty FRA11<br>Equinix FR7 | 1 | Germany West Central |✓| Colt<sup>1</sup><br>DE-CIX<br>Equinix<sup>1</sup><br>Megaport<sup>1</sup>|
53
+
| Frankfurt Metro | Digital Realty FRA11<br>Equinix FR7 | 1 | Germany West Central |✓| Colt<sup>1</sup><br>DE-CIX<br>Equinix<sup>1</sup><br>Megaport |
54
54
| Jakarta Metro | NeutraDC HDC<br>NTT GDC | 2 | Indonesia Central |✓| DCI Indonesia<br>Telin<sup>1</sup><br>XL Axiata<sup>1</sup> |
55
55
| Madrid Metro | Equinix MD2<br>Digital Realty MAD1 | 1 | Spain Central |✓| Colt<br>Equinix<br>Megaport<br>Telefonica<sup>1</sup> |
56
56
| Milan Metro | Irideos Milan<br>Data4Italy Milan | 1 | Italy North |✓| Colt<br>Equinix<br>Megaport<br>Telecom Italia Sparkle<sup>1</sup><br>Telia Carrier (Arelion)<sup>1</sup> |
57
57
| Mumbai Metro | TATA LVSB<br>Nxtra Data| 2 | West India |✓||
58
58
| New York Metro | Equinix NY5<br>165 Halsey Street | 1 |✗|✓| Megaport<br>DE-CIX|
59
59
| Oslo Metro | DigiPlex Ulven <br>Bulk Data IX | 2 | Norway East |✓| Colt<sup>1</sup><br>GlobalConnect<sup>1</sup><br>Telenor<sup>1</sup> |
60
-
| Silicon Valley Metro | Equinix SV10<br>CoreSite SV7 | 1 | West US |✓| Megaport<sup>1</sup><br>Zayo<sup>1</sup> |
60
+
| Silicon Valley Metro | Equinix SV10<br>CoreSite SV7 | 1 | West US |✓| Megaport<br>Zayo<sup>1</sup> |
61
61
| Singapore Metro | Global Switch Tai Seng<br>Equinix SG1 | 2 | Southeast Asia |✓| Colt<br>Equinix<br>IX Reach<br>Megaport<br>MegaPOP (Singtel)<br>Singtel International |
62
62
| Stockholm Metro | Equinix SK1<br>Digital Realty STO6 | 1 | Sweden Central |✓| Megaport<sup>1</sup><br>Telia Carrier (Arelion) |
63
63
| Taipei Metro | Chief Telecom<br>Chunghwa Telecom Co. Ltd | 2 | Taiwan North |✓| Chunghwa Telecom<sup>1</sup> |
64
64
| Toronto Metro | Cologix TOR1<br>Allied King West | 1 | Canda Central |✓| Megaport<sup>1</sup><br>Zayo<sup>1</sup> |
65
-
| Vienna Metro | Digital Realty VIE1<br>NTT GDC | 1 | Austria East |✓| A1 Telekom Austria<sup>1</sup><br>Colt<br>Next Layer GMBH |
65
+
| Vienna Metro | Digital Realty VIE1<br>NTT GDC | 1 | Austria East |✓| A1 Telekom Austria<br>Colt<br>Next Layer GMBH |
66
66
| Zurich Metro | Digital Realty ZUR2<br>Equinix ZH5 | 1 | Switzerland North |✓| BICS<sup>1</sup><br>Colt<br>Digital Realty<br>Swisscom |
67
67
| Washington DC Metro | Equinix DC6<br>CoreSite VA3 | 1 | East US<br/>East US 2 |✓| Equinix<br>Megaport<br>Zayo<sup>1</sup> |
68
68
69
-
<sup>1<sup> These service providers will be available in the future.
69
+
<sup>1<sup> These service providers will be available in the future. While they are listed under the peering location, circuit creation is expected to fail until the providers become active.
70
70
71
71
> [!NOTE]
72
72
> The naming convention for Metro sites will utilize `City` and `City2` to denote the two unique peering locations within the same metropolitan region. As an illustration, Amsterdam and Amsterdam2 are indicative of the two separate peering locations within the metropolitan area of Amsterdam. In the Azure portal, these locations will be referred to as `Amsterdam Metro`.
![learn-build-service-prod[bot]](https://avatars.githubusercontent.com/in/237442?v=4&size=40){kind=avatar}
0 commit comments