Document Details
Functions How To Use Azure Function App Settings
❌
This page contains Windows bias
About This Page
This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.
Bias Analysis
Bias Types:
⚠️
powershell_heavy
⚠️
windows_first
⚠️
missing_linux_example
⚠️
windows_tools
Summary:
The documentation demonstrates a Windows bias by consistently providing Azure PowerShell examples alongside Azure CLI, often before or with more detail than Linux-specific workflows. Several features and tools (such as Kudu, App Service Editor, and in-portal console) are described as available or fully functional only on Windows, with Linux support either missing, limited, or explicitly marked as unsupported. Migration steps and plan management are documented only for Windows, with Linux migration called out as unsupported or limited. There are also several places where Windows terminology and patterns are used by default, and Linux alternatives are not described or are marked as unavailable.
Recommendations:
- Provide explicit Linux examples and workflows where possible, especially for command-line and deployment operations.
- Clarify feature parity and limitations for Linux up front, and offer Linux-specific guidance or workarounds where features are missing.
- Balance the use of PowerShell and CLI examples, and avoid presenting Windows tools or patterns first unless they are the only option.
- Where features are Windows-only (such as Kudu, App Service Editor, or in-portal console), suggest alternative Linux-compatible tools or approaches.
- For plan migration and management, document Linux-specific scenarios and clearly outline supported migration paths for Linux-hosted function apps.
- Review screenshots and UI instructions to ensure they are relevant for both Windows and Linux users, or provide parallel guidance.
Create pull request
Scan History
| Date | Scan ID | Status | Bias Status |
|---|---|---|---|
| 2025-09-16 00:00 | #113 | completed | ✅ Clean |
| 2025-08-17 00:01 | #83 | in_progress | ✅ Clean |
| 2025-07-13 21:37 | #48 | completed | ❌ Biased |
| 2025-07-09 13:09 | #3 | cancelled | ✅ Clean |
| 2025-07-08 04:23 | #2 | cancelled | ❌ Biased |
Flagged Code Snippets
### [Consumption-to-Premium](#tab/to-premium/azure-powershell)
Use the following procedure to migrate from a Consumption plan to a Premium plan on Windows:
1. Run the [New-AzFunctionAppPlan](/powershell/module/az.functions/new-azfunctionappplan) command as follows to create a new App Service plan (Elastic Premium) in the same region and resource group as your existing function app:
1. Run the [Update-AzFunctionApp](/powershell/module/az.functions/update-azfunctionapp) command as follows to migrate the existing function app to the new Premium plan:
1. When you no longer need the Consumption plan originally used by the app, you can run the [Remove-AzFunctionAppPlan](/powershell/module/az.functions/remove-azfunctionappplan) command as follows to delete the Consumption plan you migrated from:
### [Premium-to-Consumption](#tab/to-consumption/azure-cli)
Use the following procedure to migrate from a Premium plan to a Consumption plan on Windows:
1. Run the [az functionapp create](/cli/azure/functionapp#az-functionapp-create) command as follows to create a new function app (Consumption) in the same region and resource group as your existing function app. This command also creates a new Consumption plan in which the function app runs:
### [Azure PowerShell](#tab/azure-powershell)
The [`Get-AzFunctionAppSetting`](/powershell/module/az.functions/get-azfunctionappsetting) cmdlet returns the existing application settings, for example:
### [Consumption-to-Premium](#tab/to-premium/azure-powershell)
Use the following procedure to migrate from a Consumption plan to a Premium plan on Windows:
1. Run the [New-AzFunctionAppPlan](/powershell/module/az.functions/new-azfunctionappplan) command as follows to create a new App Service plan (Elastic Premium) in the same region and resource group as your existing function app: