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 1476-1500 of 2185 flagged pages
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/application-gateway/configuration-request-routing-rules.md ...ication-gateway/configuration-request-routing-rules.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation references both PowerShell and Azure CLI for configuration tasks, but PowerShell (a Windows-centric tool) is consistently mentioned before Azure CLI. In the 'For more information' sections, PowerShell examples or links are listed before CLI equivalents, and in some cases, only PowerShell and CLI are mentioned, with no explicit mention of Bash or Linux-native tools. There are no Linux-specific examples or guidance, and the ordering implies a preference for Windows/PowerShell workflows.
Recommendations
  • Alternate the order of PowerShell and CLI references so that CLI (cross-platform) is sometimes listed first.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide Bash shell examples where appropriate.
  • Include Linux-native tooling or scripting examples (such as Bash scripts) where possible.
  • Add a section or callout highlighting cross-platform support and providing parity in instructions for both Windows and Linux users.
  • Ensure screenshots and UI references are not Windows-specific unless unavoidable.
GitHub Create Pull Request
Azure Docs 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
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation provides instructions for obtaining deployment credentials but does not include any platform-specific examples. However, it implicitly assumes a Windows-centric workflow by referencing the 'Git prompt' without clarifying how authentication might differ on Linux or macOS. There are no Linux-specific instructions or terminal examples, and the lack of explicit cross-platform guidance may leave Linux users uncertain about the process.
Recommendations
  • Add explicit instructions or examples for both Windows (e.g., Command Prompt, PowerShell) and Linux/macOS (e.g., Bash terminal) when describing how to use the credentials.
  • Clarify that the authentication process works similarly across platforms, or highlight any differences (such as how to enter the username/password in different terminal environments).
  • Include sample git commands for both Windows and Linux/macOS to demonstrate the deployment process.
  • Avoid assuming the use of the 'Git prompt' without specifying that this applies to all platforms, or provide platform-specific notes as needed.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/includes/tutorial-connect-msi-azure-database/code-sql-mi.md ...des/tutorial-connect-msi-azure-database/code-sql-mi.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation consistently references the use of Microsoft SQL Server and its associated drivers (e.g., ODBC Driver 18 for SQL Server, mssql-jdbc, mssql npm package), which are primarily Microsoft technologies. In the Python example, only the 'ODBC Driver 18 for SQL Server' is mentioned, which is often associated with Windows environments, and there is no mention of how to install or configure this driver on Linux. There are no explicit Linux-specific instructions or examples, such as installing drivers on Linux, handling environment variables in Linux shells, or troubleshooting common Linux issues. No PowerShell or cmd examples are present, but the documentation implicitly assumes familiarity with Microsoft-centric tooling.
Recommendations
  • Explicitly mention and provide installation instructions for SQL Server drivers on Linux (e.g., how to install ODBC Driver 18 for SQL Server on Ubuntu/Debian/Red Hat).
  • Include notes or examples for setting environment variables in Linux shells (e.g., export AZURE_SQL_CONNECTIONSTRING=...).
  • Add troubleshooting tips or references for common Linux issues (e.g., driver library paths, permissions).
  • Where possible, mention cross-platform alternatives or clarify that the provided drivers and code samples work on both Windows and Linux.
  • If any code or driver is Windows-only or has different behavior on Linux, clearly document those differences.
GitHub Create Pull Request
Azure Docs 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 →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias in the 'Hybrid Connections' section, where it specifies that the Hybrid Connection Manager must be installed on a 'Windows Server 2012 or newer host' and provides no mention of Linux support or alternatives. There are no Linux-specific instructions or examples, and the documentation does not clarify whether Linux-based hosts are supported for Hybrid Connection Manager. No PowerShell-heavy or Windows-first command examples are present, but the lack of Linux parity in tool support is notable.
Recommendations
  • Clarify whether Hybrid Connection Manager is available for Linux hosts. If so, provide installation and usage instructions for Linux.
  • If Hybrid Connection Manager is Windows-only, explicitly state this limitation and suggest alternative approaches for Linux environments.
  • Wherever tools or agents are mentioned, always indicate cross-platform availability and provide parity in instructions/examples for both Windows and Linux.
  • Review other sections for implicit Windows assumptions and ensure Linux users are not excluded from key networking features or guidance.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/overview-inbound-outbound-ips.md .../articles/app-service/overview-inbound-outbound-ips.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for finding outbound IP addresses, but PowerShell examples are always given immediately after the CLI, and there are no explicit Linux shell or Bash-specific examples beyond the initial nslookup command. The use of PowerShell as a primary scripting example may favor Windows users, and the documentation does not mention Linux-specific tools or workflows beyond generic CLI usage.
