Skip to content

Commit f57825a

Browse files
committed
fix resource id
1 parent 022c04d commit f57825a

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/static-web-apps/publish-bicep.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -104,7 +104,7 @@ Save the values of the output variables to a text editor. You'll need these to c
104104

105105
To link a Functions app for your backend, use the Static Web Apps standard plan for your web app and complete the following steps.
106106

107-
To create the Azure Function app, follow the instructions provided in the Create the Azure Function app guide. You'll need the resourceId for the Function app, which looks like: /subscriptions/<SUBSCRIPTION-ID>/resourcegroups/<RESOURCE-GROUP-NAME>/providers/Microsoft.Web/sites/<FUNCTION-APP-NAME>.
107+
To create the Azure Function app, follow the instructions provided in the Create the Azure Function app guide. You'll need the resourceId for the Function app, which looks like: `/subscriptions/<SUBSCRIPTION-ID>/resourcegroups/<RESOURCE-GROUP-NAME>/providers/Microsoft.Web/sites/<FUNCTION-APP-NAME>`.
108108

109109
Next, create the static web app using the Bicep template provided in the previous section. This sets up the necessary resources for your static web app. Finally, link the static web app to the function app to enable seamless integration between your front-end and back-end services.
110110

0 commit comments

Comments
 (0)