AI Freshness Edit: Azure App Services

TimShererWithAquent · TimShererWithAquent · commit b3a36d1c4d0c · 2025-03-31T10:30:42.000-07:00
diff --git a/articles/app-service/configure-language-php.md b/articles/app-service/configure-language-php.md
@@ -3,11 +3,12 @@ title: Configure a PHP App
 description: Learn how to configure a PHP app in a prebuilt PHP container in Azure App Service. This article shows the most common configuration tasks.
 ms.devlang: php
 ms.topic: how-to
-ms.date: 08/31/2023 
+ms.date: 04/01/2025
 ms.custom: devx-track-azurecli, linux-related-content
 zone_pivot_groups: app-service-platform-windows-linux
 ms.author: msangapu
 author: msangapu-msft
+#customer intent: As an app developer who uses PHP, I want to understand how to configure my PHP web apps in Azure App Service.
 ---
 
 # Configure a PHP app for Azure App Service
@@ -18,7 +19,7 @@ author: msangapu-msft
 
 This guide shows you how to configure your PHP web apps, mobile back ends, and API apps in Azure App Service.
 
-This guide provides key concepts and instructions for PHP developers who deploy apps to App Service. If you've never used App Service, you should first follow the [Create a PHP web app in Azure App Service](quickstart-php.md) quickstart and the [Deploy a PHP, MySQL, and Redis app to Azure App Service](tutorial-php-mysql-app.md) tutorial.
+This guide provides key concepts and instructions for PHP developers who deploy apps to App Service. If you're new to App Service, you should first follow the [Create a PHP web app in Azure App Service](quickstart-php.md) quickstart and the [Deploy a PHP, MySQL, and Redis app to Azure App Service](tutorial-php-mysql-app.md) tutorial.
 
 ## Show the PHP version
 
@@ -43,7 +44,7 @@ az webapp list-runtimes --os windows | grep PHP
 
 This guide shows you how to configure your PHP web apps, mobile back ends, and API apps in Azure App Service.
 
-This guide provides key concepts and instructions for PHP developers who deploy apps to App Service. If you've never used Azure App Service, you should first follow the [Create a PHP web app in Azure App Service](quickstart-php.md) quickstart and the [Deploy a PHP, MySQL, and Redis app to Azure App Service](tutorial-php-mysql-app.md) tutorial.
+This guide provides key concepts and instructions for PHP developers who deploy apps to App Service. If you're new to App Service, you should first follow the [Create a PHP web app in Azure App Service](quickstart-php.md) quickstart and the [Deploy a PHP, MySQL, and Redis app to Azure App Service](tutorial-php-mysql-app.md) tutorial.
 
 ## Show the PHP version
 
@@ -68,7 +69,7 @@ az webapp list-runtimes --os linux | grep PHP
 
 ::: zone pivot="platform-windows"  
 
