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 2076-2100 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 examples or instructions, but it also does not mention or illustrate Linux-specific workflows, tools, or commands. While it avoids explicit Windows bias (such as PowerShell commands or Windows-only tools), it misses the opportunity to demonstrate parity by including Linux (or macOS) command-line examples for pushing code to the remote repository.
Recommendations
- Add explicit examples for pushing code using both Windows (e.g., PowerShell or Command Prompt) and Linux/macOS (e.g., Bash) terminals.
- Mention common cross-platform tools (such as Git Bash, Terminal, etc.) to ensure users on all platforms feel included.
- If screenshots are included elsewhere, ensure they represent a mix of operating systems.
- Clarify that the instructions apply equally to all platforms, or provide platform-specific notes where behavior may differ.
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 how to open an SSH session via the Azure portal's web interface, but does not mention or provide examples for accessing the SSH session using standard Linux or cross-platform command-line tools (e.g., OpenSSH client). This omits guidance for users who prefer or require CLI-based workflows, which are common on Linux.
Recommendations
- Add instructions for connecting to the App Service container using the standard SSH client (e.g., `ssh` command) from a terminal.
- Clarify whether the SSH feature is available for both Windows and Linux App Service containers, and note any differences.
- Provide equivalent command-line examples for Linux/macOS users, not just browser-based instructions.
- Mention any prerequisites or configuration needed to enable SSH access from non-browser clients.
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 instructions using the Azure portal UI, which is platform-agnostic, but does not include any examples for configuring application settings via command-line tools such as Azure CLI or PowerShell. This omission can disadvantage Linux users who may prefer or require CLI-based workflows.
Recommendations
- Add examples for configuring application settings using the Azure CLI, which is cross-platform and commonly used on Linux.
- If relevant, include PowerShell examples as well, but ensure they are presented alongside or after CLI examples to avoid Windows-first bias.
- Explicitly mention that the Azure portal UI is available on all platforms, but provide alternative instructions for users who prefer command-line interfaces.
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' ordering bias. However, Linux content is present and not missing.
Recommendations
- Reorder the pivots so that Linux and Windows examples are presented in parallel or with Linux first, especially since the ms.custom metadata includes 'linux-related-content'.
- Explicitly mention that equivalent instructions are available for both Windows and Linux to reassure users of parity.
- Consider providing a summary table or section at the top outlining support for both platforms before diving into platform-specific pivots.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/environment/overview.md
...blob/main/articles/app-service/environment/overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation lists Windows web apps before Linux web apps in the supported workloads and consistently references Windows SKUs and containers first in pricing and feature tables. There are no explicit examples or tooling references, but the ordering and phrasing suggest a subtle Windows-first bias.
Recommendations
- Alternate the order of Windows and Linux mentions throughout the documentation (e.g., 'Linux and Windows web apps').
- Where possible, provide equal emphasis on Linux and Windows in feature and pricing tables, or clarify that both are equally supported.
- Explicitly mention that all features and capabilities apply equally to Linux and Windows unless there are exceptions, and clearly highlight any such exceptions.
- If examples or command-line instructions are added in the future, ensure both Windows (PowerShell/CLI) and Linux (Bash/CLI) examples are provided.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/environment/creation.md
...blob/main/articles/app-service/environment/creation.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation references a minimum charge for 'one instance of Windows Isolated v2' in the App Service plan before mentioning any Linux equivalent, and does not clarify Linux-specific pricing or deployment details. There are no explicit Linux examples or references, and the only OS-specific mention is for Windows, which may suggest a Windows-first bias.
Recommendations
- Include information about Linux-based App Service plans, including any minimum charges or differences in deployment and scaling.
- Clarify whether the minimum instance charge applies to Linux as well as Windows, or provide Linux-specific pricing details.
- Add examples or notes that address both Windows and Linux scenarios where relevant.
- Review the documentation for other subtle OS-specific assumptions and ensure parity in guidance for both platforms.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/environment/creation.md
...blob/main/articles/app-service/environment/creation.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page exhibits a subtle 'windows_first' bias by referencing Windows-specific SKUs (e.g., 'Windows Isolated v2') as the default or minimum charge in the App Service plan, without mentioning Linux equivalents or clarifying Linux support. There are no command-line examples, but the only platform-specific mention is Windows, and Linux is not addressed at all.
Recommendations
- Explicitly mention Linux support and pricing models where Windows-specific SKUs are referenced. For example, clarify whether there is a Linux Isolated v2 SKU and its minimum charges.
- If App Service Environment supports both Windows and Linux, provide parity in documentation by describing both options equally.
- Where platform-specific behavior or pricing applies, add a comparative table or note to help users understand differences between Windows and Linux deployments.
- Include Linux-specific considerations or links to Linux documentation if relevant.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/scenario-secure-app-authentication-app-service.md
...vice/scenario-secure-app-authentication-app-service.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation page does not provide any platform-specific examples or instructions. However, it also does not mention or demonstrate Linux-specific commands, tools, or workflows, potentially leaving Linux users without clear guidance if platform differences exist.
Recommendations
- Review included content (such as referenced includes) to ensure Linux-specific instructions or examples are present where platform differences exist.
- Explicitly mention if steps are platform-agnostic, or provide side-by-side examples for both Windows (PowerShell/Command Prompt) and Linux (Bash/CLI) where relevant.
- Add notes or links to Linux-specific troubleshooting or environment setup if applicable.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/environment/creation.md
...blob/main/articles/app-service/environment/creation.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page demonstrates a subtle Windows bias by referencing 'Windows Isolated v2' as the minimum charge in the 'Regional deployment' section, without mentioning Linux equivalents or clarifying Linux support. No explicit Linux examples, tools, or deployment patterns are provided, and the only OS-specific reference is to Windows, which is mentioned first and exclusively.
Recommendations
- Clarify whether Linux-based App Service plans are supported in each deployment type, and if so, mention them alongside Windows.
- If there are differences in pricing or minimum instance requirements for Linux plans, document these explicitly.
- Include examples or notes relevant to Linux deployments where applicable, such as Linux-specific considerations for App Service Environment.
- Review the documentation for other subtle OS-specific terminology or defaults and ensure parity in coverage for both Windows and Linux.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/environment/creation.md
...blob/main/articles/app-service/environment/creation.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page demonstrates a 'windows_first' bias by mentioning Windows Isolated v2 as the minimum charge for App Service plans in regional deployments, without referencing Linux equivalents or clarifying Linux support. There are no explicit Linux examples, nor is Linux parity discussed. However, there are no PowerShell-heavy examples, Windows tools, or missing Linux command-line instructions, as the guide is portal-focused.
Recommendations
- Clarify whether Linux-based App Service plans are supported in all deployment types, and if so, specify any differences in minimum charges or instance types for Linux.
- Where Windows-specific SKUs or terms are mentioned (e.g., 'Windows Isolated v2'), also mention the Linux equivalents or explicitly state if there are none.
- Add a section or note on Linux support and considerations for App Service Environment deployments.
- If possible, provide parity in examples, such as showing how to deploy both Windows and Linux web apps in the created environment.
- Review all references to ensure Linux users are not left with ambiguity regarding support, pricing, or configuration.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/environment/creation.md
...blob/main/articles/app-service/environment/creation.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page exhibits a subtle 'windows_first' bias by referencing Windows-specific App Service plan SKUs (e.g., 'Windows Isolated v2') before any mention of Linux equivalents. There are no explicit Linux examples, nor is there mention of Linux-specific deployment considerations or pricing, even though Azure App Service supports both Windows and Linux workloads. No PowerShell or CLI examples are present, but the only concrete SKU/pricing example is Windows-specific.
Recommendations
- Explicitly mention both Windows and Linux App Service plan SKUs and pricing models where relevant, especially in sections discussing minimum charges or deployment types.
- Add notes or examples for Linux-based App Service Environments, including any differences in deployment, configuration, or pricing.
- Ensure that screenshots and instructions are inclusive of both Windows and Linux scenarios, or clarify when a step or option is Windows-only.
- Where possible, provide parity in documentation for both operating systems, including references to Linux-specific documentation or considerations.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/tutorial-ai-agent-web-app-semantic-kernel-foundry-dotnet.md
...torial-ai-agent-web-app-semantic-kernel-foundry-dotnet.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation avoids explicit Windows bias by using cross-platform tools (Azure CLI, AZD, dotnet CLI) and recommending GitHub Codespaces for development. However, it does not mention or show any Linux-specific instructions, terminal environments, or deployment scenarios, nor does it acknowledge running locally on Linux or WSL. All command-line examples are generic and do not reference Windows-specific shells or tools, but there is a lack of explicit Linux parity or validation.
Recommendations
- Explicitly state that all steps and commands work on Linux, macOS, and Windows.
- Add a note or section confirming that the tutorial has been tested on Linux and macOS, not just Windows.
- Include screenshots or terminal output from a Linux shell (e.g., bash) to reinforce cross-platform compatibility.
- Mention that Codespaces provides a Linux-based environment, and clarify that users can also run the sample locally on their own Linux or macOS machines.
- If any step has OS-specific caveats (such as file paths or environment variable syntax), provide side-by-side examples for Windows (PowerShell/CMD) and Linux/macOS (bash/zsh).
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/environment/creation.md
...blob/main/articles/app-service/environment/creation.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page exhibits a subtle Windows bias by referencing 'Windows Isolated v2' as the minimum charge for regional deployments, without mentioning Linux equivalents or clarifying Linux support. No command-line examples are provided, but the only OS-specific reference is to Windows, and Linux is not mentioned in deployment or pricing contexts.
Recommendations
- Explicitly mention Linux support and pricing for App Service Environment v3, especially in sections discussing deployment types and minimum charges.
- If there are differences in features, pricing, or deployment steps between Windows and Linux, provide clear comparisons or links to relevant Linux documentation.
- Include examples or notes for both Windows and Linux where OS-specific behavior or options exist.
- Review all references to OS-specific SKUs (such as 'Windows Isolated v2') and clarify if Linux equivalents exist or if the information is Windows-only.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/environment/creation.md
...blob/main/articles/app-service/environment/creation.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page exhibits a subtle Windows bias by referencing 'Windows Isolated v2' as the minimum charge for App Service plans in regional deployments, without mentioning Linux equivalents or clarifying Linux support. No explicit Linux examples, tools, or deployment considerations are provided, and the only OS-specific reference is to Windows.
Recommendations
- Explicitly mention Linux support and pricing models for App Service Environment, especially in sections discussing minimum charges or instance types.
- Add clarifying statements or examples for both Windows and Linux deployments where relevant, such as supported runtimes or differences in configuration.
- Ensure parity in documentation by providing Linux-specific considerations, if any, or stating that the process is identical for Linux-based App Service plans.
- Avoid referencing only Windows SKUs or features unless there is a technical limitation, and if so, clearly state it.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/environment/creation.md
...blob/main/articles/app-service/environment/creation.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page exhibits a 'windows_first' bias by referencing Windows-specific SKUs (e.g., 'Windows Isolated v2') as the default or minimum charge in the regional deployment section, without mentioning Linux equivalents or clarifying Linux support. There are no explicit PowerShell or Windows-only tool examples, but the mention of Windows pricing and SKUs before any Linux context may suggest to readers that Windows is the primary or default platform.
Recommendations
- Explicitly mention Linux support and pricing/SKU details alongside Windows wherever applicable, especially in deployment and billing sections.
- Clarify whether the minimum instance charge applies to both Windows and Linux App Service plans, or provide Linux-specific details if different.
- Add examples or notes for Linux-based App Service Environments where relevant, to ensure parity and inclusivity.
- Review all references to platform-specific features or pricing to ensure both Windows and Linux users are equally informed.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/environment/creation.md
...blob/main/articles/app-service/environment/creation.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page exhibits a subtle 'windows_first' bias by referencing Windows-specific SKUs (such as 'Windows Isolated v2') as the default or minimum charge in the App Service plan, without mentioning Linux equivalents or clarifying Linux support. There are no explicit PowerShell examples or Windows-only tools, but the language and examples assume Windows as the primary platform, with no mention of Linux options or parity.
Recommendations
- Explicitly mention Linux support and available SKUs (e.g., 'Linux Isolated v2') where Windows SKUs are referenced.
- Clarify whether the minimum charge applies to both Windows and Linux App Service plans, or provide details for both.
- Add examples or notes for Linux-based deployments if there are differences or additional considerations.
- Ensure that screenshots, instructions, and terminology are platform-neutral or provide both Windows and Linux perspectives where relevant.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/environment/creation.md
...blob/main/articles/app-service/environment/creation.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page demonstrates a subtle Windows bias by referencing 'Windows Isolated v2' as the default/minimum charge in the 'regional deployment' section, without mentioning Linux equivalents or clarifying Linux support. There are no explicit Linux examples, nor is there mention of Linux-specific deployment considerations. However, the page does not provide any command-line examples (PowerShell, CLI, or otherwise), so it is not 'powershell_heavy' or missing Linux CLI examples. The bias is primarily in the ordering and defaulting to Windows terminology.
Recommendations
- Explicitly mention Linux support and pricing in the 'regional deployment' section, or clarify if the minimum charge applies to both Windows and Linux Isolated v2 plans.
- Where Windows-specific SKUs or terminology are used (e.g., 'Windows Isolated v2'), provide the Linux equivalent or state if there is none.
- Add a section or note about Linux compatibility and any differences in deployment or pricing.
- Ensure that any future examples (scripts, CLI, etc.) include both Windows (PowerShell) and Linux (Bash/Azure CLI) variants.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/environment/creation.md
...blob/main/articles/app-service/environment/creation.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page exhibits a subtle 'windows_first' bias. In the 'Deployment considerations' section, the minimum charge for the App Service plan is specifically described as 'one instance of Windows Isolated v2,' with no mention of Linux equivalents or pricing. No command-line examples (PowerShell, Bash, CLI) are present, but the only OS-specific reference is to Windows, and Linux is not mentioned at all in deployment or pricing contexts.
Recommendations
- Explicitly mention Linux support and pricing for App Service Environment, especially in the 'Deployment considerations' section.
- If there are differences in minimum charges or instance types for Linux, document them alongside Windows information.
- Add a section or note clarifying OS support (Windows and Linux) for App Service Environment v3.
- Where possible, provide parity in examples, terminology, and guidance for both Windows and Linux users.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/quickstart-python/stream-logs-azure-portal-2.md
...cludes/quickstart-python/stream-logs-azure-portal-2.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not display explicit Windows bias, as it avoids mentioning any OS-specific tools or commands. However, it also lacks any platform-specific guidance or examples, including for Linux, which could leave Linux users without clarity on whether the instructions are applicable to their environment.
Recommendations
- Clarify if the instructions are platform-agnostic or specify any OS-specific steps if needed.
- If there are differences in accessing the 'Log stream' feature or generating log messages on Linux vs. Windows, provide examples for both platforms.
- Explicitly state that the steps apply to all supported platforms, or add notes for Linux users if there are unique considerations.
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 in this excerpt, but it lacks any mention of Linux-specific considerations or alternative interfaces (such as CLI or configuration files) that Linux users might use, especially since App Service can be managed via both the Azure Portal and command-line tools on different platforms.
Recommendations
- Add equivalent instructions for managing configuration using the Azure CLI, which is cross-platform and commonly used on Linux.
- Mention that the Azure Portal UI is the same across platforms, but provide links or notes for users who prefer command-line or automation approaches.
- If there are any Linux-specific configuration differences, highlight them or provide a link to relevant documentation.
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 using a generic dialog interface without specifying platform-specific steps. However, it does not mention or provide examples for Linux environments, such as setting environment variables via the command line or configuration files, which are common on Linux.
Recommendations
- Add Linux-specific instructions, such as how to set SCM_DO_BUILD_DURING_DEPLOYMENT using the export command in bash or by editing configuration files.
- Include examples for both Windows (e.g., using set in Command Prompt or PowerShell) and Linux (e.g., using export or editing .env files).
- Clarify if the dialog is available on all platforms or provide alternative methods for platforms where it is not.
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. However, it does not mention or provide examples for setting this configuration via Linux command-line tools or scripts, which may be relevant for cross-platform users.
Recommendations
- Add examples for setting SCM_DO_BUILD_DURING_DEPLOYMENT using Linux shell commands (e.g., export, echo, or editing configuration files).
- Clarify whether the dialog is available on all platforms or provide alternative instructions for Linux users.
- Include parity in documentation by showing both Windows (e.g., PowerShell, GUI) and Linux (e.g., Bash, CLI) methods for setting environment variables.
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 provides instructions for obtaining Git credentials but does not include any platform-specific examples or commands. However, it implicitly assumes a generic workflow and does not mention Linux or provide Linux-specific guidance, which may leave Linux users uncertain about steps such as credential usage in their environment.
Recommendations
- Add explicit instructions or examples for both Windows (e.g., using PowerShell or Command Prompt) and Linux/macOS (e.g., using Bash) for cloning and pushing to the repository.
- Clarify that the instructions are platform-agnostic if that is the intent, or provide side-by-side examples for each major platform.
- Mention any differences in credential handling or command syntax between Windows and Linux environments.
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 provides generic instructions for accessing deployment credentials but does not include any platform-specific examples. There are no explicit Windows or Linux command-line examples, but the lack of Linux (or any OS-specific) guidance may leave Linux users without clear next steps for using these credentials.
Recommendations
- Add explicit examples for both Windows (e.g., using PowerShell or Command Prompt) and Linux (e.g., using Bash) to demonstrate how to use the credentials when pushing code.
- Include sample git commands for both platforms, showing how to input the credentials.
- Clarify any platform-specific differences in credential storage or usage, if applicable.
- Ensure parity in the order and depth of examples 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-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 SSH via the Azure portal's web interface, which is platform-agnostic. However, it does not provide any command-line examples (e.g., using native SSH clients on Linux or Windows), nor does it mention platform-specific tools or workflows. There is a lack of parity for users who may prefer or require CLI-based access, especially common in Linux environments.
Recommendations
- Add examples for accessing the App Service container via SSH from a terminal using the standard ssh command, including any prerequisites or authentication steps.
- Clarify whether the web-based SSH interface works identically across all platforms, and mention any platform-specific considerations if they exist.
- If there are PowerShell or Windows-specific methods, ensure equivalent Linux (bash) examples are provided.
- Explicitly mention that the instructions are platform-agnostic if that is the case, or provide links to platform-specific guides.