Merge pull request #312343 from MicrosoftDocs/main

Auto Publish – main to live - 2026-02-26 06:00 UTC

Author: learn-build-service-prod[bot]

articles/app-service/configure-error-pages.md

@@ -1,62 +1,70 @@
 ---
 title: Configure error pages on App Service
-description: Learn how to configure a custom error page on App Service
+description: Learn how to configure the custom error pages available on Azure App Service.
 author: jefmarti
 ms.topic: how-to
 ms.custom: linux-related-content
-ms.date: 10/14/2024
+ms.date: 02/19/2026
 ms.author: jefmarti
 ms.service: azure-app-service
+#customer intent: As a website owner and designer, I want to configure custom error pages for my App Service apps so that I can present customized error pages to my website users if they encounter errors.
+
 ---
 
 # Configure error pages on App Service
 
-This article explains how to configure custom error pages on your web app. With App Service you can configure an error page for specific errors that will be presented to users instead of the default error page. 
+Azure App Service lets you configure specific error pages to present to your web app users instead of the default error pages. This article explains how to configure these custom error pages for your web app.
 
-### Prerequisite
-In this tutorial, we're adding a custom 403 error page to our web app hosted on App Service and test it with an IP restriction. To do so, you need the following:
-- a web app hosted on App Service w/ a Premium SKU
-- an html file under 10 kb in size
+The three types of error code pages available for customization in App Service are *403 Access restrictions*, *502 Gateway errors*, and *503 Service unavailable*. This article walks through adding a custom 403 error page to a web app hosted on App Service, and testing it by using an IP restriction.
 
-## Upload an error page
-For this example, we're uploading and testing a 403 error page to present to the user. Name your html file to match the error code (for example, `403.html`). Once you have your html file prepared, you can upload it to your web app. In the configuration blade, you should see an **Error pages** tab. Click on this tab to view the error page options. If the options are greyed out, you need to upgrade to at least a Premium SKU to use this feature.
+## Prerequisites
 
-Select the error code that you'd like to upload an error page for and click **Edit**. On the next screen, click the folder icon to select your html file. The file must be in html format and within the 10 kb size limit. Find your .html file and click on the **Upload** button at the bottom of the screen. Notice the Status in the table updates from Not Configured to Configured. Then click **Save** to complete the upload. 
+- A web app hosted on an Azure App Service Premium SKU. You must have a Premium SKU to customize error pages.
+- An HTML file smaller than 10 kb that presents a 403 error message such as **Forbidden**. Name the HTML file to match the error code, in this case *403.html*.
 
-## Confirm error page
-Once the custom error page is uploaded and saved, we can trigger and view the page. In this example, we can trigger the 403 error by using an IP restriction however you can also trigger a 403 error page by stopping the site.
+## Configure the custom error page
 
-To set an IP restriction, go to the **Networking** blade and click the **Enabled with access restrictions** link under **Inbound traffic configuration**.
+Upload your custom error page and apply it to your web app.
 
-Under the **Site access and rules** section, select the **+Add** button to create an IP restriction.
+1. On the Azure portal page for your web app, select **Settings** > **Configuration (preview)** from the left navigation menu.
+1. Select the **Error pages** tab on the **Configuration** page.
+1. On the **Error pages** page, select the **Browse** button next to the error code you want to configure, in this case **403**.
+1. Browse to your custom *403.html* error page and select **Open**. The file uploads, and the filename appears in the field next to the error code.
+1. Select the checkbox next to **Apply to all requests**, and then select **Apply**.
 
-In the form that follows, you need to change the Action to **Deny** and fill out the **Priority** and **IP Address Block**. In this example, we use the **Inbound address** found on the Networking blade and we're setting it to /0 (for example, `12.123.12.123/0`). This disables all public access when visiting the site.
+>[!NOTE]
+>If the configuration options are greyed out, you need to upgrade to at least a Premium SKU to use this feature.
 
