App Service
432
Total Pages
240
Linux-Friendly Pages
192
Pages with Bias
44.4%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
2121 issues found
Showing 2026-2050 of 2121 flagged pages
App Service
Getting started with Azure App Service
...docs/blob/main/articles/app-service/getting-started.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias, especially in the .NET/ASP.NET section, where Windows tools like Visual Studio and Azure PowerShell are listed before Linux-friendly options. The 'Next step' callout also promotes a Windows-centric workflow. Some Python examples default to Windows tabs, and PowerShell is highlighted as a deployment method for .NET, with Linux CLI options not always equally emphasized. Other stacks (Java, Node.js, PHP) show better Linux parity, but the overall structure and example ordering favor Windows tools and workflows.
Recommendations
- Reorder tool lists to present cross-platform or Linux options first, or in parallel with Windows tools.
- Ensure all examples (especially for .NET and Python) include explicit Linux/macOS instructions and tabs.
- Add Azure CLI and Bash examples wherever PowerShell is mentioned.
- Balance 'Next step' actions to include Linux/macOS-friendly workflows, not just Windows-centric ones.
- Clarify in each section which tools are cross-platform and which are Windows-only.
Create Pull Request
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/quickstart-python/deploy-zip-curl-commands.md
...includes/quickstart-python/deploy-zip-curl-commands.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents both Bash and PowerShell examples, but the instructions and notes are slightly more tailored to PowerShell/Windows users. The PowerShell example includes a special note, and the order of tabs places Bash first, but the initial instructions reference the Azure portal UI, which is identical across platforms. There is a mild emphasis on PowerShell-specific considerations.
Recommendations
- Add Linux/macOS-specific notes if needed (e.g., file path formats, authentication differences).
- Ensure that any PowerShell-specific caveats are matched with Bash/Linux equivalents if applicable.
- Consider clarifying that both Bash and PowerShell examples are cross-platform and that the Azure portal steps are the same regardless of OS.
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both PowerShell and Azure CLI examples for granting Microsoft Graph permissions to a managed identity, but PowerShell is presented first and in more detail. PowerShell is typically associated with Windows environments, and its prominence may signal a Windows-first approach. There are no Linux-specific shell examples (e.g., Bash), nor is there explicit mention of Linux/macOS compatibility for the CLI commands.
Recommendations
- Present Azure CLI examples before PowerShell, as Azure CLI is cross-platform and more familiar to Linux/macOS users.
- Explicitly state that Azure CLI commands work on Linux/macOS, and provide any necessary prerequisites or troubleshooting tips for those platforms.
- Add Bash script examples or clarify that the Azure CLI example is intended for Bash/zsh shells on Linux/macOS.
- Avoid language that assumes use of Visual Studio or other Windows-centric tooling unless alternatives are also described.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-nodejs-mongodb-app/deploy-zip-curl-commands.md
...utorial-nodejs-mongodb-app/deploy-zip-curl-commands.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for deploying via curl, but the PowerShell section includes extra guidance and troubleshooting specific to Windows users (about quoting the username). The Bash example is presented first, but the PowerShell example is more detailed, which may suggest a slight Windows bias.
Recommendations
- Add equivalent troubleshooting notes for Bash users if relevant (e.g., quoting issues, authentication nuances).
- Ensure that any special instructions for PowerShell are matched with similar guidance for Bash or other shells if applicable.
- Consider including a Linux-specific troubleshooting section if there are known issues.
- Explicitly state that both examples are functionally equivalent and clarify platform applicability.
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation exhibits mild Windows bias. Windows-specific paths (e.g., %HOME%, D:\home\site\wwwroot) and tools (Kudu DebugConsole, FTP) are mentioned without Linux equivalents. Examples and instructions often use Windows-style paths and refer to Windows concepts first, with Linux alternatives mentioned secondarily or not at all. PowerShell is referenced as a scripting option, but Bash or Linux shell scripting is not. There are no explicit Linux/macOS CLI or file management examples, and some instructions (like uploading files to D:\home) are Windows-centric.
Recommendations
- Provide Linux/macOS equivalents for file paths (e.g., /home/site/wwwroot) and clarify platform differences.
- Include Bash or Linux shell scripting samples alongside PowerShell in the 'Automate with scripts' section.
- Mention Linux-native tools (such as SCP, SFTP) for file uploads, not just FTP/Kudu.
- Show Linux examples first or side-by-side with Windows examples where applicable.
- Clarify whether Kudu DebugConsole and other tools are available and behave the same on Linux App Service plans.
App Service
Supported platforms and file types
...includes/webjobs-create/webjobs-supported-platforms.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation lists Windows hosting options and Windows file/script types before Linux equivalents. Windows executables and scripts are described first, and PowerShell scripts are called out separately, while Bash scripts are grouped with other scripting languages. This ordering and emphasis subtly prioritize Windows tools and patterns.
Recommendations
- List Linux and Windows hosting options together or alternate their order to avoid implicit prioritization.
- Present file/script types in a neutral order (e.g., alphabetical or by usage popularity) rather than Windows-first.
- Give equal emphasis to Bash scripts as to PowerShell scripts, possibly by listing them together or providing parallel examples.
- Consider adding explicit examples for both Windows and Linux script types to demonstrate parity.
App Service
Set Up Azure Arc for App Service, Functions, and Logic Apps
.../articles/app-service/manage-create-arc-environment.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for all commands, but PowerShell examples are always shown immediately after Bash, and in some cases, the PowerShell syntax is more detailed. There is a slight Windows-first bias in the ordering and presence of PowerShell examples, which may suggest Windows as a primary environment. However, Linux users are not blocked from completing any steps, as Bash examples are always present and complete.
Recommendations
- Consider listing Bash examples first, as Bash is the default shell for most Linux/macOS users and also available in Windows via WSL.
- Explicitly mention Linux/macOS compatibility in the prerequisites, and clarify that Bash examples work on Linux/macOS and Windows (with WSL or Git Bash).
- Add a note that PowerShell examples are primarily for Windows users, while Bash is cross-platform.
- Where platform-specific behaviors exist (e.g., file paths, base64 encoding), clarify any differences or provide additional guidance for Linux/macOS users.
App Service
Migrate from gateway-based to regional virtual network integration
.../app-service/migrate-gateway-based-vnet-integration.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides command-line examples for Azure CLI and Azure PowerShell, with PowerShell examples shown for every step alongside CLI and portal instructions. PowerShell is a Windows-centric tool, and its inclusion in parity with CLI may suggest a slight Windows bias. However, Azure CLI is cross-platform and appears first in each example section, and there are no steps that require Windows-only tools or patterns. The documentation does not provide Linux/macOS-specific shell examples (e.g., bash scripts), but the CLI commands are suitable for all platforms. There is no evidence of critical Windows-only instructions, but the presence of PowerShell throughout may create minor friction for Linux/macOS users unfamiliar with it.
Recommendations
- Clarify that Azure CLI commands are fully cross-platform and recommended for Linux/macOS users.
- Consider providing bash script examples or notes for Linux/macOS users where appropriate.
- Explicitly state that PowerShell examples are optional and primarily for Windows users.
- Add a brief section on platform compatibility for the provided tools (Azure CLI vs PowerShell).
App Service
Authentication and Authorization
...s/app-service/overview-authentication-authorization.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page presents the architecture for Windows (IIS module) before Linux (container/Ambassador pattern) and provides more detail about the Windows implementation. The only platform-specific tool mentioned is IIS (Windows), and no Linux-specific tools or patterns (such as nginx, Apache, or Linux service management) are referenced. However, the page does describe the Linux/container architecture and does not provide Windows-only examples or commands. All CLI examples use Azure CLI, which is cross-platform.
Recommendations
- Present Linux/container architecture before or alongside Windows to avoid Windows-first impression.
- Include references to common Linux web server patterns (e.g., nginx, Apache) where relevant.
- Clarify that Azure CLI commands work on Linux/macOS as well as Windows.
- Add explicit notes or examples for Linux/macOS users if there are platform-specific steps or considerations.
- Balance the level of detail between Windows and Linux/container sections.
App Service
Integrate your app with an Azure virtual network
...main/articles/app-service/overview-vnet-integration.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias. Windows-specific features (such as Windows Containers) are described in detail, including sample calculations and subnet sizing, while equivalent Linux container scenarios are not covered. Windows limitations (e.g., domain join, NetBIOS) are mentioned, but Linux-specific networking or container considerations are absent. CLI examples are cross-platform, but troubleshooting and operational guidance do not provide parity for Linux/macOS users. The only explicit Linux mention is in the context of continuous deployment network dependencies, which is brief and lacks broader Linux operational guidance.
Recommendations
- Add equivalent Linux container subnet/IP sizing guidance and examples.
- Include Linux/macOS-specific networking limitations or considerations, if any.
- Provide troubleshooting steps and operational guidance for Linux-based App Service scenarios.
- Ensure examples and sample calculations are provided for both Windows and Linux environments.
- Where Windows-specific features or limitations are described, add parallel Linux information or explicitly state if not applicable.
App Service
Quickstart: Run a Custom Container on App Service
...in/articles/app-service/quickstart-custom-container.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page presents Windows-related pivots and examples before Linux equivalents, such as listing Windows Visual Studio and Azure Portal instructions prior to Linux Visual Studio Code and Portal instructions. This ordering may subtly prioritize Windows workflows, but both platforms are covered with dedicated sections.
Recommendations
- Alternate the order of Windows and Linux pivots to avoid implicit prioritization.
- Ensure that Linux/macOS examples are as detailed and prominent as Windows ones.
- Add a neutral introductory section clarifying parity and platform support.
- Explicitly mention cross-platform CLI options where possible.
App Service
Tutorial - .NET Web app accesses Microsoft Graph as the user | Azure
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/scenario-secure-app-access-microsoft-graph-as-user.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both .NET CLI and Visual Studio Package Manager Console (PowerShell) instructions for installing NuGet packages, but the Visual Studio/PowerShell example is given after the cross-platform .NET CLI example. There is a slight Windows bias in mentioning Visual Studio and its Package Manager Console, which is Windows-specific, but Linux users are not blocked since the .NET CLI instructions are present and shown first. No other Windows-specific tools or patterns are present, and Linux/macOS users can follow the tutorial without significant friction.
Recommendations
- Explicitly mention that the .NET CLI commands work on Linux and macOS.
- Clarify that the Visual Studio Package Manager Console is Windows-only.
- Optionally, add a note for Linux/macOS users to use the .NET CLI for package installation.
- Consider adding a short section or callout for Linux/macOS users to confirm parity.
App Service
Tutorial - .NET Web app accesses Microsoft Graph as the app| Azure
...e/scenario-secure-app-access-microsoft-graph-as-app.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides installation instructions for the required NuGet packages using both the .NET Core CLI and the Package Manager Console in Visual Studio. However, the Package Manager Console example uses PowerShell syntax and references Visual Studio, which is primarily a Windows tool. The .NET Core CLI example is cross-platform, but the ordering places the Windows-centric Visual Studio/PowerShell instructions immediately after, potentially implying priority. No Linux/macOS-specific instructions or tooling are mentioned.
Recommendations
- Explicitly state that the .NET Core CLI commands work on Windows, Linux, and macOS.
- Move the .NET Core CLI instructions before the Visual Studio/PowerShell instructions to emphasize cross-platform support.
- Add a note for Linux/macOS users confirming that Visual Studio is optional and that cross-platform editors (e.g., VS Code) can be used.
- Consider including installation instructions for popular Linux/macOS package managers or editors if relevant.
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias, primarily through the use of Windows-style file paths (e.g., 'c:\data\import') in configuration examples and the absence of explicit Linux/macOS equivalents. All examples use C# and .NET APIs, which are cross-platform, but there are no instructions or notes for Linux/macOS users regarding file path formats, environment variable conventions, or platform-specific behaviors. Windows file system patterns are shown exclusively, and Windows paths are used in examples before any mention of Linux alternatives.
Recommendations
- Provide Linux/macOS equivalents for file path examples (e.g., '/home/user/data/import').
- Add notes clarifying that file paths and environment variable conventions differ on Linux/macOS.
- Explicitly state that all .NET Core examples are cross-platform and provide guidance for running on Linux/macOS.
- Where relevant, mention platform-specific considerations (e.g., permissions, case sensitivity, path separators).
- Include troubleshooting tips for Linux/macOS users, especially for file system bindings and configuration.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/quickstart-python/create-app-service-visual-studio-code-3.md
...tart-python/create-app-service-visual-studio-code-3.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides an instruction to create an App Service Web App but does not specify or illustrate how this action would differ or be performed on Linux versus Windows platforms. There is no mention of Linux-specific steps, tools, or considerations.
Recommendations
- Include explicit instructions or notes for both Windows and Linux users if the process differs.
- If the UI or CLI tools behave differently on Linux, provide screenshots or command examples for both platforms.
- Clarify whether the 'Create App Service Web App...' option is available and behaves identically on Linux environments.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/quickstart-python/create-app-service-visual-studio-code-9.md
...tart-python/create-app-service-visual-studio-code-9.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any platform-specific examples or instructions, but it also omits any mention of Linux or cross-platform considerations. This absence can be seen as a subtle bias, as it may implicitly assume a default (often Windows) environment without clarifying applicability to Linux users.
Recommendations
- Explicitly state whether the instructions apply to both Windows and Linux environments.
- If there are platform-specific steps or differences, provide examples for both Windows (e.g., PowerShell, Command Prompt) and Linux (e.g., Bash).
- Clarify any prerequisites or environment-specific considerations for Linux users.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/quickstart-python/deploy-cli.md
...s/app-service/includes/quickstart-python/deploy-cli.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation references the use of the 'az webapp up' command without providing any platform-specific examples. While the command is cross-platform, there is no indication of how to run it on Linux or macOS, nor are there any shell-specific examples (e.g., Bash vs. PowerShell). This lack of explicit Linux (or non-Windows) guidance may unintentionally bias the documentation toward Windows users, especially if other pages in the documentation set default to Windows examples.
Recommendations
- Include explicit examples for running the 'az webapp up' command in both Bash (Linux/macOS) and PowerShell (Windows) shells.
- Add a note clarifying that the Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
- If there are platform-specific considerations (such as authentication or environment setup), provide guidance for each major OS.
- Ensure that future documentation consistently provides parity between Windows and Linux/macOS examples.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/quickstart-python/deploy-zip-azure-portal-2.md
...ncludes/quickstart-python/deploy-zip-azure-portal-2.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides instructions for setting a configuration value using a dialog interface, but does not specify or illustrate how to perform this action on Linux systems or via command-line tools commonly used on Linux. There is no mention of Linux-specific methods or parity with Windows approaches.
Recommendations
- Add explicit instructions for setting the configuration using Linux command-line tools, such as the Azure CLI or environment variable export commands.
- Include examples for both Windows (e.g., PowerShell, GUI) and Linux (e.g., Bash, CLI) to ensure parity.
- Clarify whether the dialog interface is available on both Windows and Linux, or specify alternatives for Linux users.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/quickstart-python/stream-logs-visual-studio-code-2.md
.../quickstart-python/stream-logs-visual-studio-code-2.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not explicitly mention or provide examples for Linux users. While it references the VS Code Output window, which is cross-platform, there is no guidance or examples specific to Linux environments, nor is there mention of Linux-specific tools or workflows.
Recommendations
- Add explicit statements confirming that the instructions apply equally to Linux, macOS, and Windows.
- Include examples or screenshots from Linux environments to demonstrate parity.
- Mention any Linux-specific considerations or troubleshooting steps, if applicable.
- Clarify that VS Code Output window behavior is consistent across platforms, or note any differences.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-python-postgresql-app/deploy-local-git-azure-portal-4.md
...thon-postgresql-app/deploy-local-git-azure-portal-4.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides instructions for obtaining deployment credentials but does not include any platform-specific examples or commands. However, it also does not mention or demonstrate how to use these credentials on either Windows or Linux, resulting in a lack of Linux parity if users expect command-line guidance.
Recommendations
- Add explicit examples for both Windows (e.g., using PowerShell or Command Prompt) and Linux/macOS (e.g., using Bash) to show how to use the credentials when pushing code.
- Include sample git commands for both platforms, demonstrating how to input the credentials when prompted.
- Clarify that the process is cross-platform and provide any platform-specific notes if there are differences in credential handling.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-php-mysql-app/azure-portal-get-connection-string-2.md
...-php-mysql-app/azure-portal-get-connection-string-2.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides generic instructions for configuring an application setting in Azure App Service but does not include any platform-specific examples. However, it also does not mention or provide examples for Linux environments (e.g., using Azure CLI, bash, or Linux-specific configuration methods), which may leave Linux users without clear guidance.
Recommendations
- Add explicit instructions or examples for configuring application settings using the Azure CLI or bash, which are commonly used in Linux environments.
- Include a note or section clarifying that the instructions apply to both Windows and Linux App Service plans, or specify any differences.
- Provide screenshots or command-line examples relevant to Linux users to ensure parity.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-nodejs-mongodb-app/build-settings-azure-portal-2.md
...al-nodejs-mongodb-app/build-settings-azure-portal-2.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides instructions using a generic dialog interface without specifying any platform-specific commands or tools. However, it does not include any command-line examples for either Windows (e.g., PowerShell) or Linux (e.g., Bash), which could leave Linux users without clear guidance if they prefer or require CLI-based configuration.
Recommendations
- Add equivalent command-line examples for both Windows (PowerShell) and Linux (Bash) to set the environment variable.
- Explicitly mention how to perform this configuration using CLI tools such as Azure CLI or environment variable files on both platforms.
- Ensure that any future examples or instructions are presented for both Windows and Linux users to maintain parity.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-nodejs-mongodb-app/deploy-local-git-azure-portal-3.md
...-nodejs-mongodb-app/deploy-local-git-azure-portal-3.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation references setting up a Git remote but does not provide any platform-specific instructions or examples. There is no mention of how to perform the task on either Windows or Linux, but the absence of Linux (or any cross-platform) command-line examples is a missed opportunity for parity.
Recommendations
- Add explicit examples for setting up a Git remote using both Windows (e.g., PowerShell or Command Prompt) and Linux/macOS (e.g., Bash).
- Ensure that any future steps referencing command-line actions include both Windows and Linux/macOS syntax.
- Consider providing a generic, cross-platform Git command example (e.g., 'git remote add origin <Git Clone Uri>') and clarifying that it works on all major platforms.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-php-mysql-app/azure-portal-clean-up-resources-1.md
...ial-php-mysql-app/azure-portal-clean-up-resources-1.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides generic instructions for using the Azure portal and does not mention or provide examples for either Windows or Linux environments. However, it omits any command-line or OS-specific instructions, which could be relevant for users who prefer or require CLI-based workflows, especially on Linux.
Recommendations
- Add equivalent instructions for accessing resource groups using the Azure CLI (az group show) with example commands.
- Include both Windows (PowerShell) and Linux (Bash) command-line examples where relevant.
- Clarify that the instructions are for the Azure portal UI, and provide links or references to CLI documentation for both Windows and Linux users.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-php-mysql-app/azure-portal-deploy-sample-code-3.md
...ial-php-mysql-app/azure-portal-deploy-sample-code-3.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not explicitly show Windows bias, as it avoids mentioning any OS-specific tools or commands. However, it lacks any platform-specific guidance or examples, and does not provide Linux-specific instructions or parity checks, which could be seen as a missed opportunity for inclusivity.
Recommendations
- Add explicit notes or examples for both Windows and Linux users where relevant, especially if file paths, environment variable syntax, or tooling might differ.
- Clarify that the instructions are platform-agnostic if that is the case, or specify any steps that may differ between Windows and Linux.
- Include troubleshooting or verification steps for both Windows and Linux environments to ensure parity.