Recommendations
  • Ensure that all command-line examples are clearly labeled as cross-platform (e.g., Azure CLI works on Windows, macOS, and Linux) and provide explicit Bash/shell examples where appropriate.
  • If PowerShell examples are included, consider also including Bash or shell script equivalents, especially for common administrative tasks.
  • Clarify in the documentation that Azure CLI commands can be run on any platform, and provide installation/use guidance for Linux/macOS users if not already present.
  • When listing multiple command options, alternate the order (e.g., sometimes show Bash/CLI first, sometimes PowerShell) or group them under clear headings for each platform.
  • Mention any platform-specific considerations (such as differences in output formatting or prerequisites) for both Windows and Linux users.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/quickstart-java.md ...ocs/blob/main//articles/app-service/quickstart-java.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page uses zone pivots to separate instructions for different Java stacks. However, for 'java-javase' and 'java-jboss', only Windows-based instructions are included, while only 'java-tomcat' has a Linux-based example. This results in missing Linux examples for Java SE and JBoss, and Windows instructions are prioritized for these stacks.
Recommendations
  • Provide Linux-based quickstart instructions for Java SE and JBoss stacks, ensuring parity with the Tomcat example.
  • Ensure that for each Java stack (Tomcat, Java SE, JBoss), both Windows and Linux deployment options are documented and accessible.
  • Review included markdown files to confirm that Linux examples are as detailed and prominent as Windows examples.
  • Consider restructuring pivots so that users can easily select their OS/platform first, then the Java stack, to avoid implicit prioritization of Windows.
GitHub Create Pull Request
Azure Docs 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 →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation assumes a development environment based on GitHub Codespaces and .NET, with deployment and terminal instructions that are platform-agnostic but implicitly favor Windows-centric workflows (e.g., Azure App Service, .NET, Visual Studio Code). There are no explicit Linux or cross-platform command-line examples, nor any mention of Linux-specific tools, deployment methods, or troubleshooting. The tutorial does not address how to perform the same steps on a local Linux machine or reference Linux-native development environments.
Recommendations
  • Add explicit instructions or notes for users developing on local Linux or macOS environments, including how to install .NET, run the app, and deploy using CLI tools.
  • Include Linux/macOS terminal commands (e.g., bash) alongside or instead of generic 'codespace terminal' instructions.
  • Mention alternative editors (such as VS Code on Linux/macOS) and provide guidance for users not using GitHub Codespaces.
  • Clarify that the steps are cross-platform where applicable, or provide platform-specific notes if there are differences.
  • If any step is Windows-specific (such as using Azure App Service deployment features in Visual Studio), provide equivalent Linux/macOS alternatives.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/tutorial-auth-aad.md ...s/blob/main//articles/app-service/tutorial-auth-aad.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Minor Missing Linux Example
Summary
The documentation provides both Windows and Linux instructions using zone pivots, ensuring that both platforms are covered for core deployment steps. However, the Windows instructions are presented first, and there are subtle differences in detail and clarity between the two. Some minor inconsistencies exist in directory names and runtime versions between the Windows and Linux sections. Additionally, certain troubleshooting and portal-based steps do not explicitly mention platform differences, which could be confusing for Linux users.
Recommendations
  • Alternate the order of Windows and Linux pivots in different tutorials, or present both side-by-side when possible, to avoid always prioritizing Windows.
  • Ensure that directory names and runtime versions are consistent and correct in both Windows and Linux instructions (e.g., 'cd js-e2e-web-app-easy-auth-app-to-app/frontend' vs. 'cd frontend').
  • Explicitly mention when steps are platform-agnostic versus platform-specific, especially in troubleshooting and Azure Portal instructions.
  • Provide a summary table or section at the start that highlights any differences between Windows and Linux deployments, including supported runtimes and command variations.
  • Review for completeness and parity in example commands, ensuring that both platforms receive equal detail and clarity.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dev-box/how-to-configure-dev-box-serverless-gpu.md ...les/dev-box/how-to-configure-dev-box-serverless-gpu.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively referencing Windows Terminal for command-line access and not mentioning or providing instructions for Linux or macOS environments. All examples and instructions assume the user is operating from a Windows-based Dev Box, with no guidance for Linux shells or cross-platform usage.