-Run the following command in [Cloud Shell](https://shell.azure.com) to set the PHP version to 8.1:
+To set the PHP version to 8.1, run the following command in [Cloud Shell](https://shell.azure.com):
 
 ```azurecli-interactive
 az webapp config set --resource-group <resource-group-name> --name <app-name> --php-version 8.1
@@ -78,7 +79,7 @@ az webapp config set --resource-group <resource-group-name> --name <app-name> --
 
 ::: zone pivot="platform-linux"
 
-Run the following command in [Cloud Shell](https://shell.azure.com) to set the PHP version to 8.1:
+To set the PHP version to 8.1, run the following command in [Cloud Shell](https://shell.azure.com):
 
 ```azurecli-interactive
 az webapp config set --resource-group <resource-group-name> --name <app-name> --linux-fx-version "PHP|8.1"
@@ -101,7 +102,7 @@ npm install kuduscript -g
 kuduscript --node --scriptType bash --suppressPrompt
 ```
 
-Your repository root now has two additional files: `.deployment` and `deploy.sh`.
+Your repository root now has two new files: `.deployment` and `deploy.sh`.
 
 Open `deploy.sh` and find the `Deployment` section, which looks like this example:
 
@@ -129,7 +130,7 @@ Commit all your changes and deploy your code by using Git or by using ZIP deploy
 
 ## Run Bower, Gulp, or Grunt
 
-If you want App Service to run popular automation tools at deployment time (such as Bower, Gulp, or Grunt), you need to supply a [custom deployment script](https://github.com/projectkudu/kudu/wiki/Custom-Deployment-Script). App Service runs this script when you deploy by using Git or by using ZIP deploy with [build automation enabled](deploy-zip.md#enable-build-automation-for-zip-deploy).
+If you want App Service to run popular automation tools at deployment time, such as Bower, Gulp, or Grunt, you need to supply a [custom deployment script](https://github.com/projectkudu/kudu/wiki/Custom-Deployment-Script). App Service runs this script when you deploy by using Git or by using ZIP deploy with [build automation enabled](deploy-zip.md#enable-build-automation-for-zip-deploy).
 
 To enable your repository to run these tools, you need to add them to the dependencies in `package.json`. For example:
 
@@ -149,7 +150,7 @@ npm install kuduscript -g
 kuduscript --node --scriptType bash --suppressPrompt
 ```
 
-Your repository root now has two additional files: `.deployment` and `deploy.sh`.
+Your repository root now has two new files: `.deployment` and `deploy.sh`.
 
 Open `deploy.sh` and find the `Deployment` section, which looks like this example:
 
@@ -212,13 +213,13 @@ fi
 
 ## Customize build automation
 
-If you deploy your app by using Git or by using ZIP packages [with build automation enabled](deploy-zip.md#enable-build-automation-for-zip-deploy), the App Service build automation steps through the following sequence:
+If you deploy your app by using Git or by using ZIP packages [with build automation enabled](deploy-zip.md#enable-build-automation-for-zip-deploy), the build automation in App Service steps through the following sequence:
 
 1. Run a custom script if `PRE_BUILD_SCRIPT_PATH` specifies it.
 1. Run `php composer.phar install`.
 1. Run a custom script if `POST_BUILD_SCRIPT_PATH` specifies it.
 
-`PRE_BUILD_COMMAND` and `POST_BUILD_COMMAND` are environment variables that are empty by default. To run pre-build commands, define `PRE_BUILD_COMMAND`. To run post-build commands, define `POST_BUILD_COMMAND`.
+`PRE_BUILD_COMMAND` and `POST_BUILD_COMMAND` are environment variables that are empty by default. To run prebuild commands, define `PRE_BUILD_COMMAND`. To run post-build commands, define `POST_BUILD_COMMAND`.
 
 The following example specifies the two variables to a series of commands, separated by commas:
 
@@ -227,13 +228,13 @@ az webapp config appsettings set --name <app-name> --resource-group <resource-gr
 az webapp config appsettings set --name <app-name> --resource-group <resource-group-name> --settings POST_BUILD_COMMAND="echo foo, scripts/postbuild.sh"
 ```
 
-For additional environment variables to customize build automation, see [Oryx configuration](https://github.com/microsoft/Oryx/blob/master/doc/configuration.md).
+For other environment variables to customize build automation, see [Oryx configuration](https://github.com/microsoft/Oryx/blob/master/doc/configuration.md).
 
 For more information on how App Service runs and builds PHP apps in Linux, see the [Oryx documentation on how PHP apps are detected and built](https://github.com/microsoft/Oryx/blob/master/doc/runtimes/php.md).
 
 ## Customize startup
 
-If you want, you can run a custom command at the container startup time. Run the following command in [Cloud Shell](https://shell.azure.com):
+You can run a custom command at the container startup time. Run the following command in [Cloud Shell](https://shell.azure.com):
 
 ```azurecli-interactive
 az webapp config set --resource-group <resource-group-name> --name <app-name> --startup-file "<custom-command>"
@@ -271,7 +272,7 @@ The web framework of your choice might use a subdirectory as the site root. For
 
 The default PHP image for App Service uses NGINX, and you change the site root by [configuring the NGINX server with the `root` directive](https://docs.nginx.com/nginx/admin-guide/web-server/serving-static-content/). [This example configuration file](https://github.com/Azure-Samples/laravel-tasks/blob/main/default) contains the following snippet that changes the `root` directive:
 
-```
+```output
 server {
     #proxy_cache cache;
     #proxy_cache_valid 200 1s;
@@ -286,9 +287,9 @@ server {
     ...
 ```
 
-The default container uses the configuration file at `/etc/nginx/sites-available/default`. Keep in mind that any edit you make to this file is erased when the app restarts. To make a change that's effective across app restarts, [add a custom startup command](#customize-startup) like this example:
+The default container uses the configuration file at `/etc/nginx/sites-available/default`. Any edit you make to this file is erased when the app restarts. To make a change that's effective across app restarts, [add a custom startup command](#customize-startup) like this example:
 
-```
+```output
 cp /home/site/wwwroot/default /etc/nginx/sites-available/default && service nginx reload
 ```
 
@@ -323,7 +324,7 @@ To customize `PHP_INI_USER`, `PHP_INI_PERDIR`, and `PHP_INI_ALL` directives, add
 
 Add configuration settings to the `.user.ini` file by using the same syntax that you would use in a `php.ini` file. For example, if you wanted to turn on the `display_errors` setting and set the `upload_max_filesize` setting to `10M`, your `.user.ini` file would contain this text:
 
-```
+```ini
  ; Example Settings
  display_errors=On
  upload_max_filesize=10M
@@ -342,15 +343,15 @@ As an alternative to using a `.user.ini` file, you can use [`ini_set()`](https:/
 
 To customize `PHP_INI_USER`, `PHP_INI_PERDIR`, and `PHP_INI_ALL` directives for Linux web apps, such as `upload_max_filesize` and `expose_php`, use a custom .ini file. You can create it in an [SSH session](configure-linux-open-ssh-session.md). First, set up the directory:
 
-1. Go to your Kudu site: `https://<sitename>.scm.azurewebsites.net`.
-2. On the top menu, select **Bash** or **SSH**.
-3. In Bash or SSH, go to your `/home/site/wwwroot` directory.
-4. Create a directory called `ini` (for example, `mkdir ini`).
-5. Change the current working directory to the `ini` folder that you just created.
+1. Go to your Kudu site, by default: `https://<app-name>-<random-hash>.scm.<region>.azurewebsites.net/`. To get the random hash and region values, in your app **Overview**, copy **Default domain**.
+1. On the top menu, select **Debug console**, then **Bash** or **SSH**.
+1. In Bash or SSH, go to your `/home/site/wwwroot` directory.
+1. Create a directory called `ini` (for example, `mkdir ini`).
+1. Change the current working directory to the `ini` folder that you created.
 
-Now, create an .ini file where you'll add your settings. This example uses `extensions.ini`. There are no file editors such as Vi, Vim, or Nano, so use Echo to add the settings to the file. Change the `upload_max_filesize` value from `2M` to `50M`. Use the following command to add the setting and create an `extensions.ini` file if one doesn't already exist:
+Next, create an .ini file where you add your settings. This example uses `extensions.ini`. There are no file editors such as Vi, Vim, or Nano, so use Echo to add the settings to the file. Change the `upload_max_filesize` value from `2M` to `50M`. Use the following command to add the setting and create an `extensions.ini` file if one doesn't already exist:
 
-```
+```bash
 /home/site/wwwroot/ini>echo "upload_max_filesize=50M" >> extensions.ini
 /home/site/wwwroot/ini>cat extensions.ini
 
@@ -362,9 +363,10 @@ upload_max_filesize=50M
 In the Azure portal, add an application setting to scan the `ini` directory that you just created to apply the change for `upload_max_filesize`:
   
 1. Go to the [Azure portal](https://portal.azure.com) and select your App Service Linux PHP application.
-2. Under **Application settings**, select **+ Add new setting**.
-3. For the app setting name, enter `PHP_INI_SCAN_DIR`. For the value, enter `:/home/site/wwwroot/ini`.
-4. Select **Save**.
+1. Go to **Settings** > **Environment variables**.
+1. Select **Add**.
+1. For **Name** enter *PHP_INI_SCAN_DIR* and for **Value**, enter `:/home/site/wwwroot/ini`.
+1. Select **Apply**, then **Apply** again. Confirm your changes.
 
 > [!NOTE]
 > If you recompiled a PHP extension, such as GD, follow the steps at [Recompiling PHP extensions](/archive/blogs/azureossds/azure-app-service-linux-adding-php-extensions#recompiling-php-extensions--).
@@ -383,9 +385,9 @@ First, run the following command in [Cloud Shell](https://shell.azure.com) to ad
 az webapp config appsettings set --name <app-name> --resource-group <resource-group-name> --settings PHP_INI_SCAN_DIR="d:\home\site\ini"
 ```
 
-Go to the Kudu console (`https://<app-name>.scm.azurewebsites.net/DebugConsole`), and then go to `d:\home\site`.
+Go to the Kudu console (`https://<app-name>-<random-hash>.scm.<region>.azurewebsites.net/DebugConsole`), and then go to `d:\home\site`.
 
-Create a directory in `d:\home\site` called `ini`. Then, create an .ini file in the `d:\home\site\ini` directory (for example, `settings.ini`) with the directives that you want to customize. Use the same syntax that you would use in a `php.ini` file.
+Create a directory in `d:\home\site` called `ini`. Then, create an .ini file in the `d:\home\site\ini` directory, for example, `settings.ini`, with the directives that you want to customize. Use the same syntax that you would use in a `php.ini` file.
 
 For example, to change the value of [`expose_php`](https://php.net/manual/ini.core.php#ini.expose-php), run the following commands:
 
@@ -409,11 +411,11 @@ First, run the following command in [Cloud Shell](https://shell.azure.com) to ad
 az webapp config appsettings set --name <app-name> --resource-group <resource-group-name> --settings PHP_INI_SCAN_DIR="/usr/local/etc/php/conf.d:/home/site/ini"
 ```
 
-The value `/usr/local/etc/php/conf.d` is the default directory where `php.ini` exists. The value `/home/site/ini` is the custom directory in which you'll add a custom .ini file. You separate the values with a colon (`:`).
+The value `/usr/local/etc/php/conf.d` is the default directory where `php.ini` exists. The value `/home/site/ini` is the custom directory in which you add a custom .ini file. You separate the values with a colon (`:`).
 
-Go to the web SSH session with your Linux container (`https://<app-name>.scm.azurewebsites.net/webssh/host`).
+Go to the web SSH session with your Linux container (`https://<app-name>-<random-hash>.scm.<region>.azurewebsites.net/webssh/host`).
 
-Create a directory in `/home/site` called `ini`. Then, create an .ini file in the `/home/site/ini` directory (for example, `settings.ini`) with the directives that you want to customize. Use the same syntax that you would use in a `php.ini` file.
+Create a directory in `/home/site` called `ini`. Then, create an .ini file in the `/home/site/ini` directory, for example, `settings.ini`, with the directives that you want to customize. Use the same syntax that you would use in a `php.ini` file.
 
 > [!TIP]
 > The built-in Linux containers in App Service use `/home` as persisted shared storage.
@@ -434,20 +436,20 @@ For the changes to take effect, restart the app.
 
 ::: zone pivot="platform-windows"  
 
-The built-in PHP installations contain the most commonly used extensions. You can enable additional extensions in the same way that you [customize php.ini directives](#customize-php_ini_system-directives).
+The built-in PHP installations contain the most commonly used extensions. You can enable more extensions in the same way that you [customize php.ini directives](#customize-php_ini_system-directives).
 
 > [!NOTE]
 > The best way to see the PHP version and the current `php.ini` configuration is to call [`phpinfo()`](https://php.net/manual/function.phpinfo.php) in your app.
 
-To enable additional extensions, use the following steps:
+To enable other extensions, use the following steps:
 
-1. Add a `bin` directory to the root directory of your app, and put the `.dll` extension files in it (for example, `mongodb.dll`). Make sure that the extensions are compatible with the PHP version in Azure, and that they're VC9 and non-thread-safe (NTS) compatible.
+1. Add a `bin` directory to the root directory of your app, and put the `.dll` extension files in it, for example, `mongodb.dll`. Make sure that the extensions are compatible with the PHP version in Azure, and that they're VC9 and non-thread-safe (NTS) compatible.
 
 1. Deploy your changes.
 
 1. Follow the steps in [Customize PHP_INI_SYSTEM directives](#customize-php_ini_system-directives), and add the extensions into the custom .ini file with the [extension](https://www.php.net/manual/ini.core.php#ini.extension) or [zend_extension](https://www.php.net/manual/ini.core.php#ini.zend-extension) directive:
 
-   ```
+   ```ini
    extension=d:\home\site\wwwroot\bin\mongodb.dll
    zend_extension=d:\home\site\wwwroot\bin\xdebug.dll
    ```
@@ -458,12 +460,12 @@ For the changes to take effect, restart the app.
 
 ::: zone pivot="platform-linux"
 
-The built-in PHP installations contain the most commonly used extensions. You can enable additional extensions in the same way that you [customize php.ini directives](#customize-php_ini_system-directives).
+The built-in PHP installations contain the most commonly used extensions. You can enable more extensions in the same way that you [customize php.ini directives](#customize-php_ini_system-directives).
 
 > [!NOTE]
 > The best way to see the PHP version and the current `php.ini` configuration is to call [`phpinfo()`](https://php.net/manual/function.phpinfo.php) in your app.
 
-To enable additional extensions, use the following steps:
+To enable other extensions, use the following steps:
 
 1. Add a `bin` directory to the root directory of your app, and put the `.so` extension files in it (for example, `mongodb.so`). Make sure that the extensions are compatible with the PHP version in Azure, and that they're VC9 and non-thread-safe (NTS) compatible.
 