-Once the Add rule form is filled out, select the **Add rule** button. Then click **Save**.
+>[!NOTE]
+>If you're using the legacy, nonpreview **Configuration** > **Error codes** page, select **Edit** next to the error code you want to configure. On the **Add custom error page (.html)** pane, select the folder icon to browse to and select your custom *403.html* file. After the file loads, select **Upload**.
 
-Once saved, you need to restart the site for the changes to take effect. Go to your overview page and select **browse**. You should now see your custom error page load.
+## Confirm the error page
 
-## Error codes
-App Service currently supports three types of error codes that are available to customize:
+Once you upload and apply the custom error page, you can trigger and view the page. For this example, trigger the 403 error by using an IP restriction. You can also trigger a 403 error page by stopping the site.
 
-| Error code  | description |
-| ------------- | ------------- |
-| 403  | Access restrictions |
-| 502  | Gateway errors  |
-| 503  | Service unavailable  |
+1. On the Azure portal page for your web app, select **Settings** > **Networking** from the left navigation menu.
+1. Under **Inbound traffic configuration** on the **Networking** page, copy the IP address next to **IP Addresses** to use in a later step.
+1. Next to **Public access restrictions**, select the link for **Enabled with no access restrictions**.
+1. On the **Access Restrictions** page, under **Site access**, select **Enabled from select virtual networks and IP addresses**.
+1. At the bottom of the page under **Site access and rules**, select **Add** to add an IP restriction.
+1. On the **Add rule** pane, give the rule a **Name** like *Test403*, set **Action** to **Deny**, and set **Priority** to *300*.
+1. Paste the IP address you copied from the main **Networking** page into the **IP Address Block** field, followed by */0*, for example *203.0.113.254/0*.
+1. Select **Add rule**.
+1. On the **Access Restrictions** page, select **Save**. If necessary, confirm the action and select **Continue**. This action disables all public access to the site.
 
-## FAQ
-1. I've uploaded my error page, why doesn't it show when the error is triggered?
+Restart the site for the changes to take effect. Return to the **Overview** page for your site and select **Restart** from the top menu. When you select the URL to go to your site, you see your custom error page.
 
-Custom error pages are triggered from front end failures. If the error is coming from the app level, it won't trigger or show the configured error page. If you want the error page to show for all requests, check the **Apply to all requests** box under the configured error code. This will show the error page for all requests matching the status code regardless of where it failed. Note, when this box is checked it will override any existing error pages that are configured for the app.
+## FAQ
 
-2. Why is the error page feature greyed out?
+### Why doesn't my uploaded error page show when the error is triggered?
 
-Error pages are currently a Premium feature. You need to use at least a Premium SKU to enable the feature. 
+Make sure you select **Apply to all requests** when you configure the error page. By default, custom error pages are triggered only from front-end failures. Errors from the app level don't trigger or show the custom error page. Selecting **Apply to all requests** for the configured error code shows the error page for all requests that match the status code, regardless of where they failed. Selecting this option overrides any existing error pages configured for the app.
 
-3. How can I reference a single error page across multiple apps?
+### Why is the error page feature grayed out?
 
-If you need to use the same error page across multiple apps, you can link to your error page hosted in a storage account in your uploaded html file. Upload your error page to a [storage account](/azure/storage/common/storage-account-overview) and add the provided storage URL for your page in an `<iframe>` tag located in the html file uploaded to the app. 
+You must use at least a Premium SKU to enable the error code feature.
 
+### How can I use a custom error page across multiple apps?
 
+You can host your custom HTML error page in an [Azure Storage account](/azure/storage/common/storage-account-overview), and add the page's storage URL in an `<iframe>` tag in the HTML file you upload to the app.
 

articles/app-service/configure-grpc.md

@@ -1,88 +1,81 @@
 ---
 title: Configure gRPC on App Service