Recommendations
  • Add explicit instructions and examples for connecting to serverless GPU from Linux and macOS Dev Boxes, including references to common terminals (e.g., GNOME Terminal, Terminal.app, bash, zsh).
  • Clarify whether the 'devbox gpu shell' command is available and supported on non-Windows platforms, and provide installation or usage notes as needed.
  • Present cross-platform instructions in a parallel or unified way, ensuring that Linux/macOS steps are given equal prominence to Windows steps.
  • If there are platform-specific limitations, document them clearly so users on all platforms understand their options.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/tutorial-webjobs.md ...cs/blob/main//articles/app-service/tutorial-webjobs.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation exhibits a mild Windows bias, primarily by referencing Windows-specific terminology and links (such as 'supported file types' and 'CRON expressions' sections that use 'tabs=windowscode'), and by presenting the .NET example (typically associated with Windows) as the first and most detailed example. However, all language pivots use Linux-style Bash scripts and run.sh, and there are no exclusive PowerShell or Windows command examples. The PHP section explicitly mentions Linux, but other pivots do not clarify OS context. The documentation does not provide Windows batch or PowerShell examples, but the structure and references suggest a Windows-first approach.
Recommendations
  • Provide explicit Linux and Windows instructions or clarify the OS context for each language pivot, especially for .NET, which is often used on both platforms.
  • Update links and references (such as 'supported file types' and 'CRON expressions') to use neutral or Linux-specific tabs where appropriate, or provide both Windows and Linux tabs.
  • If Windows batch or PowerShell scripts are supported, include equivalent examples alongside Bash scripts.
  • Clearly state in each pivot whether the instructions are for Linux, Windows, or both, and provide OS-specific guidance where needed.
  • Ensure parity in detail and sample availability across all language pivots, and avoid presenting Windows-centric stacks or tools first unless justified by usage data.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dev-box/how-to-configure-stop-on-disconnect.md ...rticles/dev-box/how-to-configure-stop-on-disconnect.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exclusively references RDP sessions as the trigger for the auto-stop feature, which is a Windows-centric remote desktop protocol. There is no mention of Linux remote access methods (such as SSH), nor any examples or notes about how the feature behaves for Linux-based dev boxes or non-RDP connections. All examples and terminology assume a Windows environment.
Recommendations
  • Clarify whether the auto-stop feature works for Linux-based dev boxes and, if so, specify which disconnect events (e.g., SSH session end) are supported.
  • Include examples or notes for Linux users, such as how to configure auto-stop for Linux dev boxes or what triggers are available.
  • If the feature is Windows-only, explicitly state this limitation at the beginning of the documentation.
  • Consider referencing both RDP (for Windows) and SSH (for Linux) in the documentation to provide parity and clarity for cross-platform users.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/application-gateway/quick-create-terraform.md ...articles/application-gateway/quick-create-terraform.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively demonstrates the creation of a Windows Virtual Machine as the backend for the Application Gateway, without mentioning or providing examples for Linux virtual machines. This presents a Windows-first bias and omits Linux parity in the core scenario.
