Skip to content

Commit 499acdc

Browse files
committed
Switch note to an include
1 parent ef38823 commit 499acdc

File tree

3 files changed

+14
-8
lines changed

3 files changed

+14
-8
lines changed

articles/azure-functions/functions-proxies.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -14,8 +14,7 @@ In some scenarios, you may need your API to support a more complex set of REST b
1414
Today, the recommended approach to build more complex and robust APIs based on your functions is to leverage the comprehensive API services provided by [Azure API Management](../api-management/api-management-key-concepts.md).
1515
API Management uses a policy-based model to let you control routing, security, and OpenAPI integration. It also supports advanced policies like rate limiting monetization. Previous versions of the Functions runtime used the legacy Functions Proxies feature.
1616

17-
> [!IMPORTANT]
18-
> Azure Functions proxies is a legacy feature of Azure Functions [runtime versions](./functions-versions.md) 1.x to 3.x. Proxies are only supported in version 4.x to allow you to successfully upgrade your function apps to the latest runtime version. To take advantage of a more complete set of API behaviors, you should switch to using [Azure API Management](../api-management/api-management-key-concepts.md) for exposing and managing your APIs at the earliest possible convenience.
17+
[!INCLUDE [functions-legacy-proxies-deprecation](../../includes/functions-legacy-proxies-deprecation.md)]
1918

2019
## <a name="migration"></a>Moving from Functions Proxies to API Management
2120

@@ -47,8 +46,7 @@ After you have your function app endpoints exposed by using API Management, the
4746

4847
The legacy [Functions Proxies feature](legacy-proxies.md) also provides a set of basic API functionality for version 3.x and older version of the Functions runtime.
4948

50-
> [!IMPORTANT]
51-
> Azure Functions proxies is a legacy feature of Azure Functions [runtime versions](./functions-versions.md) 1.x to 3.x. Proxies are only supported in version 4.x to allow you to successfully upgrade your function apps to the latest runtime version. To take advantage of a more complete set of API behaviors, you should switch to using [Azure API Management](../api-management/api-management-key-concepts.md) for exposing and managing your APIs at the earliest possible convenience.
49+
[!INCLUDE [functions-legacy-proxies-deprecation](../../includes/functions-legacy-proxies-deprecation.md)]
5250

5351
Some basic hints for how to perform equivalent tasks using API Management have been added to the [Functions Proxies article](legacy-proxies.md). We don't currently have documentation or tools to help you migrate an existing Functions Proxies implementation to API Management.
5452

articles/azure-functions/legacy-proxies.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2,14 +2,12 @@
22
title: Work with legacy Azure Functions Proxies
33
description: Overview of how to use the legacy Proxies feature in Azure Functions
44
ms.topic: conceptual
5-
ms.date: 09/08/2022
5+
ms.date: 09/14/2022
66

77
---
88
# Work with legacy proxies
99

10-
> [!IMPORTANT]
11-
> Azure Functions Proxies is a legacy feature of Azure Functions [runtime versions](./functions-versions.md) 1.x to 3.x. Proxies are only supported in version 4.x to allow you to successfully upgrade your function apps to the latest runtime version. To take advantage of a more complete set of API behaviors, you should switch to using [Azure API Management](../api-management/api-management-key-concepts.md) for exposing and managing your APIs at the earliest possible convenience.
12-
>
10+
[!INCLUDE [functions-legacy-proxies-deprecation](../../includes/functions-legacy-proxies-deprecation.md)]
1311
> To help make it easier to migrate from existing proxy implemetations, this article links to equivalent API Management content, when available.
1412
1513
This article explains how to configure and work with Azure Functions Proxies. With this feature, you can specify endpoints on your function app that are implemented by another resource. You can use these proxies to break a large API into multiple function apps (as in a microservice architecture), while still presenting a single API surface for clients.
Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
---
2+
author: ggailey777
3+
ms.service: azure-functions
4+
ms.topic: include
5+
ms.date: 09/14/2022
6+
ms.author: glenga
7+
---
8+
9+
> [!IMPORTANT]
10+
> Azure Functions proxies is a legacy feature of Azure Functions [runtime versions](../articles/azure-functions/functions-versions.md) 1.x to 3.x. Proxies are only supported in version 4.x to allow you to successfully upgrade your function apps to the latest runtime version. To take advantage of a more complete set of API behaviors, you should switch to using [Azure API Management](../articles/api-management/api-management-key-concepts.md) for exposing and managing your APIs at the earliest possible convenience.

0 commit comments

Comments
 (0)