-description: Learn how to configure a gRPC application with Azure App Service on Linux.
+description: Learn how to configure a Google Remote Procedure Call (gRPC) application with Azure App Service on Linux.
 author: jefmarti
 ms.topic: how-to
 ms.custom: linux-related-content
-ms.date: 11/10/2023
+ms.date: 02/12/2026
 ms.author: jefmarti
 ms.service: azure-app-service
+#customer intent: As an Azure App Service developer, I want to learn how to configure gRPC for my Linux apps so I can streamline messages between my clients and server over HTTP/2.
+
 ---
 
 # Configure gRPC on App Service
 
-This article explains how to configure your web app for gRPC.
-
-gRPC is a Remote Procedure Call framework that can streamline messages between your client and server over HTTP/2. Using the gRPC protocol over HTTP/2 enables the use of features like:
+This article explains how to configure your web app for gRPC, a remote procedure call framework that can streamline messages between your client and server over HTTP/2. Using the gRPC protocol over HTTP/2 lets you use features like:
 
 - Multiplexing to send multiple parallel requests over the same connection.
 - Bidirectional streaming to send requests and responses simultaneously.
 
-Support for gRPC is currently available on Azure App Service for Linux. To use gRPC on your web app, you need to configure your app by selecting the HTTP version, proxy, and port.
+Support for gRPC is available on Azure App Service for Linux. To use gRPC on your web app, you configure your app by selecting the HTTP version, proxy, and port.
 
