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 826-850 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/batch/batch-task-output-files.md
...s/blob/main//articles/batch/batch-task-output-files.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. All code samples use Windows-specific command syntax (cmd.exe), and there are no Linux shell (bash) equivalents. File path examples use backslashes, with only a brief note to change to forward slashes for Linux, but no Linux-specific code is provided. The sample project is a Visual Studio solution targeting .NET/C#, with no mention of cross-platform development environments or alternative languages. Windows tools and patterns (such as Visual Studio, .exe files, and Windows paths) are mentioned exclusively or before any Linux equivalents, which are not provided.
Recommendations
- Provide equivalent Linux/bash code samples for task commands (e.g., use bash shell commands instead of only cmd.exe).
- Show file path examples using both Windows (\) and Linux (/) conventions, or use platform-agnostic path construction.
- Include instructions for running the sample project on Linux (e.g., using .NET Core/SDK on Linux, VS Code, or CLI tools), not just Visual Studio on Windows.
- Mention and provide examples for alternative languages and SDKs (e.g., Python, Java) that are cross-platform.
- Explicitly state any platform-specific requirements or differences, and offer guidance for both Windows and Linux users.
- Where possible, use platform-neutral terminology and tools, or provide parallel instructions for both environments.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/batch/batch-sig-images.md
...ure-docs/blob/main//articles/batch/batch-sig-images.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 tools (PowerShell) are mentioned before their Linux equivalents, and Windows connection methods (RDP) are described before Linux (SSH). PowerShell commands are listed before Azure CLI, and there is a lack of explicit Linux shell examples for common tasks. Some instructions and UI steps reference Windows patterns or terminology first, and Linux alternatives are sometimes only mentioned as an afterthought.
Recommendations
- When listing supported image references, present Azure CLI (cross-platform) examples before PowerShell, or provide both side-by-side.
- Include explicit Linux shell (bash) command examples for tasks like connecting to VMs, mounting disks, or preparing images.
- In UI instructions, mention Linux (SSH) and Windows (RDP) connection methods equally and in parallel, not with Windows first.
- Where PowerShell commands are shown, always provide the equivalent Azure CLI or bash commands.
- Add Linux-specific considerations (e.g., mounting disks, file permissions) where relevant, not just generic instructions.
- Ensure that screenshots and UI walkthroughs do not assume a Windows environment or terminology.
- Review for any terminology or steps that are Windows-centric and provide Linux alternatives or clarifications.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/batch/batch-task-output.md
...re-docs/blob/main//articles/batch/batch-task-output.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Windows Tools
Summary
The documentation page demonstrates bias toward Windows by providing a Windows-specific example for custom file movement (using .exe files and Windows command chaining), omitting equivalent Linux/bash examples. The only explicit example for running post-task scripts is Windows-centric, and there is no mention of Linux tools, shell scripts, or cross-platform command patterns. Additionally, the .NET/C# library is highlighted before mentioning the standard for other languages, reinforcing a Windows-first perspective.
Recommendations
- Add equivalent Linux/bash examples alongside Windows examples, such as using shell scripts (.sh) and bash command chaining (e.g., './doMyWork.sh && ./uploadMyFilesToSql.sh').
- Explicitly mention that custom scripts can be written in any language and run on both Windows and Linux nodes, providing examples for both.
- When discussing the Batch File Conventions library, clarify cross-platform support and provide links or references to libraries or patterns for non-Windows environments.
- Avoid using only Windows-specific file extensions (.exe) or command syntax; always pair with Linux equivalents.
- Consider reordering sections or examples so that Windows and Linux approaches are presented in parallel, rather than Windows-first.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/batch/batch-upgrade-policy.md
...docs/blob/main//articles/batch/batch-upgrade-policy.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a clear Windows bias: all code examples (REST API and C# SDK) exclusively use Windows images and Windows-specific configuration properties. There are no Linux image examples or Linux-specific configuration guidance. The only OS-specific property discussed is 'windowsConfiguration.enableAutomaticUpdates', with no mention of Linux equivalents. The documentation does not provide parity for Linux users, omitting both configuration and example usage for Linux-based pools.
Recommendations
- Add parallel examples for Linux pools in both REST API and SDK sections, using a Linux image (e.g., Ubuntu) and appropriate nodeAgentSKUId.
- Document Linux-specific configuration options, such as 'linuxConfiguration', and clarify any differences in upgrade or patching behavior.
- When discussing OS-specific properties (e.g., 'windowsConfiguration.enableAutomaticUpdates'), also mention the Linux equivalents or explicitly state if not applicable.
- In all code and JSON examples, provide both Windows and Linux variants, or use a neutral example with comments for both OS types.
- Ensure the 'Supported OS images' section explicitly lists both Windows and Linux images, and clarify any differences in support or behavior.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dns/dns-get-started-template.md
...cs/blob/main//articles/dns/dns-get-started-template.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. All command-line examples use Azure PowerShell, with no Azure CLI (bash) or Linux shell equivalents provided. Instructions for validating DNS resolution use Windows Command Prompt syntax (cmd), and there is no mention of Linux or macOS alternatives. The workflow and screenshots are tailored to Windows users, and Linux users are not directly addressed.
Recommendations
- Provide equivalent Azure CLI (az) commands alongside PowerShell examples, preferably with a tabbed interface for PowerShell, Azure CLI, and REST API.
- Include Linux/macOS shell instructions for DNS validation (e.g., using 'dig' or 'nslookup' in bash/zsh), and clarify that the commands work cross-platform.
- Mention that Azure Cloud Shell supports both Bash and PowerShell, and show how to select the preferred shell.
- Ensure that screenshots and instructions are not Windows-specific, or provide Linux/macOS alternatives where appropriate.
- Explicitly state that all steps can be performed from Linux, macOS, or Windows, and link to platform-agnostic documentation where possible.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/batch/batch-task-output-file-conventions.md
...//articles/batch/batch-task-output-file-conventions.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively providing .NET (C#) code samples, referencing Visual Studio 2019 as the development environment, and mentioning Windows-specific tools and patterns (e.g., .exe files, Visual Studio solution, WindowsAzure.Storage). There are no Linux or cross-platform development instructions, nor are there examples for running or building the sample on Linux or with non-Windows tooling. The documentation does not mention or provide parity for Linux-based workflows, such as using .NET Core/SDK on Linux, or alternative editors and build tools.
Recommendations
- Add explicit instructions and examples for running and building the sample on Linux, including using the .NET SDK/CLI and cross-platform editors like VS Code.
- Replace or supplement references to Visual Studio 2019 with cross-platform alternatives, such as Visual Studio Code or JetBrains Rider, and provide CLI-based build/run instructions.
- Clarify that the .NET File Conventions library works on both Windows and Linux, and provide sample code or scripts for Linux environments.
- Avoid referencing Windows-specific file extensions (e.g., .exe) or provide Linux equivalents (e.g., .dll, .sh) where appropriate.
- Include guidance for installing dependencies and running the code on Linux (e.g., using dotnet CLI, Mono, or Docker containers).
- Ensure that all code samples, instructions, and tooling references are cross-platform or have Linux-specific alternatives.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/batch/create-pool-ephemeral-os-disk.md
.../main//articles/batch/create-pool-ephemeral-os-disk.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell as the only example for programmatically querying VM capabilities, and by not providing equivalent Linux/CLI examples. There is no mention of Linux tools or Bash/CLI commands for checking ephemeral OS disk support, and the only referenced script is a PowerShell cmdlet. The code examples are platform-neutral (Python and C#), but operational guidance is Windows-centric.
Recommendations
- Add Azure CLI and Bash examples for querying VM series capabilities (e.g., using 'az vm list-skus' or similar commands) alongside the PowerShell example.
- Explicitly mention both Windows and Linux approaches/tools when discussing how to check for ephemeral OS disk support.
- Ensure that operational instructions and examples are provided for both Windows and Linux users, not just PowerShell/Windows.
- Where PowerShell is referenced, provide an equivalent Bash or Azure CLI command immediately after or alongside it.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dns/dns-import-export.md
...zure-docs/blob/main//articles/dns/dns-import-export.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation shows a mild Windows bias. When describing how to obtain a DNS zone file, the Windows DNS file location is mentioned before BIND (the most common Linux DNS server). In the verification section, only the Windows Command Prompt syntax for nslookup is shown, with no Linux/macOS equivalent. There are no explicit Linux shell examples for nslookup or file paths, and the only command-line verification example uses Windows-centric syntax.
Recommendations
- When listing DNS zone file locations, mention BIND (Linux) before or alongside Windows DNS, and provide example file paths for both.
- In the verification section, provide nslookup examples for both Windows (cmd) and Linux/macOS (bash/terminal), showing the appropriate command syntax for each.
- Explicitly state that the Azure CLI commands work identically on Windows, Linux, and macOS, and provide sample commands or notes for common Linux/macOS shells where relevant.
- Where file paths are referenced, show both Windows and Linux/Mac path formats if applicable.
- Consider adding a note or section for Linux users about common DNS tools (e.g., dig) and how to use them to verify DNS records.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dns/dns-import-export-portal.md
...cs/blob/main//articles/dns/dns-import-export-portal.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation references Windows DNS and its default zone file location before mentioning BIND (the most common Linux DNS server), and provides explicit Windows file paths and console navigation steps. There are no Linux or cross-platform file path examples, nor are there screenshots or instructions for obtaining zone files from Linux/BIND systems. The only explicit file path given is for Windows, and the documentation assumes familiarity with Windows conventions.
Recommendations
- Provide parallel instructions and file path examples for obtaining DNS zone files from BIND/Linux systems, including typical BIND zone file locations (e.g., /etc/bind/).
- Mention BIND and Linux-based DNS servers before or alongside Windows DNS to avoid prioritizing Windows.
- Include screenshots or command-line examples for both Windows and Linux environments.
- Use neutral language and avoid assuming the user is on Windows; when referencing file paths, provide both Windows and Linux equivalents.
- Add a section or note about exporting zone files from BIND/Linux using common tools (e.g., cat, cp, or named tools).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/batch/create-pool-public-ip.md
...ocs/blob/main//articles/batch/create-pool-public-ip.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by listing Azure PowerShell as a primary method for creating public IP addresses, with no explicit Linux shell or Bash examples provided. While Azure CLI is mentioned (which is cross-platform), PowerShell is listed after the portal and before any Linux-specific guidance. There are no Linux/Bash command-line examples, and the documentation does not clarify that Azure CLI commands can be run in Bash or other Linux shells. The only code example is a REST API payload, which is platform-neutral, but the supporting instructions favor Windows tools.
Recommendations
- Provide explicit Bash/Linux shell examples for creating public IP addresses using Azure CLI.
- Clarify that Azure CLI commands can be run on Linux, macOS, and Windows, and provide sample commands in a Bash context.
- List Azure CLI (cross-platform) before PowerShell in the list of methods for creating public IP addresses.
- Consider adding a note or section for Linux users, highlighting any differences or tips for Linux environments.
- Ensure parity in tool recommendations by mentioning Linux-native tools or approaches where relevant.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/batch/batch-user-accounts.md
...-docs/blob/main//articles/batch/batch-user-accounts.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias in several areas. Windows tools and patterns (e.g., cmd.exe, DPAPI, RDP) are mentioned before or instead of Linux equivalents. Code examples often default to Windows command lines (e.g., 'cmd /c echo hello'), and Windows-specific features are referenced without parallel Linux guidance. While there are some Linux-specific notes and a .NET example for Linux pool creation, Linux command-line examples and tools are generally missing or less emphasized.
Recommendations
- Provide Linux shell command examples (e.g., 'bash -c "echo hello"') alongside or before Windows 'cmd.exe' examples in all code snippets.
- Mention Linux tools (e.g., OpenSSL, GPG) as alternatives to Windows DPAPI when discussing secrets management.
- Ensure that references to remote access (RDP/SSH) are balanced and that Linux SSH guidance is as prominent as Windows RDP guidance.
- Include explicit Linux-focused code snippets for running tasks, especially in sections where only Windows commands are shown.
- Where possible, use cross-platform neutral language and examples (e.g., 'echo hello' without specifying shell) or provide both Windows and Linux variants.
- Highlight any Linux-specific considerations or differences in user account handling, not just in passing but with concrete examples.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/batch/monitor-batch.md
.../azure-docs/blob/main//articles/batch/monitor-batch.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a mild Windows bias. While it mentions both Linux and Windows monitoring agents and extensions, Windows tools and .NET libraries are referenced more prominently, and there are no explicit Linux command-line or code examples. The Application Insights integration walkthrough is only provided for .NET (a Windows-centric stack), and no equivalent example is given for Linux or cross-platform languages. There are also no Linux shell (bash/CLI) examples for accessing logs or monitoring, nor are Linux-specific tools or SDKs highlighted.
Recommendations
- Provide equivalent Linux-based examples for accessing and processing diagnostic logs (e.g., using Azure CLI, azcopy, or Python scripts).
- Include sample code or walkthroughs for integrating Application Insights or monitoring in cross-platform languages (such as Python or Java), not just .NET.
- When listing monitoring agents and extensions, alternate the order or group by OS rather than listing Windows first.
- Mention and provide examples for Linux-native tools or SDKs (e.g., Azure CLI, Bash scripts) alongside Windows/PowerShell/.NET examples.
- Add explicit Linux usage scenarios or troubleshooting steps to ensure parity with Windows-focused content.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dns/dns-private-records.md
...re-docs/blob/main//articles/dns/dns-private-records.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation references Azure PowerShell as a primary interface for managing DNS records (e.g., in the TXT records and Etags sections), without providing equivalent examples or explicit mention of Linux-native tools or cross-platform CLI usage. There are no Linux-specific or cross-platform command-line examples, and the only tool-specific guidance is for PowerShell, which is traditionally associated with Windows environments.
Recommendations
- Add Azure CLI examples alongside or before PowerShell examples, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Explicitly mention that PowerShell is available cross-platform, or clarify when instructions are Windows-specific.
- Include references or examples using Linux-native tools (e.g., dig, nslookup) where relevant, especially when demonstrating DNS record queries.
- Ensure that all tool-specific guidance is paired with equivalent instructions for both Windows and Linux environments.
- Review and update documentation to avoid assuming PowerShell as the default management tool, and provide parity for Linux administrators.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/batch/nodes-and-pools.md
...zure-docs/blob/main//articles/batch/nodes-and-pools.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation generally mentions both Windows and Linux support, but there are subtle biases: Windows tools and patterns (e.g., .exe, .cmd, .bat, PowerShell, RDP, Windows Server 2016 Datacenter with Containers) are often listed first or exclusively, while Linux equivalents (e.g., shell scripts, SSH, Linux container images) are mentioned later or not at all. Some sections (like container support) focus on Windows images or tools, with less detail or no examples for Linux. There are no explicit Linux command-line or scripting examples, and the documentation references Windows-specific tools and images more prominently.
Recommendations
- When listing supported executable/script types, alternate the order or explicitly mention Linux formats first in some places (e.g., '.sh, Python, and binary executables (for Linux); .exe, .cmd, .bat, PowerShell (for Windows)').
- In sections discussing remote access, give equal prominence to SSH for Linux and RDP for Windows, and provide links or examples for both.
- For container support, provide explicit instructions and examples for both Windows and Linux pools, including references to common Linux container images and setup steps.
- Add Linux-focused examples or code snippets where appropriate (e.g., shell script examples for start tasks, Linux VM image selection).
- Where Windows tools or patterns are mentioned (e.g., PowerShell, .bat), ensure Linux equivalents (e.g., Bash, .sh) are also described and linked.
- Review the order of presentation to avoid always listing Windows first, especially in introductory or summary sections.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/batch/tutorial-run-python-batch-azure-data-factory.md
.../batch/tutorial-run-python-batch-azure-data-factory.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively using Windows-based tools (Batch Explorer, Storage Explorer), selecting a Windows VM image (Dsvm Win 2019) for the Batch pool, and providing only Windows command-line examples (e.g., 'cmd /c'). There are no Linux equivalents or instructions, and Linux VM images or shell commands are not mentioned or offered as alternatives.
Recommendations
- Include instructions and screenshots for creating Batch pools with Linux VM images (e.g., Ubuntu or CentOS) in Batch Explorer.
- Provide alternative shell commands for Linux nodes (e.g., use 'bash -c' instead of 'cmd /c' for the start task and pipeline command).
- Mention and demonstrate the use of Batch Explorer and Storage Explorer on Linux/macOS, or provide CLI alternatives (e.g., Azure CLI, azcopy) for users who do not use Windows.
- Add explicit notes or sections for cross-platform compatibility, highlighting any differences or considerations for Linux users.
- Ensure that all code and command-line snippets are provided for both Windows and Linux environments where applicable.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/batch/quick-create-portal.md
...-docs/blob/main//articles/batch/quick-create-portal.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively using Windows compute nodes (Windows Server 2019) in the pool creation steps and providing only Windows command-line examples (cmd, timeout). There is no mention of Linux-based pools or examples of Linux shell commands, and the workflow assumes Windows environments throughout.
Recommendations
- Include parallel instructions for creating a pool of Linux compute nodes, specifying a common Linux VM image (e.g., Ubuntu LTS).
- Provide Linux shell command examples (e.g., using bash and sleep) alongside Windows cmd examples when creating tasks.
- Explicitly mention that Azure Batch supports both Windows and Linux pools, and guide users on how to select the appropriate OS for their workloads.
- Add screenshots and walkthroughs for Linux-based pools and tasks to ensure visual parity.
- Consider a table or toggle to show both Windows and Linux steps side-by-side for each relevant section.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/batch/monitor-application-insights.md
...b/main//articles/batch/monitor-application-insights.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a strong Windows bias: it exclusively references Windows tools (Visual Studio, cmd, WindowsServer images), uses PowerShell/NuGet commands for package installation, and all code/configuration examples assume a Windows environment. There are no Linux equivalents or instructions for cross-platform development, and the only VM image referenced is 'MicrosoftWindowsServer'.
Recommendations
- Provide equivalent instructions and examples for Linux environments, including how to install Application Insights packages using dotnet CLI or other cross-platform tools.
- Include guidance for developing and running Azure Batch .NET applications on Linux, such as using VS Code or JetBrains Rider instead of only Visual Studio.
- Show how to configure Application Insights for Linux compute nodes, including using a Linux VM image in the pool configuration and appropriate command-line syntax (e.g., bash instead of cmd).
- Add Linux-specific code snippets or highlight any differences in file paths, environment variables, or deployment steps.
- Mention cross-platform compatibility and link to relevant documentation for .NET Core/.NET 5+ on Linux.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/batch/security-best-practices.md
...s/blob/main//articles/batch/security-best-practices.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation generally maintains OS neutrality but exhibits subtle Windows bias in several areas. Windows-specific tools (PowerShell) are mentioned before or instead of Linux equivalents for some operations (e.g., discovering supported images). The section on TLS focuses exclusively on Windows configuration, with no Linux guidance. References to remote access mention RDP before SSH, and Windows-specific configuration properties are discussed in more detail than Linux equivalents.
Recommendations
- For every mention of PowerShell, provide equivalent Azure CLI and/or Bash examples or links, especially for Linux users.
- In the TLS/SSL configuration section, add guidance or references for securing TLS on Linux compute nodes (e.g., updating OpenSSL, configuring ciphers).
- When discussing remote access, mention SSH before or alongside RDP, and provide parity in configuration details for both Windows and Linux.
- Where Windows-specific VM configuration properties are discussed (e.g., enableAutomaticUpdates), include Linux equivalents or clarify if not applicable.
- Review all tool and command references to ensure both Windows and Linux management tools are equally represented and ordered neutrally.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/digital-twins/tutorial-command-line-cli.md
...n//articles/digital-twins/tutorial-command-line-cli.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. While it primarily uses the Azure CLI (which is cross-platform), several sections and tips are written with a Windows-first perspective. Cloud Shell (which is Linux-based) is referenced, but there is a notable lack of explicit Linux or macOS terminal examples. PowerShell is mentioned as an alternative, but Bash/Linux-specific guidance is minimal and often only appears as a note about escaping characters. There are no Linux-specific screenshots or step-by-step instructions for Linux/macOS users, and file upload instructions are written generically, not tailored for Linux environments.
Recommendations
- Add explicit Linux/macOS terminal examples and screenshots alongside or before Windows/Cloud Shell examples.
- Provide clear instructions for downloading and managing files on Linux/macOS (e.g., using wget/curl, cp, mv, etc.), not just via browser or Cloud Shell upload.
- Include Bash-specific command-line nuances and troubleshooting tips, not just notes about escaping characters.
- Where PowerShell is mentioned, provide equivalent Bash/Linux shell commands and highlight any differences in behavior.
- Clarify when Cloud Shell is Linux-based and how that affects command syntax, file paths, and environment variables.
- Add a section or callout for Linux/macOS users in the prerequisites and setup steps, ensuring parity with Windows instructions.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/batch/quick-run-dotnet.md
...ure-docs/blob/main//articles/batch/quick-run-dotnet.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a clear Windows bias: it exclusively configures Batch pools with Windows Server images, uses Windows command-line tools (e.g., 'cmd /c type'), and provides no Linux equivalents or examples. While .NET and Visual Studio are cross-platform, the quickstart does not show how to use Linux pools, Linux command lines, or provide Linux-specific guidance, despite mentioning .NET 6+ compatibility with Linux.
Recommendations
- Provide parallel examples for creating Linux-based Batch pools, including code snippets for specifying a Linux Marketplace image and the appropriate node agent SKU (e.g., 'batch.node.ubuntu 20.04').
- Show how to use Linux command-line equivalents in tasks (e.g., use 'bash -c cat {filename}' instead of 'cmd /c type {filename}').
- Explicitly mention in the prerequisites and throughout the guide that the quickstart works on both Windows and Linux, and clarify any platform-specific steps.
- Include sample output and troubleshooting notes for Linux-based pools.
- Where Windows tools or patterns are mentioned (e.g., Visual Studio), also mention Linux alternatives (e.g., VS Code, JetBrains Rider, or using the dotnet CLI).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/batch/virtual-file-mount.md
...e-docs/blob/main//articles/batch/virtual-file-mount.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is used as the primary scripting interface for both Windows and Linux examples, rather than showing native Linux shell commands. In several sections, Windows tools and workflows (e.g., 'net use', 'cmdkey', RDP) are described in detail, sometimes before or more prominently than their Linux equivalents. The documentation also references Windows-specific troubleshooting tools and patterns, and links to Windows resources before Linux ones in some places.
Recommendations
- Provide native Linux shell (bash) command examples for mounting file systems, especially for manual mounting and troubleshooting, rather than only using PowerShell.
- Balance the order of presentation so that Linux and Windows instructions/examples are given equal prominence, or alternate which comes first.
- Include Linux-native troubleshooting steps and tools (e.g., using 'mount', 'dmesg', 'journalctl', or 'lsblk') alongside Windows tools like RDP and 'net use'.
- Reference Linux documentation and resources as prominently as Windows ones in the 'Next steps' and throughout the page.
- Where possible, avoid assuming PowerShell is the default scripting environment for Linux users; offer bash alternatives.
- Clarify when a tool or command is platform-specific, and provide parallel instructions for both OSes.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dns/dns-private-resolver-overview.md
...ob/main//articles/dns/dns-private-resolver-overview.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Azure PowerShell and Azure portal (GUI) instructions, with no mention of Linux-native tools (such as Azure CLI or Bash scripting) for managing Azure DNS Private Resolver. References to PowerShell are made before any cross-platform or Linux-friendly alternatives, and there are no Linux-specific or cross-platform command-line examples provided.
Recommendations
- Add Azure CLI examples and quickstarts alongside or before PowerShell examples to ensure cross-platform parity.
- Explicitly mention that Azure CLI can be used from Linux, macOS, and Windows, and provide links to relevant CLI documentation.
- Where PowerShell is referenced, also provide equivalent Bash or shell script commands for Linux users.
- In the 'Next steps' and 'For more information' sections, include links to Azure CLI and REST API guides, not just PowerShell and portal.
- Review all quickstart and tutorial links to ensure Linux users are not excluded or forced to use Windows-centric tools.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/business-continuity-center/tutorial-manage-data-using-copilot.md
...ontinuity-center/tutorial-manage-data-using-copilot.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation repeatedly references PowerShell scripts and 'Command tools (PowerShell/CLI)' as the primary or only command-line automation method, with explicit mention and screenshots of PowerShell scripts for backup and security operations. There are no explicit Linux shell (bash) or cross-platform CLI examples, and PowerShell is consistently mentioned before CLI, suggesting a Windows-first approach. No Linux-specific instructions, screenshots, or parity examples are provided.
Recommendations
- Provide explicit bash/Azure CLI script examples alongside PowerShell scripts for all automation tasks.
- When referencing 'Command tools', use 'Azure CLI/PowerShell' or 'CLI tools (Azure CLI/PowerShell)' and alternate the order to avoid Windows-first bias.
- Include screenshots and downloadable scripts for both PowerShell and bash/Azure CLI workflows.
- Clarify that all features and scripts are available cross-platform where applicable, and note any exceptions.
- Add a section or callout specifically addressing Linux/macOS users, with guidance on using Azure CLI and shell scripting.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/batch/tutorial-parallel-dotnet.md
.../blob/main//articles/batch/tutorial-parallel-dotnet.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Powershell Heavy
Summary
The documentation demonstrates a strong Windows bias. It exclusively uses Windows Server VM images for compute pools, Windows-specific ffmpeg binaries, and Windows command-line syntax (cmd /c). There are no examples or guidance for running the workload on Linux compute nodes, nor are Linux-compatible ffmpeg packages or shell commands discussed. The sample pool, job, and task names (e.g., WinFFmpegPool) reinforce the Windows-centric approach. While .NET Core is mentioned as cross-platform in prerequisites, all operational steps and code are tailored for Windows environments.
Recommendations
- Provide parallel Linux examples throughout, including pool creation with a Linux VM image and node agent SKU.
- Show how to use a Linux-compatible ffmpeg package (e.g., static build tar.gz or apt install) and reference it in the application package.
- Include Linux shell command-line syntax (e.g., bash -c './ffmpeg ...') for task command lines.
- Rename pools, jobs, and variables to be OS-neutral (e.g., FfmpegPool instead of WinFFmpegPool).
- Add notes or sections explaining differences and considerations for running on Linux vs. Windows compute nodes.
- Ensure screenshots and portal instructions are not specific to Windows pools only.
- Explicitly mention that Azure Batch supports both Windows and Linux, and link to documentation for both.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cdn/cdn-troubleshoot-compression.md
...lob/main//articles/cdn/cdn-troubleshoot-compression.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively mentioning Windows-centric tools (Fiddler, IIS) for troubleshooting and configuration, without referencing Linux alternatives or providing cross-platform guidance. All server-side configuration examples are for Microsoft IIS, and no Linux web server (e.g., Apache, Nginx) is mentioned. The only troubleshooting tool named is Fiddler, which is primarily a Windows application.
Recommendations
- Include Linux web server (e.g., Apache, Nginx) equivalents for compression configuration and troubleshooting, with links to relevant documentation.
- Mention and provide examples using cross-platform or Linux-native tools for inspecting HTTP headers, such as curl, wget, or command-line utilities.
- List Fiddler and browser developer tools as examples, but also suggest alternatives like Wireshark, tcpdump, or curl for Linux users.
- Ensure that troubleshooting steps and configuration advice are not limited to Windows/IIS environments, and provide parity for common Linux server scenarios.