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 1676-1700 of 2121 flagged pages
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
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation page focuses exclusively on assessing ASP.NET web apps, which are traditionally associated with Windows environments. There are no explicit examples, commands, or tools mentioned for Linux-based .NET web apps. All referenced materials and linked tutorials assume a Windows-centric workflow, and there is no mention of Linux assessment tools or cross-platform considerations.
Recommendations
- Include explicit guidance or examples for assessing .NET web apps running on Linux, such as those hosted on Kestrel or using .NET Core.
- Mention and link to any Linux-compatible assessment tools or scripts, if available.
- Clarify whether the assessment process and recommendations apply equally to both Windows and Linux-based .NET web apps.
- Add a section or note addressing Linux-specific considerations, such as file system differences, service management, or dependency handling.
- Ensure parity in documentation by providing at least one Linux-based example or workflow alongside any Windows-centric instructions.
Create Pull Request
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-linux-open-ssh-session.md
...ticles/app-service/configure-linux-open-ssh-session.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation presents Windows container information before Linux, and the Windows section lacks parity with the Linux section: there are no command-line or Azure CLI examples for Windows containers, while Linux containers receive detailed CLI and SSH instructions. This may give the impression that Windows is prioritized or that Linux is more complex, and it leaves Windows users without equivalent guidance.
Recommendations
- Provide equivalent Azure CLI or PowerShell instructions for connecting to Windows containers, or explicitly state if such functionality is not supported.
- Present Linux and Windows instructions in parallel or in a more balanced manner, rather than always listing Windows first.
- If certain features (like CLI SSH access) are not available for Windows containers, clearly explain the limitation and suggest any available alternatives.
- Ensure that both Linux and Windows sections contain similar levels of detail, including troubleshooting tips, example outputs, and command-line usage where possible.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias by referencing the Windows deployment path (C:\home\site\wwwroot) as the default and only later mentioning the Linux equivalent. There are no Linux-specific examples or screenshots, and the Linux path is only mentioned in a note, not in the main instructional steps. No Linux command-line or tooling examples are provided.
Recommendations
- Present both Windows and Linux file paths side-by-side in the main instructions, not just in a note.
- Include explicit Linux examples (e.g., using /home/site/wwwroot in the step-by-step instructions and sample commands).
- If showing file paths or deployment locations, always show both Windows and Linux equivalents together.
- If referencing tools or commands, provide both Windows (PowerShell, CMD) and Linux (Bash, CLI) examples where relevant.
- Consider adding a table or section that summarizes platform-specific differences for clarity.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/deploy-intelligent-apps/deploy-intelligent-apps-linux-python-pivot.md
...ent-apps/deploy-intelligent-apps-linux-python-pivot.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by referencing Windows first in the quickstart links (e.g., 'flask,windows,azure-cli,...') and not providing any explicit Linux-specific instructions or examples. While the content is mostly OS-agnostic, there is a lack of parity in highlighting or supporting Linux environments, especially in setup and deployment steps.
Recommendations
- Ensure that quickstart and sample links include both Windows and Linux tabs or provide a neutral default.
- Explicitly mention that all steps are cross-platform, or provide Linux/macOS-specific instructions where relevant (e.g., for environment variable setup, file paths, or deployment).
- Add a section or note clarifying any OS-specific differences, even if minimal, to reassure Linux users.
- Where portal or CLI instructions are given, ensure parity in screenshots or command examples for both Windows and Linux terminals.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/tutorial-ai-integrate-azure-ai-agent-dotnet.md
...service/tutorial-ai-integrate-azure-ai-agent-dotnet.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation assumes the use of GitHub Codespaces and Azure App Service, which are cross-platform, but it lacks explicit Linux or non-Windows instructions or examples. All terminal commands are given in a generic form, but there is no mention of Linux-specific workflows, nor are there any references to Linux tools or environments. The documentation implicitly assumes a Windows/.NET development environment and does not provide parity guidance for Linux users.
Recommendations
- Explicitly mention that all commands work on Linux, macOS, and Windows, and clarify any OS-specific differences.
- Provide alternative instructions or notes for users developing on native Linux environments (e.g., Ubuntu) outside of Codespaces.
- Include examples of running the app and deploying from a local Linux terminal, not just Codespaces.
- Reference Linux package managers or tools (e.g., apt, snap) where relevant, especially for .NET SDK installation.
- Add troubleshooting tips for common Linux-specific issues (e.g., file permissions, environment variables).
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias by referencing the Windows deployment path (C:\home\site\wwwroot) first and providing a relative path example for Windows, while only later mentioning the Linux path and its requirements. There are no explicit Linux command-line or file system examples, and Linux-specific instructions are minimal and secondary.
Recommendations
- Present Linux and Windows instructions/examples side by side or in parallel sections.
- Provide explicit Linux file path examples (e.g., /home/site/wwwroot/auth.json) alongside Windows examples.
- Clarify platform-specific differences early and equally, rather than mentioning Linux as an afterthought.
- Include Linux command-line examples (e.g., using bash or Linux-native tools) where relevant.
- Avoid using only Windows-style paths (C:\...) in initial instructions; always show both formats.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-authentication-provider-aad.md
...s/app-service/configure-authentication-provider-aad.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing the Azure portal UI and omitting any command-line examples, such as Azure CLI, PowerShell, or Bash. There are no platform-specific instructions, but the absence of Linux or cross-platform command-line examples means Linux users are not directly supported. All examples and instructions assume use of the Azure portal, which is platform-agnostic but often associated with Windows workflows. No Linux-specific tools, shell commands, or deployment patterns are mentioned.
Recommendations
- Add Azure CLI examples for all configuration steps, including app registration, authentication provider setup, and application settings. Ensure these examples are cross-platform and runnable on Linux, macOS, and Windows.
- Where PowerShell is relevant, provide equivalent Bash or shell commands, or explicitly reference Azure CLI as the preferred cross-platform tool.
- Include notes or sections on how to perform key steps (such as setting application settings, managing secrets, or registering apps) using the command line on Linux systems.
- Reference automation and scripting options (e.g., ARM/Bicep templates, Terraform) that are platform-independent.
- Clarify that the Azure portal is accessible from any OS, but provide parity for users who prefer or require command-line or automated approaches, which are common in Linux environments.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-authentication-provider-github.md
...pp-service/configure-authentication-provider-github.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation focuses exclusively on configuring GitHub authentication via the Azure Portal UI, which is platform-agnostic but implicitly assumes a graphical interface more commonly associated with Windows environments. There are no command-line examples (such as Azure CLI or PowerShell), but also no Linux-specific or cross-platform terminal instructions. The absence of CLI-based or Linux-native configuration steps means Linux users do not see parity in guidance, and the documentation may feel Windows-centric by omission.
Recommendations
- Add Azure CLI examples for configuring GitHub authentication, which work cross-platform (Windows, Linux, macOS).
- Include instructions for configuring authentication using ARM templates or Bicep, which are platform-neutral.
- Explicitly mention that the Azure Portal can be accessed from any OS, and provide links to CLI documentation for users who prefer terminal-based workflows.
- If PowerShell examples are added in the future, ensure equivalent Azure CLI examples are provided alongside.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/deploy-intelligent-apps/deploy-intelligent-apps-linux-python-pivot.md
...ent-apps/deploy-intelligent-apps-linux-python-pivot.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias: in the initial quickstart and sample app links, the 'windows' tab is prioritized or included before Linux equivalents, and there are no explicit Linux-specific instructions or examples for environment setup, deployment, or command-line usage. While the main content is generally cross-platform (Python, Flask, Azure), there is a lack of parity in explicitly addressing Linux users, especially in setup and deployment steps.
Recommendations
- Ensure that all quickstart and sample app links include Linux tabs or examples, and do not default to 'windows' first.
- Explicitly mention Linux as a supported platform in setup and deployment instructions.
- Provide Linux-specific command-line examples (e.g., bash, export commands) alongside any Windows (PowerShell/cmd) examples.
- Include notes or sections for common Linux development environments (e.g., WSL, Ubuntu, CentOS) where relevant.
- Review all referenced documentation links to ensure Linux parity in their content and tab ordering.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-authentication-provider-aad.md
...s/app-service/configure-authentication-provider-aad.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively describes configuration steps using the Azure Portal UI and does not provide any command-line examples. There are no references to Windows-specific tools like PowerShell, but the absence of CLI examples (such as Azure CLI or Bash scripts) means Linux and cross-platform users lack parity. The documentation implicitly assumes a GUI workflow, which is more common on Windows, and does not address automation or scripting scenarios typical for Linux environments.
Recommendations
- Add Azure CLI examples for all major configuration steps, such as app registration, authentication provider setup, and permission assignment.
- Where possible, provide Bash script snippets alongside any UI instructions to support automation and Linux users.
- Explicitly mention that all steps can be performed on any OS using the Azure CLI or REST API, and link to relevant cross-platform guides.
- If PowerShell or Windows tools are referenced in related content, ensure equivalent Linux/Bash/Azure CLI alternatives are provided and linked.
- Include a section summarizing cross-platform options for managing authentication configuration, highlighting both GUI and CLI approaches.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-linux-open-ssh-session.md
...ticles/app-service/configure-linux-open-ssh-session.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page presents Windows containers first and describes their SSH access in a brief, positive manner ('require no modifications'), while the Linux section is more detailed but only provides CLI-based SSH instructions for Linux containers. There are no equivalent CLI or PowerShell instructions for Windows containers, and the browser-based SSH session is only mentioned as working for Windows, with no parity in command-line access. This creates a 'Windows first' impression and omits Linux parity for browser SSH and Windows parity for CLI SSH.
Recommendations
- Present Linux and Windows container instructions in parallel, rather than always listing Windows first.
- Provide explicit CLI or PowerShell instructions for accessing Windows containers via SSH, or clearly state if such access is not supported.
- Clarify whether browser-based SSH is available for Linux containers and, if so, provide instructions.
- If certain features are only available on one platform, explain the reason and suggest workarounds or alternatives for the other platform.
- Ensure that both Linux and Windows sections have equivalent depth and example coverage, including troubleshooting tips and sample commands.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-web-tutorial-custom-domain.md
.../app-service/app-service-web-tutorial-custom-domain.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides a troubleshooting step for clearing the DNS cache that only mentions the Windows-specific command ('ipconfig /flushdns') and does not provide equivalent instructions for Linux or macOS users. No PowerShell scripts or Windows-only tools are otherwise present, but the only explicit command-line example is Windows-specific, and no Linux or cross-platform alternatives are mentioned.
Recommendations
- When providing troubleshooting steps such as clearing DNS cache, include equivalent commands for Linux (e.g., 'sudo systemd-resolve --flush-caches' or 'sudo resolvectl flush-caches') and macOS (e.g., 'sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder').
- If mentioning OS-specific commands, group them together and clearly label them for each operating system.
- Review the documentation for other places where implicit Windows-first assumptions may exist and ensure parity by including Linux/macOS alternatives.
- Consider adding a note or section on cross-platform DNS troubleshooting to help all users.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias by referencing the Windows deployment path (C:\home\site\wwwroot) before mentioning the Linux equivalent, and by providing a detailed example path for Windows but only a brief note for Linux. There are no Linux-specific examples or step-by-step instructions, and the Linux path is only mentioned in a note, not in the main instructional flow.
Recommendations
- Provide Linux-specific examples alongside Windows examples, such as using '/home/site/wwwroot' in the main instructions and code snippets.
- Rephrase instructions to mention both Windows and Linux paths equally, or use platform-agnostic language where possible.
- Include a table or section explicitly comparing Windows and Linux behaviors and requirements for config file paths.
- Add step-by-step Linux deployment instructions or references, not just a note.
- Ensure that all examples and sample paths are provided for both platforms to improve parity and reduce confusion for Linux users.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/deploy-intelligent-apps/deploy-intelligent-apps-linux-python-pivot.md
...ent-apps/deploy-intelligent-apps-linux-python-pivot.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by referencing Windows first in the sample app quickstart link (with 'tabs=flask,windows,azure-cli,...'), and does not provide explicit Linux-specific or cross-platform deployment instructions or examples. While the core instructions are generally OS-agnostic (Python, Flask, environment variables), there is a lack of parity in showing Linux or WSL-specific commands, environment variable setup, or deployment flows, especially given the 'linux-related-content' tag.
Recommendations
- Provide explicit Linux/WSL/macOS instructions and examples alongside or before Windows ones, especially in quickstart links and deployment steps.
- Ensure that all referenced quickstarts and code tabs include Linux and macOS options, not just Windows.
- Add examples of setting environment variables and running the app on Linux (e.g., using export in Bash, systemd service setup, etc.).
- Include Linux-specific deployment guidance for Azure App Service (e.g., using Azure CLI from Bash, VS Code on Linux, or GitHub Actions from Linux runners).
- Review all links and ensure that Linux tabs are present and not omitted in favor of Windows.
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
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation references using a dialog to set deployment settings, which is typically a Windows or Azure Portal pattern, without providing equivalent command-line or Linux-native instructions. There are no examples for Linux users (e.g., using environment variables in bash or CLI commands).
Recommendations
- Provide equivalent instructions for setting SCM_DO_BUILD_DURING_DEPLOYMENT using the Azure CLI or in a Linux shell.
- Include examples for both Windows (PowerShell/cmd) and Linux (bash) environments.
- Clarify whether the 'dialog' refers to the Azure Portal UI, and if so, link to CLI-based alternatives for cross-platform users.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/networking-features.md
.../blob/main/articles/app-service/networking-features.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in the 'Hybrid Connections' section, where it specifies that the required relay agent (Hybrid Connection Manager) must be installed on a Windows Server 2012 or newer host. There is no mention of Linux support or alternatives for this component. No command-line examples (PowerShell, Bash, etc.) are present, but the only explicit tooling requirement is Windows-based. This omission may mislead Linux users or limit their perceived options.
Recommendations
- Clarify whether Hybrid Connection Manager is available for Linux, and if so, provide installation and usage instructions for Linux hosts.
- If Hybrid Connection Manager is Windows-only, explicitly state this limitation and suggest alternative approaches for Linux environments (such as VPN, VNet Integration, or other supported connectivity methods).
- Wherever platform-specific requirements exist, present both Windows and Linux options (or note the lack thereof) to ensure parity and transparency.
- Consider including examples or references for Linux-based deployments and tooling throughout the documentation, especially in sections discussing agent installation or network configuration.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/quickstart-custom-container.md
...in/articles/app-service/quickstart-custom-container.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page presents Windows-related pivots (Visual Studio, PowerShell, CLI, Azure Portal) before Linux equivalents, and includes a dedicated PowerShell section for Windows but not for Linux. This ordering and tooling focus may suggest a Windows-first bias and heavier emphasis on Windows-native tools.
Recommendations
- Reorder the pivots so that Linux and Windows options are presented in a parallel or alternating fashion, or group them together for parity.
- Add a Linux-specific CLI or shell example if not already present, to match the PowerShell coverage for Windows.
- Ensure that Linux tools and workflows (such as Bash, Linux CLI, or VS Code on Linux) are given equal prominence and detail as Windows tools.
- Consider including a table or matrix at the top summarizing all platform/tool combinations for quick navigation and parity.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/manage-scale-up.md
...docs/blob/main/articles/app-service/manage-scale-up.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page focuses exclusively on scaling via the Azure Portal UI and does not provide any command-line examples. Where pricing details are mentioned, the link points to the Windows-specific App Service pricing page. There are no examples or references to Linux-specific workflows, tools, or parity considerations. This may implicitly bias the documentation toward Windows users or those deploying Windows-based apps, while Linux users are not directly addressed.
Recommendations
- Include CLI-based examples for scaling up App Service plans using Azure CLI (az), which is cross-platform and commonly used on Linux.
- When linking to pricing details, provide both Windows and Linux App Service pricing pages, or clarify the differences.
- Explicitly mention that the scaling process applies to both Windows and Linux App Service plans, and note any differences if they exist.
- Add a section or note about scaling App Service plans for Linux-based apps, including any relevant considerations or links.
- If screenshots are OS-specific, consider including Linux-relevant visuals or clarifying that the UI is the same regardless of OS.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/invoke-openapi-web-app-from-azure-ai-agent-service.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/invoke-openapi-web-app-from-azure-ai-agent-service.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a bias toward Windows by exclusively referencing Azure App Service (which is often associated with Windows hosting, though it can host Linux), and by omitting any mention of Linux-specific workflows, tools, or deployment patterns. All command-line instructions use Azure Developer CLI (azd), which is cross-platform, but there are no explicit Linux shell or deployment examples, nor any mention of Linux-specific considerations. The tutorial assumes the use of the Azure Portal and Codespaces, which are cross-platform, but does not address Linux environments or tools (e.g., SSH, systemd, Linux file paths, or troubleshooting on Linux-based App Service plans). There are no PowerShell-specific commands, but the absence of Linux-specific content or examples constitutes a subtle bias.
Recommendations
- Explicitly mention that Azure App Service supports both Windows and Linux hosting plans, and clarify which is being used in the tutorial.
- Include Linux-specific notes or troubleshooting steps, such as how to access logs or environment variables via SSH on Linux App Service.
- Provide examples of deploying and managing the app from a Linux terminal, including any differences in file paths, permissions, or environment variable configuration.
- If the sample app or infrastructure is platform-agnostic, state this clearly to reassure Linux users.
- Add a section or callout addressing any differences in behavior or setup between Windows and Linux App Service plans, especially for .NET/Blazor apps.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/manage-create-arc-environment.md
.../articles/app-service/manage-create-arc-environment.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for most steps, but consistently presents Bash (Linux/macOS) examples before PowerShell (Windows) ones. However, PowerShell examples are present for every step, which is not always the case in cross-platform docs. There is no exclusive use of Windows tools or patterns, and Linux examples are not missing. The use of Azure CLI and kubectl is cross-platform, but the presence of PowerShell examples throughout may indicate a slight Windows bias, especially since PowerShell is not the default shell on most non-Windows systems.
Recommendations
- Clarify in the introduction that both Linux/macOS (Bash) and Windows (PowerShell) users are supported, and explain how to choose the appropriate tab.
- Consider including a note that PowerShell Core is available cross-platform, but Bash is the default on most Linux/macOS systems.
- Where possible, provide a single, unified script with cross-platform variable syntax, or explicitly mention any differences in environment variable handling between Bash and PowerShell.
- Ensure that any references to file paths, environment variables, or shell-specific behavior are clearly marked as Bash- or PowerShell-specific.
- If possible, add a short section or callout for users on WSL (Windows Subsystem for Linux), as this is a common cross-platform scenario.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-authentication-authorization.md
...s/app-service/overview-authentication-authorization.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation presents the Windows (IIS module) architecture before the Linux/containers architecture and references IIS (a Windows-specific technology) without mentioning equivalent Linux web server modules or patterns. There are no explicit Linux command-line or configuration examples, but the architecture section does acknowledge Linux/container deployments. No PowerShell or Windows-only CLI examples are present, and the only CLI examples use the cross-platform Azure CLI.
Recommendations
- Present Linux/container architecture before or alongside Windows/IIS to avoid the impression of Windows primacy.
- When mentioning IIS modules for Windows, also mention the equivalent Linux web server context (e.g., NGINX/Apache modules or reverse proxy patterns), or clarify that the Linux/container implementation uses a sidecar/ambassador pattern.
- Include Linux-specific operational notes or troubleshooting tips where relevant (e.g., log locations, integration caveats).
- Ensure that all examples, especially CLI commands, are cross-platform (which is already the case here), and explicitly state that the Azure CLI commands work on Windows, Linux, and macOS.
- If referencing file-based configuration, provide example file paths or commands for both Windows and Linux environments.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/migrate-gateway-based-vnet-integration.md
.../app-service/migrate-gateway-based-vnet-integration.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides command-line examples for Azure CLI and Azure PowerShell, with PowerShell examples given equal prominence to CLI. However, there is a subtle Windows bias: PowerShell is a Windows-centric tool, and its inclusion as a primary example (alongside CLI) can be seen as favoring Windows users. Additionally, in the feature comparison table, 'Platform support' lists 'Windows, Linux, Windows containers' for regional integration but only 'Windows' for gateway-based, which is accurate but may reinforce a Windows-centric view. No Linux-specific shell (e.g., Bash) or scripting examples are given, and there is no mention of Linux-native tools or patterns. The documentation does not provide Linux-first or Linux-specific guidance, and PowerShell is not as commonly used on Linux as on Windows.
Recommendations
- Add explicit Bash shell examples (in addition to Azure CLI), showing commands as they would be run in a typical Linux environment.
- Clarify that Azure CLI commands are cross-platform and can be run in Bash, Cloud Shell, or Windows Command Prompt.
- Where PowerShell is shown, consider adding a note that PowerShell Core is available on Linux, or provide Bash alternatives for scripting scenarios.
- In the prerequisites and migration steps, mention that all steps can be performed from Linux or macOS using Azure CLI.
- Consider reordering examples to show Azure CLI (Bash) first, then PowerShell, to avoid a 'Windows first' impression.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/routine-maintenance.md
.../blob/main/articles/app-service/routine-maintenance.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by referencing 'local cache for Windows apps' as a mitigation for cold starts, without mentioning an equivalent or alternative for Linux-based App Service apps. There are no Linux-specific examples or guidance, and the only platform-specific advice is for Windows. No PowerShell or Windows-only tools are mentioned, but the omission of Linux parity is notable.
Recommendations
- Provide equivalent guidance or explicitly state options for Linux-based App Service apps regarding cold start mitigation (e.g., mention if local cache is available or suggest alternatives).
- Include examples or notes for both Windows and Linux App Service environments where platform-specific features or behaviors are discussed.
- Review all platform-specific recommendations to ensure Linux users are not left without guidance or workarounds.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/quickstart-java.md
...docs/blob/main/articles/app-service/quickstart-java.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page presents separate pivots for Java app deployment on Azure App Service, with Tomcat (Linux) and Java SE/JBoss (Windows) options. However, for Java SE and JBoss, only Windows-based instructions/examples are provided, while Linux-based equivalents are missing. This creates a bias by prioritizing Windows deployment scenarios for these runtimes and omitting Linux guidance.
Recommendations
- Add Linux-based quickstart pivots/examples for Java SE and JBoss runtimes, ensuring parity with the Windows instructions.
- Ensure that for each Java runtime (Tomcat, Java SE, JBoss), both Windows and Linux deployment options are clearly documented and equally accessible.
- Review included markdown files to verify that Linux instructions are present and up-to-date for all supported runtimes.
- Consider presenting Linux and Windows options side-by-side or in a consistent order to avoid implicit prioritization.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/samples-terraform.md
...cs/blob/main/articles/app-service/samples-terraform.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page provides Terraform samples for Azure App Service, but the listed examples are exclusively focused on Windows-based App Service scenarios. There are no examples for Linux-based App Service deployments, and the scripts specifically mention 'Windows web app' and 'Windows container app' without Linux equivalents.
Recommendations
- Add Terraform sample scripts for creating and managing Linux-based App Service apps.
- Ensure that for every Windows-specific example, there is a parallel Linux example (e.g., 'Create an Azure Linux web app with a backup').
- Explicitly mention both Windows and Linux options in script descriptions and titles where applicable.
- Consider a table structure that clearly distinguishes between Windows and Linux scenarios to help users find relevant samples for their platform.