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/app-service/configure-language-php.md
+12-8Lines changed: 12 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -348,31 +348,33 @@ As an alternative to using a `.user.ini` file, you can use [`ini_set()`](https:/
348
348
349
349
::: zone pivot="platform-linux"
350
350
351
+
This section applies to directives with a change mode of `PHP_INI_USER`, `PHP_INI_PERDIR`, or `PHP_INI_ALL`. For directives that require change mode `PHP_INI_SYSTEM`, see [Customize PHP_INI_SYSTEM directives](#customize-php_ini_system-directives).
352
+
351
353
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:
352
354
353
355
1. Go to your Kudu site. To get the random hash and region values, in your app **Overview**, copy **Default domain**.
354
356
1. On the top menu, select **Debug console**, then **Bash** or **SSH**.
355
-
1. In Bash or SSH, go to your `/home/site/wwwroot` directory.
357
+
1. In Bash or SSH, go to your `/home/site` directory.
356
358
1. Create a directory called `ini` (for example, `mkdir ini`).
357
359
1. Change the current working directory to the `ini` folder that you created.
358
360
359
361
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:
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`:
371
373
372
374
1. Go to the [Azure portal](https://portal.azure.com) and select your App Service Linux PHP application.
373
375
1. Go to **Settings** > **Environment variables**.
374
376
1. Select **+ Add**.
375
-
1. For **Name** enter *PHP_INI_SCAN_DIR* and for **Value**, enter `:/home/site/wwwroot/ini`.
377
+
1. For **Name** enter *PHP_INI_SCAN_DIR* and for **Value**, enter `:/home/site/ini`.
376
378
1. Select **Apply**, then **Apply** again. Confirm your changes.
377
379
378
380
> Make sure to include the colon (:) when appending custom paths to PHP_INI_SCAN_DIR. Omitting it will result in NGINX returning a 404 error.
@@ -403,7 +405,7 @@ For example, to change the value of [`expose_php`](https://php.net/manual/ini.co
403
405
```bash
404
406
cd /home/site
405
407
mkdir ini
406
-
echo"expose_php = Off">> ini/setting.ini
408
+
echo"expose_php = Off">> ini/settings.ini
407
409
```
408
410
409
411
For the changes to take effect, restart the app.
@@ -412,7 +414,9 @@ For the changes to take effect, restart the app.
412
414
413
415
::: zone pivot="platform-linux"
414
416
415
-
To customize `PHP_INI_SYSTEM` directives, you can't use the *.htaccess* approach. App Service provides a separate mechanism that uses the `PHP_INI_SCAN_DIR` app setting.
417
+
This section applies to directives with a change mode of `PHP_INI_SYSTEM`. If your changes don't take effect after following the previous section, verify the directive's [change mode](https://www.php.net/manual/ini.list.php) before proceeding.
418
+
419
+
To customize `PHP_INI_SYSTEM` directives, use the `PHP_INI_SCAN_DIR` app setting.
416
420
417
421
First, run the following command to add an app setting called `PHP_INI_SCAN_DIR`:
418
422
@@ -434,7 +438,7 @@ For example, to change the value of [`expose_php`](https://php.net/manual/ini.co
Copy file name to clipboardExpand all lines: articles/app-service/overview-authentication-authorization.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Authentication and Authorization
3
3
description: Learn about the built-in authentication and authorization support in Azure App Service and Azure Functions, and how it can help secure your app.
Copy file name to clipboardExpand all lines: articles/application-gateway/quick-create-cli.md
+17-2Lines changed: 17 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ services: application-gateway
6
6
author: mbender-ms
7
7
ms.service: azure-application-gateway
8
8
ms.topic: quickstart
9
-
ms.date: 05/30/2024
9
+
ms.date: 02/25/2026
10
10
ms.author: mbender
11
11
ms.custom:
12
12
- mvc
@@ -76,6 +76,19 @@ az network public-ip create \
76
76
--sku Standard
77
77
```
78
78
79
+
## Create a network security group
80
+
81
+
Create a network security group with [az network nsg create](/cli/azure/network/nsg#az-network-nsg-create). The default rules in the network security group block all inbound access from the internet.
82
+
83
+
```azurecli-interactive
84
+
az network nsg create \
85
+
--resource-group myResourceGroupAG \
86
+
--name myNSG
87
+
```
88
+
89
+
> [!NOTE]
90
+
> The default rules of the network security group block all inbound access from the internet, including SSH. To connect to the virtual machine, use Azure Bastion. For more information, see [Quickstart: Deploy Azure Bastion with default settings](../bastion/quickstart-host-portal.md).
91
+
79
92
## Create the backend servers
80
93
81
94
A backend can have NICs, virtual machine scale sets, public IP addresses, internal IP addresses, fully qualified domain names (FQDN), and multitenant backends like Azure App Service. In this example, you create two virtual machines to use as backend servers for the application gateway. You also install NGINX on the virtual machines to test the application gateway.
Copy file name to clipboardExpand all lines: articles/application-gateway/quick-create-portal.md
+5-2Lines changed: 5 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ description: In this quickstart, you learn how to use the Azure portal to create
5
5
services: application-gateway
6
6
author: mbender-ms
7
7
ms.author: mbender
8
-
ms.date: 09/04/2024
8
+
ms.date: 02/25/2026
9
9
ms.topic: quickstart
10
10
ms.service: azure-application-gateway
11
11
ms.custom:
@@ -182,11 +182,14 @@ To create a backend subnet:
182
182
-**Public inbound ports**: None.
183
183
4. Accept the other defaults and then select **Next: Disks**.
184
184
5. Accept the **Disks** tab defaults and then select **Next: Networking**.
185
-
6. On the **Networking** tab, verify that **myVNet** is selected for the **Virtual network** and the **Subnet** is set to **myBackendSubnet**. Accept the other defaults and then select **Next: Management**.<br>Application Gateway can communicate with instances outside of the virtual network that it's in, but you need to ensure there's IP connectivity.
185
+
6. On the **Networking** tab, verify that **myVNet** is selected for the **Virtual network** and the **Subnet** is set to **myBackendSubnet**. For **Public IP**, select **None**. Accept the other defaults and then select **Next: Management**.<br>Application Gateway can communicate with instances outside of the virtual network that it's in, but you need to ensure there's IP connectivity.
186
186
7. Select **Next: Monitoring** and set **Boot diagnostics** to **Disable**. Accept the other defaults and then select **Review + create**.
187
187
8. On the **Review + create** tab, review the settings, correct any validation errors, and then select **Create**.
188
188
9. Wait for the virtual machine creation to complete before continuing.
189
189
190
+
> [!NOTE]
191
+
> The default rules of the network security group block all inbound access from the internet, including RDP. To connect to the virtual machine, use Azure Bastion. For more information, see [Quickstart: Deploy Azure Bastion with default settings](../bastion/quickstart-host-portal.md).
192
+
190
193
### Install IIS for testing
191
194
192
195
In this example, you install IIS on the virtual machines to verify Azure created the application gateway successfully.
0 commit comments