Recommendations
  • Include parallel instructions and Terraform code examples for creating an Azure Linux Virtual Machine (using azurerm_linux_virtual_machine) alongside the Windows VM example.
  • Explicitly mention that either Windows or Linux VMs can be used as backend pool members, and provide links to both resource documentation.
  • When listing steps or resources, avoid defaulting to Windows unless there is a specific requirement; instead, present both options or indicate that the choice is flexible.
  • If scripts or commands are provided for verification or setup, ensure they are cross-platform or provide both Windows and Linux variants where applicable.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dev-box/how-to-configure-network-connections.md ...ticles/dev-box/how-to-configure-network-connections.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page focuses exclusively on configuring network connections via the Azure portal and Microsoft-centric tools and concepts (such as Active Directory, Microsoft Entra join, and Windows-based network security). There are no examples or references to Linux-specific tools, command-line interfaces, or cross-platform alternatives. The documentation assumes a Windows-centric environment and omits guidance for users who may be managing networks or dev boxes from Linux or non-Windows systems.
Recommendations
  • Include CLI-based instructions using Azure CLI (az), which is cross-platform and can be run on Windows, Linux, and macOS.
  • Provide examples for creating and managing network connections using PowerShell and Bash, highlighting parity between Windows and Linux environments.
  • Reference Linux-compatible tools and workflows for managing Azure resources, such as using the Azure CLI in Bash or Cloud Shell.
  • Clarify that the Azure portal is accessible from any OS, but also provide command-line alternatives for automation and scripting.
  • Mention how Linux administrators can interact with Active Directory (e.g., via realmd, sssd, or Azure AD integration tools) if relevant to the dev box scenario.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/application-gateway/for-containers/container-networking.md ...ication-gateway/for-containers/container-networking.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page references a 'Next steps' link to 'Deploy ALB Controller' with a URL parameter '?tabs=install-helm-windows', which suggests that Windows installation instructions are prioritized or shown by default. There are no explicit Linux or cross-platform command examples or references, and no mention of Linux-specific tooling or instructions. This could lead Linux users to perceive the documentation as Windows-biased or less relevant to their environment.
Recommendations
  • Ensure that all installation and usage examples (such as Helm commands) are provided for both Windows (PowerShell/CMD) and Linux/macOS (Bash) environments.
  • If using tabbed instructions, default to a neutral or most common platform (often Linux/Bash for Kubernetes) or provide clear tabs for both Windows and Linux.
  • Explicitly mention that the Application Gateway for Containers and related tooling are cross-platform, and provide parity in documentation for both Windows and Linux users.
  • Review all linked pages (such as the ALB Controller deployment guide) to ensure Linux instructions are present and not secondary to Windows.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/application-gateway/configuration-listeners.md ...rticles/application-gateway/configuration-listeners.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides a PowerShell example for enabling HTTP/2 support but does not include equivalent CLI or Linux-native command examples. There are no references to Linux tools or shell commands, and the only automation example is Windows-centric, which may disadvantage Linux users.
Recommendations
  • Include Azure CLI examples alongside PowerShell for all configuration tasks, especially for enabling features like HTTP/2.
  • Where automation or scripting is demonstrated, provide both PowerShell and Bash/Azure CLI equivalents.
  • Explicitly mention that all features are available via cross-platform tools (e.g., Azure CLI, ARM templates) and link to relevant documentation.
  • Review the documentation for other sections where only Windows tooling is referenced and add Linux-friendly alternatives.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/application-gateway/configuration-overview.md ...articles/application-gateway/configuration-overview.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page lists PowerShell (a Windows-centric tool) before Azure CLI in the 'Next steps' section, suggesting a Windows-first approach. While Azure CLI (cross-platform) is included, the ordering may imply a preference for Windows tools. No Linux-specific examples or tools are highlighted, and there are no explicit Linux command-line instructions.
Recommendations
  • List Azure CLI before PowerShell in the 'Next steps' section to reflect its cross-platform nature and appeal to Linux users.
  • Include explicit examples or links for Linux users where relevant, such as Bash scripts or Linux command-line usage.
  • Ensure parity in documentation by providing equal prominence to cross-platform tools and workflows.
  • Consider adding a note or section that highlights the cross-platform compatibility of Azure CLI and provides guidance for both Windows and Linux users.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/application-gateway/configure-alerts-with-templates.md ...application-gateway/configure-alerts-with-templates.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page references the use of ARM templates and provides links to deploy them via the Azure Portal, but the only procedural link for using these templates is to a page titled 'alerts-create-rule-cli-powershell-arm', which prioritizes PowerShell (a Windows-centric tool) in its naming and likely in its content. There are no explicit Linux/CLI/Bash examples or instructions, and no mention of cross-platform command-line tools. This may lead Linux users to feel unsupported or unclear about how to perform these tasks outside of Windows/PowerShell environments.
