Azure Docs
14605
Total Pages
12420
Linux-Friendly Pages
2185
Pages with Bias
15.0%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
2185 issues found
Showing 101-125 of 2185 flagged pages
Azure Docs
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
High Priority
View Details →
Detected Bias Types
Windows First
Missing Windows Example
Linux Tools
Summary
The documentation page presents both Linux and Windows container SSH access, but the detailed, step-by-step instructions and CLI examples are provided only for Linux containers. Windows containers are mentioned first, but lack any equivalent technical walkthrough or command-line guidance. The Linux section includes Azure CLI and SSH command examples, while Windows users are told only that browser SSH is supported, with no further detail or parity in tooling or troubleshooting.
Recommendations
- Add equivalent, step-by-step instructions for accessing SSH in Windows containers, including any available command-line tools, PowerShell examples, or troubleshooting steps.
- If CLI or remote SSH is not supported for Windows containers, explicitly state this and provide alternative workflows or tools for Windows users.
- Balance the order of presentation: if Windows is mentioned first, ensure Linux and Windows sections have similar depth and structure.
- Include screenshots, command outputs, and example sessions for Windows containers, matching the detail provided for Linux.
- If certain features are Linux-only, clearly label them as such and provide guidance for Windows users.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/deployment-environments/how-to-create-access-environments.md
...ment-environments/how-to-create-access-environments.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation is generally cross-platform in its use of the Azure CLI, but it introduces a Windows/Powershell bias in the example for passing parameters to the CLI. The example uses Powershell variable assignment syntax ($params = ...) and single quotes for JSON, which is not valid in Bash or other Unix shells. There are no equivalent Linux/Bash examples, and the only variable assignment shown is in Powershell style, which may confuse Linux/macOS users.
Recommendations
- Provide both Windows (Powershell) and Linux/macOS (Bash) examples for passing parameters to the Azure CLI, especially for JSON strings and file references.
- Explicitly note shell differences when showing variable assignment or command usage that is shell-dependent.
- Use cross-platform compatible syntax where possible, or clearly label examples as 'Windows (Powershell)' and 'Linux/macOS (Bash)'.
- Add a Bash example for parameter passing, e.g., params='{"name": "firstMsi", "location": "northeurope"}' and use $params in the CLI command.
- Review for any other CLI usage patterns that may differ between shells and ensure parity in documentation.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/configure-custom-container.md
...in//articles/app-service/configure-custom-container.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific sections and details (such as parent images, memory/CPU customization, and diagnostic access) are often presented first or in greater detail. PowerShell examples are provided alongside Bash, but sometimes Windows-specific tools (like Kudu, IIS, .NET Framework details) are emphasized. Some advanced configuration and diagnostic steps are more thoroughly documented for Windows containers, while Linux equivalents are less detailed or missing.
Recommendations
- Ensure Linux and Windows instructions/examples are presented with equal prominence, and alternate which comes first in sections.
- Where PowerShell is shown, always provide a Bash/Linux CLI equivalent, and ensure both are equally detailed.
- Expand Linux-specific guidance for advanced topics (e.g., memory/CPU limits, diagnostic access, health checks) to match Windows coverage.
- Add Linux-native troubleshooting and diagnostic tool references (e.g., journalctl, docker logs, Linux process inspection) where appropriate.
- Review all 'zone pivot' sections to ensure parity in depth and clarity between Windows and Linux content.
- Where Windows-specific tools (like Kudu) are mentioned, clarify Linux alternatives or note cross-platform applicability.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/configure-basic-auth-disable.md
...//articles/app-service/configure-basic-auth-disable.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias by referencing Windows-specific tools (such as Web Deploy and MSBuild) without mentioning Linux equivalents or alternatives. Visual Studio deployment is discussed without clarifying cross-platform support. There are no explicit Linux or macOS command-line examples, and some deployment scenarios (like Web Deploy) are implicitly Windows-centric. However, the use of Azure CLI and Bash Cloud Shell is cross-platform, and there is no heavy use of PowerShell or exclusive Windows command syntax.
Recommendations
- When mentioning tools like Web Deploy and MSBuild, clarify their platform support and suggest Linux/macOS alternatives (e.g., zip deploy, Kudu REST API, or Azure CLI).
- For Visual Studio deployment, note whether cross-platform IDEs (like Visual Studio Code or JetBrains Rider) are supported and provide guidance for Linux/macOS users.
- Add explicit Linux/macOS command-line examples where relevant, especially for deployment and troubleshooting steps.
- Where possible, avoid assuming the use of Windows agents in Azure Pipelines, or provide equivalent instructions for Linux agents.
- In tables and lists, avoid listing Windows-centric methods first unless they are the only supported option; otherwise, present cross-platform options with equal prominence.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/deploy-container-azure-pipelines.md
...ticles/app-service/deploy-container-azure-pipelines.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily focused on deploying Windows containers, with all examples and instructions tailored to Windows environments. It specifies the use of 'windows-latest' build agents, references a Windows app as the starting point, and only demonstrates deployment to Windows-based App Service. There are no Linux container examples, nor mention of Linux build agents or App Service for Linux, despite Azure Pipelines supporting both platforms.
Recommendations
- Provide parallel examples for deploying Linux containers, including YAML snippets using 'ubuntu-latest' or other Linux build agents.
- Mention and demonstrate how to deploy to App Service for Containers (Linux) as well as Windows.
- Clarify in the prerequisites that the instructions are Windows-specific, or broaden the scope to include Linux scenarios.
- Include guidance on how to adapt the pipeline for Linux-based .NET applications and Dockerfiles.
- Balance the order of presentation so that Linux and Windows options are given equal prominence.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/scenario-secure-app-access-microsoft-graph-as-app.md
...e/scenario-secure-app-access-microsoft-graph-as-app.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides installation instructions for the required NuGet packages using both the .NET Core CLI and the Visual Studio Package Manager Console (PowerShell-based), but it lists the Visual Studio/PowerShell method second. There is no explicit mention of Linux or cross-platform development environments beyond the .NET CLI, and there are no Linux-specific instructions or examples. The focus on Visual Studio and PowerShell may implicitly bias the documentation toward Windows users.
Recommendations
- Explicitly mention that the .NET Core CLI commands work on Linux, macOS, and Windows, and recommend it as the primary cross-platform method.
- Add a section or note for Linux/macOS users, clarifying that Visual Studio and the Package Manager Console are Windows-specific, and suggest alternatives such as Visual Studio Code or JetBrains Rider.
- Provide terminal commands for Linux/macOS environments (e.g., bash/zsh) where appropriate.
- Ensure parity in tooling instructions by not assuming Visual Studio is the default IDE, and by including cross-platform editor/IDE options.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dev-box/concept-dev-box-architecture.md
...main//articles/dev-box/concept-dev-box-architecture.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation for Microsoft Dev Box architecture demonstrates a Windows-centric bias. It exclusively references Windows management tools and patterns (such as Microsoft Intune, Windows device management, and Windows-specific configuration profiles), and does not mention Linux or provide examples for Linux-based development environments. There is no guidance for Linux VM images, Linux device management, or cross-platform developer scenarios.
Recommendations
- Include explicit references to Linux support in Dev Box, if available, such as provisioning Linux-based dev boxes or using Linux VM images.
- Provide examples or sections on managing Linux dev boxes, including integration with Linux management tools (e.g., Ansible, SSH, Linux configuration management).
- Clarify whether Microsoft Intune or other management tools can be used with Linux dev boxes, or suggest alternatives for Linux device management.
- Add guidance for cross-platform development scenarios, including how to connect to dev boxes from Linux or macOS clients.
- Ensure parity in documentation structure by presenting Linux options and tools alongside Windows ones, rather than focusing solely on Windows.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/app-service-migration-discover-net.md
...cles/app-service/app-service-migration-discover-net.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively discusses discovery of ASP.NET web apps hosted on IIS web servers within VMware environments, which are Windows-specific technologies. There is no mention of Linux-based web servers (such as Apache or Nginx), nor are there examples or guidance for discovering .NET apps running on Linux. All discovery capabilities and tooling referenced are tailored to Windows environments, indicating a strong Windows bias.
Recommendations
- Include information and examples for discovering .NET web apps hosted on Linux servers (e.g., Kestrel, Apache, Nginx).
- Mention whether Azure Migrate supports agentless or agent-based discovery for Linux-based .NET deployments, and provide relevant instructions if available.
- Add parity in documentation by referencing Linux-compatible tools and migration paths alongside Windows/IIS.
- Clarify in the introduction whether the guidance is Windows-only, or expand the scope to cover cross-platform .NET app discovery.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/routine-maintenance-downtime.md
...//articles/app-service/routine-maintenance-downtime.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a Windows-first bias, especially in the 'Application Initialization (AppInit)' section, where Windows/IIS mechanisms are described in detail and Linux alternatives are only briefly mentioned. Windows-specific tools and modules (IIS Application Initialization, .NET Core stdout logging) are referenced without equivalent Linux-focused guidance or examples. Linux features are mentioned as afterthoughts, with minimal explanation or practical examples, and there are no Linux shell or configuration examples provided.
Recommendations
- Provide equal detail for Linux features, such as expanding on how to use WEBSITE_WARMUP_PATH with concrete examples and best practices.
- Include Linux-specific examples (e.g., shell commands, configuration snippets) alongside Windows/IIS examples.
- Reference Linux-native tools and patterns for logging and initialization, such as systemd, NGINX/Apache warmup strategies, or stdout/stderr log handling.
- Ensure that Linux guidance is presented with parity to Windows, both in order and in technical depth.
- Where a feature is Windows-only, clearly state this and offer Linux alternatives or workarounds where possible.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/api-management/virtual-network-reference.md
...//articles/api-management/virtual-network-reference.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows Update
Windows Defender
Kms Windows
Missing Linux Example
Summary
The documentation page includes several references and configuration requirements specific to Windows environments, such as KMS activation for Windows VMs, Windows Update, and Windows Defender endpoints. There are no equivalent mentions or guidance for Linux VMs or Linux-specific tooling, nor are there examples or notes about Linux-specific network requirements. This creates a Windows-centric bias, with Linux scenarios and needs not addressed.
Recommendations
- Add a section or notes addressing network requirements for Linux VMs in the VNet, such as package repository access (e.g., Ubuntu, Red Hat, CentOS mirrors) and Linux security updates.
- Include guidance on configuring outbound rules for Linux update endpoints (e.g., security.ubuntu.com, mirrors for yum/dnf/apt) alongside Windows Update.
- If mentioning KMS for Windows, also mention any licensing or activation considerations for Linux (if applicable), or explicitly state that no such configuration is needed for Linux.
- Provide parity in examples and troubleshooting notes for both Windows and Linux VM scenarios.
- Review all references to Windows-specific tools and ensure Linux equivalents are either mentioned or the documentation clarifies when they are not required.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/app-service-web-nodejs-best-practices-and-troubleshoot-guide.md
...rvice-web-nodejs-best-practices-and-troubleshoot-guide.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Powershell Heavy
Summary
The documentation is heavily focused on Windows environments, specifically Azure App Service on Windows with iisnode. All configuration examples, troubleshooting steps, and tool references are Windows-centric, with no mention of Linux equivalents or cross-platform considerations. Tools and paths (e.g., node.exe, web.config, named pipes, Win32 error codes, d:\ paths, IIS, PowerShell, CMD) are specific to Windows. There are no Linux or cross-platform examples, and Linux troubleshooting or deployment patterns are not discussed.
Recommendations
- Add equivalent sections or notes for Node.js applications running on Azure App Service for Linux, including differences in configuration and troubleshooting.
- Provide Linux-specific examples (e.g., using environment variables, file paths, and process management tools relevant to Linux).
- Include Linux command-line examples (bash, sh) alongside or before Windows CMD/PowerShell examples.
- Mention Linux logging and diagnostic file locations and tools (e.g., /var/log, journalctl, pm2 logs).
- Clarify which recommendations and settings are Windows-only and provide alternatives or links for Linux users.
- Reference Linux-native process managers (e.g., PM2, systemd) and configuration files (e.g., .env, ecosystem.config.js) where appropriate.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/deploy-authentication-types.md
...n//articles/app-service/deploy-authentication-types.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-centric tools and workflows (such as Azure PowerShell, Visual Studio, and migration assistants for PowerShell scripts) and referencing them before or more prominently than cross-platform or Linux-native alternatives. There is a lack of explicit Linux command-line examples, and Linux deployment tools or patterns (such as Bash scripting, Linux-native CI/CD tools, or SSH/SCP/SFTP workflows) are not mentioned. Visual Studio and PowerShell are highlighted, while Linux-first developer experiences are underrepresented.
Recommendations
- Add explicit Linux/Bash command-line examples alongside PowerShell and Windows tool references, especially for common deployment scenarios.
- Include references to Linux-native tools and workflows (e.g., Bash scripts, SCP/SFTP, rsync, or Linux-based CI/CD pipelines) where appropriate.
- Ensure parity in documentation by providing Visual Studio Code examples for Linux/Mac users, not just Visual Studio (which is Windows-centric).
- Mention cross-platform alternatives before or alongside Windows-specific tools, rather than after.
- Highlight the use of Azure CLI (which is cross-platform) with Linux shell examples, not just as a generic tool.
- Where PowerShell is referenced, note that PowerShell Core is available cross-platform, and provide examples for both Windows PowerShell and PowerShell Core on Linux.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/app-service-web-tutorial-dotnet-sqldatabase.md
...service/app-service-web-tutorial-dotnet-sqldatabase.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily oriented toward Windows and Visual Studio users, with all instructions, screenshots, and tooling based on the Windows platform. There are no Linux or cross-platform alternatives provided for development, deployment, or database management. The use of Visual Studio, SQL Server Object Explorer, and PowerShell/Package Manager Console commands further reinforces a Windows-centric workflow, and there are no mentions of equivalent Linux tools or command-line alternatives.
Recommendations
- Add instructions for developing and deploying the ASP.NET app using cross-platform tools such as Visual Studio Code, the .NET CLI, and Azure CLI.
- Provide Linux/macOS-specific steps for tasks such as publishing the app, configuring Azure resources, and managing the SQL database.
- Include examples using Azure CLI and/or Bash scripts for database setup and managed identity configuration, rather than only PowerShell and Visual Studio GUI.
- Mention and demonstrate how to use cross-platform SQL clients (e.g., Azure Data Studio, sqlcmd) for database management.
- Ensure screenshots and walkthroughs are not exclusively tied to Windows/Visual Studio, and provide alternative visuals or text-based instructions for non-Windows environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/configure-language-java-deploy-run.md
...cles/app-service/configure-language-java-deploy-run.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation generally provides parity between Windows and Linux for most tasks, but there are several areas where a Windows bias is evident. Windows examples or tools (such as Kudu, FTPS, and web.config) are sometimes mentioned first or exclusively, and some instructions (like using Kudu's Process Explorer or Debug Console) are specific to Windows without clear Linux equivalents. There are also sections where Windows-specific tools or patterns are referenced without always providing Linux alternatives or highlighting Linux-native troubleshooting approaches.
Recommendations
- Ensure that for every Windows-specific tool or workflow (e.g., Kudu, FTPS, web.config), a Linux equivalent is provided or clearly stated if not available.
- When describing steps that differ between platforms, alternate the order (sometimes Linux first) or present both together, rather than defaulting to Windows-first.
- Expand Linux troubleshooting and management sections to include more native Linux tools and workflows (e.g., using SSH, Linux process management, log viewing with tail/less, etc.).
- Where Windows portal or Kudu instructions are given, provide explicit Linux container alternatives (e.g., using SSH and Linux commands to find PIDs, manage files, etc.).
- Review all examples to ensure that both Linux and Windows users can follow the documentation end-to-end without needing to infer missing steps for their platform.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/configure-ssl-certificate.md
...ain//articles/app-service/configure-ssl-certificate.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. While it does provide some cross-platform guidance (notably OpenSSL commands for certificate handling), it frequently references Windows-specific tools (IIS, Certreq.exe), provides PowerShell examples alongside Azure CLI but not Bash or Linux-native scripting, and lists Windows/container limitations before Linux ones. There are no explicit Linux GUI or command-line examples for certificate management, and automation examples are limited to Azure CLI and PowerShell, omitting Bash or Linux-native approaches.
Recommendations
- When referencing certificate export or creation, provide Linux-native alternatives (e.g., using OpenSSL on Linux) before or alongside Windows tools like IIS or Certreq.exe.
- For automation, include Bash shell script examples or at least mention that Azure CLI commands work cross-platform, and provide explicit Linux/Bash usage where possible.
- When listing platform-specific limitations or capabilities (e.g., outbound calls with private CA client certificates), clearly state Linux support status and provide parity in explanations.
- Avoid listing Windows/PowerShell examples before Linux equivalents; alternate or group by platform.
- Add a section or callout for Linux users, summarizing the typical workflow and tools they would use for certificate management in Azure App Service.
- Where screenshots or UI steps are shown, clarify if the experience is identical on Linux-hosted apps or note any differences.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/app-service-asp-net-migration.md
.../articles/app-service/app-service-asp-net-migration.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page demonstrates a strong Windows bias. All migration tools and examples focus exclusively on migrating from Windows environments, specifically IIS servers, and use Windows-specific tools such as the App Service Migration Assistant (MSI installer) and PowerShell scripts. There are no examples or guidance for migrating .NET apps from Linux environments, nor are Linux-native tools or command-line examples provided. The documentation repeatedly references Windows containers and IIS, with no mention of Apache, Nginx, or Linux-based hosting scenarios.
Recommendations
- Add equivalent migration guidance and tooling for .NET apps hosted on Linux (e.g., Apache, Nginx, Kestrel).
- Provide Linux shell (bash) script examples alongside PowerShell for discovery, assessment, and migration.
- Include references to Linux-native tools or workflows for .NET app migration.
- Clarify in each tool description whether Linux is supported, and if not, provide alternative recommendations.
- Add a section or FAQ addressing migration from common Linux environments and how to approach those scenarios.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/app-service-configure-premium-v4-tier.md
...s/app-service/app-service-configure-premium-v4-tier.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias by prioritizing Windows terminology and examples. Windows SKUs are listed before Linux, and Azure PowerShell is given equal prominence to Azure CLI, despite CLI being more cross-platform. There are no Linux shell or scripting examples, and the documentation refers to Windows-specific deployment scenarios and tools without providing equivalent Linux guidance.
Recommendations
- Present Linux and Windows options in parallel, or alternate which is listed first to avoid implicit prioritization.
- Include Linux shell (bash) scripting examples alongside PowerShell, especially in automation sections.
- Clarify when instructions or features are Windows-only, and provide Linux alternatives or workarounds where possible.
- Expand automation guidance to include Linux-native tools and scripting environments.
- Ensure that screenshots and UI instructions are not Windows-centric, or provide Linux-specific visuals if the experience differs.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/app-service-best-practices.md
...in//articles/app-service/app-service-best-practices.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page shows subtle Windows bias, particularly in the Node.js section, where it references iisnode (a Windows-specific module) as a configuration point for Node.js apps. There is no mention of Linux equivalents or guidance for Linux-based Node.js hosting (such as PM2 or NGINX, except for a brief PM2 mention in a different context). The configuration example for auto-healing refers to web.config, which is a Windows/IIS configuration file, without mentioning Linux alternatives. Linux-specific patterns, tools, or configuration files are not discussed or are mentioned secondarily, if at all.
Recommendations
- Provide Linux-specific configuration guidance alongside or before Windows/IIS examples (e.g., mention process.json or ecosystem.config.js for PM2, or NGINX configuration for Linux-based Node.js apps).
- When referencing iisnode or web.config, explicitly state that these apply to Windows App Service plans, and provide equivalent Linux guidance (such as app settings or startup scripts).
- Ensure all examples (such as auto-healing, memory dumps, or scaling) include both Windows and Linux approaches, or clarify platform applicability.
- Balance tool recommendations: if mentioning iisnode, also mention PM2, NGINX, or other common Linux process managers.
- Add explicit notes or callouts when a feature or configuration is platform-specific.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/configure-language-nodejs.md
...ain//articles/app-service/configure-language-nodejs.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias. Windows instructions and tools (such as IISNode, web.config, and PowerShell) are often mentioned first or exclusively, with some features (like web.config troubleshooting and PowerShell instrumentation) described only for Windows. Linux-specific instructions are present but sometimes less detailed or appear after Windows content. Some advanced configuration and troubleshooting scenarios are more thoroughly covered for Windows users.
Recommendations
- Ensure Linux and Windows instructions/examples are presented with equal prominence, or alternate which platform appears first in each section.
- Where a Windows tool (e.g., web.config, IISNode, PowerShell) is mentioned, provide the Linux equivalent or explicitly state if not applicable.
- Expand Linux troubleshooting and configuration sections to match the depth of Windows coverage (e.g., provide more details on Linux-specific errors or configuration files).
- For instrumentation and monitoring (e.g., Application Insights), provide Linux CLI or Bash examples alongside PowerShell instructions.
- Audit all sections for parity—ensure that every Windows-specific example or note has a Linux counterpart, or clearly indicate platform limitations.
- Consider adding a summary table at the top that links directly to both Windows and Linux instructions for each major task.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/app-service-configure-premium-v3-tier.md
...s/app-service/app-service-configure-premium-v3-tier.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a mild Windows bias. In the 'Premium V3 availability' section, Windows SKU availability is listed before Linux, and the Linux command is presented as a variant of the Windows command. In the automation section, Azure PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, despite CLI being cross-platform. There are no Linux shell (bash) examples, and the use of PowerShell may imply a Windows-first audience. The portal UI instructions do not clarify platform differences, and there is no mention of Linux-specific considerations or parity.
Recommendations
- Present Linux and Windows examples in parallel, or alternate which comes first to avoid implicit prioritization.
- Include bash or shell script examples for automation, not just Azure CLI and PowerShell.
- Clarify in the portal instructions if there are any platform-specific differences or considerations.
- When referencing Azure PowerShell, note its cross-platform availability, but also highlight that Azure CLI is often preferred for Linux users.
- Explicitly state that all features and instructions apply equally to Linux and Windows App Service plans, or note any exceptions.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/deploy-ftp.md
...ure-docs/blob/main//articles/app-service/deploy-ftp.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a moderate Windows bias. While it covers Azure CLI (cross-platform) and PowerShell (Windows-centric), it prioritizes Windows tools and patterns in several areas. The FTP client examples list Visual Studio and WinSCP (both Windows-focused) before Cyberduck (cross-platform), and there are no explicit Linux command-line FTP client examples (such as lftp, ncftp, or the standard ftp command). Troubleshooting and connection examples reference WinSCP documentation, and there is no mention of Linux-native tools or workflows. No Linux shell (bash) or Mac-specific guidance is provided.
Recommendations
- Include explicit Linux and macOS command-line FTP/S client examples (e.g., lftp, ncftp, curl, or the standard ftp command) alongside PowerShell and Azure CLI.
- List cross-platform or Linux-native FTP clients (e.g., FileZilla, lftp) before or alongside Windows-specific tools like Visual Studio and WinSCP.
- Provide sample Linux shell commands for connecting and uploading files via FTP/S.
- Reference documentation or screenshots for Linux and macOS FTP clients in troubleshooting sections.
- Ensure that all steps and screenshots are platform-neutral or provide platform-specific tabs (Windows, Linux, macOS) where appropriate.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/deploy-continuous-deployment.md
...//articles/app-service/deploy-continuous-deployment.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates subtle Windows bias by referencing 'Windows apps' specifically in the External Git section, and by not providing any Linux-specific instructions, examples, or parity in terminology. There are no mentions of Linux tools, shell commands, or platform-specific considerations for Linux users. The documentation assumes a platform-neutral approach but implicitly favors Windows by referencing Windows apps and omitting Linux-specific guidance.
Recommendations
- Replace 'For Windows apps, you can select External Git...' with a platform-neutral statement, or add a parallel note for Linux apps if there are differences.
- Include examples or notes for deploying from Linux environments, such as using Bash, SSH keys, or Linux-specific tooling where relevant.
- Explicitly state if the instructions are identical for both Windows and Linux, or highlight any platform-specific differences.
- Provide links or references to Linux deployment guides or troubleshooting resources.
- Review screenshots and UI references to ensure they are not Windows-centric (e.g., avoid showing only Windows app scenarios).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/app-service-undelete.md
...lob/main//articles/app-service/app-service-undelete.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a strong bias toward Windows and PowerShell usage. All command-line examples use the Azure PowerShell module, with no mention of Azure CLI or Bash equivalents, which are more common on Linux and macOS. The only programmatic restoration method described is via PowerShell, and there are no Linux-specific instructions or examples. The documentation assumes the user is familiar with PowerShell and Windows tooling, and does not provide parity for users on other platforms.
Recommendations
- Add equivalent Azure CLI (az) command examples for all PowerShell cmdlets shown, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Explicitly mention that the PowerShell module can be used on Linux and macOS via PowerShell Core, if relevant, and provide installation instructions.
- Provide Bash shell script examples where appropriate, especially for listing and restoring deleted apps using Azure CLI.
- Reorganize sections so that cross-platform tools (like Azure CLI) are presented before or alongside PowerShell examples, rather than PowerShell being the only or primary method.
- Include a table or section comparing PowerShell and Azure CLI commands for each operation, to help users choose their preferred tool.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/configure-language-java-security.md
...ticles/app-service/configure-language-java-security.md
High Priority
View Details →
Detected Bias Types
Linux First
Windows Tools
Missing Windows Example
Summary
The documentation page demonstrates a Linux-first bias in sections related to Java key store and certificate management, providing detailed instructions and examples only for Linux environments. Windows-specific tools, patterns, or examples are not mentioned, and there is no guidance for users running Tomcat, JBoss, or Java SE apps on Windows-based Azure App Service. The use of Linux paths, environment variables, and SSH/Unix tools (like keytool via SSH) is exclusive, with no Windows equivalents or parity.
Recommendations
- Add equivalent instructions and examples for managing Java key stores and certificates on Windows-based App Service environments, including default paths and how certificates are loaded.
- Provide guidance for accessing the Windows environment (e.g., using Kudu/PowerShell) to interact with the Java key store and run keytool commands.
- Mention the differences in environment variable usage and file paths between Linux and Windows App Service environments.
- Ensure that all code snippets and configuration steps are available for both Linux and Windows, or clearly state if a feature is Linux-only.
- Include links to Windows-specific documentation or troubleshooting guides where relevant.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/deploy-run-package.md
.../blob/main//articles/app-service/deploy-run-package.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a Windows-first bias by referencing Windows directory paths (e.g., D:\home\site\wwwroot) before Linux equivalents, and by describing deployment behaviors and manual steps (such as creating directories and files) only with Windows-style paths. There are no explicit Linux or cross-platform examples for manual deployment steps, and the documentation assumes familiarity with Windows filesystem conventions. Additionally, when discussing WebJobs and troubleshooting, only Windows paths are shown, and no Linux-specific instructions or examples are provided.
Recommendations
- Provide Linux and cross-platform equivalents for all directory paths (e.g., /home/site/wwwroot) alongside Windows paths, especially in manual deployment steps and troubleshooting.
- Include explicit Linux/macOS examples or notes wherever file paths, directory creation, or file manipulation are discussed.
- When describing behaviors or manual steps (such as creating packagename.txt or deploying WebJobs), show both Windows and Linux paths and commands, or use cross-platform notation.
- Add a section or callouts for Linux-specific considerations, especially for file permissions and path differences.
- Review all examples and ensure parity between Windows and Linux environments, avoiding assumptions that users are on Windows.