Skip to content

Commit 33f4a7a

Browse files
committed
ghi 96274 fix
1 parent f020dfb commit 33f4a7a

File tree

1 file changed

+9
-8
lines changed

1 file changed

+9
-8
lines changed

articles/static-web-apps/functions-bring-your-own.md

Lines changed: 9 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,18 @@
11
---
22
title: Bring your own functions to Azure Static Web Apps
33
description: Use an existing Azure Functions app with your Azure Static Web Apps site.
4+
ms.custom: engagement-fy23
45
services: static-web-apps
56
author: craigshoemaker
67
ms.service: static-web-apps
78
ms.topic: how-to
8-
ms.date: 07/27/2022
9+
ms.date: 10/13/2022
910
ms.author: cshoe
1011
---
1112

1213
# Bring your own functions to Azure Static Web Apps
1314

14-
Azure Static Web Apps APIs are supported by two possible configurations: managed functions and bring your own functions. See the [overview](apis-functions.md) for details between the two configurations.
15+
Azure Static Web Apps APIs are supported by two possible configurations: managed functions and bring your own functions. For more information on the differences in configurations, see the [overview](apis-functions.md).
1516

1617
This article demonstrates how to link an existing Azure Functions app to an Azure Static Web Apps resource.
1718

@@ -32,19 +33,19 @@ Once linked, you can access that same endpoint through the `api` path from your
3233
https://red-sea-123.azurestaticapps.net/api/getProducts
3334
```
3435

35-
Both endpoint URLs point to the same function.
36+
Both endpoint URLs point to the same function.
3637

3738
## Link an existing Azure Functions app
3839

3940
Before you associate an existing Functions app, you first need to adjust to configuration of your static web app.
4041

4142
1. Set `api_location` value to an empty string (`""`) in the [workflow configuration](./build-configuration.md) file.
4243

43-
1. Open your Static Web Apps instance in the [Azure portal](https://portal.azure.com).
44+
2. Open your Static Web Apps instance in the [Azure portal](https://portal.azure.com).
4445

45-
1. From the _Settings_ menu, select **APIs**.
46+
3. From the _Settings_ menu, select **APIs**.
4647

47-
1. From the _Production_ row, select **Link** to open the *Link new Backend* window.
48+
4. From the _Production_ row, select **Link** to open the *Link new Backend* window.
4849

4950
Enter the following settings.
5051

@@ -54,12 +55,12 @@ Before you associate an existing Functions app, you first need to adjust to conf
5455
| Subscription | Select your Azure subscription name. |
5556
| Resource name | Select the Azure Functions app name. |
5657

57-
1. Select the **Link** button.
58+
5. Select the **Link** button.
5859

5960
The Azure Functions app is now mapped to the `/api` route of your static web app.
6061

6162
> [!IMPORTANT]
62-
> Make sure to set the `api_location` value to an empty string (`""`) in the [workflow configuration](./build-configuration.md) file before you link an existing Functions application.
63+
> Make sure to set the `api_location` value to an empty string (`""`) in the [workflow configuration](./build-configuration.md) file before you link an existing Functions application. Also, calls assume that the external function app retains the default "api" route prefix. Many apps remove this prefix in the host.json, so make sure the prefix is in place, otherwise the call fails.
6364
6465
## Deployment
6566

0 commit comments

Comments
 (0)