13614
Pages Scanned
34
Pages Flagged
13614
Changed Pages
0.2%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
18:15:25
Scan Information
Started At: 2026-01-06 18:15:25
Finished At: 2026-01-07 06:09:36
Status: cancelled
Target Repo: Azure
Current Phase: discovery
Files Queued: 13808
Files Completed: 13614
Problematic Pages
34 issues found
Bastion
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/quickstart-host-portal.md
...s/blob/main/articles/bastion/quickstart-host-portal.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing Windows VM creation before Linux VM creation, mentioning Windows-specific ports and keyboard shortcuts in more detail, and providing examples and instructions that prioritize Windows scenarios. There is a lack of parity in Linux-specific examples, especially regarding keyboard shortcuts and connection details.
Recommendations
- Present Linux VM creation instructions before or alongside Windows instructions to avoid 'windows_first' bias.
- Include Linux-specific connection details, such as keyboard shortcuts for common tasks when connecting to Linux VMs via Bastion.
- Expand the section on required VM inbound ports to provide equal detail for Linux (e.g., mention SSH configuration nuances).
- Add troubleshooting tips or examples for connecting to Linux VMs, similar to those provided for Windows VMs.
- Ensure that all examples and tables provide Linux equivalents where applicable, not just Windows-focused values or instructions.
Create Pull Request
Bastion
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/work-remotely-support.md
...cs/blob/main/articles/bastion/work-remotely-support.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates Windows bias by listing PowerShell as a primary configuration method before Azure CLI, which is more commonly used on Linux/macOS. No explicit Linux or SSH examples are provided, and Windows-centric tools (PowerShell) are mentioned without equivalent Linux command-line or shell examples. The page lacks references to Linux remote access patterns or tools, and does not mention SSH clients or Linux desktop environments for remote work.
Recommendations
- Add explicit Linux/SSH examples for accessing Azure Bastion and managing VMs.
- Mention Linux command-line tools (e.g., SSH, Azure CLI) alongside or before PowerShell.
- Provide step-by-step instructions for configuring Azure Bastion from Linux/macOS environments.
- Include references to Linux desktop remote access tools (e.g., Remmina, xfreerdp) where appropriate.
- Ensure parity in troubleshooting and FAQ sections for both Windows and Linux users.
Bastion
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/shareable-link.md
...zure-docs/blob/main/articles/bastion/shareable-link.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
powershell_heavy
Summary
The documentation page demonstrates Windows bias by exclusively referencing the Azure portal UI and PowerShell cmdlets for permissions management, with no mention of Linux equivalents (such as Azure CLI or Bash). All examples and screenshots are based on the Azure portal, which is most commonly used on Windows, and there are no instructions or examples for Linux users or command-line alternatives. The permissions section lists only PowerShell cmdlets, omitting Azure CLI or REST API options that are platform-agnostic.
Recommendations
- Add Azure CLI examples for enabling, creating, and deleting shareable links, alongside PowerShell cmdlets.
- Include instructions and screenshots for using the Azure portal on Linux (if any differences exist), or clarify platform neutrality.
- Document REST API methods for managing shareable links to provide platform-independent options.
- Explicitly mention that the Azure portal and Bastion shareable links are accessible from browsers on any OS, not just Windows.
- Provide SSH examples for Linux users connecting to VMs via Bastion, if applicable.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-applications-to-pool-nodes.md
...ain/articles/batch/batch-applications-to-pool-nodes.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation page exhibits Windows bias by referencing Windows-specific installation patterns (e.g., .exe and .msi files) and omitting Linux equivalents (such as .sh scripts or .deb/.rpm packages). There are no examples or mentions of Linux tools, file formats, or installation commands. Windows terminology and scenarios are presented first and exclusively, with no parity for Linux users.
Recommendations
- Include Linux-specific examples alongside Windows ones, such as using shell scripts (.sh), tarballs, or package managers (apt, yum) for installation.
- Mention Linux file formats and installation patterns (e.g., .deb, .rpm, chmod +x, bash install.sh) when discussing application deployment.
- Provide parallel examples for both Windows and Linux in sections describing start tasks, job preparation, and resource files.
- Avoid using Windows-centric language exclusively (e.g., .msi, .exe) and clarify that Azure Batch supports both Windows and Linux nodes.
- Add guidance on handling permissions and execution on Linux nodes (e.g., setting executable bit, using sudo).
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/accounts.md
...ftDocs/azure-docs/blob/main/articles/batch/accounts.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates Windows bias by referencing Windows-centric tools and workflows, such as the Azure portal and Batch Management .NET library, without mentioning Linux equivalents (e.g., Azure CLI, REST API, or Python SDK). There are no examples or instructions for creating or managing Batch accounts from Linux environments, nor is there mention of Linux-specific tooling or patterns. The documentation implicitly prioritizes Windows approaches and omits guidance for Linux users.
Recommendations
- Include examples for creating and managing Batch accounts using cross-platform tools such as Azure CLI, REST API, or Python SDK.
- Explicitly mention Linux compatibility and provide instructions or code samples that can be run on Linux systems.
- Balance references to Windows-specific tools (like .NET and Azure portal) with equivalent Linux-friendly options (such as Bash scripts, CLI commands, or Python).
- Add a section or callout highlighting cross-platform development and management options for Azure Batch accounts.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/access-tokens.md
...ob/main/articles/active-directory-b2c/access-tokens.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates Windows bias by explicitly recommending Microsoft PowerShell as the example HTTP client for testing the POST request, without mentioning any Linux or cross-platform alternatives (such as curl or HTTPie). The only tool suggestion is Windows-centric and appears before any mention of Linux equivalents, which are absent. No Linux-specific or cross-platform command-line examples are provided for making token requests.
Recommendations
- Include examples using curl and/or HTTPie for making HTTP requests, which are available on both Linux and Windows.
- Mention cross-platform tools before or alongside Windows-specific tools like PowerShell.
- Provide sample commands for Linux/macOS environments to ensure parity and inclusivity.
- Clarify that any HTTP client can be used, and list several options for different operating systems.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/client-credentials-grant-flow.md
.../active-directory-b2c/client-credentials-grant-flow.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation page demonstrates Windows bias in several areas. The instructions for generating a GUID mention Microsoft PowerShell first and provide a PowerShell command, with only a secondary reference to an online GUID generator. In the scripting section, the PowerShell example is presented before the cURL (Linux/macOS) example. There are no explicit Linux shell or CLI examples for generating GUIDs or interacting with Azure, and Windows-centric tools and patterns (PowerShell, Azure Portal screenshots) are referenced without Linux equivalents.
Recommendations
- Provide Linux and macOS equivalents for all command-line instructions, such as using 'uuidgen' for GUID generation.
- Present cURL (Linux/macOS) examples before or alongside PowerShell examples to avoid Windows-first ordering.
- Explicitly mention cross-platform tools (e.g., Azure CLI) and provide examples for both Windows and Linux environments.
- Include screenshots or instructions that are platform-neutral or show both Windows and Linux interfaces where relevant.
- Reference Linux shell commands and utilities where applicable, not just Windows/PowerShell tools.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/apache-hadoop-connect-excel-power-query.md
...ight/hadoop/apache-hadoop-connect-excel-power-query.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation is heavily focused on Windows environments, requiring a Windows workstation and Microsoft Excel. All instructions and examples are tailored to Windows and Microsoft Office products, with no mention of Linux-compatible alternatives for connecting to HDInsight or accessing Hadoop data. The prerequisites and step-by-step guides exclusively reference Windows operating systems and tools, omitting any guidance for Linux users.
Recommendations
- Provide equivalent instructions for Linux users, such as using LibreOffice Calc, OpenOffice, or other BI tools available on Linux to connect to HDInsight.
- Include examples of accessing HDInsight data from Linux workstations, possibly via Python (pandas, pyodbc), R, or command-line tools.
- Mention cross-platform alternatives to Power Query, or clarify that the described method is Windows-only and suggest Linux-compatible workflows.
- Add a section comparing Windows and Linux approaches to connecting to HDInsight, ensuring parity in documentation.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hbase/apache-hbase-rest-sdk.md
...main/articles/hdinsight/hbase/apache-hbase-rest-sdk.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates Windows bias by exclusively providing installation instructions using the Visual Studio NuGet Package Manager Console (a Windows-centric tool), omitting Linux-specific installation guidance. All code examples are in C#/.NET, which is most commonly used on Windows, and there are no references to Linux development environments, cross-platform .NET usage, or alternative package managers. The documentation does not mention how to use the SDK from Linux, nor does it provide parity for Linux users in terms of setup or tooling.
Recommendations
- Add instructions for installing the NuGet package using the dotnet CLI (cross-platform) and/or Mono for Linux environments.
- Explicitly mention that the .NET SDK can be used on Linux and provide setup steps for Linux users, including prerequisites (e.g., .NET Core/SDK installation).
- Include example commands for Linux shells (bash/zsh) and clarify that the SDK is not limited to Visual Studio or Windows.
- Reference cross-platform development environments (e.g., VS Code, JetBrains Rider) alongside Visual Studio.
- Add a note or section on running the sample code on Linux, including any platform-specific considerations.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/apache-hadoop-etl-at-scale.md
...rticles/hdinsight/hadoop/apache-hadoop-etl-at-scale.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page exhibits a Windows bias in several ways. Data ingestion into Azure Storage is described as typically performed via PowerShell, the Azure Storage SDK, or AzCopy, all of which are Windows-centric tools, with no mention of Linux-native alternatives or CLI usage. Windows tools and patterns (PowerShell, AzCopy) are mentioned before any Linux equivalents, and Linux-specific examples or workflows are missing throughout the page. The orchestration and ingestion sections prioritize Windows approaches, and there is little guidance for Linux users on performing equivalent tasks.
Recommendations
- Include Linux-native CLI examples for data ingestion, such as using Azure CLI, curl, or Python scripts.
- Mention and provide examples for cross-platform tools (e.g., Azure CLI, REST API) alongside PowerShell and AzCopy.
- Add explicit Linux and macOS usage instructions or references for all major workflows, especially in sections currently focused on Windows tools.
- Ensure that examples and tool recommendations are presented in a platform-neutral order, or grouped by OS, rather than Windows-first.
- Reference documentation pages that specifically address Linux/macOS scenarios where available.
Static Web Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/static-web-apps/database-mysql.md
...s/blob/main/articles/static-web-apps/database-mysql.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page demonstrates a moderate Windows bias. Azure Data Studio (a Microsoft tool, primarily Windows-focused) is recommended first for MySQL management, with MySQL Workbench only mentioned as an alternative. Command examples are consistently provided for both Bash and PowerShell, but PowerShell is always presented alongside Bash, rather than offering Linux-specific alternatives (e.g., native Linux tools or workflows). The use of Azure Data Studio and the Azure portal (both Microsoft-centric tools) is emphasized throughout, with no mention of Linux-native database management tools (such as the mysql CLI or Linux desktop clients) or Linux-specific configuration steps. There are no explicit Linux examples or guidance for Linux users, and the workflow assumes familiarity with Windows tooling and patterns.
Recommendations
- Provide explicit Linux examples and workflows, such as using the mysql CLI for database management and querying, and instructions for configuring environment variables in Linux shells (e.g., Bash, Zsh) without referencing PowerShell.
- List Linux-native tools (e.g., DBeaver, mysql CLI) as first-class options for database management, not just as alternatives.
- Include screenshots and instructions for Linux environments (e.g., Ubuntu, Fedora) when demonstrating Azure portal or CLI usage.
- Clarify any platform-specific differences in steps (such as file paths, environment variable syntax, or CLI installation commands) for Linux users.
- Consider adding a 'Platform considerations' section that highlights differences and best practices for both Windows and Linux users.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/authorize-access-azure-active-directory.md
...orage/blobs/authorize-access-azure-active-directory.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by consistently mentioning PowerShell before Azure CLI when discussing command-line access, and by referencing PowerShell as a primary tool for data access. There are no explicit Linux-specific examples or references to Linux-native tools, and the documentation does not provide parity in examples or instructions for Linux users. The focus on PowerShell and lack of Linux examples may make it less accessible for users on Linux platforms.
Recommendations
- Ensure that Azure CLI examples are presented before or alongside PowerShell examples, as Azure CLI is cross-platform and widely used on Linux.
- Include explicit Linux usage instructions and examples, such as shell commands for authentication and data access.
- Reference Linux-native tools (e.g., curl, azcopy) where appropriate, and provide sample commands for these tools.
- Clarify that PowerShell is available on Linux, but also highlight alternatives that are more common in Linux environments.
- Add a section or callouts for Linux users, describing any platform-specific considerations or best practices.
Storage Mover
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-mover/project-manage.md
...ocs/blob/main/articles/storage-mover/project-manage.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell examples for command-line operations, with no mention of Linux-native tools, Bash, or Azure CLI. All automation and scripting instructions use PowerShell cmdlets and installation steps, which are primarily Windows-centric. There are no Linux or cross-platform command-line examples, and PowerShell is presented as the default/only scripting option, despite Azure CLI being widely used on Linux and macOS.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell cmdlets, showing how to create, view, edit, and delete Storage Mover projects using az commands.
- Include Bash shell scripting examples where appropriate, especially for variable assignment and command chaining.
- Explicitly state cross-platform support for Azure CLI and PowerShell, and clarify installation steps for Linux and macOS users.
- Reorder examples to present Azure CLI (cross-platform) before PowerShell, or provide both side-by-side.
- Mention that Azure PowerShell is available on Linux/macOS, but highlight Azure CLI as the more native choice for those platforms.
Storage Mover
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-mover/troubleshooting.md
...cs/blob/main/articles/storage-mover/troubleshooting.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates Windows bias by referencing Windows tools and patterns first and exclusively. It mentions that a secure FTP client is installed on most typical Windows instances, and recommends WinRAR (a Windows tool) for extracting Zstandard archives, without mentioning Linux equivalents. There are no examples or instructions for Linux users, such as using native Linux tools (e.g., scp, sftp, tar, zstd), nor is there guidance for Linux environments, despite the agent logs referencing Linux-style commands and file structures.
Recommendations
- Include instructions and examples for Linux users, such as using scp or sftp to retrieve the support bundle.
- Recommend Linux-native tools for extracting Zstandard archives, such as the 'zstd' and 'tar' command-line utilities.
- Avoid assuming the host is Windows; provide parity for Linux and macOS hosts.
- List both Windows and Linux tools side-by-side when discussing prerequisites.
- Explicitly mention how to perform each step on Linux, including command syntax and package installation if needed.
Static Web Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/static-web-apps/database-postgresql.md
...b/main/articles/static-web-apps/database-postgresql.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation demonstrates a moderate Windows bias. Azure Data Studio (a Microsoft/Windows-centric tool) is presented as the primary tool for interacting with PostgreSQL, with PgAdmin only briefly mentioned as an alternative. Command-line examples are provided for both Bash and PowerShell, but PowerShell is given equal prominence, which may not reflect the usage patterns of Linux/macOS developers. The instructions for configuring the database and accessing the Azure portal are written from a perspective familiar to Windows users, with no mention of Linux-specific tools or workflows (e.g., psql, Linux desktop environments, or CLI-only workflows).
Recommendations
- Provide explicit examples using Linux-native tools such as psql for database creation and querying, alongside Azure Data Studio and PgAdmin.
- Clarify that Azure Data Studio is cross-platform, and offer installation instructions for Linux and macOS users.
- Include screenshots and instructions for Linux desktop environments (e.g., GNOME, KDE) when referencing GUI tools.
- When listing command-line examples, consider listing Bash first and PowerShell second, or clarify which is most common for Linux/macOS users.
- Add a section or note on using the Azure CLI for portal-related steps, as many Linux users prefer CLI workflows.
- Ensure parity in troubleshooting and cleanup instructions for Linux environments (e.g., using psql to drop tables).
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/blob-cli.md
...zure-docs/blob/main/articles/storage/blobs/blob-cli.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by consistently using Windows-style file paths (e.g., C:\temp\) in all code samples, even though the examples are written in Bash and intended for cross-platform use. There are no Linux or macOS-specific path examples, nor is there any mention of Linux file system conventions. Additionally, instructions for creating or referencing files (such as the XML file for blob tags) assume a Windows directory structure and do not provide Linux alternatives.
Recommendations
- Provide both Windows and Linux/macOS path examples in all code samples, e.g., use C:\temp\ for Windows and /tmp/ or ~/temp/ for Linux/macOS.
- Explicitly mention that the Bash scripts are cross-platform and note any platform-specific considerations (such as path separators).
- When referencing files to be created locally (e.g., blob-list.xml), include instructions for both Windows and Linux/macOS environments.
- Add a note at the beginning of the article clarifying that examples are intended to work on all platforms, and highlight any differences users should be aware of.
- Where applicable, show how to run the Azure CLI commands in PowerShell, Bash (Linux/macOS), and Windows Command Prompt, or at least provide links to platform-specific guidance.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-pools-to-simplified-compute-node-communication-model-migration-guide.md
...ified-compute-node-communication-model-migration-guide.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates subtle Windows bias by mentioning RDP connectivity before SSH in the FAQ section and by not providing explicit Linux-specific examples or instructions. While both Linux and Windows are referenced in the context of agent binaries, practical guidance (e.g., how to connect for diagnostics) is presented in a Windows-first order and lacks Linux parity in terms of example commands or troubleshooting steps.
Recommendations
- Present SSH connectivity before or alongside RDP in diagnostic connection instructions to avoid Windows-first ordering.
- Include explicit Linux examples, such as SSH command-line usage or troubleshooting steps for Linux nodes.
- Provide parity in agent binary references, e.g., clarify the usage and location of agent binaries on both Linux and Windows.
- Add Linux-specific networking configuration guidance where relevant, such as firewall or outbound access setup.
Bastion
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/vm-about.md
...Docs/azure-docs/blob/main/articles/bastion/vm-about.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates Windows bias by referencing Windows-specific features and examples before Linux equivalents. For instance, the copy/paste section links only to 'Copy and paste - Windows VMs', with no mention of Linux VM support or guidance. There is also a general lack of explicit Linux examples or parity in feature descriptions, suggesting Windows is the primary platform considered.
Recommendations
- Add equivalent documentation and links for Linux VM features, such as copy/paste functionality for Linux VMs.
- Ensure that examples and feature descriptions mention both Windows and Linux platforms where applicable.
- Where features differ between Windows and Linux, provide clear guidance and links for both.
- Review linked articles (e.g., for file transfer, audio) to confirm Linux support is documented and referenced from this page.
Bastion
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/private-only-deployment.md
.../blob/main/articles/bastion/private-only-deployment.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exclusively describes deployment using the Azure portal UI, which is platform-agnostic, but does not provide any command-line examples. There is no mention of PowerShell, Azure CLI, or any OS-specific tools. However, the lack of CLI examples means that users who prefer or require Linux-based workflows (e.g., Azure CLI on Bash) are not served. The documentation implicitly assumes a graphical workflow, which is more common on Windows, and does not address Linux parity or automation scenarios.
Recommendations
- Add Azure CLI command examples for deploying Bastion in private-only mode, suitable for Linux/macOS users.
- If PowerShell examples are added in the future, ensure Azure CLI (Bash) equivalents are provided and presented with equal prominence.
- Explicitly mention that the Azure portal is accessible from any OS, and link to CLI-based documentation for users who prefer command-line automation.
- Include a section on automating Bastion deployment using scripts, with examples for both PowerShell and Bash/Azure CLI.
Bastion
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/bastion-vm-copy-paste.md
...cs/blob/main/articles/bastion/bastion-vm-copy-paste.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exclusively discusses copying and pasting to and from Windows virtual machines, with no mention of Linux VMs or their specific requirements. All examples, prerequisites, and instructions are tailored to Windows, potentially excluding users who need guidance for Linux VM scenarios.
Recommendations
- Add a dedicated section for Linux VMs, outlining any differences in clipboard support or configuration when using Azure Bastion.
- Include Linux-specific examples and instructions, such as how to copy and paste in common Linux desktop environments (e.g., GNOME, KDE) or terminal sessions.
- Clarify whether the Bastion clipboard feature works identically for Linux VMs, and note any limitations or additional steps required.
- Ensure parity in screenshots and tool references, showing the experience on both Windows and Linux VMs.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/authorization-code-flow.md
...ticles/active-directory-b2c/authorization-code-flow.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page is generally platform-neutral in its HTTP request examples and explanations. However, there is a subtle Windows bias: when suggesting tools for testing HTTP requests, only Microsoft PowerShell is mentioned, with no reference to Linux-native tools (such as curl or wget). This may lead Linux users to feel unsupported or unsure about how to perform these actions on their platform.
Recommendations
- When suggesting HTTP clients for testing requests, mention cross-platform tools such as curl, wget, or httpie alongside PowerShell.
- Provide example commands for both Windows (PowerShell) and Linux/macOS (curl, wget) when demonstrating how to send HTTP requests.
- Explicitly state that the instructions and examples are applicable on any platform, and link to documentation for popular Linux tools where appropriate.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/b2c-global-identity-proof-of-concept-regional.md
...y-b2c/b2c-global-identity-proof-of-concept-regional.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a subtle Windows bias by referencing API protection instructions with a link that explicitly uses the 'windows' tab (secure-rest-api.md?tabs=windows), without mention of Linux or cross-platform alternatives. There are no examples or instructions for Linux, Bash, or cross-platform tooling; all references to command-line or environment setup are either generic or point to Windows-specific documentation. No PowerShell scripts or Windows-only tools are present, but the guidance does not provide parity for Linux users.
Recommendations
- Update all links to API protection or setup guides to include both Windows and Linux tabs, or use a neutral/default tab.
- Explicitly mention that the process can be performed on Linux and provide equivalent Bash or CLI examples where relevant.
- Add a note or section for Linux users, outlining any differences or confirming parity in steps and tools.
- Ensure all referenced documentation (e.g., secure-rest-api.md) is cross-platform and does not default to Windows unless necessary.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/configure-authentication-sample-web-app.md
...rectory-b2c/configure-authentication-sample-web-app.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a bias toward Windows environments by exclusively referencing Visual Studio and Visual Studio Code as development environments, without mentioning Linux-specific tools or workflows. There are no explicit Linux setup or run instructions, nor any examples of using Linux-native editors or command-line tools. The sample application and instructions are tailored to ASP.NET, which is cross-platform, but the documentation does not provide parity for Linux users in terms of environment setup or usage.
Recommendations
- Add explicit instructions for setting up and running the sample on Linux, including installation of .NET SDK on Linux distributions.
- Include examples using Linux-native editors (e.g., Vim, Emacs) or command-line workflows.
- Mention cross-platform compatibility of ASP.NET Core and clarify that the sample can be run on Linux and macOS, not just Windows.
- Provide troubleshooting tips for common Linux issues (e.g., file permissions, HTTPS certificate setup for localhost).
- List Linux prerequisites (e.g., apt-get install dotnet-sdk-6.0) alongside Windows instructions.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/configure-authentication-in-azure-web-app-file-based.md
...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/configure-authentication-in-azure-web-app-file-based.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_first
Summary
The documentation page focuses on configuring Azure AD B2C authentication for Azure Web Apps but implicitly prioritizes Windows environments. It references Azure Web Apps using .NET Core (commonly associated with Windows), and all example URLs and instructions use the default Azure Web App domain (azurewebsites.net), which is more familiar to Windows users. There are no explicit Linux or cross-platform examples, nor are Linux-specific tools or deployment patterns mentioned. The instructions for configuring application settings mention the Azure portal and Azure CLI but do not provide CLI examples or clarify cross-platform usage. No mention is made of Linux-specific configuration files, deployment methods, or troubleshooting steps.
Recommendations
- Include explicit Linux examples for configuring Azure Web App authentication, such as using Linux-based runtimes or deployment methods.
- Provide Azure CLI commands for all configuration steps, ensuring they work on both Windows and Linux shells.
- Mention and demonstrate how to edit configuration files and manage secrets on Linux-based Azure Web Apps.
- Add troubleshooting tips for common Linux-specific issues (e.g., file permissions, environment variables).
- Clarify that the instructions apply to both Windows and Linux App Service plans, or specify any differences.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/configure-authentication-in-azure-web-app.md
...ctory-b2c/configure-authentication-in-azure-web-app.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation consistently references Azure Web Apps using the default Azure domain (azurewebsites.net), which is typically associated with Windows-based hosting, and does not mention Linux-specific hosting options or provide any Linux-specific configuration guidance. There are no examples or instructions for Linux environments, nor are Linux tools or patterns referenced. All steps are described in a platform-neutral way but implicitly assume Windows defaults, and there is no parity for Linux users or explicit mention of Linux App Service plans.
Recommendations
- Explicitly mention both Windows and Linux hosting options for Azure Web Apps, including any differences in authentication configuration.
- Provide examples or notes for configuring authentication in Azure Web Apps running on Linux, including any relevant settings or troubleshooting tips.
- Reference Linux-specific documentation or tools where appropriate, such as command-line configuration using Bash or Azure CLI on Linux.
- Clarify that the instructions apply to both Windows and Linux App Service plans, or highlight any platform-specific considerations.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/configure-authentication-sample-python-web-app.md
...-b2c/configure-authentication-sample-python-web-app.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation page demonstrates mild Windows bias. In the 'Run the sample web app' section, the Windows instructions are presented after Linux and macOS, but the Windows-specific command ('py' instead of 'python') is called out. Additionally, the note about path length limitations ("Extract the sample file to a folder where the total length of the path is 260 or fewer characters") is a Windows-specific constraint, but it is not explicitly labeled as such, potentially confusing Linux/macOS users for whom this limitation does not apply.
Recommendations
- Clearly label Windows-specific instructions and constraints, such as the path length limitation, and provide context for non-Windows users.
- Where possible, provide parity in examples and troubleshooting notes for Linux/macOS (e.g., mention that the path length limitation does not apply on those platforms).
- Consider listing Linux/macOS instructions first if the audience is cross-platform, or alternate the order in different sections.
- Ensure that any platform-specific commands (e.g., 'py' vs 'python') are explained, and provide guidance for users who may not have 'py' installed on Windows.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/configure-authentication-sample-web-app-with-api.md
...2c/configure-authentication-sample-web-app-with-api.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a bias towards Windows environments by referencing Visual Studio (a Windows-first IDE) before Visual Studio Code, and by omitting explicit instructions or examples for running the sample application on Linux (e.g., using the dotnet CLI or Linux-specific setup steps). There are no PowerShell-heavy examples or exclusive use of Windows tools, but the lack of Linux parity in setup and run instructions is notable.
Recommendations
- Add explicit instructions for running the sample on Linux, including using the dotnet CLI (e.g., 'dotnet build', 'dotnet run') instead of relying solely on Visual Studio/Visual Studio Code.
- Include notes about installing .NET SDK on Linux distributions and any required dependencies.
- Provide troubleshooting tips for common Linux-specific issues (e.g., file permissions, HTTPS certificate trust for localhost).
- Ensure screenshots and examples do not assume the use of Windows-only tools or interfaces.
- Consider listing Visual Studio Code and CLI instructions before or alongside Visual Studio to avoid Windows-first ordering.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hbase/apache-hbase-replication.md
...n/articles/hdinsight/hbase/apache-hbase-replication.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation is generally Linux-focused, with Ubuntu VMs and Bash/SSH commands used throughout. However, there is a notable Windows bias in the section describing how to obtain the SSH utility: Windows options are listed separately and before Linux/macOS, and several Windows-specific tools (Azure Cloud Shell, Bash on Ubuntu on Windows, Git for Windows, OpenSSH for Windows) are mentioned. This may suggest to readers that Windows is a primary platform, despite the actual setup being Linux-based.
Recommendations
- Present Linux/macOS instructions and tools before Windows-specific options when describing cross-platform utilities like SSH.
- Clarify that the main environment for HDInsight HBase replication is Linux, and that Windows instructions are supplementary for users who happen to be on Windows.
- For parity, provide explicit instructions for Linux and macOS users first, then add a separate note for Windows users.
- Avoid listing Windows tools in a way that implies they are required or preferred for the workflow, especially when the main environment is Linux.
- Where possible, link to cross-platform documentation or note that most commands are identical across Linux, macOS, and Windows (with WSL or similar).
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hbase/apache-hbase-provision-vnet.md
...rticles/hdinsight/hbase/apache-hbase-provision-vnet.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation demonstrates Windows bias by exclusively referencing Windows in the virtual machine creation instructions ("Create a Virtual Machine Running Windows Server") and omitting equivalent Linux VM creation steps or links. The example for verifying communication uses generic commands (ping), but the VM creation section is Windows-centric and does not provide parity for Linux users.
Recommendations
- Add instructions and links for creating a Linux-based virtual machine in Azure, such as Ubuntu or CentOS, alongside the Windows VM example.
- Present both Windows and Linux VM creation options in parallel, or mention Linux first to avoid implicit prioritization of Windows.
- Ensure that subsequent steps (such as connecting, verifying communication, and using tools) include Linux-specific guidance where appropriate.
- Review all referenced links to ensure Linux equivalents are provided wherever Windows-specific documentation is cited.
Static Web Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/static-web-apps/database-azure-sql.md
...ob/main/articles/static-web-apps/database-azure-sql.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for command-line steps, but consistently lists Bash first, then PowerShell. There is no evidence of exclusive use of Windows tools or missing Linux examples; however, the presence of PowerShell examples throughout and the explicit tabbing for PowerShell indicates a slight Windows bias. The Azure Portal instructions are platform-neutral, but the CLI instructions could be improved for Linux parity.
Recommendations
- Explicitly mention that all CLI steps work on Linux, macOS, and Windows, and clarify any platform-specific differences if they exist.
- Consider including a brief note or section for users on Linux/macOS, confirming that Bash instructions are applicable and that no additional steps are required.
- If any steps have platform-specific caveats (e.g., environment variable syntax, npm installation), highlight these in a dedicated 'Platform differences' note.
- Ensure that screenshots and UI references do not imply a Windows-only environment.
- If possible, add a table or summary at the start of the CLI section indicating supported platforms for each command.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-blob-container-lease.md
...articles/storage/blobs/storage-blob-container-lease.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page is focused exclusively on .NET and C#, which are commonly associated with Windows development. All code examples are in C#, and there is no mention of Linux-specific tools, patterns, or alternative SDKs (such as Python, Java, or CLI usage on Linux). There are no instructions or examples for setting up or running the code on Linux, nor any discussion of cross-platform considerations. The page implicitly assumes a Windows/.NET development environment.
Recommendations
- Add explicit instructions for running .NET code and setting up the environment on Linux, including installation of the .NET SDK on Linux distributions.
- Provide code examples or links for other languages/platforms commonly used on Linux (e.g., Python, Java, Node.js).
- Include guidance for using Azure CLI or REST API directly from Linux shells (bash), demonstrating lease management operations.
- Mention cross-platform compatibility of the Azure Storage .NET SDK and clarify any OS-specific considerations.
- Add troubleshooting or FAQ sections for Linux users (e.g., common permission or environment issues).
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-blob-container-properties-metadata.md
...ge/blobs/storage-blob-container-properties-metadata.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page exclusively provides .NET/C# examples and setup instructions, which are most commonly associated with Windows environments. There are no Linux-specific instructions, examples, or mentions of cross-platform considerations (such as Mono or .NET Core on Linux). The setup and code snippets assume a Windows-centric development workflow, and do not address Linux users or alternative tooling.
Recommendations
- Add explicit instructions for setting up the .NET client library on Linux, including installation of .NET SDK and any platform-specific dependencies.
- Include code examples and console output that demonstrate usage on Linux (e.g., bash shell, Linux terminal).
- Mention cross-platform compatibility of the .NET client library, clarifying that the examples work on Linux and macOS as well as Windows.
- Reference Linux-friendly editors (such as VS Code) and command-line tools in the setup section.
- Provide troubleshooting tips or notes for common Linux-specific issues (such as file permissions or environment variables).
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/blob-storage-estimate-costs.md
.../articles/storage/blobs/blob-storage-estimate-costs.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation page consistently references AzCopy as the canonical tool for data transfer and cost estimation, but does not mention or provide examples for Linux-native alternatives (such as Azure CLI, REST API via curl, or third-party tools). There are no command-line examples or usage patterns shown for Linux environments, and the documentation does not address cross-platform usage or parity, implicitly favoring Windows tooling and workflows.
Recommendations
- Include examples using Azure CLI and REST API (e.g., with curl) for cost estimation and data operations, showing commands that work natively on Linux and macOS.
- Explicitly mention that AzCopy is cross-platform and provide installation and usage instructions for Linux and macOS, not just Windows.
- Add references to other popular Linux tools (such as rclone) that can interact with Azure Blob Storage, and discuss their cost implications.
- Ensure that any sample scripts or automation patterns are shown in both PowerShell and Bash (or POSIX shell) formats.
- Add a section or note clarifying platform compatibility for all recommended utilities and workflows.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-blob-containers-list.md
...articles/storage/blobs/storage-blob-containers-list.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_first
Summary
The documentation page exclusively provides .NET (C#) examples and setup instructions, which are most commonly associated with Windows environments. There is no mention of Linux-specific setup, usage patterns, or alternative code examples (e.g., for .NET on Linux, Bash, or cross-platform CLI usage). The documentation implicitly assumes a Windows-first perspective by not acknowledging Linux or cross-platform development scenarios.
Recommendations
- Add explicit instructions or notes for running .NET code and setting up the environment on Linux (e.g., using .NET Core on Ubuntu).
- Include code examples or CLI commands that demonstrate listing blob containers using Bash or Azure CLI, which are commonly used on Linux.
- Reference cross-platform compatibility of the .NET client library and provide troubleshooting tips for Linux users.
- Mention any platform-specific considerations (such as authentication or environment variables) for Linux.
- Ensure that examples and setup steps do not assume Windows-only tools or patterns (e.g., Visual Studio, PowerShell) and provide alternatives for Linux (e.g., VS Code, Bash).