← Back to Dashboard
13828
Pages Scanned
420
Pages Flagged
13828
Changed Pages
3.0%
% Pages Flagged

Scan Information

Started At: 2026-01-10 00:00:06

Finished At: 2026-01-10 20:08:25

Status: completed

Target Repo: Azure

Current Phase: discovery

Files Queued: 13828

Files Completed: 13828

Problematic Pages

420 issues found
Active Directory B2C Manage directory size quota in Azure Active Directory B2C ...ive-directory-b2c/tenant-management-directory-quota.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides only a PowerShell script for monitoring directory quota usage, which is specific to Windows environments. There are no examples or instructions for Linux or cross-platform alternatives (such as Bash, curl, or Python). This may hinder users on Linux or macOS from easily following the tutorial.
Recommendations
  • Add equivalent Linux/macOS examples using Bash and curl or Python (e.g., using curl for token acquisition and API calls).
  • Explicitly mention that the PowerShell script is for Windows and provide cross-platform alternatives.
  • Consider using platform-neutral tools (like Azure CLI or REST API examples) where possible.
  • Add a section on troubleshooting or adapting the instructions for non-Windows environments.
GitHub Create Pull Request
Active Directory B2C Define an ID token hint technical profile in a custom policy ...ob/main/articles/active-directory-b2c/id-token-hint.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias, especially in the 'How-to guide' sections for generating symmetric and asymmetric keys. PowerShell is exclusively used for key and certificate generation, with no mention of Linux or cross-platform alternatives. Windows tools and patterns are referenced first and exclusively, and there are no examples or instructions for performing these tasks on Linux or macOS.
Recommendations
  • Add equivalent Linux/macOS instructions for key and certificate generation, such as using OpenSSL for both symmetric key and self-signed certificate creation.
  • Provide cross-platform code samples (e.g., bash scripts, OpenSSL commands) alongside PowerShell examples.
  • Explicitly mention that the steps can be performed on non-Windows platforms and link to relevant external documentation for Linux/macOS users.
  • Ensure that references to platform-specific tools (like PowerShell) are balanced with alternatives for other operating systems.
GitHub Create Pull Request
App Service Use Private Endpoints for Apps ...main/articles/app-service/overview-private-endpoint.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a mild Windows bias. Windows is mentioned first in the list of supported platforms for private endpoints, and the related content section lists Azure PowerShell as a primary method for creating private endpoints, with no explicit Linux shell or Bash examples. The use of Windows-centric terminology and tools (e.g., PowerShell, references to Windows DNS patterns) is more prominent than Linux equivalents, and Linux-specific instructions or examples are missing or less visible.
Recommendations
  • Explicitly provide Linux/Bash examples alongside PowerShell, especially in quickstart and scripting sections.
  • List Linux and Windows platforms together or alternate their order to avoid Windows-first perception.
  • Include references to Linux-native tools and workflows (e.g., Bash, curl, dig for DNS) where relevant.
  • Clarify that all CLI instructions (e.g., Azure CLI) are cross-platform, and provide sample commands for both Windows and Linux environments.
  • Add troubleshooting notes or examples for common Linux scenarios (e.g., modifying /etc/hosts, using Linux DNS tools).
GitHub Create Pull Request
App Service Quickstart: Run a Custom Container on App Service ...in/articles/app-service/quickstart-custom-container.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page displays a Windows bias by listing Windows-specific pivots (Visual Studio, PowerShell, CLI) before their Linux equivalents, and by providing dedicated sections for Windows tools (PowerShell, Visual Studio) while Linux pivots are limited to Visual Studio Code and Azure Portal. There is no mention of Linux command-line or shell examples (e.g., Bash), and Windows tooling (PowerShell, Visual Studio) is given more prominence and variety than Linux alternatives.
Recommendations
  • Add Linux shell (Bash) and CLI examples alongside Windows PowerShell and CLI pivots.
  • Ensure Linux pivots are presented with equal prominence and order as Windows pivots.
  • Include Linux-native tools and workflows (e.g., Docker CLI, Bash scripts) in the quickstart.
  • Provide parity in the number and detail of examples for both Windows and Linux environments.
  • Review and balance the use of platform-specific terminology and tooling throughout the documentation.
GitHub Create Pull Request
App Service Overview of Azure App Service .../azure-docs/blob/main/articles/app-service/overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias, especially in the 'Managed Instance on App Service (preview)' section, which focuses exclusively on Windows-specific technologies (COM, registry, MSI, drive mapping, PowerShell scripts, RDP). Windows tools and patterns (PowerShell, RDP, registry, drive letters) are mentioned without Linux equivalents or alternatives. Linux and container support are only referenced as not supported in Managed Instance, and no Linux-specific examples, tools, or patterns are provided elsewhere on the page.
Recommendations
  • Provide Linux-specific examples and scenarios, especially for deployment, configuration, and diagnostics.
  • Mention Linux tools (e.g., Bash, SSH, systemd) alongside Windows tools like PowerShell and RDP.
  • Clarify which features are available on Linux and how to achieve similar outcomes (e.g., startup scripts, diagnostics) on Linux-based App Service plans.
  • Include parity tables or explicit guidance for Linux users where features differ or are unavailable.
  • Ensure that command-line tool references (Azure CLI, Azure PowerShell) include both Windows and Linux usage patterns.
GitHub Create Pull Request
Automanage Tutorial - python ...ticles/automanage/tutorial-create-assignment-python.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ powershell_heavy
Summary
The documentation demonstrates a Windows bias by exclusively providing examples for creating Windows virtual machines, omitting Linux VM creation steps. Both Azure CLI and PowerShell instructions are included, but PowerShell is a Windows-centric tool. There are no Linux-specific commands, nor is there mention of creating or managing Linux VMs, which are common in Azure environments.
Recommendations
  • Add examples for creating Linux virtual machines using both Azure CLI and PowerShell, e.g., using --image UbuntuLTS.
  • Explicitly mention Linux support and provide guidance for Linux VM scenarios.
  • Include Linux shell (bash) command examples where relevant, not just PowerShell.
  • Balance the documentation by presenting Windows and Linux options side-by-side in all relevant sections.
GitHub Create Pull Request
Automation Disaster recovery for Azure Automation ...in/articles/automation/automation-disaster-recovery.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a Windows bias by exclusively providing PowerShell-based migration scripts and workflows, with no mention of Bash, Python, or other Linux-native scripting alternatives. The examples and instructions for Hybrid Runbook Worker installation and migration reference Windows tabs and steps first, and do not provide parity for Linux users. There is no guidance or sample code for Linux-centric automation or migration, despite the article stating applicability to both Linux and Windows VMs.
Recommendations
  • Provide equivalent Bash or Python scripts for migrating Automation account assets, suitable for Linux environments.
  • Include Linux-first or Linux-parallel tabs/examples in all step-by-step instructions, especially for Hybrid Runbook Worker installation and migration.
  • Document any Linux-specific modules, tools, or patterns for Azure Automation disaster recovery.
  • Clarify any differences in process or limitations for Linux users, and offer troubleshooting steps or best practices for Linux environments.
  • Ensure that all PowerShell instructions are accompanied by Linux-native alternatives where possible, or explicitly state if PowerShell Core is required and supported on Linux.
GitHub Create Pull Request
Automation Migrate from a Run As account to Managed identities ...automation/migrate-run-as-accounts-managed-identity.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation is heavily focused on PowerShell-based automation, which is primarily a Windows-centric tool. All code samples, migration steps, and graphical runbook instructions use PowerShell cmdlets (Connect-AzAccount, Get-AzResourceGroup, etc.) and reference PowerShell modules (Az, AzureRM). There are no examples or guidance for using Linux-native tools, Bash, Python, or cross-platform SDKs. Windows/PowerShell patterns are presented exclusively and first, with no mention of alternatives for Linux or cross-platform users.
Recommendations
  • Add equivalent code samples for Bash (using Azure CLI) and Python (using Azure SDK) to demonstrate managed identity authentication and resource access.
  • Include migration steps and scripts for runbooks written in Bash or Python, not just PowerShell.
  • Explicitly mention cross-platform options for Azure Automation, such as using Azure CLI or Python runbooks, and link to relevant documentation.
  • Clarify which steps, scripts, and modules are Windows-specific and provide Linux-compatible alternatives where possible.
  • Add a section or note about how managed identities can be used in Linux-based hybrid runbook workers, including any differences or limitations.
GitHub Create Pull Request
Active Directory B2C Create & delete Azure AD B2C consumer user accounts in the Azure portal ...n/articles/active-directory-b2c/manage-users-portal.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias primarily in the 'Revoke a consumer user's session' section, where only Windows PowerShell and Microsoft Graph PowerShell are mentioned and example commands are provided. There is no mention of Linux or cross-platform alternatives, nor are CLI or REST API examples given. The instructions and tooling assume a Windows environment, and Linux users are not provided with equivalent guidance.
Recommendations
  • Include examples using Microsoft Graph API via curl or other cross-platform tools for session revocation.
  • Mention that Microsoft Graph PowerShell can be installed and used on Linux/macOS, and provide instructions for those platforms.
  • Provide Azure CLI or REST API examples where possible, especially for tasks like session revocation.
  • Avoid language that assumes Windows as the default environment (e.g., 'In your Windows PowerShell...').
  • Add notes or sections specifically for Linux/macOS users to ensure parity in guidance and tooling.
GitHub Create Pull Request
Active Directory B2C IDology integration with Azure Active Directory B2C .../main/articles/active-directory-b2c/partner-idology.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation demonstrates Windows bias by referencing Visual Studio and linking to Windows-centric deployment instructions for publishing the API, without mentioning Linux alternatives or cross-platform deployment methods. There are no examples or guidance for deploying the API from Linux environments, nor are Linux-native tools or workflows discussed. The documentation assumes the use of Windows tooling and does not provide parity for Linux users.
Recommendations
  • Include instructions for deploying the API using cross-platform tools such as Azure CLI, GitHub Actions, or VS Code, which are available on Linux.
  • Provide Linux-specific deployment examples, such as using the dotnet CLI or zip deployment via Azure CLI.
  • Reference documentation for deploying from Linux or macOS environments alongside Visual Studio instructions.
  • Avoid assuming Visual Studio as the default tool; mention alternatives like VS Code or JetBrains Rider.
  • Ensure that all steps (such as configuring app settings and uploading policy files) are described in a way that is platform-agnostic or include Linux/macOS equivalents.
GitHub Create Pull Request
Active Directory B2C Secure APIs used for API connectors in Azure AD B2C .../main/articles/active-directory-b2c/secure-rest-api.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a bias towards Windows environments by exclusively referencing PowerShell for self-signed certificate creation and omitting equivalent Linux/macOS commands or tooling. The only explicit method for local certificate generation is via PowerShell, with no mention of OpenSSL or other cross-platform alternatives. This may hinder Linux and macOS users who do not have access to PowerShell or prefer native tools.
Recommendations
  • Provide Linux/macOS equivalents for certificate creation, such as OpenSSL commands, alongside PowerShell instructions.
  • Explicitly mention cross-platform tools and workflows where possible, ensuring parity for non-Windows environments.
  • Add examples and screenshots for Linux/macOS certificate management and upload processes.
  • Review other sections for any implicit Windows-first assumptions and clarify that all steps can be performed on any OS with appropriate tooling.
GitHub Create Pull Request
App Service Tutorial: ASP.NET app with Azure SQL Database ...service/app-service-web-tutorial-dotnet-sqldatabase.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation is heavily oriented toward Windows and Visual Studio workflows, with all examples and instructions assuming a Windows environment. There are no Linux or cross-platform alternatives provided for key steps such as publishing, database management, or command-line operations. Windows-specific tools (Visual Studio, SQL Server Object Explorer, PowerShell, Package Manager Console) are used exclusively, and Azure App Service (Windows) is selected by default. No mention is made of Linux-based development environments, deployment from Linux, or using cross-platform tools like Azure CLI or VS Code.
Recommendations
  • Add instructions and examples for deploying ASP.NET apps from Linux environments, including using VS Code and the Azure CLI.
  • Provide equivalent steps for publishing to Azure App Service (Linux), including screenshots and configuration details.
  • Include cross-platform command-line examples (bash, Azure CLI) for database setup, migrations, and managed identity configuration.
  • Mention and demonstrate how to use SQL tools available on Linux (e.g., sqlcmd, Azure Data Studio) for database management.
  • Clarify which steps are Windows-specific and offer alternatives for macOS and Linux users.
  • Reference cross-platform .NET development workflows and tooling where possible.
GitHub Create Pull Request
App Service Customize Sign-ins and Sign-outs ...vice/configure-authentication-customize-sign-in-out.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation provides a dedicated section for Windows apps, detailing how to configure authorization via IIS and web.config, but does not offer equivalent guidance or examples for Linux-based apps. Windows-specific tools (IIS, web.config) are mentioned exclusively, and Linux alternatives are not discussed or referenced. The overall flow and examples are platform-neutral except for the authorization section, which is Windows-centric.
Recommendations
  • Add equivalent guidance for Linux-based apps, such as how to implement authorization using common web servers (e.g., Nginx, Apache) or application-level code.
  • Include Linux-specific configuration examples for restricting access, such as sample code or configuration for popular frameworks (Node.js, Python, etc.) running on Linux App Service.
  • Explicitly mention that Linux apps require application-level authorization and provide links or code samples for common scenarios.
  • Balance the documentation by presenting both Windows and Linux approaches side-by-side where platform-specific configuration is required.
GitHub Create Pull Request
App Service Configure a Custom Container ...ain/articles/app-service/configure-custom-container.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a moderate Windows bias. Windows-specific concepts, tools, and examples (such as PowerShell commands, IIS, .NET Framework, Windows Server base images, and C:\home paths) are often presented first or in greater detail. PowerShell examples are provided alongside Bash, but sometimes with more explanation. Windows-specific features (like machine key injection, group managed service accounts, and memory/core customization) receive dedicated sections, while Linux equivalents are less emphasized or missing. Some advanced configuration and troubleshooting guidance is richer for Windows containers. Linux coverage is present, but sometimes less detailed or appears after Windows content.
Recommendations
  • Ensure Linux examples and guidance are provided with equal detail and prominence as Windows, especially for advanced scenarios (e.g., memory/core limits, diagnostic logs, environment variable injection).
  • Present Linux and Windows instructions in parallel or side-by-side, rather than Windows-first ordering.
  • Expand Linux-specific troubleshooting and configuration sections to match the depth of Windows coverage (e.g., persistent storage, diagnostic logs, SSH access, environment variable handling).
  • Where PowerShell is used, ensure Bash/Linux CLI equivalents are always shown and explained equally.
  • Highlight Linux-specific base images, patterns, and best practices in the same way as Windows (e.g., recommend official Linux base images for .NET, Node, Python, etc.).
  • Review and update references to Windows-only tools or paths (e.g., C:\home) to clarify Linux equivalents (/home), and avoid implying Windows as the default.
GitHub Create Pull Request
App Service Configure ASP.NET Core apps .../articles/app-service/configure-language-dotnetcore.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a mild Windows bias. Windows-specific instructions and tools (such as Visual Studio and Kudu) are introduced first and receive more detailed attention, while Linux equivalents are mentioned later or in separate pivots. Windows tools like Kudu and PowerShell are referenced before Linux alternatives, and Visual Studio is presented as the default publishing tool. Linux instructions are present but sometimes less detailed or introduced after Windows steps.
Recommendations
  • Ensure that Linux instructions are presented with equal prominence and detail as Windows instructions, possibly by alternating which platform is shown first in examples.
  • Provide Linux-native tooling examples (such as SSH, Bash, or VS Code Remote) alongside or before Windows tools like Kudu and PowerShell.
  • Expand Linux-specific sections to match the depth of Windows instructions, including troubleshooting, deployment, and configuration scenarios.
  • Where Visual Studio is referenced, also mention cross-platform alternatives (such as VS Code, JetBrains Rider, or CLI workflows) for Linux users.
  • Review all examples to ensure Linux parity, especially in areas like build automation, diagnostics, and environment variable configuration.
GitHub Create Pull Request
App Service Disable Basic Authentication for Deployment ...n/articles/app-service/configure-basic-auth-disable.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. It frequently references Windows-centric deployment tools and patterns, such as Web Deploy (MSDeploy), Visual Studio, and FTP, which are traditionally associated with Windows environments. These tools are mentioned before or instead of Linux-native equivalents. There is a lack of explicit Linux or cross-platform deployment examples (e.g., SFTP, rsync, SCP, or Linux-specific CLI workflows), and troubleshooting guidance is focused on Windows agents. The documentation does not provide parity for Linux users in terms of deployment methods, troubleshooting, or alternative tool recommendations.
Recommendations
  • Include Linux-native deployment examples (e.g., SFTP, SCP, rsync) and clarify their support or limitations with Azure App Service.
  • Add troubleshooting guidance for Linux agents and self-hosted runners, not just Windows agents.
  • Mention cross-platform tools and workflows (such as VS Code, Git CLI, or Azure CLI on Linux/macOS) alongside Windows tools.
  • Provide parity in documentation for both Windows and Linux environments, including screenshots and step-by-step instructions.
  • Explicitly state which deployment methods and authentication mechanisms are supported or unsupported on Linux and macOS.
GitHub Create Pull Request
App Service Configure ASP.NET Apps ...les/app-service/configure-language-dotnet-framework.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by focusing on Windows-specific tools and patterns, such as Visual Studio publishing, Kudu with CMD/PowerShell, and referencing Windows file paths. There are no Linux-specific examples or instructions, and Windows deployment methods and tooling are mentioned exclusively or before any Linux alternatives. The lack of parity for Linux users is evident, especially in sections about runtime version discovery and deployment.
Recommendations
  • Add equivalent Linux instructions and examples, such as using Bash in Kudu or SSH for Linux-based App Service environments.
  • Include Linux file paths and commands for listing .NET Framework/Mono assemblies in Linux containers.
  • Mention Linux deployment tools and patterns (e.g., dotnet CLI, VS Code, GitHub Actions) alongside Visual Studio.
  • Clarify which steps apply to Windows, Linux, or both, and provide links to Linux-specific documentation where relevant.
  • Ensure that environment variable access and diagnostic logging examples include Linux container scenarios.
GitHub Create Pull Request
Backup Back up Exchange server with Azure Backup Server ...lob/main/articles/backup/backup-azure-exchange-mabs.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation exclusively describes backup and recovery procedures using Microsoft Azure Backup Server (MABS), which is a Windows-only tool. All instructions, screenshots, and file paths (e.g., C:\Program Files\...) are Windows-centric. There are no Linux equivalents, examples, or mentions of Linux-based Exchange deployments or backup tools. The documentation assumes the administrator is operating in a Windows environment from start to finish.
Recommendations
  • Explicitly state that MABS is a Windows-only solution and clarify platform requirements at the beginning.
  • Provide guidance or links for Linux-based Exchange alternatives, if supported, or mention that Linux is not supported.
  • If Linux support is planned, add parallel instructions, examples, and screenshots for Linux environments.
  • Reference cross-platform backup tools or Azure-native backup options that can be used with Linux servers, if applicable.
  • Ensure that documentation for similar backup scenarios includes both Windows and Linux workflows where possible.
GitHub Create Pull Request
Backup Monitor Azure Backup protected workloads ...les/backup/backup-azure-monitoring-built-in-monitor.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias by referencing Windows-centric backup tools (DPM, MABS, MARS) and providing links and examples that focus on Windows Server management. There are no explicit Linux backup tool mentions, nor are there examples or instructions for monitoring Linux workloads. The order and emphasis are on Windows solutions, with no Linux parity in examples or tool references.
Recommendations
  • Include explicit references to Linux-supported backup agents and workloads (e.g., Azure Backup for Linux VMs, Azure Backup agent for Linux).
  • Provide examples and instructions for monitoring Linux backup items and jobs, including any differences in portal experience or supported features.
  • Mention Linux-specific constraints or requirements (e.g., supported distributions, file system considerations) alongside Windows details.
  • Ensure parity in documentation structure by presenting Linux and Windows solutions side-by-side where applicable.
  • Add links to Linux backup management documentation and troubleshooting guides.
GitHub Create Pull Request
Backup Tutorial - Back up Azure Database for PostgreSQL server ...lob/main/articles/backup/tutorial-postgresql-backup.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates a Windows bias by primarily referencing PowerShell scripts for privilege assignment and not providing equivalent Linux/Unix command-line examples. PowerShell is mentioned as the main method for granting database privileges, with alternatives (PG admin or PSQL tool) only briefly referenced and not documented with examples. The step-by-step instructions and screenshots are focused on the Azure portal, which is platform-agnostic, but the only explicit scripting guidance is for PowerShell, leaving Linux users without clear instructions.
Recommendations
  • Provide equivalent examples using Linux/Unix command-line tools (e.g., psql) for granting database privileges.
  • Include sample bash scripts or psql commands alongside PowerShell scripts to ensure parity.
  • Explicitly document how to perform all steps on Linux systems, especially privilege assignment and automation.
  • Clarify that PowerShell is not required and offer guidance for users on non-Windows platforms.
  • Where templates/scripts are generated, offer both PowerShell and bash/psql versions for download.
GitHub Create Pull Request
App Service Authentication Types by Deployment Methods ...in/articles/app-service/deploy-authentication-types.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-centric tools and workflows such as Azure PowerShell, Visual Studio, and migration assistants tailored for Windows environments. Examples and references for deployment methods are heavily skewed towards Windows tools, with PowerShell and Visual Studio featured prominently and before cross-platform alternatives. There is a lack of explicit Linux or macOS command-line examples, and no mention of Linux-specific deployment patterns or tools (e.g., Bash, SSH, SCP, rsync, or Linux package managers). The documentation does not provide parity for Linux users in terms of guidance, examples, or tool recommendations.
Recommendations
  • Add Linux/macOS-specific deployment examples using Bash, native SSH, SCP, or rsync commands.
  • Include references to Linux-friendly tools and workflows, such as deploying from a Linux terminal or using Linux-based CI/CD pipelines.
  • Provide parity in documentation for Visual Studio Code on Linux/macOS, including screenshots and step-by-step guides.
  • Explicitly mention cross-platform compatibility for Azure CLI and clarify any differences in authentication or usage on Linux.
  • Add guidance for deploying Java, Python, Node.js, and other non-Windows-centric stacks from Linux environments.
  • Ensure migration tools and scripts have Linux equivalents or alternatives, and document their usage.
GitHub Create Pull Request
App Service Supported platforms and file types ...includes/webjobs-create/webjobs-supported-platforms.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation lists Windows hosting options and file types before Linux equivalents, and gives more detailed mention to Windows-specific tools (executables, batch files, PowerShell scripts) before mentioning Bash and other scripting languages. There are no explicit Linux-specific examples or tools highlighted, and PowerShell is called out separately, reinforcing a Windows-centric perspective.
Recommendations
  • List Linux hosting options and file types before or alongside Windows equivalents to avoid ordering bias.
  • Explicitly mention Linux-specific tools or patterns, such as shell scripts, cron jobs, or systemd services, where relevant.
  • Provide Linux-specific examples (e.g., sample Bash script usage or integration patterns) to match the detail given for Windows tools.
  • Include a note clarifying cross-platform support and parity, emphasizing that both Windows and Linux are first-class citizens.
  • Consider grouping file/script types by platform or presenting them in a parallel structure to highlight equal support.
GitHub Create Pull Request
App Service Migrate Docker Compose to sidecars ...es/app-service/migrate-sidecar-multi-container-apps.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by requiring PowerShell for both the prerequisites and migration script, providing only PowerShell examples for critical steps (such as base64 decoding), and referencing Windows-centric tools and workflows before any Linux alternatives. There are no Bash or Linux shell examples, and the migration script is only available as a PowerShell script (.ps1), which excludes native Linux users. The documentation does not mention or provide parity for Linux shell usage, nor does it offer alternative scripts or commands for non-Windows environments.
Recommendations
  • Provide Bash or Linux shell equivalents for all PowerShell commands, especially for base64 decoding and other scripting steps.
  • Offer a migration script in Bash (.sh) or cross-platform scripting language (e.g., Python), or document how to run the PowerShell script on Linux using PowerShell Core.
  • List prerequisites for both Windows and Linux environments, including installation instructions for PowerShell Core on Linux if required.
  • Ensure examples are given for both Windows and Linux users, or present Linux examples first to avoid implicit Windows prioritization.
  • Explicitly mention Linux compatibility and provide troubleshooting tips for Linux users where workflows differ.
GitHub Create Pull Request
App Service Managed Identities ...main/articles/app-service/overview-managed-identity.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is featured prominently as a primary automation tool, with detailed examples and instructions for both App Service and Functions. There are no explicit Linux shell (bash) or cross-platform scripting examples outside of Azure CLI, and PowerShell is presented as a first-class option, which is more commonly used on Windows. Additionally, some instructions (e.g., for creating user-assigned identities in Functions) are only available for PowerShell, and the lack of bash or Linux-native scripting alternatives may hinder Linux users. The documentation does not mention or recommend Linux-specific tools or patterns, and PowerShell examples are given equal or greater prominence than Azure CLI.
Recommendations
  • Add bash shell scripting examples alongside PowerShell for all automation steps, especially for token retrieval and identity management.
  • Explicitly state cross-platform compatibility for Azure CLI and ARM template examples, and clarify that these tools work equally well on Linux and macOS.
  • Where PowerShell is used, provide equivalent bash or shell script snippets to ensure Linux users have clear guidance.
  • Mention Linux-native tools (such as curl, jq) for REST endpoint interactions and token retrieval, and provide sample commands.
  • Review and update any instructions that are PowerShell-only to include Linux-compatible alternatives, or note platform limitations where applicable.
GitHub Create Pull Request
App Service Migration Checklist - Azure App Service on Arc-enabled Kubernetes to Azure Container Apps on Arc-enabled Kubernetes ...b/main/articles/app-service/migrate-app-service-arc.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for resource queries, but PowerShell is given equal prominence to CLI, which is more cross-platform. There are no Linux-specific shell examples (e.g., Bash), and no mention of Linux-native tools or patterns. The documentation does not reference Windows tools directly, but the inclusion of PowerShell examples (which are most commonly used on Windows) and the lack of Linux shell examples indicate a subtle Windows bias.
Recommendations
  • Add Bash shell examples for all CLI commands to demonstrate usage on Linux and macOS.
  • Clarify that Azure CLI commands work cross-platform and provide explicit instructions for Linux users where relevant.
  • Consider removing or de-emphasizing PowerShell examples unless there is a specific Windows-only scenario.
  • Include notes or sections addressing Linux-specific considerations, such as permissions, environment setup, or troubleshooting.
  • Ensure that any references to tools or patterns are balanced between Windows and Linux environments.
GitHub Create Pull Request
App Service Managed Instance on App Service overview (preview) ...main/articles/app-service/overview-managed-instance.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation is heavily focused on Windows-specific features and tooling, such as PowerShell scripts, registry modifications, COM components, MSI installers, IIS Manager, and RDP access. All configuration and operational examples reference Windows tools and patterns, with no Linux equivalents or parity. The platform is described as Windows-only, and Linux/container support is explicitly excluded. Windows terminology and tools are mentioned first and exclusively throughout the page.
Recommendations
  • Add explicit Linux support or roadmap information if planned, including equivalent configuration and operational patterns.
  • Provide Linux/bash script examples alongside PowerShell for configuration tasks, where applicable.
  • Reference Linux-native tools (e.g., SSH, systemd, cron, Linux package managers) in relevant sections.
  • Clarify which features are Windows-only and suggest Linux alternatives or workarounds for users needing cross-platform solutions.
  • Include a comparison table of Windows vs. Linux capabilities for Managed Instance and App Service, highlighting gaps and parity.
  • If Linux support is not planned, make this limitation prominent at the top of the documentation.
GitHub Create Pull Request
App Service Create an App by Using a Terraform Template ...n/articles/app-service/provision-resource-terraform.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation demonstrates a mild Windows bias in several areas: Windows and PowerShell configuration options are listed before Linux equivalents in the prerequisites, and Windows-specific tools (PowerShell, Visual Studio Code extension) are highlighted. While both Linux and Windows Terraform templates are provided, the initial orientation and tooling recommendations lean toward Windows environments. There is also a lack of parity in mentioning Linux-native editors or shell environments outside Cloud Shell Bash.
Recommendations
  • List Linux and Windows configuration options in parallel or alternate order to avoid Windows-first impression.
  • Include explicit instructions and examples for Linux desktop environments (e.g., Ubuntu, Fedora) outside of Azure Cloud Shell.
  • Mention Linux-native editors (e.g., Vim, Nano, Emacs) alongside Visual Studio Code for authoring Terraform files.
  • Highlight Bash and other Linux shells equally with PowerShell in all relevant sections.
  • Ensure that any tooling recommendations (such as VS Code extensions) clarify cross-platform compatibility and suggest alternatives where appropriate.
GitHub Create Pull Request
Application Gateway Deploy an Azure Application Gateway with an IPv6 frontend ...ation-gateway/ipv6-application-gateway-arm-template.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates bias towards Windows by exclusively using IIS (a Windows web server) for backend validation, referencing only PowerShell for resource cleanup, and omitting Linux-based alternatives or examples (such as Apache/Nginx or Bash/Azure CLI commands). There are no Linux VM validation steps or cleanup instructions using Linux-friendly tools.
Recommendations
  • Include examples of deploying Linux VMs (e.g., Ubuntu) in the backend pool and instructions for validating deployment using Apache or Nginx.
  • Provide resource cleanup instructions using Azure CLI (az group delete) and Bash, alongside PowerShell.
  • Add browser-based validation steps for both Windows and Linux VMs, showing expected responses from different web servers.
  • Mention that IIS is used for demonstration and offer equivalent steps for Linux-based web servers.
  • Ensure parity in screenshots and instructions for both Windows and Linux environments.
GitHub Create Pull Request
Application Gateway Configure Application Gateway with a frontend public IPv6 address using the Azure portal ...application-gateway/ipv6-application-gateway-portal.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates Windows bias by exclusively using Windows Server as the backend VM example and providing only PowerShell-based instructions for backend configuration (IIS installation). There are no Linux VM examples, nor are there Linux command-line instructions (e.g., Bash, SSH, cloud-init) for backend setup or testing. The documentation references Azure PowerShell as an alternative to the portal, but does not mention Azure CLI or provide parity for Linux users.
Recommendations
  • Include Linux VM examples (e.g., Ubuntu or CentOS) as backend targets alongside Windows Server.
  • Provide instructions for installing a web server (e.g., Apache or Nginx) on Linux VMs using Bash/SSH commands or cloud-init scripts.
  • Offer Azure CLI commands as alternatives to Azure PowerShell for resource creation and configuration.
  • Explicitly mention cross-platform options for testing connectivity (e.g., curl, wget) from Linux/macOS terminals.
  • Ensure that both Windows and Linux setup/testing instructions are presented with equal prominence and detail.
GitHub Create Pull Request
Automanage Azure Automanage for Azure Arc-enabled servers ...e-docs/blob/main/articles/automanage/automanage-arc.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation lists Windows Server versions first in the supported operating systems section and includes a Windows-only service (Microsoft Antimalware) in the participating services table. There are no Linux-specific examples, tools, or configuration patterns mentioned, and the guidance does not provide parity for Linux anti-malware or security tooling. The 'ms.collection' metadata references Linux, but the content and examples are Windows-centric.
Recommendations
  • List Linux operating systems before or alongside Windows in supported OS sections to avoid Windows-first bias.
  • Include Linux-specific security and anti-malware solutions in the participating services table, or clarify their absence and recommend alternatives.
  • Provide examples or guidance for configuring Automanage on Linux systems, including command-line or automation patterns relevant to Linux (e.g., Bash, systemd, package managers).
  • Highlight any differences in service behavior or limitations for Linux systems, ensuring users are aware of platform-specific considerations.
  • Add links to Linux-focused documentation or best practices for Azure Automanage and related services.
GitHub Create Pull Request
Automanage SMB over QUIC with Azure Automanage machine best practices ...b/main/articles/automanage/automanage-smb-over-quic.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation exclusively references Windows Server 2022 Datacenter: Azure Edition as the required VM image for SMB over QUIC and Automanage best practices, with no mention of Linux support, equivalents, or examples. All configuration steps and links point to Windows-specific resources, and there are no instructions or guidance for Linux-based VMs or cross-platform scenarios.
Recommendations
  • Explicitly state whether SMB over QUIC and Automanage best practices are supported or not on Linux VMs.
  • If Linux support exists, provide equivalent examples and instructions for deploying and managing SMB over QUIC on Linux-based Azure VMs.
  • Include references to Linux tools, commands, or configuration patterns where applicable.
  • If support is Windows-only, clarify this limitation early in the documentation to set user expectations.
  • Consider adding a comparison table outlining feature parity and differences between Windows and Linux VM support for SMB over QUIC and Automanage.
GitHub Create Pull Request
Automanage Move an Azure Automanage configuration profile across regions ...s/automanage/move-automanaged-configuration-profile.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation exclusively uses PowerShell and Windows-centric tooling (Invoke-RestMethod, PowerShell syntax) for all examples and instructions. No Linux or cross-platform alternatives (such as Bash, curl, or Azure CLI) are provided, making the guidance inaccessible or less clear for Linux users. The use of Windows tools is implicit and not balanced by Linux equivalents.
Recommendations
  • Provide equivalent examples using Bash and curl for REST API calls.
  • Include Azure CLI commands for each step, as Azure CLI is cross-platform.
  • Explicitly mention that the steps can be performed on Linux/macOS and provide sample scripts.
  • Add a note or section on platform compatibility, clarifying that REST API calls can be made from any OS.
  • Ensure that Linux examples appear alongside or before Windows/PowerShell examples to avoid implicit prioritization.
GitHub Create Pull Request
Automanage Repair a broken Azure Automanage Account .../main/articles/automanage/repair-automanage-account.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by mentioning PowerShell as a primary method for ARM deployments before Linux alternatives, listing PowerShell modules alongside Azure CLI, and referencing Windows-centric tooling patterns. There are no explicit Linux-specific examples, and PowerShell is presented as a default option, which may disadvantage Linux users.
Recommendations
  • Provide explicit Bash and Linux shell examples for ARM deployments, not just Azure CLI.
  • List Azure CLI commands before PowerShell commands to avoid implying Windows-first workflows.
  • Clarify that Azure CLI is cross-platform and highlight its use on Linux and macOS.
  • Avoid referencing PowerShell modules as a primary method unless parity is shown for Bash/shell users.
  • Include notes or sections for Linux users, such as installation and usage tips for Azure CLI on Linux.
GitHub Create Pull Request
Automation Manage connections in Azure Automation ...lob/main/articles/automation/automation-connections.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by focusing heavily on PowerShell cmdlets and workflows, providing detailed PowerShell examples and references to Windows-specific tools (e.g., PowerShell, Az modules). Linux or cross-platform CLI examples are missing, and the PowerShell workflow is described before Python, with no mention of Bash, Azure CLI, or Linux-native automation approaches. The documentation assumes the use of Windows-centric tools and patterns, which may disadvantage Linux users or those preferring non-PowerShell environments.
Recommendations
  • Add equivalent examples using Azure CLI and Bash scripts for creating and managing connections.
  • Explicitly mention Linux compatibility and provide steps for Linux users, including installation and usage of required modules.
  • Include cross-platform instructions and clarify which features are available on Windows vs. Linux.
  • Provide Python examples earlier or in parallel with PowerShell, and add other language examples if supported.
  • Reference Linux tools and patterns where appropriate, such as environment variables, shell scripting, or alternative credential management approaches.
GitHub Create Pull Request
Automation Convert configurations to composite resources for Azure Automation State Configuration ...articles/automation/automation-dsc-create-composite.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a strong Windows bias by focusing exclusively on Windows PowerShell 5.1 and PowerShell DSC tooling. All examples and instructions are tailored to PowerShell, with no mention of Linux-native configuration management tools or cross-platform DSC usage. References to configuration management scenarios (web server, DNS, SQL, SharePoint) are implicitly Windows-centric, and links and next steps direct users to Windows PowerShell resources. There is no guidance for Linux users, nor examples using Linux shell or DSC on Linux.
Recommendations
  • Add explicit support and examples for Linux environments, including how to use DSC on Linux nodes.
  • Include Linux shell (bash) equivalents for configuration management tasks where possible.
  • Reference cross-platform DSC modules and clarify any differences in usage between Windows and Linux.
  • Provide links to documentation for Linux DSC resources and configuration management tools.
  • Update 'Applies to' section to specify whether Linux is supported and, if so, how to use these features on Linux.
GitHub Create Pull Request
Automation Authenticate Azure Automation runbooks with Amazon Web Services ...n/articles/automation/automation-config-aws-account.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias by referencing AWS credential management via a PowerShell-specific link, omitting Linux or cross-platform CLI examples. The instructions and links focus on Azure portal and PowerShell workflows, with no mention of Linux tools, shell commands, or guidance for non-Windows environments.
Recommendations
  • Include examples for authenticating and managing AWS credentials using the AWS CLI on Linux/macOS.
  • Reference AWS documentation for Linux and cross-platform credential management, not just PowerShell.
  • Provide parity in instructions for storing credentials, such as using Azure Automation assets via Azure CLI or REST API, which are platform-agnostic.
  • Add notes or sections for Linux users, including common shell commands and credential file locations.
  • Ensure that all referenced external documentation covers both Windows and Linux usage patterns.
GitHub Create Pull Request
Automation Use an alert to trigger an Azure Automation runbook ...utomation/automation-create-alert-triggered-runbook.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a strong Windows bias. All code examples and instructions are provided exclusively in PowerShell, which is primarily a Windows-centric tool (though available on Linux, it's less commonly used there). The prerequisites specifically reference Windows virtual machines and the Azure Az PowerShell module, with no mention of Linux VMs or CLI alternatives. There are no Bash, Azure CLI, or Linux shell examples, nor any guidance for users working in non-Windows environments. The workflow and tooling are presented from a Windows-first perspective, and Linux parity is not addressed.
Recommendations
  • Add equivalent Azure CLI (az) and Bash script examples for all PowerShell instructions, especially for role assignment and runbook creation.
  • Explicitly mention that the Az PowerShell module is cross-platform, and provide installation instructions for Linux/macOS.
  • Include Linux VM scenarios in prerequisites and examples, such as links to Linux VM quickstart guides.
  • Show how to create and trigger runbooks using Azure CLI and REST API, not just PowerShell.
  • Clarify which steps or scripts are platform-agnostic and which are Windows-specific.
  • Provide troubleshooting or notes for users working on Linux/macOS, especially regarding authentication and managed identity.
  • Balance the documentation by alternating or paralleling Windows and Linux instructions throughout the page.
GitHub Create Pull Request
Automation Create configurations from existing servers for Azure Automation State Configuration ...ticles/automation/automation-dsc-config-from-server.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page exhibits a strong Windows bias. It is focused almost exclusively on Windows PowerShell 5.1 and Windows-centric tools (DSC, SharePointDSC, ReverseDSC). All examples, references, and next steps are tailored to Windows environments, with no Linux-specific instructions, examples, or equivalent tooling mentioned. Linux is referenced only in passing, with no guidance on how to achieve similar outcomes on Linux servers.
Recommendations
  • Add explicit examples and instructions for Linux environments, including how to extract configurations from Linux servers.
  • Mention and link to Linux equivalents of DSC, such as 'OMI' or 'DSC for Linux', and community projects relevant to Linux configuration extraction.
  • Provide parity in step-by-step guides for Linux, including how to generate MOF files from Linux servers and upload them to Azure Automation.
  • Update the 'Applies to' section to clarify Linux support and limitations, and offer alternative approaches for Linux users.
  • Include references to Linux-specific documentation and resources in the 'Next steps' section.
GitHub Create Pull Request
Automation Configure data based on STIG for Azure Automation State Configuration ...tomation/automation-dsc-configuration-based-on-stig.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page is heavily focused on Windows and PowerShell, with all examples and tooling references centered around Windows PowerShell DSC and the PowerSTIG project. Linux is only briefly mentioned as a possible target for onboarding, but no Linux-specific configuration guidance, examples, or tools are provided. The documentation assumes familiarity with Windows PowerShell and does not address Linux equivalents or cross-platform DSC usage.
Recommendations
  • Include Linux-specific examples for configuring STIG baselines using DSC, such as using DSC for Linux or alternative configuration management tools (e.g., Ansible, Chef, or native Linux DSC support).
  • Mention and link to Linux-compatible DSC resources and documentation, clarifying any platform limitations.
  • Provide guidance or references for generating and applying MOF files on Linux systems, including any prerequisites or differences from Windows.
  • Balance the introduction and next steps by equally highlighting Linux and cross-platform approaches, not just Windows PowerShell.
  • If PowerSTIG is Windows-only, explicitly state this and suggest Linux alternatives for STIG compliance automation.
GitHub Create Pull Request
Automation Integrate Azure Automation State Configuration with Azure Monitor Logs ...main/articles/automation/automation-dsc-diagnostics.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a strong Windows bias. All code examples and setup instructions use PowerShell and Az PowerShell modules, which are native to Windows and only available on Linux via PowerShell Core (which is less commonly used). There are no Bash, CLI, or Linux-native examples, and no mention of Linux-specific tools or workflows. The prerequisites and troubleshooting modules are PowerShell-centric. The only reference to Linux is an end-of-life announcement, not guidance or parity.
Recommendations
  • Add equivalent Azure CLI (az) commands for all PowerShell examples, as Azure CLI is cross-platform and widely used on Linux.
  • Include Bash script examples for setup and integration steps.
  • Explicitly state Linux support status and provide guidance for Linux users where possible.
  • Reference Linux-compatible DSC modules and workflows if available.
  • Clarify which steps are platform-agnostic and which require Windows/PowerShell, and suggest alternatives for Linux environments.
  • Update troubleshooting and onboarding sections to include Linux-specific instructions or note limitations.
GitHub Create Pull Request
Automation Get started with Azure Automation State Configuration .../articles/automation/automation-dsc-getting-started.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page exhibits a strong Windows bias. All configuration examples use Windows PowerShell DSC syntax and the WindowsFeature resource, with no Linux equivalents or cross-platform DSC resources shown. The prerequisites and VM creation instructions reference only Windows VMs, and links point to Windows-specific documentation. Linux support is only mentioned in passing and in the context of retirement announcements, with no practical guidance or examples for Linux users.
Recommendations
  • Add equivalent Linux DSC configuration examples, such as using nxFile or nxPackage resources.
  • Include instructions for creating and onboarding Linux VMs, with links to Linux VM creation guides.
  • Provide cross-platform DSC examples and clarify which resources and steps are supported on Linux.
  • Update prerequisites to mention supported Linux operating systems and their requirements.
  • Balance references to Windows PowerShell DSC with information about cross-platform DSC (including PowerShell Core and Linux).
  • Remove or update retirement announcements to clarify current Linux support and alternatives.
GitHub Create Pull Request
Automation Remediate noncompliant Azure Automation State Configuration servers ...b/main/articles/automation/automation-dsc-remediate.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page presents remediation steps for Azure Automation State Configuration servers with a clear Windows bias. Windows remediation is described first, with a direct PowerShell example and references to Windows-specific tools (PowerShell, Update-DscConfiguration). Linux remediation is described as less capable, with no script example, and only general guidance to repeat registration or use Python scripts, but no concrete code. Windows tools and patterns are mentioned exclusively or before Linux equivalents.
Recommendations
  • Provide concrete Linux remediation script examples, similar to the PowerShell example for Windows.
  • Include references to Linux-native tools and commands (e.g., shell scripts, Python commands) for correcting drift.
  • Present Linux and Windows remediation steps in parallel, rather than Windows-first.
  • Clarify the limitations and alternatives for Linux users, and link to up-to-date Linux DSC documentation.
  • Avoid exclusive reliance on PowerShell and Windows tools; highlight cross-platform or Linux-specific solutions where available.
GitHub Create Pull Request
Automation Edit textual runbooks in Azure Automation ...articles/automation/automation-edit-textual-runbook.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation is heavily focused on PowerShell and Windows-specific workflows. All code examples use Windows PowerShell, with explicit references to Windows paths (e.g., c:\runbooks) and no mention of Linux or cross-platform alternatives. There are no Bash or Linux shell examples, nor guidance for users on non-Windows platforms. Windows tools and patterns are referenced exclusively, and the documentation does not address Linux or macOS users.
Recommendations
  • Include equivalent examples for Linux/macOS environments, such as using PowerShell Core (pwsh) on non-Windows platforms.
  • Use platform-neutral file paths in examples (e.g., $HOME/runbooks or ./runbooks).
  • Clarify that Az PowerShell module and Azure Automation can be used from Linux/macOS, and provide instructions for installing and using PowerShell Core.
  • Add Bash or Azure CLI examples for common runbook management tasks.
  • Explicitly state cross-platform compatibility and provide guidance for users on Linux and macOS.
GitHub Create Pull Request
Automation Forward Azure Automation job data to Azure Monitor logs ...mation/automation-manage-send-joblogs-log-analytics.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a moderate Windows bias. PowerShell is mentioned as the primary CLI for viewing job logs, and the only example of CLI interaction is with PowerShell. There are no references to Linux tools, Bash, or cross-platform alternatives for querying or interacting with Azure Automation job data. The documentation assumes familiarity with Windows-centric workflows and does not provide parity for Linux users.
Recommendations
  • Add examples using Azure CLI (az), which is cross-platform and works on both Windows and Linux.
  • Include Bash shell examples for querying logs and interacting with Azure Monitor, especially for Linux users.
  • Explicitly mention that all portal and Kusto query steps are platform-agnostic, and clarify that PowerShell is just one option.
  • Provide links or references to Linux-specific documentation for Azure Automation and Azure Monitor.
  • Where PowerShell is referenced, add equivalent steps for Bash/Azure CLI to ensure Linux users can follow along.
  • Review and update any screenshots or instructions that show Windows-only interfaces to include Linux or web-based alternatives where possible.
GitHub Create Pull Request
Automation Azure Automation account authentication overview ...in/articles/automation/automation-security-overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell cmdlets as the primary method for Azure Automation authentication, without mentioning or providing equivalent Linux or cross-platform examples (such as Azure CLI, Bash, or Python SDK). Windows tools and patterns (PowerShell, Azure Resource Manager templates) are mentioned exclusively or before any Linux alternatives. There are no examples or guidance for Linux users or those using non-Windows environments, and no mention of how to authenticate from Linux-based Hybrid Runbook Workers.
Recommendations
  • Include authentication examples using Azure CLI, Bash, or Python SDK alongside PowerShell cmdlets.
  • Explicitly mention and provide guidance for Linux-based Hybrid Runbook Workers, including how to configure authentication from Linux systems.
  • Add cross-platform code snippets for creating and managing Automation accounts and managed identities.
  • Reference Linux tools and patterns (e.g., shell scripts, cron jobs) where relevant, and ensure parity in documentation structure and examples.
  • Clarify that Azure Automation supports both Windows and Linux environments, and provide links to Linux-specific documentation where available.
GitHub Create Pull Request
Devtest Labs Azure DevTest Labs concepts ...lob/main/articles/devtest-labs/devtest-lab-concepts.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates Windows bias by referencing Windows virtual machines before Linux equivalents, omitting explicit mentions or examples of Linux VM usage, and listing Windows-specific tools (e.g., Visual Studio, Fiddler) as artifact examples without Linux alternatives. There are no PowerShell-heavy examples, but the overall focus is on Windows environments and tooling.
Recommendations
  • Include references and links to both Windows and Linux VM documentation (e.g., add a link to 'Linux virtual machines in Azure').
  • Provide examples of artifacts and tools relevant to Linux environments (e.g., install Apache, Git, or other Linux utilities).
  • Ensure artifact and template repository examples include Linux-focused templates and artifacts.
  • Mention Linux base images and their configuration alongside Windows base images.
  • Balance the order of presentation so that Windows and Linux options are discussed equally and in parallel.
GitHub Create Pull Request
Devtest Labs Integrate Azure DevTest Labs with DevOps CI/CD Pipelines ...blob/main/articles/devtest-labs/devtest-lab-dev-ops.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell scripts and Azure CLI as primary integration methods, without mentioning Linux shell scripting or providing Linux-specific examples. Windows-centric tools and patterns are mentioned first or exclusively, and there is a lack of explicit Linux or cross-platform examples for CI/CD integration with DevTest Labs.
Recommendations
  • Include Linux shell scripting (e.g., Bash) examples alongside PowerShell for managing DevTest Labs resources.
  • Mention Linux-based CI/CD agents and workflows explicitly, and provide parity in instructions for both Windows and Linux environments.
  • Highlight cross-platform compatibility of Azure CLI and REST APIs, and provide sample commands for both Windows and Linux terminals.
  • Add references to Linux tools and patterns (such as cron jobs, systemd services, or Ansible) where relevant.
  • Ensure that examples and guidance do not assume a Windows-first approach, and balance the order and prominence of Windows and Linux content.
GitHub Create Pull Request
Devtest Labs Delete a lab virtual machine or a lab ...ain/articles/devtest-labs/devtest-lab-delete-lab-vm.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation provides detailed instructions and examples for deleting lab VMs and labs in Azure DevTest Labs, but automation is only demonstrated using PowerShell, a Windows-centric tool. There are no equivalent examples for Linux users (e.g., Bash, Azure CLI), and the scripting section exclusively references PowerShell cmdlets and patterns. This creates a bias toward Windows users and may hinder Linux users from automating these tasks.
Recommendations
  • Add equivalent automation examples using Azure CLI (az) commands, which are cross-platform and commonly used on Linux.
  • Provide Bash script samples for deleting all VMs in a lab, alongside the PowerShell example.
  • Explicitly mention that the Azure portal steps are OS-agnostic, but clarify that scripting can be done from any platform using Azure CLI.
  • Include links to Azure CLI documentation for resource deletion tasks.
  • Ensure that future documentation covers both Windows and Linux automation options in parallel.
GitHub Create Pull Request
Automation Track updated files with an Azure Automation watcher task ...s/automation/automation-scenario-using-watcher-task.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation is heavily focused on PowerShell and Windows environments. All examples and instructions assume the use of PowerShell and Windows-style paths (e.g., D:\examplefiles), with no mention of Linux equivalents or Bash commands. The Hybrid Runbook Worker is only described in the context of Windows, and there are no examples or guidance for monitoring directories on Linux systems or using Linux-native tools. This creates a clear Windows bias and leaves Linux users without guidance for equivalent scenarios.
Recommendations
  • Add parallel examples using Bash or shell scripts for Linux Hybrid Runbook Workers.
  • Include instructions and screenshots for Linux file paths and directory monitoring.
  • Clarify whether watcher tasks and runbooks can run on Linux Hybrid Runbook Workers, and provide setup steps if supported.
  • Mention Linux tools (e.g., inotifywait, find) for file monitoring alongside PowerShell.
  • Ensure all parameter examples (e.g., FOLDERPATH) include both Windows and Linux path formats.
  • Provide troubleshooting and output examples for Linux environments.
GitHub Create Pull Request
Automation Disable local authentication in Azure Automation ...in/articles/automation/disable-local-authentication.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell examples and referencing Windows-centric tools (e.g., PowerShell cmdlets like Invoke-AzRestMethod and Get-AzAutomationAccount). There are no CLI, Bash, or Linux-native examples or instructions, and the workflow assumes the user is operating in a Windows environment. Linux alternatives (such as using curl or Azure CLI) are not mentioned, and PowerShell is presented as the default/first (and only) method for interacting with the API.
Recommendations
  • Add equivalent examples using Azure CLI (az automation account update) for disabling/enabling local authentication.
  • Provide REST API usage examples with curl or httpie, which are common on Linux systems.
  • Explicitly mention that PowerShell is cross-platform, but clarify how Linux/macOS users can install and use it, or offer alternative commands.
  • Reorder or supplement instructions so that Linux-friendly methods (CLI, REST with curl) are presented alongside or before PowerShell examples.
  • Include troubleshooting or verification steps using Azure CLI or REST API responses, not just PowerShell.
GitHub Create Pull Request
Automation Using a system-assigned managed identity for an Azure Automation account ...s/automation/enable-managed-identity-for-automation.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a strong Windows and PowerShell bias. Nearly all code examples and step-by-step instructions use PowerShell, with no equivalent Bash, CLI, or Linux-native scripting examples provided. Windows-specific tools and paths are mentioned first or exclusively in several places, such as instructions for checking Hybrid Runbook Worker versions and file paths. REST API and ARM template sections also use PowerShell for invocation, omitting cross-platform alternatives. Linux is mentioned only briefly and without practical examples. This limits accessibility for users on Linux or those preferring Azure CLI or Bash.
Recommendations
  • Provide equivalent Azure CLI and Bash examples for all PowerShell scripts, especially for enabling managed identity, assigning roles, and authenticating.
  • Include Linux-native instructions and file paths alongside Windows instructions, not only in version checks but also in practical automation scenarios.
  • Demonstrate REST API and ARM template invocations using curl or az CLI, not just PowerShell.
  • Add examples of using managed identity in Bash or Python scripts for resource access, not only PowerShell.
  • Ensure that instructions for hybrid workers, authentication, and troubleshooting are platform-neutral or include both Windows and Linux variants.
  • Consider a 'Platform parity' table or section summarizing how each step can be performed on both Windows and Linux.
GitHub Create Pull Request
Automation Create an Azure Automation account using a Resource Manager template ...ation/quickstart-create-automation-account-template.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is mentioned explicitly and referenced before Azure CLI in deployment instructions. The error handling example is given for PowerShell and the portal, with Azure CLI mentioned only after PowerShell. There are no Linux-specific examples, nor is Bash or shell scripting referenced. The documentation does not provide parity in example commands or troubleshooting steps for Linux users.
Recommendations
  • Provide explicit Bash/Azure CLI examples alongside PowerShell instructions, including full command syntax for Linux/macOS users.
  • List Azure CLI instructions before or alongside PowerShell to avoid Windows-first ordering.
  • Include troubleshooting steps and error messages for Azure CLI and Bash, not just PowerShell.
  • Mention cross-platform compatibility and clarify which steps apply to Windows, Linux, or macOS.
  • Add a note or section for Linux/macOS users, highlighting any differences or considerations.
GitHub Create Pull Request
Automation Azure Quickstart - Configure a VM with Desired State Configuration ...n/articles/automation/quickstarts/dsc-configuration.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates a strong Windows bias by centering all configuration and automation steps around PowerShell, referencing Windows-centric DSC resources, and mentioning Windows server management explicitly. Linux support is noted as retired, and while a LAMP stack example is given, all code samples use PowerShell syntax and Windows DSC tooling. There are no equivalent Linux-native examples, and references to tools like Chocolatey further reinforce the Windows focus.
Recommendations
  • Provide Linux-native configuration examples using tools such as Ansible, Chef, or native shell scripts, especially since Azure Automation DSC for Linux is retired.
  • Include alternative workflows for Linux VMs, such as using Azure Policy Guest Configuration or other supported mechanisms.
  • Clearly separate instructions for Windows and Linux, indicating which steps/tools apply to each platform.
  • Offer guidance on migrating from DSC to supported Linux configuration management solutions.
  • Avoid referencing Windows-only tools (e.g., Chocolatey) in general quickstarts, or provide Linux equivalents (e.g., apt, yum, dnf).
GitHub Create Pull Request
Automation Use Source Control Integration in Azure Automation ...main/articles/automation/source-control-integration.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation demonstrates a strong Windows bias. All command-line examples use PowerShell, with no mention of Bash, Azure CLI, or Linux-native workflows. The prerequisites and configuration steps assume use of PowerShell and Windows tooling, and there are no Linux-specific instructions or parity for non-Windows users. The only supported runbook type for source control integration is PowerShell 5.1, which is Windows-specific. Encoding issues are referenced via PowerShell documentation, and all automation examples are presented with PowerShell cmdlets.
Recommendations
  • Provide equivalent examples using Azure CLI and Bash for Linux/macOS users.
  • Clarify whether source control integration supports Python or other cross-platform runbook types, and update documentation if support is added.
  • Include instructions for configuring managed identities and role assignments using Azure CLI.
  • Reference Linux editors and encoding issues, not just PowerShell/VSCode.
  • Explicitly state platform requirements and limitations (e.g., PowerShell 5.1 is Windows-only) at the top of the documentation.
  • Add troubleshooting and configuration steps for Linux environments, including authentication and token management.
GitHub Create Pull Request
Automation Troubleshoot Azure Automation shared resource issues ...n/articles/automation/troubleshoot/shared-resources.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page exhibits a strong Windows bias, primarily through exclusive use of PowerShell cmdlets and scripts for troubleshooting and resolution steps. All code examples and tool references are Windows-centric (PowerShell, .psd1, .psm1, .dll files), with no mention of Linux equivalents or cross-platform alternatives. The troubleshooting steps assume familiarity with Windows tooling and scripting, and there are no Bash, CLI, or Linux-specific instructions provided.
Recommendations
  • Provide equivalent troubleshooting steps using Azure CLI and Bash scripts for Linux users.
  • Mention cross-platform module management tools and patterns, such as az automation module commands.
  • Include examples of how to resolve issues on Linux-based automation accounts or hybrid worker scenarios.
  • Clarify which steps are Windows-specific and offer alternative instructions for Linux environments.
  • Reference Linux file formats and dependency management (e.g., .so files, shell scripts) where relevant.
GitHub Create Pull Request
Automation Runtime Environment in Azure Automation ...in/articles/automation/runtime-environment-overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a bias towards Windows and PowerShell environments. PowerShell is mentioned as the primary scripting language, with multiple versions listed and detailed integration with Azure CLI. Examples and package management references focus on PowerShell and Windows-centric tools, with little to no mention of Linux-specific patterns, shell scripting, or non-Windows automation tools. Python is referenced, but only as an alternative language, without parity in examples or tooling. There are no Linux shell (bash) examples, nor is there discussion of Linux-native package management or runtime environments.
Recommendations
  • Add examples and guidance for Linux shell scripting (e.g., bash) in Azure Automation runbooks.
  • Include details on how to use Azure CLI directly in Python or bash runbooks, not just PowerShell.
  • List Linux-native package management options and patterns for custom packages (e.g., pip for Python, apt for bash).
  • Provide parity in documentation for Python environments, including versioning, package management, and integration with Azure CLI.
  • Explicitly mention cross-platform support and clarify any Windows-specific limitations or behaviors.
  • Add links to Linux and Python documentation alongside PowerShell references.
GitHub Create Pull Request
Automation Remove DSC and node from Automation State Configuration ...configuration/remove-node-and-configuration-package.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell and Windows-specific tools (cmdlets like Unregister-AzAutomationDscNode and Remove-DscConfigurationDocument) are mentioned first and in more detail, while Linux instructions are less prominent and less detailed. The manual deletion section provides explicit PowerShell commands for Windows but only describes file deletion for Linux without command-line examples. The overall structure and examples favor Windows users, with Linux instructions often appearing as secondary notes.
Recommendations
  • Provide equivalent Linux command-line examples (e.g., shell commands for deleting .mof files) alongside PowerShell examples.
  • Present Windows and Linux instructions in parallel, rather than listing Windows steps first.
  • Include references to Linux-native automation tools (such as Bash scripts or Ansible) where appropriate.
  • Expand Linux sections to match the detail and clarity of Windows instructions, including troubleshooting and verification steps.
  • Avoid assuming PowerShell as the default tool; clarify when instructions are OS-specific.
GitHub Create Pull Request
Automation Troubleshoot agent-based Hybrid Runbook Worker issues in Azure Automation ...icles/automation/troubleshoot/hybrid-runbook-worker.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates a Windows bias in several ways: troubleshooting steps and examples are often presented for Windows first or exclusively, with PowerShell commands and Windows-specific tools (event logs, registry keys, config files) dominating the guidance. Linux troubleshooting is covered in a separate, shorter section, and some scenarios (e.g., updating Az modules, config file changes, registry edits) only provide Windows instructions or examples. In mixed sections, Windows tools and patterns (event logs, registry, PowerShell) are mentioned before or instead of Linux equivalents.
Recommendations
  • Provide Linux-specific troubleshooting steps and examples for all scenarios currently covered only for Windows (e.g., updating Az modules, config file changes, registry edits).
  • Where PowerShell or Windows event logs are referenced, include equivalent Linux commands (e.g., Bash, journalctl, syslog) and file paths.
  • Ensure that Linux and Windows troubleshooting guidance is presented in parallel for each scenario, rather than segregating Linux into a separate section.
  • Include Linux-specific error messages and their resolutions alongside Windows examples.
  • Reference Linux tools and patterns (e.g., systemd, sudoers, log file locations) with the same level of detail as Windows tools.
  • Avoid using Windows paths and registry keys as the default; provide Linux equivalents where relevant.
GitHub Create Pull Request
Automation Configure machines to a desired state in Azure Automation ...automation/tutorial-configure-servers-desired-state.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation is heavily biased towards Windows and PowerShell. All examples use Windows-specific resources (such as installing IIS via WindowsFeature) and PowerShell cmdlets. The prerequisites and instructions focus exclusively on Windows VMs, with no Linux configuration examples or equivalent Linux tooling mentioned. References to onboarding Linux machines are present only as links, not as actionable steps or examples.
Recommendations
  • Add explicit Linux configuration examples, such as using DSC resources for Linux (e.g., nxPackage, nxFile) and show how to configure a Linux VM to a desired state.
  • Include Bash/CLI examples or instructions for Linux users, not just PowerShell.
  • Update prerequisites to mention Linux VM support, and provide links to creating Linux VMs in Azure.
  • Present Windows and Linux instructions/examples in parallel, or clarify platform-specific differences early in the document.
  • Reference Linux equivalents for Windows tools and patterns (e.g., alternatives to WindowsFeature for package installation on Linux).
GitHub Create Pull Request
Avere Vfxt Disaster recovery guidance for Avere vFXT for Azure ...ocs/blob/main/articles/avere-vfxt/disaster-recovery.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates Windows bias by mentioning Azure PowerShell and AzCopy (both Windows-centric tools) as primary options for copying data, without referencing Linux-native equivalents or providing Linux command-line examples. The order of tool presentation also puts Windows tools before alternatives, and there are no explicit Linux workflow examples or mentions of Linux copy tools.
Recommendations
  • Include Linux-native copy tool examples, such as using 'azcopy' from the Linux command line, 'Azure CLI' (az storage blob copy), or 'rsync' for NAS storage.
  • Present cross-platform tools (e.g., AzCopy, Azure CLI) with explicit instructions for both Windows and Linux environments.
  • Add sample commands for Linux users alongside PowerShell examples, ensuring parity in guidance.
  • Mention installation and usage steps for Linux tools where appropriate.
  • Avoid listing Windows tools first; instead, group cross-platform tools together and clarify their OS compatibility.
GitHub Create Pull Request
Azure App Configuration Tutorial: Use Dynamic Configuration Using Push Refresh in a .NET App ...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/enable-dynamic-configuration-dotnet-core-push-refresh.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. Environment variable setup instructions are presented in a Windows-first order (Command Prompt, then PowerShell, then macOS/Linux), and screenshots consistently show Windows Command Prompt. While Linux/macOS commands are included, there are no screenshots or explicit instructions for running or troubleshooting on Linux. The use of Windows-specific tools and patterns (Command Prompt, PowerShell) is more prominent, and Linux is treated as an afterthought. There are no Linux-specific troubleshooting tips or examples, and the visual cues reinforce Windows as the default platform.
Recommendations
  • Present environment variable setup instructions in a neutral or rotating order (e.g., Linux/macOS first in some sections).
  • Include screenshots of the app running in Linux/macOS terminals alongside Windows examples.
  • Add troubleshooting notes or tips for Linux/macOS users (e.g., shell differences, permissions, environment variable persistence).
  • Explicitly mention that all steps and code samples are cross-platform, and highlight any platform-specific caveats.
  • Where possible, use generic .NET CLI commands and avoid referencing Windows-only tools unless necessary.
  • Add a section or callout for Linux/macOS users to ensure parity and inclusivity.
GitHub Create Pull Request
Azure App Configuration Quickstart for Azure App Configuration with Aspire .../articles/azure-app-configuration/quickstart-aspire.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ docker_desktop_bias ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a subtle Windows bias by exclusively referencing Docker Desktop (which is most commonly used on Windows and Mac), omitting Linux-specific container runtime instructions. There are no examples or instructions tailored for Linux users, such as using Podman or native Docker on Linux. The documentation does not mention platform-specific differences or provide parity for Linux environments, which may leave Linux users uncertain about compatibility or required steps.
Recommendations
  • Explicitly mention Linux as a supported development environment in the prerequisites and throughout the guide.
  • Provide instructions or notes for installing and using Docker on Linux (e.g., apt/yum installation commands, service management).
  • Reference alternative container runtimes such as Podman, especially for Linux users.
  • Include screenshots or CLI commands from Linux environments where relevant.
  • Add troubleshooting tips for common Linux-specific issues (e.g., permissions, networking).
  • Avoid referring only to Docker Desktop; use more generic terms like 'Docker' or 'OCI-compliant container runtime', and link to official Linux installation guides.
GitHub Create Pull Request
Azure App Configuration Quickstart for Azure App Configuration with Azure Functions | Microsoft Docs ...app-configuration/quickstart-azure-functions-csharp.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ visual_studio_heavy ⚠ī¸ powershell_heavy
Summary
The documentation demonstrates a Windows bias by prioritizing Visual Studio (Windows-only) as the development environment, listing Windows command prompt and PowerShell instructions before Linux/macOS equivalents, and relying on screenshots and workflow descriptions that assume a Windows/Visual Studio context. Linux and macOS instructions are present but secondary, and alternative cross-platform tools (such as VS Code or Azure Functions Core Tools CLI) are not mentioned.
Recommendations
  • Add instructions for creating and running Azure Functions apps using cross-platform tools like Visual Studio Code and Azure Functions Core Tools CLI.
  • Present environment variable setting instructions for Linux/macOS before or alongside Windows examples, rather than after.
  • Include screenshots and workflow steps for non-Windows environments (e.g., VS Code debugging, terminal usage).
  • Clarify that Visual Studio is optional and provide parity for Linux/macOS users throughout the quickstart.
  • Reference cross-platform installation and usage guides for Azure Functions development.
GitHub Create Pull Request
Azure App Configuration Create an Azure App Configuration store by using Azure Resource Manager template (ARM template) ...azure-app-configuration/quickstart-resource-manager.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides deployment instructions using PowerShell only, with no equivalent Azure CLI or Bash examples. PowerShell is a Windows-centric tool, and its exclusive use in deployment and cleanup sections suggests a bias toward Windows users. The only CLI command shown is for a specific configuration scenario, not for the main deployment workflow. There is no mention of Linux or cross-platform alternatives for the main steps.
Recommendations
  • Add Azure CLI examples for deploying and cleaning up resources, as Azure CLI is cross-platform and commonly used on Linux and macOS.
  • Include Bash script examples for resource deployment and cleanup to demonstrate parity for Linux users.
  • Present CLI and PowerShell instructions side-by-side, or clearly indicate both options, to avoid Windows-first bias.
  • Explicitly mention that Azure CLI and Bash can be used on Linux/macOS, and provide links to relevant documentation.
GitHub Create Pull Request
Azure Cache For Redis Reboot, Flush, and Schedule Updates Azure Cache for Redis ...articles/azure-cache-for-redis/cache-administration.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a bias toward Windows and PowerShell by exclusively providing PowerShell examples and references for management tasks such as rebooting and scheduling updates. There is no mention of Linux-specific tools, nor are there CLI (az CLI), Bash, or REST API examples. PowerShell is repeatedly referenced as the primary method for automation and configuration, and Windows-centric terminology and tools are presented before or instead of cross-platform alternatives.
Recommendations
  • Add equivalent az CLI examples for all management tasks (reboot, flush, schedule updates) alongside PowerShell examples.
  • Include Bash script snippets or REST API calls for common operations to ensure Linux parity.
  • Explicitly mention that PowerShell is available cross-platform, but also provide instructions for Linux users using native tools.
  • Reorder sections or present CLI and REST API options before or alongside PowerShell to avoid Windows-first perception.
  • Add a table or section summarizing all available management interfaces (Portal, PowerShell, CLI, REST API) with links to platform-specific documentation.
GitHub Create Pull Request
Azure App Configuration Quickstart for Adding Feature Flags to .NET/.NET Framework Apps ...re-app-configuration/quickstart-feature-flag-dotnet.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation page exhibits Windows bias by exclusively providing instructions and examples for setting environment variables using Windows Command Prompt and PowerShell, with no mention of Linux or macOS equivalents (such as Bash or export commands). Visual Studio is presented as the only development environment, which is primarily a Windows tool. All screenshots and workflow steps assume a Windows environment, and there is no guidance for users on other platforms. This may hinder Linux or macOS developers from following the quickstart without additional research.
Recommendations
  • Add equivalent instructions for setting environment variables on Linux/macOS (e.g., using export in Bash or zsh).
  • Include examples for using cross-platform editors like VS Code or JetBrains Rider, or clarify that the steps can be adapted for other IDEs.
  • Provide screenshots and workflow notes for running the app in Linux/macOS terminals.
  • Explicitly state platform compatibility and provide guidance for non-Windows users where steps differ.
  • Consider using platform tabs or callouts to distinguish Windows-specific and Linux/macOS-specific instructions.
GitHub Create Pull Request
Azure App Configuration Azure App Configuration REST API - Microsoft Entra authorization ...e-app-configuration/rest-api-authorization-azure-ad.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation mentions PowerShell and the Azure portal as tools for managing role assignments before mentioning the Azure CLI. There are no explicit Linux-specific examples, and the guidance leans toward Windows-centric tools and workflows, such as PowerShell, without providing parity for Linux users.
Recommendations
  • Provide explicit examples using Azure CLI commands, which are cross-platform, and place them before or alongside PowerShell examples.
  • Include references to Linux shell environments (e.g., Bash) and how to use Azure CLI from those environments.
  • Ensure that instructions do not assume the use of Windows-only tools and clarify that Azure CLI works on Linux, macOS, and Windows.
  • Add links to documentation for installing and using Azure CLI on Linux.
GitHub Create Pull Request
DNS Azure DNS Private Resolver endpoints and rulesets ...in/articles/dns/private-resolver-endpoints-rulesets.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias primarily by referencing Azure PowerShell as the only command-line example for creating a DNS Private Resolver, with no mention of Linux-friendly tools such as Azure CLI or Bash scripts. The 'Next steps' section lists PowerShell before the Azure portal and omits Linux/CLI options. No Linux-specific patterns, tools, or examples are provided, and there is no discussion of cross-platform command-line usage.
Recommendations
  • Add Azure CLI examples for creating and managing DNS Private Resolvers alongside PowerShell examples.
  • Explicitly mention that both Windows and Linux users can use Azure CLI and provide Bash script snippets where appropriate.
  • Ensure that references to command-line tools do not prioritize Windows tools (e.g., PowerShell) over cross-platform alternatives.
  • Include a section or note on platform compatibility, clarifying that all features are accessible from Linux, macOS, and Windows.
  • Provide links to both PowerShell and CLI documentation in 'Next steps' and throughout the article.
GitHub Create Pull Request
DNS Overview of DNS security policy ...ure-docs/blob/main/articles/dns/dns-security-policy.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation mentions Azure PowerShell as a configuration method for DNS security policy, but does not reference Azure CLI or provide Linux-oriented examples. There are no Linux shell commands, nor is there mention of Linux tools or workflows. The configuration instructions and screenshots focus on the Azure portal and PowerShell, which are more commonly used on Windows, suggesting a Windows-first approach and missing Linux parity.
Recommendations
  • Include Azure CLI examples alongside PowerShell for all configuration steps, as Azure CLI is cross-platform and widely used on Linux.
  • Explicitly mention support for Linux and macOS environments where applicable.
  • Provide bash or shell script examples for common tasks, such as querying DNS logs or managing domain lists.
  • Add a section comparing PowerShell and Azure CLI usage, highlighting platform compatibility.
  • Ensure screenshots and UI references are not specific to Windows-only tools.
GitHub Create Pull Request
DNS Scenarios for Azure Private DNS zones ...e-docs/blob/main/articles/dns/private-dns-scenarios.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits Windows bias primarily in the 'Next steps' section, where the link to 'create a Private DNS zone' points specifically to a PowerShell-based guide, which is most commonly used on Windows. There are no Linux-specific examples, CLI commands, or references to Linux tooling throughout the scenarios or guidance. The documentation does not mention or provide parity for Linux users, such as using Azure CLI or Bash, nor does it reference Linux DNS tools (e.g., dig, nslookup) for querying or troubleshooting.
Recommendations
  • Add equivalent Linux examples using Azure CLI (az) commands for creating and managing Private DNS zones.
  • Include references to Linux DNS query tools (e.g., dig, nslookup) in scenario explanations and troubleshooting steps.
  • Provide links to documentation pages that cover both PowerShell and Azure CLI/Bash workflows for DNS zone management.
  • Ensure that examples and instructions are platform-neutral or present both Windows and Linux options side-by-side.
  • Explicitly mention cross-platform compatibility and best practices for both Windows and Linux administrators.
GitHub Create Pull Request
DNS Private resolver architecture ...lob/main/articles/dns/private-resolver-architecture.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias primarily in the 'Next steps' section, where only Azure PowerShell and Azure portal are mentioned as configuration methods, with no reference to Azure CLI or Linux-based tooling. There are no examples or instructions for Linux users, and Windows-centric tools (PowerShell) are listed before any alternatives. The main architecture guidance is platform-neutral, but the actionable setup guidance favors Windows environments.
Recommendations
  • Include Azure CLI instructions alongside PowerShell and portal for creating and configuring Azure DNS Private Resolver.
  • Explicitly mention Linux and cross-platform options for DNS configuration and management.
  • Provide example commands for both Windows (PowerShell) and Linux (Azure CLI, shell scripting) users.
  • Ensure parity in troubleshooting and operational guidance for both Windows and Linux environments.
GitHub Create Pull Request
Event Grid Azure Resource Manager template samples - Event Grid | Microsoft Docs ...docs/blob/main/articles/event-grid/template-samples.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page lists PowerShell samples before CLI samples in the 'Next steps' section, suggesting a Windows-first approach. There is a specific mention of PowerShell, which is traditionally associated with Windows, and no explicit mention of Bash or Linux shell examples. The page lacks Linux-specific guidance or parity in examples.
Recommendations
  • List CLI (az CLI) samples before PowerShell samples to avoid Windows-first bias.
  • Add explicit Bash/Linux shell script examples for deploying and managing Event Grid resources.
  • Include notes or links for Linux users, such as installation and usage of Azure CLI on Linux.
  • Ensure that all sample templates and deployment instructions are cross-platform and clarify any platform-specific steps.
GitHub Create Pull Request
Expressroute ExpressRoute for Cloud Solution Providers - Azure | Microsoft Docs ...ressroute/expressroute-for-cloud-solution-providers.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates Windows bias in several ways: it references PowerShell as the primary method for managing ExpressRoute routing filters, links to Windows-specific management APIs, and omits Linux or cross-platform CLI examples. Windows tools and terminology are mentioned exclusively or before any Linux equivalents, and there is a lack of parity in example commands or tooling for Linux users.
Recommendations
  • Include Azure CLI and/or REST API examples alongside PowerShell for all configuration steps, especially for routing and circuit management.
  • Reference cross-platform management tools and APIs, not just Windows-specific ones.
  • Add explicit Linux usage scenarios and commands for ExpressRoute provisioning and management.
  • Ensure links to management capabilities and workflows include Linux and macOS compatibility information.
  • Review all examples and instructions to provide parity for Linux users, avoiding exclusive reliance on Windows tooling.
GitHub Create Pull Request
Azure Netapp Files Understand SMB file permissions in Azure NetApp Files ...-netapp-files/network-attached-file-permissions-smb.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page focuses exclusively on NTFS ACLs and references Microsoft's Windows documentation for access control, without mentioning Linux file permission models (such as POSIX ACLs) or providing any Linux-specific examples or tools. The terminology and linked resources are Windows-centric, and there is no guidance for users managing SMB permissions from Linux clients.
Recommendations
  • Include a section comparing NTFS ACLs with POSIX ACLs to help Linux administrators understand differences and interoperability.
  • Provide examples of managing SMB permissions from Linux clients, such as using the 'smbcacls' tool or 'setfacl' where applicable.
  • Reference Linux documentation or resources for SMB and file permissions, in addition to Microsoft/Windows links.
  • Clarify whether and how Linux clients can view or modify NTFS ACLs on Azure NetApp Files SMB volumes.
  • Add troubleshooting tips for Linux users accessing SMB shares with NTFS ACLs.
GitHub Create Pull Request
Azure Netapp Files Understand NAS file permissions in Azure NetApp Files ...zure-netapp-files/network-attached-file-permissions.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page presents Windows/SMB permission management patterns and tools (such as the 'advanced permission view' and a screenshot of a Windows interface) before Linux/NFS equivalents. It describes Windows inheritance mechanisms in detail, including UI elements, while Linux/NFS methods are mentioned briefly and without examples or screenshots. There are no Linux command-line examples (e.g., setfacl, chmod, chown) or screenshots of Linux tools, resulting in a lack of parity for Linux administrators.
Recommendations
  • Provide Linux/NFS command-line examples for managing permissions and inheritance (e.g., setfacl, chmod, chown, umask, setgid).
  • Include screenshots or step-by-step instructions for Linux/NFS permission management, similar to the Windows example.
  • Present Windows and Linux/NFS methods in parallel, giving equal detail and prominence to both.
  • Clarify differences and similarities in permission inheritance mechanisms between SMB (Windows) and NFS (Linux), with practical guidance for each.
GitHub Create Pull Request
Azure Netapp Files Access an Azure NetApp Files object REST API-enabled volume with S3-compatible clients ...articles/azure-netapp-files/object-rest-api-browser.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates Windows bias by prioritizing Windows-specific instructions and tools. The certificate installation steps are written for Windows, referencing the Edge browser and Windows certificate store, with no Linux or macOS equivalent provided. S3 Browser, a Windows-only tool, is featured exclusively. While AWS CLI installation is covered for both Windows and Linux, the overall flow and examples favor Windows environments.
Recommendations
  • Add explicit instructions for installing certificates on Linux (e.g., using OpenSSL and updating system trust stores) and macOS.
  • Include examples using Linux-native S3 clients (e.g., s3cmd, rclone, or MinIO client) alongside S3 Browser.
  • Present installation and usage steps for both Windows and Linux/macOS in parallel, rather than Windows-first.
  • Clarify cross-platform compatibility for all steps and tools mentioned.
  • Consider adding screenshots or terminal commands for Linux/macOS workflows where appropriate.
GitHub Create Pull Request
Azure Netapp Files Understand guidelines for Active Directory Domain Services site design and planning ...rstand-guidelines-active-directory-domain-service-site.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by consistently referencing Windows-centric tools (such as Active Directory Sites and Services), providing step-by-step instructions and screenshots for Windows GUI utilities, and prioritizing Windows authentication scenarios. Linux client support is mentioned only briefly, with no equivalent configuration examples or tooling guidance. There are no Linux-specific instructions, screenshots, or parity for site topology management, and all sample workflows use Windows tools.
Recommendations
  • Add Linux-focused examples for AD DS integration, including configuration steps for Kerberos authentication and LDAP client setup on Linux systems.
  • Provide CLI-based instructions (e.g., using samba-tool, ldapsearch, or realm commands) for managing AD DS site topology and verifying domain controller assignments from Linux environments.
  • Include screenshots or terminal output from Linux tools where appropriate, alongside Windows GUI screenshots.
  • Explicitly mention cross-platform considerations and clarify which steps are OS-agnostic versus Windows-specific.
  • Ensure that troubleshooting and validation steps (such as checking DNS SRV records) include Linux command-line equivalents (e.g., dig, host, nslookup on Linux).
GitHub Create Pull Request
Azure Netapp Files Azure NetApp Files tools ...ob/main/articles/azure-netapp-files/tools-reference.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page lists several tools for Azure NetApp Files, but only provides a specific example of automation and reporting using PowerShell (ANFHealthCheck), which is Windows-centric. There are no equivalent Linux/bash examples or mentions of Linux-native automation/reporting tools. The use of PowerShell as the sole scripting example suggests a bias towards Windows environments, and Linux users may not find guidance for their preferred platforms.
Recommendations
  • Add examples or references for Linux/bash-based automation and reporting tools for Azure NetApp Files.
  • Provide cross-platform scripts or indicate if tools like ANFHealthCheck can be run with PowerShell Core on Linux/macOS.
  • Include guidance or links for using Azure CLI, shell scripts, or other Linux-friendly tools for monitoring and managing Azure NetApp Files.
  • Ensure that future documentation lists both Windows and Linux options for automation and monitoring, or explicitly states platform compatibility.
GitHub Create Pull Request
Azure Netapp Files Understand volume languages in Azure NetApp Files ...cles/azure-netapp-files/understand-volume-languages.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. Windows tools (Explorer, PowerShell, CMD, Notepad, Notepad++) are mentioned and illustrated first or exclusively in several sections, especially in SMB and file encoding conversion scenarios. PowerShell examples and screenshots are prevalent, while equivalent Linux command-line examples (e.g., using 'file', 'iconv', 'cat') are less frequent and often appear later in the text. Windows-specific troubleshooting and configuration (fonts, region settings, code pages) are described in detail, whereas Linux alternatives (e.g., changing locale, font support in terminals) are not covered with the same depth. Some conversion and encoding operations are shown only with PowerShell, with Linux alternatives mentioned briefly or not at all.
Recommendations
  • Provide Linux command-line examples (e.g., using 'iconv', 'file', 'cat', 'locale', 'ls', 'stat') alongside or before Windows/PowerShell examples in all relevant sections.
  • Include troubleshooting steps for Linux clients (e.g., handling fonts, locale settings, encoding issues in common terminals like GNOME Terminal, xterm, etc.), similar to the depth given for Windows.
  • Mention and illustrate Linux-native tools for file encoding conversion and inspection (e.g., 'vim', 'nano', 'file', 'iconv') with screenshots or command output.
  • Balance the order of presentation so that Linux and Windows examples are given equal prominence, or alternate which platform is described first in each section.
  • Expand on Linux-specific behaviors and limitations (e.g., how different distributions or desktop environments handle Unicode, encoding, and font rendering).
  • Add notes or tips for Linux users regarding common pitfalls (e.g., locale misconfiguration, font package installation for CJK/emoji support).
GitHub Create Pull Request
Azure Resource Manager Quickstart: Create Bicep files with Visual Studio Code ...icep/quickstart-create-bicep-use-visual-studio-code.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a moderate Windows bias. Windows-centric tools (Visual Studio Code, Bicep extension, Azure PowerShell) are mentioned prominently, and PowerShell examples are provided alongside Azure CLI. The deployment workflow is described primarily through Visual Studio Code's GUI, which is most commonly used on Windows. There are no Linux-specific instructions, nor are Linux terminal patterns (e.g., Bash, shell scripting) referenced. The order of examples and tool mentions generally favors Windows-first patterns.
Recommendations
  • Explicitly mention Linux and macOS compatibility for Visual Studio Code and the Bicep extension.
  • Provide Linux-specific instructions for installing prerequisites (e.g., using apt, yum, or Homebrew for Bicep and Azure CLI).
  • Include Bash or shell script examples for deployment and cleanup, especially for users who prefer terminal workflows.
  • Clarify that Azure CLI commands work cross-platform and highlight any differences in usage between Windows and Linux/macOS.
  • Add troubleshooting tips for common Linux/macOS issues (e.g., permissions, path configuration).
  • Consider adding screenshots from Linux/macOS environments to balance the visual representation.
GitHub Create Pull Request
Azure Resource Manager Create and deploy a template spec with Bicep ...urce-manager/bicep/quickstart-create-template-specs.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation exhibits Windows bias by consistently using Windows-style file paths (e.g., C:\templates\main.bicep) in all CLI and PowerShell examples, without providing Linux/macOS equivalents. All command examples assume a Windows environment, and there is no mention of Linux-specific patterns, such as using forward slashes in file paths or handling environment variables in Bash. The documentation also references Windows tools (PowerShell) and links to PowerShell-based tutorials for access control, without offering Bash or Linux alternatives.
Recommendations
  • Provide Linux/macOS file path examples (e.g., ~/templates/main.bicep or /home/user/templates/main.bicep) alongside Windows paths in all CLI and PowerShell command samples.
  • Explicitly mention cross-platform compatibility of Azure CLI and PowerShell, and note any platform-specific caveats.
  • Where PowerShell is referenced for role assignments or other tasks, include equivalent Bash/Azure CLI instructions.
  • Add notes or tabs for Linux/macOS users, especially for steps involving file paths, environment variables, or shell scripting.
  • Ensure all command snippets and explanations are clear about platform differences, and avoid assuming a Windows-only environment.
GitHub Create Pull Request
Azure Resource Manager Azure Resource Manager resource group and resource deletion ...e-resource-manager/management/delete-resource-group.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page demonstrates Windows bias by consistently presenting PowerShell examples first, referencing PowerShell-specific commands, and using terminology and tooling (PowerShell) that is native to Windows. While Azure CLI and Python examples are included, the ordering and prominence of PowerShell, as well as the lack of explicit Linux shell examples (e.g., Bash), reinforce a Windows-centric approach. There are no direct Linux shell or scripting examples, and no mention of Linux-specific considerations or tools.
Recommendations
  • Alternate the order of examples so that Azure CLI (cross-platform) or Bash examples appear before PowerShell.
  • Include explicit Bash shell examples for resource deletion, demonstrating usage in a Linux environment.
  • Clarify that Azure CLI works on both Windows and Linux, and provide installation/usage notes for Linux users.
  • Add notes or sections highlighting Linux-specific considerations, such as differences in authentication or environment setup.
  • Reduce reliance on PowerShell-specific syntax and terminology, or provide equivalent Linux-native commands where appropriate.
GitHub Create Pull Request
Azure Resource Manager Move guidance for classic deployment model resources ...ent/move-limitations/classic-model-move-limitations.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation refers to Azure PowerShell before Azure CLI when listing move operations, and does not provide any explicit Linux-specific examples or guidance. The mention of PowerShell (a Windows-centric tool) before CLI may suggest a Windows-first bias. There are no examples of using Linux-native tools or shell environments, nor is there parity in showing how to perform these operations on Linux systems.
Recommendations
  • List Azure CLI before Azure PowerShell when mentioning cross-platform tools, or mention them together to avoid implying preference.
  • Provide explicit examples of move operations using Azure CLI in Bash or other Linux shells.
  • Clarify that all operations can be performed equally on Linux, macOS, and Windows, and link to platform-specific instructions if available.
  • Avoid referencing PowerShell exclusively; ensure that CLI commands are shown alongside or before PowerShell commands.
  • Add a section or note on how Linux users can perform these operations, including installation and usage of Azure CLI.
GitHub Create Pull Request
Azure Vmware Configure VMware vSAN ESA .../blob/main/articles/azure-vmware/configure-vsan-esa.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing PowerShell cmdlets (e.g., Set-vSANDataInTransitEncryption), Azure portal workflows, and Windows-centric features such as Windows Server Failover Clusters. There are no Linux CLI examples, nor are Linux tools or workflows mentioned for managing vSAN ESA features. The documentation assumes users are operating in a Windows/Azure environment and omits guidance for Linux administrators.
Recommendations
  • Include equivalent Linux command-line examples (e.g., using VMware's CLI tools such as esxcli or govc) for configuring vSAN ESA features.
  • Mention and document how Linux-based VMs interact with TRIM/UNMAP and other vSAN features, including any OS-specific requirements or flags.
  • Provide parity in instructions for both Windows and Linux environments, such as how to run commands from Linux shells or using REST APIs.
  • Reference Linux-supported clustering solutions (e.g., Pacemaker, Corosync) where relevant, not just Windows Server Failover Clusters.
  • Clarify whether the PowerShell cmdlets and Azure portal workflows are mandatory, or if alternative cross-platform tools can be used.
GitHub Create Pull Request
Azure Vmware Configure VMware vSAN ...docs/blob/main/articles/azure-vmware/configure-vsan.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by exclusively providing examples using PowerShell cmdlets and Azure portal workflows, with no mention of Linux CLI or automation equivalents. Windows prerequisites are listed before Linux, and there are no Linux-specific usage or configuration examples for vSAN management. The documentation assumes users are operating in a Windows-centric environment, omitting guidance for Linux administrators.
Recommendations
  • Include Linux CLI or automation examples (e.g., using VMware's PowerCLI on Linux, or REST API usage via curl or Python).
  • Provide parity in prerequisites and instructions, listing Linux requirements alongside Windows, and not always after.
  • Mention cross-platform tools and workflows, such as how to perform these tasks from Linux or macOS environments.
  • Add references to Linux-specific documentation or community resources for managing VMware vSAN.
  • Clarify which steps are platform-agnostic and which require Windows-specific tooling.
GitHub Create Pull Request
Azure Vmware Deploy Arc-enabled VMware vSphere for Azure VMware Solution private cloud ...s/azure-vmware/deploy-arc-for-azure-vmware-solution.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a moderate Windows bias. Windows-based instructions (PowerShell) are presented before Linux equivalents, and Windows-specific tooling (e.g., Set-ExecutionPolicy, .ps1 scripts, Windows file paths) is referenced more frequently and in greater detail. Linux instructions are present but appear secondary. Examples such as certificateFilePath use Windows-style paths, and proxy configuration examples also default to Windows conventions.
Recommendations
  • Present Linux and Windows instructions in parallel, or alternate which platform is shown first.
  • Use platform-neutral file path examples (e.g., /home/user/file.crt and C:\Users\file.crt) in config samples.
  • Expand Linux-specific guidance (e.g., troubleshooting, permissions, script execution) to match Windows detail.
  • Explicitly mention cross-platform compatibility for all scripts and tools, and link to platform-specific prerequisites if needed.
  • Ensure all screenshots, UI references, and examples are available for both Windows and Linux environments.
GitHub Create Pull Request
Azure Vmware Deploy Zerto disaster recovery on Azure VMware Solution ...rticles/azure-vmware/deploy-zerto-disaster-recovery.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a moderate Windows bias, primarily in its description of the Zerto Cloud Appliance (ZCA), which is presented as a Windows-only VM for Azure IaaS VM recovery. Windows services (ZVM and VRA) are highlighted for Azure integration, while Linux equivalents or alternatives are not mentioned or provided. Although the core Zerto management and replication components are described as Linux-based, there are no Linux-specific deployment or troubleshooting examples, and Windows tooling is emphasized for cloud scenarios.
Recommendations
  • Provide equivalent Linux-based examples and tooling for Azure VM recovery scenarios, or clarify if such options are unavailable.
  • Explicitly mention the absence or presence of Linux alternatives for ZCA and related services.
  • Include Linux command-line or automation examples for installation, configuration, and troubleshooting, especially for hybrid or cloud deployments.
  • Ensure that both Windows and Linux patterns are presented in parallel where possible, rather than focusing on Windows-first solutions.
  • Add guidance for Linux administrators on integrating Zerto with Azure, including any limitations or workarounds.
GitHub Create Pull Request
Azure Vmware vCenter Server access and identity description ...vmware/includes/vcenter-access-identity-description.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows Server Active Directory for user and group management, without mentioning or providing examples for Linux-based identity solutions (such as OpenLDAP). Windows tools and patterns are mentioned first and exclusively, with no Linux equivalents or parity in examples.
Recommendations
  • Include examples and guidance for integrating Linux-based identity sources (e.g., OpenLDAP) with vCenter Server.
  • Mention Linux tools and patterns alongside Windows Server Active Directory when discussing user and group management.
  • Provide parity in documentation by showing how both Windows and Linux administrators can configure identity sources and assign roles.
  • Clarify any platform-specific limitations or requirements for identity source integration, and offer alternative solutions for non-Windows environments.
GitHub Create Pull Request
Azure Vmware Install Cloud Backup for Virtual Machines .../azure-vmware/install-cloud-backup-virtual-machines.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Azure portal run commands and VMware vSphere client interfaces, which are typically accessed from Windows environments. All operational instructions (install, upgrade, uninstall, password reset) are given using GUI workflows or PowerShell-like command names (e.g., Install-NetAppCBSA), with no mention of Linux CLI, shell scripts, or cross-platform alternatives. There are no examples or guidance for performing these tasks from Linux systems or using Linux-native tools.
Recommendations
  • Provide equivalent Linux CLI instructions for installation, upgrade, and uninstallation, such as using Azure CLI, REST API, or shell scripts.
  • Include examples of accessing and managing the VMware vSphere client from Linux environments (e.g., using open-source vSphere clients or web interfaces).
  • Clarify whether the run commands can be executed from Linux systems and, if so, provide step-by-step guidance.
  • Mention any Linux prerequisites or compatibility notes for the Cloud Backup plug-in.
  • Ensure screenshots and field tables do not assume a Windows-only context (e.g., show browser-based interfaces or CLI outputs from Linux terminals).
GitHub Create Pull Request
Azure Vmware Migrate Microsoft SQL Server Always On Availability Group to Azure VMware Solution ...are/migrate-sql-server-always-on-availability-group.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation is heavily focused on Windows-based SQL Server deployments, specifically referencing Windows Server Failover Clustering and SQL Server Management Studio (SSMS) throughout. All examples, prerequisites, and migration steps assume a Windows environment, with no mention of Linux-based SQL Server deployments or tools. References and links are exclusively for Windows Server and related Microsoft technologies, omitting any Linux equivalents or cross-platform considerations.
Recommendations
  • Include guidance for migrating SQL Server Always On Availability Groups running on Linux, referencing supported distributions and clustering technologies (e.g., Pacemaker).
  • Provide examples using cross-platform SQL Server tools, such as Azure Data Studio, or command-line tools available on Linux.
  • Add documentation links for SQL Server on Linux, including official Microsoft guides and best practices for high availability on Linux.
  • Discuss differences in migration steps or prerequisites for Linux-based SQL Server deployments, ensuring parity in instructions.
  • Mention alternative witness/quorum configurations available on Linux and how to handle them during migration.
GitHub Create Pull Request
Azure Vmware Migrate Microsoft SQL Server Standalone to Azure VMware Solution .../azure-vmware/migrate-sql-server-standalone-cluster.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a clear Windows bias. All examples, tested configurations, and prerequisites reference only Windows Server and Microsoft SQL Server. There are no mentions of Linux-based SQL Server deployments, nor are there examples or guidance for migrating SQL Server running on Linux. Tools and procedures (such as SQL Server Management Studio and Windows Server Failover Clustering) are Windows-centric, and Linux alternatives are not discussed.
Recommendations
  • Include tested configurations and migration steps for SQL Server running on Linux (e.g., Ubuntu, Red Hat).
  • Provide examples using Linux tools (such as sqlcmd, Azure Data Studio) alongside SQL Server Management Studio.
  • Reference Linux clustering solutions (e.g., Pacemaker) and provide links to relevant documentation.
  • Clarify whether VMware HCX migration steps differ for Linux-based SQL Server VMs and document any differences.
  • Add troubleshooting and verification steps for Linux environments, including connectivity checks and service validation.
GitHub Create Pull Request
Azure Vmware Enable first-party application service principal for Azure VMware Solution Generation 2 Private Clouds .../azure-vmware/native-first-party-principle-security.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides step-by-step instructions for enabling the service principal using the Microsoft Entra ID portal (GUI), Azure PowerShell, and Azure CLI. The PowerShell example is detailed and presented before the Azure CLI example, which is more cross-platform. There are no Linux-specific instructions or examples, and the PowerShell commands are Windows-centric. The documentation implicitly prioritizes Windows tools and workflows, with no mention of Linux shell environments or alternative command-line tools.
Recommendations
  • Provide explicit Linux shell examples for Azure CLI usage, including notes about installation and environment differences.
  • Reorder the command-line options to present Azure CLI (cross-platform) before PowerShell (Windows-centric).
  • Add notes clarifying that Azure CLI works on Windows, Linux, and macOS, and provide troubleshooting tips for Linux users.
  • Where PowerShell is mentioned, note that PowerShell Core is available on Linux and macOS, and provide installation links.
  • Include screenshots or instructions for using the portal from non-Windows browsers or devices.
GitHub Create Pull Request
Azure Vmware Protect web apps on Azure VMware Solution with Azure Application Gateway ...protect-azure-vmware-solution-with-application-gateway.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a strong Windows bias in its configuration examples. All backend VM setup instructions use Windows Server and PowerShell commands to install and configure IIS, with no mention of Linux alternatives (such as Apache or Nginx) or Linux-based configuration steps. Windows tooling (PowerShell, IIS) is used exclusively, and Windows is referenced first and solely in all practical examples. There are no Linux-specific instructions, nor is there guidance for deploying non-Windows web servers.
Recommendations
  • Add Linux-based examples for backend pool configuration, such as using Ubuntu VMs with Apache or Nginx.
  • Provide equivalent Linux shell commands for web server setup (e.g., apt install apache2, echo $HOSTNAME > /var/www/html/index.html).
  • Include screenshots or instructions for configuring Linux VMs in VMware vSphere Client.
  • Explicitly mention that both Windows and Linux VMs are supported as backend pools, and provide parity in documentation for both platforms.
  • Where PowerShell is used, offer Bash or shell script alternatives for Linux users.
GitHub Create Pull Request
Azure Vmware Remove Arc-enabled Azure VMware Solution vSphere resources from Azure ...led-azure-vmware-solution-vsphere-resources-from-azure.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation demonstrates a Windows bias by presenting Windows uninstall instructions before Linux, using Windows-centric tools and UI patterns (Control Panel, Programs and Features), and generally referencing Windows terminology and workflows more prominently. Linux instructions are present but less detailed and appear after Windows steps.
Recommendations
  • Present Linux and Windows instructions in parallel or grouped together, rather than listing Windows first.
  • Provide equivalent Linux UI-based uninstall instructions if available (e.g., for distributions with graphical package managers).
  • Expand Linux examples to cover more distributions and edge cases, such as agent removal verification and folder cleanup.
  • Use neutral terminology and ordering (e.g., 'For Windows, do X. For Linux, do Y.') to avoid implying Windows is the default.
  • Where possible, provide cross-platform CLI instructions (e.g., using azcmagent commands) before platform-specific steps.
GitHub Create Pull Request
Azure Vmware Restore guest files and folders using Cloud Backup for Virtual Machines ...n/articles/azure-vmware/restore-guest-files-folders.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation is heavily biased towards Windows environments. All examples, instructions, and credential requirements are specific to Windows guest OS, with explicit statements that Linux guest OS restore is not supported. Windows tools and patterns (e.g., UNC paths, Administrator account, UAC) are mentioned exclusively, and there are no Linux equivalents or examples provided.
Recommendations
  • Add explicit instructions and examples for restoring files from Linux guest OS, even if only manual restore is supported.
  • Clarify and expand the process for attaching VMDKs to Linux VMs and manually restoring files, including recommended tools (e.g., mounting VMDKs on Linux, using guestmount, etc.).
  • Provide parity in credential requirements and restore workflows for Linux environments where possible.
  • Include troubleshooting steps and considerations for Linux guest OS restores.
  • If Linux restore is not supported, offer guidance on alternative backup/restore strategies for Linux VMs.
GitHub Create Pull Request
Azure Vmware Set up Azure Backup Server for Azure VMware Solution ...ware/set-up-backup-server-for-azure-vmware-solution.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation page exhibits a strong Windows bias. All setup instructions, examples, and referenced tools are exclusively for Windows environments. The VM creation tutorial, disk attachment, and installation steps are all Windows-centric, with no Linux equivalents or parity. Powershell is used for configuration checks, and only Windows VM recovery is discussed in detail. There is no guidance for deploying Azure Backup Server on Linux, nor for backing up or restoring Linux VMs beyond a brief mention of pre/post scripts for application consistency.
Recommendations
  • Provide explicit instructions for deploying Azure Backup Server on Linux VMs, if supported, or clarify its Windows-only support.
  • Include Linux-based examples for VM creation, disk attachment, and storage configuration (e.g., using Azure CLI, Bash, or Linux tools).
  • Offer parity in backup and restore procedures for Linux VMs, including file-level recovery and application-consistent backup steps.
  • Replace or supplement Powershell scripts with Bash or shell equivalents for Linux environments.
  • Clearly state platform limitations and support matrix at the beginning of the documentation.
  • Reference Linux documentation and tools where applicable, such as mounting disks, configuring storage pools, and joining domains.
GitHub Create Pull Request
Azure Vmware Azure Hybrid Benefit for Windows Server, SQL Server, or Linux subscriptions ...ain/articles/azure-vmware/sql-server-hybrid-benefit.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
Although the page title and description mention Linux subscriptions, the content and examples focus almost exclusively on Windows Server and SQL Server. All detailed scenarios, migration guides, and configuration steps are centered on Microsoft SQL Server and Windows Server technologies, with no Linux-specific examples, migration paths, or tooling mentioned. Windows tools and patterns (e.g., Windows Server Failover Cluster) are referenced, while Linux equivalents are absent.
Recommendations
  • Add concrete examples and migration guides for Linux workloads, such as migrating Linux-based databases or applications to Azure VMware Solution.
  • Include Linux-specific licensing and Azure Hybrid Benefit scenarios, detailing how Linux subscriptions are applied and managed.
  • Provide parity in tooling and configuration instructions, such as mentioning Linux clustering solutions (e.g., Pacemaker, Corosync) and how they can be configured on Azure VMware Solution.
  • Ensure that Linux is not only mentioned in the title and description but also integrated throughout the documentation with equal depth and clarity as Windows technologies.
GitHub Create Pull Request
Azure Vmware Use VMware HCX Run Commands ...lob/main/articles/azure-vmware/use-hcx-run-commands.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation exclusively references PowerShell cmdlets and Windows-centric tools for managing VMware HCX in Azure VMware Solution. All examples, command syntax, and operational steps are based on PowerShell and the Azure portal, with no mention of Linux shell equivalents, cross-platform CLI options, or alternative workflows for non-Windows environments. This creates a strong Windows bias and may hinder Linux users from fully utilizing the documented features.
Recommendations
  • Provide equivalent command examples using Linux shell (bash) or cross-platform CLI tools where possible.
  • Clarify whether the Run Commands can be executed via Azure CLI, REST API, or other non-Windows interfaces, and provide usage examples.
  • Explicitly state platform requirements or limitations for each command, including whether PowerShell is mandatory.
  • Add documentation sections or notes for Linux/macOS users, including setup instructions and troubleshooting tips.
  • Ensure parity in tool references and workflows, mentioning Linux alternatives alongside Windows tools.
GitHub Create Pull Request
Backup Azure Backup - Archive tier overview ...docs/blob/main/articles/backup/archive-tier-support.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by listing PowerShell as a supported client before CLI, referencing Azure Virtual Machines (which are typically Windows-centric) as the primary workload, and omitting explicit Linux or Bash examples. The screenshots and walkthroughs focus on Azure VM backup scenarios, which are often associated with Windows environments, and do not mention Linux-specific backup scenarios or tools. There is no mention of Linux-based recovery point management, nor are there examples using Bash or Linux-native tooling.
Recommendations
  • Add explicit Linux/Bash CLI examples for managing Archive tier operations, alongside PowerShell examples.
  • Clarify that Azure Virtual Machines can run both Windows and Linux, and provide examples/scenarios for both OS types.
  • Include screenshots or walkthroughs for Linux VM backup and recovery point management.
  • List CLI before PowerShell in supported clients, or present them together to avoid order bias.
  • Reference Linux-native tools or commands where applicable, and ensure parity in documentation coverage for Linux workloads.
GitHub Create Pull Request
Azure Vmware Tutorial - Access an Azure VMware Solution private cloud ...articles/azure-vmware/tutorial-access-private-cloud.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation exclusively describes creating and using a Windows VM as the jump box to access Azure VMware Solution resources. All instructions, screenshots, and references are for Windows, with no mention of Linux alternatives or parity. There are no Linux VM examples, nor guidance for connecting from Linux environments.
Recommendations
  • Add instructions and screenshots for creating a Linux VM as a jump box, including recommended distributions (e.g., Ubuntu, CentOS).
  • Provide steps for connecting to vCenter Server and NSX Manager from a Linux VM, including browser usage and credential management.
  • Include links to Linux-specific Azure documentation for VM creation and remote access.
  • Mention that both Windows and Linux VMs can be used as jump boxes, and discuss any differences or considerations.
  • Ensure parity in examples and guidance for both platforms throughout the tutorial.
GitHub Create Pull Request
Azure Vmware Using Run Command in Azure VMware Solution ...s/blob/main/articles/azure-vmware/using-run-command.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing PowerShell cmdlets as the mechanism for Run Command operations, with no mention of Linux shell equivalents or cross-platform alternatives. The examples and terminology are focused on Windows tooling, and there are no examples or guidance for users who may prefer or require Linux-based workflows.
Recommendations
  • Provide equivalent Linux/bash examples for Run Command usage, or clarify if the feature is Windows-only.
  • Mention whether Run Command supports cross-platform scripting (e.g., Bash, Python) and document any limitations.
  • Include references to Linux tools or workflows where applicable, or explicitly state platform requirements.
  • Add a section comparing Windows and Linux support for Run Command, including any differences in available operations or syntax.
GitHub Create Pull Request
Azure Web Pubsub Add a custom domain .../main/articles/azure-web-pubsub/howto-custom-domain.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias in several ways. PowerShell/Windows examples are presented before Bash/Linux equivalents, with the PowerShell tab listed first in the 'Verify your custom domain' section. The PowerShell example uses 'curl.exe' and the 'PS C:\>' prompt, both of which are Windows-specific tools and conventions. Throughout the document, there is a lack of explicit Linux or cross-platform guidance, and the Azure portal screenshots and instructions do not mention platform-specific alternatives or considerations.
Recommendations
  • Present Bash/Linux examples before or alongside PowerShell/Windows examples, or randomize tab order to avoid implicit prioritization.
  • Use platform-neutral tools and prompts in examples (e.g., generic 'curl' usage, avoid 'PS C:\>' prompt).
  • Explicitly mention that all steps and portal instructions apply equally to Linux, macOS, and Windows, or provide notes where there are differences.
  • Include CLI examples using Azure CLI (az) for certificate and managed identity operations, which are cross-platform.
  • Add guidance or screenshots for Linux/macOS users where relevant, especially for command-line operations.
GitHub Create Pull Request
Azure Web Pubsub Move an Azure Web PubSub resource to another region | Microsoft Docs ...articles/azure-web-pubsub/howto-move-across-regions.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation provides detailed instructions for moving an Azure Web PubSub resource using the Azure Portal and Azure PowerShell, with all command-line examples exclusively using PowerShell. The use of 'notepad' for editing files and the absence of Azure CLI or bash examples further indicate a Windows-centric approach. No Linux or cross-platform command-line alternatives are mentioned, and PowerShell is presented as the only scripting option.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell commands, including exporting templates, editing files, creating resource groups, and deploying resources.
  • Replace or supplement 'notepad' with cross-platform editors such as 'vim', 'nano', or 'code' (Visual Studio Code), or simply refer to 'your preferred text editor'.
  • Explicitly mention that all steps can be performed on Linux, macOS, or Windows, and provide guidance for non-Windows environments.
  • Reorder or parallelize sections so that Azure CLI and PowerShell instructions are presented together, rather than PowerShell being the only command-line option.
  • Include notes or links to documentation for installing and using Azure CLI and PowerShell on Linux/macOS.
GitHub Create Pull Request
Azure Web Pubsub Quickstart - Publish messages using Azure Web PubSub service SDK ...b/main/articles/azure-web-pubsub/quickstart-use-sdk.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides both Bash and Azure PowerShell examples for all CLI steps, but PowerShell is given equal prominence to Bash throughout, and is explicitly listed as a prerequisite alongside Bash. There is a slight Windows bias in the repeated mention of PowerShell, the use of PowerShell variable syntax, and the assumption that users may be using PowerShell locally. The prerequisites mention 'a Bash and PowerShell command shell' but do not mention Linux shells or environments specifically. There are no explicit Linux-only examples, and Windows tools (PowerShell) are always presented as an equal option, sometimes before Bash. There is also an assumption that VS Code is the editor, which is cross-platform but often associated with Windows.
Recommendations
  • Clarify that Bash examples work on Linux/macOS and Windows (via WSL or Git Bash), and that PowerShell is primarily for Windows users.
  • Add explicit references to Linux/macOS environments in the prerequisites, e.g., 'Linux/macOS terminal' or 'Bash shell on Linux/macOS'.
  • Consider listing Bash examples before PowerShell, or noting that Bash is the default on Linux/macOS.
  • Where PowerShell is mentioned, add a note that it is most relevant for Windows users.
  • Provide guidance for Linux users on installing prerequisites (e.g., Python, Node.js, Java) using native package managers.
  • Ensure that all steps and code samples are tested and confirmed to work on Linux/macOS as well as Windows.
GitHub Create Pull Request
Azure Web Pubsub Tutorial - Publish and subscribe messages using WebSocket API and Azure Web PubSub service SDK ...articles/azure-web-pubsub/tutorial-pub-sub-messages.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation page demonstrates a mild Windows bias. Windows command shell usage is mentioned before Bash, and Windows-specific instructions (such as using 'set' instead of 'export') are called out in multiple places. The Java section uses Windows-style 'cmd' for directory creation, and there is a general tendency to mention Windows tools and patterns before their Linux equivalents. However, most code and CLI examples are cross-platform and use Bash syntax, and Linux is not excluded from any steps.
Recommendations
  • Present Bash/Linux instructions before or alongside Windows instructions, rather than after.
  • Use neutral language when referring to command shells (e.g., 'In Bash, use export; in Windows cmd.exe, use set').
  • Include explicit Linux/MacOS instructions for activating Python virtual environments (e.g., 'source env/bin/activate' vs 'env\Scripts\activate' for Windows).
  • Avoid using Windows-style directory creation ('cmd') in Java sections; use Bash syntax or clarify both.
  • Add a note at the beginning clarifying that all steps are cross-platform unless otherwise specified.
  • Where possible, provide PowerShell examples alongside Bash, or clarify that Azure CLI commands work in both environments.
GitHub Create Pull Request
Backup Back up a SharePoint farm to Azure with MABS ...articles/backup/backup-azure-backup-sharepoint-mabs.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation is heavily oriented toward Windows environments, with all examples, tools, and procedures referencing Windows-specific components such as CMD commands, Registry Editor, Windows file paths, and Windows services. There are no Linux equivalents or cross-platform instructions, and all administrative tasks assume a Windows OS context. The use of tools like ConfigureSharePoint.exe, references to NT AUTHORITY\SYSTEM, and registry modifications further reinforce the Windows bias. No Linux or PowerShell Core examples are provided, nor is there mention of how (or if) MABS can be used in non-Windows environments.
Recommendations
  • Explicitly state platform requirements and limitations at the start of the documentation, including whether Linux is supported or not.
  • If MABS is Windows-only, provide guidance or links for Linux-based alternatives for SharePoint backup to Azure.
  • Where possible, offer PowerShell Core or cross-platform command examples, or clarify that only Windows PowerShell/CMD is supported.
  • Include a comparison table or section outlining differences in procedure or support between Windows and Linux environments.
  • If any part of the workflow can be performed from a Linux machine (e.g., Azure CLI for monitoring or notification setup), provide those examples.
  • Clarify whether SharePoint on Linux (if supported in future) or hybrid environments can be protected, and document any limitations.
GitHub Create Pull Request
Backup Back up SQL Server to Azure as a DPM workload ...s/blob/main/articles/backup/backup-azure-backup-sql.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation is heavily focused on Windows environments, specifically using Data Protection Manager (DPM), which is a Windows-only tool. All examples, screenshots, and instructions assume the use of Windows Server, Windows-based SQL Server, and DPM management consoles. There are no references to Linux-based SQL Server deployments, nor are there any examples or guidance for backing up SQL Server on Linux. The only automation reference is to PowerShell, which is Windows-centric.
Recommendations
  • Add explicit guidance and examples for backing up SQL Server running on Linux, including supported backup tools and workflows.
  • Mention and provide parity for Linux-native backup tools and automation options (such as Bash scripts, cron jobs, or Azure CLI).
  • Clarify whether Azure Backup supports SQL Server on Linux and, if so, document any differences or limitations.
  • Include screenshots and walkthroughs for Linux environments where applicable.
  • Reference cross-platform automation options (e.g., Azure CLI, REST API) alongside PowerShell.
  • If DPM is not supported on Linux, suggest alternative Azure-native backup solutions for SQL Server on Linux.
GitHub Create Pull Request
Backup Overview of Azure Database for PostgreSQL Backup ...es/backup/backup-azure-database-postgresql-overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates a Windows bias by exclusively recommending and illustrating the use of pgAdmin—a GUI tool most commonly used on Windows—for database management tasks. There are no examples or instructions for Linux-native tools (such as psql CLI), nor is there mention of Linux workflows or command-line alternatives. The screenshots and step-by-step instructions focus on GUI interactions typical of Windows environments, and there is no parity for Linux users who may prefer or require CLI-based management.
Recommendations
  • Add examples and instructions for using psql (the PostgreSQL command-line client) for backup, restore, and user management tasks.
  • Include Linux-specific workflows, such as connecting via terminal, managing firewall rules, and running SQL commands from the shell.
  • Provide screenshots or text-based walkthroughs for Linux environments (e.g., Ubuntu, CentOS) alongside the existing pgAdmin GUI instructions.
  • Explicitly mention cross-platform compatibility and recommend tools available on both Windows and Linux, or clarify when a tool is Windows-specific.
  • Ensure REST API and CLI instructions are highlighted and not only GUI-based, to support automation and Linux-native usage.
GitHub Create Pull Request
Backup Prepare the DPM server to back up workloads .../main/articles/backup/backup-azure-dpm-introduction.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation is heavily oriented toward Windows environments, specifically System Center Data Protection Manager (DPM), which is a Windows-only product. All examples, prerequisites, and instructions reference Windows tools (PowerShell, .NET Framework, MARSAgentInstaller.exe), and there are no Linux equivalents or cross-platform alternatives mentioned. The documentation assumes the use of Windows servers and omits guidance for Linux-based backup scenarios, even in sections where general backup agent installation or vault credential usage is discussed.
Recommendations
  • Explicitly state that DPM is a Windows-only product at the beginning of the documentation.
  • Provide links or references to Azure Backup documentation for Linux workloads, such as using MARS agent alternatives or Azure Backup for Linux VMs.
  • Where backup agent installation is discussed, include a note or section on how Linux servers can be backed up to Azure (if supported), or clarify that the instructions are not applicable to Linux.
  • Add parity in troubleshooting and prerequisites sections by mentioning Linux-specific requirements or limitations, if any.
  • In related content, include links to documentation for backing up Linux servers to Azure.
GitHub Create Pull Request
Backup Troubleshoot the Azure Backup agent ...main/articles/backup/backup-azure-mars-troubleshoot.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation page for troubleshooting the Azure Backup (MARS) agent exhibits strong Windows bias. All examples, troubleshooting steps, and tool references are exclusively for Windows environments. There are no Linux equivalents or mentions, and Windows-specific tools (MMC console, Internet Explorer, Task Scheduler, Registry Editor, Device Manager, vssadmin, PowerShell, etc.) are used throughout. The page assumes the user is operating on Windows, with no guidance for Linux users or cross-platform parity.
Recommendations
  • Add explicit statements clarifying platform support (e.g., whether MARS agent is Windows-only, and alternatives for Linux).
  • If Linux is supported, provide troubleshooting steps and examples for Linux environments (e.g., using systemd, cron, Linux file paths, bash commands).
  • Mention Linux equivalents for Windows tools (e.g., use curl/wget for downloads, systemctl for service management, etc.).
  • Include PowerShell alternatives for Linux (such as Bash scripts or Azure CLI commands).
  • Provide parity in error codes and troubleshooting for Linux-based backup agents, if available.
  • If MARS agent is not supported on Linux, clearly state this and link to documentation for Linux backup solutions (such as Azure Backup for Linux VMs or Azure CLI-based backup).
GitHub Create Pull Request
Backup Troubleshoot Azure Backup Server ...main/articles/backup/backup-azure-mabs-troubleshoot.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation for Azure Backup Server troubleshooting is heavily oriented towards Windows environments. All examples, paths, registry keys, and troubleshooting steps reference Windows-specific tools, locations, and patterns (e.g., C:\Program Files, Windows registry, Windows services, Windows Server Backup, DPM, MARS agent, and commands like 'net start'). There is no mention of Linux equivalents, nor are there any examples or instructions for Linux-based systems. The documentation assumes the user is operating in a Windows ecosystem, with no guidance for Linux users.
Recommendations
  • Add troubleshooting steps and examples for Linux-based servers where Azure Backup Server or agents may be supported.
  • Include Linux file paths, service management commands (e.g., systemctl), and configuration file locations alongside Windows examples.
  • Provide guidance on configuring antivirus exclusions and backup settings for common Linux distributions.
  • Mention Linux equivalents for registry settings (e.g., configuration files or environment variables).
  • Clarify platform support at the beginning of the documentation and, if only Windows is supported, explicitly state this to avoid confusion.
  • If Linux is not supported, add a note to inform users and direct them to relevant Linux backup solutions.
GitHub Create Pull Request
Backup Private Endpoints Overview: Version 2 Experience ...icles/backup/backup-azure-private-endpoints-concept.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by primarily referencing Windows-centric backup tools (MARS agent, DPM, MABS) and scenarios. There are no explicit Linux backup agent examples, nor are Linux-specific patterns or tools mentioned. The focus is on workloads like SQL Server and SAP HANA in Azure VMs, but only Windows backup agents (MARS, DPM, MABS) are discussed in detail. No Linux command-line or agent instructions are provided, and the documentation does not clarify how private endpoints interact with Linux-based backup solutions.
Recommendations
  • Add explicit examples and instructions for configuring private endpoints with Linux-based backup agents (such as Azure CLI, azbackup, or third-party Linux backup tools).
  • Mention Linux VM scenarios and clarify how private endpoint connectivity works for Linux workloads, including any differences in DNS or agent setup.
  • Include parity in supported backup agents by listing Linux-compatible solutions and their requirements for private endpoint usage.
  • Provide sample configurations or troubleshooting steps for Linux environments, such as modifying /etc/hosts, using systemd-resolved, or integrating with custom DNS on Linux.
  • Ensure that references to tools and agents are balanced between Windows and Linux, and avoid assuming Windows-only environments.
GitHub Create Pull Request
Backup Troubleshoot System Center Data Protection Manager .../articles/backup/backup-azure-scdpm-troubleshooting.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation is heavily focused on troubleshooting System Center Data Protection Manager (DPM), which is a Windows-only product. All examples, commands (e.g., net stop/start), and troubleshooting steps reference Windows tools, services, and concepts (such as NT AUTHORITY\SYSTEM and USN journal) without mention of Linux equivalents or cross-platform scenarios. There are no Linux-specific troubleshooting steps or examples, and Windows terminology is used exclusively and presented first.
Recommendations
  • If DPM or Azure Backup Server supports Linux workloads or agents, include troubleshooting steps and examples for Linux environments (e.g., service management via systemctl, Linux agent installation, file system considerations).
  • Explicitly state platform limitations at the top of the documentation if the product is Windows-only, to avoid confusion for Linux users.
  • Where possible, provide parity in error resolution steps for Linux-based backup agents or workloads, including relevant commands and log locations.
  • Mention and link to documentation for Linux backup solutions if DPM does not support Linux, to guide users to appropriate resources.
GitHub Create Pull Request
Backup Back up SQL Server databases to Azure ...blob/main/articles/backup/backup-azure-sql-database.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation is heavily biased towards Windows environments. All instructions, examples, and tooling references (such as SSMS, NT SERVICE accounts, Windows authentication, PowerShell scripts, and Windows file paths) are specific to Windows. There is no mention of Linux-based SQL Server VMs, nor any guidance for Linux authentication, file permissions, or command-line equivalents. The backup extension is named 'AzureBackupWindowsWorkload', and all operational steps assume a Windows OS, leaving Linux users without clear instructions.
Recommendations
  • Add explicit guidance for Linux-based SQL Server VMs, including any differences in extension installation, service accounts, and authentication.
  • Provide Linux-specific examples for setting SQL Server permissions (e.g., using sqlcmd or other CLI tools on Linux).
  • Include file path and permission instructions for Linux (e.g., using chmod/chown instead of Windows Security tab).
  • Offer Bash or shell script equivalents for PowerShell automation steps.
  • Clarify whether the AzureBackupWindowsWorkload extension is supported or available for Linux VMs, and if not, document alternatives.
  • Document any limitations or differences for SQL Server on Linux in Azure VMs, and link to relevant Linux documentation.
GitHub Create Pull Request
Backup Back Up and Restore Encrypted Azure VMs ...ob/main/articles/backup/backup-azure-vms-encryption.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides some parity between Windows and Linux in conceptual coverage, but exhibits bias in several areas. PowerShell is used as the only example for identifying a VM's associated key vault, with no equivalent Linux or Azure CLI example. Windows tooling (PowerShell) is mentioned before Linux alternatives, and there are no explicit Linux command-line examples. The documentation refers to Windows and Linux VMs in general, but practical steps and code samples favor Windows/PowerShell, leaving Linux users without direct guidance.
Recommendations
  • Add Azure CLI and/or Bash examples alongside PowerShell commands for key vault and VM operations.
  • When referencing command-line operations, present both Windows (PowerShell) and Linux (CLI/Bash) examples, or use Azure CLI as the default cross-platform tool.
  • Explicitly mention Linux-specific considerations or steps where relevant, especially in sections that currently only show Windows tooling.
  • Ensure screenshots and instructions do not assume a Windows-centric workflow (e.g., referencing PowerShell as the default).
  • Review related links and troubleshooting guides to ensure Linux scenarios are covered with equal depth.
GitHub Create Pull Request
Backup About agentless multi-disk crash-consistent backup for Azure Virtual Machines by using Azure Backup ...ure-vms-agentless-multi-disk-crash-consistent-overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows-first bias by mentioning Windows-specific backup mechanisms (VSS) before Linux equivalents (fsfreeze), and by linking only to Windows VM Agent and snapshot extension documentation. There are no Linux-specific examples, links, or tools referenced, and Linux backup patterns (such as pre/post scripts) are only mentioned in passing as a reason not to use crash-consistent backups.
Recommendations
  • Provide equal prominence to Linux backup mechanisms (e.g., link to documentation for fsfreeze and Linux VM Agent/extensions).
  • Include Linux-specific examples or scenarios, such as how crash-consistent backups interact with common Linux workloads.
  • Add links to Linux documentation for VM Agent and snapshot extensions, similar to the Windows links.
  • Clarify the behavior for Linux VMs in agentless backup scenarios, including any limitations or best practices.
  • List both Windows and Linux tools/patterns together when describing backup consistency mechanisms.
GitHub Create Pull Request
Backup Script Sample - Create a new or modify the current system state backup policy ...icles/backup/scripts/set-system-state-backup-policy.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation exclusively provides a PowerShell script for managing system state backup policies with the MARS agent, which is a Windows-only tool. There are no examples, instructions, or mentions of Linux or cross-platform alternatives. All tooling and scripting patterns are Windows-centric, and the guidance assumes a Windows environment from the outset.
Recommendations
  • Add equivalent examples or guidance for Linux systems, if supported, using Bash, Python, or other relevant scripting languages.
  • Clearly state platform limitations (e.g., if MARS agent is Windows-only) and provide links or references to Linux backup solutions if applicable.
  • Include a section comparing Windows and Linux backup policy management, highlighting differences and cross-platform considerations.
  • If Linux is not supported, explicitly mention this in the prerequisites or introduction to set expectations for cross-platform users.
GitHub Create Pull Request
Backup Soft delete for virtual machines ...b/main/articles/backup/soft-delete-virtual-machines.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell examples and cmdlets for managing soft delete operations, referencing Windows-centric tools and patterns, and omitting equivalent Linux CLI (Azure CLI, Bash) examples. The PowerShell workflow is described in detail, while no Linux-native or cross-platform command-line instructions are given. The ordering also places PowerShell before REST API, and there is no mention of Azure CLI or Bash scripting, which are commonly used on Linux and macOS.
Recommendations
  • Add equivalent Azure CLI examples for all operations (delete backup, undelete, resume backup) to ensure Linux and cross-platform parity.
  • Include Bash script snippets where appropriate, demonstrating how to interact with Azure Backup using REST API or Azure CLI.
  • Explicitly mention that all operations can be performed from Linux/macOS environments using Azure CLI or REST API.
  • Reorder sections so that cross-platform tools (Azure CLI, REST API) are presented before or alongside PowerShell to avoid implicit prioritization of Windows tools.
  • Add a note clarifying tool availability and platform compatibility for each method.
GitHub Create Pull Request
Backup Upgrade the Microsoft Azure Recovery Services (MARS) agent for Azure Backup ...e-docs/blob/main/articles/backup/upgrade-mars-agent.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation exclusively describes upgrading the MARS agent on Windows environments, referencing Windows-specific tools (Remote Desktop, DPM Console, agent installer wizards) and omitting any mention of Linux systems, commands, or upgrade procedures. All examples, screenshots, and next steps are Windows-centric, with no Linux parity or cross-platform guidance.
Recommendations
  • Clarify in the introduction whether the MARS agent is Windows-only, or explicitly state platform limitations.
  • If Linux support exists, add equivalent Linux upgrade instructions, including command-line examples (e.g., Bash, SSH, package managers).
  • Include Linux-specific troubleshooting steps, firewall configuration, and agent version discovery methods.
  • Provide parity in screenshots and step-by-step guides for Linux environments.
  • If the agent is not available for Linux, add a note explaining this to avoid confusion for cross-platform administrators.
GitHub Create Pull Request
Bastion Configure Bastion for native client connections ...azure-docs/blob/main/articles/bastion/native-client.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_heavy ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates a Windows bias by listing Windows native client connection instructions and features before Linux equivalents, providing more detailed examples and links for Windows, and omitting explicit Linux command-line examples in the main text. The connection table and 'Next steps' section prioritize Windows, and references to Windows tools (RDP) are more prominent than Linux tools (SSH).
Recommendations
  • Present Linux and Windows instructions with equal prominence, alternating order or grouping by scenario rather than OS.
  • Include explicit Linux command-line examples and screenshots in the main documentation, not just in linked pages.
  • Add parity in feature explanations, such as file transfer and authentication, for both Windows and Linux clients.
  • Reference common Linux tools (e.g., OpenSSH, Remmina) alongside Windows tools (RDP), and provide usage examples.
  • Ensure 'Next steps' links for Linux are as detailed and visible as those for Windows.
GitHub Create Pull Request
Bastion Quickstart: Deploy Azure Bastion automatically ...s/blob/main/articles/bastion/quickstart-host-portal.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools and patterns before their Linux equivalents. For example, keyboard shortcuts for remote access are described in detail for Windows VMs and clients, with only a brief mention of Mac clients connecting to Windows VMs. There are no equivalent examples or guidance for connecting to Linux VMs from Linux or Mac clients. Additionally, the inbound port requirements list Windows (3389) before Linux (22), and the VM creation quickstart links mention Windows before Linux.
Recommendations
  • Provide detailed examples and guidance for connecting to Linux VMs from Linux and Mac clients, including keyboard shortcuts and remote access patterns.
  • Ensure parity in documentation order by listing Linux and Windows examples side-by-side or alternating which is mentioned first.
  • Include Linux-specific remote access tips (e.g., SSH client usage, clipboard integration, keyboard shortcuts) where Windows-specific guidance is given.
  • Explicitly mention cross-platform considerations and tools for both Windows and Linux users throughout the documentation.
GitHub Create Pull Request
Batch Deploy application packages to compute nodes ...blob/main/articles/batch/batch-application-packages.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page exhibits Windows bias in several ways: all code examples are in C# and use Windows-centric constructs (e.g., 'cmd /c', Windows environment variable formats, Windows image references), with no Linux shell or cross-platform code samples. Windows node configuration and usage patterns are described first and in detail, while Linux equivalents are only briefly mentioned, often as afterthoughts. There is no example of deploying or running application packages on Linux nodes using Linux command lines or shell scripts. Windows-specific tools and patterns (e.g., 'cmd /c', Windows image references) are used exclusively in code samples.
Recommendations
  • Provide equivalent Linux examples for deploying and running application packages, including shell script command lines (e.g., 'bash -c ...') and Linux image references.
  • Include cross-platform code samples or highlight differences in API usage between Windows and Linux nodes.
  • Document Linux-specific considerations (such as file paths, permissions, and environment variable usage) alongside Windows instructions.
  • Avoid using Windows tools and patterns exclusively in examples; show parity by alternating or combining Windows and Linux scenarios.
  • Add a section or table summarizing differences and best practices for both Windows and Linux compute nodes.
GitHub Create Pull Request
Batch Copy applications and data to pool nodes ...ain/articles/batch/batch-applications-to-pool-nodes.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page exhibits Windows bias by referencing Windows-specific installation formats (.exe, .msi) and omitting Linux equivalents (such as .sh scripts or .deb/.rpm packages). There are no examples or mentions of Linux tools, patterns, or file formats, and Windows terminology appears first and exclusively in installation scenarios.
Recommendations
  • Include Linux-specific examples, such as installing .sh scripts or .deb/.rpm packages using start tasks.
  • Mention Linux tools and patterns (e.g., using bash scripts, apt/yum/zypper for package installation) alongside Windows examples.
  • Provide parity in documentation by describing both Windows and Linux workflows for copying and installing applications and data.
  • Avoid referencing only Windows file formats (.exe, .msi) and instead use generic terms or include Linux equivalents.
  • Add explicit guidance for Linux users, such as how to set up permissions, run shell commands, or handle resource files on Linux nodes.
GitHub Create Pull Request
Batch Azure Quickstart - Create a Batch account - Azure Resource Manager template ...docs/blob/main/articles/batch/quick-create-template.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias by prioritizing the Azure portal (which is most commonly used on Windows) and referencing Azure PowerShell as a deployment method before mentioning Azure CLI or REST API. There are no explicit Linux or cross-platform command-line examples, and the links for further deployment methods point to PowerShell documentation first. No Linux-specific instructions or screenshots are provided.
Recommendations
  • Add explicit Azure CLI examples for deploying the ARM template, including Linux/macOS terminal instructions.
  • Reference Azure CLI before or alongside Azure PowerShell when listing deployment options.
  • Include screenshots or instructions for using the Azure portal on Linux/macOS browsers, if relevant.
  • Ensure links to deployment methods include both PowerShell and CLI documentation equally.
  • Mention that all steps can be performed on Linux, macOS, and Windows, and clarify any platform-specific differences.
GitHub Create Pull Request
Cloud Services Extended Support Available sizes for Azure Cloud Services (extended support) ...les/cloud-services-extended-support/available-sizes.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell examples for retrieving VM sizes, referencing Windows-centric tools (PowerShell, Visual Studio), and omitting equivalent Linux/CLI examples. The deployment options list PowerShell and Visual Studio before mentioning templates, with no explicit mention of Azure CLI or Bash commands. This may disadvantage users working on Linux or cross-platform environments.
Recommendations
  • Add Azure CLI examples for listing available VM sizes, alongside the PowerShell example.
  • Explicitly mention Linux-compatible tools and workflows (e.g., Bash, Azure CLI) in deployment steps.
  • Balance the order of tool references so that cross-platform or Linux-native options (Azure CLI, ARM templates) are listed before or alongside Windows-specific tools.
  • Include notes or links for Linux users on how to perform equivalent tasks.
  • Consider adding sample commands for both Windows and Linux environments wherever code snippets or instructions are provided.
GitHub Create Pull Request
Cloud Services Extended Support Guest OS family 1 retirement notice | Microsoft Docs ...-support/cloud-services-guestos-family-1-retirement.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page exclusively references Windows Server-based Guest OS families and provides only Azure PowerShell scripts for determining affected services. There are no examples or guidance for Linux-based cloud services, nor are cross-platform tools or CLI alternatives mentioned. Windows terminology and migration paths are presented without Linux parity.
Recommendations
  • Include examples for identifying affected services using Azure CLI or REST API, which are cross-platform and usable on Linux and macOS.
  • Clarify whether Linux-based cloud services are impacted, and if not, explicitly state this to avoid confusion.
  • Provide migration guidance for Linux-based workloads if applicable, or reference relevant documentation for Linux cloud service management.
  • Balance the presentation by mentioning both Windows and Linux Guest OS families (if supported), and provide equivalent instructions for each.
  • Add notes or links to resources for users managing cloud services from non-Windows environments.
GitHub Create Pull Request
Cloud Services Extended Support Azure Cloud Services (extended support) NetworkConfiguration Schema | Microsoft Docs ...-extended-support/schema-cscfg-networkconfiguration.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits mild Windows bias. The only tool mentioned for deployment is PowerShell, which is primarily a Windows-centric tool (though it is available on Linux, its usage is much less common in Linux environments). There are no examples or references to Linux-native tools (such as Azure CLI, Bash, or ARM templates) for managing or deploying network configuration. No Linux-specific patterns or examples are provided, and the documentation does not mention or demonstrate parity for Linux users.
Recommendations
  • Add examples using Azure CLI commands for deployment and configuration, alongside PowerShell examples.
  • Explicitly mention that PowerShell is available on Linux, but also provide Bash/CLI equivalents for common tasks.
  • Include references to ARM/Bicep templates for infrastructure-as-code scenarios, which are platform-neutral.
  • Where deployment tooling is discussed, present Linux and Windows options side-by-side, or clarify cross-platform support.
  • Review and update documentation to ensure Linux users are not required to infer steps from Windows-centric instructions.
GitHub Create Pull Request
Cloud Shell Azure Cloud Shell features .../azure-docs/blob/main/articles/cloud-shell/features.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits several signs of Windows bias. PowerShell is frequently mentioned and given special features (such as the Azure drive), with detailed instructions and examples focused on PowerShell before Bash. Many Microsoft-centric tools (e.g., Office 365 CLI, Exchange Online PowerShell, Microsoft Graph PowerShell, SqlServer PowerShell modules) are highlighted, and several sections list PowerShell modules and features without Linux/Bash equivalents or alternatives. The Azure drive feature is described only for PowerShell, with no mention of similar navigation for Bash. Some commands are listed as 'Bash or PowerShell', but PowerShell-specific commands are often given first or exclusively. There are few, if any, Bash-specific examples, and Linux tools are grouped in a short list without further explanation.
Recommendations
  • Provide Bash-specific examples and instructions alongside PowerShell, especially for features like Azure drive navigation and resource management.
  • List Linux/Bash tools and equivalents with the same level of detail as PowerShell modules, including links to documentation for Bash-based Azure management.
  • Ensure that introductory and feature sections mention Bash and Linux tools first or equally, not just as secondary options.
  • Highlight open source and cross-platform tools more prominently, and clarify their usage in both Bash and PowerShell environments.
  • Add examples of common workflows using Bash, such as managing Azure resources with Azure CLI, scripting with Bash, and using Linux-native utilities.
  • Where features are PowerShell-only (e.g., Azure drive), explicitly state this and suggest Linux/Bash alternatives or workarounds.
GitHub Create Pull Request
Cloud Shell What is Azure Cloud Shell? .../azure-docs/blob/main/articles/cloud-shell/overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page for Azure Cloud Shell mentions both Bash and PowerShell, but consistently lists PowerShell before Bash and provides links to Azure PowerShell documentation before Azure CLI (which is more commonly used on Linux). There are no explicit Linux-specific examples, tools, or usage patterns highlighted. The integrated editor is described only in terms of Azure CLI and PowerShell, with no mention of Linux-native editors or workflows. The page does not provide parity in examples or tool references for Linux users.
Recommendations
  • Alternate the order of Bash and PowerShell mentions, or list Bash first in some sections to avoid implicit prioritization of Windows/PowerShell.
  • Provide explicit examples or links for Linux workflows, such as using Bash scripts, Linux command-line tools, or integration with Linux-native editors (e.g., Vim, Nano).
  • Include references to Linux documentation or guides for using Cloud Shell with Bash.
  • Highlight the availability of Linux command-line tools in the preinstalled tools list and provide examples of their usage.
  • Ensure that both Azure CLI and PowerShell are given equal prominence in links and examples.
GitHub Create Pull Request
Cloud Shell Persist files in Azure Cloud Shell .../main/articles/cloud-shell/persisting-shell-storage.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a bias toward Windows and PowerShell environments. All command-line examples for managing Cloud Shell storage use PowerShell cmdlets (e.g., Get-CloudDrive, Dismount-CloudDrive) with no equivalent Bash or Linux shell commands provided. The 'Use PowerShell commands' section is prominent, and no Linux/Unix-specific tools or patterns are mentioned. This may disadvantage users who prefer or use the Bash environment in Azure Cloud Shell.
Recommendations
  • Add equivalent Bash/Linux shell commands for all PowerShell examples, such as using Azure CLI (az) commands to manage clouddrive and storage.
  • Include a 'Use Bash commands' section alongside the PowerShell section, demonstrating parity in functionality.
  • When describing commands or workflows, present both PowerShell and Bash examples, or alternate which is presented first.
  • Reference Linux/Unix patterns and tools where relevant, ensuring that documentation is inclusive for both Windows and Linux users.
GitHub Create Pull Request
Cloud Shell Azure Cloud Shell release notes ...e-docs/blob/main/articles/cloud-shell/release-notes.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page demonstrates a moderate Windows bias. Azure PowerShell and Windows-centric tools are consistently highlighted alongside Azure CLI, with PowerShell versions and features mentioned in every release note. Windows-specific keyboard shortcuts are referenced before Linux equivalents, and some links default to PowerShell tabs. There is limited mention of Linux-specific tools or patterns, and Linux features are generally not emphasized or explained in parity with Windows/PowerShell features.
Recommendations
  • Include Bash and Linux command examples and version updates alongside PowerShell in each release note.
  • When referencing keyboard shortcuts, list Linux shortcuts first or equally with Windows, and clarify differences.
  • Add more details about Linux-specific tools, utilities, and patterns available in Cloud Shell.
  • Ensure documentation links and tabs default to a neutral or Linux shell option, not PowerShell.
  • Explicitly mention updates or changes to Bash, Zsh, or other Linux shells if applicable.
  • Highlight Linux container base image changes and their impact on available tools and workflows.
GitHub Create Pull Request
Communication Services Enable interoperability in your Teams tenant ...s/includes/enable-interoperability-for-teams-tenant.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation exclusively uses PowerShell commands and Windows-centric tools (MicrosoftTeams PowerShell module) for enabling interoperability in Teams. There are no examples or instructions for Linux or macOS users, nor are alternative CLI tools or cross-platform methods mentioned. The instructions assume the use of PowerShell and administrative privileges typical of Windows environments.
Recommendations
  • Provide equivalent instructions for Linux and macOS users, such as using PowerShell Core (pwsh) on those platforms.
  • Clarify whether the MicrosoftTeams PowerShell module is supported on PowerShell Core and how to install it on non-Windows systems.
  • Include examples using Azure CLI or REST API if available, which are cross-platform.
  • Explicitly mention any platform limitations or requirements for the described steps.
  • Add troubleshooting notes for common issues encountered on Linux/macOS (e.g., module installation, authentication prompts).
GitHub Create Pull Request
Communication Services Teams Phone extensibility FAQ .../concepts/interop/tpe/teams-phone-extensibility-faq.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page demonstrates Windows bias primarily by referencing the Teams Admin Center (TAC) portal and PowerShell cmdlets as the methods for configuring emergency calling support, without mentioning equivalent Linux-friendly tools or CLI alternatives. Windows-centric tools are presented as the default or only options for administrative tasks, and there are no examples or guidance for Linux environments or cross-platform command-line usage.
Recommendations
  • Include instructions for configuring Teams Phone extensibility features using cross-platform tools such as Microsoft Graph API, Azure CLI, or REST APIs.
  • Provide Linux-compatible examples for administrative tasks, such as using bash scripts or platform-neutral CLI commands.
  • Explicitly mention whether PowerShell cmdlets can be run on Linux (via PowerShell Core), and provide guidance for Linux users.
  • Add references to platform-agnostic management options and clarify any limitations or requirements for non-Windows environments.
  • Ensure that documentation does not assume the use of Windows-only tools and offers parity for Linux and macOS administrators.
GitHub Create Pull Request
Communication Services Plan user experience for virtual appointments ...oncepts/interop/virtual-visits/plan-user-experience.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing the Teams Admin Center and PowerShell as the primary tools for configuration, without mentioning Linux-compatible alternatives or providing cross-platform examples. The guidance assumes access to Windows-centric administration tools and does not address how Linux users can perform equivalent tasks.
Recommendations
  • Include instructions or examples for configuring Teams tenant using cross-platform tools, such as Microsoft Graph API or web-based portals.
  • Explicitly mention whether Teams Admin Center is accessible via web browser on Linux and provide links or notes for Linux users.
  • Provide parity by listing Linux-compatible methods for managing Teams policies and configurations, such as using REST APIs or CLI tools available on Linux.
  • Avoid referencing PowerShell exclusively; if PowerShell is required, note how it can be installed and used on Linux, or offer alternative approaches.
  • Add examples or notes clarifying how Linux administrators can achieve the same outcomes as those using Windows tools.
GitHub Create Pull Request
Communication Services Microsoft Teams shared line appearance ...pts/interop/teams-user/teams-shared-line-appearance.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates Windows bias by referencing Teams PowerShell and the Microsoft Teams Client as the primary methods for assigning delegates, without mentioning Linux equivalents or alternatives. There are no examples or instructions for Linux users, and the prerequisite steps and tooling are Windows-centric. The note about platform support lists Windows explicitly, but does not clarify Linux support or provide parity information.
Recommendations
  • Include instructions or examples for assigning delegates using cross-platform tools, such as Azure CLI, REST API, or Graph API, if available.
  • Explicitly state whether Linux users can perform the same actions, and provide guidance or workarounds if direct support is missing.
  • Add references to Linux-compatible tools or scripts where possible, and ensure that examples are not exclusively PowerShell-based.
  • Clarify platform support for shared line appearance, including Linux and macOS, in the relevant sections.
  • Consider reordering examples or instructions so that platform-neutral or cross-platform methods are presented before Windows-specific ones.
GitHub Create Pull Request
Communication Services Teams Phone extensibility Troubleshooting ...terop/tpe/teams-phone-extensibility-troubleshooting.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a Windows bias, especially in the troubleshooting steps for Microsoft Entra App permission issues. Only PowerShell commands are provided, with explicit instructions to use PowerShell and install the Microsoft Graph module—both Windows-centric tools. There are no equivalent examples or guidance for Linux or cross-platform environments (e.g., Azure CLI, Bash, or REST API). The troubleshooting workflow assumes access to Windows tools and does not mention alternatives for Linux or macOS users.
Recommendations
  • Provide equivalent troubleshooting steps using Azure CLI, Bash, or REST API for Linux/macOS users.
  • Include cross-platform instructions and examples alongside PowerShell commands.
  • Mention and link to documentation for non-Windows environments where possible.
  • Clarify which steps are Windows-specific and offer alternatives for other operating systems.
  • Consider reordering examples so that cross-platform tools (e.g., Azure CLI) are presented before or alongside PowerShell.
GitHub Create Pull Request
Communication Services Tutorial - Integrate Microsoft Teams breakout rooms ...nication-services/how-tos/calling-sdk/breakoutrooms.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias by referencing Windows-specific tools (e.g., PowerShell for Teams meeting policy management) and linking to Windows-centric documentation before mentioning or providing Linux alternatives. There are no examples or instructions for managing Teams policies or breakout rooms using Linux-native tools, nor is there mention of cross-platform command-line options. The SDK support table lists 'Windows' as a platform but does not clarify parity or provide Linux desktop guidance.
Recommendations
  • Include instructions or references for managing Teams meeting policies using cross-platform tools such as Microsoft Graph API, which can be used on Linux and macOS.
  • Provide explicit Linux/macOS examples for any command-line or scripting steps, especially for administrative tasks.
  • Clarify SDK support for Linux desktop environments and add relevant documentation or links.
  • Avoid linking exclusively to Windows PowerShell documentation; offer alternatives or mention that PowerShell Core is available cross-platform.
  • Add a section or notes on how Linux users can perform equivalent operations, ensuring parity in administrative and developer workflows.
GitHub Create Pull Request
Communication Services Tutorial - Teams Shared Line Appearance ...ices/how-tos/cte-calling-sdk/shared-line-appearance.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing Teams PowerShell and Microsoft Teams Client (both Windows-centric tools) as the primary methods for assigning delegates. No Linux equivalents or cross-platform CLI alternatives are mentioned. The SDK support table lists 'Windows' as a platform but does not mention Linux or macOS, nor does it provide parity in examples or tooling for non-Windows environments.
Recommendations
  • Include instructions or examples for assigning delegates using cross-platform tools, such as Azure CLI or REST APIs, if available.
  • Explicitly mention Linux and macOS support status in the SDK support table, and provide guidance for those platforms.
  • If PowerShell is required, clarify whether PowerShell Core (which runs on Linux/macOS) is supported, and provide installation and usage instructions for those platforms.
  • Offer alternative methods for managing Teams features that do not rely on Windows-only tools.
  • Ensure that all examples and prerequisites are platform-agnostic or provide parallel instructions for Linux/macOS users.
GitHub Create Pull Request
Communication Services include file ...-services/quickstarts/email/includes/send-email-net.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation is heavily focused on .NET and C#, with all code samples and instructions tailored to the .NET SDK. Command-line instructions mention 'cmd, PowerShell, or Bash', but examples use Windows-centric tools and patterns (dotnet CLI, Program.cs, Console.WriteLine) without providing Linux-specific guidance or parity for alternative platforms. There are no Linux-specific examples, troubleshooting steps, or mentions of Linux tools/environments. The documentation assumes a Windows development environment and omits guidance for Linux users beyond generic references to 'your operating system'.
Recommendations
  • Add explicit Linux and macOS instructions for installing .NET Core and running dotnet commands, including package managers (apt, yum, brew).
  • Include sample code and instructions for using the Email SDK in other languages/platforms (e.g., Python, Java, Node.js) to improve cross-platform parity.
  • Provide troubleshooting steps and environment setup guidance for Linux users, including permissions, environment variables, and common issues.
  • Reference Linux-specific terminals and editors (e.g., GNOME Terminal, nano, vim) alongside Windows tools.
  • Clarify that the .NET SDK and Azure Communication Services can be used on Linux and macOS, and link to official cross-platform documentation.
GitHub Create Pull Request
Communication Services include file ...send-email-smtp/includes/send-email-smtp-powershell.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation exclusively provides PowerShell examples and references the Windows-specific Send-MailMessage utility, with no mention of Linux-compatible tools or cross-platform alternatives. There are no examples for Linux users (e.g., using sendmail, mailx, or Python scripts), and Windows tools are presented as the default approach.
Recommendations
  • Add equivalent Linux examples using common tools such as sendmail, mailx, or Python's smtplib.
  • Include cross-platform code samples (e.g., Python, Node.js) that work on both Windows and Linux.
  • Explicitly mention Linux compatibility and provide instructions for Linux users.
  • Present Windows and Linux examples side-by-side, or clarify which platforms each example supports.
  • Avoid assuming PowerShell is available by default; note installation requirements for non-Windows platforms.
GitHub Create Pull Request
Communication Services Send an email using SMTP ...s/quickstarts/email/send-email-smtp/send-email-smtp.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation provides examples for sending email via SMTP using SmtpClient (typically .NET, often associated with Windows) and Windows PowerShell, but does not include equivalent Linux or cross-platform command-line examples (e.g., using 'sendmail', 'mailx', or 'curl'). Windows-specific tools and patterns are emphasized, and Linux alternatives are missing.
Recommendations
  • Add Linux-specific examples, such as using 'sendmail', 'mail', 'mailx', or 'curl' to send emails via SMTP.
  • Include cross-platform scripting examples (e.g., Python, Node.js) that work on both Windows and Linux.
  • Explicitly mention Linux tools and provide step-by-step instructions for common Linux distributions.
  • Balance the order of examples so that Windows and Linux approaches are presented equally or in parallel.
GitHub Create Pull Request
Communication Services Prerequisites ...es/create-custom-managed-domain-resource-powershell.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation exclusively uses PowerShell commands and references the Azure Az PowerShell Module for all resource management tasks, without mentioning or providing examples for Linux-friendly alternatives such as Azure CLI, Bash, or REST API. This creates a strong Windows bias, as PowerShell is primarily associated with Windows environments, and Linux users may not have PowerShell installed or prefer native tools.
Recommendations
  • Add equivalent Azure CLI examples for all resource management operations (e.g., az communication email-domain create, update, list, delete).
  • Mention that PowerShell is available cross-platform, but clarify installation steps for Linux and macOS if PowerShell is required.
  • Provide Bash or shell script examples where appropriate, especially for DNS record updates or verification steps.
  • Reference REST API documentation for users who prefer direct API calls.
  • Reorder sections or add parallel examples so that Linux-friendly tools (Azure CLI, Bash) are presented alongside or before PowerShell examples.
GitHub Create Pull Request
Communication Services Register the Event Grid resource provider ...starts/events/includes/register-provider-powershell.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation exclusively provides PowerShell commands for registering the Event Grid resource provider, which are primarily used on Windows. There are no examples or instructions for Linux/macOS users, such as using Azure CLI or Bash. This creates a Windows-centric experience and may hinder users on other platforms.
Recommendations
  • Add equivalent Azure CLI commands (e.g., 'az provider register --namespace Microsoft.EventGrid') for cross-platform compatibility.
  • Include Bash or shell examples where appropriate.
  • Clearly indicate that PowerShell is one option and provide alternatives for Linux/macOS users.
  • Consider reordering examples so that cross-platform tools (like Azure CLI) are presented before or alongside PowerShell.
GitHub Create Pull Request
Communication Services Send an email using Azure Communication Services ...communication-services/quickstarts/email/send-email.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page presents platform-specific pivots for Azure Portal, Azure CLI, .NET, JavaScript, Java, Python, Logic Apps, and PowerShell. PowerShell (a Windows-centric tool) is given its own pivot, and Windows tools (PowerShell, .NET) are represented prominently. There is no explicit mention of Linux shell examples (e.g., Bash), nor are Linux-specific tools or patterns highlighted. The ordering of pivots places Windows-centric options (PowerShell, .NET) before Linux-native alternatives, and there is no dedicated Linux section or parity for Linux command-line usage beyond Azure CLI.
Recommendations
  • Add explicit Bash or Linux shell examples alongside PowerShell, especially for command-line operations.
  • Ensure parity by providing Linux-specific troubleshooting steps and cleanup instructions.
  • Reorder pivots or provide equal prominence to Linux-native tools (e.g., Bash, Azure CLI) before or alongside Windows-centric options.
  • Mention cross-platform compatibility for SDKs and tools, clarifying usage on Linux systems.
  • Include a dedicated section or pivot for Linux users, highlighting best practices and common patterns.
GitHub Create Pull Request
Communication Services Prerequisites ...vents/includes/create-event-subscription-powershell.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page exclusively uses Azure PowerShell commands and modules for all examples and instructions, with no mention of Linux-native tools, Bash, Azure CLI, or cross-platform alternatives. The prerequisites and all code samples assume PowerShell usage, which is traditionally associated with Windows environments, and there is no guidance for Linux users or parity in tooling.
Recommendations
  • Add equivalent Azure CLI examples for all operations (create, list, update, delete event subscriptions), as Azure CLI is cross-platform and widely used on Linux.
  • Mention installation instructions for Azure CLI and/or Bash scripting alongside PowerShell in the prerequisites.
  • Include notes or sections clarifying that PowerShell Core is available cross-platform, but also provide native Linux/Bash/CLI alternatives.
  • Reorder or parallelize examples so that Linux-friendly tools (Azure CLI, Bash) are presented before or alongside PowerShell.
  • Add troubleshooting or environment-specific notes for Linux users, such as authentication or module installation differences.
GitHub Create Pull Request
Communication Services Prerequisites ...ces/quickstarts/includes/create-resource-powershell.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page exclusively uses PowerShell commands and references Windows-centric tooling (e.g., Azure Az PowerShell Module), with no mention or examples for Linux or cross-platform alternatives such as Azure CLI or Bash. All code samples and instructions are tailored for PowerShell, which is traditionally associated with Windows environments, and there is no guidance for users on Linux or macOS platforms.
Recommendations
  • Add equivalent Azure CLI examples for all resource creation and management tasks.
  • Explicitly mention cross-platform compatibility and provide instructions for Linux/macOS users.
  • Include Bash shell examples where appropriate.
  • Clarify when PowerShell commands can be run on non-Windows platforms (e.g., PowerShell Core on Linux/macOS), or suggest alternatives.
  • Reorder sections to present cross-platform or CLI options before or alongside PowerShell instructions.
GitHub Create Pull Request
Communication Services Set up and create access tokens for Teams users ...nication-services/quickstarts/manage-teams-identity.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a bias towards Windows environments, particularly in the administrator troubleshooting section. PowerShell is the only command-line tool mentioned for resolving service principal issues, with no equivalent Bash or Azure CLI examples for Linux/macOS users. The instructions and troubleshooting steps assume the use of Windows tools and patterns, such as starting PowerShell as an administrator and installing PowerShell modules, without offering alternatives for non-Windows platforms. There is no mention of Linux or cross-platform approaches for these administrative tasks.
Recommendations
  • Provide equivalent Azure CLI or Bash commands for service principal creation and troubleshooting steps, ensuring Linux/macOS users can follow along without PowerShell.
  • Explicitly mention cross-platform alternatives where PowerShell is referenced, and clarify which steps are platform-agnostic.
  • Add notes or sections indicating how to perform these administrative tasks on Linux and macOS, including installation and usage of required tools.
  • Where possible, use Azure Portal or REST API instructions that are platform-independent.
  • Review and update examples to ensure parity between Windows and Linux, especially in troubleshooting and setup steps.
GitHub Create Pull Request
Communication Services include file ...ion-services/quickstarts/sms/includes/send-sms-java.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides command-line examples specifically for Windows environments, listing Command Prompt and PowerShell commands, but does not include equivalent Linux/macOS shell examples (e.g., Bash). This prioritizes Windows usage and may hinder Linux users from following along easily.
Recommendations
  • Add Bash (Linux/macOS) command examples alongside Command Prompt and PowerShell, especially for Maven commands.
  • Explicitly mention that the commands work on Linux/macOS terminals and provide any necessary syntax adjustments (e.g., quoting).
  • Ensure that all instructions referencing 'terminal or command window' clarify cross-platform compatibility.
  • Consider listing Bash examples first or equally with Windows examples to avoid implicit prioritization.
GitHub Create Pull Request
Communication Services Access a user's Teams Phone separate from their Teams client ...ts/tpe/teams-phone-extensibility-access-teams-phone.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation shows a Windows bias in several ways: the only explicit UI instructions for enabling Teams users refer to the Microsoft 365 admin center, which is primarily accessed via a web interface but is often associated with Windows environments. The only command-line tool mentioned for obtaining a Resource Account ObjectId is the MicrosoftTeams PowerShell cmdlet (Get-CsOnlineApplicationInstance), with no mention of equivalent Graph API or CLI commands for Linux/Mac users. There are no Linux-specific instructions, nor are cross-platform alternatives (such as Azure CLI or REST API examples) provided for steps that reference PowerShell.
Recommendations
  • Include Linux/macOS-friendly instructions for enabling Teams users, such as using Microsoft Graph API or Azure CLI.
  • When referencing PowerShell cmdlets, also provide equivalent REST API or CLI commands and examples.
  • Explicitly mention that the admin center is web-based and accessible from any OS, to avoid implying a Windows-only workflow.
  • Add examples using cross-platform tools for all steps currently covered only by Windows-centric tools.
  • Review all steps for implicit Windows assumptions and clarify cross-platform compatibility where applicable.
GitHub Create Pull Request
Communication Services Teams Phone Extensibility ...uickstarts/tpe/teams-phone-extensibility-quickstart.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates a strong Windows bias, particularly in the provisioning and administration steps for Teams Phone extensibility. Most command-line examples use PowerShell cmdlets and modules (e.g., Connect-MicrosoftTeams, New-CsOnlineApplicationInstance), which are native to Windows and not available or fully supported on Linux. The instructions for bot creation also reference Azure PowerShell modules and commands before mentioning Azure CLI, and do not provide Linux shell equivalents or guidance for cross-platform usage. There is no mention of Linux-specific tools, nor are there alternative examples for Linux environments. The use of Teams Admin Center and Microsoft 365 Admin Center further reinforces a Windows-centric workflow.
Recommendations
  • Provide equivalent Linux/bash command examples for all PowerShell cmdlets, especially for Teams administration tasks. If not possible, clarify platform limitations.
  • Highlight Azure CLI as the preferred cross-platform tool for bot and resource provisioning, and ensure all steps can be completed via CLI on Linux/macOS.
  • Explicitly state platform requirements and limitations for PowerShell modules and Teams administration, and offer guidance for Linux users (e.g., using remote management, web portals, or REST APIs).
  • Where GUI steps are described (Teams Admin Center, Microsoft 365 Admin Center), clarify that these are web-based and accessible from any OS.
  • Add a section or callouts for Linux/macOS developers, summarizing the steps that can be performed on non-Windows platforms and providing links to relevant documentation.
GitHub Create Pull Request
Communication Services Quickstart - Teams interop calls on Azure Communication Services ...video-calling/get-started-teams-interop-group-calls.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by referencing Windows-centric tools and patterns, such as linking to Teams deployment instructions that are Windows-focused, and mentioning PowerShell as the method for enabling Enterprise Voice for Teams users without providing equivalent Linux or cross-platform alternatives. There are no explicit Linux examples or instructions for Linux users, and Windows tools are referenced before any cross-platform or Linux options.
Recommendations
  • Provide Linux-specific instructions or alternatives for Teams deployment and configuration, such as using Teams on Linux or web clients.
  • Include cross-platform or Linux-friendly methods for enabling Enterprise Voice, such as using Microsoft Graph API or Azure CLI, instead of only referencing PowerShell.
  • Clarify that the sample code and instructions are OS-agnostic where applicable, and explicitly mention compatibility with Linux and macOS.
  • Add notes or links to documentation for running the sample on Linux (e.g., installing Node.js, using npx/webpack on Linux, browser compatibility).
  • Ensure all referenced tools (e.g., Azure portal, Graph API) are described as accessible from any OS, and avoid implying Windows exclusivity.
GitHub Create Pull Request
Confidential Computing Secure Key Release with Azure Key Vault and application on Confidential VMs with AMD SEV-SNP ...idential-computing/skr-flow-confidential-vm-sev-snp.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits several signs of Windows bias. PowerShell is the only scripting example provided for performing the key release operation, with no equivalent Bash or Linux shell script. Windows tools and patterns (such as PowerShell, VC_redist, and Windows-specific instructions) are mentioned before or more prominently than their Linux equivalents. The instructions for retrieving managed identity object IDs mention PowerShell first, and the main scripting example is PowerShell-centric, despite the scenario being equally applicable to Linux confidential VMs. There is a lack of parity in scripting examples and tool usage for Linux users.
Recommendations
  • Provide a Bash or Linux shell script example for the key release operation, mirroring the PowerShell example.
  • Ensure that instructions for retrieving managed identity object IDs mention Azure CLI and Linux-native tools before or alongside PowerShell.
  • Where possible, use cross-platform tools (e.g., Azure CLI, REST API) in examples, or provide both Windows and Linux variants.
  • Balance the order and prominence of Windows and Linux instructions throughout the documentation.
  • Clarify which steps are OS-agnostic and which require platform-specific commands, and offer guidance for both platforms.
GitHub Create Pull Request
Connectors Enable stateful mode for stateless built-in connectors ...ectors/enable-stateful-affinity-built-in-connectors.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation provides detailed instructions and code samples for Azure PowerShell, a Windows-centric tool, but does not offer equivalent examples for Linux-native tools (such as Azure CLI or REST via curl). The troubleshooting and configuration sections rely exclusively on PowerShell commands, and there are no Linux shell or cross-platform alternatives presented. This creates a bias toward Windows users and may hinder Linux users from following the guide easily.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, showing how to update resource properties and troubleshoot errors using az commands.
  • Include REST API usage examples with curl, demonstrating how to PATCH the resource configuration from a Linux shell.
  • Explicitly mention that Azure PowerShell is available on Linux and macOS, but provide native shell examples to improve accessibility.
  • Ensure troubleshooting steps are also covered for CLI and REST methods, not just PowerShell.
  • Review all screenshots and UI instructions to confirm they are not Windows-specific (e.g., avoid references to Windows-only browser features or tools).
GitHub Create Pull Request
Connectors Process IBM Host Files in Standard Workflows ...icles/connectors/integrate-host-files-ibm-mainframe.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-based tools (HIS Designer, Visual Studio, .NET Framework 4.8) for generating required metadata files, with no mention of Linux alternatives or cross-platform options. All setup and workflow examples assume the use of Windows environments and tools, and there are no instructions or guidance for Linux users. The documentation does not provide parity for Linux users who may wish to generate or manage HIDX files, nor does it mention any Linux-compatible approaches.
Recommendations
  • Provide instructions for generating HIDX files on Linux, or clarify if the process is Windows-only.
  • List any cross-platform or Linux-compatible alternatives to HIS Designer and Visual Studio, if available.
  • Explicitly state platform requirements and limitations for metadata generation and workflow design.
  • Offer guidance on using Azure Logic Apps and IBM Host File connector from Linux environments, including file upload and workflow management.
  • If no Linux alternatives exist, suggest workarounds (e.g., using a Windows VM or container) and document these steps.
GitHub Create Pull Request
Confidential Computing About Azure confidential VMs ...les/confidential-computing/confidential-vm-overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ windows_reference_links
Summary
The documentation page demonstrates mild Windows bias. Windows tools and documentation are referenced more frequently and prominently than Linux equivalents, especially in sections discussing Trusted Platform Module (TPM), Secure Boot, and feature limitations. Reference links for TPM and Secure Boot point to Windows documentation, and some feature limitations link to Windows Server/Hyper-V docs. In the OS support table, Windows versions are listed in detail and with more granularity than Linux distributions, and Windows is presented before Linux in some feature limitation links.
Recommendations
  • Provide equivalent Linux documentation links for TPM and Secure Boot concepts (e.g., point to Linux kernel or distribution documentation on TPM and Secure Boot).
  • Balance reference links by including both Windows and Linux resources where applicable.
  • Ensure Linux examples and tools are mentioned alongside Windows ones, especially for key features like attestation, disk encryption, and boot security.
  • Expand the OS support table to include more Linux distributions and versions, and provide parity in detail with Windows listings.
  • Where feature limitations reference Windows-specific technologies (e.g., Hyper-V live migration), clarify Linux equivalents or note if the limitation applies to Linux as well.
GitHub Create Pull Request
Container Apps Code to cloud options in Azure Container Apps .../main/articles/container-apps/code-to-cloud-options.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-centric tools and workflows, such as Visual Studio and Visual Studio Code, and referencing PowerShell before Bash in CLI automation. There is a lack of explicit Linux-focused examples, and Windows tools are mentioned exclusively or before their Linux equivalents. The resources and next steps also emphasize Windows development environments, with no mention of Linux editors or workflows.
Recommendations
  • Include explicit Linux examples and workflows, such as using Linux-native editors (e.g., Vim, Emacs, JetBrains IDEs) for container app deployment.
  • Provide Bash-first or Bash-only CLI automation examples, and clarify cross-platform compatibility for CLI commands.
  • Add resources and tutorials for deploying from Linux environments, including instructions for common Linux distributions.
  • Balance references to Visual Studio/VS Code with Linux alternatives, or at least acknowledge their cross-platform nature.
  • Mention container tooling and registry workflows commonly used in Linux environments (e.g., Podman, Docker Compose on Linux).
GitHub Create Pull Request
Container Apps Monitor Azure Container Apps metrics ...zure-docs/blob/main/articles/container-apps/metrics.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page references both Azure CLI and Azure PowerShell for retrieving metrics, but PowerShell is mentioned explicitly and linked alongside CLI, which is a Windows-centric tool. There are no Linux-specific examples, nor is there mention of Linux-native tools or shell commands. The documentation does not provide parity in examples or instructions for Linux users, and the order of mention (CLI and PowerShell) subtly prioritizes Windows tooling.
Recommendations
  • Provide explicit Linux shell examples (e.g., bash commands using Azure CLI) for metric retrieval.
  • Mention and link to cross-platform tools first (Azure CLI) before Windows-specific tools (PowerShell).
  • Clarify that Azure CLI works on Linux, macOS, and Windows, and provide installation/use instructions for non-Windows platforms.
  • Include screenshots or terminal examples from Linux environments.
  • If PowerShell is referenced, also mention PowerShell Core's cross-platform support, or clarify the distinction.
GitHub Create Pull Request
Cost Management Billing Assign permissions to Cost Management APIs ...nt-billing/automate/cost-management-api-permissions.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by referencing Azure PowerShell as the primary CLI tool for assigning roles to service principals, without mentioning cross-platform alternatives such as Azure CLI or providing Linux/macOS-specific instructions. The examples and links focus on PowerShell and portal-based workflows, which are more familiar to Windows users, and do not offer parity for Linux users or those using bash or other shells.
Recommendations
  • Include Azure CLI examples for assigning roles to service principals, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Explicitly mention that Azure PowerShell is available on Linux/macOS, or provide instructions for installing and using it on those platforms.
  • Add bash or shell script examples where appropriate, especially for automation scenarios.
  • Ensure that portal instructions are supplemented with command-line alternatives for users who prefer or require non-GUI workflows.
  • Review linked articles to ensure Linux/macOS parity in examples and instructions.
GitHub Create Pull Request
Cost Management Billing Analyze Azure costs with the Power BI App ...-cost-data-azure-cost-management-power-bi-template-app.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates Windows bias by exclusively referencing Power BI, a tool with limited Linux support, and by providing instructions and screenshots that assume a Windows/Power BI Desktop environment. There are no examples or guidance for Linux users, nor are alternative cross-platform or Linux-native tools mentioned. The documentation also highlights Windows Server AHB usage in reporting, further centering Windows-specific scenarios.
Recommendations
  • Include explicit notes about Power BI's platform support, clarifying limitations for Linux users.
  • Provide alternative instructions or tool recommendations for Linux users (e.g., using Power BI web, Azure CLI, or open-source BI tools like Grafana).
  • Add examples or troubleshooting steps relevant to Linux environments where possible.
  • Mention cross-platform data access methods (such as REST APIs or CSV exports) that Linux users can utilize.
  • Balance coverage of Windows-specific features (like AHB) with equivalent Linux VM scenarios, if applicable.
GitHub Create Pull Request
Cost Management Billing Quickstart - Create a budget with Bicep ...-management-billing/costs/quick-create-budget-bicep.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all deployment and management tasks. However, PowerShell examples are given equal prominence as CLI, and PowerShell is a Windows-centric tool. References to PowerShell modules (e.g., Get-AzActionGroup) are included alongside CLI commands. There is no explicit mention of Linux-specific shell patterns (such as Bash arrays), nor are there any notes about differences in variable syntax or usage between Windows (PowerShell) and Linux (Bash). The documentation assumes familiarity with PowerShell, which may disadvantage Linux users.
Recommendations
  • Add explicit Bash shell examples for variable assignment and usage, especially for parameters passed to Azure CLI commands (e.g., arrays of emails or resource groups).
  • Include notes or tips about differences in variable syntax between PowerShell and Bash when using Azure CLI.
  • Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows, while PowerShell is primarily Windows-focused.
  • Consider listing CLI (Bash) examples before PowerShell to reduce perceived Windows-first bias.
  • Where PowerShell modules are referenced, provide equivalent Bash/CLI commands or links to relevant documentation for Linux users.
GitHub Create Pull Request
Cost Management Billing Introduction to cost allocation ...nagement-billing/costs/cost-allocation-introduction.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by consistently listing Windows-centric tools (Azure portal, PowerShell) before cross-platform options (CLI, REST API) when describing how to manage subscriptions and resource groups. There are no explicit Linux or Bash examples, nor is there mention of Linux-specific tooling or workflows. The repeated emphasis on PowerShell and the Azure portal, both of which are traditionally associated with Windows environments, further reinforces this bias.
Recommendations
  • Provide explicit examples using Azure CLI commands (which are cross-platform) alongside or before PowerShell examples.
  • Include references to Bash scripting or Linux-native workflows where applicable.
  • When listing management options, alternate the order or explicitly state that CLI and REST API are cross-platform and suitable for Linux/macOS users.
  • Add links to documentation or tutorials for managing Azure resources from Linux environments.
  • Ensure screenshots and diagrams do not exclusively depict Windows interfaces.
GitHub Create Pull Request
Cost Management Billing Copy billing roles from one MCA to another MCA across tenants with a script ...s/cost-management-billing/manage/mca-role-migration.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a strong Windows bias by exclusively providing a PowerShell script for role migration, instructing users to save the script as a PS1 file, and guiding them to use PowerShell in Azure Cloud Shell. There are no Bash or Linux-native script examples, nor is there mention of how to perform the same task using Linux tools or shell environments. The instructions and screenshots prioritize PowerShell and do not address Linux users' needs.
Recommendations
  • Provide equivalent Bash or Python script examples for Linux/macOS users.
  • Include instructions for running the migration script in Bash within Azure Cloud Shell, or clarify cross-platform compatibility.
  • Mention prerequisites and installation steps for PowerShell Core on Linux/macOS if PowerShell is required.
  • Add notes or sections highlighting any differences or considerations when running the script on non-Windows platforms.
  • Offer troubleshooting tips for Linux users, such as file permission issues or dependency installation.
GitHub Create Pull Request
Cost Management Billing Protect tenants and subscriptions from abuse and fraud attacks ...gement-billing/manage/protect-tenants-subscriptions.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation focuses exclusively on Microsoft-centric tools and environments (Azure portal, Microsoft 365 Admin Center, Microsoft Entra, etc.), with no mention of Linux-specific tools, CLI commands, or cross-platform alternatives. References to deletion and management actions point to Microsoft portals and documentation, and related content links include Azure PowerShell tabs but do not mention Bash, Azure CLI, or Linux workflows. This creates a Windows-first bias and omits guidance for Linux users.
Recommendations
  • Include examples using Azure CLI and Bash for subscription and resource management alongside PowerShell examples.
  • Add explicit instructions or links for performing tenant and subscription actions from Linux environments.
  • Reference cross-platform tools and workflows where possible, not just Microsoft portals and Windows-based admin centers.
  • Ensure related content links offer parity between PowerShell and CLI/Bash tabs, and clarify which steps are platform-agnostic.
GitHub Create Pull Request
Cost Management Billing Link a partner ID to your Power Platform and Dynamics Customer Insights accounts with your Azure credentials ...-billing/manage/link-partner-id-power-apps-accounts.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a Windows bias by prioritizing Windows-centric tools and workflows. PowerShell is featured heavily and mentioned before Azure CLI, with detailed PowerShell command examples provided. The Azure portal (a GUI typically used on Windows) is presented as the primary method for PAL association, and there is no mention of Linux-specific considerations, shell environments, or cross-platform differences. Azure CLI is included, but only as an alternative, and there are no explicit Linux shell examples or guidance for non-Windows users.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples, highlighting its cross-platform compatibility.
  • Include explicit instructions or notes for Linux/macOS users, such as shell environment setup, authentication differences, or package installation steps.
  • Clarify that both PowerShell and Azure CLI are available on Windows, Linux, and macOS, and provide links to installation guides for all platforms.
  • Add screenshots or walkthroughs using Linux environments (e.g., Ubuntu terminal) for parity with Windows GUI examples.
  • Avoid referring to PowerShell as the default or primary method; instead, use neutral language and order (e.g., 'You can use either PowerShell or Azure CLI...').
GitHub Create Pull Request
Cost Management Billing Link a partner ID to your account that’s used to manage customers ...cles/cost-management-billing/manage/link-partner-id.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates a Windows bias in several ways: command examples for PowerShell and Azure CLI are consistently shown with Windows-style prompts (C:\>), and installation instructions reference PowerShell modules and CLI extensions without clarifying cross-platform usage. There are no explicit Linux/macOS examples, nor are there instructions for using these tools on non-Windows platforms. The ordering of examples and screenshots also implicitly prioritizes Windows environments.
Recommendations
  • Provide explicit Linux/macOS command examples, using appropriate shell prompts (e.g., $ for bash/zsh) and paths.
  • Clarify that Azure PowerShell and Azure CLI are cross-platform, and provide installation instructions for Linux/macOS alongside Windows.
  • Remove Windows-specific prompts (C:\>) from CLI and PowerShell examples, or provide platform-specific variants.
  • Mention alternative shells and package managers (e.g., apt, yum, Homebrew) for installing Azure CLI/PowerShell modules.
  • Add notes or sections addressing usage in Linux/macOS environments, including any differences in authentication or environment setup.
GitHub Create Pull Request
Cost Management Billing Programmatically create MCA subscriptions across tenants ...bscription-microsoft-customer-agreement-across-tenants.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for obtaining the service principal ID, but lists Azure CLI first. However, only Azure PowerShell is mentioned for Windows-specific tooling, and there are no explicit Linux shell (bash) or cross-platform scripting examples beyond Azure CLI. The rest of the steps use REST API calls, which are platform-neutral, but there is a lack of explicit Linux or bash command-line examples for authentication and other steps. No mention is made of Linux-specific tools or patterns, and Windows tools (PowerShell) are given parity or precedence.
Recommendations
  • Add explicit bash/Linux shell examples for all command-line steps, especially for authentication and REST API invocation (e.g., using curl or httpie).
  • Ensure that Azure CLI examples are clearly marked as cross-platform and provide guidance for running them on Linux/macOS.
  • If PowerShell is mentioned, also mention bash equivalents or alternatives for Linux users.
  • Consider adding a section or note about platform compatibility for all tools used.
  • Review the order of examples to avoid implicit prioritization of Windows tools (e.g., alternate between CLI and PowerShell or group by platform).
GitHub Create Pull Request
Cost Management Billing What is Azure savings plans for compute? ...-billing/savings-plan/savings-plan-compute-overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page shows mild Windows bias. Windows-specific details (such as Windows VM meters and Windows software costs) are mentioned before or more prominently than Linux equivalents. There are references to Windows licensing and Azure Hybrid Benefit, but no equivalent Linux licensing or cost considerations. No Linux-specific examples, scenarios, or tooling are provided, and the only technical differentiation is that Linux compute meters are mentioned as 'same as Windows', rather than described independently.
Recommendations
  • Add explicit Linux VM examples and scenarios, including any differences in billing or savings plan application.
  • Clarify Linux-specific cost considerations, such as licensing, and explicitly state if there are none.
  • Present Windows and Linux information in parallel, rather than Windows-first (e.g., describe both compute meters for Windows and Linux VMs together).
  • If mentioning Azure Hybrid Benefit for Windows, clarify if there are similar or no equivalent benefits for Linux.
  • Include Linux-specific tools or patterns for managing savings plans, if any exist.
GitHub Create Pull Request
Cost Management Billing Software costs not included in Azure savings plans ...nt-billing/savings-plan/software-costs-not-included.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page focuses exclusively on Windows software costs and Windows Server meters, with no mention of Linux VM software costs or equivalent Linux licensing considerations. All examples and tables are Windows-centric, and there is no discussion of how savings plans interact with Linux VMs or any Linux-specific meters. This creates a Windows-first perspective and omits Linux parity.
Recommendations
  • Add a section describing how savings plans apply to Linux VMs, including any relevant software costs or the absence thereof.
  • Include tables or examples for Linux VM meters, if applicable, or explicitly state that Linux VMs do not incur additional software meter charges.
  • Provide guidance for users running Linux workloads on Azure, clarifying any differences in cost structure compared to Windows VMs.
  • Ensure that documentation addresses both Windows and Linux users equally, with parallel examples and explanations.
GitHub Create Pull Request
Cost Management Billing Understand your detailed usage and charges ...cost-management-billing/understand/understand-usage.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a mild Windows bias. It suggests opening the usage and charges CSV file in Microsoft Excel or another spreadsheet application, with Excel mentioned first and no Linux-specific tools (such as LibreOffice Calc or command-line utilities) referenced. There are no examples or instructions tailored for Linux users, nor are Linux-native tools or workflows discussed. The documentation does not provide parity in terms of platform-specific guidance or examples.
Recommendations
  • Explicitly mention Linux-compatible tools for opening CSV files, such as LibreOffice Calc, GNOME Spreadsheet, or command-line utilities like 'csvkit' or 'awk'.
  • Provide example workflows for Linux users, such as using 'cat', 'head', or 'grep' to inspect the CSV file, or using Python/pandas for analysis.
  • When listing tools, avoid putting Microsoft Excel first or exclusively; use neutral phrasing such as 'You can open your usage and charges CSV file in spreadsheet applications like Microsoft Excel, LibreOffice Calc, or other compatible tools.'
  • Include a section or note for Linux/macOS users with tips or troubleshooting for common issues when handling Azure billing files on non-Windows platforms.
GitHub Create Pull Request
Cost Management Billing Troubleshoot Azure payment issues ...t-billing/billing-troubleshoot-azure-payment-issues.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates Windows bias by referencing Microsoft Edge and Internet Explorer as the primary browsers for troubleshooting, specifically linking to 'Browse InPrivate in Microsoft Edge'. There are no mentions of Linux browsers (such as Firefox or Chrome on Linux), nor are there troubleshooting steps tailored for Linux users. All browser-related instructions assume a Windows environment, and no command-line or OS-specific examples are provided for Linux users.
Recommendations
  • Include troubleshooting steps for popular Linux browsers (e.g., Firefox, Chrome) and mention their private/incognito modes.
  • Add notes or examples for Linux users, such as clearing browser cache/cookies on Linux.
  • Avoid referencing only Windows-specific tools or browsers; provide cross-platform alternatives or mention them in parallel.
  • Explicitly state that the Azure portal is accessible from any modern browser and OS, and provide links to relevant help articles for Linux and macOS users.
GitHub Create Pull Request
Cost Management Billing Review your Azure Enterprise Agreement bill ...billing/understand/review-enterprise-agreement-bill.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Microsoft Excel for CSV report handling and troubleshooting, without mentioning Linux or cross-platform alternatives. All instructions for viewing and manipulating billing data are based on the Azure portal, with no mention of command-line tools or automation options that might be preferred by Linux users. The guidance assumes the use of Windows-centric tools and workflows, and does not provide parity for Linux environments.
Recommendations
  • Include instructions for opening and processing CSV reports using Linux tools such as LibreOffice Calc, csvkit, or command-line utilities (awk, sed, etc.).
  • Add examples for downloading and manipulating billing data using Azure CLI or PowerShell Core, which are cross-platform, and provide Linux-specific usage notes.
  • Mention alternative workflows for Linux users, such as scripting CSV report handling with Python or shell scripts.
  • Clarify that the Azure portal is web-based and accessible from any OS, but provide parity for users who prefer terminal-based or automated solutions.
  • Where troubleshooting CSV formatting is discussed, add Linux/LibreOffice-specific guidance for regional settings and import options.
GitHub Create Pull Request
Cyclecloud Cluster Template Reference - Nodes ...lecloud/cluster-references/node-nodearray-reference.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits mild Windows bias. Windows-specific features (such as Hybrid Benefit licensing and Secure Boot/TPM) are described in detail, and Windows is mentioned first or as the default in several places (e.g., HybridBenefitLicense defaults to Windows_Server). There is a lack of Linux-specific examples or parity in some advanced attributes (e.g., Secure Boot, TPM, Hybrid Benefit), and no explicit Linux command-line or configuration examples are provided. Some attributes and notes are Windows-centric, and Linux equivalents or considerations are not always mentioned.
Recommendations
  • Include explicit Linux examples and use cases alongside Windows ones, especially for attributes that have OS-specific behavior.
  • Clarify which attributes are applicable to Linux, Windows, or both, and document any differences in behavior or requirements.
  • Provide Linux-first or at least Linux-equal ordering in attribute tables and examples, especially for features like Secure Boot, TPM, and licensing.
  • Add Linux-specific troubleshooting notes or references where Windows-specific features are discussed.
  • Ensure that all OS-specific features (e.g., Hybrid Benefit) are described with equal detail for Linux distributions that support similar features (such as RHEL/SLES BYOS).
GitHub Create Pull Request
Cyclecloud User Authentication ...main/articles/cyclecloud/how-to/user-authentication.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias by prioritizing Active Directory (a Windows-centric technology) in both order and detail, providing examples and terminology specific to Windows (e.g., DOMAIN\user), and referencing Windows authentication patterns before mentioning LDAP (which is more cross-platform). There are no explicit Linux or OpenLDAP configuration examples, and the only Linux-specific mention is in the context of SSH keys for cluster nodes, which is brief and lacks setup details.
Recommendations
  • Add explicit examples for configuring LDAP with OpenLDAP servers, including sample settings and user formats typical for Linux environments.
  • Provide authentication examples using Linux tools (e.g., ldapsearch, shell commands) alongside GUI instructions.
  • Balance the order of presentation by discussing LDAP and Linux authentication patterns before or alongside Active Directory.
  • Include screenshots or configuration samples from Linux environments, not just Windows/Active Directory.
  • Clarify user formats for Linux/LDAP (e.g., uid=username,ou=users,dc=example,dc=com) in addition to Windows formats.
  • Expand the section on SSH key management for Linux clusters with step-by-step instructions and examples.
GitHub Create Pull Request
Cyclecloud Jetpack Reference ...cs/azure-docs/blob/main/articles/cyclecloud/jetpack.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation demonstrates mild Windows bias. Windows paths and behaviors are often mentioned before Linux equivalents (e.g., installation directories), and some features are described as Windows-only or unsupported on Windows without providing Linux-specific guidance. There are references to Windows tools and patterns (e.g., custom script extension, Windows paths), but Linux-specific examples, commands, or troubleshooting steps are generally missing or less emphasized.
Recommendations
  • Alternate the order of Windows and Linux references, or present Linux examples first where appropriate.
  • Provide explicit Linux command-line examples, including shell commands and file paths, especially for features that differ between platforms.
  • Clarify platform-specific limitations and offer Linux alternatives or workarounds when a feature is Windows-only.
  • Include troubleshooting steps and usage notes for both Windows and Linux environments.
  • Add more detail about Linux system integration (e.g., systemd service management, permissions, SELinux/AppArmor considerations) where relevant.
GitHub Create Pull Request
Data Factory Applying DataOps ...-docs/blob/main/articles/data-factory/apply-dataops.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-centric tools (PowerShell, Visual Studio, .NET/NUnit) for automated testing and CI/CD, and by providing examples and recommendations that assume a Windows development environment. Linux alternatives (such as Bash, shell scripts, or Linux-native CI/CD tools) are not mentioned, and Windows tools are referenced before any cross-platform or Linux options. There are no explicit Linux or macOS examples, and the documentation does not address how to perform equivalent tasks on non-Windows platforms.
Recommendations
  • Include examples using Bash, shell scripts, and Linux-native tools for CI/CD and automated testing.
  • Mention cross-platform alternatives to PowerShell, such as Azure CLI or REST API calls via curl.
  • Provide guidance for setting up automated testing environments using Python (pytest), JavaScript (Jest), or other cross-platform frameworks.
  • Add explicit instructions and screenshots for performing key steps on Linux and macOS, not just Windows.
  • Reference and link to documentation for Azure Data Factory usage from Linux environments, including deployment and testing.
  • Clarify that Azure CLI and REST API methods work on all platforms and provide sample commands for Linux/macOS.
GitHub Create Pull Request
Cyclecloud Install the Command Line Interface ...n/articles/cyclecloud/how-to/install-cyclecloud-cli.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation provides both Linux and Windows installation instructions for the CycleCloud CLI, but Windows-specific details (such as PowerShell scripts and GUI-based extraction) are given equal prominence. The Windows installation section references Windows Explorer and PowerShell, while the Linux section uses standard shell commands. The prerequisites section mentions installing Python for Windows, but assumes Linux/Mac users already have Python. There is a slight Windows-first bias in the prerequisites and the use of Windows tools (Explorer, PowerShell) without mentioning Linux equivalents for GUI extraction or scripting.
Recommendations
  • Provide parity in scripting examples: For Windows, offer command-line installation instructions (e.g., using Command Prompt or PowerShell commands to unzip and run the installer), not just GUI-based steps.
  • Mention Linux GUI alternatives for extracting zip files, such as using Nautilus or Archive Manager, to match the Windows Explorer example.
  • In the prerequisites, explicitly mention how to verify or install Python on Linux and Mac, not just Windows.
  • Ensure that both platforms have equal detail and clarity in their instructions, and avoid assuming prior knowledge for one platform over the other.
  • If PowerShell scripts are provided for Windows, consider providing Bash scripts for Linux where appropriate.
GitHub Create Pull Request
Cyclecloud Projects ...-docs/blob/main/articles/cyclecloud/how-to/projects.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page references specs as Python, shell, or PowerShell scripts, but does not provide any concrete examples for Linux shell scripts or Linux-specific usage. The only explicit environment variable path examples are for Linux, but there are no corresponding Windows paths. There is no mention of Linux tools or patterns, and PowerShell is mentioned as a script type without parity for bash or other Linux shells. The documentation does not provide Linux-first or Linux-specific examples, and the CLI commands shown are platform-neutral but lack explicit Linux context.
Recommendations
  • Add explicit Linux shell script examples alongside PowerShell examples.
  • Provide Linux-specific file path examples (e.g., /var/log, /home/user) and contrast with Windows equivalents (e.g., C:\ClusterInit\...).
  • Mention bash or other Linux shells as supported script types wherever PowerShell is referenced.
  • Include Linux CLI usage patterns, such as using environment variables, permissions, and file system conventions.
  • Ensure that Linux tools and workflows are described with equal prominence to Windows/PowerShell ones.
GitHub Create Pull Request
Devtest Labs Automate adding a lab user ...ob/main/articles/devtest-labs/automate-add-lab-user.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a clear Windows bias. PowerShell is heavily featured throughout, with multiple examples and references to PowerShell-specific cmdlets for key tasks (e.g., obtaining ObjectId, deploying templates, generating GUIDs). Windows tools and patterns (PowerShell, New-Guid) are mentioned exclusively or before their cross-platform equivalents. The Azure CLI section is present but less detailed and lacks parity in example depth. There are no explicit Linux shell/bash examples, nor references to Linux-native tools or workflows.
Recommendations
  • Add bash/Linux shell examples for tasks such as generating GUIDs, obtaining ObjectId, and deploying ARM templates using Azure CLI.
  • Expand the Azure CLI section to match the detail and coverage of the PowerShell section, including step-by-step instructions and parameter explanations.
  • Reference cross-platform tools and workflows (e.g., uuidgen for GUID generation, az ad user for ObjectId retrieval) alongside or before Windows-specific tools.
  • Ensure that all examples and instructions are clearly marked as cross-platform where applicable, and explicitly mention Linux/Mac compatibility.
  • Consider adding a table or section comparing PowerShell and CLI commands for each major step, to help users choose their preferred environment.
GitHub Create Pull Request
Devtest Labs Create a Service Fabric cluster environment ...test-labs/create-environment-service-fabric-cluster.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates a Windows bias in several ways: the default operating system for cluster VMs is Windows; certificate creation instructions exclusively use a PowerShell script (Create-ClusterCertificate.ps1) and require launching PowerShell and Notepad, both Windows-centric tools; there are no Linux-specific instructions or examples for certificate creation or cluster management; and Windows terminology and workflows are presented first or exclusively.
Recommendations
  • Provide Linux-specific instructions for certificate creation, such as using OpenSSL commands, and include example scripts.
  • Mention and demonstrate how to perform cluster management tasks (start/stop, etc.) from Linux environments, including CLI commands.
  • When describing OS selection, present Windows and Linux options equally, and avoid defaulting to Windows.
  • Replace or supplement PowerShell/Notepad steps with cross-platform alternatives (e.g., Bash, nano, vi, or VS Code).
  • Add screenshots and examples from Linux environments to balance visual representation.
GitHub Create Pull Request
Devtest Labs Add and configure lab users with role-based access control (RBAC) .../articles/devtest-labs/devtest-lab-add-devtest-user.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by exclusively providing Azure PowerShell examples for automation, referencing Microsoft accounts and Entra ID (with links to Windows Server docs), and omitting any Linux-specific CLI (az CLI) or Bash examples. The prerequisites and instructions focus on PowerShell and do not mention Linux tools or workflows, making it less accessible for Linux users.
Recommendations
  • Add equivalent examples using Azure CLI (az) commands, which are cross-platform and commonly used on Linux and macOS.
  • Include instructions for running automation scripts in Bash or other Linux shells, not just PowerShell.
  • Reference Linux account management and authentication documentation where relevant, not only Microsoft account and Windows Server docs.
  • Clarify that Azure Cloud Shell supports both Bash and PowerShell, and provide steps for both environments.
  • Ensure screenshots and UI references are not Windows-specific, or supplement with examples from Linux environments where applicable.
GitHub Create Pull Request
Devtest Labs Create and add a VM to a lab .../blob/main/articles/devtest-labs/devtest-lab-add-vm.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates a Windows-first bias by using a Windows 11 Pro image as the example in the main workflow, mentioning PowerShell scripts for VM copying without Linux alternatives, and omitting explicit Linux VM creation or connection examples. Linux-specific instructions, images, or CLI commands are not provided, and Windows terminology is used by default.
Recommendations
  • Provide parallel examples using a popular Linux image (e.g., Ubuntu) alongside the Windows 11 Pro example, including screenshots and step-by-step instructions.
  • Include Linux-specific connection instructions (e.g., SSH commands) and mention differences in credential setup for Linux VMs.
  • When referencing scripts for copying VMs, offer both PowerShell and Bash/CLI alternatives, or clarify cross-platform options.
  • Ensure artifact examples include Linux-relevant tools and software, not just those commonly used on Windows.
  • Review terminology and screenshots to ensure Linux VMs are equally represented in visuals and instructions.
GitHub Create Pull Request
Devtest Labs Create custom artifacts for VMs ...n/articles/devtest-labs/devtest-lab-artifact-author.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell-based examples and referencing Windows-specific tools (e.g., Chocolatey, powershell.exe) without offering equivalent Linux shell script or tool examples. All code snippets and walkthroughs focus on Windows artifacts, and there is no demonstration of how to create or use artifacts for Linux VMs. The structure and examples prioritize Windows scenarios, leaving Linux users without guidance or parity.
Recommendations
  • Add parallel Linux examples using shell scripts (e.g., Bash) in artifact definitions, showing how to use 'commandToExecute' for Linux VMs.
  • Include Linux-specific tools (e.g., apt, yum) in sample artifacts, similar to how Chocolatey is used for Windows.
  • Provide a downloadable sample artifact for Linux, such as one that installs a package or runs a shell script.
  • Ensure that documentation sections and examples alternate or equally represent both Windows and Linux scenarios.
  • Explicitly mention differences and best practices for Linux artifact development, including script file extensions (.sh), permissions, and common patterns.
GitHub Create Pull Request
Devtest Labs Grant user permissions to specific lab policies ...st-lab-grant-user-permissions-to-specific-lab-policies.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page exclusively uses PowerShell for all examples and instructions, which is primarily a Windows-centric tool. There are no references to Linux-native tools, Bash, Azure CLI, or cross-platform alternatives. The installation instructions and all code samples assume the use of Azure PowerShell, and there is no mention of how to perform these tasks on Linux or macOS systems. This creates a strong Windows bias and may hinder users working in non-Windows environments.
Recommendations
  • Add equivalent examples using Azure CLI, which is cross-platform and commonly used on Linux and macOS.
  • Include Bash shell scripts or command-line instructions for Linux users.
  • Explicitly mention that Azure PowerShell is available on Linux and macOS, or provide installation instructions for those platforms.
  • Reorder or balance examples so that Linux and cross-platform tools are presented alongside or before Windows-specific tools.
  • Provide guidance on how to perform role assignments and policy management using the Azure Portal (web interface), which is platform-agnostic.
GitHub Create Pull Request
Devtest Labs Create a custom image from a lab VM ...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-create-custom-image-from-vm-using-portal.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by mentioning Windows-specific tools (Sysprep) before Linux equivalents (deprovision), and by providing more detail and direct links for Windows processes. There are no concrete Linux command examples or screenshots, and the generalization step is described primarily in Windows terms.
Recommendations
  • Present Linux and Windows generalization options with equal prominence, possibly alternating the order or grouping them together.
  • Include explicit Linux command examples (e.g., waagent -deprovision) and step-by-step instructions for Linux VMs.
  • Add screenshots or illustrations showing the process for both Windows and Linux VMs.
  • Provide direct links to both Windows and Linux documentation for generalization procedures.
  • Clarify any differences in the image creation workflow for Linux VMs, if applicable.
GitHub Create Pull Request
Devtest Labs Create environments from ARM templates ...evtest-labs/devtest-lab-create-environment-from-arm.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by providing detailed automation instructions and scripts exclusively for Azure PowerShell, with no equivalent Bash or Linux shell example. PowerShell is presented first and in greater detail than Azure CLI, and the automation section is heavily focused on Windows tooling. There are no Linux-specific instructions or examples, and the only mention of Azure CLI is brief and lacks a worked example.
Recommendations
  • Add a full Azure CLI (bash) example for automating environment creation, including a sample script and usage instructions.
  • Present Azure CLI and PowerShell options side-by-side, or alternate which is presented first, to avoid Windows-first ordering.
  • Explicitly mention cross-platform compatibility and provide guidance for Linux/macOS users.
  • Include notes or links to relevant Linux tools or patterns (e.g., using curl, jq, or bash scripting for automation).
  • Review screenshots and UI instructions for OS-neutral language and imagery.
GitHub Create Pull Request
Devtest Labs Create custom images for lab VMs from VHD files ...n/articles/devtest-labs/devtest-lab-create-template.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page shows moderate Windows bias. PowerShell is mentioned as an alternative method for creating custom images and for uploading VHD files, with no equivalent Bash or Linux CLI examples referenced. Windows tools (sysprep) are described before Linux equivalents (deprovision), and the upload instructions reference Microsoft-centric tools (AzCopy, Storage Explorer, PowerShell) without mentioning Linux-native options. The flow and examples tend to prioritize Windows terminology and tooling.
Recommendations
  • Include Bash/Azure CLI examples alongside PowerShell for creating custom images and uploading VHD files.
  • Mention Linux-native tools (e.g., dd, qemu-img, SCP, rsync) for VHD creation and upload, where relevant.
  • Ensure Linux instructions (e.g., waagent --deprovision) are described with equal detail and prominence as Windows (sysprep).
  • Add explicit guidance for Linux users, such as command-line steps for uploading VHDs from Linux environments.
  • Balance the order of Windows and Linux instructions, alternating or grouping them to avoid Windows-first presentation.
GitHub Create Pull Request
Devtest Labs Azure DevTest Labs scenarios ...icles/devtest-labs/devtest-lab-guidance-get-started.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias in several ways: Windows-specific tools (PowerShell, Visual Studio, Fiddler) are mentioned exclusively or before Linux equivalents; automation examples and scripts reference PowerShell without mentioning Bash or CLI alternatives; links to quickstarts and templates are labeled as 'create-lab-windows-vm-*', with no explicit Linux VM examples; artifact examples and VM customization focus on Windows-centric scenarios; and Active Directory domain-join is highlighted without mention of Linux identity solutions.
Recommendations
  • Include Linux-specific examples and quickstarts, such as 'create-lab-linux-vm-bicep.md', 'create-lab-linux-vm-template.md', and 'create-lab-linux-vm-terraform.md'.
  • Provide Bash/Azure CLI script examples alongside PowerShell for automation tasks, such as adding users or deleting VMs.
  • Mention Linux tools and applications (e.g., Git, VS Code, Apache) as artifact examples, not just Windows tools.
  • Describe how to join Linux VMs to identity solutions (e.g., Azure AD, LDAP) if applicable.
  • Ensure ARM template and image builder documentation explicitly covers both Windows and Linux scenarios.
  • Balance references to Windows and Linux in all lists and examples, and avoid defaulting to Windows-first naming or ordering.
GitHub Create Pull Request
Devtest Labs Move DevTest Labs to another region ...cs/blob/main/articles/devtest-labs/how-to-move-labs.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates a Windows bias by providing PowerShell-centric instructions and examples, referencing Windows-specific tools (such as AzCopy and PowerShell cmdlets), and linking to Windows-focused articles (e.g., swapping OS disks using PowerShell). Linux alternatives (such as Bash, CLI, or Linux-native tools) are either missing or mentioned after Windows, and there are no explicit Linux command examples for key steps like disk migration or VM management.
Recommendations
  • Provide equivalent Bash/Azure CLI examples for all PowerShell commands, especially for disk migration and VM management.
  • Include instructions and examples for using AzCopy on Linux/macOS, clarifying cross-platform usage.
  • Reference Linux-focused documentation (e.g., swapping OS disks on Linux VMs) alongside Windows articles.
  • Explicitly state that all steps can be performed on Linux/macOS, and highlight any platform-specific differences.
  • Where screenshots or UI references are given, clarify if the experience differs on non-Windows platforms or in browser-based tools like Azure Cloud Shell.
GitHub Create Pull Request
Devtest Labs Quickstart: Create a lab with REST API ...n/articles/devtest-labs/quickstarts/create-lab-rest.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page exclusively uses PowerShell for all command-line examples, assumes the presence of the PowerShell Az Module, and does not provide equivalent instructions for Linux or macOS users (e.g., Bash, curl, Azure CLI). Windows tooling and patterns are mentioned throughout, with no cross-platform alternatives or parity.
Recommendations
  • Add equivalent examples using Bash and curl for REST API calls, suitable for Linux/macOS users.
  • Include Azure CLI examples for authentication and resource management, as it is cross-platform.
  • Update the prerequisites section to mention both PowerShell and Bash/Azure CLI options.
  • Clearly indicate which steps are platform-specific and provide alternatives for each major OS.
  • Avoid assuming file path conventions (e.g., 'path\body.json') that are Windows-specific; use cross-platform notation or clarify.
GitHub Create Pull Request
Devtest Labs Azure CLI Samples ...re-docs/blob/main/articles/devtest-labs/samples-cli.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ powershell_heavy
Summary
The documentation page exhibits Windows bias by consistently referencing Windows VMs as the default in examples, labeling code samples as 'powershell' even though the scripts are bash/CLI, and omitting explicit Linux VM creation or management examples. There is no mention of Linux-specific VM images, authentication methods, or usage patterns, and the terminology and sample focus suggest a Windows-centric approach.
Recommendations
  • Include examples for creating and managing Linux VMs, specifying Linux marketplace images and SSH authentication.
  • Correct code sample language labels to 'bash' or 'azurecli' where appropriate, instead of 'powershell'.
  • Provide parity in documentation by mentioning both Windows and Linux options in descriptions and tables.
  • Add notes or sections highlighting differences or considerations when working with Linux VMs in Azure DevTest Labs.
  • Ensure that script samples and instructions are platform-neutral or provide alternatives for both Windows and Linux users.
GitHub Create Pull Request
Devtest Labs Upload a VHD file to Azure DevTest Labs by using AzCopy ...es/devtest-labs/devtest-lab-upload-vhd-using-azcopy.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a strong Windows bias. AzCopy is described as a Windows-only tool, and all usage instructions reference Windows environments (Command Prompt, Windows file paths). The process for obtaining the storage account URI is tied to PowerShell and Windows screenshots. There are no Linux or cross-platform examples, nor any mention of Linux-compatible alternatives or usage patterns.
Recommendations
  • Clarify whether AzCopy v10+ is cross-platform (since newer versions support Linux/macOS) and update the note accordingly.
  • Provide Linux and macOS installation instructions for AzCopy, if supported.
  • Include example commands for Linux/macOS shells (e.g., bash), with appropriate file paths and syntax.
  • Add screenshots or instructions that do not reference PowerShell or Windows-only UI elements.
  • Mention alternative tools or approaches for non-Windows users if AzCopy is truly Windows-only.
  • Ensure parity in automation examples, showing how to script uploads on Linux/macOS.
GitHub Create Pull Request
Devtest Labs Create and manage virtual machines in Azure DevTest Labs with Azure CLI ...s/blob/main/articles/devtest-labs/devtest-lab-vmcli.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation demonstrates a moderate Windows bias. The first VM creation example uses a Windows image, and Windows terminology (e.g., 'Remote Desktop') is mentioned before Linux equivalents. Artifact examples include both Linux and Windows, but the sample output for listing artifacts only shows a Windows artifact. The Cloud Shell section gives PowerShell instructions before Bash, and highlights Windows-specific shell syntax issues. Linux examples are present but generally appear after Windows ones.
Recommendations
  • Provide Linux VM creation examples before or alongside Windows examples, or alternate their order.
  • Include sample outputs for both Linux and Windows artifacts when listing artifacts.
  • Present Bash and PowerShell instructions in parallel, or alternate which is shown first.
  • Explicitly mention Linux tools (e.g., SSH) before or alongside Windows tools (e.g., Remote Desktop) when discussing connection options.
  • Ensure parity in artifact examples, showing both Linux and Windows use cases.
  • Consider a section highlighting cross-platform considerations and differences.
GitHub Create Pull Request
Devtest Labs Specify resource group for Azure VMs in DevTest Labs ...b/main/articles/devtest-labs/resource-group-control.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides a detailed PowerShell example for scripting the resource group assignment, but does not offer equivalent examples for Bash, Linux shell, or cross-platform scripting. The command invocation uses Windows-style notation and file extensions (.ps1), and the scripting section is titled 'Use PowerShell' without mentioning alternatives. There is no mention of Linux-specific tools or CLI patterns, nor are Linux/Bash examples provided alongside the PowerShell example.
Recommendations
  • Add a Bash or shell script example using the Azure CLI for Linux/macOS users.
  • Include instructions for running the script on Linux/macOS, such as using .sh files and appropriate command syntax.
  • Clarify that the Azure CLI commands used in the PowerShell script are cross-platform, and provide examples for both Windows and Linux environments.
  • Consider renaming the 'Use PowerShell' section to 'Use scripting' or 'Use PowerShell or Bash', and provide parity in examples.
  • Explicitly mention that the steps are applicable to both Windows and Linux users where relevant.
GitHub Create Pull Request
Devtest Labs Define VM start order with Azure Automation ...devtest-labs/start-machines-use-automation-runbooks.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page exclusively uses PowerShell for scripting and automation examples, with no mention of Bash, Python, or other cross-platform alternatives. All instructions and code samples are tailored to PowerShell and Azure Automation, which is most commonly used on Windows. There is no guidance for Linux users or those preferring non-Windows tools, and Windows-centric terminology and patterns are used throughout.
Recommendations
  • Provide equivalent examples using Bash or Python scripts that can be run on Linux-based systems.
  • Include instructions for using Azure CLI or REST API, which are cross-platform, to achieve the same VM start order functionality.
  • Add a section explicitly addressing Linux users, outlining how to set up and run automation from a Linux environment.
  • Mention and link to Azure Automation support for non-PowerShell runbooks (e.g., Python), and provide sample code.
  • Ensure that references to tools and patterns do not assume a Windows environment by default, and present Linux options alongside Windows options.
GitHub Create Pull Request
Digital Twins Troubleshoot CLI parsing failures ...articles/digital-twins/troubleshoot-error-cli-parse.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page lists Windows shells (CMD, PowerShell) and Windows-specific escaping patterns (backtick) before or alongside Linux equivalents. Examples and troubleshooting steps do not provide Linux-specific details or examples, and Windows tools/shells are mentioned at least as prominently as Linux ones. There is no explicit Linux example or prioritization, and the mention of escaping with a backtick is a Windows/PowerShell-specific pattern.
Recommendations
  • Provide explicit Linux shell (Bash, Zsh) examples for escaping special characters, including common Linux-specific patterns (e.g., use of single/double quotes, backslash).
  • List Linux shells and solutions before or alongside Windows shells to avoid Windows-first ordering.
  • Clarify which escaping patterns apply to which shells (e.g., backtick for PowerShell, backslash for Bash) and provide examples for each.
  • Include troubleshooting steps or examples specifically for Linux environments, such as handling inline JSON in Bash.
  • Mention Linux tools (e.g., cat, nano, vi) for file creation and editing when suggesting passing JSON via file path.
GitHub Create Pull Request
Devtest Labs Troubleshoot VM deployment failures ...es/devtest-labs/troubleshoot-vm-deployment-failures.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell as the primary example for deploying VMs with ARM templates, without mentioning or providing equivalent examples for Linux users (such as Azure CLI or Bash). The troubleshooting steps and patterns are described in a way that assumes familiarity with Windows-centric tools, and there is no parity for Linux or cross-platform command-line approaches.
Recommendations
  • Add Azure CLI and Bash examples alongside PowerShell for ARM template deployments.
  • Explicitly mention that both Windows and Linux users can deploy VMs and provide links or code snippets for Linux workflows.
  • Rephrase troubleshooting steps to be tool-agnostic or provide parallel instructions for both PowerShell and Azure CLI.
  • Include references to Linux documentation and troubleshooting tools where relevant.
GitHub Create Pull Request
Devtest Labs Access, claim, and connect to lab VMs .../main/articles/devtest-labs/tutorial-use-custom-lab.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation page demonstrates a Windows bias in several ways. In the VM connection instructions, Windows (RDP) is mentioned before Linux (SSH/Azure CLI), and the Windows-specific tool (RDP) is called out by name, while Linux options are grouped together. The structure and screenshots focus on portal actions that are most familiar to Windows users, and there is no parity in example depth or tool explanation for Linux users. There are no Linux-specific screenshots or step-by-step instructions, and the flow assumes familiarity with Windows patterns.
Recommendations
  • Present Linux connection options (SSH, Azure CLI) before or alongside Windows (RDP) options, not after.
  • Include Linux-specific screenshots and step-by-step instructions for connecting to Linux VMs.
  • Explicitly mention Linux tools (e.g., SSH clients, Azure CLI) and provide example commands.
  • Balance the depth of instructions and examples for both Windows and Linux users.
  • Avoid assuming Windows as the default; clarify that both OS types are supported and provide equal guidance.
GitHub Create Pull Request
Devtest Labs Use commands to start and stop lab VMs ...t-labs/use-command-line-start-stop-virtual-machines.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell examples first, referencing Windows-specific tools and patterns (such as REM comments and Windows environment variable syntax), and generally prioritizing Windows environments in explanations. While Azure CLI examples are provided for both Bash and Windows, the PowerShell section is more extensive and presented before CLI, reinforcing a Windows-centric approach.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples to avoid prioritizing Windows tools.
  • Expand Bash/Linux-specific instructions and examples to match the detail given to PowerShell/Windows.
  • Remove or minimize Windows-specific syntax (e.g., REM comments, set commands) unless equally balanced with Linux equivalents.
  • Explicitly mention Linux/macOS environments where applicable, including installation and usage notes.
  • Ensure parity in troubleshooting, prerequisites, and environment setup for both Windows and Linux users.
GitHub Create Pull Request
Digital Twins Azure Digital Twins CLI command set ...-docs/blob/main/articles/digital-twins/concepts-cli.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation provides examples and guidance for Bash, PowerShell, and Windows CMD environments. However, Windows-specific shells (PowerShell and CMD) receive equal or greater attention than Bash, with PowerShell mentioned before Bash in some sections and detailed escaping instructions for Windows shells. There is a notable emphasis on Windows tools and patterns, such as PowerShell and CMD, and the CLI version requirements are specifically called out for PowerShell users. Linux-specific shells beyond Bash (e.g., zsh, fish) are not mentioned, and Bash guidance is limited compared to the detailed PowerShell/CMD sections.
Recommendations
  • Add examples and guidance for additional Linux shells (e.g., zsh, fish) to improve parity.
  • Ensure Bash/Linux instructions are presented before or alongside Windows/PowerShell instructions to avoid implicit Windows-first bias.
  • Expand Bash section to include more detailed examples and common pitfalls, matching the depth of PowerShell/CMD guidance.
  • Clarify that CLI version requirements apply to all platforms, not just PowerShell users.
  • Consider adding a summary table comparing shell-specific escaping requirements for quick reference.
GitHub Create Pull Request
Digital Twins Security for Azure Digital Twins solutions .../blob/main/articles/digital-twins/concepts-security.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page demonstrates Windows bias primarily by referencing PowerShell cmdlets (e.g., New-AzRoleAssignment) as the main example for role assignment automation, without providing equivalent Azure CLI or Bash examples. Windows-centric tools and patterns (PowerShell, cmdlet terminology) are mentioned exclusively or before any cross-platform alternatives. There are no explicit Linux or cross-platform command examples for key operations such as role assignment, which may hinder parity for Linux users.
Recommendations
  • Provide Azure CLI (az) examples alongside PowerShell cmdlets for all automation scenarios, especially for role assignment and resource management.
  • Include Bash shell command examples where relevant, to demonstrate cross-platform usage.
  • Explicitly mention that all operations can be performed from Linux/macOS environments using Azure CLI, and link to relevant documentation.
  • Avoid using Windows-specific terminology (e.g., 'cmdlet') as the primary example; instead, use neutral or cross-platform language.
  • Add a section or callout highlighting Linux/macOS compatibility and best practices for those platforms.
GitHub Create Pull Request
Digital Twins Customer personal data requests in Azure Digital Twins ...cles/digital-twins/resources-customer-data-requests.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias by exclusively referencing the Azure portal (a web-based tool often associated with Windows workflows) and omitting command-line examples for Linux users. There are no examples using cross-platform tools such as Azure CLI, nor are there references to Linux shell commands or scripting patterns. The REST API is mentioned, but no practical example is given for Linux environments.
Recommendations
  • Add examples using Azure CLI commands for identifying, exporting, and deleting personal data, which are cross-platform and commonly used on Linux.
  • Provide sample REST API calls using curl or other Linux-native tools to demonstrate how Linux users can interact with Azure Digital Twins.
  • Explicitly mention that the Azure portal is accessible from any OS/browser, but offer parity by including command-line alternatives.
  • Include links to documentation or tutorials for Linux users on managing Azure Digital Twins resources.
GitHub Create Pull Request
Digital Twins Tutorial: Create a graph in Azure Digital Twins (CLI) ...in/articles/digital-twins/tutorial-command-line-cli.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates several forms of Windows bias. Windows tools and patterns (such as Cloud Shell and file upload via GUI) are mentioned first or exclusively, with limited or no Linux-specific guidance. PowerShell is referenced as an alternative shell, but the main instructions and troubleshooting tips focus on Windows environments. There are missing Linux-specific examples for file upload and shell escaping, and the documentation does not provide parity for Linux command-line workflows or tools.
Recommendations
  • Add explicit instructions and screenshots for uploading files to Cloud Shell from Linux environments, including command-line methods (e.g., using SCP, wget, or Azure CLI storage commands).
  • Provide Linux-specific examples for shell escaping, especially for inline JSON and special characters, with clear Bash and Zsh syntax.
  • Mention and demonstrate Linux-native editors (e.g., nano, vim) for editing model files, not just generic 'code editor'.
  • Clarify that Azure CLI is cross-platform and provide troubleshooting tips for common Linux issues (e.g., file permissions, path formats).
  • Balance references to PowerShell and Bash, and ensure that Bash/Linux instructions are given equal prominence and detail.
  • Include a section or callout for Linux users, summarizing any differences or additional steps they may encounter.
GitHub Create Pull Request
DNS Use Azure DNS with other Azure services ...-docs/blob/main/articles/dns/dns-for-azure-services.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias primarily by referencing PowerShell and CLI for VM creation, without mentioning Linux-specific tools or providing Linux-oriented examples. The examples and terminology (e.g., 'PowerShell', 'CLI') are presented in a way that assumes familiarity with Windows-first workflows, and there is a lack of parity in examples or instructions for Linux users.
Recommendations
  • Include explicit examples for Linux users, such as using Azure CLI commands from Bash or shell scripts.
  • Clarify that 'CLI' refers to cross-platform Azure CLI, and provide both Windows (PowerShell) and Linux (Bash) command examples where relevant.
  • Add notes or sections that address Linux VM creation and management, including references to Linux tools and workflows.
  • Avoid mentioning PowerShell exclusively; when referencing VM creation, specify both PowerShell and Bash/CLI alternatives.
  • Ensure that documentation links and tutorials cover both Windows and Linux environments for DNS configuration tasks.
GitHub Create Pull Request
DNS Quickstart: Create an Azure DNS zone and record - Azure Resource Manager template (ARM template) ...ocs/blob/main/articles/dns/dns-get-started-template.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
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 and Windows command prompt (cmd), with no Azure CLI (bash) or Linux shell examples provided. The instructions and screenshots reference Windows tools and workflows first and exclusively, omitting equivalent Linux/macOS steps. This may hinder Linux users or those who prefer cross-platform tools.
Recommendations
  • Add Azure CLI (bash) examples alongside or before PowerShell examples for template deployment and resource group deletion.
  • Include instructions and screenshots for running nslookup from a Linux/macOS terminal (e.g., bash), not just Windows cmd.
  • Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and provide guidance for both environments.
  • Balance references to Windows tools with Linux/macOS equivalents, ensuring parity in steps and screenshots.
  • Consider reordering examples so that cross-platform tools (Azure CLI, Bash) are presented before or alongside Windows-specific tools.
GitHub Create Pull Request
DNS Import and export a domain zone file - Azure CLI ...azure-docs/blob/main/articles/dns/dns-import-export.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing Windows DNS file locations before mentioning Linux/BIND equivalents, providing explicit instructions for using Windows Command Prompt and nslookup, and omitting Linux-specific command examples for verification. The guidance for obtaining zone files and verifying DNS records is Windows-centric, with no parity for Linux shell commands or tools.
Recommendations
  • Present instructions for both Windows and Linux environments in parallel, or alternate which platform is mentioned first.
  • Include Linux shell command examples for verifying DNS records (e.g., using dig or nslookup in bash).
  • Reference Linux/BIND zone file locations and retrieval methods with equal prominence to Windows DNS.
  • Provide explicit examples for Linux users, such as using the terminal to run Azure CLI commands and verify DNS records.
  • Avoid phrases like 'Use Windows Command Prompt' unless also providing the equivalent for Linux/macOS.
GitHub Create Pull Request
DNS Private DNS records overview - Azure Private DNS ...ure-docs/blob/main/articles/dns/dns-private-records.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page shows evidence of Windows bias primarily through references to PowerShell as the default or primary interface for managing Azure DNS features (e.g., Etags, TXT records). Windows tools (PowerShell) are mentioned explicitly, while Linux equivalents (such as Azure CLI or Bash) are not given equal prominence or examples. In sections discussing record management and concurrency (Etags), PowerShell is referenced first and exclusively, with no mention of Linux-native workflows or tools.
Recommendations
  • Provide parallel examples using Azure CLI and Bash scripts alongside PowerShell examples.
  • Explicitly mention cross-platform tools and interfaces (e.g., Azure CLI, REST API) before or alongside Windows-specific tools.
  • Clarify that all features are accessible from Linux and macOS environments, and link to relevant documentation for those platforms.
  • Where PowerShell is referenced, add equivalent Azure CLI commands and usage notes for Linux users.
  • Review and update language to avoid implying PowerShell is the default or only supported method.
GitHub Create Pull Request
DNS Protecting private DNS Zones and Records - Azure DNS ...n/articles/dns/dns-protect-private-zones-recordsets.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation consistently presents Azure PowerShell examples alongside Azure CLI, but PowerShell is always listed first and is referenced as the primary method for several tasks. Some operations (notably record set level resource locks) are only documented for PowerShell, with explicit notes that they are not supported in Azure CLI or the portal. There are no references to Linux-specific tools, shell environments, or considerations for non-Windows users, and no examples using Bash scripting or Linux-native workflows.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present CLI first in some sections to avoid Windows-first bias.
  • Where PowerShell is the only supported method, explicitly acknowledge the limitation and provide guidance for Linux/macOS users (e.g., using PowerShell Core on Linux, or alternatives if available).
  • Add Bash shell scripting examples where possible, especially for Azure CLI commands, to demonstrate Linux-native workflows.
  • Include notes or links for installing and using Azure PowerShell on Linux/macOS, and clarify cross-platform compatibility.
  • If certain features are unavailable in CLI or on Linux, document the roadmap or workarounds for non-Windows users.
GitHub Create Pull Request
DNS Reverse DNS for Azure services - Azure DNS ...ain/articles/dns/dns-reverse-dns-for-azure-services.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by prioritizing Azure PowerShell and classic PowerShell examples, and by using PowerShell-specific terminology and tooling throughout. While Azure CLI examples are provided (which are cross-platform), there are no explicit Linux shell (bash) or native Linux tool examples (such as dig, nslookup, or scripting via bash). The Cloud Services section is exclusively PowerShell-based, with no CLI or Linux-native alternatives. The ordering of examples often places PowerShell first, reinforcing a Windows-centric approach.
Recommendations
  • Add Linux-native command examples (e.g., bash, dig, nslookup) for verifying reverse DNS records.
  • Include explicit instructions for performing tasks on Linux/macOS, such as using Azure CLI in bash/zsh.
  • Reorder examples to present Azure CLI (cross-platform) before PowerShell, or alternate the order.
  • Clarify that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
  • For Cloud Services, investigate and document any possible CLI or REST API alternatives, or explicitly state PowerShell is required.
  • Add troubleshooting and validation steps using Linux tools to ensure parity for non-Windows users.
GitHub Create Pull Request
DNS DNS Zones and Records Overview ...azure-docs/blob/main/articles/dns/dns-zones-records.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page references Azure DNS management via PowerShell and REST API, but does not mention or provide examples for Linux-native tools or workflows (such as Azure CLI, bash, or shell scripting). The only tool-specific mention is PowerShell, which is Windows-centric. There are no Linux-specific examples or parity in tool recommendations, and PowerShell is referenced as the default for Etag handling.
Recommendations
  • Add explicit examples and references for managing Azure DNS using Azure CLI (cross-platform) and bash/shell scripting.
  • When discussing Etags and concurrent changes, mention how Azure CLI and other Linux-friendly tools handle Etags, not just PowerShell.
  • Where PowerShell is referenced, provide equivalent Azure CLI or REST API command examples.
  • Review all tool and workflow mentions to ensure Linux parity and avoid implying PowerShell is the default or only option.
GitHub Create Pull Request
DNS Quickstart - Create an Azure private DNS zone using the Azure CLI ...s/blob/main/articles/dns/private-dns-getstarted-cli.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation exhibits a strong Windows bias in the testing and VM creation sections. Only Windows VM images are used in examples, and all instructions for testing DNS resolution and configuring firewalls use Windows PowerShell commands and Windows-centric output. There are no equivalent Linux VM creation examples, nor instructions for configuring Linux firewalls or testing DNS resolution from Linux VMs.
Recommendations
  • Include Linux VM creation examples using az vm create with a Linux image (e.g., Ubuntu).
  • Provide instructions for configuring Linux firewalls to allow ICMP (e.g., using ufw or iptables).
  • Add Linux-based DNS resolution test examples (e.g., using ping or dig from a bash shell).
  • Show output examples from Linux terminals alongside Windows PowerShell output.
  • Mention Linux as an alternative platform explicitly in the prerequisites and testing sections.
GitHub Create Pull Request
DNS Azure DNS Private Resolver Overview ...lob/main/articles/dns/dns-private-resolver-overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page shows a Windows bias by prioritizing Azure PowerShell (a Windows-centric tool) in its quickstart and next steps, while omitting equivalent Linux/CLI examples. The only automation example mentioned is PowerShell, and there is no reference to Azure CLI or Linux-native DNS tools. This may disadvantage Linux users or those who prefer cross-platform solutions.
Recommendations
  • Add quickstart and setup instructions using Azure CLI, which is cross-platform and widely used on Linux.
  • Include examples for configuring DNS forwarding using Linux-native tools (e.g., dig, resolvectl, systemd-resolved) in addition to Windows DNS Manager and PowerShell.
  • Ensure that automation and scripting examples cover both PowerShell and Bash/CLI workflows.
  • Explicitly mention Linux support and provide parity in guidance for both Windows and Linux administrators.
  • Where PowerShell is referenced, also provide Azure CLI or REST API alternatives.
GitHub Create Pull Request
DNS Protecting DNS Zones and Records - Azure DNS ...blob/main/articles/dns/dns-protect-zones-recordsets.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by consistently presenting Azure PowerShell examples before Azure CLI, and in some cases, only providing PowerShell commands (e.g., record set level resource locks). There are no Linux-specific examples, nor is there mention of Linux-native tools or shell scripting patterns. The reliance on PowerShell (traditionally a Windows tool) and the lack of parity for features in Azure CLI or portal (which are more cross-platform) further reinforce the bias.
Recommendations
  • Ensure all features and scenarios have Azure CLI examples, especially where currently only PowerShell is documented.
  • Explicitly state platform limitations (e.g., if a feature is only available in PowerShell, clarify whether this is due to backend limitations or tooling gaps).
  • Where PowerShell is used, provide equivalent bash/shell scripting examples for Linux users.
  • Highlight cross-platform usage and recommend CLI or REST API approaches where possible.
  • Add notes or guidance for Linux/macOS users, including installation and usage of Azure CLI.
  • Consider reordering examples so that CLI (cross-platform) appears before PowerShell, or present both together.
GitHub Create Pull Request
DNS Tutorial: Create Custom Azure DNS Records For a Web App .../blob/main/articles/dns/dns-web-sites-custom-domain.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell examples are provided for every step, and the 'Test the new records' section uses nslookup with explicit Windows/PowerShell syntax and screenshots. The order of examples consistently lists Portal, PowerShell, and then Azure CLI, placing Windows-centric tools before cross-platform options. There is no mention of Linux-specific tools (e.g., dig) for DNS testing, nor are there any Linux shell-specific instructions or screenshots.
Recommendations
  • Include Linux-native DNS testing tools such as 'dig' alongside 'nslookup', with example commands and expected output.
  • Alternate the order of CLI and PowerShell examples, or present CLI first to emphasize cross-platform parity.
  • Add notes clarifying that Azure CLI works on Windows, Linux, and macOS, and provide guidance for installing/running CLI on Linux.
  • Provide screenshots or terminal examples from Linux environments where relevant.
  • Avoid using Windows-specific paths or prompts (e.g., 'PS C:\>') in generic command examples; use neutral or cross-platform formats.
  • Mention that 'nslookup' is available on Linux, but also suggest 'dig' as a more common alternative.
GitHub Create Pull Request
DNS How to sign your Azure Public DNS zone with DNSSEC ...ocs/azure-docs/blob/main/articles/dns/dnssec-how-to.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page exhibits Windows bias by providing detailed PowerShell examples, using Windows-centric terminology (e.g., dig.exe), and listing PowerShell as a primary method for DNSSEC operations. The CLI and PowerShell tabs are present, but Linux-specific examples, such as bash or native Linux tools, are missing. The use of 'dig.exe' and the absence of explicit Linux command-line examples or instructions further reinforce the Windows-centric approach.
Recommendations
  • Add explicit Linux/Bash examples for all CLI operations, including using native Linux tools (e.g., dig, jq) without Windows-specific extensions.
  • Replace references to 'dig.exe' with platform-neutral 'dig' and clarify usage on both Windows and Linux.
  • Provide instructions for installing required tools on Linux (e.g., dig, jq) and demonstrate commands in a Linux shell context.
  • Ensure parity in example outputs and command syntax for both Windows and Linux environments.
  • Consider adding a dedicated Linux tab or section, or clarify that CLI examples are cross-platform and provide any necessary platform-specific notes.
GitHub Create Pull Request
DNS Overview of DNSSEC - Azure Public DNS ...rosoftDocs/azure-docs/blob/main/articles/dns/dnssec.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation exhibits a Windows bias in several ways: Windows tools (Resolve-DnsName, nslookup.exe) and PowerShell commands are presented first and in more detail, with explicit references to Windows client behavior and Group Policy. Linux tools (dig) are mentioned, but not explained or prioritized, and there are no explicit Linux shell examples or references to Linux DNSSEC validation patterns. The documentation assumes familiarity with Windows environments and omits parity for Linux users.
Recommendations
  • Provide Linux shell examples (e.g., dig, drill, kdig) alongside or before Windows/PowerShell examples.
  • Explicitly mention Linux client/server DNSSEC validation behaviors and configuration (e.g., systemd-resolved, Unbound, BIND).
  • Include instructions for viewing DNSSEC records on Linux and macOS, not just Windows.
  • Balance references to Windows-specific features (Group Policy, NRPT) with Linux equivalents (e.g., resolv.conf, DNSSEC validation options in Unbound/BIND).
  • Avoid presenting Windows tools first; alternate or parallelize examples for both platforms.
  • Clarify that dig is available natively on Linux/macOS and explain installation for Windows if needed.
GitHub Create Pull Request
DNS Quickstart - Create an Azure private DNS zone using the Azure portal ...lob/main/articles/dns/private-dns-getstarted-portal.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ powershell_heavy
Summary
The documentation page demonstrates a Windows bias by exclusively using Windows Server as the example VM OS, providing only Windows-centric instructions (such as RDP and PowerShell), and omitting any Linux VM creation or Linux command-line examples for DNS testing. The 'Test the private zone' section uses PowerShell and Windows ping output, with no mention of Linux alternatives.
Recommendations
  • Include parallel instructions for creating a Linux VM (e.g., Ubuntu) alongside the Windows VM example.
  • Provide Linux-specific steps for connecting to the VM (e.g., SSH instead of RDP) and for running DNS resolution commands (e.g., using 'ping', 'dig', or 'nslookup' in a Linux shell).
  • Show both Windows and Linux command outputs when demonstrating DNS record testing.
  • Mention that the Azure portal workflow is OS-agnostic, but provide explicit parity in examples for both platforms.
  • Where PowerShell is referenced, also show Bash/Azure CLI equivalents for Linux users.
GitHub Create Pull Request
DNS Azure Private DNS: Secure DNS for Virtual Networks ...re-docs/blob/main/articles/dns/private-dns-overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias by listing Azure PowerShell before Azure CLI in the 'Next steps' section, suggesting a Windows-first approach. The emphasis on PowerShell as a primary tool, with no explicit mention of Linux shell or Bash examples, and the lack of references to Linux-specific tools or workflows, further reinforces this bias. There are no examples or guidance tailored for Linux users, and the documentation does not mention cross-platform considerations when discussing tools or usage patterns.
Recommendations
  • Present Azure CLI and PowerShell examples side-by-side, or list Azure CLI first to reflect its cross-platform nature.
  • Explicitly mention that Azure CLI works on Linux, macOS, and Windows, and provide Bash shell examples where appropriate.
  • Include references to Linux-specific DNS tools (e.g., dig, nslookup) when discussing DNS resolution and troubleshooting.
  • Add a section or note highlighting cross-platform support and considerations for both Windows and Linux administrators.
  • Ensure that all instructions and examples are available for both PowerShell and Bash/CLI environments.
GitHub Create Pull Request
DNS Azure Private DNS zone resiliency ...-docs/blob/main/articles/dns/private-dns-resiliency.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias by referencing a PowerShell-based guide ('private-dns-getstarted-powershell.md') as the primary next step for creating a Private DNS zone, without mentioning or linking to Linux/CLI equivalents. No Linux or cross-platform examples or tools are provided, and the PowerShell approach is presented first and exclusively.
Recommendations
  • Include links to Azure CLI and/or Bash-based guides for creating Private DNS zones alongside the PowerShell guide.
  • Explicitly mention that management tasks can be performed on Linux, macOS, and Windows, and provide examples for each platform.
  • Ensure that examples and walkthroughs are available for both Windows (PowerShell) and Linux/macOS (CLI/Bash) users.
  • Review and update related documentation to maintain parity between Windows and Linux instructions.
GitHub Create Pull Request
DNS Create and manage reverse DNS zones in Azure Private DNS ...ure-docs/blob/main/articles/dns/private-reverse-dns.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias in its example for testing DNS resolution, showing only a Windows command prompt and PowerShell output (nslookup) without providing equivalent Linux/macOS instructions or screenshots. There is no mention of Linux tools (such as dig or host), nor are Linux command-line examples or screenshots included. The documentation assumes a Windows environment for verification steps.
Recommendations
  • Include Linux/macOS equivalents for DNS resolution testing, such as examples using 'dig' and 'host' commands.
  • Provide screenshots or sample outputs from Linux terminals alongside Windows examples.
  • Explicitly mention that the verification steps can be performed on both Windows and Linux VMs, and provide instructions for each.
  • Avoid presenting Windows commands and screenshots first or exclusively; strive for parity by showing both platforms together or alternating.
  • Reference cross-platform tools and patterns where possible, and clarify any platform-specific differences.
GitHub Create Pull Request
DNS Tutorial - Set up DNS failover using private resolvers ...articles/dns/tutorial-dns-private-resolver-failover.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates Windows bias by providing only Windows Server and PowerShell examples for DNS forwarding configuration, referencing Windows-specific tools (DNS console, PowerShell), and omitting equivalent Linux/BIND instructions. The main configuration steps are described using Windows terminology and tools, with no mention of how to perform these tasks on Linux-based DNS servers or with common Linux utilities.
Recommendations
  • Add step-by-step instructions for configuring conditional forwarders on Linux-based DNS servers (e.g., BIND/named.conf).
  • Include Linux command-line examples (such as editing /etc/bind/named.conf.options and using systemctl to reload BIND) alongside Windows PowerShell commands.
  • Reference Linux tools (e.g., dig, systemctl, named-checkconf) in verification and troubleshooting steps, not just nslookup and Windows DNS console.
  • Explicitly state that the procedure applies to both Windows and Linux environments, and provide links to official documentation for both platforms.
  • Present Windows and Linux examples in parallel, or alternate which platform is shown first to avoid 'windows_first' bias.
GitHub Create Pull Request
Energy Data Services Tutorial: Use sdutil to load data into Seismic Store ...s/energy-data-services/tutorial-seismic-ddms-sdutil.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation exhibits a Windows bias by listing Windows prerequisites and instructions before Linux/Mac equivalents, referencing Windows-specific tools (Microsoft C++ Build Tools, WSL), and providing activation commands and package manager instructions with a Windows-first approach. Some installation steps and environment setup details are more explicit for Windows users, while Linux/Mac instructions are less detailed or mentioned as alternatives. There are also references to using WSL for Ubuntu on Windows, but no equivalent guidance for native Linux users. The usage examples and testing sections use generic Bash commands, but overall, the initial setup and configuration favor Windows environments.
Recommendations
  • Present Linux and Mac instructions before or alongside Windows instructions, not after.
  • Provide equally detailed installation steps for Linux and Mac, including C++ build tools and package manager commands.
  • Avoid referencing Windows Subsystem for Linux (WSL) as the primary Linux environment; provide native Linux instructions.
  • Include explicit Linux/Mac equivalents for all Windows-specific commands (e.g., activating virtualenv, installing dependencies).
  • Ensure all examples and troubleshooting notes are platform-neutral or include both Windows and Linux/Mac variants.
  • Add troubleshooting and FAQ sections for Linux/Mac users, not just Windows.
  • Review and update tool references to ensure parity (e.g., mention gcc/g++ for Linux instead of only Microsoft C++ Build Tools).
GitHub Create Pull Request
Event Grid Configure IP firewall for Azure Event Grid topics or domains ...cs/blob/main/articles/event-grid/configure-firewall.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for configuring IP firewall rules for Azure Event Grid topics or domains. However, there is a notable emphasis on PowerShell, a Windows-centric tool, with a dedicated section and multiple examples. The documentation also refers to PowerShell-specific syntax and patterns, and does not mention or provide examples for Bash, Linux shell scripting, or other Linux-native tools. The PowerShell section appears after the CLI section, but the CLI examples are generic and do not address Linux-specific usage or considerations. There is no explicit Linux bias, and the CLI commands are cross-platform, but the presence of PowerShell examples and terminology may make the documentation feel more Windows-oriented.
Recommendations
  • Add explicit Bash/Linux shell examples alongside Azure CLI commands, including variable assignment and command chaining typical in Linux environments.
  • Clarify that Azure CLI commands are cross-platform and provide notes or examples for Linux/macOS users (e.g., differences in environment variable syntax).
  • Consider mentioning or linking to Linux-specific troubleshooting or scripting resources.
  • Balance PowerShell examples with equivalent Bash or shell script examples to ensure parity for Linux users.
  • Avoid using Windows-specific terminology (e.g., PowerShell) without providing Linux alternatives.
GitHub Create Pull Request
Event Grid Configure custom Azure Policies on Event Grid resources to enhance you security posture ...ent-grid/custom-azure-policies-for-security-control.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation references running CLI or PowerShell commands to find property aliases, but does not provide explicit examples for either platform. However, by mentioning PowerShell alongside CLI (which is often interpreted as Azure CLI, available cross-platform), there is a subtle Windows-first bias, as PowerShell is traditionally associated with Windows. No Linux-specific tools or shell examples (e.g., bash) are provided, and there is no explicit parity in instructions for Linux users.
Recommendations
  • Provide explicit Azure CLI command examples, as Azure CLI is cross-platform and preferred by many Linux users.
  • If PowerShell examples are given, also provide equivalent bash or shell script examples for Linux.
  • Clarify that Azure CLI works on Windows, Linux, and macOS, and link to installation instructions for all platforms.
  • Avoid mentioning PowerShell before CLI unless both are given equal prominence and examples.
  • Add a section or note for Linux/macOS users to ensure they are equally supported in the documentation.
GitHub Create Pull Request
Event Grid Webhooks as event handlers for Azure Event Grid events ...docs/blob/main/articles/event-grid/handler-webhooks.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by consistently listing PowerShell examples alongside Azure CLI and Portal, and by referencing Microsoft Teams and Azure Automation runbooks, which are more commonly used in Windows-centric environments. PowerShell is mentioned as a primary automation tool, and Windows tools/patterns (such as Azure Automation and Teams integration) are highlighted without equivalent Linux-native alternatives or examples. Linux-specific tools, shell scripts, or automation patterns are not mentioned or demonstrated.
Recommendations
  • Add Linux shell (bash) examples for all quickstarts and tutorials, especially for webhook creation and event handling.
  • Include references to Linux-native automation tools (e.g., cron jobs, systemd services, or Ansible playbooks) as possible event handlers via webhooks.
  • Provide parity in examples by listing CLI/bash examples before or alongside PowerShell, rather than always including PowerShell.
  • Mention Linux-compatible notification tools (e.g., Slack, Mattermost, or email via sendmail) in addition to Microsoft Teams.
  • Clarify that Azure Automation runbooks can be authored and triggered from Linux environments, and provide examples if possible.
GitHub Create Pull Request
Event Grid Publish events with event domains with Azure Event Grid .../blob/main/articles/event-grid/how-to-event-domains.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides both Azure CLI and PowerShell examples for all major operations, but PowerShell (a Windows-centric tool) is given equal prominence and detail as Azure CLI. There are no explicit Linux shell (bash/curl) examples for publishing events, nor are Linux-specific tools or patterns mentioned. The documentation does not show how to use native Linux utilities (e.g., curl, wget) to POST events, and PowerShell is presented as a first-class option throughout, which may imply a Windows bias.
Recommendations
  • Add explicit bash/curl examples for publishing events to the Event Grid domain endpoint, showing how to POST JSON using standard Linux tools.
  • Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows, while PowerShell is primarily a Windows tool (though it is available cross-platform).
  • Where HTTP requests are required, provide both PowerShell and bash/curl examples side-by-side.
  • Consider listing Azure CLI examples before PowerShell, or note that CLI is platform-neutral.
  • Add troubleshooting notes or tips for Linux users, such as installing Azure CLI or using curl for REST API calls.
GitHub Create Pull Request
Event Grid Tutorial: Send Event Hubs data to data warehouse - Event Grid ...lob/main/articles/event-grid/event-hubs-integration.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ visual_studio_only ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates a Windows bias by exclusively using Visual Studio for publishing the Azure Functions app and running the sample projects, with no mention of cross-platform alternatives like VS Code or CLI-based deployment. The prerequisites and instructions assume a Windows development environment, and there are no examples or guidance for Linux or macOS users for building, publishing, or running the sample code.
Recommendations
  • Include instructions for publishing the Azure Functions app using cross-platform tools such as Azure CLI, Azure Functions Core Tools, or Visual Studio Code.
  • Add guidance for building and running the sample projects on Linux and macOS, including .NET CLI commands and any required dependencies.
  • Update prerequisites to mention cross-platform development environments and tools, not just Visual Studio.
  • Provide alternative steps for users who do not use Visual Studio, such as using VS Code or command-line tools for .NET and Azure Functions.
  • Ensure screenshots and walkthroughs are not exclusively from Windows environments; include examples from Linux/macOS where applicable.
GitHub Create Pull Request
Event Grid Quickstart: Publish on an MQTT topic by using the CLI .../articles/event-grid/mqtt-publish-and-subscribe-cli.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates Windows bias in several ways: certificate generation instructions and examples are provided only for Windows (using Command Prompt and Powershell), with no equivalent Linux or macOS shell commands. The sample code section references Visual Studio and NuGet package installation in a Windows-centric manner, without mentioning cross-platform alternatives. The initial instructions for certificate creation mention 'Consider installing manually for Windows' and direct users to open a Command Prompt, but do not provide Linux or macOS guidance. No Linux shell or OpenSSL examples are given for certificate creation, and the .NET sample code is presented with Windows tooling in mind.
Recommendations
  • Provide equivalent certificate generation instructions and examples for Linux and macOS, using bash and OpenSSL or step CLI in a Unix shell.
  • Include cross-platform guidance for running the sample code, such as using VS Code, JetBrains Rider, or .NET CLI, and mention NuGet installation via dotnet CLI.
  • Add explicit instructions for Linux/macOS users on where to run commands and how to locate certificate files.
  • Ensure all CLI commands and code samples are presented in a platform-neutral way, or provide parallel examples for each major OS.
  • Avoid referencing Windows-specific shortcuts (e.g., Win+R) without alternatives for other platforms.
GitHub Create Pull Request
Event Grid Publish and subscribe on an MQTT topic using portal ...ticles/event-grid/mqtt-publish-and-subscribe-portal.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates a Windows bias in the certificate generation section, where instructions and examples are tailored for Windows users (e.g., opening a command prompt in %USERPROFILE% and using PowerShell commands), with no equivalent Linux or macOS instructions provided. The phrase 'Consider installing manually for Windows' implies a Windows-first approach, and there are no Bash or Linux terminal examples for certificate generation. The rest of the guide is platform-neutral, focusing on Azure Portal and MQTTX app, which are cross-platform.
Recommendations
  • Add explicit instructions and command examples for Linux and macOS users, including how to open a terminal and navigate to the appropriate directory.
  • Provide Bash shell equivalents for all certificate generation commands, including file path conventions and environment variables (e.g., $HOME instead of %USERPROFILE%).
  • Clarify that the step CLI is cross-platform and link to installation guides for Linux and macOS.
  • Avoid using Windows-specific terminology (such as 'Win+R') without providing cross-platform alternatives.
  • Where screenshots or instructions are OS-specific, include alternatives for other platforms.
GitHub Create Pull Request
Event Grid Azure PowerShell - Secure WebHook delivery with Microsoft Entra Application in Azure Event Grid ...powershell-webhook-secure-delivery-microsoft-entra-app.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation is heavily biased towards Windows, as it exclusively provides PowerShell examples and references PowerShell modules (e.g., Microsoft.Graph.PowerShell). There are no Linux or cross-platform CLI examples, and the instructions assume the use of Windows tools and patterns. The use of PowerShell and Microsoft-specific tooling is presented as the default and only option, with no mention of alternatives such as Azure CLI, REST API, or scripting in Bash.
Recommendations
  • Provide equivalent examples using Azure CLI and Bash, which are cross-platform and commonly used on Linux.
  • Include instructions for performing the same tasks using REST API calls, which are platform-agnostic.
  • Explicitly mention that PowerShell Core is available on Linux and macOS, and clarify compatibility if PowerShell is required.
  • Add notes or sections for Linux users, including installation and usage of necessary tools.
  • Reorder or supplement examples so that cross-platform approaches are presented alongside or before Windows-specific methods.
GitHub Create Pull Request
Event Grid Secure WebHook delivery with Microsoft Entra ID ...ob/main/articles/event-grid/secure-webhook-delivery.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a strong Windows bias by exclusively using PowerShell scripts and the Azure Portal (which is Windows-centric) for configuration steps. All code examples and referenced scripts are in PowerShell, with no Bash, Linux shell, or cross-platform alternatives provided. The instructions repeatedly direct users to use the Azure Shell in PowerShell mode, and there is no mention of Linux-native tools or workflows. The use of Windows tools and patterns is pervasive, and Linux users are left without guidance for equivalent steps.
Recommendations
  • Provide equivalent Bash or Azure CLI scripts for all PowerShell examples, ensuring Linux users can follow along without switching environments.
  • Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and show how to select Bash for Linux users.
  • Add step-by-step instructions for configuring Microsoft Entra ID and Event Grid subscriptions using Linux-native tools and workflows.
  • Reference cross-platform SDKs (e.g., Python, Node.js) for automation, and provide sample code in those languages.
  • Ensure that all referenced scripts (currently PowerShell-only) have Linux shell or Azure CLI equivalents, and link to them.
  • Review diagrams and screenshots to ensure they do not reinforce a Windows-only workflow.
GitHub Create Pull Request
Event Grid Publish Events to Azure Event Grid Custom Topics .../blob/main/articles/event-grid/post-to-custom-topic.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation consistently presents Azure PowerShell (a Windows-centric tool) examples alongside Azure CLI, and references Azure portal and Cloud Shell (which defaults to PowerShell for many users). PowerShell examples are given equal prominence to CLI, and Windows tools/patterns (PowerShell, Azure portal) are mentioned before or alongside Linux-friendly equivalents. There is a slight Windows-first bias in the ordering and tool selection, but Linux parity is present via Azure CLI and Bash examples.
Recommendations
  • Explicitly mention that Azure CLI and Bash examples work natively on Linux/macOS and in WSL environments.
  • Provide a clear separation between PowerShell and Bash/CLI examples, and consider listing Bash/CLI first to reduce perceived Windows-first bias.
  • Add a note clarifying that Azure PowerShell is available cross-platform, but Bash/CLI is the default on Linux.
  • Include troubleshooting tips or notes for Linux users (e.g., curl installation, date formatting differences).
  • Ensure screenshots and instructions for Azure portal/Cloud Shell show both Bash and PowerShell session options, with Bash as default for Linux users.
GitHub Create Pull Request
Event Grid Send events to webhooks hosted in private destinations ...vent-grid/send-events-webhooks-private-destinations.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by providing command-line examples using Windows-style paths and executables (e.g., .\azbridge.exe), referencing .NET/C# code samples exclusively, and omitting explicit Linux or cross-platform examples for key steps. Windows tools and patterns (such as .NET SDK and Windows executable invocation) are mentioned before or instead of Linux equivalents, and there is no mention of Linux-specific commands or shell usage.
Recommendations
  • Provide equivalent Linux shell commands and examples (e.g., using ./azbridge or Docker invocation).
  • Include code samples in additional languages (such as Python, Node.js) to demonstrate cross-platform implementation.
  • Clarify that Azure Relay Bridge can be run on Linux and show Docker-based usage explicitly.
  • Add instructions for installing and running Azure Relay Bridge on Linux, including permissions and executable usage.
  • Mention Linux-friendly tools and patterns (such as bash scripts, systemd services) where appropriate.
  • Ensure that examples and instructions do not assume Windows paths or conventions by default.
GitHub Create Pull Request
Event Grid Subscribe to Microsoft Graph Events Using Azure Event Grid ...n/articles/event-grid/subscribe-to-graph-api-events.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. It references Windows-specific tools (PowerShell, Azure CLI, and commands like 'az account list-locations'), and includes PowerShell as a primary example language. There is an implicit prioritization of Windows development environments, with no explicit mention of Linux equivalents for certain steps (e.g., obtaining Azure region names, setting up development environments, or running CLI commands on Linux/macOS). Additionally, the sample code and setup instructions do not clarify cross-platform compatibility, and there is no guidance for Linux users regarding prerequisites, environment setup, or alternative tools.
Recommendations
  • Explicitly state that Azure CLI and all code samples can be run on Linux/macOS as well as Windows, and provide installation/setup instructions for Linux environments.
  • Include Linux/macOS-specific examples or notes for commands like 'az account list-locations', clarifying shell usage and potential differences.
  • Add guidance for setting up development environments on Linux, including authentication, SDK installation, and any OS-specific considerations.
  • Ensure that PowerShell examples are accompanied by Bash or shell script equivalents where relevant, or clarify that PowerShell Core is cross-platform.
  • Review referenced samples and documentation links to ensure Linux parity and highlight any OS-specific steps or requirements.
GitHub Create Pull Request
Event Hubs Dynamically add partitions to an event hub in Azure Event Hubs ...main/articles/event-hubs/dynamically-add-partitions.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page demonstrates Windows bias by presenting PowerShell as the first method for updating partition count, using a Windows-specific tool (Set-AzEventHub), and referencing the old .NET SDK (WindowsAzure.ServiceBus) which is primarily Windows-focused. Although Azure CLI and Apache Kafka CLI examples are included, the ordering and emphasis favor Windows tools and patterns, with no explicit Linux shell or bash examples provided.
Recommendations
  • Reorder the update methods to present cross-platform tools (Azure CLI, Kafka CLI) before Windows-specific tools (PowerShell).
  • Add explicit bash/shell examples for Linux users, especially for Azure CLI and Kafka CLI commands.
  • Mention that Azure CLI and Kafka CLI are cross-platform and provide installation links for Linux/macOS.
  • Reference .NET Core SDKs or other cross-platform libraries instead of (or in addition to) the Windows-only .NET SDK.
  • Clarify that PowerShell Core is available on Linux/macOS, or provide equivalent bash scripts where possible.
GitHub Create Pull Request
Event Hubs SAS Authentication for Azure Event Hubs Resources ...les/event-hubs/authenticate-shared-access-signature.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation provides code examples for SAS token generation in multiple languages, including PowerShell and Bash. However, PowerShell (a Windows-centric tool) is given a full example and is listed before Bash, and the Bash example requires non-standard tools (jq, iconv) without guidance for Linux users. There is a strong presence of Windows-specific tooling (PowerShell, .NET, C#) and references to Windows patterns (HttpUtility, System.Web), while Linux-native approaches (Bash, openssl) are less detailed and may be harder for Linux users to follow. The ARM template and portal instructions are platform-neutral, but the overall example set and ordering show a Windows-first bias.
Recommendations
  • Provide Linux-native command-line examples (e.g., Bash) with clear instructions and alternatives for required tools (like jq, iconv), or use only POSIX-standard utilities.
  • List Bash examples before PowerShell to avoid implicit prioritization of Windows tools.
  • Add explicit notes on cross-platform compatibility for each code sample, especially for PowerShell and Bash.
  • Include more Linux-friendly programming language examples (e.g., Python) and clarify any platform-specific dependencies.
  • Where .NET or C# examples use Windows-specific libraries (e.g., System.Web), provide alternatives for Linux/Mono environments.
GitHub Create Pull Request
Event Hubs Azure Event Hubs Dedicated Tier Overview ...n/articles/event-hubs/event-hubs-dedicated-overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates subtle Windows bias in its operational instructions. For example, the 'Determine the cluster type' section provides a command-line example using nslookup with a Windows-style namespace (ns.servicebus.windows.net) and does not mention Linux equivalents or syntax. The instructions reference PowerShell as a tool for checking Azure Resource Manager properties, listing it alongside Azure CLI and the portal, but do not provide Linux-specific guidance or examples. No Linux shell commands (e.g., dig, host) are mentioned, and Windows-centric terminology (servicebus.windows.net) is used without clarifying cross-platform applicability.
Recommendations
  • Add Linux shell command equivalents (e.g., dig, host) alongside nslookup for cluster type determination.
  • Provide explicit Azure CLI examples for resource property checks, and clarify that PowerShell is optional for Windows users.
  • Use neutral terminology for namespaces and endpoints, or clarify that servicebus.windows.net is platform-agnostic.
  • Ensure all operational instructions and examples are presented for both Windows and Linux environments, or indicate platform-specific steps where necessary.
GitHub Create Pull Request
Event Hubs Management libraries - Azure Event Hubs| Microsoft Docs ...articles/event-hubs/event-hubs-management-libraries.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by focusing exclusively on .NET and C# code samples, referencing Windows-centric tools and workflows (such as PowerShell and Azure Portal tutorials before CLI), and omitting Linux-specific examples or cross-platform alternatives. The prerequisites and sample code are tailored to Windows environments, with no mention of Linux or other platforms, and the management library showcased is only available for .NET, which is traditionally Windows-focused.
Recommendations
  • Include equivalent examples using cross-platform languages (e.g., Python, Java) and SDKs where available.
  • Provide Linux-specific instructions for authentication and environment setup, such as using Azure CLI or bash scripts.
  • Reference Azure CLI tutorials before or alongside PowerShell and Portal instructions to ensure parity.
  • Clarify platform compatibility for the management libraries and suggest alternatives for non-Windows users.
  • Add notes or sections explicitly addressing Linux/macOS usage, including sample code and troubleshooting tips.
GitHub Create Pull Request
Event Hubs Quickstart: Create an Azure event hub with consumer group ...ubs/event-hubs-resource-manager-namespace-event-hub.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing Azure PowerShell examples for deploying, validating, and cleaning up Event Hub resources. There are no Azure CLI or Bash examples, which are more common on Linux and macOS. The instructions and code blocks assume the use of PowerShell, which is native to Windows, and do not mention or prioritize cross-platform alternatives. References to Azure CLI are only present in the link section, not in the main workflow.
Recommendations
  • Add equivalent Azure CLI examples for all deployment, validation, and cleanup steps, using Bash syntax.
  • Explicitly mention that Azure Cloud Shell supports both PowerShell and Bash, and provide instructions for both.
  • Reorder or parallelize examples so that CLI/Bash instructions appear alongside PowerShell, rather than only after or not at all.
  • Ensure that tool references and screenshots are platform-neutral or include both Windows and Linux/macOS variants.
  • Review and update language to avoid implying PowerShell is the default or only supported method.
GitHub Create Pull Request
Expressroute Azure ExpressRoute FastPath: Features, availability, and limitations ...docs/blob/main/articles/expressroute/about-fastpath.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias by only providing configuration instructions for the Azure portal and Azure PowerShell, with no mention of Azure CLI or Linux-based configuration examples. The 'Next steps' section lists PowerShell before any other tool, and there are no references to Linux-specific tools or workflows, nor are cross-platform alternatives (such as Azure CLI) presented.
Recommendations
  • Add configuration instructions using Azure CLI, which is cross-platform and widely used on Linux and macOS.
  • Ensure that examples and walkthroughs include both PowerShell and Azure CLI commands, presented side-by-side or in parallel sections.
  • Explicitly mention Linux/macOS compatibility in prerequisites and configuration steps.
  • Where possible, provide bash script examples for automation alongside PowerShell scripts.
  • Review and update links to reference both Windows and Linux documentation resources.
GitHub Create Pull Request
Event Hubs Test Applications Locally with the Azure Event Hubs Emulator ...les/event-hubs/test-locally-with-event-hub-emulator.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits Windows bias by presenting Windows-specific instructions (PowerShell, WSL) before Linux/macOS equivalents, referencing Windows tools (WSL, Docker Desktop for Windows) and providing more detailed step-by-step guidance for Windows users. Linux/macOS instructions are less detailed and lack parity in example commands and troubleshooting notes. Additionally, file path conventions and environment setup tips are Windows-centric.
Recommendations
  • Provide equally detailed step-by-step instructions for Linux and macOS, including terminal commands and troubleshooting tips.
  • Include explicit Linux/macOS examples for cloning repositories, navigating directories, and running scripts.
  • Mention Linux-native Docker installation and usage before or alongside Windows-specific instructions.
  • Add notes on Linux/macOS file path conventions and environment variable usage.
  • Balance the order of presentation so that Linux/macOS instructions are not always secondary to Windows.
  • Avoid referencing Windows tools (WSL, PowerShell) in generic sections; move them to OS-specific tabs or subsections.
  • Ensure all examples (e.g., running scripts, configuring Docker) are shown for both Windows and Linux/macOS.
GitHub Create Pull Request
Event Hubs Configure Transport Layer Security (TLS) for an Event Hubs client application ...s/transport-layer-security-configure-client-version.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates bias towards Windows environments by providing only .NET (typically Windows-centric) code samples, referencing Fiddler (a Windows-only tool) for TLS verification, and omitting any Linux-specific instructions, tools, or code examples. There are no examples for Linux platforms, nor are cross-platform or Linux-native tools mentioned for verifying TLS connections.
Recommendations
  • Add examples for configuring TLS in client applications running on Linux, such as using Python, Java, or .NET Core on Linux.
  • Include instructions for verifying TLS connections using cross-platform or Linux-native tools like tcpdump, Wireshark, or OpenSSL.
  • Mention platform-specific considerations for TLS support, such as differences in .NET Framework vs .NET Core/Mono on Linux.
  • Present verification tools in parallel (e.g., 'On Windows, use Fiddler; on Linux, use Wireshark or OpenSSL') rather than referencing only Windows tools.
  • Ensure that code samples and instructions are clearly marked as platform-specific where applicable, and provide parity for major platforms.
GitHub Create Pull Request
Event Hubs Troubleshoot connectivity issues - Azure Event Hubs | Microsoft Docs ...blob/main/articles/event-hubs/troubleshooting-guide.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias by prioritizing Windows-specific tools (e.g., psping.exe), referencing PowerShell/Windows CLI usage, and not providing equivalent Linux commands or examples. Windows tools are mentioned first and in detail, while Linux alternatives are only briefly referenced or omitted.
Recommendations
  • Provide explicit Linux command examples for connectivity checks, such as using 'nc', 'telnet', or 'ss' for port testing.
  • Include installation instructions and usage for Linux-native tools alongside Windows tools (e.g., show how to use 'nc <hostname> <port>' or 'timeout 1 bash -c "echo > /dev/tcp/<hostname>/<port>"').
  • List cross-platform tools (e.g., Wireshark) with platform-specific installation notes.
  • When referencing CLI, clarify if commands work on both Windows and Linux, and provide syntax for both where they differ.
  • Avoid mentioning Windows tools first; present Windows and Linux options side-by-side to ensure parity.
GitHub Create Pull Request
Expressroute Configure customer-controlled maintenance for your virtual network gateway ...xpressroute/customer-controlled-gateway-maintenance.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by exclusively providing PowerShell-based examples and instructions for command-line configuration, with no mention of Linux-native tools or CLI alternatives. The Azure portal and PowerShell are presented as the only supported methods, and PowerShell is referenced before any Linux-compatible options (such as Azure CLI or Bash scripting). There are no examples or guidance for users on Linux or macOS platforms.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, showing how to perform the same configuration from Linux/macOS terminals.
  • Explicitly mention cross-platform support and clarify which steps can be performed from non-Windows environments.
  • Include Bash script samples or references to REST API usage for advanced users on Linux.
  • Reorder sections or provide parallel instructions so that Linux-compatible methods (Azure CLI, Bash) are not secondary to PowerShell.
  • Note any limitations or differences in functionality between PowerShell and Azure CLI, if applicable.
GitHub Create Pull Request
Expressroute About Azure ExpressRoute Direct ...n/articles/expressroute/expressroute-erdirect-about.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page provides onboarding instructions for Azure ExpressRoute Direct using only Azure PowerShell commands, with no mention of equivalent Azure CLI or Bash commands. This approach assumes users are on Windows or using PowerShell, which may disadvantage Linux and macOS users. The onboarding section presents Windows-centric tooling first and exclusively, without Linux parity.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all onboarding and configuration steps.
  • Explicitly mention that both PowerShell and CLI are supported, and link to cross-platform installation guides.
  • Where possible, provide Bash script examples or note any platform-specific differences.
  • Review other sections for Windows-centric terminology or tools and ensure Linux equivalents are referenced.
GitHub Create Pull Request
Expressroute Configure a virtual network gateway for ExpressRoute using the Azure portal ...expressroute-howto-add-gateway-portal-resource-manager.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias by prioritizing Azure portal and PowerShell instructions, with no mention of Linux-specific tools or CLI examples. The only command-line instructions referenced are PowerShell-based, and there are no Azure CLI or Bash examples, nor any guidance for Linux users. The navigation and examples assume a Windows-centric workflow, omitting Linux parity.
Recommendations
  • Add Azure CLI examples for all major tasks (gateway creation, configuration, SKU upgrade, deletion) alongside PowerShell and portal instructions.
  • Explicitly mention that Azure CLI is cross-platform and provide Bash shell usage examples.
  • Ensure that navigation tabs or selectors include 'Azure CLI' or 'Linux/Bash' options, not just 'PowerShell'.
  • Reference Linux-specific considerations where relevant (e.g., differences in shell environments, authentication methods).
  • Review screenshots and instructions to ensure they are not exclusively Windows/PowerShell oriented.
GitHub Create Pull Request
Expressroute Link a virtual network to ExpressRoute circuits - Azure portal ...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/expressroute/expressroute-howto-linkvnet-portal-resource-manager.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by listing PowerShell examples and links before Azure CLI, and by referencing PowerShell (classic) as a primary method. There are no explicit Linux-specific instructions, nor are Linux command-line tools or patterns mentioned. The Azure portal and PowerShell are emphasized, which are traditionally more Windows-centric, while Azure CLI (which is cross-platform and preferred on Linux) is listed after PowerShell and not discussed in detail. No Linux shell (bash) examples or Linux-specific troubleshooting steps are provided.
Recommendations
  • Provide explicit Linux/bash examples alongside PowerShell, especially for command-line operations.
  • List Azure CLI instructions before or alongside PowerShell to emphasize cross-platform parity.
  • Reference Linux tools and patterns (e.g., using bash, scripting, or Linux-native troubleshooting) where relevant.
  • Clarify that Azure CLI is cross-platform and suitable for Linux and macOS users.
  • Include screenshots or walkthroughs from Linux environments where possible.
  • Add troubleshooting or configuration notes specific to Linux users (e.g., authentication, environment setup).
GitHub Create Pull Request
Expressroute Azure ExpressRoute: Configure Global Reach ...es/expressroute/expressroute-howto-set-global-reach.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation exclusively uses Azure PowerShell for all configuration, verification, and management steps, with no mention of Azure CLI, Bash, or cross-platform alternatives. All examples and instructions assume the use of PowerShell, which is traditionally associated with Windows environments. There is no guidance for Linux or macOS users, nor are there references to platform-neutral tools or workflows.
Recommendations
  • Add equivalent Azure CLI examples for all configuration, verification, and management steps.
  • Include guidance for running Azure CLI or PowerShell Core on Linux and macOS, highlighting cross-platform compatibility.
  • Mention Azure Cloud Shell as a platform-neutral option and provide both PowerShell and Bash/CLI instructions.
  • Explicitly state that the procedures can be performed on Linux and macOS, not just Windows, and link to relevant setup guides.
  • Where possible, use generic terminology (e.g., 'command line' or 'shell') rather than assuming PowerShell as the default.
GitHub Create Pull Request
Firewall Deploy and configure Enterprise CA certificates for Azure Firewall Premium .../firewall/premium-deploy-certificates-enterprise-ca.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation is heavily oriented toward Windows environments, specifically Active Directory and Windows Server tools. All certificate management steps rely on Windows-only utilities (certtmpl.msc, Internet Explorer, Windows Certificate Export Wizard), and there are no Linux or cross-platform alternatives provided. The prerequisites assume an Active Directory Forest and AD CS, which are Windows-centric. No guidance is given for Linux/macOS users or for using open-source PKI solutions.
Recommendations
  • Add instructions for generating and managing certificates using open-source PKI tools (e.g., OpenSSL, EJBCA) on Linux/macOS.
  • Provide examples for certificate requests and exports using command-line tools available on Linux (e.g., openssl, certtool).
  • Clarify whether Azure Firewall Premium supports certificates from non-AD CS sources and document the process for those.
  • Include screenshots and walkthroughs for Linux/macOS environments where applicable.
  • Reorder examples so that platform-neutral or Linux/macOS methods appear before or alongside Windows-specific instructions.
GitHub Create Pull Request
Hdinsight Apache Hadoop & Visual Studio Data Lake Tools - Azure HDInsight ...adoop/apache-hadoop-visual-studio-tools-get-started.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation is heavily focused on using Data Lake Tools for Visual Studio, a Windows-only IDE, for interacting with Azure HDInsight and running Hive queries. All instructions, screenshots, and workflows assume the user is on Windows and using Visual Studio, with no mention of Linux/macOS alternatives or equivalent tools. There are no examples or guidance for Linux users, and Windows tools are presented exclusively and first.
Recommendations
  • Add sections describing how to connect to HDInsight clusters and run Hive queries from Linux/macOS using cross-platform tools (e.g., VS Code, command-line Hive, Beeline, Jupyter, or web-based interfaces).
  • Provide equivalent examples for Linux/macOS users, such as using SSH, CLI tools, or browser-based Azure portal workflows.
  • Explicitly state the platform limitations of Data Lake Tools for Visual Studio and link to Linux/macOS alternatives.
  • Reorganize documentation to mention cross-platform options before or alongside Windows-specific instructions.
GitHub Create Pull Request
Hdinsight Customize Azure HDInsight cluster configurations using bootstrap ...nsight/hdinsight-hadoop-customize-cluster-bootstrap.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page is heavily biased towards Windows and PowerShell. All code samples and detailed walkthroughs use Azure PowerShell, a Windows-centric tool. There are no equivalent examples for Linux/macOS users (e.g., Bash/CLI), and PowerShell is presented as the primary method for customization, with .NET and ARM templates mentioned only briefly. The appendix provides a full PowerShell script, but there is no Linux shell or Azure CLI alternative. References to Linux customization are relegated to 'See also' links, not integrated into the main content.
Recommendations
  • Add equivalent Azure CLI (Bash) examples for all PowerShell code snippets.
  • Provide step-by-step instructions for customizing HDInsight clusters using Linux/macOS tools.
  • Include sample shell scripts for cluster configuration and verification.
  • Present Windows and Linux methods side-by-side or in parallel sections.
  • Explicitly mention cross-platform compatibility and differences where relevant.
GitHub Create Pull Request
Automanage Azure Quickstart SDK for Java ...e-docs/blob/main/articles/automanage/quick-java-sdk.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing only the Windows VM quick-create documentation in the prerequisites and omitting any mention or example of Linux virtual machines. There are no Linux-specific instructions, links, or examples, which may lead users to assume the SDK is primarily or exclusively for Windows VMs.
Recommendations
  • Include links to both Windows and Linux VM quick-create documentation in the prerequisites.
  • Explicitly state that the SDK supports both Windows and Linux VMs, if applicable.
  • Provide example usage or notes for Linux VMs, highlighting any differences in configuration or prerequisites.
  • Ensure that terminology and instructions are platform-neutral unless a step is genuinely platform-specific.
GitHub Create Pull Request
API Center Enable API Center portal view - Azure API Center - VS Code extension ...i-center/enable-api-center-portal-vs-code-extension.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows-first bias by exclusively referencing Visual Studio Code (VS Code) and its extensions, which are cross-platform but are often associated with Windows workflows. All instructions and screenshots are tailored to VS Code usage, with no mention of Linux-specific tools, terminal commands, or alternative editors. Keyboard shortcuts and troubleshooting steps are presented in a way that assumes a Windows environment (e.g., Ctrl+Shift+P), and there are no examples or guidance for Linux users or those using non-Microsoft authentication methods.
Recommendations
  • Explicitly mention that VS Code and its extensions are available on Linux and macOS, and provide links or instructions for installation on those platforms.
  • Include Linux-specific keyboard shortcuts (e.g., Ctrl+Shift+P is the same, but clarify if there are differences) and note any platform-specific UI differences.
  • Add troubleshooting steps relevant to Linux environments, such as checking environment variables, file permissions, or network configurations.
  • Provide examples or guidance for using the Azure API Center from the command line (e.g., Azure CLI) or alternative editors (such as Vim or Emacs) where possible.
  • Clarify that Microsoft Entra ID and Azure RBAC are platform-agnostic, and provide links to documentation for configuring these on Linux.
GitHub Create Pull Request
API Center Include file .../includes/configure-managed-identity-kv-secret-user.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both Bash and PowerShell examples for Azure CLI commands, but PowerShell examples are given immediately after Bash in every case, and the PowerShell formatting is explicitly called out. This may signal a slight Windows bias, as Linux shell usage is treated as the default but Windows/PowerShell is always included and highlighted. There are no Linux-specific tools or patterns mentioned, but the parity is reasonable.
Recommendations
  • Clarify in the introduction that both Bash (Linux/macOS) and PowerShell (Windows) examples are provided for cross-platform users.
  • Consider alternating the order of examples, or grouping them under explicit OS tabs (e.g., 'Linux/macOS', 'Windows') for clarity.
  • Ensure that any OS-specific nuances (such as environment variable handling or path formats) are explained for both platforms.
  • If possible, provide guidance for users of WSL (Windows Subsystem for Linux) or other cross-platform environments.
GitHub Create Pull Request
App Service Configure Sign in with Apple (Preview) ...app-service/configure-authentication-provider-apple.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing Azure PowerShell and Azure CLI management experiences before mentioning their limitations, and by providing only a C#/.NET example for JWT signing using Microsoft.IdentityModel.Tokens. There are no Linux-specific or cross-platform command-line examples, nor are alternative JWT signing methods (such as using OpenSSL, Python, or Node.js) provided. The documentation does not mention Linux tools or workflows, and does not offer parity for developers working outside the Windows/.NET ecosystem.
Recommendations
  • Add Linux-friendly examples for generating and signing JWTs, such as using OpenSSL, Python (PyJWT), or Node.js (jsonwebtoken).
  • Include CLI commands that work on both Windows and Linux, or explicitly mention platform differences.
  • Reference Linux management tools or workflows where appropriate, such as Bash scripts or Linux text editors for handling the .p8 file.
  • Provide parity in code samples by including at least one non-.NET example for JWT creation and signing.
  • Clarify any platform-specific limitations or requirements, and suggest alternatives for Linux users.
GitHub Create Pull Request
Bastion Quickstart: Deploy Azure Bastion to a virtual network using an ARM template .../main/articles/bastion/quickstart-host-arm-template.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias primarily in the 'Next steps' section, where only Windows VM creation and Windows RDP connection guides are linked. There are no Linux VM or SSH connection examples or references, and the workflow assumes Windows usage patterns. No Linux-specific instructions, tools, or parity are provided throughout the page.
Recommendations
  • Add links to Linux VM quickstart guides alongside Windows VM guides in the 'Next steps' section.
  • Include instructions or references for connecting to Linux VMs via SSH using Azure Bastion.
  • Provide example ARM template parameters and usage for both Windows and Linux VM scenarios.
  • Ensure parity in screenshots and walkthroughs by showing both Windows and Linux VM resource validation and connection steps.
GitHub Create Pull Request
App Service Prerequisites ...cludes/tutorial-microsoft-graph-as-app/introduction.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both PowerShell and Azure CLI examples for granting Microsoft Graph permissions, but PowerShell is presented first and in greater detail, which may indicate a Windows-first and PowerShell-heavy bias. There are no explicit Linux shell (bash) examples or references to Linux-specific tools or workflows, and the initial mention of Visual Studio (a Windows-centric IDE) further reinforces the Windows-first approach.
Recommendations
  • Present Azure CLI (cross-platform) examples before PowerShell, or side-by-side, to avoid implying a Windows-first workflow.
  • Add bash-specific examples and clarify that Azure CLI commands work on Linux, macOS, and Windows.
  • Mention cross-platform IDEs (e.g., VS Code) alongside Visual Studio when discussing publishing/deployment.
  • Explicitly state that the steps and tools are applicable to both Windows and Linux environments.
  • Include troubleshooting notes or tips for Linux users where workflows may differ.
GitHub Create Pull Request
App Service Set Up Azure Arc for App Service, Functions, and Logic Apps .../articles/app-service/manage-create-arc-environment.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for all major steps, but consistently lists PowerShell examples immediately after Bash, giving them equal prominence. However, there is a subtle Windows bias: PowerShell is featured as the only alternative to Bash, with no mention of Linux-native shells other than Bash (e.g., zsh, fish), nor any explicit Linux-specific instructions or troubleshooting. Additionally, some command explanations and environment variable conventions (e.g., use of $variable vs. $variableName) are tailored to PowerShell, which is primarily a Windows tool, though available on Linux. There are no examples using Linux-specific tools or patterns, and no troubleshooting or notes for Linux-specific scenarios (e.g., file permissions, package managers).
Recommendations
  • Add explicit notes or troubleshooting steps for Linux environments, such as file permissions, package installation, or differences in CLI behavior.
  • Include examples for other popular Linux shells (e.g., zsh, fish) or clarify that Bash instructions apply to all POSIX-compliant shells.
  • Mention Linux package managers (apt, yum, etc.) for installing prerequisites like Azure CLI and kubectl.
  • Clarify that PowerShell is available on Linux, but Bash is the default shell for most Linux distributions.
  • Provide guidance for users working in native Linux environments, such as handling environment variables, file paths, and permissions.
  • Consider adding a 'Linux-specific considerations' section to address common issues faced by Linux users.
GitHub Create Pull Request
App Service Create an App Service app using an Azure Resource Manager template ...b/main/articles/app-service/quickstart-arm-template.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation uses a zone pivot system to separate Windows, Linux, and Windows container instructions, providing parity in examples and template links for each platform. However, there is mild Windows bias: the Windows pivot appears first in every section, and references to deployment methods mention Azure PowerShell (a Windows-centric tool) before Linux alternatives. The template review and deployment instructions are well-matched for both platforms, but the overall structure and ordering favor Windows.
Recommendations
  • Rotate or randomize the order of platform pivots so Linux is not always listed after Windows.
  • When listing deployment methods, mention cross-platform tools (Azure CLI, REST API) before Windows-specific tools like Azure PowerShell.
  • Ensure that any referenced samples, screenshots, or next steps are equally available for Linux and Windows, and that Linux examples are not less detailed.
  • Consider adding a brief note at the top clarifying that all platforms are equally supported and that instructions are available for both.
GitHub Create Pull Request
Communication Services include file ...ices/quickstarts/includes/manage-teams-identity-net.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation mentions Windows-specific console environments (cmd, PowerShell) before Bash, and does not provide any Linux-specific instructions, examples, or troubleshooting notes. All commands and code are platform-neutral, but the setup and run instructions implicitly assume a Windows environment by listing Windows shells first and omitting Linux-specific context.
Recommendations
  • List Bash (Linux/macOS) before or alongside cmd/PowerShell when referencing console windows.
  • Explicitly mention that all commands work on Linux/macOS as well as Windows.
  • Add notes or examples for common Linux/macOS workflows, such as using Terminal, setting environment variables, and installing .NET SDK on Linux.
  • Include troubleshooting tips for Linux users, e.g., permissions, path issues, or package installation differences.
  • Ensure parity in instructions for opening and editing files (e.g., suggest 'nano', 'vim', or 'gedit' for Linux users).
GitHub Create Pull Request
Automanage Automanage Configuration profiles ...articles/automanage/overview-configuration-profiles.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page discusses Azure Automanage configuration profiles in a general way but shows subtle Windows bias. It references Microsoft Antimalware (a Windows-centric solution) as the default example for customizing profiles, and does not provide any Linux-specific examples or mention Linux tools. The links to further documentation list 'Automanage for Linux' after 'Automanage for Windows Server', and the only concrete example (antimalware) is Windows-specific. No Linux command-line or configuration examples are present.
Recommendations
  • Include Linux-specific examples when discussing customization, such as referencing Linux security tools (e.g., ClamAV) alongside Microsoft Antimalware.
  • Alternate the order of links or mention Linux and Windows equivalently when listing further reading or supported platforms.
  • Provide examples or notes on how configuration profiles differ for Linux machines, including any unique services or settings.
  • Explicitly state parity or differences between Windows and Linux support in Automanage profiles to help users understand platform-specific considerations.
GitHub Create Pull Request
Automanage Azure Quickstart SDK for JavaScript .../blob/main/articles/automanage/quick-javascript-sdk.md
Medium Priority View Details →
Reviewed by: LLM Analysis
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 VM quick-create portal in the prerequisites, without mentioning or providing equivalent instructions or links for Linux virtual machines. There are no Linux-specific examples or references, and the documentation implicitly assumes the user is working with Windows VMs.
Recommendations
  • Include links to both Windows and Linux VM quick-create documentation in the prerequisites.
  • Clarify that Automanage supports both Windows and Linux VMs, if applicable.
  • Provide examples or notes for enabling Automanage on Linux VMs, including any differences in configuration or supported features.
  • Ensure terminology and instructions are platform-neutral unless a feature is Windows-specific, in which case explicitly state so.
GitHub Create Pull Request
Automanage Azure Automanage Machine Best Practices ...articles/automanage/virtual-machines-best-practices.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias by referencing Windows-specific features (such as Windows security baselines) without mentioning Linux equivalents, and by omitting Linux-specific examples or guidance throughout. The guest configuration section only discusses Windows baselines, and there is no mention of Linux security baselines or configuration management. No Linux-specific tools, patterns, or examples are provided, and the documentation implicitly assumes a Windows-centric environment.
Recommendations
  • Include information about Linux security baselines and how guest configuration applies to Linux VMs.
  • Provide examples or guidance for both Windows and Linux environments, especially in sections discussing configuration, monitoring, and compliance.
  • Mention Linux-specific tools or patterns where relevant (e.g., OS update management, security hardening).
  • Clarify which services and features are supported for Linux VMs and highlight any differences in implementation or configuration.
  • Add links to Linux documentation or best practices where appropriate.
GitHub Create Pull Request
Automanage About Azure Automanage Machine Best Practices ...e-docs/blob/main/articles/automanage/overview-about.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page generally maintains platform neutrality in its descriptions, but there is a subtle Windows bias: Windows Server is mentioned before Linux in lists and links, and there are no concrete examples or walkthroughs for Linux users (e.g., onboarding steps, configuration, or screenshots). The page references both platforms but does not provide Linux-specific examples or parity in guidance.
Recommendations
  • Alternate the order of Windows and Linux mentions to avoid implicit prioritization (e.g., list Linux before Windows in some sections).
  • Provide concrete onboarding/configuration examples for both Windows and Linux, including screenshots or command-line instructions relevant to each platform.
  • Ensure that any referenced tools or services (such as Azure Update Management) include notes or links about Linux compatibility and usage.
  • Add a section or callout specifically addressing Linux users, highlighting any differences or considerations unique to Linux environments.
GitHub Create Pull Request
Automanage Azure Quickstart SDK for Go ...ure-docs/blob/main/articles/automanage/quick-go-sdk.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias by linking only to the Windows VM quick-create guide in the prerequisites, without mentioning or providing a Linux VM equivalent. There are no Linux-specific instructions or examples, and the documentation implicitly assumes Windows as the default platform for virtual machines.
Recommendations
  • Include links to both Windows and Linux VM quick-create guides in the prerequisites section.
  • Clarify that Automanage can be used with both Windows and Linux VMs, if applicable.
  • Provide examples or notes for Linux VM scenarios where relevant.
  • Ensure terminology and instructions are platform-neutral unless a feature is Windows-only.
GitHub Create Pull Request
Automanage Azure Quickstart SDK for Python ...docs/blob/main/articles/automanage/quick-python-sdk.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias by referencing only Windows virtual machines in the prerequisites and linking exclusively to Windows VM creation guides. There are no examples or guidance for Linux VMs, nor are Linux-specific considerations mentioned, despite Azure Automanage supporting both Windows and Linux VMs.
Recommendations
  • Include links to both Windows and Linux VM creation guides in the prerequisites section.
  • Explicitly state that the steps apply to both Windows and Linux VMs, or note any differences if applicable.
  • Provide examples or notes for Linux VM users, such as OS-specific configuration profile options or troubleshooting tips.
  • Ensure parity in documentation references and examples for both platforms to avoid implicit bias.
GitHub Create Pull Request
Azure App Configuration Export settings from App Configuration with Azure Pipelines .../azure-app-configuration/azure-pipeline-export-task.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides only a PowerShell example for consuming exported key-values, without offering a Linux shell (e.g., Bash) equivalent. This may unintentionally signal a preference for Windows environments and PowerShell usage, while omitting guidance for users running pipelines on Linux agents.
Recommendations
  • Add equivalent Bash (or sh) examples for accessing environment variables in subsequent tasks, e.g., `echo "$myBuildSetting"`.
  • Explicitly mention that the export task works on both Windows and Linux agents, and clarify any platform-specific considerations if present.
  • Where screenshots or UI instructions are platform-neutral, consider adding notes or images for Linux agent setup if relevant.
  • Review troubleshooting and FAQ sections for any implicit Windows assumptions and provide Linux alternatives where appropriate.
GitHub Create Pull Request
Azure App Configuration Tutorial for using Azure App Configuration dynamic configuration in an Azure Functions app ...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/enable-dynamic-configuration-azure-functions-csharp.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS (bash), and references Visual Studio and Windows-specific tooling (e.g., setx, F5, firewall exception) without offering equivalent Linux development workflows or tooling guidance. PowerShell and Windows command prompt examples are given more prominence and detail than bash equivalents.
Recommendations
  • Present Linux/macOS (bash) instructions before or alongside Windows examples, not after.
  • Include equivalent Linux development workflows, such as using VS Code, Azure Functions Core Tools CLI, or other cross-platform editors, and describe how to run and debug functions on Linux.
  • Mention Linux-specific considerations (e.g., permissions, shell differences) where relevant.
  • Avoid language that assumes Visual Studio or Windows as the default development environment; reference cross-platform tools and editors.
  • Ensure all command-line examples are provided for bash/zsh/fish as well as Windows shells, with equal detail and troubleshooting guidance.
GitHub Create Pull Request
Azure App Configuration Roll out features to targeted audiences in a Node.js app ...-app-configuration/howto-targetingfilter-javascript.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page demonstrates a Windows bias in the section about setting environment variables. Windows Command Prompt and PowerShell instructions are presented before Linux/macOS equivalents, and both Windows shells are given dedicated examples. No other Windows-specific tools or patterns are present, and the main Node.js/Express workflow is cross-platform.
Recommendations
  • Present Linux/macOS environment variable instructions before Windows/PowerShell, or group all OS instructions together for parity.
  • Consider using a table or side-by-side layout to show environment variable commands for all platforms equally.
  • Explicitly state that the Node.js/Express workflow is cross-platform and works on Windows, Linux, and macOS.
  • Avoid giving Windows-specific instructions more prominence than Linux/macOS unless there is a technical reason.
GitHub Create Pull Request
Azure App Configuration Enable telemetry for feature flags in a Python application ...cles/azure-app-configuration/howto-telemetry-python.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation demonstrates a mild Windows bias in the 'Build and run the app' section, where Windows (cmd) and PowerShell commands for setting environment variables are presented before the Linux/macOS equivalent. The inclusion of both Windows and Linux/macOS commands is positive, but the ordering prioritizes Windows environments. There are no exclusive Windows tools or missing Linux examples elsewhere in the page.
Recommendations
  • Present environment variable commands for Linux/macOS and Windows side-by-side or in parallel sections, rather than listing Windows first.
  • Consider using tabbed or collapsible sections for platform-specific instructions to avoid implicit prioritization.
  • Explicitly state that all platforms are supported and provide equal visibility to Linux/macOS instructions.
  • Review other documentation pages for similar ordering and update to ensure Linux parity.
GitHub Create Pull Request
Azure App Configuration Use dynamic configuration using push refresh - Java Spring ...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/enable-dynamic-configuration-java-spring-push-refresh.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS (bash), and includes explicit PowerShell and Windows command prompt examples. While Linux/macOS instructions are present, Windows tooling and patterns are mentioned first, and Windows command-line examples are more detailed (e.g., restart prompt note). There are no Linux-specific tools or patterns highlighted, and the overall flow assumes familiarity with Windows environments.
Recommendations
  • Present Linux/macOS and Windows instructions in parallel or start with Linux/macOS to avoid implicit prioritization.
  • Add notes about differences in environment variable persistence between shells (e.g., setx vs export), and clarify that Linux/macOS changes are session-scoped unless added to shell profiles.
  • Include Linux/macOS-specific troubleshooting tips or common patterns (e.g., using systemd for environment variables, or .env files).
  • Ensure that all command examples (curl, Maven, etc.) are shown in both Windows and Linux/macOS contexts where relevant.
  • Mention cross-platform editors and tools (e.g., IntelliJ IDEA, Eclipse) alongside Visual Studio Code.
  • Review images and screenshots to ensure they are not Windows-centric (e.g., Azure Portal screenshots should not show Windows-only features).
GitHub Create Pull Request
Azure App Configuration Create an Azure App Configuration store using Bicep ...n/articles/azure-app-configuration/quickstart-bicep.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment, resource review, and cleanup. However, PowerShell examples are given equal prominence to CLI, and PowerShell is a Windows-centric tool. There is no mention of Linux-specific shell environments (e.g., Bash), nor are there notes about running PowerShell on Linux or macOS. The ordering of examples does not consistently prioritize cross-platform tools (CLI) over Windows-centric ones (PowerShell).
Recommendations
  • Explicitly state that Azure CLI is cross-platform and preferred for Linux/macOS users, while PowerShell is primarily for Windows.
  • List Azure CLI examples before PowerShell examples to reinforce CLI as the default, cross-platform choice.
  • Add notes or tabs for Bash or other Linux-native shells if relevant.
  • Mention that PowerShell Core is available on Linux/macOS, if PowerShell usage is necessary.
  • Ensure all instructions and examples work seamlessly on Linux, and highlight any platform-specific considerations.
GitHub Create Pull Request
Azure App Configuration Quickstart for using chat completion configuration in a .NET app ...app-configuration/quickstart-chat-completion-dotnet.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page demonstrates mild Windows bias in the 'Build and run the app' section, where Windows command prompt and PowerShell instructions are listed before Linux/macOS equivalents. PowerShell and Windows-specific commands are explicitly called out, while Linux/macOS instructions are present but appear after Windows examples. No Linux-specific tools or patterns are discussed elsewhere, but the .NET CLI commands and code samples themselves are cross-platform.
Recommendations
  • Present environment variable instructions in a platform-neutral order (e.g., group Windows, macOS, and Linux together or list Linux/macOS first in some cases).
  • Explicitly state that all .NET CLI commands and code samples work on Windows, Linux, and macOS.
  • Consider providing more parity in troubleshooting or configuration steps for Linux/macOS (e.g., mention common shell environments, permissions, or differences in environment variable persistence).
  • Avoid using terms like 'If you use Windows...' first; instead, use 'On Windows...', 'On macOS...', 'On Linux...' in parallel bullet points.
  • Add a note clarifying that Azure App Configuration and Azure OpenAI SDKs are supported cross-platform.
GitHub Create Pull Request
Azure App Configuration Quickstart for Azure App Configuration with .NET | Microsoft Docs .../azure-app-configuration/quickstart-dotnet-core-app.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides environment variable setting instructions for Windows (cmd and PowerShell) before Linux/macOS (bash), and includes explicit PowerShell examples. However, Linux/macOS instructions are present and the .NET CLI is emphasized as cross-platform. No major Windows-only tools or patterns are used, and Linux parity is generally maintained.
Recommendations
  • Present environment variable instructions for all platforms in parallel or grouped by OS, rather than listing Windows first.
  • Consider listing Linux/macOS commands before Windows, or in a neutral order, to avoid implicit prioritization.
  • Add notes clarifying that all .NET CLI commands work identically on Linux/macOS.
  • Where PowerShell is mentioned, clarify its availability on Linux/macOS, or provide bash equivalents if relevant.
  • Ensure screenshots and terminal output examples reflect cross-platform usage, not just Windows terminals.
GitHub Create Pull Request
Azure App Configuration Quickstart for adding feature flags to Python with Azure App Configuration ...re-app-configuration/quickstart-feature-flag-python.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation demonstrates a mild Windows bias in the section about setting environment variables. Windows Command Prompt and PowerShell instructions are listed before macOS and Linux, and PowerShell is given its own tab. The Windows instructions are more detailed, including validation steps, while Linux/macOS instructions are more succinct. No Linux-specific tools or patterns are mentioned elsewhere, but the environment variable setup section prioritizes Windows.
Recommendations
  • Present OS instructions in a neutral or alphabetical order (e.g., Linux, macOS, Windows) rather than Windows-first.
  • Ensure parity in detail and validation steps for Linux/macOS instructions, matching those given for Windows.
  • Consider combining macOS and Linux instructions if they are identical, and avoid giving Windows multiple tabs unless justified.
  • Explicitly state that the instructions apply equally to all platforms, and provide troubleshooting tips for Linux/macOS users where relevant.
GitHub Create Pull Request
Azure Cache For Redis Azure Cache for Redis Event Grid Overview ...ain/articles/azure-cache-for-redis/cache-event-grid.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page lists PowerShell as a primary method for interacting with Azure Cache for Redis events, both in the quickstart table and in the 'Next steps' section. PowerShell is a Windows-centric tool, and its mention before Linux-native alternatives (such as Bash or shell scripting) suggests a Windows-first bias. There are no explicit Linux-specific examples or references to Linux tools, though Azure CLI (cross-platform) is included.
Recommendations
  • Add explicit Linux/Bash examples and quickstarts, such as using Bash scripts or Linux shell environments to interact with Azure Event Grid and Azure Cache for Redis.
  • Ensure parity in documentation by providing step-by-step instructions for Linux users, including installation and usage of Azure CLI on Linux.
  • Reorder examples so that cross-platform tools (like Azure CLI) are listed before Windows-specific tools (like PowerShell), or group them together with clear platform indications.
  • Include a note clarifying platform compatibility for each tool, and link to Linux-specific guidance where relevant.
GitHub Create Pull Request
DNS Import and export a domain zone file - Azure portal ...ocs/blob/main/articles/dns/dns-import-export-portal.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a mild Windows bias by mentioning Windows DNS and its zone file location before mentioning BIND (the most common Linux DNS server). The Windows DNS path is given in detail, while the BIND section is brief and less explicit. No Linux command-line examples or tools (such as dig, named, or shell commands) are provided for obtaining zone files, whereas the Windows DNS console and file path are described. There are no PowerShell examples, but Windows-centric patterns are referenced first.
Recommendations
  • Present Linux/BIND instructions before or alongside Windows DNS instructions when describing how to obtain zone files.
  • Provide explicit Linux/BIND file path examples (e.g., /etc/bind/zones or /var/named) and mention how to locate them using named.conf.
  • Include Linux shell command examples for exporting or viewing zone files (e.g., cat, less, or named-compilezone).
  • Add references to common Linux DNS tools and workflows to balance the documentation.
  • Ensure parity in troubleshooting notes (e.g., error messages or file handling) for both Windows and Linux environments.
GitHub Create Pull Request
DNS Tutorial: Host your domain in Azure DNS ...lob/main/articles/dns/dns-delegate-domain-azure-dns.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides command-line verification instructions using nslookup, referencing a 'command prompt' without specifying platform. This implicitly assumes Windows, as 'command prompt' is a Windows term, and nslookup is available on both platforms but no Linux-specific context (e.g., 'terminal', 'dig' command) is given. There are no Linux or macOS examples, nor are alternative tools or instructions for those platforms mentioned.
Recommendations
  • Include Linux/macOS terminology (e.g., 'terminal') alongside 'command prompt'.
  • Provide equivalent verification examples using the 'dig' command, which is commonly used on Linux/macOS.
  • Explicitly state that nslookup is available on multiple platforms, and provide installation instructions if needed.
  • Add a note or section for Linux/macOS users, ensuring parity in instructions and tool recommendations.
GitHub Create Pull Request
DNS Tutorial: Create an alias record to refer to a resource record in a zone ...azure-docs/blob/main/articles/dns/tutorial-alias-rr.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates a Windows bias by providing only Windows-centric instructions for testing DNS records (using nslookup from 'a command prompt'), without mentioning Linux or cross-platform alternatives. No Linux-specific tools or terminal commands are referenced, and the example assumes a Windows environment for verification steps.
Recommendations
  • Include Linux-specific instructions for testing DNS records, such as using 'dig' or 'host' commands.
  • Clarify that 'nslookup' is available on both Windows and Linux, and provide example commands for both platforms.
  • Replace references to 'command prompt' with 'terminal or command prompt', or specify steps for both Windows and Linux environments.
  • Add screenshots or terminal output examples from Linux systems to demonstrate parity.
  • Mention cross-platform DNS testing tools and provide guidance for macOS users as well.
GitHub Create Pull Request
DNS Quickstart: Create an Azure DNS Private Resolver - Azure Resource Manager template (ARM template) ...icles/dns/dns-private-resolver-get-started-template.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying the ARM template, but the PowerShell example is given equal prominence and is presented immediately after the CLI example. There is no explicit Linux shell (bash) example, nor is there any mention of Linux-specific tools or patterns. The validation steps are exclusively portal-based and do not reference cross-platform command-line validation.
Recommendations
  • Add explicit bash shell examples alongside Azure CLI and PowerShell, demonstrating deployment from a Linux/macOS environment.
  • Clarify that Azure CLI commands work cross-platform (Windows, Linux, macOS) and consider making CLI the default or first example.
  • Include validation steps using Azure CLI or REST API to verify deployment, not just portal screenshots.
  • Avoid presenting PowerShell as the only or primary alternative to CLI; mention other cross-platform automation options.
GitHub Create Pull Request
DNS What is a virtual network link subresource of Azure DNS private zones ...main/articles/dns/private-dns-virtual-network-links.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page demonstrates a mild Windows bias by listing Azure PowerShell before Azure CLI in the 'Next steps' section and referencing PowerShell as a primary method for creating private DNS zones. This ordering can imply a preference for Windows-centric tooling, as PowerShell is traditionally associated with Windows environments, while Azure CLI is cross-platform and more commonly used on Linux and macOS.
Recommendations
  • List Azure CLI before Azure PowerShell in examples and 'Next steps' to signal cross-platform parity.
  • Explicitly mention that both Azure CLI and PowerShell are available on Windows, Linux, and macOS, and provide links to installation guides for each platform.
  • Include example commands for both Azure CLI and PowerShell side-by-side in relevant sections to ensure equal visibility.
  • Add a note clarifying that users can choose either tool based on their operating system and preference.
GitHub Create Pull Request
Frontdoor Troubleshoot common issues ...cs/blob/main/articles/frontdoor/troubleshoot-issues.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation references Windows-specific tools (Fiddler) and browser developer tools for troubleshooting, with no mention of Linux/macOS alternatives. The only explicit command-line example given is for OpenSSL, which is cross-platform, but troubleshooting steps and tool recommendations are otherwise Windows-centric. Linux/macOS users may need to infer or substitute their own tools, creating friction.
Recommendations
  • Include Linux/macOS equivalents for troubleshooting tools (e.g., suggest curl, wget, tcpdump, Wireshark, or browser dev tools available on all platforms).
  • When mentioning Fiddler, also mention cross-platform alternatives such as mitmproxy or Wireshark.
  • Provide example commands for both Windows (PowerShell, Fiddler) and Linux/macOS (curl, openssl, etc.) where relevant.
  • Clarify that browser developer tools are available on all major platforms.
  • Add troubleshooting steps using Linux-native tools for HTTP header inspection and SSL verification.
GitHub Create Pull Request
Azure Resource Manager Create Bicep files - Visual Studio ...ger/bicep/quickstart-create-bicep-use-visual-studio.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page focuses on using Visual Studio, a Windows-centric IDE, and lists Visual Studio as the primary tool for Bicep file creation. While it mentions Visual Studio Code as an alternative, the main instructions and screenshots are for Visual Studio. In deployment and cleanup sections, both Azure CLI (cross-platform) and Azure PowerShell (Windows-preferred) examples are provided, but PowerShell is given equal prominence. There are no Linux-specific instructions, nor is there mention of Linux-native editors or workflows beyond a brief link to Visual Studio Code.
Recommendations
  • Add explicit instructions and screenshots for Visual Studio Code, which is cross-platform, or link to a Linux-specific quickstart.
  • Include a note about platform compatibility for Visual Studio and Visual Studio Code, clarifying that Visual Studio is Windows-only while VS Code runs on Linux and macOS.
  • Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and more commonly used on Linux.
  • Mention Linux-native editors (e.g., Vim, Emacs) and how Bicep files can be authored and deployed from Linux environments.
  • Provide troubleshooting tips for Linux users, such as installing the Bicep CLI and using it with Azure CLI.
GitHub Create Pull Request
Azure Resource Manager Create multiple resource instances in Bicep ...icles/azure-resource-manager/bicep/quickstart-loops.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying and cleaning up Bicep resources. However, PowerShell (a Windows-centric tool) is given equal prominence as Azure CLI, and Visual Studio Code is the only editor mentioned for Bicep development. There is no explicit mention of Linux-specific tools, shell environments, or editor alternatives. The examples and instructions do not reference Linux shell patterns (e.g., bash, zsh), nor do they address platform-specific nuances for Linux users.
Recommendations
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide bash/zsh syntax for variable assignment (e.g., resourceGroupName="value") instead of PowerShell-style ($resourceGroupName).
  • Include instructions or examples for deploying Bicep files using bash or other Linux-native shells, clarifying any differences in command syntax or environment setup.
  • List alternative editors for Bicep development, such as Vim, Emacs, or JetBrains IDEs, and note their cross-platform availability.
  • Add a note or section addressing Linux/macOS users, including any prerequisites or installation steps that differ from Windows.
  • Ensure that CLI examples precede PowerShell examples, or clarify that CLI is cross-platform while PowerShell is primarily Windows-focused.
GitHub Create Pull Request
Azure Resource Manager Use Bicep to create and publish an Azure Managed Application definition ...nager/managed-applications/publish-bicep-definition.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for all major steps, but consistently lists PowerShell (a Windows-centric tool) first in each tabbed example section. The narrative also refers to opening a PowerShell terminal in Visual Studio Code before mentioning Bash, and explains PowerShell-specific features (like splatting) in detail, while not providing equivalent context for Bash/Linux users. There are no explicit Linux-only tools or patterns mentioned, and the CLI examples are present and correct, but the ordering and extra detail for PowerShell suggest a subtle Windows bias.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or default to CLI first, as CLI is cross-platform.
  • Provide equivalent contextual explanations for Bash/Linux users (e.g., line continuation, variable usage), not just PowerShell splatting.
  • Explicitly state that all commands work on Windows, macOS, and Linux, and clarify any platform-specific differences.
  • Include guidance for using native Linux terminals (e.g., GNOME Terminal, xterm) in addition to Visual Studio Code.
  • Where possible, add notes about using the Azure CLI in Windows Command Prompt, PowerShell, and Linux shells to reinforce parity.
GitHub Create Pull Request
Azure Resource Manager Manage Azure resources by using Azure CLI ...re-resource-manager/management/manage-resources-cli.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page primarily uses Azure CLI examples, which are cross-platform. However, there is evidence of Windows bias in the 'Deploy a template' section, where the link for creating ARM templates with Visual Studio Code explicitly references PowerShell tabs and does not mention Linux or Bash alternatives. There are no explicit Linux-specific instructions or examples, and the documentation does not clarify that all CLI examples work equally well on Linux/macOS. The page also lacks references to Linux tools or shell patterns, and does not provide parity for Linux users in the linked resources.
Recommendations
  • Ensure that linked tutorials (such as the Visual Studio Code ARM template quickstart) include Bash/Linux tabs and examples, not just PowerShell.
  • Explicitly state that Azure CLI commands work on Windows, Linux, and macOS, and mention any platform-specific considerations if relevant.
  • Where scripts are shown, clarify that they are POSIX shell compatible and will work in Bash on Linux/macOS.
  • Add references to Linux-native tools or editors (such as VS Code on Linux, nano, vim) where appropriate.
  • Review all linked resources for similar bias and update them to provide Linux parity.
GitHub Create Pull Request
Azure Resource Manager Handling special cases when moving virtual machines to resource group or subscription .../move-limitations/virtual-machines-move-limitations.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for all command-line operations, but PowerShell is mentioned explicitly and frequently, sometimes with more detail (e.g., accepting Marketplace terms). The use of PowerShell is prominent, and the documentation references it alongside Azure CLI and ARM templates, but does not mention Linux-specific tools or shell patterns (such as Bash scripting or Linux-native command usage). There is a slight ordering bias, with PowerShell often listed before or alongside CLI, and no explicit Linux-first guidance or examples.
Recommendations
  • Add explicit Bash shell scripting examples for Linux users, especially for multi-step operations.
  • Clarify that Azure CLI commands work cross-platform and highlight Linux usage where appropriate.
  • Ensure that PowerShell and CLI examples are presented in a neutral order or alternate which comes first.
  • Add notes or links for Linux users about prerequisites (e.g., installing Azure CLI on Linux, using Bash variables).
  • Consider including examples using ARM templates or REST API calls, which are platform-neutral.
GitHub Create Pull Request
Azure Resource Manager Understand the structure and syntax of ARM templates ...in/articles/azure-resource-manager/templates/syntax.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits mild Windows bias. In sections discussing JSON schema selection and deployment tooling, Windows-centric editors (Visual Studio, Visual Studio Code) are mentioned first or exclusively, with no mention of Linux alternatives. Deployment instructions reference Azure PowerShell and Azure CLI, but PowerShell is listed first and there are no explicit Linux shell examples. There are no references to Linux-native editors (e.g., Vim, Emacs, nano) or Linux-specific deployment patterns. No Windows-only tools are used, but the ordering and omission of Linux examples suggest a subtle preference for Windows environments.
Recommendations
  • Mention Linux-native editors (e.g., Vim, Emacs, nano) alongside Visual Studio and VS Code when discussing editing ARM templates.
  • Provide explicit Linux shell examples (e.g., bash commands) for deploying templates, especially when referencing Azure CLI.
  • Clarify that Azure CLI is cross-platform and provide usage examples for both Windows (cmd/PowerShell) and Linux (bash/zsh).
  • When listing deployment tools, avoid always listing PowerShell first; alternate or group by platform.
  • Add notes or links for Linux users regarding installation and usage of Azure CLI and editors.
GitHub Create Pull Request
Azure Vmware Enable VMware Cloud Director service with Azure VMware Solution .../articles/azure-vmware/enable-vmware-cds-with-azure.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page exclusively references Azure VMs and configuration steps via the Azure portal, with all verification and connectivity examples using Azure VMs. There are no examples or instructions for Linux-based VMs, nor any mention of Linux-specific tools or command-line patterns (e.g., SSH, Linux networking commands). The workflow assumes Windows/Azure environments and omits parity for Linux users.
Recommendations
  • Include examples for both Windows and Linux VMs when verifying connectivity (e.g., using SSH and ping from a Linux VM).
  • Add instructions for configuring VPN and firewall rules using Linux command-line tools (such as iptables, strongSwan, or OpenVPN) where applicable.
  • Provide parity in troubleshooting steps for Linux environments, including relevant logs and commands.
  • Reference Linux-based Azure VM deployment and management alongside Windows VM examples.
  • Clarify that the steps apply to both Windows and Linux workloads, or specify any differences.
GitHub Create Pull Request
Azure Vmware Manage Arc-enabled Azure VMware private cloud ...ure-vmware/manage-arc-enabled-azure-vmware-solution.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides command examples for both Windows and Linux management VMs when activating the Python environment, but the Windows example is listed first. However, the Linux example is missing a closing quote and is less clearly presented. There are no explicit PowerShell or Windows-only tool references, but the documentation does not provide parity in clarity or completeness for Linux users. Additionally, most command examples are generic (az CLI), but there is no mention of Linux-specific nuances or troubleshooting.
Recommendations
  • Present Windows and Linux examples side-by-side or in parallel, ensuring equal clarity and completeness.
  • Correct the Linux example to include the missing closing quote and verify its accuracy.
  • Add Linux-specific troubleshooting notes or considerations where relevant (e.g., file paths, permissions).
  • Explicitly state that az CLI commands work on both Windows and Linux, and provide any OS-specific flags or environment setup steps if needed.
  • Ensure that all examples and instructions are equally detailed for both platforms.
GitHub Create Pull Request
Azure Vmware Attach Azure NetApp Files to Azure VMware Solution VMs ...zure-vmware/netapp-files-with-azure-vmware-solution.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation mentions both Windows and Linux VMs as prerequisites and notes that Azure NetApp Files supports both SMB (Windows) and NFS (Linux) protocols. However, the examples and instructions for mounting shares are generic and do not provide explicit command-line examples for either platform. The SMB (Windows) workflow is described first, and the NFS (Linux) workflow is described second, but neither includes concrete mounting steps or commands. There is a slight Windows-first bias in ordering and terminology, and the lack of Linux-specific examples (such as mount commands or /etc/fstab entries) limits Linux parity.
Recommendations
  • Provide explicit mounting instructions and examples for both Windows (using net use or PowerShell) and Linux (using mount command and /etc/fstab).
  • Ensure that Linux examples (NFS mounting) are given equal prominence and detail as Windows examples (SMB mapping).
  • Consider alternating the order of Windows and Linux instructions or presenting them side-by-side for parity.
  • Include troubleshooting tips for both platforms, not just generic guidance.
GitHub Create Pull Request
Azure Vmware Configure AVS Identities Role Assignments Manually ...b/main/articles/azure-vmware/native-role-assignment.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation describes manual role assignment steps exclusively using the Azure Portal GUI, which is most commonly accessed from Windows environments. There are no CLI or script-based examples (such as Azure CLI, Bash, or PowerShell), and no mention of Linux-compatible workflows or tools. This may disadvantage Linux users or those preferring automation.
Recommendations
  • Add Azure CLI examples for each role assignment step, demonstrating commands that can be run on Linux, macOS, or Windows.
  • Include PowerShell examples only if parity with Azure CLI is maintained, and clearly indicate platform compatibility.
  • Explicitly mention that the Azure Portal is web-based and accessible from any OS, but provide automation/script alternatives for cross-platform parity.
  • Add a section comparing GUI and CLI approaches, highlighting use cases for each.
GitHub Create Pull Request
Backup Support matrix for Azure Elastic SAN Backup (preview) ...cles/backup/azure-elastic-san-backup-support-matrix.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page exclusively references the Azure portal for backup configuration, restore, and management, without mentioning or providing examples for command-line tools such as Azure CLI, PowerShell, or REST API. While this avoids explicit Windows tool bias, it implicitly favors GUI-based workflows, which are more commonly associated with Windows environments. There is no mention of Linux-specific tools, CLI instructions, or cross-platform automation patterns, resulting in a lack of parity for Linux users who may prefer or require command-line or scriptable interfaces.
Recommendations
  • Add examples and instructions for configuring, restoring, and managing Elastic SAN backups using Azure CLI, which is cross-platform and widely used on Linux.
  • Include PowerShell examples for parity, but ensure CLI examples are presented first or alongside PowerShell to avoid Windows-first bias.
  • Reference REST API documentation for users who wish to automate backup operations in a platform-agnostic way.
  • Explicitly state that all operations can be performed via CLI and API, not just the Azure portal, and link to relevant documentation.
  • Consider adding a section comparing portal, CLI, and API workflows, highlighting cross-platform options.
GitHub Create Pull Request
Backup Integrate Microsoft Defender's ransomware alerts to protect Azure Backup recovery points ...up-azure-integrate-microsoft-defender-using-logic-apps.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation focuses exclusively on Azure Virtual Machines, with implicit emphasis on Windows environments. There are no examples, instructions, or notes regarding Linux VMs, Linux backup agents, or Linux-specific security considerations. All workflow steps, permissions, and integration points assume Windows-centric tools and services (e.g., Office 365 for email alerts, Microsoft Defender for Cloud, Azure Logic Apps) without mentioning Linux alternatives or compatibility. There is no guidance for users managing Linux VMs, nor any mention of Linux-specific ransomware detection or backup protection nuances.
Recommendations
  • Explicitly state whether the solution supports Linux VMs and, if so, provide Linux-specific instructions or caveats.
  • Include examples or screenshots demonstrating the integration process for Linux-based Azure VMs.
  • Mention any differences in ransomware detection or backup protection for Linux VMs compared to Windows VMs.
  • If Office 365 is not available or preferred, suggest alternative email alerting solutions compatible with Linux environments.
  • Clarify whether permissions and roles (e.g., Backup Operator, Security Reader) apply equally to Linux VMs, and note any required configuration steps.
  • Add troubleshooting or FAQ sections addressing common Linux VM scenarios (e.g., agent installation, alert compatibility, backup retention).
GitHub Create Pull Request
Backup Manage SQL server databases in Azure VMs using Azure Backup via CLI ...ob/main/articles/backup/backup-azure-sql-manage-cli.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page focuses exclusively on managing SQL Server databases in Azure VMs using the Azure CLI, but all examples and terminology assume SQL Server (a Windows-centric database) running on Azure VMs. There is no mention of Linux-based SQL Server deployments, nor are there any examples or notes about differences when running SQL Server on Linux VMs. All resource names and references (e.g., 'mssqlserver', 'testSQLVM') implicitly assume Windows environments, and there is no guidance for Linux users or parity in examples.
Recommendations
  • Explicitly mention support for SQL Server on Linux VMs, if applicable, and clarify any differences in CLI usage or prerequisites.
  • Provide example commands and output for SQL Server running on Linux VMs, including any differences in resource naming or container conventions.
  • Add notes or sections highlighting Linux-specific considerations (e.g., authentication, file paths, service management) where relevant.
  • Ensure terminology and examples do not assume Windows by default (e.g., use generic VM names, clarify when 'mssqlserver' applies to both platforms).
  • Include links to documentation for deploying and managing SQL Server on Linux in Azure VMs.
GitHub Create Pull Request
Backup Tutorial: Configure item-level backup for an Azure Kubernetes Service cluster .../main/articles/backup/tutorial-configure-backup-aks.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation exclusively uses the Azure portal UI for configuration steps, which is platform-agnostic but implicitly Windows-centric due to the prevalence of Windows usage in portal screenshots and workflows. There are no command-line examples (e.g., Azure CLI, kubectl, Bash scripts) for Linux users, nor are Linux-specific tools or workflows mentioned. The 'Next step' section references the Azure CLI, but the main tutorial does not provide CLI or Linux-native instructions, resulting in a lack of parity for Linux users.
Recommendations
  • Add Azure CLI and kubectl command examples for each configuration step, showing how to perform the same actions via command line on Linux.
  • Include Bash script snippets for automating backup configuration on Linux systems.
  • Provide screenshots or instructions for Linux desktop environments where relevant.
  • Explicitly mention cross-platform compatibility and clarify that the portal steps apply equally to Linux and macOS users.
  • Where possible, link to Linux-specific documentation or troubleshooting guides.
GitHub Create Pull Request
Bastion Quickstart: Use Terraform to deploy Azure Bastion ...b/main/articles/bastion/quickstart-deploy-terraform.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for verifying results, but PowerShell is given equal prominence as CLI, and there is no mention of Linux-specific shell environments or alternative tools. The CLI examples are generic and cross-platform, but the inclusion of PowerShell examples (which are most commonly used on Windows) without mentioning Bash or other Linux-native shells suggests a mild Windows bias. There are no explicit Linux examples or references to Linux tools or patterns.
Recommendations
  • Explicitly mention that Azure CLI commands work in Bash, Zsh, and other Linux shells, not just Windows.
  • Add example commands using Bash syntax (e.g., export instead of $var=...) to demonstrate Linux parity.
  • Clarify that PowerShell examples are optional and provide guidance for users on Linux/macOS who may not use PowerShell.
  • Consider including troubleshooting or environment setup notes for Linux users, such as installing Azure CLI on Linux.
  • Ensure that any referenced scripts or instructions do not assume a Windows environment by default.
GitHub Create Pull Request
Bastion VNet peering and Azure Bastion architecture .../azure-docs/blob/main/articles/bastion/vnet-peering.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias by referencing Windows virtual machines first and exclusively in deployment steps and example links (e.g., linking to '/azure/virtual-machines/windows/quick-create-portal' but not the Linux equivalent). There are no Linux-specific examples, instructions, or links, and the connection instructions reference RDP (primarily a Windows protocol) without mentioning SSH (commonly used for Linux VMs).
Recommendations
  • Include parallel instructions and links for Linux virtual machines, such as '/azure/virtual-machines/linux/quick-create-portal'.
  • Mention SSH explicitly alongside RDP when describing connection options, clarifying that Azure Bastion supports both.
  • Provide examples or references for connecting to Linux VMs via Bastion, not just Windows.
  • Ensure that deployment steps and architecture descriptions are OS-neutral or include both Windows and Linux scenarios.
GitHub Create Pull Request
Business Process Tracking Create Pipelines for Infrastructure, CI, and CD ...s-tracking/set-up-continuous-integration-deployment.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Visual Studio Code (VS Code) and its menus, which are typically presented in a Windows-centric manner. All command-line instructions use generic 'command prompt' terminology, with no mention of Linux shells (e.g., Bash) or macOS Terminal. There are no examples or instructions tailored for Linux users, such as alternative commands, file paths, or environment setup. The screenshots and UI references are also Windows-oriented, and there is no guidance for Linux-specific tooling or troubleshooting.
Recommendations
  • Include explicit instructions and examples for Linux users, such as using Bash or zsh in the Terminal, and clarify any differences in file paths or commands.
  • Add screenshots or descriptions for VS Code on Linux/macOS, noting any UI or menu differences.
  • Mention Linux package managers (e.g., apt, yum) for installing prerequisites like VS Code and Git.
  • Clarify that the steps are cross-platform where applicable, and highlight any platform-specific caveats.
  • Provide troubleshooting tips for common Linux issues (e.g., file permissions, environment variables).
GitHub Create Pull Request
Cloud Shell Get started with Azure Cloud Shell .../blob/main/articles/cloud-shell/get-started/classic.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI (Bash) and Azure PowerShell examples, but PowerShell is consistently mentioned alongside Bash, and in some cases, PowerShell-specific features (such as the Azure drive and context navigation) are highlighted without Linux/Bash equivalents. The 'Next steps' section lists PowerShell before CLI, suggesting a Windows-first orientation. There are no Linux-specific tools or workflows mentioned, and the Bash/CLI examples are limited to Azure CLI, which is cross-platform but does not showcase Linux-native patterns.
Recommendations
  • Ensure that Bash/Azure CLI examples are as detailed as PowerShell examples, including navigation and context management.
  • Alternate the order of CLI and PowerShell examples to avoid implicit prioritization.
  • Include Linux-native patterns or tips (e.g., using environment variables, piping, or shell scripting) where relevant.
  • Add a 'Next steps' link for Bash scripting or Linux command-line usage in Cloud Shell.
  • Explicitly mention that Azure CLI works natively on Linux and macOS, and provide examples of integrating with common Linux tools.
GitHub Create Pull Request
Cloud Shell Get started with Azure Cloud Shell ephemeral sessions ...lob/main/articles/cloud-shell/get-started/ephemeral.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation presents both Bash (Azure CLI) and PowerShell examples, but PowerShell is mentioned alongside Bash as a first-choice shell, and PowerShell examples are given equal prominence throughout. In some cases, PowerShell-specific features (such as the 'Azure:' drive and 'Get-AzCommand') are described, which do not have Linux/Bash equivalents. The 'Next steps' section lists PowerShell before CLI, suggesting a slight Windows-first ordering.
Recommendations
  • Ensure Bash/Azure CLI examples are presented first, or alternate the order to avoid perceived prioritization.
  • Clearly indicate which features are exclusive to PowerShell/Windows and provide equivalent guidance for Bash/Linux users where possible.
  • Add notes or sections highlighting Linux/Bash-specific workflows or tools, especially where PowerShell features are described.
  • In 'Next steps', alternate or randomize the order of PowerShell and CLI links to avoid implicit prioritization.
  • Where screenshots or instructions reference PowerShell-specific UI elements or behaviors, provide parallel Bash/Azure CLI visuals or explanations.
GitHub Create Pull Request
Cloud Shell Deploy Azure Cloud Shell in a virtual network with quickstart templates ...docs/blob/main/articles/cloud-shell/vnet/deployment.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation generally presents Azure CLI and Azure PowerShell as equivalent options for resource creation and management, but in several places, PowerShell is mentioned before CLI (e.g., in lists and links). The alternate way to get the Azure Container Instance ID gives the PowerShell command before the CLI command. There are no Linux-specific tools or patterns mentioned, and no explicit Bash scripting examples are provided. The documentation does not exclusively focus on Windows, but there is a subtle ordering bias favoring PowerShell/Windows tools over CLI/Linux equivalents.
Recommendations
  • Present Azure CLI and PowerShell examples in parallel, alternating which comes first, or group them together under neutral headings.
  • Include explicit Bash scripting examples where relevant, especially for steps that could be automated.
  • When listing options (portal, CLI, PowerShell), alternate the order or use alphabetical ordering to avoid implicit prioritization.
  • Add notes clarifying that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
  • Where screenshots or UI references are given, clarify if they are platform-agnostic or provide Linux/macOS equivalents if any differences exist.
GitHub Create Pull Request
Communication Services Additional Prerequisites ...ity/includes/active-directory/service-principal-cli.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows VM configuration guides for enabling managed identities (portal, PowerShell, CLI, ARM template, SDK), with no mention of Linux VM equivalents. Additionally, there are no Linux-specific examples or instructions for setting environment variables, and Windows-centric development environments (e.g., Visual Studio) are referenced without Linux alternatives.
Recommendations
  • Include links and examples for enabling managed identities on Linux VMs alongside Windows VM guides.
  • Provide instructions and examples for setting environment variables in Linux shells (e.g., Bash, zsh), in addition to Windows methods.
  • Reference cross-platform development environments (such as VS Code) and Linux-specific workflows where relevant.
  • Ensure that CLI examples and environment setup steps are clearly applicable to both Windows and Linux, or explicitly note any platform-specific differences.
GitHub Create Pull Request
Communication Services include file ...ces/quickstarts/includes/telemetry-app-insights-net.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation mentions Windows-specific console environments (cmd, PowerShell) before Bash, and does not provide any Linux/macOS-specific instructions or examples. All setup and run commands are generic but lack explicit Linux parity (e.g., environment variable setup, editor usage, troubleshooting). No Linux tools or patterns are discussed.
Recommendations
  • List Bash (Linux/macOS) first or equally when mentioning console windows.
  • Provide explicit Linux/macOS instructions for setting environment variables (e.g., export in Bash).
  • Include examples of opening and editing files using common Linux editors (e.g., nano, vim).
  • Add troubleshooting notes for Linux/macOS users (e.g., permissions, .NET SDK installation differences).
  • Ensure all commands and paths are cross-platform, or provide platform-specific notes where needed.
GitHub Create Pull Request
Communication Services Set up and obtain access tokens for Microsoft Entra ID users ...ntity/microsoft-entra-id-authentication-integration.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a mild Windows bias. While it does provide both REST API and Azure CLI methods for creating service principals, it references the Azure portal and Microsoft Entra admin center extensively, which are primarily accessed via web browsers and are platform-agnostic. However, there are no explicit Linux-specific examples, nor is there mention of Linux shell commands or patterns (e.g., bash, curl, etc.). The Azure CLI example is cross-platform, but the documentation does not clarify this, and there are no Linux terminal screenshots or instructions. There is no mention of Powershell, but the overall pattern is to present Windows-centric tools (Azure portal, admin center) first and exclusively.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows.
  • Provide Linux shell (bash/curl) examples for REST API calls, e.g., using curl to create a service principal.
  • Include screenshots or instructions for Linux terminal environments where relevant.
  • Add a note or section highlighting cross-platform compatibility of SDKs and tools.
  • Where possible, mention alternative Linux-native tools or workflows (e.g., using az CLI in bash scripts).
GitHub Create Pull Request
Connectors Integrate and manage security operations & Microsoft Graph Security ...ecurity-operations-create-api-microsoft-graph-security.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing the Azure portal and Microsoft-centric tools (Logic Apps Designer, Outlook connector, Microsoft Entra, etc.) without mentioning or providing examples for Linux or cross-platform alternatives. All instructions and examples assume use of the Azure portal, which is most commonly accessed via a web browser on Windows, and there is no mention of command-line interfaces (CLI), REST API usage, or automation via Linux tools. No Linux-specific guidance, examples, or parity is provided.
Recommendations
  • Include examples for using Azure Logic Apps and Microsoft Graph Security connector via Azure CLI, PowerShell, and REST API, highlighting cross-platform usage.
  • Explicitly mention that the Azure portal and Logic Apps Designer are accessible from any OS via a web browser, not just Windows.
  • Provide sample workflows or automation scripts using Linux tools (e.g., curl, bash scripts) to interact with Microsoft Graph Security API.
  • Reference or link to documentation on using Microsoft Graph Security from Linux environments.
  • Add parity in examples for sending alerts via email using non-Outlook connectors (e.g., SMTP, SendGrid) to demonstrate platform neutrality.
GitHub Create Pull Request
Container Apps Tutorial: Scale an Azure Container Apps application .../blob/main/articles/container-apps/tutorial-scaling.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for all Azure CLI commands, maintaining parity in command-line instructions. However, in the 'Send requests' section, the PowerShell example is significantly more complex and Windows-specific, while the Bash example uses standard Linux utilities. The PowerShell example is presented with equal prominence, but the explanations and referenced tools (e.g., PowerShell runspaces) are Windows-centric and may not be familiar to Linux users. Additionally, the instructions for opening a shell refer to 'bash shell' for Bash and 'command prompt and enter PowerShell' for PowerShell, subtly prioritizing Windows terminology. There is no explicit mention of Linux alternatives for the PowerShell-specific patterns, nor is there guidance for macOS users.
Recommendations
  • Add explicit instructions for macOS users, clarifying that Bash commands work on macOS and most Linux distributions.
  • In the 'Send requests' section, provide a brief explanation that Bash commands are native to Linux/macOS, while PowerShell commands are for Windows users.
  • Consider mentioning cross-platform shells such as PowerShell Core, which runs on Linux and macOS, and clarify any differences in command syntax or behavior.
  • Where PowerShell examples use advanced Windows-specific constructs (e.g., runspaces), offer alternative Bash or Linux-native approaches for concurrency, or reference tools like GNU Parallel.
  • Review terminology to avoid subtle Windows bias (e.g., use 'terminal' or 'shell' instead of 'command prompt' when referring to opening a shell).
GitHub Create Pull Request
Container Apps Tutorial: Communication between microservices in Azure Container Apps ...es/container-apps/communicate-between-microservices.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both Bash and PowerShell examples for all command-line steps, ensuring cross-platform coverage. However, PowerShell examples are given equal prominence to Bash, and in some sections (such as the 'Deploy front end application'), the PowerShell workflow is significantly more verbose and detailed, which may implicitly favor Windows users by offering more guidance and explanation for PowerShell. There is no explicit mention of Linux-specific tools, patterns, or troubleshooting, and no examples for native Linux shells other than Bash. Windows/PowerShell is treated as a first-class citizen throughout, with detailed object-oriented scripting, while Bash examples are more concise.
Recommendations
  • Ensure that Bash and PowerShell examples are equally detailed, so Linux users receive the same level of guidance as Windows users.
  • Add troubleshooting notes or tips specific to Linux environments, such as permissions, environment variable handling, or common issues with Docker and Azure CLI on Linux.
  • Consider including examples for other popular Linux shells (e.g., zsh, fish) or note that Bash examples are applicable to most POSIX shells.
  • Where PowerShell-specific objects and workflows are explained, provide equivalent explanations for Bash workflows (e.g., how environment variables are set and used, how to handle output parsing).
  • Explicitly state that all steps are cross-platform and highlight any platform-specific caveats or differences.
GitHub Create Pull Request
Container Apps Deploy an artifact file to Azure Container Apps ...s/blob/main/articles/container-apps/deploy-artifact.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for all commands, ensuring cross-platform coverage. However, PowerShell is given equal prominence to Bash, which may reflect a slight Windows bias, as Linux users are more likely to use Bash. Additionally, in the 'Run the project locally' section, the example uses a Windows-style path separator (target\containerapps-albumapi-java-0.0.1-SNAPSHOT.jar) in both Bash and PowerShell tabs, which may confuse Linux users. No Linux-specific tools or patterns are mentioned, and Windows tools are not exclusively referenced.
Recommendations
  • Ensure that Bash examples use Linux-style path separators (forward slashes) to avoid confusion.
  • Consider listing Bash examples before PowerShell, as Bash is more common in cross-platform and cloud-native scenarios.
  • Add a note clarifying that PowerShell examples are intended for Windows users, and Bash for Linux/macOS.
  • Where relevant, mention Linux/macOS-specific troubleshooting tips or environment setup steps.
  • Review all code snippets for platform-specific assumptions (such as file paths) and adjust as needed for true cross-platform parity.
GitHub Create Pull Request
Container Apps Deploy the Dapr extension for Azure Functions in Azure Container Apps ...in/articles/container-apps/dapr-functions-extension.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both PowerShell and curl examples for API invocation and log retrieval, but PowerShell is consistently presented first, suggesting a Windows-first approach. There is no explicit mention of Linux-specific tools or shell environments, and the examples do not address potential differences in command syntax or environment setup between Windows and Linux. The Azure CLI is used throughout, which is cross-platform, but the ordering and prominence of PowerShell may signal a subtle bias toward Windows users.
Recommendations
  • Alternate the order of PowerShell and curl examples, or present curl first to better reflect Linux usage patterns.
  • Explicitly mention that Azure CLI and curl commands work on Linux, macOS, and Windows, and provide any necessary notes about environment-specific differences.
  • Include example terminal prompts or screenshots from Linux environments alongside Windows examples.
  • Add a brief section or note confirming cross-platform compatibility and pointing to further resources for Linux/macOS users.
  • Consider including bash or zsh shell examples for common tasks, especially for scripting or automation.
GitHub Create Pull Request
Container Apps Generate GitHub Actions workflow with Azure CLI in Azure Container Apps ...lob/main/articles/container-apps/github-actions-cli.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for all commands, but PowerShell (Windows) examples are always presented immediately after Bash, suggesting a slight Windows-first ordering. The presence of PowerShell examples throughout indicates a moderate bias toward Windows users, as Linux users typically use Bash. No Linux-specific tools or patterns are missing, but the parity in example presentation could be improved.
Recommendations
  • Consider presenting Bash examples before PowerShell, or alternating which comes first to avoid implicit prioritization.
  • Explicitly mention that Bash examples are suitable for Linux/macOS and PowerShell for Windows, to guide users.
  • Add a short section clarifying cross-platform compatibility of Azure CLI commands, reassuring Linux users.
  • If relevant, include troubleshooting notes for common Linux-specific issues (e.g., permissions, environment variables).
GitHub Create Pull Request
Container Apps Configure the APM Java agent with Init Containers ...apps/java-application-performance-management-config.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both Bash and PowerShell examples for all command-line steps, ensuring parity between Linux and Windows users. However, PowerShell is featured as a first-class citizen throughout, which is a Windows-centric shell. There is no explicit mention of Linux-specific tools or troubleshooting, and PowerShell examples are given equal prominence to Bash, which may subtly reinforce Windows usage in cross-platform scenarios.
Recommendations
  • Clarify that Bash examples are intended for Linux/macOS and PowerShell for Windows, to help users choose the right instructions.
  • Add troubleshooting notes for common Linux-specific issues (e.g., file permissions, shell differences).
  • Include explicit references to Linux distributions (Ubuntu, CentOS, etc.) where relevant, especially for Docker and shell script usage.
  • Consider providing examples using native Linux tools (e.g., sed, grep) for configuration editing, or mention alternatives to PowerShell for Linux users.
  • Add a note that PowerShell Core is cross-platform, but most Windows users will use Windows PowerShell, and Linux/macOS users will likely use Bash.
GitHub Create Pull Request
Container Apps Observability of managed Java components in Azure Container Apps ...ob/main/articles/container-apps/java-component-logs.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for querying logs via Azure CLI, but in each case, the PowerShell example is presented immediately after Bash, and variable assignment uses 'SET' (which is a Windows command, not standard Bash). There is a subtle preference for Windows tooling and patterns, such as the use of PowerShell and 'SET' for Bash, which may confuse Linux users. No Linux-specific tools or patterns (e.g., export, shell scripting, grep) are mentioned, and the Bash examples use syntax that is not idiomatic for Linux environments.
Recommendations
  • Replace 'SET' with 'export' for Bash variable assignment to match Linux conventions.
  • Ensure Bash examples use idiomatic Linux shell syntax and commands.
  • Consider presenting Bash (Linux) examples before PowerShell (Windows) to avoid implicit Windows-first bias.
  • Add notes clarifying differences between Bash on Linux/macOS and PowerShell on Windows, especially for variable assignment and command usage.
  • Include troubleshooting tips or alternative commands for common Linux shells (e.g., zsh, sh) if relevant.
GitHub Create Pull Request
Container Apps View log streams in Azure Container Apps ...ocs/blob/main/articles/container-apps/log-streaming.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both Bash and PowerShell examples for all Azure CLI commands, ensuring coverage for both Linux/macOS and Windows users. However, PowerShell examples are given equal prominence to Bash, which may be unnecessary given that Azure CLI is cross-platform and Bash is the default shell for most Linux/macOS environments. The use of PowerShell examples throughout the page, rather than focusing primarily on Bash (with a note for Windows users), reflects a mild Windows bias. Additionally, instructions for stopping the log stream mention both Ctrl-C and Cmd-C, but do not reference Linux-specific shortcuts or considerations.
Recommendations
  • Make Bash the default or primary example, with PowerShell examples available via tabs or expandable sections for Windows users.
  • Clarify that Bash commands work on Linux/macOS and Windows (with WSL or Git Bash), and that PowerShell is primarily for native Windows environments.
  • Add notes or guidance for Linux users regarding shell compatibility, especially if any command syntax differs.
  • Ensure that instructions for stopping log streams mention Linux-specific shortcuts (e.g., Ctrl-C) and clarify any differences for macOS/Windows.
  • Consider reducing the prominence of PowerShell examples unless there are Windows-specific behaviors or requirements.
GitHub Create Pull Request
Container Apps Quickstart: Deploy a Dapr application to Azure Container Apps with an Azure Resource Manager or Bicep file ...iner-apps/microservices-dapr-azure-resource-manager.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both Bash and PowerShell examples for all CLI commands, ensuring cross-platform coverage. However, PowerShell examples are included for every step, which may indicate a slight bias towards Windows users. Additionally, in some sections (such as log viewing and resource cleanup), PowerShell examples are presented immediately after Bash, potentially giving Windows tools parity or priority. There are no Linux-specific tools or patterns mentioned, but Bash examples are present throughout, so Linux users are not excluded.
Recommendations
  • Explicitly state that Bash examples are suitable for Linux/macOS and PowerShell for Windows, to clarify platform relevance.
  • Consider including a note about running Bash commands in Windows environments (e.g., via WSL or Git Bash) for users who may not use PowerShell.
  • Add troubleshooting or environment setup tips for Linux/macOS users, such as common issues with Azure CLI or permissions.
  • Ensure that any referenced scripts or templates work identically on Linux/macOS and Windows, and mention any platform-specific caveats.
  • If possible, provide a summary table mapping commands to platforms (Windows/PowerShell, Linux/Bash, macOS/Bash) for quick reference.
GitHub Create Pull Request
Cost Management Billing Assign access to Cost Management data ...ost-management-billing/costs/assign-access-acm-data.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation exclusively references the Azure portal for all access assignment tasks and does not provide any command-line examples, such as Azure CLI, PowerShell, or REST API. While PowerShell is not mentioned directly, the lack of CLI or API instructions means users on Linux or macOS are not shown platform-neutral or Linux-friendly ways to perform these tasks. The portal is typically accessed via a web browser, but in Microsoft documentation, portal-centric instructions often reflect a Windows-first approach, especially when no alternatives are given.
Recommendations
  • Add Azure CLI examples for all access assignment tasks, as the CLI is cross-platform and widely used on Linux.
  • Include REST API instructions or references for programmatic access, which are platform-neutral.
  • If PowerShell examples are provided in other related docs, ensure Azure CLI equivalents are present and shown alongside or before PowerShell.
  • Explicitly mention that all portal steps can be performed from any OS with a supported browser, to clarify platform neutrality.
  • Add a section comparing methods (Portal, CLI, PowerShell, REST) and recommend CLI for Linux users.
GitHub Create Pull Request
Cyclecloud Download Cluster Projects and Templates ...main/articles/cyclecloud/download-cluster-templates.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page displays mild Windows bias by highlighting Microsoft HPC Pack (a Windows-centric job scheduler) prominently among the available templates, including a direct link to a PowerShell-based overview. No Linux-specific tools are given priority, and the HPC Pack entry is the only one with a link to a Microsoft documentation page, while others link to their respective open-source or vendor sites. There are no explicit Linux command examples or references to Linux-specific configuration patterns.
Recommendations
  • Provide equivalent documentation links for Linux-based schedulers (e.g., Slurm, Grid Engine, HTCondor) to balance the prominence given to HPC Pack.
  • Include example usage or configuration snippets for both Windows and Linux environments, especially for template import and management.
  • Avoid giving exclusive or first mention to Windows tools; present all scheduler options in a neutral order or group by platform.
  • Add notes or sections clarifying platform compatibility (Windows/Linux) for each template, and offer guidance for Linux users where appropriate.
GitHub Create Pull Request
Cyclecloud Plan your CycleCloud Workspace for Slurm Deployment ...rticles/cyclecloud/how-to/ccws/plan-your-deployment.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a bias towards Windows/Azure-centric tools and patterns. It exclusively references Azure Bastion, VPN Gateway, and ExpressRoute for network access, which are primarily managed through Azure Portal or PowerShell, with no mention of Linux-native alternatives or CLI-based workflows. There are no examples or guidance for Linux users (e.g., SSH tunneling, OpenVPN, or Linux command-line tools), nor are Linux-specific deployment or access patterns discussed.
Recommendations
  • Add examples and instructions for accessing CycleCloud Workspace for Slurm from Linux environments, such as SSH tunneling or OpenVPN.
  • Include CLI-based workflows using Azure CLI and Linux shell commands alongside or before Azure Portal/PowerShell instructions.
  • Mention Linux-native tools and patterns for network access and management (e.g., SSH, scp, rsync) where appropriate.
  • Provide parity in documentation by ensuring that Linux and Windows users have clear, step-by-step guidance for all major deployment and access scenarios.
GitHub Create Pull Request
Devtest Labs Create activity log alerts for labs ...-docs/blob/main/articles/devtest-labs/create-alerts.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation exclusively describes how to create activity log alerts using the Azure portal GUI, which is most commonly accessed via Windows. There are no examples or references to command-line methods (such as Azure CLI, Bash, or PowerShell), nor is there any mention of Linux-specific workflows or parity. This implicitly prioritizes Windows-centric usage patterns and omits guidance for Linux users or those preferring automation.
Recommendations
  • Add equivalent instructions for creating activity log alerts using Azure CLI and/or Azure PowerShell, with explicit examples for both Windows and Linux shells.
  • Include screenshots or terminal output for Linux environments where relevant.
  • Mention cross-platform access to the Azure portal and clarify that the steps apply equally regardless of OS, or note any differences.
  • Provide links to documentation for automating alert creation via scripts, and ensure examples are available for Bash and PowerShell.
  • Explicitly state that the Azure portal is accessible from any modern browser on Windows, Linux, or macOS.
GitHub Create Pull Request
Devtest Labs Hibernation for virtual machines ...main/articles/devtest-labs/devtest-lab-hibernate-vm.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias by exclusively using Windows 11 Pro as the example OS for VM creation, referencing 'your Windows VM' in screenshots, and omitting any mention or example of Linux VM creation or hibernation. There are no Linux-specific instructions, screenshots, or clarifications about Linux support or differences.
Recommendations
  • Include parallel Linux VM creation instructions and screenshots (e.g., using Ubuntu or other supported Linux images).
  • Clarify whether hibernation is supported for Linux VMs, and if there are any differences or limitations compared to Windows.
  • Use neutral language in examples and screenshots (e.g., 'Select your VM' instead of 'Select your Windows VM').
  • Provide explicit examples for both Windows and Linux, or indicate OS-specific steps where necessary.
GitHub Create Pull Request
Devtest Labs Store secrets in a key vault ...devtest-labs/devtest-lab-store-secrets-in-key-vault.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias by mentioning Windows VM passwords as the first example of secrets, while Linux SSH keys are mentioned second. There are no platform-specific examples or instructions for Linux users (e.g., how to use secrets for Linux VMs), nor are Linux command-line tools or patterns referenced. The screenshots and instructions are generic and do not provide parity for Linux scenarios.
Recommendations
  • Provide explicit Linux examples, such as storing and retrieving SSH keys for Linux VMs.
  • Include instructions or screenshots demonstrating secret usage in Linux VM creation workflows.
  • Mention Linux command-line tools (e.g., Bash, CLI) where relevant, alongside any Windows-specific tools.
  • Ensure that examples and ordering do not consistently prioritize Windows scenarios over Linux.
GitHub Create Pull Request
Devtest Labs Stop and resize lab VMs ...ob/main/articles/devtest-labs/devtest-lab-resize-vm.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation exclusively describes resizing Azure DevTest Lab VMs using the Azure portal GUI, with screenshots and instructions that implicitly assume a Windows-centric workflow. There are no examples or mentions of resizing VMs via command-line tools, such as Azure CLI, PowerShell, or Bash, nor is there any guidance for Linux users or those using non-GUI environments.
Recommendations
  • Add examples for resizing VMs using Azure CLI and/or PowerShell, with clear instructions for both Windows and Linux/macOS environments.
  • Include screenshots or terminal output for command-line workflows, demonstrating parity for users who do not use the Azure portal GUI.
  • Explicitly mention that the resizing process can be performed from any OS using the Azure CLI, and provide links to relevant cross-platform documentation.
  • If possible, add troubleshooting steps or notes relevant to Linux users, such as SSH connection guidance after resizing.
GitHub Create Pull Request
Devtest Labs Encrypt Disks with Customer-Managed Keys ...es/devtest-labs/encrypt-disks-customer-managed-keys.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation exclusively describes disk encryption management in Azure DevTest Labs using the Azure portal UI, with screenshots and step-by-step instructions. There are no command-line examples, and no mention of Linux-specific tools or workflows (such as Azure CLI, Bash, or Linux shell scripting). The documentation implicitly assumes a Windows-centric approach by relying solely on graphical interfaces and omitting cross-platform command-line alternatives.
Recommendations
  • Add Azure CLI and/or PowerShell command examples for each major step, ensuring parity for users on Linux, macOS, and Windows.
  • Explicitly mention that all steps can be performed using Azure CLI or REST API, and provide links or code snippets.
  • Include notes or sections for Linux users, such as how to validate disk encryption from a Linux VM or using Linux-native tools.
  • Balance screenshots with terminal output examples to support users who prefer or require command-line workflows.
GitHub Create Pull Request
Devtest Labs Set up a lab, lab VM, and lab user ...in/articles/devtest-labs/tutorial-create-custom-lab.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias by exclusively providing instructions and examples for creating a Windows Server 2019 Datacenter VM, without mentioning or providing equivalent steps for Linux-based VMs. There are no references to Linux images, tools, or user patterns, and the workflow implicitly assumes Windows as the default operating system for lab VMs.
Recommendations
  • Include instructions and screenshots for creating a Linux VM (e.g., Ubuntu, CentOS) alongside the Windows example.
  • Mention Linux images as available options when selecting a base for the VM, and highlight any differences in configuration (e.g., SSH key setup instead of password).
  • Provide guidance on Linux-specific user management and access patterns, such as using SSH keys and configuring sudo privileges.
  • Ensure that artifact examples and automation templates demonstrate parity for both Windows and Linux environments.
  • Use neutral language when referring to VM operating systems, and avoid implying Windows as the default or only choice.
GitHub Create Pull Request
DNS Delegate a subdomain - Azure DNS ...zure-docs/blob/main/articles/dns/delegate-subdomain.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates a Windows bias by providing only Windows-centric instructions for testing DNS delegation (using 'nslookup' at a command prompt) and referencing Azure PowerShell for automation, without mentioning Linux equivalents or CLI alternatives. There are no examples or instructions for Linux users, such as using Bash, dig, or Azure CLI.
Recommendations
  • Include Linux-specific instructions for testing DNS delegation, such as using 'dig' or 'nslookup' from a Bash terminal.
  • Mention Azure CLI as an alternative to Azure PowerShell for managing DNS zones and records, with example commands.
  • When referencing command-line tools, provide both Windows and Linux usage examples side-by-side.
  • Clarify that the steps can be performed from any OS, and link to cross-platform installation guides for Azure CLI and PowerShell.
GitHub Create Pull Request
DNS Integrate Azure DNS with your Azure resources - Azure DNS ...azure-docs/blob/main/articles/dns/dns-custom-domain.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation consistently uses Windows-centric validation instructions, specifically referencing the 'nslookup' command and showing screenshots of its use in Windows CMD. There are no examples or instructions for performing DNS validation on Linux or macOS systems, nor are alternative tools (like 'dig') mentioned. This creates a subtle Windows bias by assuming the user is on a Windows environment and omitting Linux/macOS parity.
Recommendations
  • Include Linux/macOS equivalents for DNS validation, such as examples using the 'dig' command.
  • Add screenshots or terminal output from Linux/macOS environments to complement the Windows CMD examples.
  • Explicitly mention that DNS validation can be performed on any OS and provide cross-platform instructions.
  • Where 'nslookup' is referenced, note that it is available on multiple platforms, but also suggest alternatives like 'host' or 'dig' for Linux/macOS users.
GitHub Create Pull Request
DNS Quickstart: Create an Azure DNS zone and record - Azure CLI ...zure-docs/blob/main/articles/dns/dns-getstarted-cli.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a mild Windows bias in the 'Test the name resolution' section, where instructions refer to 'opening a command prompt' and show a screenshot of the Windows command prompt. The use of 'nslookup' is presented generically, but the context and visuals are Windows-centric. There are no Linux-specific instructions or screenshots, and alternative tools (e.g., 'dig') commonly used on Linux are not mentioned.
Recommendations
  • Include explicit instructions for testing DNS resolution on Linux and macOS, such as using 'nslookup' or 'dig' in a terminal.
  • Add screenshots or example outputs from Linux/macOS terminals alongside the Windows command prompt screenshot.
  • Replace 'Open a command prompt' with platform-neutral language like 'Open a terminal or command prompt'.
  • Mention that 'nslookup' is available on most platforms, and suggest alternatives like 'dig' for Linux users.
  • Ensure that all steps and examples are clearly applicable to all supported platforms, not just Windows.
GitHub Create Pull Request
DNS Quickstart: Create an Azure DNS Private Resolver using Terraform ...cles/dns/dns-private-resolver-get-started-terraform.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for verifying results, but PowerShell is presented as a primary tab alongside CLI, and PowerShell-specific commands are included. There is no explicit mention of Linux-specific shell environments or examples, and PowerShell is a Windows-centric tool, which may signal a Windows bias. The instructions for running Terraform do not specify platform-specific commands, but the verification steps could be improved for Linux parity.
Recommendations
  • Add explicit Bash/Linux shell examples for verification steps, especially for variable assignment and command usage.
  • Clarify that Azure CLI commands work cross-platform and provide example shell syntax for Linux/macOS (e.g., export instead of $var=...).
  • Consider listing Azure CLI (which is cross-platform) before PowerShell, or clarify that PowerShell Core is available on Linux/macOS.
  • Include notes or tabs for Linux/macOS users where command syntax or environment setup differs.
  • Avoid presenting PowerShell as a default or primary option unless parity is ensured for Linux users.
GitHub Create Pull Request
DNS Quickstart: Use Terraform to configure private DNS zones in Azure ...s/blob/main/articles/dns/dns-private-zone-terraform.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by exclusively creating Windows virtual machines in the Terraform example and omitting Linux VM creation. The customer intent and checklist both specify Windows VMs only, and there are no Linux-specific instructions, examples, or parity in the resource creation steps.
Recommendations
  • Add parallel examples and instructions for creating Linux virtual machines alongside Windows VMs.
  • Update the checklist and customer intent to mention both Windows and Linux VM scenarios.
  • Provide sample Terraform code and output examples for Linux VM creation.
  • Include verification steps that demonstrate connecting to and managing Linux VMs (e.g., using SSH).
  • Clarify that the process applies to both Windows and Linux VMs, or provide separate quickstarts for each.
GitHub Create Pull Request
DNS What is autoregistration feature in Azure DNS private zones? ...blob/main/articles/dns/private-dns-autoregistration.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page mentions Azure PowerShell before Azure CLI in the 'Next steps' section, which may suggest a Windows-first bias. The primary example for creating a private zone is given using PowerShell, a Windows-centric tool, before mentioning the cross-platform Azure CLI. No explicit Linux examples or Linux-specific tools are provided.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples to ensure cross-platform parity.
  • Explicitly mention that Azure CLI is available on Linux and macOS, and provide links or notes for Linux users.
  • Include screenshots or instructions that demonstrate the process on Linux environments, not just Windows.
  • Add a note clarifying that both PowerShell and CLI are supported on multiple platforms, and provide guidance for Linux users where relevant.
GitHub Create Pull Request
DNS Tutorial: Create an Azure DNS alias record to refer to an Azure public IP address ...zure-docs/blob/main/articles/dns/tutorial-alias-pip.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The tutorial exclusively uses Windows Server for the virtual machine example, including instructions for installing IIS via Windows GUI and connecting via RDP. There are no examples or instructions for deploying a Linux VM, installing a web server (e.g., Apache or Nginx), or connecting via SSH. All screenshots and step-by-step guidance are Windows-centric, and Linux alternatives are not mentioned.
Recommendations
  • Add parallel instructions for creating a Linux-based VM (e.g., Ubuntu) and installing a web server (Apache or Nginx) using SSH and command-line tools.
  • Include screenshots and steps for Linux VM setup and web server verification.
  • Explicitly mention that the tutorial applies to both Windows and Linux VMs, and provide links to relevant Linux documentation.
  • Where possible, use generic Azure portal steps that apply to both OS types, or clearly indicate OS-specific differences.
GitHub Create Pull Request
DNS Import and export a domain zone file for Azure private DNS - Azure CLI ...cs/blob/main/articles/dns/private-dns-import-export.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation mentions Windows DNS and its default zone file location before mentioning BIND (Linux), and provides specific Windows paths and console instructions. There is a slight prioritization of Windows tooling and conventions when describing how to obtain zone files, with Windows DNS discussed before BIND. However, the CLI examples themselves are cross-platform and do not show PowerShell or Windows-only commands.
Recommendations
  • Present Linux/BIND and Windows DNS sources in parallel or alternate the order to avoid Windows-first bias.
  • Include explicit Linux file path examples for BIND (e.g., /etc/bind/zones/) alongside Windows paths.
  • Clarify that the Azure CLI commands work identically on Linux, macOS, and Windows, and consider showing example CLI usage on Linux (e.g., using bash).
  • Add notes or examples for verifying zone files using Linux-native tools (e.g., dig) in addition to nslookup.
  • Ensure that any references to file paths or system tools are balanced between Windows and Linux environments.
GitHub Create Pull Request
DNS Tutorial: Create an Azure child DNS zone ...b/main/articles/dns/tutorial-public-dns-zones-child.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation exclusively uses the Azure portal UI for all instructions and does not provide any command-line examples. While it avoids explicit Windows tools or PowerShell, the absence of CLI instructions (such as Azure CLI or Bash) means Linux users are not given parity. The UI-centric approach implicitly favors Windows users, who are more likely to use graphical interfaces, and omits guidance for those who prefer or require command-line automation, common in Linux environments.
Recommendations
  • Add equivalent Azure CLI commands for all major steps (creating child DNS zone, verifying NS records, deleting resources), with example usage in Bash.
  • Explicitly mention that all steps can be performed via CLI and provide links to relevant Azure CLI documentation.
  • Include a section comparing portal and CLI workflows, highlighting cross-platform options.
  • Ensure screenshots and instructions do not assume a Windows environment (e.g., avoid references to Windows-only features or terminology).
GitHub Create Pull Request
Event Grid Send Blob storage events to web endpoint - template .../articles/event-grid/blob-event-quickstart-template.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation primarily describes deployment and interaction via the Azure Portal, with only a brief mention of Azure PowerShell, Azure CLI, and REST API as alternative methods. However, it links first to PowerShell-specific instructions for template deployment, and does not provide explicit Linux or cross-platform CLI examples inline. There are no Linux-specific instructions, screenshots, or terminal commands, and the workflow assumes use of browser-based Azure Portal, which is platform-agnostic but often associated with Windows environments.
Recommendations
  • Add explicit Azure CLI examples for template deployment, including Linux/macOS terminal usage.
  • Provide links to both PowerShell and CLI documentation, mentioning CLI first or equally.
  • Include sample commands for uploading files to Blob storage using cross-platform tools (e.g., Azure CLI, curl, azcopy).
  • Add screenshots or terminal output from Linux environments where relevant.
  • Clarify that all steps can be performed from Linux/macOS as well as Windows, and highlight any platform-specific considerations.
GitHub Create Pull Request
Event Grid Concepts (push delivery) in Event Grid basic ...s/azure-docs/blob/main/articles/event-grid/concepts.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page demonstrates mild Windows bias in the section listing examples for creating event subscriptions. Azure PowerShell samples are mentioned explicitly and listed before Linux-friendly alternatives like Azure CLI. There is no explicit Linux example or mention of Linux-specific tools, and PowerShell (primarily a Windows tool, though now cross-platform) is highlighted. The CLI example is present, but PowerShell is listed immediately after, suggesting a Windows-first approach.
Recommendations
  • Ensure that Linux-friendly tools (such as Azure CLI) are listed before or alongside Windows-centric tools like PowerShell.
  • Provide explicit Linux examples or mention Linux compatibility where appropriate.
  • Include Bash or shell script examples for common operations, especially in sections where PowerShell is referenced.
  • Clarify that PowerShell is now cross-platform, but also offer native Linux command alternatives where possible.
  • Review other documentation links (such as template and script samples) to ensure parity between Windows and Linux environments.
GitHub Create Pull Request
Event Grid Subscribe to Azure Resource Notifications - ContainerService events ...ribe-to-resource-notifications-containerservice-events.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides step-by-step instructions and examples for Azure CLI, Azure PowerShell, and Azure Portal. However, the PowerShell examples are given equal prominence to Azure CLI, and in some cases, PowerShell is listed before CLI in the tab order. PowerShell is a Windows-centric tool, and its inclusion as a primary automation method can signal a Windows bias, especially since there are no Bash, Linux shell, or cross-platform scripting examples. There are no explicit references to Windows-only tools, but the lack of Linux-specific guidance or parity in scripting examples is notable.
Recommendations
  • Add Bash or Linux shell script examples alongside Azure CLI to demonstrate usage in a Linux environment.
  • Clarify that Azure CLI is fully cross-platform and can be used on Windows, macOS, and Linux.
  • If PowerShell is included, mention that PowerShell Core is available on Linux and macOS, and provide examples using PowerShell Core where appropriate.
  • Consider including automation examples using other popular Linux-native tools (e.g., curl, jq) for event subscription management.
  • Review tab ordering to ensure CLI (cross-platform) is listed before PowerShell (Windows-centric) to reduce perceived Windows-first bias.
GitHub Create Pull Request
Expressroute Managing complex network architectures with BGP communities - Azure ExpressRoute ...ocs/blob/main/articles/expressroute/bgp-communities.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page focuses on conceptual guidance for managing BGP communities in Azure ExpressRoute but demonstrates subtle Windows bias by referencing configuration via the Azure portal only, which is most commonly used on Windows environments. There are no examples or instructions for configuring BGP communities using Linux tools, CLI, or automation scripts, nor is there mention of cross-platform command-line options (e.g., Azure CLI, PowerShell vs. Bash). This omission may disadvantage Linux users or those preferring command-line or automation approaches.
Recommendations
  • Include step-by-step instructions for configuring BGP communities using Azure CLI and/or REST API, which are cross-platform and accessible from Linux, macOS, and Windows.
  • Explicitly mention that configuration can be performed from any OS, and provide examples for both PowerShell (Windows) and Bash (Linux/macOS) environments.
  • Add troubleshooting and verification steps using common Linux networking tools (e.g., tcpdump, bgpctl, bird, FRRouting) to demonstrate parity.
  • Reference automation options (e.g., Terraform, Ansible) that are widely used in Linux environments for network configuration.
  • Ensure that future documentation pages include both portal and CLI/script-based examples, with equal prominence.
GitHub Create Pull Request
Extended Zones Create an Arc-enabled AKS cluster in an Extended Zone ...zones/arc-enabled-workloads-arc-enabled-aks-cluster.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides all command-line examples and scripts in PowerShell syntax, including a complex function for cluster creation. No Bash or Linux/macOS shell equivalents are given, and PowerShell is used for Azure CLI invocation throughout. This creates friction for Linux/macOS users, who typically use Bash and may not be familiar with PowerShell scripting.
Recommendations
  • Provide Bash shell equivalents for all PowerShell scripts and command examples.
  • Explicitly note that Azure CLI commands work cross-platform and show usage in Bash (e.g., with environment variables, parameter passing).
  • Avoid wrapping Azure CLI commands in PowerShell functions unless a Bash alternative is also provided.
  • Clarify any platform-specific requirements or differences in the prerequisites section.
GitHub Create Pull Request
Extended Zones Deploy Arc-enabled workloads in an Extended Zone: ContainerApps ...extended-zones/arc-enabled-workloads-container-apps.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides only PowerShell-based automation for deploying Arc-enabled ContainerApps in Extended Zones, with no Bash or Linux shell equivalents. All scripting and resource management examples are given in PowerShell syntax, which is native to Windows and less common on Linux/macOS. This creates friction for users on non-Windows platforms, as they must translate the workflow to Bash or use PowerShell Core, which is not standard on most Linux distributions.
Recommendations
  • Provide equivalent Bash shell scripts for all PowerShell examples, using standard Linux tools and Azure CLI.
  • Explicitly mention cross-platform compatibility and note if PowerShell Core is required for Linux/macOS users.
  • Reorder examples so that Bash and PowerShell are presented side-by-side, or Bash is shown first to emphasize parity.
  • Add notes or links to resources for installing PowerShell Core on Linux/macOS, if PowerShell scripting is unavoidable.
  • Ensure all az CLI commands are shown in a way that works in Bash (e.g., avoid backticks, use \ for line continuation).
GitHub Create Pull Request
Extended Zones Deploy Arc-enabled workloads in an Extended Zone: PostgreSQL ...es/extended-zones/arc-enabled-workloads-postgre-sql.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides only PowerShell-based examples and scripts for deploying Arc-enabled PostgreSQL in Extended Zones. There are no Bash, shell, or Linux-native script examples, and the instructions assume the use of PowerShell, which is primarily a Windows tool. This creates friction for Linux/macOS users who typically use Bash or other shells.
Recommendations
  • Provide equivalent Bash/shell script examples for all PowerShell scripts.
  • Explicitly mention that az CLI commands are cross-platform and can be run in Bash, Zsh, etc.
  • Add notes or sections for Linux/macOS users, clarifying any differences in environment variables or command syntax.
  • Ensure cleanup and other operational commands are shown in both PowerShell and Bash formats.
GitHub Create Pull Request
Expressroute Reset a failed circuit - ExpressRoute | Microsoft Docs ...-docs/blob/main/articles/expressroute/reset-circuit.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation provides detailed instructions for resetting an ExpressRoute circuit using the Azure portal and Azure PowerShell. The PowerShell section assumes use of Windows and does not mention or provide examples for Bash, Azure CLI, or Linux/macOS workflows. There is no guidance for Linux/macOS users who may prefer command-line tools native to their platforms.
Recommendations
  • Add equivalent instructions using Azure CLI, which is cross-platform and works natively on Linux/macOS.
  • Explicitly mention that Azure PowerShell can be installed and used on Linux/macOS, or provide installation guidance for those platforms.
  • Present command-line examples for both PowerShell and Azure CLI, ideally side-by-side.
  • Avoid language that implies PowerShell is the only supported or recommended method for command-line operations.
GitHub Create Pull Request
Extended Zones Deploy a virtual machine in an Extended Zone using Azure CLI ...ocs/blob/main/articles/extended-zones/deploy-vm-cli.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides only a Windows VM deployment example, with no mention of Linux VM images or examples. The quickstart uses Azure CLI, which is cross-platform, but the exclusive use of a Windows image and lack of Linux parity in examples creates a subtle Windows bias.
Recommendations
  • Include a Linux VM deployment example alongside the Windows example, such as using Ubuntu or CentOS images.
  • Explicitly mention that Azure CLI supports deploying both Windows and Linux VMs.
  • Provide guidance or links to documentation for common Linux VM images and their parameters.
  • Alternate or parallelize examples to show both Windows and Linux scenarios.
GitHub Create Pull Request
Extended Zones Quickstart: Deploy a virtual machine in an Extended Zone - Azure portal .../blob/main/articles/extended-zones/deploy-vm-portal.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by exclusively using Windows Server as the example VM image, instructing users to open RDP ports (which are primarily used for Windows remote desktop access), and providing connection instructions only for RDP. There are no examples or instructions for deploying or connecting to Linux VMs (e.g., using SSH), nor are Linux images mentioned as options.
Recommendations
  • Include instructions and screenshots for deploying a Linux VM (e.g., Ubuntu) alongside the Windows example.
  • Add steps for configuring SSH access (port 22) for Linux VMs, including how to generate and use SSH keys.
  • Provide connection instructions for Linux/macOS users, such as using SSH from a terminal.
  • Mention Linux images as selectable options in the VM creation process.
  • Clarify that the portal supports both Windows and Linux VM deployments.
GitHub Create Pull Request
Firewall Manager Tutorial: Secure your hub virtual network using Azure Firewall Manager ...ain/articles/firewall-manager/secure-hybrid-network.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The tutorial demonstrates a notable Windows bias: all virtual machine examples use Windows Server, IIS installation is shown only via PowerShell, and no Linux VM or command-line alternatives are provided. Windows tools and workflows (PowerShell, RDP, IIS) are used exclusively, with no mention of Linux equivalents (e.g., SSH, Apache/Nginx, Bash). This creates friction for users wishing to follow the tutorial with Linux-based workloads.
Recommendations
  • Include Linux VM creation steps alongside Windows examples, using Ubuntu or other common distributions.
  • Provide Linux command-line equivalents for tasks such as web server installation (e.g., apt install apache2/nginx) and remote access (SSH instead of RDP).
  • Show how to use Bash or Azure CLI for VM extension deployment, not just PowerShell.
  • Explicitly mention that the tutorial applies to both Windows and Linux workloads, and highlight any differences.
  • Add screenshots and walkthroughs for Linux VM configuration and testing.
GitHub Create Pull Request
Firewall Manager Quickstart: Secure virtual hub using Azure Firewall Manager - Resource Manager template .../articles/firewall-manager/quick-secure-virtual-hub.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation demonstrates a notable Windows bias: all example virtual machines are Windows Server 2019, validation steps exclusively use Windows tools (Remote Desktop, Internet Explorer), and resource cleanup uses a PowerShell cmdlet. There are no Linux VM deployment or validation instructions, nor are Linux tools (SSH, browsers) mentioned.
Recommendations
  • Include Linux VM deployment options in the ARM template or documentation.
  • Provide validation steps for Linux users, such as using SSH to connect and testing with browsers like Firefox or curl.
  • Show resource group deletion using Azure CLI (az group delete) for cross-platform parity.
  • Mention macOS compatibility where relevant (e.g., RDP clients, browser testing).
  • Present examples for both Windows and Linux side by side, or clarify that the quickstart is Windows-specific if Linux is unsupported.
GitHub Create Pull Request
Firewall Azure Firewall Draft + Deployment (preview) ...azure-docs/blob/main/articles/firewall/draft-deploy.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation provides detailed examples for Azure Portal, Azure CLI, and Azure PowerShell. While the CLI section uses az commands (which are cross-platform), the PowerShell section is extensive and assumes the user has access to PowerShell, a tool primarily associated with Windows. There is no mention of Linux/macOS-specific shell usage (e.g., Bash), nor are there any Bash or shell script examples. Additionally, PowerShell is given a dedicated tab and full example set, which may suggest a Windows-centric approach. The CLI examples are cross-platform but do not explicitly mention Linux/macOS compatibility or provide shell-specific guidance. The documentation does not mention or prioritize Linux tools or patterns.
Recommendations
  • Add explicit Bash or shell script examples for Linux/macOS users alongside PowerShell.
  • Clarify that Azure CLI commands work on Linux/macOS and provide any necessary environment setup instructions for those platforms.
  • Mention cross-platform compatibility in the prerequisites and CLI sections.
  • Avoid implying PowerShell is required for non-Windows users; suggest alternatives where appropriate.
GitHub Create Pull Request
Firewall Azure Firewall preview features ...e-docs/blob/main/articles/firewall/firewall-preview.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation references Azure PowerShell as a configuration method for certain features (e.g., redeploying a firewall in a secured hub), but does not mention or provide equivalent instructions for Linux/macOS users (such as Azure CLI or Bash). There are no explicit examples or instructions for Linux tools or platforms, and PowerShell is referenced as a primary method, which may create friction for non-Windows users.
Recommendations
  • Include Azure CLI examples alongside PowerShell instructions for all configuration steps.
  • Explicitly mention that Azure CLI and Bash can be used on Linux/macOS for all supported operations.
  • Add links or references to cross-platform tools and documentation where appropriate.
  • Ensure that any portal-based instructions are clearly marked as platform-agnostic.
GitHub Create Pull Request
Firewall Azure Firewall Management NIC ...ure-docs/blob/main/articles/firewall/management-nic.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation provides only Azure PowerShell examples for critical firewall management operations (stop/start, allocate IPs), with no equivalent Azure CLI or REST API instructions. PowerShell is most commonly used on Windows, and Linux/macOS users are likely to use Azure CLI or REST API. The lack of cross-platform examples creates friction for non-Windows users and may prevent them from completing tasks efficiently.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands shown, especially for stopping/starting the firewall and assigning public IPs.
  • Mention REST API alternatives for automation and scripting on any platform.
  • Explicitly state that all operations can be performed via Azure CLI, REST API, or portal, and link to relevant documentation.
  • Where possible, show CLI examples before or alongside PowerShell to signal cross-platform parity.
GitHub Create Pull Request
Firewall Azure Firewall prescaling ...s/azure-docs/blob/main/articles/firewall/prescaling.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides a PowerShell example for configuring Azure Firewall prescaling, but omits equivalent examples for Linux/macOS users (e.g., Azure CLI or Bash). PowerShell is a Windows-centric tool, and its example is given before any cross-platform alternatives. No Linux-native tools or commands are mentioned, and the configuration section does not offer parity for non-Windows environments.
Recommendations
  • Add Azure CLI examples for configuring prescaling, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that PowerShell is available on Linux/macOS, or provide Bash script examples.
  • Ensure that ARM template and Bicep examples are accompanied by CLI deployment instructions suitable for Linux/macOS users.
  • Present cross-platform examples (Azure CLI, Bash) before or alongside PowerShell examples to avoid Windows-first bias.
GitHub Create Pull Request
Firewall Quickstart: Create an Azure Firewall and IP Groups - Resource Manager template ...ain/articles/firewall/quick-create-ipgroup-template.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation provides a PowerShell-only example for resource cleanup and references the Remove-AzResourceGroup cmdlet, which is a Windows/PowerShell-centric tool. There are no equivalent CLI or Bash examples for Linux/macOS users. The deployment instructions rely on the Azure Portal, which is cross-platform, but command-line automation is only shown for Windows/PowerShell environments.
Recommendations
  • Add equivalent Azure CLI (az group delete) and Bash examples for resource group deletion.
  • Where PowerShell cmdlets are shown, also provide cross-platform alternatives (Azure CLI, Bash, etc.).
  • Explicitly mention that Azure CLI commands work on Linux/macOS and provide links to relevant documentation.
  • Review other sections for implicit Windows-centric language or assumptions.
GitHub Create Pull Request
Firewall Quickstart: Create an Azure Firewall with multiple public IP addresses - Bicep ...in/articles/firewall/quick-create-multiple-ip-bicep.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by focusing exclusively on connecting to Windows Server VMs via RDP, without mentioning Linux VM scenarios or SSH access. The validation step assumes Remote Desktop Connection, a Windows-centric tool, and does not provide Linux/macOS alternatives. While deployment instructions include both Azure CLI and PowerShell, the example workloads and connection methods are Windows-only.
Recommendations
  • Include examples for deploying and connecting to Linux VMs, such as using SSH.
  • Mention cross-platform remote access tools (e.g., SSH for Linux/macOS, RDP for Windows).
  • In the 'Validate the deployment' section, provide instructions for connecting from Linux/macOS clients.
  • Clarify that the firewall can be used for both Windows and Linux VM scenarios.
  • Add cleanup instructions using Azure CLI, not just PowerShell.
GitHub Create Pull Request
Firewall Deploy and configure Azure Firewall Premium ...ure-docs/blob/main/articles/firewall/premium-deploy.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing a Windows test virtual machine (WorkerVM) for all testing steps, including browser and command-line usage. All examples and instructions (e.g., opening an administrator command prompt, deploying certificates, browsing to test URLs) assume a Windows environment, with no mention of Linux or macOS alternatives for VM deployment, certificate installation, or testing procedures. There are no Linux/macOS-specific instructions or examples provided.
Recommendations
  • Include instructions for deploying and configuring a Linux test VM alongside the Windows VM.
  • Provide Linux/macOS equivalents for certificate installation and curl usage.
  • Add browser testing steps for Linux/macOS environments.
  • Clarify that the testing steps can be performed on non-Windows platforms and provide any necessary platform-specific guidance.
  • Ensure that references to 'WorkerVM' are not exclusively tied to Windows, or explicitly mention support for other OS types.
GitHub Create Pull Request
Firewall Use Azure Firewall to protect Azure Virtual Desktop ...ain/articles/firewall/protect-azure-virtual-desktop.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page focuses on Azure Virtual Desktop, which is inherently Windows-centric, but it further reinforces Windows bias by referencing Windows-specific service tags, tools, and examples (such as Microsoft Edge proxy configuration). There are no Linux/macOS-specific instructions, examples, or tool references, and Windows terminology and endpoints are mentioned exclusively or first throughout the page.
Recommendations
  • Include examples or guidance for configuring Azure Firewall for Linux/macOS session hosts, if supported.
  • Mention whether Linux/macOS clients or session hosts are supported and provide relevant documentation links.
  • Provide proxy configuration examples for browsers commonly used on Linux/macOS (e.g., Firefox, Chrome) in addition to Microsoft Edge.
  • Clarify whether the 'WindowsVirtualDesktop' service tag applies to non-Windows session hosts, or provide equivalent tags/instructions for Linux/macOS.
  • Add a note about cross-platform compatibility and any limitations for non-Windows environments.
GitHub Create Pull Request
Firewall Quickstart: Create an Azure Firewall with multiple public IP addresses - Resource Manager template ...articles/firewall/quick-create-multiple-ip-template.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ powershell_heavy
Summary
The documentation is notably Windows-centric: it only references RDP to Windows Server VMs, links to PowerShell deployment guides, and provides a PowerShell-only example for resource cleanup. There are no Linux/macOS-specific instructions, examples, or SSH-based scenarios, which may hinder non-Windows users.
Recommendations
  • Include examples for connecting to Linux VMs via SSH, not just RDP to Windows Server.
  • Provide equivalent Azure CLI or Bash commands for resource cleanup alongside PowerShell.
  • Reference documentation for deploying Azure Firewall using Linux/macOS tools (e.g., Azure CLI, Bash scripts).
  • Clarify that the template can deploy Linux VMs and provide sample parameters for such deployments.
GitHub Create Pull Request
Firewall Quickstart: Create an Azure Firewall with multiple public IP addresses - Terraform ...rticles/firewall/quick-create-multiple-ip-terraform.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation is notably Windows-centric: it only demonstrates deploying Windows Server VMs and configuring RDP access, with no mention of Linux VM deployment or SSH access. The referenced PowerShell article is highlighted before any Linux/CLI alternatives, and all VM examples are Windows-only. There are no Linux VM or SSH rule examples, which may hinder Linux/macOS users seeking parity.
Recommendations
  • Add examples for deploying Linux VMs (e.g., using azurerm_linux_virtual_machine).
  • Include NAT rule examples for SSH access to Linux VMs alongside RDP for Windows.
  • Reference equivalent Linux-focused documentation (e.g., CLI or Bash guides) alongside PowerShell articles.
  • Clarify that the process is similar for Linux VMs and provide links or code samples.
  • Ensure troubleshooting and verification steps mention Linux scenarios where relevant.
GitHub Create Pull Request
Firewall Customer provided public IP address support in secured hubs ...in/articles/firewall/secured-hub-customer-public-ip.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation provides configuration instructions for customer-provided public IP addresses in Azure Firewall secured hubs primarily through Azure PowerShell examples, which are Windows-centric. There are no CLI (az), Bash, or Linux/macOS-specific instructions. The PowerShell approach is presented as the main automation method, with no mention of cross-platform alternatives. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer using the Azure CLI.
Recommendations
  • Add equivalent Azure CLI (az) examples for all configuration steps, including creating, associating, and reconfiguring public IP addresses with Azure Firewall.
  • Explicitly mention that Azure CLI can be used on Linux/macOS and provide links to relevant CLI documentation.
  • Reorder or parallelize examples so that CLI and PowerShell instructions are presented side-by-side or with equal prominence.
  • Clarify any platform-specific requirements for PowerShell, and suggest alternatives for non-Windows users.
GitHub Create Pull Request
Firewall Azure Firewall SNAT private IP address ranges ...docs/blob/main/articles/firewall/snat-private-range.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides extensive Azure PowerShell examples, which are typically used on Windows, and presents PowerShell instructions before Azure CLI equivalents. There are no Linux/macOS-specific shell examples (e.g., Bash), nor are there any references to Linux-native tools or considerations. While Azure CLI is cross-platform, the emphasis and ordering favor Windows/PowerShell users.
Recommendations
  • Add explicit Bash shell examples for Azure CLI commands to demonstrate usage on Linux/macOS.
  • Clarify that Azure CLI commands work on all platforms and provide platform-specific notes where relevant.
  • Consider including screenshots or step-by-step instructions for Linux/macOS users in portal sections.
  • Ensure parity in troubleshooting and deployment notes for non-Windows environments.
  • If PowerShell is required, mention PowerShell Core compatibility on Linux/macOS.
GitHub Create Pull Request
Firewall Tutorial: Deploy & configure Azure Firewall and policy using the Azure portal ...les/firewall/tutorial-firewall-deploy-portal-policy.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The tutorial exclusively demonstrates the deployment and testing of Azure Firewall using a Windows Server 2019 virtual machine. All instructions for creating and accessing the test workload VM are Windows-centric, with no mention of Linux or macOS alternatives. The remote desktop testing step assumes RDP and Windows tools, and there are no examples or guidance for Linux VM creation, SSH access, or browser testing from non-Windows platforms.
Recommendations
  • Add parallel instructions for deploying a Linux VM (e.g., Ubuntu) in the workload subnet, including steps for SSH access and browser installation.
  • Include testing steps for Linux users, such as using SSH to connect to the VM and using Firefox/Chrome to verify firewall rules.
  • Mention that the firewall and policy configuration applies equally to Linux workloads, and provide guidance for Linux/macOS users where steps differ (e.g., remote access methods).
  • Present both Windows and Linux VM creation options side-by-side to improve parity.
  • Clarify that the tutorial is not limited to Windows workloads and that Azure Firewall supports any OS.
GitHub Create Pull Request
Firewall Tutorial: Filter inbound Internet or intranet traffic with Azure Firewall DNAT policy using the portal ...ain/articles/firewall/tutorial-firewall-dnat-policy.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The tutorial exclusively uses Windows Server as the example workload VM and only describes connecting via Remote Desktop (RDP), which is a Windows-centric protocol. There are no examples or instructions for deploying a Linux VM, nor for connecting to a Linux workload (e.g., via SSH). This creates friction for users who wish to follow the tutorial with Linux or macOS workloads.
Recommendations
  • Include instructions for deploying a Linux VM (e.g., Ubuntu) alongside the Windows VM example.
  • Provide examples for configuring DNAT rules for SSH (port 22) access to a Linux VM.
  • Add testing steps for connecting to a Linux VM using SSH from Linux/macOS clients.
  • Present both Windows and Linux examples in parallel, or alternate which is shown first.
GitHub Create Pull Request
Firewall Filter inbound Internet or intranet traffic with Azure Firewall DNAT using the portal .../blob/main/articles/firewall/tutorial-firewall-dnat.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides step-by-step instructions for deploying Azure Firewall DNAT, but when creating the test workload virtual machine, it exclusively uses Windows Server 2019 Datacenter as the example OS. The only connectivity test described is via Remote Desktop Protocol (RDP), which is Windows-specific. There are no examples or guidance for deploying a Linux VM, nor for testing connectivity using SSH or other Linux-friendly methods.
Recommendations
  • Include parallel instructions for creating a Linux-based virtual machine (e.g., Ubuntu Server) in the 'Create a virtual machine' section.
  • Provide examples for testing connectivity to the Linux VM using SSH (port 22), including how to configure the DNAT rule for SSH.
  • When describing the test step, mention both RDP (for Windows) and SSH (for Linux) as valid methods, and provide sample commands for each.
  • Consider alternating or randomizing the order of OS examples, or presenting both side-by-side, to avoid implicit prioritization of Windows.
GitHub Create Pull Request
Firewall Overview of Azure Firewall service tags ...azure-docs/blob/main/articles/firewall/service-tags.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page provides only Azure PowerShell examples for configuring Azure Firewall service tags, with no equivalent Azure CLI or portal instructions. PowerShell is primarily a Windows tool, and its exclusive use here creates friction for Linux/macOS users. The mention of Azure CLI and portal as supported options is not followed by any examples or guidance, reinforcing a Windows-centric approach.
Recommendations
  • Add equivalent Azure CLI examples for all configuration steps, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Provide step-by-step instructions or screenshots for configuring service tags via the Azure portal.
  • Consider listing CLI and portal methods before or alongside PowerShell to avoid Windows-first bias.
  • Explicitly state that PowerShell Core is available cross-platform, if relevant, or clarify any limitations.
GitHub Create Pull Request
Firewall Azure Firewall threat intelligence based filtering ...azure-docs/blob/main/articles/firewall/threat-intel.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides a hosts file modification example explicitly for Windows, referencing the Windows file path and omitting equivalent instructions for Linux or macOS. No Linux/macOS hosts file location or syntax is mentioned, and the example is Windows-centric.
Recommendations
  • Include hosts file modification instructions for Linux (e.g., /etc/hosts) and macOS.
  • Provide example commands for editing the hosts file on Linux/macOS (e.g., using sudo nano /etc/hosts).
  • Present cross-platform instructions together or in parallel, not just Windows-first.
  • Clarify that the procedure applies to all OSes and specify differences where relevant.
GitHub Create Pull Request
Firmware Analysis Use service principals to automate workflows in firmware analysis ...lysis/automate-firmware-analysis-service-principals.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation references Azure PowerShell as a primary automation tool alongside Azure CLI and Python, but does not provide explicit Linux/macOS-specific guidance or examples. The command-line instructions are generic, but the mention of Azure PowerShell and lack of Linux shell examples (e.g., Bash scripting, environment variable handling) suggest a Windows-first approach. There are no examples of Linux-specific tools or considerations, such as credential storage or shell differences.
Recommendations
  • Add explicit Bash/Linux shell examples for automating service principal authentication and usage.
  • Clarify that Azure CLI works cross-platform and provide notes on any OS-specific differences.
  • Include links or sections for Linux/macOS users on credential management and scripting best practices.
  • Balance references to Azure PowerShell with equivalent Linux-native automation tools (e.g., Bash, zsh).
GitHub Create Pull Request
Frontdoor Secure traffic to origins ...e-docs/blob/main/articles/frontdoor/origin-security.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation provides example configurations for multiple origin types, including App Service, Application Gateway, AKS NGINX, and IIS. However, IIS (a Windows-only web server) is given a dedicated example, while there is no equivalent example for popular Linux web servers such as Apache or Nginx (outside of AKS NGINX, which is Kubernetes-specific). The IIS example is presented before the AKS NGINX example, indicating a slight Windows-first ordering. There are no PowerShell-heavy or Windows-only instructions, but the lack of parity for standalone Linux web servers (Apache, Nginx) constitutes a notable bias.
Recommendations
  • Add example configurations for popular Linux web servers such as Apache HTTP Server and standalone Nginx (outside of Kubernetes), showing how to filter requests based on the X-Azure-FDID header.
  • Ensure ordering of examples alternates or starts with platform-neutral or Linux examples to avoid implicit prioritization of Windows tools.
  • Explicitly mention that the IIS example is for Windows and provide guidance for equivalent Linux scenarios.
GitHub Create Pull Request
Frontdoor Migration FAQ ...ure-docs/blob/main/articles/frontdoor/migration-faq.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation references Azure PowerShell for migration tasks and lists it before any mention of Linux-friendly alternatives (such as Azure CLI or Bash scripting). There are no explicit Linux/macOS examples or instructions, and the only command-line migration guide linked is PowerShell-based, which is Windows-centric. This creates friction for Linux/macOS users who may prefer or require Azure CLI or other cross-platform tools.
Recommendations
  • Add migration instructions using Azure CLI and Bash for Linux/macOS users.
  • Provide parity in example scripts and links for both PowerShell and CLI.
  • Explicitly mention cross-platform options and clarify tool compatibility.
  • Reorder related content to present platform-neutral or Linux-friendly options before Windows/PowerShell-specific ones.
GitHub Create Pull Request
Frontdoor Post Migration Dev-Ops Experience ...rticles/frontdoor/post-migration-dev-ops-experience.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation provides extensive coverage of PowerShell (a Windows-centric tool) with a dedicated section, detailed prerequisites, and command mappings, while Linux/macOS alternatives (such as Bash or shell scripting) are not mentioned. PowerShell examples and references are given before CLI examples, and installation links for PowerShell point to Windows-specific instructions. There is no mention of cross-platform scripting approaches or parity for Linux/macOS users in the PowerShell section.
Recommendations
  • Add explicit Bash/shell script examples for deployment tasks alongside PowerShell examples.
  • Clarify that Azure CLI and Terraform are cross-platform and provide installation instructions for Linux/macOS as well as Windows.
  • In the PowerShell section, mention that PowerShell Core is available on Linux/macOS, and link to installation instructions for those platforms.
  • Reorder sections so that cross-platform tools (CLI, Terraform, Bicep) are presented before Windows-centric tools like PowerShell.
  • Where possible, provide parity in examples and troubleshooting steps for Linux/macOS users.
GitHub Create Pull Request
Frontdoor Troubleshoot File Compression ...frontdoor/standard-premium/troubleshoot-compression.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page shows a Windows bias by recommending Windows-specific tools (Fiddler, IIS) for troubleshooting and configuration. It provides detailed IIS instructions for compression settings but omits equivalent guidance for Linux-based web servers (e.g., Apache, Nginx). No Linux/macOS command-line or tool examples are given, and Windows tools are mentioned before cross-platform alternatives.
Recommendations
  • Include examples for checking compression using Linux/macOS command-line tools (e.g., curl, wget).
  • Mention and provide instructions for configuring compression on popular Linux web servers such as Apache (mod_deflate) and Nginx (gzip module).
  • List cross-platform tools (e.g., Wireshark, curl) alongside Fiddler for inspecting HTTP headers.
  • Ensure troubleshooting steps are not IIS-specific and cover common Linux server scenarios.
GitHub Create Pull Request
Frontdoor Settings mapping between Azure Front Door (classic) and Standard/Premium tier ...zure-docs/blob/main/articles/frontdoor/tier-mapping.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page mentions Azure PowerShell as a migration method in the 'Next steps' section, but does not mention CLI or Bash/Linux alternatives. This prioritizes Windows tooling and may create friction for Linux/macOS users who typically use Azure CLI or shell scripts.
Recommendations
  • Include Azure CLI migration instructions and link to relevant documentation alongside PowerShell.
  • Mention Bash or shell scripting options if available.
  • Present cross-platform tools (CLI, REST API) before or alongside PowerShell to avoid Windows-first impression.
GitHub Create Pull Request
Governance Quickstart: Create a blueprint with REST API ...les/governance/blueprints/create-blueprint-rest-api.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides only PowerShell examples for making REST API calls, with no mention of Linux/macOS alternatives such as curl, httpie, or bash scripting. Windows/PowerShell tooling is recommended first and exclusively, creating friction for users on non-Windows platforms.
Recommendations
  • Add equivalent examples using curl and/or httpie for Linux/macOS users.
  • Mention cross-platform tools (e.g., Azure CLI, ARMClient, REST clients) and clarify which are available on all OSes.
  • Reorder or parallelize examples so Linux/macOS methods are shown alongside PowerShell.
  • Explicitly state that REST API calls can be made from any OS and provide generic HTTP request examples.
GitHub Create Pull Request
Governance Canada Federal PBMM blueprint sample ...s/governance/blueprints/samples/canada-federal-pbmm.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation provides examples and parameters for both Windows and Linux VM deployments, but Windows-specific concepts (such as the 'Administrators group' and 'List of users that should be included in Windows VM Administrators group') are described in detail, while equivalent Linux user/group management is not mentioned. Windows VM examples and terminology appear before or in greater detail than Linux equivalents. There are no Linux-specific instructions or examples for managing users/groups or VM extensions, and the artifact parameters table includes Windows-specific details without Linux parity.
Recommendations
  • Add explicit Linux user/group management examples and parameters, such as instructions for configuring sudoers or local groups on Linux VMs.
  • Ensure that Linux VM extension deployment and audit requirements are described with the same level of detail as Windows.
  • Present Linux and Windows examples in parallel, or alternate which is shown first, to avoid implicit prioritization.
  • Clarify any differences in artifact deployment or configuration between Windows and Linux VMs, especially for audit and security controls.
GitHub Create Pull Request
Governance How to create a machine configuration assignment using the Azure Rest API ...-configuration/how-to/assign-configuration/rest-api.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page exhibits Windows bias primarily by referencing the PowerShell Get-AzAccessToken cmdlet as the only method for obtaining an Azure access token, without mentioning Linux/macOS alternatives (such as Azure CLI or environment variables). The only explicit tooling example for authentication is Windows-centric, and the link to Get-AzAccessToken is provided before any mention of cross-platform options. However, the main example for making the API call uses curl, which is cross-platform.
Recommendations
  • Include instructions for obtaining an Azure access token using Azure CLI (az account get-access-token), which works on Linux/macOS/Windows.
  • Mention environment variable approaches or other cross-platform authentication methods.
  • Present both PowerShell and Azure CLI examples side-by-side, or reference Azure CLI first.
  • Clarify that curl is available on all platforms and provide installation tips for Windows users if needed.
GitHub Create Pull Request
Governance How to create a machine configuration assignment using Terraform ...configuration/how-to/assign-configuration/terraform.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation exclusively demonstrates machine configuration assignment for Windows virtual machines, referencing only azurerm_windows_virtual_machine resources and built-in Windows configurations. There are no examples, instructions, or references for Linux virtual machines or Linux-specific configurations, which may leave Linux users without guidance.
Recommendations
  • Add parallel examples for azurerm_linux_virtual_machine resources showing how to assign configurations to Linux VMs.
  • Include built-in Linux configuration assignment examples (e.g., CIS Linux Baseline) if available.
  • Reference Linux/macOS Terraform getting started guides alongside the Windows/Powershell guide.
  • Clarify in the introduction whether the process applies to both Windows and Linux, or specify any limitations.
GitHub Create Pull Request
Governance How to create custom machine configuration policy definitions ...chine-configuration/how-to/create-policy-definition.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation is heavily focused on PowerShell and Windows-specific examples, with all code samples using PowerShell syntax and Windows file paths. The 'Platform' parameter is always set to 'Windows' in examples, and there are no equivalent Linux/macOS shell or file path examples. Windows tools and patterns (e.g., PowerShell cmdlets, C:\ paths) are used exclusively, and Linux is only mentioned in passing (e.g., required agent version), without actionable guidance or parity in examples.
Recommendations
  • Provide Linux/macOS-specific examples using Bash or Azure CLI, especially for steps like setting variables, uploading packages, and creating policy definitions.
  • Show examples where the 'Platform' parameter is set to 'Linux', with relevant Linux file paths (e.g., /home/user/package.zip) and context.
  • Include guidance for installing required modules and setting up the authoring environment on Linux/macOS, not just Windows.
  • Where PowerShell is required, clarify cross-platform usage and provide instructions for installing PowerShell on Linux/macOS.
  • Add notes or sections highlighting differences or additional steps for Linux/macOS users, including troubleshooting tips.
GitHub Create Pull Request
Governance How to create custom machine configuration package artifacts ...tion/how-to/develop-custom-package/2-create-package.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation is heavily PowerShell-centric, with most examples and tooling instructions using PowerShell commands and Windows paths. Windows examples and tools are presented first and in greater detail, while Linux-specific guidance is minimal and often deferred to external articles. There is a lack of Linux/macOS shell examples, and some steps (like file path outputs and packaging commands) are shown only with Windows conventions.
Recommendations
  • Provide equivalent Linux/macOS shell (bash) examples for compiling, renaming, and packaging configuration files.
  • Show Linux file paths and outputs alongside Windows examples (e.g., /home/user/dsc/MyConfig instead of only C:\dsc\MyConfig).
  • Clarify how to use PowerShell on Linux/macOS, or offer native shell alternatives for common tasks (e.g., using mv instead of Rename-Item).
  • Include a full Linux configuration authoring and packaging walkthrough, not just a reference to another article.
  • Explicitly state any platform limitations for each step, and provide workarounds or alternatives where possible.
GitHub Create Pull Request
Governance How to develop a custom machine configuration package ...onfiguration/how-to/develop-custom-package/overview.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by focusing primarily on PowerShell tooling (GuestConfiguration PowerShell module) and referencing Windows-centric technologies (PowerShell DSC) without providing equivalent Linux-specific examples or workflows. The instructional video and module links are PowerShell-focused, and Linux support is mentioned only in limitations or as an afterthought. There are no concrete Linux command-line examples, nor is there guidance for Linux-native tooling or workflows.
Recommendations
  • Add Linux-specific examples and workflows for authoring, testing, and publishing machine configuration packages, using native Linux tools where possible.
  • Provide equivalent instructions for Linux environments, such as using Bash, shell scripts, or Linux package management tools.
  • Include a Linux-focused video or tutorial demonstrating the process on Ubuntu or other supported distributions.
  • Clarify any differences in steps or requirements for Linux users, and ensure parity in documentation structure and detail.
  • Reference Linux documentation and modules/tools explicitly, not just as limitations.
GitHub Create Pull Request
Governance Troubleshooting Azure Machine Configuration ...onfiguration/overview/04-operations-troubleshooting.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is referenced as the primary tool for creating custom machine configuration packages, and the open-source nxtools module is described as a way to make Linux management easier for PowerShell users, reinforcing PowerShell as the main automation pattern. Windows-specific tools and terminology (such as PowerShell modules and Windows paths) are mentioned before or more prominently than their Linux equivalents. However, Linux examples and paths are provided alongside Windows in most troubleshooting sections, and Linux-specific policies are listed.
Recommendations
  • Provide equivalent Linux-native tooling and examples (e.g., Bash, Python, Ansible) for creating and managing machine configuration packages, not just PowerShell.
  • Highlight Linux and Windows examples equally, alternating which is shown first in each section.
  • Clarify whether PowerShell is required for Linux management or if native Linux tools can be used.
  • Expand documentation on Linux-specific troubleshooting and management workflows, including non-PowerShell approaches.
  • Consider mentioning cross-platform alternatives to PowerShell for Linux users who prefer native tools.
GitHub Create Pull Request
Governance Azure Automation State Configuration to machine configuration migration planning ...iguration/whats-new/migrating-from-azure-automation.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page exhibits a notable Windows bias. All code examples use PowerShell and Azure PowerShell modules, with no equivalent bash, shell, or Linux-native tooling shown. Windows-specific modules and patterns (such as MOF files, Import-DscResource, and PowerShell 7/5.1 compatibility) are discussed in detail, while Linux migration steps and troubleshooting are only briefly mentioned. The troubleshooting section acknowledges issues on macOS/Linux but provides only a PowerShell-based workaround. There are no Linux-specific configuration or module management examples, and Windows terminology and tools are presented first and exclusively throughout.
Recommendations
  • Add equivalent Linux/bash examples for exporting configurations and managing modules, using native Linux tools where possible.
  • Include explicit instructions for Linux users, such as using pwsh (PowerShell Core) on Linux, and clarify cross-platform compatibility.
  • Provide troubleshooting steps and workarounds using Linux-native commands (e.g., curl, wget, REST API calls) alongside PowerShell.
  • Highlight Linux-specific modules and configuration patterns, and discuss any differences in migration for Linux machines.
  • Reorder examples so that Linux and Windows are presented with equal prominence, or alternate which platform is shown first.
GitHub Create Pull Request
Governance Planning a change from Desired State Configuration extension to machine configuration ...onfiguration/whats-new/migrating-from-dsc-extension.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation is heavily focused on Windows and PowerShell workflows, referencing Windows PowerShell versions, DSC extension (primarily for Windows), and PowerShell cmdlets throughout. There are no explicit Linux/macOS examples, nor is there mention of Linux-specific DSC extension usage or migration steps. Windows tools and concepts (e.g., Local Configuration Manager, PowerShell module paths, Windows PowerShell compatibility) are referenced exclusively or before any cross-platform alternatives.
Recommendations
  • Add explicit guidance and examples for Linux VMs, including how to identify DSC extension usage and migrate configurations.
  • Clarify whether machine configuration and DSC extension support Linux, and provide parity in migration steps for Linux users.
  • Include Linux/macOS PowerShell module paths and usage patterns where relevant.
  • Reference Linux-specific extension publishers/types if applicable, and provide Kusto queries/examples for Linux DSC extensions.
  • Discuss differences in configuration management between Windows and Linux, including any limitations or requirements.
GitHub Create Pull Request
Governance Quickstart: Create policy assignment with REST API ...n/articles/governance/policy/assign-policy-rest-api.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates a notable Windows bias by primarily using PowerShell-specific syntax and escape characters in command examples, referencing PowerShell and Visual Studio Code as defaults, and providing only minimal guidance for Bash/Linux users. Linux/macOS users may encounter friction due to lack of explicit, parallel examples and instructions tailored to their environments.
Recommendations
  • Provide fully parallel Bash/Linux/macOS command examples alongside PowerShell, including correct escape characters and syntax.
  • Explicitly state which shell each example is for, and avoid assuming PowerShell as the default.
  • Include instructions for running Azure CLI commands in native Bash (not just Git Bash), and clarify any differences in file referencing and escaping.
  • Mention alternative editors (e.g., VS Code, vim, nano) for Linux/macOS users.
  • Add troubleshooting tips for common Linux/macOS issues (e.g., file permissions, path formats).
GitHub Create Pull Request
Governance Details of the policy definition structure aliases ...vernance/policy/concepts/definition-structure-alias.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation lists methods for discovering Azure Policy aliases, presenting the Visual Studio Code extension (cross-platform) first, but then gives Azure PowerShell examples before Azure CLI and REST API. The PowerShell section is more detailed, including advanced usage notes and examples, while the Azure CLI section is shorter and less emphasized. This ordering and depth may create friction for Linux/macOS users, as PowerShell is traditionally Windows-centric and CLI is more common on Linux/macOS.
Recommendations
  • Provide equally detailed examples and notes for Azure CLI, matching the PowerShell section (e.g., how to filter for modifiable aliases).
  • Consider listing Azure CLI before PowerShell, as CLI is more universally available across platforms.
  • Explicitly mention cross-platform compatibility for each tool, clarifying that PowerShell Core and VS Code are available on Linux/macOS.
  • Add links or notes for installing Azure CLI and PowerShell on Linux/macOS.
  • Ensure advanced usage scenarios (such as filtering for modifiable aliases) are shown for both CLI and PowerShell.
GitHub Create Pull Request
Governance Export Azure Policy resources .../articles/governance/policy/how-to/export-resources.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation presents both Azure CLI and Azure PowerShell methods for exporting Azure Policy resources, but PowerShell (a Windows-centric tool) is given a dedicated section and example. The CLI section appears first, but PowerShell is emphasized with detailed cmdlet references and a more complex example. No Linux/macOS-specific tools or shell examples (e.g., Bash, scripting, jq) are provided, and PowerShell is presented as a primary alternative despite its historical Windows bias.
Recommendations
  • Add Linux/macOS-specific examples, such as using Bash, jq, or other common shell tools to process the exported JSON.
  • Clarify that Azure CLI works cross-platform and highlight its parity with PowerShell.
  • Include a note or section on using PowerShell Core on Linux/macOS, if relevant.
  • Provide sample scripts for exporting and manipulating policy resources using native Linux tools.
  • Consider reordering or balancing the prominence of CLI and PowerShell sections to avoid implying PowerShell is the default or preferred method.
GitHub Create Pull Request
Governance Details of the initiative definition structure ...nce/policy/concepts/initiative-definition-structure.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_tools
Summary
The documentation generally avoids platform-specific bias, but in the 'strongType' section, it references the Windows PowerShell cmdlet 'Get-AzResourceProvider' as the method to determine valid resource types for strongType. No equivalent Azure CLI or REST API command is mentioned for Linux/macOS users, which may create friction for those not using PowerShell.
Recommendations
  • Add Azure CLI and REST API equivalents to 'Get-AzResourceProvider' for determining valid resource types for strongType.
  • Where PowerShell is referenced, provide parallel examples or links for Azure CLI and REST API usage.
  • Explicitly state that all JSON-based policy definitions and initiative structures are platform-agnostic and can be managed from any OS.
GitHub Create Pull Request
Governance Design Azure Policy as Code workflows .../articles/governance/policy/concepts/policy-as-code.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation mentions exporting policy and initiative definitions via PowerShell, CLI, or Azure Resource Graph, listing PowerShell first and referencing it as a primary tool. There are no explicit Linux/macOS shell examples (e.g., Bash, Azure CLI on Linux), nor are there references to Linux-specific workflows or tools. The documentation assumes familiarity with Windows-centric tools and patterns, which may create friction for Linux/macOS users.
Recommendations
  • Provide explicit Bash/Azure CLI examples for common tasks such as exporting policy definitions, assigning policies, and triggering remediation.
  • List cross-platform tools (e.g., Azure CLI) before Windows-specific ones like PowerShell.
  • Include notes or sections on running workflows from Linux/macOS environments, highlighting any differences or considerations.
  • Reference automation tools and scripting environments that are popular on Linux/macOS (e.g., shell scripts, cron, GitHub Actions runners on Linux).
GitHub Create Pull Request
Hdinsight Python UDF with Apache Hive and Apache Pig - Azure HDInsight ...main/articles/hdinsight/hadoop/python-udf-hdinsight.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides both shell (Linux/macOS) and PowerShell (Windows) examples for uploading files and running Hive/Pig jobs. However, PowerShell examples are more detailed, appear first in some sections, and troubleshooting is heavily PowerShell-centric. There is a notable emphasis on PowerShell tools and workflows, with specific troubleshooting steps only for Windows line endings and PowerShell scripts. Some advanced features (e.g., remote Pig jobs) are only documented for PowerShell, and limitations for Linux users are not fully addressed.
Recommendations
  • Provide equivalent Bash or Linux/macOS shell scripts for all PowerShell examples, especially for remote job submission and error retrieval.
  • Include troubleshooting steps for common Linux/macOS issues (e.g., file permissions, SSH key problems, line endings from macOS editors).
  • Ensure Linux/macOS shell examples are presented before or alongside PowerShell examples to avoid Windows-first bias.
  • Clarify any limitations or differences for Linux/macOS users (e.g., remote Pig job submission) and suggest workarounds.
  • Add links to Linux/macOS tool documentation where PowerShell tools are referenced.
GitHub Create Pull Request
Hdinsight Submit Apache Hadoop jobs in HDInsight ...t/hadoop/submit-apache-hadoop-jobs-programmatically.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation lists three main methods for submitting Hadoop jobs: .NET SDK, curl, and PowerShell. PowerShell, a Windows-centric tool, is given equal prominence to curl (cross-platform) and .NET SDK (primarily Windows, but can be cross-platform). The resource links for PowerShell are extensive, and there is no mention of Bash, Linux shell scripts, or Linux-specific tools. The ordering of examples (.NET SDK, curl, PowerShell) puts Windows-preferred technologies first, and the absence of Linux/macOS-specific guidance or parity in tooling suggests a Windows bias.
Recommendations
  • Add explicit Bash or Linux shell script examples for job submission.
  • Include guidance for Linux/macOS users, such as using the Azure CLI or native Hadoop command-line tools.
  • Clarify cross-platform compatibility for the .NET SDK and curl, and provide installation instructions for non-Windows environments.
  • Reorder examples to alternate or prioritize cross-platform tools (e.g., curl, Azure CLI) before Windows-specific tools like PowerShell.
  • Add a section addressing Linux/macOS workflows for HDInsight job submission.
GitHub Create Pull Request
Hdinsight Use Apache Maven to build a Java HBase client for Azure HDInsight ...hdinsight/hbase/apache-hbase-build-java-maven-linux.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a notable Windows bias. Windows-specific tools (Notepad, Command Prompt, PowerShell) are used exclusively or presented first in all local development steps. All file and directory commands use Windows syntax, and text editing is done with Notepad. The PowerShell workflow is described in detail, with custom modules and examples, while no equivalent Linux/macOS shell scripts or workflows are provided. There are no bash or Linux/macOS command-line examples for local development, file operations, or text editing, and Linux tools (e.g., nano, vim, bash) are not mentioned. The test environment is explicitly Windows 10, and Linux/macOS users must infer adaptations.
Recommendations
  • Provide parallel Linux/macOS examples for all command-line steps, using bash syntax (mkdir, rm, nano/vim, etc.) and POSIX paths.
  • Include instructions for editing files with common Linux/macOS editors (nano, vim, gedit, etc.), not just Notepad.
  • Offer a Linux/macOS test environment setup section, or clarify adaptations needed for non-Windows platforms.
  • Add bash shell scripts or equivalent for the PowerShell modules, or reference Azure CLI alternatives.
  • Present cross-platform commands side-by-side or clearly label OS-specific sections.
  • Avoid assuming Windows as the default; mention both platforms in prerequisites and throughout.
GitHub Create Pull Request
Hdinsight Tutorial: Apache Spark Streaming & Apache Kafka - Azure HDInsight ...t/hdinsight-apache-kafka-spark-structured-streaming.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides host information gathering commands specifically for Windows command prompt, with explicit mention that variations are needed for other environments. No Linux or macOS equivalents are given, and the jq path is hardcoded for Windows. This creates friction for Linux/macOS users, who must adapt the commands themselves.
Recommendations
  • Provide equivalent Linux/macOS shell commands for host information gathering, using standard jq and curl syntax.
  • List both Windows and Linux/macOS examples side-by-side, or default to cross-platform bash syntax where possible.
  • Avoid hardcoding Windows-specific paths (e.g., jq-win64.exe) and instead use generic references or note platform differences.
  • Explicitly mention how Linux/macOS users can adapt the commands, or link to platform-specific instructions.
GitHub Create Pull Request
Hdinsight Authorize users for Ambari Views - Azure HDInsight ...icles/hdinsight/hdinsight-authorize-users-to-ambari.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation presents PowerShell (Windows) automation for user management before the Linux-friendly curl/bash example. The PowerShell section is more detailed, with variable setup, credential handling, and output parsing, while the curl/bash section is shorter and notes that modifications are needed for Windows. This ordering and detail level may create friction for Linux/macOS users, though both platforms are ultimately supported.
Recommendations
  • Present Linux/bash (curl) examples before or alongside PowerShell examples to avoid Windows-first bias.
  • Expand the curl/bash example to match the detail and completeness of the PowerShell section (e.g., include output parsing, error handling, and privilege granting steps).
  • Explicitly state platform compatibility for each example and provide guidance for macOS users where appropriate.
  • Where possible, provide REST API examples in a platform-neutral way (e.g., using curl or HTTPie) as the primary automation method.
  • Add a table or section summarizing all supported automation methods for user management, with platform notes.
GitHub Create Pull Request
Hdinsight Manage Apache Hadoop clusters in HDInsight with .NET SDK - Azure ...icles/hdinsight/hdinsight-administer-use-dotnet-sdk.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a notable Windows bias. All package installation instructions use PowerShell, with no Linux/macOS equivalents (e.g., dotnet CLI or NuGet CLI). The code samples reference the PowerShell client GUID and use Windows-centric terminology (e.g., 'command prompt window'). In the Apache HBase section, balancing is described using Windows batch syntax (%HBASE_HOME%\bin), with no Linux shell equivalents. No Linux/macOS-specific instructions or examples are provided for any administrative tasks.
Recommendations
  • Provide Linux/macOS equivalents for package installation, such as 'dotnet add package' or 'nuget install' commands.
  • Include shell/bash examples alongside PowerShell, especially for cluster management and HBase balancing.
  • Avoid Windows-centric terminology like 'command prompt window'; use platform-neutral terms or mention both 'command prompt' and 'terminal'.
  • Reference both Windows and Linux environment variables (e.g., %HBASE_HOME% for Windows, $HBASE_HOME for Linux/macOS).
  • Clarify that the .NET SDK is cross-platform and provide guidance for Linux/macOS users where workflows differ.
GitHub Create Pull Request
Hdinsight Non-interactive authentication .NET application - Azure HDInsight ...ate-non-interactive-authentication-dotnet-applications.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation focuses exclusively on Windows-centric tools and workflows. All code examples are for .NET (C#), which is most commonly used on Windows, and NuGet package installation is shown using the PowerShell 'Install-Package' command. There are no Linux/macOS-specific instructions, nor are cross-platform alternatives (such as .NET CLI or Visual Studio Code) mentioned. The Azure portal workflow is platform-neutral, but the development and authentication steps assume a Windows environment.
Recommendations
  • Add instructions for installing NuGet packages using the .NET CLI (e.g., 'dotnet add package ...'), which works on Linux/macOS.
  • Mention that .NET Core/.NET 6+ and Visual Studio Code can be used on Linux/macOS for development.
  • Provide sample code or guidance for running the application on Linux/macOS, including any environment setup or prerequisites.
  • Include links to cross-platform authentication documentation, not just PowerShell-based guides.
  • Explicitly state platform compatibility for the SDKs and tools used.
GitHub Create Pull Request
Hdinsight Create Apache Hadoop clusters using templates - Azure HDInsight ...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-create-linux-clusters-arm-templates.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page shows a mild Windows bias: PowerShell is mentioned and linked before Azure CLI, and Visual Studio (a Windows-centric tool) is highlighted as a deployment method, including references to PowerShell scripts. There are no explicit Linux/macOS command-line examples or references to Linux-native editors (e.g., vim, nano), and the .NET client library example links to a Windows-specific page. While cross-platform tools like VS Code and Azure CLI are mentioned, Windows tools and patterns are presented first or with more detail.
Recommendations
  • Present Azure CLI examples and links before or alongside PowerShell to emphasize cross-platform support.
  • Include explicit Linux/macOS command-line examples for template deployment (e.g., bash scripts, use of native editors).
  • Mention Linux-native editors (vim, nano, gedit) as alternatives to VS Code for editing templates.
  • Provide parity in client library examples, linking to both Windows and Linux/.NET Core documentation.
  • Clarify that all deployment methods (CLI, REST API) work on Linux/macOS as well as Windows.
GitHub Create Pull Request
Hdinsight Apache Hive libraries during cluster creation - Azure HDInsight ...icles/hdinsight/hdinsight-hadoop-add-hive-libraries.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation references a PowerShell script as the primary example for adding Hive libraries, with the script location and instructions given before the Linux bash script. The script provided is a .ps1 file (PowerShell), and Azure PowerShell/.NET SDK are mentioned as cluster creation methods before Linux-specific instructions. There is a separate bash script for Linux, but it is introduced later and less prominently. Windows tools like Azure Storage Explorer are mentioned for file uploads, with no Linux alternatives suggested.
Recommendations
  • Present Linux (bash) and Windows (PowerShell) script options side-by-side, with equal prominence.
  • List Linux-native tools for uploading files to Azure Blob Storage (e.g., azcopy, Azure CLI) alongside Azure Storage Explorer.
  • Clarify which script to use based on the user's OS at the start of the instructions.
  • Provide explicit instructions for cluster creation using Linux command-line tools (e.g., Azure CLI), not just PowerShell/.NET SDK.
  • Avoid listing Windows/PowerShell options first unless there is a technical reason.
GitHub Create Pull Request
Hdinsight Add additional Azure Storage accounts to HDInsight ...ain/articles/hdinsight/hdinsight-hadoop-add-storage.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides a detailed PowerShell example for verifying the additional storage account, but does not offer an equivalent example for Linux/macOS users (e.g., Bash, curl, or Python). The PowerShell method is presented first and in more detail, while Linux verification relies on using the Apache Ambari web UI, which may not be suitable for all users or automation scenarios. There are no CLI or script examples for Linux users, and the prerequisites mention PowerShell specifically.
Recommendations
  • Add a Bash or Python example for verifying the storage account via REST API (using curl or requests) to match the PowerShell example.
  • Include Azure CLI commands for verification, if possible.
  • Present Linux/macOS-friendly methods before or alongside Windows/PowerShell examples.
  • Clarify that the PowerShell example is for Windows users and provide parity for other platforms.
GitHub Create Pull Request
Hdinsight Tutorial: On-demand clusters in Azure HDInsight with Data Factory ...dinsight/hdinsight-hadoop-create-linux-clusters-adf.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation relies exclusively on Azure PowerShell scripts for critical setup steps, such as creating the resource group, storage account, and copying files. No equivalent Bash/CLI examples are provided, and the PowerShell requirement is stated as a prerequisite. This creates friction for Linux/macOS users who may not have PowerShell installed or prefer Bash/Azure CLI. Additionally, the tutorial refers to the PowerShell script repeatedly as the canonical method for setup, with no mention of alternatives.
Recommendations
  • Provide equivalent Azure CLI (az) commands for all PowerShell script steps, including resource group, storage account, blob container creation, and file copying.
  • Explicitly state that users can use either PowerShell or Azure CLI, and link to installation guides for both.
  • Add a selector or toggle for Bash/Azure CLI vs. PowerShell throughout the tutorial, similar to other Azure docs.
  • Clarify any platform-specific requirements (e.g., PowerShell Core on Linux/macOS) if PowerShell must be used, and provide installation instructions.
  • Ensure screenshots and instructions are not Windows-centric (e.g., avoid assuming Windows file paths or UI layouts).
GitHub Create Pull Request
Firewall Azure Firewall Premium certificates ...cs/blob/main/articles/firewall/premium-certificates.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Bash and PowerShell scripts for certificate generation, but the PowerShell script is presented after the Bash script, and there is no evidence of exclusive Windows tools or patterns. Both scripts rely on OpenSSL, which is cross-platform. However, the inclusion of a PowerShell script may indicate some Windows bias, as PowerShell is primarily used on Windows (though it is available on Linux/macOS). No Windows-only tools or examples are given, and Linux users are not prevented from completing the task.
Recommendations
  • Clarify that both Bash and PowerShell scripts are cross-platform, and mention that PowerShell Core is available on Linux/macOS.
  • Explicitly state that OpenSSL commands work on Windows, Linux, and macOS, and provide installation guidance for each OS.
  • Consider providing a brief example of running the Bash script on Windows using WSL, or running PowerShell on Linux/macOS.
  • Ensure that any future troubleshooting or configuration steps do not assume Windows-only environments.
GitHub Create Pull Request
Governance Azure Machine Configuration prerequisites ...chine-configuration/overview/02-setup-prerequisites.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation demonstrates mild Windows bias by listing Windows validation tools first, referencing PowerShell DSC for both Windows and Linux, and providing links to Azure PowerShell before Azure CLI. Linux tools (Chef InSpec) are mentioned, but PowerShell DSC is emphasized as the primary validation tool for both platforms. There is no explicit omission of Linux-specific deployment instructions, but Windows-centric terminology and ordering may create friction for Linux users.
Recommendations
  • Present Linux and Windows examples/tools in parallel or alternate order to avoid Windows-first perception.
  • Include explicit Linux/macOS deployment instructions and examples, especially for managed identity and extension installation.
  • Highlight native Linux configuration management tools (e.g., Ansible, native shell scripts) if supported, or clarify why PowerShell DSC is used on Linux.
  • Provide Azure CLI examples before or alongside Azure PowerShell, as CLI is cross-platform.
  • Clarify any platform-specific limitations or differences in agent behavior.
GitHub Create Pull Request
Azure Resource Manager Resource declaration in Bicep ...s/azure-resource-manager/bicep/resource-declaration.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for querying supported resource locations, but PowerShell (a Windows-centric tool) is presented first, which may subtly prioritize Windows users. No Linux-specific tools or shell examples are given, but Azure CLI is cross-platform. There are no exclusive Windows-only examples, and the rest of the documentation is platform-neutral.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and more commonly used on Linux.
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, while PowerShell is primarily used on Windows.
  • Consider adding Bash shell examples or notes for Linux users where relevant.
  • Ensure future documentation alternates or randomizes the order of platform-specific examples to avoid implicit prioritization.
GitHub Create Pull Request
Azure Resource Manager Move Azure resources across resource groups, subscriptions, or regions ...resource-manager/management/move-resources-overview.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation mentions Azure PowerShell before Azure CLI when listing tools for moving resources, which may suggest a subtle Windows-first bias. However, no examples, commands, or instructions are given for either PowerShell or CLI, and no Windows-specific tools or patterns are described. There are no explicit PowerShell-heavy sections, nor are Linux examples missing, as none are provided for any platform.
Recommendations
  • When listing tools, mention Azure CLI before or alongside Azure PowerShell to avoid implying a Windows-first workflow.
  • Provide example commands for both Azure CLI and Azure PowerShell, ensuring parity and clarity for users on Linux, macOS, and Windows.
  • Explicitly state that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Add links to platform-specific guidance (e.g., using Azure CLI on Linux) where appropriate.
GitHub Create Pull Request
Backup Restore Azure Managed Disks ...ocs/blob/main/articles/backup/restore-managed-disks.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation provides instructions for restoring Azure Managed Disks and covers both Windows and Linux virtual machines when describing how to attach/detach disks after restore. However, the instructions for Windows VMs are consistently presented before those for Linux VMs, indicating a 'windows_first' bias. There are no PowerShell-heavy examples, exclusive mention of Windows tools, or missing Linux examples in the main restore workflow.
Recommendations
  • Alternate the order of Windows and Linux instructions, or present them in parallel (e.g., in a table or side-by-side format) to avoid implicit prioritization.
  • Explicitly state that the process applies equally to both Windows and Linux VMs at the beginning of the relevant section.
  • Ensure that any screenshots or linked instructions for Linux are as detailed and accessible as those for Windows.
  • Review linked resources to confirm Linux parity in depth and clarity.
GitHub Create Pull Request
Bastion Deploy private-only Bastion .../blob/main/articles/bastion/private-only-deployment.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ missing_linux_example
Summary
The documentation provides only Azure Portal (GUI) instructions for deploying Bastion in private-only mode. There are no command-line examples, such as Azure CLI, PowerShell, or ARM templates. This omission results in a lack of parity for Linux users, who typically use Azure CLI or bash scripting, while Windows users might expect PowerShell examples. The absence of CLI examples is a subtle bias, as it does not address the needs of users on non-Windows platforms.
Recommendations
  • Add step-by-step Azure CLI examples for all deployment steps, ensuring commands are compatible with bash and Linux environments.
  • If PowerShell examples are added, ensure Azure CLI equivalents are provided and presented either first or side-by-side.
  • Include ARM/Bicep template deployment instructions for automation across platforms.
  • Explicitly mention that the Azure Portal steps are platform-agnostic, but provide links or sections for command-line alternatives.
GitHub Create Pull Request
Cloud Shell How to use the new user interface for Azure Cloud Shell .../blob/main/articles/cloud-shell/new-ui-shell-window.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation generally maintains cross-platform neutrality, but in the 'Copy and paste' section, Windows instructions are listed first, followed by macOS and Linux. No PowerShell-heavy examples or exclusive mention of Windows tools are present, and Linux parity is maintained in most areas. However, the order of platform instructions may subtly prioritize Windows.
Recommendations
  • List platform instructions in alphabetical order (Linux, macOS, Windows) or group them in a way that does not imply priority.
  • Where platform-specific instructions are given, ensure equal detail and visibility for Linux and macOS.
  • Explicitly mention Linux/Bash features or differences where relevant, not just as an afterthought.
  • Continue to avoid exclusive use of Windows tools or PowerShell examples unless necessary, and always provide Bash/Linux equivalents.
GitHub Create Pull Request
Communication Services include file ...ts/identity/includes/access-tokens/access-token-net.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation mentions Windows command-line tools (cmd, PowerShell) before Bash when describing how to run commands, which may suggest a Windows-first bias. However, all command-line examples use 'dotnet' CLI commands, which are cross-platform, and there are no PowerShell-specific scripts or Windows-only tools used. No Linux-specific examples or instructions are provided, but the instructions are generally applicable to both Windows and Linux environments.
Recommendations
  • List Bash (Linux/macOS) before Windows tools (cmd, PowerShell) when describing command-line usage, or mention all platforms equally.
  • Explicitly state that all dotnet CLI commands work on Linux/macOS as well as Windows.
  • Provide example environment variable setting commands for both Windows (set, $env:) and Linux/macOS (export).
  • Add a note or section confirming Linux/macOS compatibility and any platform-specific considerations.
  • Include troubleshooting tips for Linux/macOS users if any common issues are known.
GitHub Create Pull Request
Communication Services Quickstart - Manage a room call ...cation-services/quickstarts/rooms/manage-rooms-call.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation page provides code samples for C#, Java, JavaScript, and Python, with no explicit Windows-only tools or PowerShell usage. However, there is evidence of Windows bias in the form of Windows-first navigation: the link to enabling PSTN dial-out in rooms points to a quickstart with '?tabs=windows', suggesting Windows is the default or primary platform. There is no mention of Linux-specific instructions, nor are Linux or cross-platform CLI examples provided for setup or configuration tasks.
Recommendations
  • Ensure that all quickstart and how-to links use neutral or platform-agnostic tabs (e.g., '?tabs=azcli' or provide both Windows and Linux tabs).
  • Add explicit instructions or examples for Linux environments, such as using Bash, Azure CLI, or other cross-platform tools for setup and configuration.
  • Review linked pages to confirm Linux parity in examples and instructions, and update navigation to avoid defaulting to Windows.
  • Where platform-specific steps are required, provide side-by-side instructions for both Windows and Linux users.
GitHub Create Pull Request
Communication Services include file ...kstarts/telephony/includes/voice-routing-sdk-csharp.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation mentions Windows-specific console environments ('Command Prompt, PowerShell') before Linux/Bash when describing how to run commands. However, all command-line examples use cross-platform .NET CLI commands and do not show Windows-only tools or PowerShell scripts. There are no Linux-specific examples or tools mentioned, but the instructions are generally applicable to both platforms.
Recommendations
  • List Bash (Linux/macOS) before Command Prompt/PowerShell, or mention all platforms equally (e.g., 'in a console window such as Bash, Command Prompt, or PowerShell').
  • Explicitly state that the .NET CLI commands work on Windows, Linux, and macOS.
  • Add a note or section confirming Linux/macOS compatibility, and provide troubleshooting tips for those platforms if relevant.
  • If platform-specific differences exist (e.g., environment variables, file paths), include examples for both Windows and Linux.
GitHub Create Pull Request
DNS Troubleshooting guide - Azure DNS .../azure-docs/blob/main/articles/dns/dns-troubleshoot.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ missing_linux_example
Summary
The documentation does not provide any platform-specific troubleshooting examples or commands. However, when discussing DNS resolution, it references using web-based tools (digwebinterface) and does not mention command-line tools like 'dig' or 'nslookup' for either Windows or Linux. There is no explicit Windows bias, but the lack of Linux-specific examples or mention of Linux tools (such as the 'dig' command) means Linux parity is not fully achieved.
Recommendations
  • Add troubleshooting examples using common Linux command-line tools such as 'dig' and 'nslookup'.
  • Include both Windows and Linux command-line examples for DNS queries and validation steps.
  • Explicitly mention platform-agnostic methods and clarify when steps apply to all operating systems.
  • Provide links to documentation for using DNS tools on both Windows and Linux.
GitHub Create Pull Request
Expressroute Quickstart: Create an ExpressRoute circuit and virtual network gateway with Terraform ...route/quickstart-create-expressroute-vnet-terraform.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for verifying results, but PowerShell is given equal prominence and detail, despite being Windows-centric. There are no Linux/macOS-specific instructions or troubleshooting notes. The CLI examples are cross-platform, but PowerShell is Windows-only, and its inclusion may suggest a slight Windows bias, especially for users unfamiliar with PowerShell.
Recommendations
  • Clearly indicate that Azure PowerShell is Windows-only and suggest alternatives for Linux/macOS users.
  • Place Azure CLI examples before PowerShell examples, as CLI is cross-platform.
  • Add troubleshooting notes or links for common Linux/macOS issues with Terraform and Azure CLI.
  • Consider including Bash scripting examples for resource verification, as Bash is native to Linux/macOS.
  • Explicitly state that all Terraform commands and Azure CLI steps work on Linux/macOS.
GitHub Create Pull Request
Firewall Azure Firewall Explicit proxy (preview) ...ure-docs/blob/main/articles/firewall/explicit-proxy.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page exhibits mild Windows bias by referencing Azure PowerShell as the primary deployment method in the 'Next steps' section, without mentioning equivalent Linux/macOS-friendly options (such as Azure CLI or ARM templates). There are no explicit examples or instructions tailored for Linux or macOS users, and Windows-centric tooling is referenced first.
Recommendations
  • Include instructions or links for deploying and configuring Azure Firewall using Azure CLI, which is cross-platform.
  • Mention ARM/Bicep template deployment options for platform neutrality.
  • Ensure examples and tooling references are presented in a platform-agnostic order, or provide parallel examples for Windows (PowerShell) and Linux/macOS (CLI).
  • Add notes clarifying that PowerShell is available on Linux/macOS, or suggest alternatives where appropriate.
GitHub Create Pull Request
Firewall Quickstart: Create an Azure Firewall and IP Groups - Terraform ...in/articles/firewall/quick-create-ipgroup-terraform.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation lists creation of a Windows VM and its password before the Linux VM in the checklist, but otherwise provides platform-neutral instructions and examples. No PowerShell, Windows-specific tools, or commands are present in the main workflow; Azure CLI is used for verification, which is cross-platform.
Recommendations
  • List Linux VM creation before Windows VM in the checklist to avoid implicit prioritization.
  • Explicitly state that all CLI commands are cross-platform and provide any necessary notes for Linux/macOS users (e.g., shell syntax differences if relevant).
  • If mentioning VM creation, clarify that both Windows and Linux VMs are supported and provide parity in example details if possible.
GitHub Create Pull Request
Firewall Configure Azure Firewall application rules with SQL FQDNs ...docs/blob/main/articles/firewall/sql-fqdn-filtering.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for configuring Azure Firewall application rules with SQL FQDNs. While Azure CLI is cross-platform, Azure PowerShell is primarily associated with Windows environments, and its inclusion may suggest a Windows-centric workflow. The order of presentation places Azure CLI first, which is positive for Linux parity, but the PowerShell section is detailed and assumes familiarity with Windows tooling. No Linux-specific tools or shell examples (e.g., Bash scripts) are provided, nor is there explicit mention of Linux/macOS compatibility for the CLI commands.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows.
  • Add Bash shell script examples or notes for Linux users where relevant.
  • Clarify that Azure PowerShell can be used on Linux/macOS (if true), or recommend Azure CLI for non-Windows users.
  • Consider including troubleshooting or environment setup notes for Linux/macOS users.
GitHub Create Pull Request
Firmware Analysis Create a firmware analysis workspace using Bicep ...irmware-analysis/quickstart-firmware-analysis-bicep.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for all major steps, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and is presented as a primary option throughout. There are no explicit Linux/macOS shell examples (e.g., bash), nor is there mention of platform-specific nuances for Linux/macOS users. The CLI instructions are generic and work cross-platform, but the presence and parity of PowerShell examples may suggest a slight Windows bias.
Recommendations
  • Clarify that Azure CLI commands work natively on Linux/macOS and Windows, while PowerShell is primarily for Windows (with cross-platform support, but less common on Linux/macOS).
  • Add explicit bash/zsh examples or notes for Linux/macOS users, especially for variable assignment and file paths.
  • Note any platform-specific considerations (e.g., file path syntax differences, installation instructions for Azure CLI/PowerShell on Linux/macOS).
  • Consider listing Azure CLI examples first, as it is the most cross-platform tool.
  • Add a short section or callout confirming Linux/macOS support and linking to relevant installation guides.
GitHub Create Pull Request
Frontdoor Secure your Origin with Private Link in Azure Front Door Premium ...zure-docs/blob/main/articles/frontdoor/private-link.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation mentions Azure PowerShell as a method for approving private endpoint connections alongside Azure CLI and Azure Portal, listing PowerShell before CLI. No explicit Linux/macOS examples or tools are highlighted, and no command-line examples are shown at all. The documentation does not provide parity guidance for Linux users or clarify cross-platform equivalence for management tasks.
Recommendations
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Provide example commands for both Azure CLI and Azure PowerShell, with CLI examples shown first or side-by-side.
  • Clarify that all management actions (approval, removal, etc.) can be performed equally on Linux/macOS using Azure CLI.
  • Add a note or section on platform compatibility for management tools.
GitHub Create Pull Request
Firmware Analysis What's new in firmware analysis .../blob/main/articles/firmware-analysis/release-notes.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page shows a mild Windows bias, particularly in the March 2024 update, where Azure CLI and PowerShell commands are mentioned for automating firmware analysis workflows. PowerShell is a Windows-centric tool, and its mention alongside Azure CLI (which is cross-platform) may suggest a preference for Windows tooling. There are no explicit Linux/macOS command examples, nor is Bash or shell scripting referenced. Additionally, Windows tools (PowerShell) are mentioned before Linux equivalents, and there is no evidence of Linux-specific guidance or parity in automation examples.
Recommendations
  • Add explicit Bash/shell command examples for Linux/macOS users alongside PowerShell examples.
  • Clarify that Azure CLI is cross-platform and provide sample usage on Linux/macOS.
  • If PowerShell is required for certain tasks, note its availability on Linux/macOS and provide installation guidance.
  • Review other sections for implicit Windows-first language and ensure equal visibility for Linux/macOS workflows.
GitHub Create Pull Request
Frontdoor Endpoints in Azure Front Door ...cs/azure-docs/blob/main/articles/frontdoor/endpoint.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for configuring endpoint domain reuse, but PowerShell (a Windows-centric tool) is given equal prominence to the CLI. The CLI is cross-platform, but PowerShell is primarily associated with Windows. No Linux/macOS-specific shell examples (such as Bash) are given, and PowerShell is presented before Bicep, which is platform-neutral. There are no explicit Linux/macOS instructions or notes.
Recommendations
  • Emphasize Azure CLI as the primary example since it is cross-platform and works natively on Linux/macOS.
  • Add explicit Bash or shell script examples for Linux/macOS users, if relevant.
  • Clarify that Azure CLI commands work on all platforms, and note any platform-specific requirements for PowerShell.
  • Consider listing Azure CLI examples before PowerShell to reduce perceived Windows-first bias.
  • Add a note or section for Linux/macOS users to ensure parity and clarity.
GitHub Create Pull Request
Frontdoor Configure HTTPS on Front Door (classic) custom domain ...n/articles/frontdoor/front-door-custom-domain-https.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page demonstrates mild Windows bias by presenting PowerShell instructions and references before Azure CLI equivalents, and by using PowerShell as the default example in several sections. However, Azure CLI instructions are provided for most tasks, and the use of Azure Cloud Shell mitigates platform-specific issues. There are no Windows-only tools or patterns, and Linux/macOS users can complete all tasks using the CLI or portal.
Recommendations
  • Present Azure CLI and PowerShell instructions side-by-side or in a neutral order, rather than defaulting to PowerShell first.
  • Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and is accessible from any OS.
  • Add a brief note clarifying that all steps can be completed on Linux/macOS using Azure CLI and Cloud Shell.
  • Where possible, use generic terms like 'command line' or 'terminal' instead of 'PowerShell' when referring to cross-platform actions.
GitHub Create Pull Request
Frontdoor Azure Front Door ...cs/blob/main/articles/frontdoor/front-door-overview.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page for Azure Front Door demonstrates mild Windows bias. In the 'Deliver modern apps and architectures' section, PowerShell is explicitly mentioned as a supported DevOps tool, and it is listed before other cross-platform tools like CLI, Bicep, and ARM templates. There are no explicit Linux/macOS examples or tools highlighted, and no mention of Bash, shell scripting, or Linux-specific patterns. However, the bias is limited to tool listing order and does not prevent Linux/macOS users from understanding or using the service.
Recommendations
  • Explicitly mention Bash or shell scripting alongside PowerShell when listing supported DevOps tools.
  • Provide example commands for both Azure CLI and PowerShell in relevant sections.
  • Ensure that cross-platform tools (e.g., Azure CLI, Bicep) are listed before or alongside Windows-specific tools like PowerShell.
  • Add a note clarifying that all major features are accessible from Linux/macOS environments using Azure CLI and SDKs.
GitHub Create Pull Request
Governance View Machine Configuration Compliance Reporting ...rnance/machine-configuration/how-to/view-compliance.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page provides a generally cross-platform overview of Azure Machine Configuration compliance reporting, but there is a mild Windows bias. PowerShell is the only shell-specific example referenced (Get-AzGuestConfigurationAssignment), and Windows-centric tooling (PowerShell cmdlet) is listed before Linux/macOS equivalents in the programmatic access table. CLI examples (az CLI) are present, but no Bash or Linux-specific shell examples are shown. The documentation does not explicitly mention Linux/macOS compatibility or provide parity in example commands for those platforms.
Recommendations
  • Add explicit Bash or shell examples for Linux/macOS users alongside PowerShell examples.
  • Clarify that az CLI and REST API are cross-platform and provide example usage on Linux/macOS.
  • List Linux/macOS tools (az CLI, REST API) before or alongside PowerShell cmdlets in tables and references.
  • Include screenshots or walkthroughs from Linux/macOS environments where applicable.
  • State platform compatibility for each tool or API referenced.
GitHub Create Pull Request
Governance How to sign machine configuration packages ...ration/how-to/develop-custom-package/6-sign-package.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation demonstrates a mild Windows bias: Windows/Powershell examples and instructions are presented first, with detailed PowerShell scripts and references to Windows certificate stores. Linux instructions are present but less detailed and still use PowerShell for some steps, which is less common for Linux users. Windows tools and patterns (certificate stores, PowerShell cmdlets) are mentioned before their Linux equivalents, and Azure Policy examples reference Windows resources first.
Recommendations
  • Present Linux and Windows instructions in parallel or alternate order to avoid Windows-first bias.
  • Provide Linux-native command-line examples (e.g., using OpenSSL for certificate management) instead of PowerShell for Linux steps.
  • Expand Linux sections to include more detail on certificate/key management, installation, and verification using standard Linux tools.
  • Reference Linux-specific Azure Policy templates and documentation where available.
  • Clarify when PowerShell is required on Linux and suggest alternatives if possible.
GitHub Create Pull Request
Hdinsight Quickstart: Query Apache HBase in Azure HDInsight - HBase Shell ...ticles/hdinsight/hbase/query-hbase-with-hbase-shell.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page shows a mild Windows bias by presenting the SSH connection example using the Windows command prompt format (`cmd`) and not providing explicit Linux/macOS terminal examples. The SSH client prerequisite links to a Unix-focused guide, but the actual example uses Windows syntax. No PowerShell or Windows-specific tools are mentioned beyond this, and the HBase shell usage is platform-neutral.
Recommendations
  • Provide both Windows (cmd/PowerShell) and Linux/macOS (bash) SSH connection examples, or use a platform-neutral format.
  • Clarify that the SSH command works on Linux/macOS terminals as well as Windows, and mention common SSH clients for each OS.
  • If referencing deletion via PowerShell, also show equivalent Azure CLI and portal steps for Linux/macOS users, or link directly to cross-platform instructions.
GitHub Create Pull Request
Hdinsight Cluster capacity planning in Azure HDInsight ...main/articles/hdinsight/hdinsight-capacity-planning.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page demonstrates mild Windows bias by mentioning PowerShell scripting and Azure Automation as methods for cluster lifecycle management, without providing equivalent Linux/macOS CLI or scripting examples. Windows tools are referenced before any Linux alternatives, and no Bash or Azure CLI examples are given for provisioning or deleting clusters. However, the majority of the documentation is platform-neutral and focuses on Azure portal usage and general concepts.
Recommendations
  • Include Azure CLI and Bash script examples for cluster provisioning and deletion alongside PowerShell.
  • Explicitly mention that Azure Automation can run scripts written in Bash or Python, not just PowerShell.
  • Add links or references to Linux/macOS-specific guidance for HDInsight cluster management.
  • Ensure that scripting examples are provided for both Windows and Linux environments in future updates.
GitHub Create Pull Request
Hdinsight Create virtual networks for Azure HDInsight clusters ...articles/hdinsight/hdinsight-create-virtual-network.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation presents both Azure PowerShell and Azure CLI examples for creating and configuring virtual networks and network security groups, but consistently lists PowerShell (Windows-centric) examples before CLI (cross-platform). The PowerShell script is more detailed and comprehensive, while the CLI steps are more segmented. There are no Linux shell or Bash examples for Azure management tasks, though DNS configuration examples are Linux-focused. The prerequisites mention both PowerShell and CLI, but PowerShell is listed first. Overall, Windows/PowerShell is given slight precedence, but Linux users can complete all tasks using Azure CLI and DNS instructions.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples to emphasize cross-platform parity.
  • Add Bash shell examples for Azure CLI usage where appropriate.
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows.
  • Balance the detail level between PowerShell and CLI examples, ensuring CLI instructions are as comprehensive.
  • Consider adding a table comparing PowerShell and CLI commands for each major step.
GitHub Create Pull Request
Hdinsight Customize Azure HDInsight clusters by using script actions .../hdinsight/hdinsight-hadoop-customize-cluster-linux.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides examples and guidance for both Azure PowerShell and Azure CLI, but PowerShell examples and references are consistently presented before CLI equivalents. Output and cmdlet examples are shown for PowerShell, while CLI examples are present but less detailed. There is a slight Windows-first bias in the ordering and depth of examples, but Linux parity is mostly maintained since Bash scripts are the core mechanism and CLI instructions are included.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples, especially in sections where both are supported.
  • Expand Azure CLI examples to match the detail and output shown for PowerShell, including sample outputs and step-by-step instructions.
  • Explicitly state that Azure CLI is cross-platform and highlight its usage for Linux/macOS users.
  • Add a summary table comparing PowerShell and CLI commands for common tasks.
  • Ensure that all code samples and walkthroughs are available for both PowerShell and CLI, with equal prominence.
GitHub Create Pull Request