-For gRPC client and server samples for each supported language, see the [documentation on GitHub](https://github.com/Azure/app-service-linux-docs/tree/master/HowTo/gRPC).
+For gRPC client and server samples for each supported language, see [gRPC on App Service](https://github.com/Azure/app-service-linux-docs/tree/master/HowTo/gRPC) on GitHub.
 
 ## Prerequisite
 
-Create your [web app](getting-started.md) as you normally would. Choose your preferred runtime stack, and choose Linux as your operating system.
+- A Linux [web app](getting-started.md) in Azure App Service that uses your preferred runtime stack.
+
+## Configure gRPC
 
 After you create your web app, configure the following details to enable gRPC before you deploy your application.
 
 > [!NOTE]
-> If you're deploying a .NET gRPC app to App Service by using Visual Studio, skip to [step 3](#3-configure-the-http2-port). Visual Studio sets the HTTP version and the HTTP 2.0 proxy configuration for you.
-
-## 1. Configure the HTTP version
+> If you're deploying a .NET gRPC app to App Service by using Visual Studio, skip to [Configure the HTTP/2 port](#configure-the-http2-port), because Visual Studio sets the HTTP version and HTTP 2.0 proxy configuration for you.
 
-The first setting that you need to configure is the HTTP version:
+### Configure the HTTP version and HTTP 2.0 proxy
 
-1. On the left pane of your web app, under **Settings**, go to **Configuration**.
-2. On the **General Settings** tab, scroll down to **Platform settings**.
-3. In the **HTTP version** dropdown list, select **2.0**.
-4. Select **Save**.
+Use the Azure portal page for your web app to configure your app's HTTP version and proxy.
 
-This setting restarts your application and configures the front end to allow clients to make HTTP/2 calls.
+1. On the left navigation menu of your web app page, select **Settings** > **Configuration**.
+1. On the **General settings** tab of the **Stack settings** page, configure the following settings:
+   - For **HTTP version**, select **2.0**.
+   - For **HTTP 2.0 Proxy**, select **gRPC only**.
+1. Select **Apply**.
 
-## 2. Configure the HTTP 2.0 proxy
+The **HTTP version** setting restarts your application and configures the front end to allow clients to make HTTP/2 calls. The **HTTP 2.0 Proxy** setting configures your site to receive HTTP/2 requests.
 
-Next, you need to configure the HTTP 2.0 proxy:
+### Configure the HTTP/2 port
 
-1. In the same **Platform settings** section, find the **HTTP 2.0 Proxy** setting and select **gRPC Only**.
-2. Select **Save**.
+App Service requires an application setting that specifically listens for HTTP/2 traffic in addition to HTTP/1.1 traffic. Use **App settings** to define the HTTP/2 port.
 
-This setting configures your site to receive HTTP/2 requests.
+1. On the left navigation menu of your web app page, select **Settings** > **Environmental variables**.
+1. On the **App settings** tab of the **Environmental variables** page, select **Add**.
+1. On the **Add/Edit application setting** screen, add the following app setting:
+   - For **Name**, enter *HTTP20_ONLY_PORT*.
+   - For **Value**, enter *8585*.
+1. Select **Apply**, and confirm that your application might restart if necessary.
 
-## 3. Configure the HTTP/2 port
+This setting configures the port on your application that listens for HTTP/2 requests.
 
-App Service requires an application setting that specifically listens for HTTP/2 traffic in addition to HTTP/1.1 traffic. You define the HTTP/2 port in the app settings:
+Now that you configured the HTTP version, port, and proxy, you can successfully make HTTP/2 calls to your web app by using gRPC.
 
-1. On the left pane of your web app, under **Settings**, go to **Environment variables**.
-2. On the **App settings** tab, add the following app settings to your application:
-   - **Name** = **HTTP20_ONLY_PORT**
-   - **Value** = **8585**
+### Provide a startup command
 
-These settings configure the port on your application that's specified to listen for HTTP/2 requests.
+For Python applications, you must provide a custom startup command. For other languages, a startup command is optional.
 
-Now that you've configured the HTTP version, port, and proxy, you can successfully make HTTP/2 calls to your web app by using gRPC.
+1. On the left navigation menu of your web app page, select **Settings** > **Configuration**.
+1. On the **Stack settings** page, select the **Stack settings** tab.
+1. Under **Startup command**, enter `python app.py`.
+1. Select **Apply**.
 
-### (Optional) Python startup command
+## Requirements and limitations
 
-For Python applications only, you also need to set a custom startup command:
+The following requirements and limitations apply to gRPC usage with App Service.
 
-1. On the left pane of your web app, under **Settings**, go to **Configuration**.
-2. Under **General Settings**, add the following value for **Startup Command**: `python app.py`.
-
-## Common topics
-
-The following table can answer your questions about using gRPC with App Service.
-
-> [!NOTE]
-> gRPC is not a supported feature in App Service Environment v2. Use App Service Environment v3.
-
-| Topic | Answer |
-| --- | --- |
-| OS support | gRPC is available on Linux. Windows support is currently in preview. |
-| Language support | gRPC is supported for each language that supports gRPC.  |
-| Client certificates | HTTP/2 enabled on App Service doesn't currently support client certificates. Client certificates need to be ignored when you're using gRPC. |
-| Secure calls | gRPC must make secure HTTP calls to App Service. You can't make nonsecure calls. |
-| Activity timeout | gRPC requests on App Service have a timeout request limit. gRPC requests time out after 20 minutes of inactivity. |
-| Custom containers | HTTP/2 and gRPC support is in addition to App Service HTTP/1.1 support. Custom containers that support HTTP/2 must also support HTTP/1.1.   |
+- **App Service Environment version**. App Service Environment v2 doesn't support gRPC. Use App Service Environment v3.
+- **OS support**. gRPC is available on Linux. Windows support is currently in preview.
+- **Client certificates**. HTTP/2 on App Service doesn't support client certificates. Client certificates must be ignored when you use gRPC.
+- **Secure calls**. gRPC must make secure HTTP calls to App Service. You can't make nonsecure calls.
+- **Activity timeout**. App Service gRPC requests have a timeout request limit. gRPC requests time out after 20 minutes of inactivity.
+- **Custom containers**. HTTP/2 and gRPC support is in addition to App Service HTTP/1.1 support. Custom containers that support HTTP/2 must also support HTTP/1.1.