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 2101-2121 of 2121 flagged pages
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 does not provide any platform-specific instructions or examples, but it also does not mention or illustrate any Linux-specific workflows, tools, or commands. There is no explicit Windows bias, but the absence of Linux (or macOS) examples or guidance could be seen as a lack of parity.
Recommendations
- Add explicit instructions or notes for Linux/macOS users, such as how to use the credentials with common Git clients on those platforms.
- Include example Git commands for both Windows (e.g., PowerShell or Command Prompt) and Linux/macOS (e.g., Bash).
- Mention any platform-specific considerations, such as where to store credentials securely on different operating systems.
- Clarify that the instructions are cross-platform if that is the case, or provide links to platform-specific documentation.
Create Pull Request
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-name-resolution.md
.../main/articles/app-service/overview-name-resolution.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation generally presents information in a cross-platform manner, but in the section 'Configure name resolution behavior', the property table lists 'Windows default value' before 'Linux default value', which may subtly prioritize Windows. There are no explicit Windows-only examples, tools, or commands; all configuration is shown using the Azure CLI, which is cross-platform. There are no missing Linux examples, and Linux-specific limitations or features are mentioned where relevant.
Recommendations
- In property tables or comparative sections, consider listing Linux and Windows in alphabetical order or using neutral phrasing (e.g., 'Default value (Windows)', 'Default value (Linux)') to avoid subtle prioritization.
- If there are platform-specific behaviors or limitations, ensure both Windows and Linux are discussed with equal prominence and detail.
- Continue using cross-platform tools like Azure CLI for examples, and avoid introducing Windows-specific tools (e.g., PowerShell) unless Linux equivalents are also provided.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-python-postgresql-app/deploy-zip-azure-portal-3.md
...ial-python-postgresql-app/deploy-zip-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 omits any mention of Linux or cross-platform considerations. This could be seen as a missed opportunity to clarify parity or platform-specific behavior.
Recommendations
- Explicitly state if the instructions apply equally to both Windows and Linux platforms.
- If there are platform-specific differences in the 'Save' operation or UI, provide examples or notes for both Windows and Linux users.
- Include screenshots or clarifications if the interface differs between platforms.
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 references the VS Code Output window for viewing logs but does not mention alternative methods or tools for viewing logs on Linux or other platforms outside of VS Code.
Recommendations
- Include instructions or examples for viewing logs using platform-agnostic tools (e.g., terminal commands like tail or cat for log files).
- Mention that logs can also be accessed via standard output or log files, and provide examples for Linux/macOS environments.
- Clarify that while VS Code Output is one option, users on other platforms or using different editors can use alternative methods.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-authentication-authorization.md
...s/app-service/overview-authentication-authorization.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation describes both Windows and Linux/container architectures for the authentication and authorization module, but the Windows (IIS module) architecture is presented first and in more detail. There are no explicit PowerShell or Windows-only command-line examples, and the only CLI examples use the cross-platform 'az' CLI. No Windows-specific tools or patterns are promoted elsewhere, and Linux/container deployment is covered, but always after Windows.
Recommendations
- Present Linux/container architecture before or alongside Windows, or use a neutral ordering (e.g., 'On Windows...' and 'On Linux/containers...').
- Ensure parity in technical detail for both Windows and Linux/container sections.
- If possible, provide explicit Linux-native examples or references (e.g., mention that the az CLI commands work on all platforms).
- Consider adding a table or diagram comparing Windows and Linux/container behaviors side by side for clarity and neutrality.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-plan-manage.md
...b/main/articles/app-service/app-service-plan-manage.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation focuses exclusively on managing App Service plans via the Azure portal UI, without providing any command-line examples. There is no evidence of Windows-specific tools or PowerShell commands, but there is also a lack of parity for Linux users: no CLI (Azure CLI, Bash) or Linux-oriented instructions are provided. The only mention of OS is in the context of selecting the operating system for the App Service plan, with no further guidance for Linux users.
Recommendations
- Add Azure CLI examples for all major tasks (create, move, scale, delete App Service plans), with commands that can be run on Linux, macOS, and Windows.
- Where relevant, provide Bash script snippets alongside any PowerShell or Windows command-line examples.
- Explicitly mention that all CLI examples are cross-platform, and clarify any OS-specific differences in behavior or prerequisites.
- Include links to documentation on using Azure CLI on Linux and macOS.
- If PowerShell or Windows tools are ever referenced, ensure Linux equivalents are presented with equal prominence and detail.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-error-pages.md
...lob/main/articles/app-service/configure-error-pages.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any OS-specific examples, commands, or tools, but it also does not mention Linux or provide Linux-specific guidance, despite being tagged as 'linux-related-content'. The instructions and UI references are generic to Azure App Service and do not demonstrate explicit Windows bias, but the lack of Linux-specific context or parity checks is a subtle bias, especially for users seeking Linux-relevant information.
Recommendations
- Explicitly state whether the error page configuration process is identical for both Windows and Linux App Service plans, or highlight any differences.
- Add a section or note clarifying Linux support, such as any known limitations or behavioral differences for custom error pages on Linux-based App Service.
- Provide Linux-specific troubleshooting tips or examples if applicable (e.g., how error handling may differ on Linux containers).
- Ensure that future updates include parity checks for both Windows and Linux App Service environments.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-python-postgresql-app/deploy-zip-azure-portal-2.md
...ial-python-postgresql-app/deploy-zip-azure-portal-2.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any platform-specific instructions or examples, but it also does not mention or demonstrate Linux-specific steps, tools, or considerations. There is a lack of parity in that no Linux (or cross-platform) guidance is given.
Recommendations
- Explicitly state whether the instructions apply equally to both Windows and Linux environments.
- If there are differences in setting environment variables or using the dialog on Linux-based App Service plans, provide Linux-specific guidance or screenshots.
- Include a note or section clarifying any platform-specific behavior for SCM_DO_BUILD_DURING_DEPLOYMENT.
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 tools or commands. However, it does not provide any examples or guidance for setting the variable via Linux command line or configuration files, which may be relevant for cross-platform users.
Recommendations
- Add examples for setting the SCM_DO_BUILD_DURING_DEPLOYMENT variable using Linux shell commands (e.g., export, or via configuration files).
- Include parity examples for both Windows (e.g., PowerShell, CMD) and Linux (e.g., Bash) environments.
- Clarify whether the dialog is available on all platforms or provide alternative instructions 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 entering a new setting using a generic 'dialog', but does not specify or provide examples for Linux environments, command-line interfaces, or cross-platform tools. There is no mention of how to accomplish the same task outside of a GUI, which may not be available or preferred on Linux systems.
Recommendations
- Add command-line examples for setting the environment variable using Bash (e.g., export SCM_DO_BUILD_DURING_DEPLOYMENT=true) for Linux users.
- Clarify whether the 'dialog' refers to a Windows-specific tool or a cross-platform interface, and provide alternatives if it is not cross-platform.
- Include instructions for setting the variable in configuration files or deployment scripts commonly used on Linux.
- Ensure that both GUI and CLI methods are documented, with equal prominence for Windows and Linux users.
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 navigation instructions that are platform-neutral, but it does not mention or provide any examples or guidance for Linux users, such as command-line alternatives or Linux-specific tools. This omission may leave Linux users without clear instructions if they are not using the portal UI.
Recommendations
- Add equivalent instructions for Linux users, such as using the Azure CLI or relevant Linux command-line tools to achieve the same configuration changes.
- Explicitly mention if the instructions apply equally to both Windows and Linux App Service plans, or clarify any differences.
- Provide links to Linux-specific documentation or examples where appropriate.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-nodejs-mongodb-app/deploy-local-git-azure-portal-4.md
...-nodejs-mongodb-app/deploy-local-git-azure-portal-4.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 command-line workflows. There are no explicit Windows tools or PowerShell commands, but the absence of Linux-specific guidance may disadvantage Linux users.
Recommendations
- Add explicit instructions or examples for both Windows and Linux users on how to use the credentials to push code (e.g., using Git from the command line on both platforms).
- Mention common tools for both environments, such as Git Bash for Windows and standard terminal for Linux.
- Clarify that the process is platform-agnostic if that is the case, or provide any platform-specific caveats if needed.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-plan-manage.md
...b/main/articles/app-service/app-service-plan-manage.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation page focuses exclusively on managing App Service plans through the Azure Portal UI and does not provide any command-line examples. There is no mention or example of using Windows-specific tools (such as PowerShell), but there is also a lack of parity for Linux users: no CLI (Azure CLI, Bash) or Linux-specific instructions are given. The only references to operating systems are in dropdowns or as prerequisites, not in actionable steps. This results in a bias of omission, where Linux users (and command-line users in general) are not served.
Recommendations
- Add Azure CLI examples for all major operations (create, move, scale, delete App Service plans), as the Azure CLI is cross-platform and widely used on Linux.
- Where relevant, include Bash script snippets for common tasks.
- Explicitly mention both Windows and Linux environments when discussing OS selection or constraints.
- If PowerShell or Windows tools are ever referenced, ensure equivalent Bash/Azure CLI examples are provided alongside.
- Consider a table or section comparing portal, CLI, and ARM template approaches for each operation.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-php-mysql-app/azure-portal-generate-db-schema-1.md
...ial-php-mysql-app/azure-portal-generate-db-schema-1.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides instructions for opening an SSH session via the Azure portal's browser-based interface, but does not mention or provide examples for connecting via native SSH clients, which are commonly used on Linux and macOS. There is no reference to platform-specific tools, but the lack of CLI-based instructions may disadvantage Linux users who prefer or require terminal access.
Recommendations
- Add instructions for connecting to the App Service container using a native SSH client (e.g., via the terminal on Linux/macOS or PowerShell/CMD on Windows).
- Include example SSH command lines, such as: `ssh <user>@<app-name>.scm.azurewebsites.net`.
- Clarify any platform-specific prerequisites or differences, if applicable.
- Ensure that both browser-based and CLI-based access methods are documented for parity.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-dotnetcore-sqldb-app/deploy-from-local-git-azure-portal-3.md
...core-sqldb-app/deploy-from-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 commands, but it implicitly assumes a generic workflow without mentioning Linux or cross-platform considerations. There are no explicit Windows or PowerShell commands, but the lack of Linux-specific guidance or parity examples (such as Linux terminal commands or credential management tips) may leave Linux users without clear instructions.
Recommendations
- Add explicit instructions or examples for both Windows (e.g., PowerShell, Command Prompt) and Linux (e.g., Bash) environments for cloning and pushing to the Git repository.
- Mention any platform-specific differences in credential usage or storage, such as how to handle passwords securely on Linux.
- Include screenshots or terminal snippets from both Windows and Linux to ensure parity.
- Clarify that the instructions are cross-platform, or specify any steps that differ between operating systems.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-name-resolution.md
.../main/articles/app-service/overview-name-resolution.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation presents both Windows and Linux default values in a configuration table, but consistently lists Windows first. There are no explicit Windows-only tools, commands, or examples, and all configuration examples use the cross-platform Azure CLI. However, the ordering of Windows before Linux in the table and in the note about unsupported features ("App Service on Windows does not support DNS resolution over TCP") subtly prioritizes Windows. There are no missing Linux examples, but Linux is always mentioned second.
Recommendations
- Alternate the order of Windows and Linux in tables and explanations, or use alphabetical order (Linux, Windows) to avoid implicit prioritization.
- Where possible, provide parity in notes and limitations (e.g., if a limitation is Windows-only, clarify if Linux has similar or different behavior).
- Explicitly state that all CLI examples are cross-platform to reinforce parity.
- Consider adding a brief section summarizing any platform-specific differences, rather than embedding Windows-first details throughout.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-app-gateway-integration.md
...ticles/app-service/overview-app-gateway-integration.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation exclusively uses Azure CLI commands and does not provide any OS-specific shell examples (such as PowerShell or Bash). However, there are no explicit Windows tools, PowerShell scripts, or references to Windows-specific patterns. The Azure CLI is cross-platform, but there are no Linux/Bash-specific examples or notes, nor are there any references to Linux tools or workflows. The documentation is neutral in tone but lacks explicit Linux parity in examples or troubleshooting steps.
Recommendations
- Add explicit Bash shell examples where relevant, especially for common Linux workflows.
- Include notes or troubleshooting tips for Linux environments, such as DNS resolution or file-based configuration nuances.
- If referencing command-line tools, clarify their cross-platform compatibility and provide alternative commands for PowerShell (Windows) and Bash (Linux/macOS) where differences exist.
- Mention any OS-specific considerations (e.g., file paths, environment variables) that may affect Linux users.
- Ensure that any referenced quickstarts or tutorials include both Windows and Linux setup instructions where applicable.
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 ordering of the code and container pivots. While Linux content is present, the structure prioritizes Windows, which may suggest a subtle bias towards Windows users.
Recommendations
- Alternate the order of platform pivots or present Linux and Windows examples side-by-side to ensure equal visibility.
- Explicitly mention that both Windows and Linux are supported at the top of the page.
- Consider a neutral introduction or overview before diving into platform-specific instructions.
- Ensure that Linux instructions are as detailed and prominent as Windows instructions.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-domain-traffic-manager.md
...ticles/app-service/configure-domain-traffic-manager.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any OS-specific command-line examples or instructions, but it does reference ASP.NET Core for URL rewriting as the only concrete application-level workaround for root domain mapping. This implicitly assumes a Windows/.NET stack and does not mention equivalent solutions for Linux-based stacks (e.g., Nginx, Apache). There are no explicit PowerShell, Windows tools, or Windows-first ordering, but the lack of Linux/OSS examples is a subtle bias.
Recommendations
- When suggesting application-level URL redirects, include examples for popular Linux-based web servers such as Nginx and Apache, alongside the ASP.NET Core example.
- Explicitly mention that the workaround for root domains can be implemented in any web framework or server, and provide links or references to documentation for common Linux stacks.
- If referencing application-level configuration, provide parity by showing both Windows/.NET and Linux/OSS approaches.
- Consider adding a note that the Azure portal and DNS changes are platform-agnostic, to reassure Linux users.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-error-pages.md
...lob/main/articles/app-service/configure-error-pages.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any OS-specific examples, but it also does not mention or demonstrate any Linux-specific tools, commands, or workflows. While the content is generally platform-neutral, there is a missed opportunity to address Linux users explicitly, especially given the 'linux-related-content' tag. There are no Windows-specific commands or tools, but the lack of Linux-specific guidance or troubleshooting constitutes a subtle bias by omission.
Recommendations
- Add explicit notes or examples for both Windows and Linux App Service environments, clarifying any differences in behavior or UI.
- Include troubleshooting steps or caveats for Linux-based App Service plans, such as file system case sensitivity, file permissions, or differences in error handling.
- If the UI or features differ between Windows and Linux App Service, provide screenshots or callouts for each.
- Mention any Linux-specific limitations or configuration steps, if applicable.
- Ensure that the FAQ and instructions address both Windows and Linux scenarios where relevant.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/webjobs-create.md
...-docs/blob/main/articles/app-service/webjobs-create.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide explicit examples or instructions for Linux users. While it mentions uploading executables or scripts in a .zip file, it does not clarify support for Linux-specific script types (e.g., Bash, Python) or provide Linux-oriented examples. There is no mention of Linux command-line tools, nor are there instructions for deploying or managing WebJobs from a Linux environment. The documentation is neutral in tone but implicitly assumes a Windows-centric workflow by omitting Linux-specific guidance.
Recommendations
- Explicitly list and provide examples for Linux-compatible script types (e.g., .sh, Python) in the 'Supported file types' section.
- Add a section or examples showing how to create, deploy, and manage WebJobs using Linux command-line tools (e.g., Azure CLI on Linux, Bash scripts).
- Clarify any differences in behavior or requirements when running WebJobs on Linux App Service plans versus Windows.
- Include screenshots or terminal output from Linux environments where relevant.
- Mention any prerequisites or considerations for Linux users, such as file permissions or shebang lines in scripts.