App Service
806
Total Pages
669
Linux-Friendly Pages
137
Pages with Bias
17.0%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
247 issues found
Showing 226-247 of 247 flagged pages
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation mentions PowerShell as a primary method for querying Azure activity logs, listing it before REST API and CLI. There is a subtle Windows-first bias in the ordering of tools, and Visual Studio integration is highlighted for Application Insights, which is a Windows-centric development environment. However, Linux and cross-platform options (CLI, REST API) are mentioned, and no critical monitoring functionality is exclusive to Windows.
Recommendations
- Explicitly mention and provide examples for Azure CLI and REST API usage alongside PowerShell, ensuring parity in instructions for Linux/macOS users.
- Highlight cross-platform development tools (such as VS Code) in addition to Visual Studio when discussing Application Insights integration.
- Ensure that all monitoring scenarios and tools are described in a platform-neutral way, with equal prominence given to Linux/macOS-compatible options.
- Consider ordering tool references alphabetically or by platform neutrality (e.g., 'Azure portal, CLI, PowerShell, REST API') to avoid implicit prioritization.
Create Pull Request
App Service
Migration Checklist - Azure App Service on Arc-enabled Kubernetes to Azure Container Apps on Arc-enabled Kubernetes
...b/main/articles/app-service/migrate-app-service-arc.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for resource queries, but PowerShell examples are always presented immediately after CLI, and no explicit Linux/macOS shell examples (e.g., Bash, zsh) are given. While Azure CLI is cross-platform, the inclusion and prominence of PowerShell may suggest a Windows-centric approach, especially since PowerShell is most commonly used on Windows. There are no Windows-only tools, but the example ordering and lack of explicit Linux shell context indicate a mild Windows bias.
Recommendations
- Clarify that Azure CLI commands work on Linux, macOS, and Windows, and provide example shell contexts (e.g., Bash, zsh) for Linux/macOS users.
- Consider including Linux/macOS-specific notes or troubleshooting tips if any CLI commands behave differently on those platforms.
- If PowerShell is included, mention that PowerShell Core is available cross-platform, or provide Bash equivalents for Linux/macOS users.
- Alternate the order of examples so that CLI (cross-platform) is shown first, and PowerShell is clearly marked as optional for Windows users.
App Service
Authentication and Authorization
...s/app-service/overview-authentication-authorization.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation describes both Windows and Linux/container architectures for the authentication module, but gives slightly more detail and explicit mention to Windows (IIS module) first. The only platform-specific tool mentioned is IIS (Windows), and the Windows architecture is described before Linux/container. However, all configuration and usage instructions are platform-neutral (using Azure portal, az CLI, configuration files), and there are no PowerShell-only examples or Windows-only steps. No critical sections are Windows-only.
Recommendations
- Present Linux/container architecture before or alongside Windows to avoid implicit prioritization.
- Provide equal technical detail for both Windows and Linux/container implementations (e.g., mention the container runtime or orchestration specifics if relevant).
- If mentioning IIS, also briefly mention the equivalent Linux web server context (e.g., nginx, Apache) or clarify that no integration is required.
- Add explicit statements confirming feature parity across Windows and Linux/container deployments.
- Ensure future examples and troubleshooting sections include Linux/container-specific guidance where applicable.
App Service
Create an App by Using a Terraform Template
...n/articles/app-service/provision-resource-terraform.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates some Windows bias in the prerequisites section, where Windows and PowerShell options are listed before Linux equivalents, and Windows-specific tools (PowerShell, Visual Studio Code) are emphasized. However, the main Terraform workflow and examples are cross-platform, and both Linux and Windows container templates are provided in parallel. The implementation steps use Bash commands, which are generally Linux/macOS-friendly.
Recommendations
- List Linux and Bash options before Windows/PowerShell in the prerequisites section to avoid implicit prioritization.
- Explicitly mention macOS support and provide links or instructions for macOS users where relevant.
- Include alternative editors (e.g., Vim, nano) or clarify that Visual Studio Code is cross-platform.
- Balance references to PowerShell with Bash or shell alternatives, especially in introductory sections.
- Add a note clarifying that all Terraform commands work equally on Linux, macOS, and Windows.
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. The Package Manager Console example uses PowerShell syntax and is specific to Visual Studio, a Windows-centric tool. The CLI instructions are cross-platform, but the ordering places Windows/Visual Studio instructions second, which is a minor 'windows_first' bias. There are no explicit Linux/macOS instructions or mentions of alternative IDEs/tools.
Recommendations
- Explicitly mention that the .NET Core CLI commands work on Linux and macOS as well as Windows.
- Add instructions for installing NuGet packages using Visual Studio Code or JetBrains Rider, which are popular on Linux/macOS.
- Clarify that the Package Manager Console is only available in Visual Studio (Windows), and suggest alternatives for non-Windows users.
- Consider listing the cross-platform CLI instructions first to emphasize platform neutrality.
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 installation instructions for required NuGet packages using both the .NET Core CLI and the Visual Studio Package Manager Console. 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 instructions immediately after. No explicit Linux/macOS IDE or package installation instructions (e.g., for JetBrains Rider, VS Code, or direct CLI usage on Linux/macOS) are provided.
Recommendations
- Explicitly state that the .NET Core CLI commands work on Windows, Linux, and macOS.
- Add installation instructions for popular Linux/macOS IDEs (e.g., VS Code, JetBrains Rider), or clarify that the Package Manager Console is only available in Visual Studio (Windows).
- Present the cross-platform .NET Core CLI instructions before the Windows-specific Visual Studio instructions.
- Consider including a note or section for Linux/macOS users, highlighting any OS-specific considerations (e.g., file paths, environment variables).
App Service
Tutorial - .NET Web app accesses storage by using managed identities | Azure
...cles/app-service/scenario-secure-app-access-storage.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides installation instructions for required NuGet packages using both the .NET Core CLI and the Visual Studio Package Manager Console (PowerShell). However, the Visual Studio/PowerShell method is listed second, and no explicit Linux/macOS-specific instructions (such as using VS Code, JetBrains Rider, or native Linux package managers) are provided. The .NET example itself is cross-platform, but the tooling instructions are slightly Windows-centric.
Recommendations
- Explicitly mention that the .NET Core CLI commands work on Linux/macOS as well as Windows.
- Add instructions for installing packages using VS Code or JetBrains Rider, which are popular on Linux/macOS.
- Clarify that Visual Studio Package Manager Console is Windows-only and suggest alternatives for non-Windows users.
- Consider adding a note about using the dotnet CLI in Bash or zsh terminals on Linux/macOS.
App Service
Build a scheduled WebJob using your preferred language
...ocs/blob/main/articles/app-service/tutorial-webjobs.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The .NET section of the documentation provides both Windows and Linux instructions, but Windows examples are presented first and in more detail (e.g., explicit .exe output, Windows-specific publish command). There is a slight emphasis on Windows tooling and terminology (e.g., referencing .exe, using Windows as the default tab, and linking to 'windowscode' tabs in supporting documentation). In contrast, Linux instructions are present but sometimes as addenda (e.g., 'Linux only' run.sh creation), and other language pivots (Python, Node, PHP, Java) focus exclusively on Linux, with no Windows parity or examples. The documentation also references 'supported file types' and CRON expressions using links with 'windowscode' tabs, which may reinforce a Windows-centric view. Overall, Linux users can complete the task, but the flow and examples are slightly Windows-biased, especially for .NET.
Recommendations
- Present Windows and Linux instructions side-by-side or in parallel, rather than Windows-first.
- Use neutral terminology (e.g., 'executable' instead of '.exe') and clarify when instructions differ by OS.
- Ensure supporting documentation links (e.g., for file types, CRON expressions) are OS-agnostic or provide both Windows and Linux tabs.
- Add explicit Windows instructions for non-.NET pivots (Python, Node, PHP, Java) if supported, or clarify OS limitations.
- Where possible, provide Linux examples with equal detail and prominence as Windows examples.
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for programmatic management of access restrictions, but PowerShell examples are consistently present and sometimes shown before CLI. Advanced scenarios (multi-source rules, restricting access to Azure Front Door) include PowerShell examples but lack explicit Linux shell (bash) or cross-platform scripting alternatives. There is a slight Windows-first bias in example ordering and tool emphasis, though Azure CLI is available and cross-platform.
Recommendations
- Ensure Azure CLI examples are always shown before or alongside PowerShell, as CLI is cross-platform.
- Add explicit bash scripting examples for advanced scenarios, especially where only PowerShell is shown.
- Clarify that all CLI examples work on Linux/macOS, and highlight cross-platform compatibility.
- Where PowerShell is used for multi-step scripting, provide equivalent bash/CLI workflows.
- Avoid implying PowerShell is the default or preferred tool for automation; present CLI as the primary option.
App Service
Build a scheduled WebJob using your preferred language
...ocs/blob/main/articles/app-service/tutorial-webjobs.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The .NET section of the documentation demonstrates a mild Windows bias: Windows build and packaging commands are presented first and in more detail, with explicit instructions for creating a Windows executable and zip file. Linux instructions are present but secondary, and require an extra step (creating a run.sh) that is not explained in depth. The references to supported file types and CRON expressions link to pages with 'windowscode' tabs, which may reinforce Windows-centric navigation. Other language pivots (Python, Node, Java, PHP) focus on Linux and do not show Windows bias.
Recommendations
- Present Linux and Windows instructions side-by-side or in parallel, rather than Windows first.
- Provide equal detail for Linux steps, such as explaining the purpose of run.sh and how to make it executable.
- Link to documentation tabs or sections that are OS-neutral or provide both Windows and Linux guidance.
- Clarify any differences in packaging or deployment for Linux users, especially in .NET scenarios.
- Consider adding macOS-specific notes where relevant, especially for local development.
App Service
Disable Basic Authentication for Deployment
...n/articles/app-service/configure-basic-auth-disable.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Summary
The documentation page exhibits mild Windows bias by referencing Windows-centric deployment tools (Web Deploy, Visual Studio) and mentioning Windows agent requirements and troubleshooting before Linux equivalents. While Azure CLI examples are cross-platform and no explicit PowerShell-only instructions are present, Windows tools and patterns (Web Deploy, Visual Studio) are referenced more frequently and with greater detail, and Windows agent caveats are described before Linux agent behaviors.
Recommendations
- Add explicit Linux/macOS deployment tool references and examples, such as using SCP/SFTP or rsync for file transfers.
- Provide troubleshooting guidance for Linux/macOS agents with equal prominence as Windows agents.
- When discussing deployment methods (e.g., Web Deploy), clarify cross-platform alternatives and their authentication behaviors.
- Ensure that any references to Visual Studio or Windows-specific tools are paired with equivalent instructions for Linux/macOS users (e.g., VS Code, JetBrains Rider, CLI workflows).
- List Linux/macOS agent behaviors before or alongside Windows agent notes to avoid Windows-first ordering.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for automating Premium V3 tier configuration, but PowerShell (a Windows-centric tool) is given a dedicated section and example. While Azure CLI is cross-platform and presented first, the inclusion of PowerShell may suggest a slight Windows bias. There are no Linux-specific shell examples (e.g., Bash), and screenshots and portal instructions are platform-neutral. No critical functionality is locked to Windows-only tools.
Recommendations
- Clarify that Azure CLI commands work on Linux, macOS, and Windows equally.
- Consider adding a Bash script example for Linux users to demonstrate parity.
- Explicitly mention that PowerShell Core is available cross-platform, or link to instructions for Linux/macOS installation.
- Ensure that any references to development tools (like 'Clone app') note their availability on all platforms.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-authentication-provider-facebook.md
...-service/configure-authentication-provider-facebook.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides only portal-based configuration steps and does not include any command-line examples. There are no explicit Windows-specific tools or commands (such as PowerShell), but there is also a lack of parity for Linux users, as no CLI (Azure CLI, Bash) or cross-platform automation examples are provided. This omission can disadvantage Linux users or those who prefer automation over portal UI.
Recommendations
- Add Azure CLI examples for configuring Facebook authentication, which are cross-platform and suitable for both Windows and Linux users.
- Include Bash script snippets for automating the setup process.
- Explicitly mention that the portal steps are platform-agnostic, but provide links or references to CLI-based alternatives for users who prefer command-line interfaces.
- Ensure future documentation includes both portal and CLI/scripted approaches to accommodate a wider range of developer preferences and environments.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-connect-to-azure-storage.md
...cles/app-service/configure-connect-to-azure-storage.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation presents Windows examples and instructions before Linux equivalents, as seen in the order of the code pivots. There is no explicit Linux bias, but the structure prioritizes Windows scenarios.
Recommendations
- Present Linux and Windows pivots in parallel or randomize their order to avoid implicit prioritization.
- Add a short introductory note clarifying that both Windows and Linux are equally supported.
- Ensure that Linux examples are as detailed and accessible as Windows examples.
- Consider starting with a neutral overview or a platform-agnostic section before splitting into OS-specific instructions.
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 for entering a setting using a generic 'dialog', but does not specify or provide examples for Linux environments, CLI usage, or platform-specific differences. There is no explicit Windows bias, but the lack of Linux-specific guidance may disadvantage Linux users.
Recommendations
- Add instructions or examples for setting SCM_DO_BUILD_DURING_DEPLOYMENT using the Azure CLI or in Linux environments.
- Clarify whether the 'dialog' refers to a cross-platform UI or a Windows-specific interface.
- Include parity examples for both Windows and Linux users, such as command-line steps for each.
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 does not provide any platform-specific examples or instructions, but it also does not mention or demonstrate how to set up a Git remote on either Windows or Linux. This omission can lead to implicit bias if future steps only cover Windows or PowerShell workflows, or if Linux users are left without guidance.
Recommendations
- Add explicit instructions and examples for setting up a Git remote on both Windows (using PowerShell or Command Prompt) and Linux (using Bash).
- Ensure that any future steps include both Windows and Linux command-line examples side by side.
- Mention common tools for both platforms (e.g., Git Bash for Windows, Terminal for Linux) to help users identify the appropriate workflow.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-php-mysql-app/azure-portal-change-site-root-1.md
...orial-php-mysql-app/azure-portal-change-site-root-1.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides instructions without specifying platform-specific steps or examples. There is no mention of Windows or Linux tools, but the absence of any Linux-specific guidance or examples may leave Linux users uncertain about platform differences or requirements.
Recommendations
- Explicitly state whether the instructions apply equally to both Windows and Linux App Service plans.
- If there are platform-specific differences in the Configuration or General settings tabs, provide separate guidance or screenshots for Linux and Windows.
- Add a note clarifying any features or settings that behave differently on Linux versus Windows.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-python-postgresql-app/deploy-local-git-azure-portal-3.md
...thon-postgresql-app/deploy-local-git-azure-portal-3.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation references copying the Git Clone URI for later use but does not provide any platform-specific instructions or examples. However, there is an implicit bias due to the absence of Linux-specific guidance or examples, such as command-line instructions for setting up a Git remote on Linux or macOS.
Recommendations
- Add explicit examples for setting up a Git remote using Linux/macOS command-line tools (e.g., git remote add origin <Git Clone Uri>).
- Ensure parity by including both Windows (PowerShell, CMD) and Linux/macOS (bash, zsh) instructions where relevant.
- Clarify that the instructions apply to all platforms, or provide links to platform-specific setup guides.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/ip-address-change-inbound.md
...main/articles/app-service/ip-address-change-inbound.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 implicitly assumes users interact with the Azure portal via a web browser. There are no Windows-specific tools or PowerShell commands mentioned, nor are there Linux equivalents. However, the absence of any CLI-based instructions (such as Azure CLI or Bash examples) means Linux users are not given parity with potential Windows users who might expect PowerShell or GUI instructions.
Recommendations
- Add Azure CLI examples for finding the inbound IP address, which can be run on Linux, macOS, or Windows.
- Explicitly mention that the steps can be performed from any OS via the web portal, or provide platform-agnostic alternatives.
- If PowerShell instructions are added in the future, ensure equivalent Bash/Azure CLI examples are included for Linux users.
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, but does not specify or illustrate how to perform this action on Linux systems (e.g., via CLI, environment variables, or configuration files). There are no explicit Windows tools mentioned, but the lack of Linux-specific guidance may hinder Linux users.
Recommendations
- Add examples for setting the configuration using the Azure CLI, which is cross-platform.
- Include instructions for setting environment variables directly in Linux shells (e.g., export SCM_DO_BUILD_DURING_DEPLOYMENT=true).
- Clarify whether the dialog is available on all platforms, or provide alternative methods for Linux users.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-connect-to-azure-storage.md
...cles/app-service/configure-connect-to-azure-storage.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation presents Windows code and container examples before Linux container examples, indicating a 'windows_first' bias. However, Linux content is present and not missing.
Recommendations
- Alternate the order of Windows and Linux sections, or present them in parallel tabs to avoid implying priority.
- Explicitly mention that both Windows and Linux are supported at the top of the page.
- Ensure that Linux examples are as detailed and accessible as Windows examples.
- Consider adding a summary table comparing Windows and Linux approaches for quick reference.