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/static-web-apps/deploy-bicep.md
+3-29Lines changed: 3 additions & 29 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: Deploy Azure Static Web Apps using Bicep including resource creatio
4
4
services: static-web-apps
5
5
ms.custom:
6
6
author: craigshoemaker
7
-
ms.service: static-web-apps
7
+
ms.service: azure-static-web-apps
8
8
ms.topic: how-to
9
9
ms.date: 08/13/2024
10
10
ms.author: cshoe
@@ -101,11 +101,9 @@ To create a static web app with a linked backend function app, you need to use a
101
101
102
102
*[Create the Azure Function app](/azure/azure-functions/functions-create-first-function-bicep). You need the resourceId for the Function app, which looks like: `/subscriptions/<SUBSCRIPTION-ID>/resourcegroups/<RESOURCE-GROUP-NAME>/providers/Microsoft.Web/sites/<FUNCTION-APP-NAME>`.
103
103
* Create the static web app using the [bicep in the previous section](#create-a-static-web-app-resource).
104
-
* Configure the static web app. Configuration includes:
105
-
* CORS: The Azure Function app needs to know the defaultHostname of the static web app.
106
-
* Link: The static web app needs to know about the Azure Function app in order to link to it.
104
+
* Link the static web app to the function app.
107
105
108
-
Create a `config.bicep` file, which creates a static web app and [links to an existing Azure Functions app](functions-bring-your-own#link-an-existing-azure-functions-app).
106
+
Create a `config.bicep` file to link the static web app to the function app.
0 commit comments