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 2051-2075 of 2121 flagged pages
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-php-mysql-app/azure-portal-deploy-sample-code-6.md
...ial-php-mysql-app/azure-portal-deploy-sample-code-6.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not explicitly show Windows bias through tools or commands, but it also lacks any platform-specific examples or instructions. There are no Linux or Windows-specific commands, but the absence of any mention of Linux (or Windows) means Linux parity is not addressed.
Recommendations
- Add explicit notes or examples for both Windows and Linux users if platform-specific steps exist.
- Clarify whether the instructions are platform-agnostic or if there are differences for Linux environments.
- Include screenshots or terminal examples from both Windows and Linux if applicable.
Create Pull Request
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 describes accessing an SSH session via the Azure portal and a web URL, but does not mention or provide examples for accessing the service using standard SSH clients or command-line tools commonly used on Linux systems. There is no explicit Windows bias, but the lack of Linux-specific or cross-platform command-line examples may disadvantage Linux users.
Recommendations
- Add instructions or examples for connecting to the App Service container using standard SSH clients (e.g., the `ssh` command-line tool) on Linux and macOS.
- Clarify whether the SSH feature is available for both Windows and Linux App Service containers, and note any differences.
- Provide parity in documentation by including both browser-based and command-line access methods, ensuring users on all platforms have clear guidance.
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 Windows defaults before Linux in the configuration table and mentions Windows-specific limitations and behaviors. However, it does not provide Windows/Powershell-only examples, nor does it omit Linux equivalents. The CLI examples are cross-platform (Azure CLI), and Linux-specific behaviors are mentioned alongside Windows. There is a slight bias in listing Windows defaults first and referencing Windows-specific limitations before Linux.
Recommendations
- List Linux and Windows defaults in parallel columns or alternate which OS is mentioned first to avoid implicit prioritization.
- Where Windows-specific limitations are mentioned, also highlight any Linux-specific limitations (if any), or explicitly state when there are none.
- Continue to use cross-platform tools like Azure CLI for examples, and avoid Windows/Powershell-only instructions.
- Consider adding a summary table or section that clearly delineates differences and similarities between Windows and Linux App Service behaviors for DNS.
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. While Linux content is present, the structure prioritizes Windows scenarios, which may suggest a bias toward Windows users.
Recommendations
- Alternate the order of pivots so that Linux examples are presented first in some cases, or present both Windows and Linux pivots side-by-side where possible.
- Explicitly mention at the top that instructions are available for both Windows and Linux, to signal parity.
- Ensure that the depth and clarity of Linux examples match those of Windows, and that all features are equally documented.
- Consider adding a summary table comparing Windows and Linux approaches for quick reference.
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 default values for DNS configuration with 'Windows default value' listed before 'Linux default value' in the property table. However, there are no exclusive Windows or PowerShell examples, and all configuration examples use the cross-platform Azure CLI. There are no missing Linux examples, and no Windows-specific tools or patterns are promoted. The only other mention of Windows is a limitation note, which is relevant and not biased.
Recommendations
- List Linux and Windows defaults in parallel columns or in alphabetical order to avoid suggesting Windows as the primary platform.
- Where platform-specific behaviors or settings exist, provide equal prominence and detail for both Windows and Linux.
- Continue to use cross-platform tools (like Azure CLI) for configuration examples, and avoid introducing Windows-only tools unless Linux equivalents are also provided.
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 configuration properties in a table where Windows default values are listed before Linux defaults, and the narrative sometimes references Windows before Linux. However, the page does not provide OS-specific command-line examples (such as PowerShell or Bash), nor does it exclusively mention Windows tools or omit Linux examples. The Azure CLI, which is cross-platform, is used throughout for configuration steps.
Recommendations
- When presenting OS-specific configuration defaults, consider listing Linux and Windows in parallel columns or explicitly stating that order does not imply priority.
- Add clarifying notes that Azure CLI commands work identically on both Windows and Linux environments.
- Where there are OS-specific limitations (e.g., 'App Service on Windows doesn't support DNS resolution over TCP'), ensure similar Linux limitations (if any) are also mentioned for parity.
- If there are any OS-specific command-line or troubleshooting steps, provide both Windows (PowerShell/CMD) and Linux (Bash) examples.
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 maintains parity between Windows and Linux, especially in the configuration commands and explanations. However, in the section 'Configure name resolution behavior', the table lists 'Windows default value' before 'Linux default value', which is a subtle form of Windows-first bias. There are no PowerShell-specific examples, Windows-only tools, or missing Linux examples. The only other Windows-specific mention is in the limitations section, which is appropriate context.
Recommendations
- In the configuration table, consider listing Linux and Windows defaults in parallel columns or in alphabetical order (e.g., 'Linux default value' before 'Windows default value') to avoid implicit prioritization.
- If possible, provide explicit notes or examples for both Windows and Linux where behaviors differ, even if the difference is only in default values.
- Continue to avoid Windows-only tooling (such as PowerShell) in examples, and maintain the use of cross-platform tools like Azure CLI.
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 defaults before Linux. There are no explicit examples or instructions that are Windows-specific (such as PowerShell commands or Windows-only tools), nor are there missing Linux examples. However, the ordering in the table and some notes (such as limitations and feature support) mention Windows first or focus on Windows-specific limitations.
Recommendations
- List Linux and Windows defaults in a neutral order, or alternate which is listed first.
- Where platform-specific limitations or behaviors are mentioned, ensure both Windows and Linux are addressed equally, or clarify if only one is affected.
- If there are platform-specific configuration steps, provide examples for both Windows and Linux, or clarify when steps are identical.
- Consider adding a summary table or section explicitly comparing Windows and Linux behaviors for clarity.
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 default values for DNS configuration with 'Windows default value' listed before 'Linux default value' in the property table. However, the overall content and examples are platform-neutral, using Azure CLI commands applicable to both Windows and Linux environments. There are no PowerShell-specific examples, Windows-only tools, or missing Linux examples. The only explicit Windows-specific mention is in the limitations section, which is appropriate.
Recommendations
- In the property table, consider listing 'Linux default value' before 'Windows default value', or present both in parallel columns without implied priority.
- Explicitly state that all CLI examples are cross-platform to reassure Linux users.
- Where differences exist (such as the limitation for Windows), ensure similar Linux limitations (if any) are also mentioned for parity.
- Continue to avoid Windows-specific tools or commands unless Linux equivalents are also provided.
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 default values and behaviors for both Windows and Linux, but consistently lists Windows defaults before Linux in tables and explanations. There are no explicit examples or commands that are Windows-specific (such as PowerShell), nor are there Windows-only tools or patterns promoted. However, the ordering and phrasing (e.g., 'Windows default value' before 'Linux default value') may subtly prioritize Windows. There are no missing Linux examples, but the note about Windows Container apps and a limitation specific to Windows are called out, which is appropriate but could be balanced with Linux-specific notes if relevant.
Recommendations
- Alternate the order in which Windows and Linux defaults are presented, or present them in parallel columns to avoid implicit prioritization.
- Where possible, provide Linux-specific notes or limitations alongside Windows ones for parity, or explicitly state when there are no such limitations on Linux.
- If there are platform-specific CLI commands or behaviors, provide both Windows and Linux examples, or clarify when commands are platform-agnostic.
- Consider a summary table at the start that clearly delineates differences and similarities between Windows and Linux App Service environments.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-authentication-file-based.md
...les/app-service/configure-authentication-file-based.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation demonstrates a 'windows_first' bias by describing the file path configuration for Windows before Linux, and by using a Windows-style path (C:\home\site\wwwroot) in the main instructions and examples. Linux instructions are only mentioned as a note, and Linux-style paths are not used in the main steps or examples.
Recommendations
- Present Linux and Windows instructions/examples side-by-side or in parallel, rather than mentioning Linux only in a note.
- Use platform-agnostic language and examples where possible (e.g., refer to 'the root of your project' and show both Windows and Linux paths).
- In step-by-step instructions, include both Windows and Linux file path examples (e.g., 'C:\home\site\wwwroot\auth.json' for Windows and '/home/site/wwwroot/auth.json' for Linux).
- Explicitly state any platform differences in the main instruction flow, not just in notes.
- Consider adding a table or section summarizing platform-specific behaviors for clarity.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-authentication-file-based.md
...les/app-service/configure-authentication-file-based.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation exhibits a 'windows_first' bias in the section describing the configuration file path. It mentions the Windows deployment path (C:\home\site\wwwroot) first and provides a relative path example for Windows, while the Linux path is only mentioned later and as a note. There are no explicit Linux command-line or tool examples, and the documentation assumes familiarity with Windows file paths and conventions.
Recommendations
- Present Linux and Windows instructions/examples side by side or in parallel sections to ensure parity.
- When mentioning file paths, provide both Windows and Linux examples together (e.g., 'C:\home\site\wwwroot\auth.json' for Windows and '/home/site/wwwroot/auth.json' for Linux).
- Clarify any platform-specific limitations or differences in the main instruction steps, not just in notes.
- Include Linux-specific deployment or configuration tips where relevant, such as using Linux shell commands or tools.
- Avoid assuming the reader is deploying to Windows by default; use neutral language or explicitly state when instructions differ by platform.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-migration-assess-net.md
...ticles/app-service/app-service-migration-assess-net.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation page discusses assessing .NET web apps for migration to Azure App Service but does not provide any platform-specific examples or tools. However, it implicitly assumes a Windows/ASP.NET context by only referencing 'ASP.NET web apps' and not mentioning Linux-based .NET Core or cross-platform scenarios. There are no explicit Windows tools or PowerShell commands, but the absence of Linux or cross-platform guidance suggests a subtle Windows bias.
Recommendations
- Explicitly mention support for both Windows (ASP.NET) and Linux (.NET Core) web apps where applicable.
- Include examples or references for assessing Linux-hosted .NET apps, such as those running on .NET Core or ASP.NET Core.
- Clarify whether the assessment tools and recommendations apply equally to Linux-based .NET workloads.
- Add links or sections addressing Linux migration scenarios and any platform-specific considerations.
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 for all examples and does not provide any OS-specific instructions or examples. While Azure CLI is cross-platform and works on both Windows and Linux, there are no examples or mentions of Windows-specific tools (like PowerShell) or Linux-specific tools (like Bash scripts). However, the absence of any Linux-specific context or troubleshooting (such as shell differences, DNS tools, or networking commands) may leave Linux users without guidance for platform-specific scenarios.
Recommendations
- Explicitly mention that Azure CLI commands work on both Windows, Linux, and macOS, and provide installation links for each platform.
- Where relevant, add Linux-specific troubleshooting tips (e.g., using dig or nslookup for DNS verification, checking network connectivity with curl or wget).
- If there are any differences in behavior or prerequisites between Windows and Linux environments (such as file path formats, environment variables, or shell syntax), document these explicitly.
- Consider including at least one example using Bash scripting for automation, or reference how to run the Azure CLI commands in a Linux shell.
- If PowerShell or Windows-specific tools are not required, clarify that the instructions are platform-agnostic to reassure Linux users.
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 for DNS settings in a table, but consistently lists Windows defaults before Linux. There are no platform-specific command-line examples (e.g., PowerShell or Bash), and the Azure CLI is used throughout, which is cross-platform. However, the ordering of Windows before Linux in explanations and tables subtly prioritizes Windows. There are also more notes about limitations on Windows (e.g., DNS over TCP not supported), but no equivalent Linux-specific notes or caveats.
Recommendations
- Alternate the order of Windows and Linux in tables and explanations, or present them alphabetically (Linux, Windows) to avoid implicit prioritization.
- Add Linux-specific notes or caveats if any exist, to ensure parity of information.
- Explicitly state that Azure CLI commands work identically on both Windows and Linux, or provide platform-specific notes if there are differences.
- Where possible, use neutral phrasing (e.g., 'On Linux, the default is X; on Windows, the default is Y') rather than always listing Windows first.
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, indicating a 'windows_first' bias. However, Linux content is present and not missing.
Recommendations
- Reorder the pivots or examples so that Linux and Windows instructions are presented with equal prominence, or alternate which platform appears first.
- Explicitly state that both Windows and Linux are supported at the beginning of the documentation.
- Ensure that all examples and instructions are equally detailed for both Windows and Linux platforms.
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 'az webapp up' command without specifying the operating system or providing examples for either Windows or Linux environments. While not overtly Windows-biased, the lack of explicit Linux examples or mention of cross-platform applicability may leave Linux users uncertain about compatibility.
Recommendations
- Clarify that the 'az webapp up' command works on both Windows and Linux platforms, if applicable.
- Provide explicit examples or notes for both Windows (e.g., PowerShell, Command Prompt) and Linux (e.g., Bash) command usage.
- Mention any OS-specific considerations or prerequisites, if they exist.
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, via command line, or using cross-platform tools. There are no explicit Windows tools mentioned, but the lack of Linux-specific or cross-platform examples suggests an implicit bias.
Recommendations
- Add instructions for setting the configuration using the Azure CLI, which works on all platforms.
- Provide examples for setting the environment variable in Linux environments, such as using shell commands or editing configuration files.
- Clarify whether the dialog is available on both Windows and Linux App Service plans, or provide alternative methods for Linux users.
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 Linux-specific guidance or examples. This absence may disadvantage Linux users if platform-specific steps are relevant.
Recommendations
- If platform-specific steps are required, provide both Windows (e.g., PowerShell, Command Prompt) and Linux (e.g., Bash) examples.
- Explicitly mention if the instructions are platform-agnostic, or clarify any differences for Linux users.
- Ensure parity by including Linux tooling or command-line instructions where appropriate.
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 include any command-line examples or references to platform-specific tools. However, there is a lack of Linux-specific guidance or CLI-based alternatives, which may disadvantage users who prefer or require non-GUI, cross-platform workflows.
Recommendations
- Add equivalent Azure CLI or PowerShell command examples for users who prefer command-line interfaces.
- Include notes or links to documentation for configuring App Service settings via the Azure CLI or ARM templates, which are cross-platform.
- Explicitly mention that the instructions apply to both Windows and Linux App Service plans, or clarify any differences if they exist.
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 Linux or cross-platform command-line usage, which may leave Linux users without clear guidance.
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).
- Include command-line snippets for common Git operations on both platforms.
- Clarify that the instructions are platform-agnostic if that is the case, or specify any platform-specific steps as needed.
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 instructions, but it also does not mention or demonstrate Linux-specific workflows or tools. There is an implicit bias due to the absence of Linux (or Mac) command-line examples, which could leave non-Windows users without clear guidance.
Recommendations
- Add explicit instructions or examples for both Windows (e.g., PowerShell, Command Prompt) and Linux/macOS (e.g., Bash) when describing how to use the Git credentials.
- Include sample commands for cloning and pushing to the repository using both Windows and Linux command lines.
- Clarify that the process applies equally to all platforms, and mention any platform-specific nuances if they exist.
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 provide any platform-specific examples, but it also does not mention or demonstrate Linux-specific tools or workflows. The absence of any reference to Linux or cross-platform considerations may leave Linux users without guidance.
Recommendations
- Add explicit notes or examples for Linux users, such as how to view logs using common Linux tools or terminals.
- Clarify whether the instructions are platform-agnostic or provide parallel steps for both Windows and Linux environments.
- Mention any differences in log access or behavior between Windows and Linux deployments, if applicable.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-php-mysql-app/azure-portal-deploy-sample-code-6.md
...ial-php-mysql-app/azure-portal-deploy-sample-code-6.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 also lacks any platform-specific guidance or examples, particularly for Linux users, which may leave gaps in understanding for those not on Windows.
Recommendations
- Add explicit notes or examples for both Windows and Linux users if any steps differ between platforms.
- Clarify whether the instructions are platform-agnostic, and if not, provide parallel steps or screenshots for Linux environments.
- Include references to common Linux tools or terminal commands if relevant to the deployment process.
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 platform-specific steps, but it lacks any mention of Linux-specific tools, command-line instructions, or parity for non-Windows environments. There are no explicit Windows-only examples, but the absence of Linux-focused guidance could disadvantage Linux users.
Recommendations
- Add equivalent instructions for setting SCM_DO_BUILD_DURING_DEPLOYMENT using Linux command-line tools (e.g., Azure CLI, Bash).
- Include examples for both Windows (PowerShell, GUI) and Linux (Bash, CLI) environments to ensure parity.
- Clarify whether the dialog is available across platforms or provide alternative steps for Linux users if not.