Recommendations
  • Explicitly include instructions and examples for deploying ARM templates using Azure CLI (az deployment), which is cross-platform and widely used on Linux.
  • Avoid referencing only PowerShell or Windows-centric tools in procedural links or section headings; instead, mention both PowerShell and Azure CLI where appropriate.
  • Add a section or note clarifying that all deployment steps can be performed from Linux, macOS, or Windows using Azure CLI, and provide sample commands.
  • Where possible, provide Bash shell script examples alongside PowerShell examples to ensure parity for Linux users.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dev-box/how-to-manage-dev-box-pools.md .../main//articles/dev-box/how-to-manage-dev-box-pools.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes managing Dev Box pools via the Azure portal UI, with all screenshots and instructions based on the web interface. There are no command-line examples, scripts, or references to automation tools for either Windows (e.g., PowerShell) or Linux (e.g., Azure CLI, Bash). However, the absence of any Linux-specific instructions or parity with cross-platform tools like Azure CLI means Linux users are not directly supported, and the documentation implicitly assumes a Windows-centric workflow.
Recommendations
  • Add Azure CLI examples for all major operations (create, manage, delete dev box pools), as the CLI is cross-platform and works on Linux, macOS, and Windows.
  • Explicitly mention that all operations can be performed via the Azure CLI or REST API, and provide links to relevant documentation.
  • Include at least one example of managing Dev Box pools using Bash scripts or shell commands to demonstrate Linux parity.
  • Where screenshots are used, clarify that the Azure portal is web-based and accessible from any OS, but also provide equivalent command-line instructions.
  • If PowerShell examples are ever added, ensure Azure CLI or Bash equivalents are always provided alongside.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dev-box/how-to-manage-dev-center.md ...lob/main//articles/dev-box/how-to-manage-dev-center.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exclusively describes managing Microsoft Dev Box dev centers via the Azure portal UI, with no mention of command-line tools or automation. There are no examples or references to PowerShell, Windows tools, or Linux equivalents. However, the implicit bias is present in that the Azure portal and its UI patterns are generally more familiar to Windows users, and there is no mention of CLI-based management (such as Azure CLI or Bash scripting), which are commonly used on Linux and cross-platform environments.
Recommendations
  • Add equivalent Azure CLI (az) command examples for all management tasks (creating, deleting, assigning permissions) alongside portal instructions.
  • Explicitly mention that all tasks can be performed from Linux, macOS, and Windows using the Azure CLI.
  • Provide Bash and PowerShell script snippets for automation, ensuring parity between platforms.
  • Include links to Azure CLI documentation and note any platform-specific considerations.
  • Where screenshots are shown, clarify that the Azure portal is web-based and accessible from any OS.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dev-box/how-to-request-quota-increase.md ...ain//articles/dev-box/how-to-request-quota-increase.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes quota management and support request processes via the Azure Portal's graphical interface, which is most commonly accessed from Windows environments. There are no command-line examples (such as Azure CLI, Bash, or PowerShell), nor are there references to Linux-native tools or workflows. This creates a subtle Windows-first bias and omits parity for users who prefer or require Linux or cross-platform command-line interfaces.
Recommendations
  • Add equivalent instructions for requesting quota increases using the Azure CLI (az) with example commands, which work on both Linux and Windows.
  • Explicitly mention that the Azure Portal is web-based and accessible from any OS, to clarify cross-platform compatibility.
  • Include links or references to documentation on using REST APIs or automation (e.g., ARM templates, Bicep, Terraform) for quota management, which are platform-agnostic.
  • If PowerShell examples are ever added, ensure Azure CLI or Bash equivalents are provided alongside.
  • Consider a section or callout for Linux/macOS users, highlighting any differences or confirming there are none.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dev-box/how-to-manage-dev-box-definitions.md .../articles/dev-box/how-to-manage-dev-box-definitions.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exclusively references Windows-based images (e.g., Windows 11 Enterprise, Visual Studio on Windows) and does not mention or provide examples for Linux-based dev box images. All example images and recommendations are Windows-centric, and there is no guidance or mention of Linux as a supported or recommended option.
