Skip to content

Conversation

@igorpupkinable
Copy link

WEBSITES_ENABLE_APP_SERVICE_STORAGE seems to be true by default for Linux containers.

I have created Web App on B1 service plan and tested 3 options as follows:

  1. SSH to Linux container to run mount | grep home with WEBSITES_ENABLE_APP_SERVICE_STORAGE=false configuration setting. Result: nothing is returned.
  2. SSH to Linux container to run mount | grep home with WEBSITES_ENABLE_APP_SERVICE_STORAGE=true configuration setting. Result: the mount point information is returned.
  3. SSH to Linux container to run mount | grep home without WEBSITES_ENABLE_APP_SERVICE_STORAGE configuration setting specified. Result: the mount point information is returned.

Web App start/stop is required for changes to take effect when conducting tests.

I am not sure if it behaves differently on other service plans but I have tested B1 in Switzerland North only.

`WEBSITES_ENABLE_APP_SERVICE_STORAGE` seems to be true by default for Linux containers.

I have created Web App on B1 service plan and tested 3 options as follows:

1. SSH to Linux container to run `mount | grep home` with `WEBSITES_ENABLE_APP_SERVICE_STORAGE=false` configuration setting. Result: nothing is returned.
2. SSH to Linux container to run `mount | grep home` with `WEBSITES_ENABLE_APP_SERVICE_STORAGE=true` configuration setting. Result: the mount point information is returned.
3. SSH to Linux container to run `mount | grep home` without `WEBSITES_ENABLE_APP_SERVICE_STORAGE` configuration setting specified. Result: the mount point information is returned.

Web App start/stop is required for changes to take effect when conducting tests.

I am not sure if it behaves differently on other service plans but I have tested B1 only.
@prmerger-automator
Copy link
Contributor

@igorpupkinable : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit eb38461:

✅ Validation status: passed

File Status Preview URL Details
articles/app-service/configure-custom-container.md ✅Succeeded

For more details, please refer to the build report.

@v-dirichards v-dirichards requested a review from Copilot January 27, 2026 15:42
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR corrects the documentation for the WEBSITES_ENABLE_APP_SERVICE_STORAGE setting in Azure App Service Linux custom containers. Based on testing, the default value is true (enabled) rather than false (disabled) as previously documented.

Changes:

  • Updated the default behavior description from "disabled" to "enabled"
  • Added instructions for disabling persistent storage (setting to false)
  • Reorganized the documentation to show disable instructions before enable instructions

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

In PowerShell, use the following command:

```azurepowershell-interactive
Set-AzWebApp -ResourceGroupName <group-name> -Name <app-name> -AppSettings @{"WEBSITES_ENABLE_APP_SERVICE_STORAGE"=false}
Copy link

Copilot AI Jan 27, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The boolean value should be lowercase to match PowerShell conventions. Change 'false' to '$false'.

Copilot uses AI. Check for mistakes.
In PowerShell, use the following command:

```azurepowershell-interactive
Set-AzWebApp -ResourceGroupName <group-name> -Name <app-name> -AppSettings @{"WEBSITES_ENABLE_APP_SERVICE_STORAGE"=false}
Copy link

Copilot AI Jan 27, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In PowerShell, the AppSettings parameter expects string values. The boolean value should be quoted as a string: \"false\" instead of false.

Copilot uses AI. Check for mistakes.
@v-dirichards
Copy link
Contributor

@msangapu-msft

Can you review the proposed changes?

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator bot added the aq-pr-triaged tracking label for the PR review team label Jan 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants