Skip to content

Commit 85d2529

Browse files
update Next.js backend addition steps
1 parent c68b4ba commit 85d2529

File tree

1 file changed

+6
-12
lines changed

1 file changed

+6
-12
lines changed

includes/static-web-apps/static-web-apps-nextjs-backends.md

Lines changed: 6 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -2,26 +2,20 @@
22
author: craigshoemaker
33
ms.service: static-web-apps
44
ms.topic: include
5-
ms.date: 04/25/2024
5+
ms.date: 06/11/2024
66
ms.author: cshoe
77
---
88

9-
Next.js applications that use server-side rendering require a dedicated Azure App Service as the deployment destination for the backend of the application. Once you have this hosting plan, you can link your static web app to the App Service plan.
9+
A managed backed is automatically available for every hybrid Next.js deployment. However, you can fine tune performance and take more control of the backend by assigning a custom backend to your site. The following steps show you how to associate a custom backend to your site.
1010

1111
When you link the backend resource to your Next.js app, server-side requests are served from the backend server.
1212

13-
Use the following steps to link your App Service plan to your static web app:
14-
15-
1. Create an Azure App Service under the **S1** plan.
16-
1713
1. Go to your static web app in the Azure portal.
1814

19-
1. In the *Settings* section, select **APIs**.
15+
1. Select **Settings** and then **APIs** from the side menu.
2016

21-
1. Append the following text to the end of the URL in your browser's location:
17+
1. Select **Configure linked backend**.
2218

23-
```text
24-
exp.AzurePortal_enable-nextjs=true
25-
```
19+
1. Either create a new App Service Plan or select an existing App Service Plan.
2620

27-
Once you complete these steps, you can link your static web app to your App Service plan using this screen.
21+
Your selected App Service Plan must use at least an **S1** SKU.

0 commit comments

Comments
 (0)