Recommendations
  • Explicitly mention whether Linux images are supported for dev box definitions. If supported, provide examples of selecting Linux images from Azure Marketplace or Azure Compute Gallery.
  • Include Linux-based image recommendations alongside Windows examples (e.g., Ubuntu, CentOS, or other popular development distributions).
  • Add screenshots and step-by-step instructions for creating dev box definitions using Linux images.
  • Clarify any limitations or differences in feature support between Windows and Linux dev boxes.
  • Ensure that references to productivity tools and preconfigured images include Linux alternatives where applicable.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/application-gateway/redirect-overview.md ...ain//articles/application-gateway/redirect-overview.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation page does not provide any OS-specific command-line examples, but the only 'Next steps' link points to a PowerShell-based tutorial, which is primarily a Windows tool. There are no references to Linux tools or cross-platform alternatives such as Azure CLI or ARM templates. This may lead Linux or cross-platform users to believe that Windows/PowerShell is the preferred or only supported environment for configuring Application Gateway redirection.
Recommendations
  • Provide links to equivalent tutorials using Azure CLI, which is cross-platform and widely used on Linux and macOS.
  • Mention that configuration can be performed via the Azure Portal, Azure CLI, PowerShell, or ARM templates, and provide links to documentation for each method.
  • Ensure that examples and next steps are balanced, offering both PowerShell and non-Windows (e.g., Azure CLI, Bash) options.
  • Explicitly state that all features described are available regardless of the user's operating system.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automanage/quick-python-sdk.md ...ocs/blob/main//articles/automanage/quick-python-sdk.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by linking exclusively to the Windows virtual machine quick-create guide in the prerequisites, without mentioning or providing equivalent Linux VM resources or examples. No Linux-specific instructions or references are present, and the only VM creation link is for Windows.
Recommendations
  • Include links to both Windows and Linux virtual machine quick-create guides in the prerequisites section.
  • Explicitly state that the instructions apply to both Windows and Linux VMs, or clarify any differences if they exist.
  • Provide example resource links or notes for Linux VM users to ensure parity and inclusivity.
  • Review other referenced documentation to ensure Linux is equally represented alongside Windows.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automanage/overview-configuration-profiles.md ...articles/automanage/overview-configuration-profiles.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page generally describes Automanage configuration profiles in a platform-neutral way, but there is a subtle Windows bias. The only specific example of a service to toggle (Microsoft Antimalware) is Windows-centric, and no Linux-specific services or examples are mentioned. Additionally, the links to platform-specific documentation list Linux first, but the main content does not provide parity in examples or details for Linux users.
Recommendations
  • Include Linux-specific examples when discussing custom profiles or toggling services (e.g., mention Linux security agents or monitoring tools).
  • Provide at least one Linux-focused scenario alongside the Windows/Microsoft Antimalware example.
  • Explicitly mention if certain features or services differ between Windows and Linux, and provide guidance for both.
  • Ensure that references to platform-specific documentation are balanced by including brief summaries or highlights for both Windows and Linux within the main content.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automanage/virtual-machines-best-practices.md ...articles/automanage/virtual-machines-best-practices.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific features (such as Windows security baselines) without mentioning Linux equivalents, and by omitting Linux-specific guidance or examples for Automanage best practices. The focus on Windows tools and lack of Linux parity in descriptions and configuration guidance may leave Linux users underserved.
Recommendations
  • Include explicit references to Linux support for each participating service, clarifying which features are available or behave differently on Linux VMs.
  • For sections like 'Guest configuration', mention whether there are Linux security baselines or equivalent compliance policies, and provide links or guidance for Linux VM configuration.
  • Add examples or notes for Linux VM onboarding, configuration, and monitoring, especially where the process or available features differ from Windows.
  • Where Windows-specific tools or baselines are mentioned, provide Linux alternatives or state clearly if they are not available/applicable.
  • Consider a comparison table or section summarizing feature parity and differences between Windows and Linux VMs for Automanage.
GitHub Create Pull Request
← Previous Page 60 of 88 Next →