← Back to Dashboard
1642
Pages Scanned
456
Pages Flagged
1642
Changed Pages
27.8%
% Pages Flagged

Scan Information

Started At: 2026-01-14 01:31:52

Finished At: 2026-01-14 02:19:06

Status: completed

Target Repo: Azure Compute

Current Phase: discovery

Files Queued: 1642

Files Completed: 1642

Problematic Pages

456 issues found
Service Fabric Install Service Fabric standalone client ...bric-tutorial-standalone-create-service-fabric-cluster.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 is heavily biased towards Windows, with all examples, scripts, and configuration steps tailored exclusively for Windows environments. Only Windows Server setup packages are referenced, and all instructions use PowerShell scripts and Windows file paths. There is no mention of Linux or macOS equivalents, nor any guidance for non-Windows users.
Recommendations
  • Provide equivalent instructions and setup packages for Linux and macOS environments.
  • Include bash or shell script examples alongside PowerShell commands.
  • Document Linux-specific configuration file paths and deployment steps.
  • Clarify OS limitations or support status for Service Fabric standalone clusters.
  • Add a section explicitly addressing cross-platform setup, or link to Linux/macOS guides if available.
GitHub Create Pull Request
Service Fabric Clean up a standalone cluster ...-fabric/service-fabric-tutorial-standalone-clean-up.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 describes the cluster removal process using Windows-specific tools (RDP, PowerShell, .ps1 scripts) and does not mention or provide instructions for Linux or macOS environments. There are no Linux shell or cross-platform alternatives, and the workflow assumes Windows as the default platform.
Recommendations
  • Add instructions for connecting to the VM via SSH for Linux/macOS users.
  • Provide equivalent commands or scripts for Bash or other Linux shells.
  • Clarify whether the removal script (.ps1) can be run with PowerShell Core on Linux/macOS, or provide an alternative.
  • Explicitly mention platform requirements and offer guidance for non-Windows users.
  • Present cross-platform instructions side-by-side, or note differences where applicable.
GitHub Create Pull Request
Virtual Machines Desired State Configuration extension with Azure Resource Manager templates ...n/articles/virtual-machines/extensions/dsc-template.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 oriented toward Windows environments, with all examples and references using PowerShell DSC, Windows-specific extension publishers, and Windows VM types. There are no examples or guidance for Linux VMs, nor mention of Linux equivalents or cross-platform DSC solutions. Windows terminology and tools are used exclusively, and the documentation does not address Linux user needs.
Recommendations
  • Add explicit examples for deploying DSC extension on Linux VMs, if supported, or clarify that it is Windows-only.
  • Mention Linux configuration management alternatives (such as Azure VM extensions for Chef, Puppet, or Ansible) and link to their documentation.
  • If DSC extension is not supported on Linux, state this clearly at the beginning of the document.
  • Provide parity in troubleshooting and settings sections by including Linux-specific notes or alternatives.
  • Ensure that cross-platform users are guided to appropriate solutions for Linux/macOS environments.
GitHub Create Pull Request
Service Fabric Run a script when an Azure Service Fabric service starts ...fabric/service-fabric-run-script-at-service-startup.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 Windows-centric, with all code and scripting examples using Windows batch files (.bat), PowerShell commands, and Windows-specific tools (setx, REG). Visual Studio instructions and file paths are Windows-only. Linux is mentioned only briefly in passing, with no concrete Linux shell script examples, file system paths, or equivalent Linux debugging instructions. There are no bash/sh examples, and no guidance for Linux/macOS users on how to achieve the same outcomes.
Recommendations
  • Add equivalent Linux examples using bash/sh scripts for SetupEntryPoint (e.g., MySetup.sh).
  • Show how to set environment variables and output files in Linux (using export, echo, etc.).
  • Provide Linux file system paths for locating output and log files.
  • Include instructions for Linux clusters on how to add scripts to the service package and set permissions.
  • Offer debugging guidance for Linux (e.g., redirecting stdout/stderr in bash, location of log files).
  • Clarify differences in user/account configuration between Windows and Linux clusters, with concrete Linux manifest snippets.
GitHub Create Pull Request
Service Fabric Scale up an Azure Service Fabric non-primary node type ...abric/service-fabric-scale-up-non-primary-node-type.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 biased towards Windows environments, with all command-line examples provided in PowerShell and explicit references to Windows file paths and certificate stores. There are no equivalent instructions or examples for Linux or macOS users, nor any mention of cross-platform Azure CLI usage. The VM upgrade scenario itself only references Windows Server SKUs, with no guidance for Linux-based Service Fabric clusters.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and works on Linux/macOS.
  • Include instructions for generating and managing certificates on Linux/macOS (e.g., using OpenSSL instead of PowerShell's Import-PfxCertificate).
  • Provide examples for upgrading Linux-based Service Fabric node types, including references to common Linux VM images.
  • Use generic file paths and avoid hardcoding Windows-specific locations (e.g., C:\certificates).
  • Explicitly state platform requirements and offer links to Linux/macOS setup guides where relevant.
GitHub Create Pull Request
Service Fabric Tutorial: Deploy a Service Fabric app to a cluster in Azure ...s/service-fabric/service-fabric-tutorial-deploy-app.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 tutorial is heavily oriented toward Windows environments, specifically Visual Studio and Windows-centric workflows. All deployment steps and screenshots use Visual Studio, with no mention of Linux/macOS alternatives. Windows tools (Visual Studio, certificate store, PFX files) are referenced exclusively, and PowerShell is mentioned before Azure CLI. There are no instructions or examples for deploying from Linux or macOS, nor guidance for using cross-platform Service Fabric tools.
Recommendations
  • Add instructions for deploying Service Fabric applications from Linux/macOS, using Azure CLI or Service Fabric CLI (sfctl).
  • Include examples for certificate creation and management on Linux/macOS (e.g., using OpenSSL).
  • Provide guidance for building and publishing Service Fabric applications using cross-platform .NET CLI tools.
  • Mention Visual Studio Code as an alternative editor for non-Windows users.
  • Reorder references to Azure CLI and PowerShell so that cross-platform tools are not secondary.
  • Clarify which steps are Windows-only and offer Linux/macOS equivalents where possible.
GitHub Create Pull Request
Service Fabric Tutorial: Add an HTTPS endpoint by using Kestrel ...rvice-fabric-tutorial-dotnet-app-enable-https-endpoint.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 biased towards Windows environments. All certificate management, access control, and deployment steps rely on Windows-specific tools (PowerShell, certlm.msc, batch files, Windows certificate store paths). There are no examples or guidance for performing these steps on Linux or macOS cluster nodes, nor any mention of cross-platform alternatives. The use of Windows tools and scripting is assumed throughout, making it difficult for Linux/macOS users to follow or adapt the tutorial.
Recommendations
  • Provide equivalent instructions for Linux clusters, including certificate creation, import, and access control using Linux tools (e.g., OpenSSL, chmod, chown).
  • Include cross-platform PowerShell Core examples or bash scripts where possible.
  • Document how Service Fabric on Linux handles certificate stores and service identities.
  • Clarify which steps are Windows-only and offer Linux/macOS alternatives or references.
  • Add notes on how to adapt the setup scripts for Linux containers or nodes.
GitHub Create Pull Request
Service Fabric How to migrate to TLS (Transport Layer Security) 1.3 for Service Fabric ...vice-fabric/how-to-migrate-transport-layer-security.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_only ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation is explicitly Windows-centric, stating that Linux is not supported for TLS 1.3 migration in Service Fabric clusters. All prerequisites and steps reference Windows Server, PowerShell, and Windows compatibility modes, with no mention of Linux equivalents, examples, or guidance. Linux users are informed at the outset that the process is unsupported, and no alternative paths or parity information is provided.
Recommendations
  • Clearly indicate current and future Linux support status, including timelines if possible.
  • Provide Linux-specific guidance or a migration path, even if partial or in preview.
  • Include examples and instructions for Linux clusters where feasible, or link to relevant Linux documentation.
  • If Linux support is unavailable, suggest alternative approaches or workarounds for Linux users.
  • Ensure parity in documentation structure and examples for both Windows and Linux platforms.
GitHub Create Pull Request
Service Fabric Initializer CodePackages in Service Fabric ...in/articles/service-fabric/initializer-codepackages.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 strong Windows bias: all examples use Windows containers, Windows-specific images (nanoserver), Windows file paths, and Windows shell commands (cmd, type, ping). The only complete example is for Windows, with no mention of Linux container equivalents or cross-platform patterns. The introductory note explicitly references Windows container application creation and links to Windows-specific compatibility guidance.
Recommendations
  • Add parallel examples using Linux containers (e.g., Ubuntu or Alpine images) with Linux shell commands.
  • Include guidance on specifying Linux file paths and volume mounts (e.g., /workspace/log.txt).
  • Reference cross-platform container creation guides, not just Windows-focused ones.
  • Clarify whether Initializer CodePackages are supported for Linux containers and, if so, provide Linux-specific configuration and troubleshooting notes.
  • Present Windows and Linux examples side-by-side or in separate sections to improve parity.
GitHub Create Pull Request
Service Fabric Deploy a Service Fabric cluster using the Azure portal ...es/service-fabric/quickstart-classic-cluster-portal.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation exclusively guides users to deploy a Service Fabric cluster using Windows Server 2019-Datacenter virtual machines. There are no instructions, options, or examples for deploying Linux-based clusters, nor any mention of Linux as an alternative. The operating system selection is hardcoded to Windows, and all steps assume a Windows environment, which creates friction for Linux/macOS users.
Recommendations
  • Include instructions and screenshots for deploying Service Fabric clusters on Linux (Ubuntu) VM images.
  • Present both Windows and Linux options when selecting the operating system, with clear guidance for each.
  • Add notes or sections describing differences in certificate handling and access for Linux users.
  • Ensure parity in validation and cleanup steps for Linux clusters.
  • Consider providing links to Linux-specific quickstarts or documentation.
GitHub Create Pull Request
Service Fabric Create a Service Fabric cluster using Bicep ...in/articles/service-fabric/quickstart-cluster-bicep.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 biased towards Windows and PowerShell. All example commands use PowerShell, including certificate creation and Azure resource deployment. The certificate helper script is a PowerShell (.ps1) script, and there are no Bash, Azure CLI, or Linux/macOS-specific instructions for key steps like certificate generation or deployment. Windows terminology and tools are used throughout, and Windows is referenced as the cluster OS. Linux alternatives are not mentioned, and the only CLI example appears at the very end for resource deletion.
Recommendations
  • Provide equivalent instructions and examples using Azure CLI and Bash for Linux/macOS users.
  • Offer a cross-platform certificate creation method (e.g., using OpenSSL and Azure CLI to upload certificates to Key Vault).
  • Clearly indicate which steps are Windows-specific and provide Linux/macOS alternatives where possible.
  • Include notes or tabs for both PowerShell and Bash/CLI workflows throughout the guide, not just for resource deletion.
  • Mention Linux clusters and how to deploy them, or clarify the scope if only Windows clusters are supported.
GitHub Create Pull Request
Service Fabric Create a Service Fabric cluster using Azure Resource Manager template ...articles/service-fabric/quickstart-cluster-template.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 biased towards Windows and PowerShell. All command-line examples use PowerShell, and the certificate creation script is a PowerShell (.ps1) script with no mention of Linux/macOS alternatives. The instructions assume the use of Windows tools and environments, and there are no CLI/bash or cross-platform instructions for key steps such as certificate generation or template deployment. Linux/macOS users are left without guidance for completing the quickstart.
Recommendations
  • Provide equivalent Azure CLI examples for all deployment steps, including signing in, resource group creation, Key Vault setup, and ARM template deployment.
  • Offer a cross-platform certificate creation method (e.g., using OpenSSL and Azure CLI to upload certificates to Key Vault).
  • Explicitly mention Linux/macOS compatibility and provide instructions or scripts for those platforms.
  • Reorder or parallelize examples so that Windows and Linux/macOS instructions are presented together, rather than Windows-first.
GitHub Create Pull Request
Service Fabric Quickly deploy an existing app to a cluster ...b/main/articles/service-fabric/quickstart-guest-app.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 Windows-centric, focusing exclusively on Visual Studio for Windows, referencing Windows-specific path limitations, and mentioning PowerShell scripts for deployment. There are no instructions or examples for Linux/macOS users, nor any mention of cross-platform tooling or alternatives to Visual Studio and PowerShell.
Recommendations
  • Add instructions for deploying from Linux/macOS, including using Service Fabric CLI (sfctl) and/or Azure CLI.
  • Provide examples for setting up and deploying Node.js apps to Service Fabric clusters using cross-platform tools.
  • Mention and link to Linux/macOS compatible SDKs and development environments.
  • Include notes on path limitations for Linux/macOS, if relevant, or clarify that the issue is Windows-specific.
  • Offer alternative deployment scripts (e.g., Bash) or document how to use PowerShell Core on non-Windows platforms.
GitHub Create Pull Request
Service Fabric RunToCompletion semantics and specifications ...blob/main/articles/service-fabric/run-to-completion.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 strong Windows bias. All code examples use Windows containers and Windows-specific commands (cmd, set, exit, etc.), with explicit references to Windows container images. The only tooling example for querying deployment status is PowerShell, with no mention of Linux or cross-platform alternatives. There are no Linux container examples, nor any guidance for running on Linux or macOS environments.
Recommendations
  • Add equivalent examples using Linux containers (e.g., Ubuntu or Alpine images) with shell commands.
  • Include instructions and code snippets for querying deployment status using Linux tools (e.g., Azure CLI, Bash scripts) or cross-platform Service Fabric SDKs.
  • Clarify RunToCompletion support and limitations for Linux-based Service Fabric clusters.
  • Present Windows and Linux examples side-by-side, or clearly indicate platform-specific sections.
  • Reference Linux container compatibility and versioning where relevant.
GitHub Create Pull Request
Service Fabric Create infrastructure for a cluster on Azure VMs ...fabric-tutorial-standalone-azure-create-infrastructure.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 is heavily biased towards Windows environments. All VM creation instructions specify Windows Server as the image, and all connection, configuration, and verification steps use Windows-specific tools (RDP, PowerShell, Command Prompt, SMB). There are no examples or guidance for Linux-based VMs or tools (e.g., SSH, Linux firewall commands), making it difficult for Linux/macOS users to follow the tutorial or adapt it to their platforms.
Recommendations
  • Provide parallel instructions for creating Linux VM instances, including recommended Linux distributions.
  • Include examples for connecting to Linux VMs using SSH, and for configuring firewalls using Linux commands (e.g., ufw, iptables).
  • Add verification steps using Linux tools (e.g., ping, smbclient, mounting shares via CIFS).
  • Clarify which steps are Windows-specific and offer Linux/macOS alternatives where possible.
  • Mention that Service Fabric clusters can be hosted on Linux VMs and link to relevant documentation.
GitHub Create Pull Request
Service Fabric Configure the upgrade of a Service Fabric application ...abric/service-fabric-visualstudio-configure-upgrade.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 is heavily focused on Windows-centric tools and workflows, specifically Visual Studio and PowerShell. All upgrade instructions and examples assume the use of Visual Studio (a Windows-only IDE) and PowerShell (primarily a Windows shell), with no mention of Linux/macOS alternatives or cross-platform command-line tools. There are no examples or guidance for performing Service Fabric application upgrades on Linux or macOS, nor are equivalent Linux tools or workflows referenced.
Recommendations
  • Add instructions and examples for upgrading Service Fabric applications using cross-platform tools such as Azure CLI or REST APIs.
  • Include Linux/macOS-specific workflows for configuring upgrade parameters and health check policies, possibly using command-line editors and deployment scripts.
  • Provide parity in examples, showing both PowerShell and Bash (or other Linux shell) commands where applicable.
  • Clarify which steps are Windows-only and offer alternatives for non-Windows users.
  • Reference documentation for Service Fabric on Linux clusters, if available.
GitHub Create Pull Request
Service Fabric Configure secure Azure Service Fabric cluster connections ...rvice-fabric-visualstudio-configure-secure-connections.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 oriented towards Windows environments, with instructions and examples focused on Visual Studio, PowerShell, and Windows certificate stores. There are no Linux/macOS equivalents provided for certificate installation, cluster connection, or publishing workflows, making it difficult for non-Windows users to follow the guide.
Recommendations
  • Add instructions for installing client certificates on Linux/macOS (e.g., using openssl or certutil).
  • Provide examples for connecting to Service Fabric clusters using cross-platform tools (such as Azure CLI or Service Fabric CLI) instead of only PowerShell.
  • Include guidance for publishing Service Fabric applications from non-Windows environments, if supported.
  • Mention Linux/macOS certificate store locations and how to specify them in publish profiles.
  • Clarify whether Visual Studio Code or other cross-platform IDEs can be used, and provide relevant steps if possible.
GitHub Create Pull Request
Service Fabric Run a service under system and local security accounts ...ce-fabric/service-fabric-application-runas-security.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 focuses on Service Fabric's ability to run services under system and local security accounts, but it is heavily oriented toward Windows environments. It references Windows-specific account types (LocalUser, NetworkService, LocalService, LocalSystem), Active Directory domain accounts, and group managed service accounts, with no mention of Linux equivalents or guidance for Linux clusters. All examples and terminology are Windows-centric, and there are no instructions or examples for Linux/macOS users.
Recommendations
  • Add explicit guidance for running Service Fabric services under local/system accounts on Linux clusters, including supported account types and configuration differences.
  • Provide Linux-specific examples and clarify any limitations or differences in account management between Windows and Linux Service Fabric clusters.
  • Reference Linux tools and patterns (such as systemd, useradd, groupadd, etc.) where appropriate, and explain how to achieve similar security configurations on Linux.
  • Clearly indicate which features or examples are Windows-only, and provide parity or alternatives for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Troubleshooting application upgrades ...https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-application-upgrade-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 exclusively uses PowerShell commands and outputs for all troubleshooting and recovery steps, with no mention of Linux/macOS equivalents (such as Service Fabric CLI or REST API). All example commands and tooling references are Windows-centric, and the 'Next steps' section prioritizes Visual Studio and PowerShell tutorials, both Windows-focused, without Linux alternatives.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • Include REST API usage for troubleshooting and upgrade operations, as these are platform-agnostic.
  • Explicitly mention Linux/macOS support and provide guidance for users on those platforms.
  • Reorder or balance 'Next steps' to include Linux/macOS tooling (e.g., CLI, VS Code) alongside Windows tools.
  • Where PowerShell commands are shown, provide parallel CLI or REST API commands and outputs.
GitHub Create Pull Request
Service Fabric Advanced Application Upgrade Topics ...-fabric/service-fabric-application-upgrade-advanced.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 for all command-line examples and references, with no mention of Linux/macOS equivalents or cross-platform CLI tools. Windows-centric tools and workflows (PowerShell, Visual Studio) are referenced throughout, and there is a lack of guidance for Linux users on how to perform the same tasks. The page assumes the reader is using Windows environments and does not provide parity for Linux/macOS users.
Recommendations
  • Add equivalent examples using Azure CLI (az sf) or REST API for all PowerShell cmdlets, especially for service creation, upgrades, and parameter changes.
  • Explicitly mention cross-platform alternatives where available, and clarify which features are available on Linux clusters.
  • Include bash or shell script examples for Linux users, and document any differences in workflow or tooling.
  • Reference Linux/macOS compatible tools (such as Service Fabric CLI or SDK) alongside Windows tools like PowerShell and Visual Studio.
  • Reorganize examples so that Windows and Linux approaches are presented side-by-side, or clarify platform-specific instructions.
GitHub Create Pull Request
Service Fabric On-demand backup in Azure Service Fabric ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-backup-restore-service-ondemand-backup.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 is heavily biased towards Windows and PowerShell. All command-line examples use PowerShell syntax and Windows-specific modules, with no mention of Linux/macOS equivalents or cross-platform alternatives. The prerequisites and workflow are described exclusively in terms of PowerShell modules and commands, and REST API usage is shown only via PowerShell. There is no guidance for Bash, CLI, or other Linux-native tools, nor any indication of how to perform these tasks on non-Windows platforms.
Recommendations
  • Provide equivalent examples using Bash/cURL for REST API calls, suitable for Linux/macOS users.
  • Document how to connect to Service Fabric clusters and trigger backups using cross-platform tools such as Azure CLI or direct REST API calls.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is required or if REST API calls can be made directly from any platform.
  • Add a section or note explicitly addressing Linux/macOS usage, including any prerequisites or limitations.
  • Ensure that examples are presented in a platform-neutral way, or provide both Windows and Linux/macOS examples side by side.
GitHub Create Pull Request
Service Fabric Periodic backup/restore in standalone Azure Service Fabric ...bric-backuprestoreservice-quickstart-standalonecluster.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 is heavily biased towards Windows environments. All command-line examples use PowerShell and Windows-specific modules (Microsoft.ServiceFabric.PowerShell.Http). Prerequisites and instructions reference Windows Server and Windows certificate stores. There are no Linux or cross-platform CLI examples, and a caveat explicitly states no support for Service Fabric clusters on Linux. Windows tools and patterns are mentioned exclusively and first throughout.
Recommendations
  • Clearly state Linux/macOS limitations at the top of the page.
  • Provide equivalent instructions and examples for Linux clusters if/when support is available.
  • Offer REST API examples using cross-platform tools (e.g., curl, Python requests) instead of only PowerShell.
  • Reference Linux-compatible certificate management and storage options.
  • If Linux is unsupported, link to documentation explaining alternatives or workarounds for Linux users.
GitHub Create Pull Request
Service Fabric Periodic backup and restore in Azure Service Fabric ...ce-fabric-backuprestoreservice-quickstart-azurecluster.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 biased towards Windows, with all command-line examples using PowerShell and the Microsoft.ServiceFabric.Powershell.Http module. There are no Linux or cross-platform CLI examples, and the prerequisites and instructions assume a Windows environment (e.g., certificate store locations, PowerShell modules). The limitation section explicitly states no support for Service Fabric clusters on Linux, making the instructions unusable for Linux users.
Recommendations
  • Add equivalent instructions and examples for Linux environments, using bash, Azure CLI, or REST API calls with curl.
  • Clarify which features are Windows-only and provide alternative approaches or workarounds for Linux users where possible.
  • Document certificate management steps for Linux (e.g., using OpenSSL and Linux certificate stores).
  • If PowerShell is required, mention PowerShell Core and its cross-platform capabilities, or provide REST API examples that work on any OS.
  • Update limitation/caveat section to link to Linux-specific documentation or roadmap if available.
GitHub Create Pull Request
Service Fabric Configure your Azure Service Fabric standalone cluster ...cles/service-fabric/service-fabric-cluster-manifest.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, with configuration examples, tools, and instructions tailored to Windows Server. There are no Linux-specific instructions, examples, or references, and Windows tools and patterns (e.g., ipconfig, netsh, C:\ paths, ETW tracing) are mentioned exclusively. The page title and content reinforce that the guidance is for Windows clusters, and Linux parity is not addressed.
Recommendations
  • Add explicit guidance and examples for configuring Service Fabric clusters on Linux, including Linux-specific ClusterConfig.json samples.
  • Include Linux equivalents for commands (e.g., use 'ip addr' or 'hostname -I' instead of 'ipconfig', and reference Linux file paths like '/var/sf/diagnostics').
  • Mention Linux-compatible diagnostic and logging tools, and provide links to relevant documentation.
  • Clarify in the introduction whether Linux clusters are supported, and if not, provide a link to Linux-specific documentation or state the limitation.
  • Present examples for both Windows and Linux side-by-side where possible, or alternate which platform is shown first.
GitHub Create Pull Request
Service Fabric Overview of Azure and standalone Service Fabric clusters ...icles/service-fabric/service-fabric-deploy-anywhere.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation mentions both Windows Server and Linux as supported platforms for Service Fabric clusters, but it notes that standalone clusters are not available on Linux. There are no Linux-specific examples, tools, or operational patterns discussed, and the focus is primarily on Azure and Windows environments. The lack of Linux standalone support is a significant limitation for Linux users.
Recommendations
  • Clearly state the lack of standalone cluster support on Linux at the beginning of the page.
  • Provide alternative guidance or links for Linux users, such as how to deploy Service Fabric clusters on Azure using Linux nodes.
  • Include a comparison table summarizing feature parity and limitations between Windows and Linux.
  • Add Linux-specific operational examples or reference documentation for managing clusters on Linux within Azure.
GitHub Create Pull Request
Service Fabric Create a cluster using certificate common name ...-fabric/service-fabric-create-cluster-using-cert-cn.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 exclusively uses PowerShell scripts and Windows file paths for all certificate and deployment operations, with no mention of Linux/macOS equivalents (such as Bash, Azure CLI, or cross-platform tooling). Windows-centric tools and patterns are presented first and solely, creating friction for Linux/macOS users who cannot directly follow the instructions.
Recommendations
  • Provide equivalent Azure CLI or Bash examples for certificate upload and template deployment steps.
  • Use cross-platform file paths in examples (e.g., /home/user/myclustercert.pfx) or clarify that paths should be adapted for non-Windows systems.
  • Explicitly mention that PowerShell scripts are for Windows and link to Linux/macOS instructions where available.
  • Add notes or sections for Linux/macOS users, including prerequisites and alternative commands.
GitHub Create Pull Request
Service Fabric Debug your application in Visual Studio ...ce-fabric/service-fabric-debugging-your-application.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 and Visual Studio workflows, with all examples, screenshots, and instructions tailored to Windows users. There is exclusive mention of Windows-specific tools (Visual Studio, Cloud Explorer, ServiceEventSource.cs, Start-Service.ps1), and no Linux/macOS equivalents or alternative debugging workflows are provided. The only nod to cross-platform is a brief selector for Eclipse/Java, but the main content is entirely Windows-centric.
Recommendations
  • Add equivalent instructions and examples for Linux/macOS users, including how to debug Service Fabric applications using cross-platform tools (e.g., VS Code, JetBrains Rider, command-line debuggers).
  • Provide guidance for running and debugging Service Fabric applications on local clusters in Linux environments.
  • Replace or supplement PowerShell script examples with Bash or shell script equivalents.
  • Include screenshots and workflow steps for non-Windows platforms.
  • Clarify which features are Windows-only and suggest alternatives for Linux/macOS users.
GitHub Create Pull Request
Virtual Machines Attach an existing OS disk to a VM .../blob/main/articles/virtual-machines/attach-os-disk.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 is heavily biased towards Windows, with all examples and instructions using PowerShell and Windows-specific patterns. There are no Linux or cross-platform CLI examples, and the workflow is described only for Windows VMs. The use of Windows terminology and tools (e.g., RDP, PowerShell cmdlets) excludes Linux users and does not mention Linux-specific considerations or alternatives.
Recommendations
  • Add Azure CLI and/or Bash examples for creating and attaching disks to VMs, applicable to Linux VMs.
  • Include instructions for attaching a specialized disk to a Linux VM, highlighting differences (e.g., SSH instead of RDP, Linux OS disk flags).
  • Clearly indicate which steps are OS-agnostic and which are Windows-specific, and provide Linux/macOS equivalents where needed.
  • Mention Linux-specific troubleshooting or configuration notes (e.g., hostname changes, SSH key handling).
  • Reorganize the documentation so that cross-platform or OS-neutral steps are presented first, followed by OS-specific details.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Event Store ...ervice-fabric/service-fabric-diagnostics-eventstore.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, with explicit notes stating that EventStore APIs and UX are only available for Azure Windows clusters as of Service Fabric version 6.4. There are no Linux or macOS instructions, examples, or workarounds provided, and enabling/configuring instructions are only relevant for Windows clusters. Linux parity is acknowledged as a future goal, but current users on Linux or Standalone clusters cannot utilize EventStore.
Recommendations
  • Clearly indicate the lack of Linux/macOS support at the top of the page and in all relevant sections.
  • Provide alternative monitoring or diagnostic solutions for Linux clusters, or link to such resources.
  • Update the documentation as soon as Linux support is available, ensuring examples and instructions for both platforms.
  • Add a comparison table showing feature availability for Windows vs. Linux clusters.
  • If possible, provide a roadmap or workaround for Linux users, even if limited.
GitHub Create Pull Request
Service Fabric Report and check health with Azure Service Fabric ...ric-diagnostics-how-to-report-and-check-service-health.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 strong Windows bias. All setup, deployment, and health-check instructions rely on Windows-specific tools: Visual Studio, PowerShell, and Local Cluster Manager (notification area). No Linux/macOS equivalents or alternatives are mentioned, and PowerShell commands are the only CLI examples provided. The prerequisites and workflow assume a Windows development environment, leaving Linux/macOS users without guidance.
Recommendations
  • Add instructions for setting up a Service Fabric dev cluster on Linux/macOS, including required SDKs and CLI tools.
  • Provide deployment and health-check examples using cross-platform tools such as Azure CLI, Service Fabric CLI (sfctl), or REST API calls.
  • Include Linux/macOS-specific prerequisites and workflows, such as using VS Code or JetBrains Rider instead of Visual Studio.
  • Present examples for both Windows and Linux/macOS side-by-side, or clearly indicate platform-specific steps.
  • Reference Service Fabric Explorer access via browser, rather than relying on Windows notification area icons.
GitHub Create Pull Request
Service Fabric Query for cluster events using the EventStore APIs ...-fabric/service-fabric-diagnostics-eventstore-query.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_only ⚠ī¸ missing_linux_example
Summary
The documentation explicitly states that the EventStore APIs are GA only for Windows clusters running on Azure. There are no examples, instructions, or notes for Linux clusters or macOS users. All sample code and scenarios assume Windows environments, and there is no mention of Linux support or parity.
Recommendations
  • Clarify whether Linux clusters are supported or not, and if so, provide equivalent instructions and examples for Linux environments.
  • If Linux support is planned, add a section describing the timeline and any limitations.
  • Include REST API usage examples that are platform-agnostic and demonstrate how to query from Linux/macOS (e.g., using curl, Python, etc.).
  • If the Service Fabric client library is available for Linux/macOS, provide code samples for those platforms.
  • Add a table or callout that summarizes feature availability across Windows, Linux, and macOS clusters.
GitHub Create Pull Request
Service Fabric Performance monitoring with Azure Diagnostics .../service-fabric/service-fabric-diagnostics-perf-wad.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 focuses almost exclusively on Windows clusters, providing detailed instructions and examples for configuring performance monitoring using the Windows Azure Diagnostics (WAD) extension. Linux clusters are only briefly mentioned, with a link to a separate page and no equivalent configuration or example provided. All code samples, configuration details, and deployment instructions (including PowerShell usage) are Windows-specific, with no parity for Linux users.
Recommendations
  • Add a dedicated section for Linux clusters, detailing how to configure performance counter collection using the Log Analytics agent, including example configuration files and deployment steps.
  • Provide Linux-specific command-line instructions (e.g., using Azure CLI or Bash scripts) for deploying and updating cluster diagnostics.
  • Ensure that references to tools and configuration patterns (such as ARM templates) include Linux-compatible approaches and examples.
  • Present Windows and Linux guidance in parallel or clearly separated sections, rather than focusing on Windows first.
  • Link to or summarize key Linux documentation inline, rather than only referencing it externally.
GitHub Create Pull Request
Service Fabric Remove a node type in Azure Service Fabric | Microsoft Docs ...rvice-fabric/service-fabric-how-to-remove-node-type.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 tooling for all operational steps, with no mention of Linux or cross-platform alternatives. There are no Bash, Azure CLI, or Linux-native instructions, and PowerShell is assumed for cluster interaction and resource management. This creates friction for Linux/macOS users and may prevent them from completing the task without significant adaptation.
Recommendations
  • Provide equivalent Azure CLI commands for all resource management steps (e.g., removing scale sets, resources).
  • Include Bash script examples for Service Fabric node operations, or clarify how to use Service Fabric CLI (sfctl) on Linux/macOS.
  • Explicitly state platform requirements and offer guidance for Linux/macOS users, including installation and usage of cross-platform tools.
  • Reorder examples so that cross-platform or Azure-native commands (Azure CLI, REST API) are shown before or alongside PowerShell.
  • Add a section or note describing how Linux/macOS administrators can perform these tasks, including any limitations.
GitHub Create Pull Request
Service Fabric Use Patch Orchestration Application ...bric/service-fabric-patch-orchestration-application.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 for Patch Orchestration Application (POA) is heavily focused on Windows environments. All examples, configuration steps, and operational details are tailored to Windows Server clusters, with repeated references to Windows Update, Windows NT services, PowerShell scripts, and Windows-specific policies. Linux is only mentioned in a single FAQ entry, which redirects users to a different Azure VMSS documentation page, with no Linux-specific POA guidance or parity in examples, tools, or troubleshooting.
Recommendations
  • Provide equivalent instructions and examples for Linux-based Service Fabric clusters, including how to orchestrate OS patching using POA or alternative tools.
  • Include Linux-specific configuration steps, deployment scripts (e.g., Bash, CLI), and troubleshooting guidance.
  • Clarify POA's applicability or limitations for Linux clusters early in the documentation, not just in the FAQ.
  • If POA is Windows-only, make this explicit at the top of the page and provide links to Linux patch orchestration solutions.
  • Balance the order of presentation so Linux users do not have to search for relevant information or feel excluded.
GitHub Create Pull Request
Service Fabric Service Fabric app upgrade tutorial ...-fabric/service-fabric-application-upgrade-tutorial.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
This documentation page is heavily focused on Windows development workflows, specifically using Visual Studio for Service Fabric application upgrades. All instructions, screenshots, and steps assume the use of Visual Studio (a Windows-only tool), with no mention of Linux/macOS alternatives or cross-platform CLI workflows. Linux users are directed only to a separate PowerShell tutorial, which itself is not natively available on Linux/macOS. There are no examples or guidance for performing these tasks on Linux or macOS, nor are cross-platform tools like Azure CLI or Service Fabric CLI mentioned.
Recommendations
  • Add equivalent instructions for upgrading Service Fabric applications using cross-platform tools such as Azure CLI or Service Fabric CLI.
  • Include Linux/macOS-specific examples and screenshots where applicable.
  • Clearly indicate which steps are Windows/Visual Studio-specific, and provide links or inline steps for Linux/macOS users.
  • Consider restructuring the tutorial to present cross-platform options first, or at least equally alongside Windows/Visual Studio workflows.
  • If PowerShell is referenced, clarify that PowerShell Core is available on Linux/macOS and provide relevant instructions.
GitHub Create Pull Request
Service Fabric Standalone Cluster Deployment Preparation ...rvice-fabric-cluster-standalone-deployment-preparation.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 biased towards Windows environments, with all instructions, requirements, and examples focused exclusively on Windows Server. There are no references to Linux or macOS equivalents, and critical steps (such as environment validation and cluster deployment) rely on Windows-only tools and scripts (e.g., PowerShell, Windows services, NTFS, RemoteRegistry). This makes it impossible for Linux/macOS users to follow the guide or deploy a standalone Service Fabric cluster using these instructions.
Recommendations
  • Add explicit statements about Linux/macOS support or lack thereof for standalone clusters.
  • If Linux support exists, provide equivalent instructions, prerequisites, and validation scripts for Linux environments.
  • Include Linux-specific examples for cluster configuration, environment setup, and validation.
  • Mention Linux file systems and services where relevant, or clarify Windows-only requirements.
  • If standalone clusters are Windows-only, make this clear at the top of the documentation.
GitHub Create Pull Request
Service Fabric Azure Service Fabric standalone cluster scaling ...ce-fabric/service-fabric-cluster-scaling-standalone.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 Windows bias by referencing only Windows-specific tools (PowerShell cmdlets like Get-ServiceFabricClusterManifest and Start-ServiceFabricClusterConfigurationUpgrade) for cluster management tasks. There are no Linux or cross-platform equivalents mentioned, nor are there examples for Linux users. The linked 'scale a standalone cluster' page is also Windows-focused, further excluding Linux scenarios.
Recommendations
  • Include Linux-specific instructions and examples for scaling standalone clusters, such as using Service Fabric CLI (sfctl) or REST APIs.
  • Mention cross-platform tools and patterns where possible, and provide parity in documentation for both Windows and Linux environments.
  • Explicitly state which steps/tools are Windows-only and offer alternatives for Linux/macOS users.
  • Add links or references to Linux/macOS documentation for Service Fabric cluster management.
GitHub Create Pull Request
Service Fabric Deploy a .NET app in a container to Azure Service Fabric ...rvice-fabric/service-fabric-host-app-in-a-container.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 biased towards Windows environments. All examples, scripts, and tool recommendations are for Windows (PowerShell, Visual Studio, Docker Desktop for Windows, Windows containers, Windows Service Fabric clusters). There are no instructions or alternatives for Linux or macOS users, and the workflow assumes the use of Windows-specific tools and patterns throughout.
Recommendations
  • Provide equivalent instructions and scripts for Linux/macOS users, including Bash/Azure CLI examples.
  • Mention and demonstrate how to use Docker Desktop for Mac/Linux, or native Docker on Linux.
  • Clarify whether Service Fabric Linux clusters are supported for this scenario, and if so, provide guidance for containerizing and deploying .NET apps to Linux-based clusters.
  • Include instructions for using cross-platform IDEs (e.g., VS Code) or command-line workflows instead of only Visual Studio.
  • List Linux/macOS prerequisites and installation steps alongside Windows ones.
  • Order examples so that Windows and Linux/macOS are presented equally, or at least note that the tutorial is Windows-specific if Linux is not supported.
GitHub Create Pull Request
Service Fabric Event Aggregation with Microsoft Azure Diagnostics ...ic/service-fabric-diagnostics-event-aggregation-wad.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 notable Windows bias. While it mentions both Windows and Linux at the top, the main body and all technical examples focus exclusively on Windows tooling, patterns, and extensions (WAD, ETW, PowerShell, Visual Studio). There are no Linux-specific examples, nor is the Linux diagnostics extension (LAD) or Linux logging patterns discussed. All example code, configuration, and troubleshooting steps are tailored for Windows clusters, leaving Linux users without actionable guidance.
Recommendations
  • Add parallel Linux-specific instructions and examples throughout the page, referencing the Linux diagnostics extension (LAD) and its configuration.
  • Include CLI examples using Bash/az CLI for Linux clusters, not just PowerShell.
  • Discuss Linux logging mechanisms (e.g., syslog, journald) and how they integrate with Azure diagnostics.
  • Provide links and references to Linux documentation at each major step, not just at the top.
  • Ensure troubleshooting and performance counter collection sections include Linux equivalents.
GitHub Create Pull Request
Service Fabric Create and Publish a .NET Core app to a remote Linux Cluster ...e-fabric/service-fabric-how-to-publish-linux-app-vs.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 is heavily focused on using Visual Studio, a Windows-centric tool, for creating and publishing .NET Core apps to a remote Linux Service Fabric cluster. All instructions and screenshots assume a Windows environment (Visual Studio UI, launching as administrator, .exe file references), with no mention of Linux-native workflows, command-line alternatives, or cross-platform tooling. There are no examples for Linux/macOS users who may prefer or require non-Windows environments.
Recommendations
  • Provide equivalent instructions for Linux/macOS users, such as using Visual Studio Code, JetBrains Rider, or command-line tools (dotnet CLI, Azure CLI).
  • Include examples for creating, building, and publishing Service Fabric applications using cross-platform tools.
  • Add screenshots and step-by-step guides for Linux environments.
  • Clarify which steps are Windows-only and offer alternatives where possible.
  • Mention and link to documentation for Linux/macOS development environments.
GitHub Create Pull Request
Service Fabric Quickly create a .NET app on Service Fabric in Azure ...les/service-fabric/service-fabric-quickstart-dotnet.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 Windows-centric, requiring Visual Studio, PowerShell commands, and Windows-specific Service Fabric tools. All setup and deployment instructions assume a Windows environment, with no mention of Linux or macOS alternatives. There are no examples or guidance for non-Windows users, making it difficult or impossible for them to follow the quickstart.
Recommendations
  • Add instructions for setting up Service Fabric development clusters on Linux and macOS, including required SDKs and tools.
  • Provide command-line examples using Bash and cross-platform .NET CLI commands instead of (or in addition to) PowerShell.
  • Include guidance for using VS Code or JetBrains Rider as alternatives to Visual Studio, especially for Linux/macOS users.
  • Document any platform-specific limitations or differences, and link to official cross-platform Service Fabric documentation.
  • Clearly indicate which steps are Windows-only and provide parity steps for other platforms where possible.
GitHub Create Pull Request
Service Fabric Create an actor-based service on Azure Service Fabric ...e-fabric/service-fabric-reliable-actors-get-started.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 development using Visual Studio and PowerShell, with no Linux/macOS equivalents provided for critical steps such as project creation, building, debugging, and package management. The only mention of Linux is in a selector at the top, but the main content exclusively describes Windows workflows and tools.
Recommendations
  • Add parallel instructions for Linux/macOS users, including how to create, build, and debug actor-based services using cross-platform tools (e.g., .NET CLI, VS Code, JetBrains Rider).
  • Replace or supplement Visual Studio-specific steps with .NET CLI commands for project creation and management.
  • Provide Linux/macOS equivalents for PowerShell commands, such as Bash or shell commands for NuGet package installation.
  • Clarify which steps are Windows-only and link to Linux/macOS documentation where available.
  • Include screenshots or terminal output from Linux/macOS environments to improve parity.
GitHub Create Pull Request
Service Fabric Scale up an Azure Service Fabric primary node type ...ce-fabric/service-fabric-scale-up-primary-node-type.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 toward Windows environments, with all command-line examples using PowerShell and Windows file paths. The upgrade scenario is described exclusively for Windows Server OS, and Linux-specific instructions are minimal and relegated to a brief note. There are no Bash, Azure CLI, or Linux-native certificate management examples, and Windows tools and patterns (such as certificate stores and file paths) are used throughout.
Recommendations
  • Provide equivalent Bash/Azure CLI examples for all PowerShell commands, including cluster deployment, certificate management, and resource cleanup.
  • Include a full Linux upgrade scenario, with explicit steps for Ubuntu or other supported distributions, including certificate generation and management.
  • Use platform-neutral file paths and clarify where Windows-specific paths should be replaced on Linux/macOS.
  • Mention Linux tools (e.g., openssl for certificate generation, Linux file system locations) alongside Windows tools.
  • Reorder examples so that Linux and Windows instructions are presented in parallel, or at least give Linux equal prominence.
  • Clarify any differences in Service Fabric management for Linux clusters, such as runtime package registration and required extensions.
GitHub Create Pull Request
Service Fabric Run an Azure Service Fabric service under a gMSA account ...s/service-fabric/service-fabric-run-service-as-gmsa.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 examples and instructions use Windows-specific tools (PowerShell cmdlets, Windows Features) and reference Windows Server and Active Directory. There are no Linux/macOS equivalents or guidance, and the prerequisites and steps are exclusively for Windows standalone clusters.
Recommendations
  • Clarify early that gMSA is a Windows-only feature and note any Linux/macOS limitations.
  • If Service Fabric on Linux supports similar managed service account features, provide equivalent instructions or explicitly state the lack of support.
  • Offer alternative security/account management approaches for Linux clusters, or link to relevant documentation.
  • Add a comparison table or section outlining differences in service account management between Windows and Linux clusters.
GitHub Create Pull Request
Service Fabric Create your first Service Fabric application in C# ...fabric/service-fabric-reliable-services-quick-start.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 development, with all examples and instructions using Visual Studio, referencing Windows-specific tools (such as PowerShell scripts and ETW), and omitting Linux/macOS equivalents. There are no instructions or examples for developing, building, or running Service Fabric applications on Linux/macOS, nor are alternative tools or workflows mentioned. The only nod to Linux is a link to a separate Java-on-Linux quickstart, but this page is exclusively C# on Windows.
Recommendations
  • Add equivalent instructions and examples for developing Service Fabric applications in C# on Linux/macOS, using cross-platform tools such as VS Code, JetBrains Rider, or the dotnet CLI.
  • Provide guidance for deploying and managing Service Fabric applications on Linux clusters, including alternative to PowerShell scripts (e.g., Bash scripts, Azure CLI).
  • Mention and demonstrate how to view diagnostic events and logs on Linux (e.g., using systemd, journald, or Service Fabric Explorer), instead of only referencing ETW and Visual Studio.
  • Ensure that all critical steps (project creation, deployment, debugging) have Linux/macOS workflows documented alongside Windows instructions.
  • Consider restructuring the page to present platform-agnostic concepts first, and then provide platform-specific instructions in parallel.
GitHub Create Pull Request
Service Fabric Azure Service Fabric reverse proxy ...articles/service-fabric/service-fabric-reverseproxy.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 exhibits a high degree of Windows bias. The reverse proxy feature is explicitly stated as unavailable for Linux clusters, and all configuration, usage, and troubleshooting guidance is written with Windows clusters in mind. Examples, references, and linked resources are focused on Windows-specific tools and patterns (e.g., http.sys-based servers, Windows container debugging). There are no Linux equivalents or workarounds provided, and Linux users are unable to utilize the reverse proxy functionality described.
Recommendations
  • Clearly state the lack of Linux support for reverse proxy at the top of the page and in all relevant sections.
  • Provide alternative guidance or recommended patterns for Linux clusters, such as using other service discovery or proxy solutions.
  • If possible, document any roadmap or plans for Linux support, or link to feature request channels.
  • Ensure that linked resources and examples include Linux alternatives or explicitly note their Windows-only applicability.
  • Consider adding a comparison table summarizing feature parity between Windows and Linux clusters for reverse proxy.
GitHub Create Pull Request
Service Fabric Create infrastructure for a cluster on AWS ...rvice-fabric-tutorial-standalone-create-infrastructure.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 toward Windows environments. All examples, scripts, and instructions assume Windows Server EC2 instances, use PowerShell, and reference Windows-specific tools and patterns (RDP, SMB, Windows domain, etc.). There are no instructions or examples for Linux-based clusters, nor any mention of how to adapt the process for Linux or macOS users.
Recommendations
  • Provide parallel instructions for launching Linux EC2 instances, including recommended distributions and instance setup.
  • Include Linux shell script examples for bootstrapping instances (e.g., using cloud-init or bash for user data).
  • Describe how to configure security groups and connectivity for Linux (e.g., SSH access, NFS or Samba for file sharing, alternatives to SMB).
  • Offer guidance on validating connectivity and file sharing between Linux instances (e.g., using ssh, scp, or mounting NFS shares).
  • Clarify which steps are Windows-specific and which are required for Linux, and provide links to Linux Service Fabric installation guides if available.
GitHub Create Pull Request
Service Fabric Troubleshoot with system health reports ...understand-and-troubleshoot-with-system-health-reports.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 significant Windows bias. All command-line examples use Windows PowerShell cmdlets, with no mention of Linux equivalents (such as Service Fabric CLI or REST API). Windows tools and patterns (PowerShell, Windows paths, 'PS C:\>' prompts) are used exclusively and shown first. There is no guidance for Linux/macOS users on how to perform the same troubleshooting tasks, nor are cross-platform tools referenced.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl) for Linux/macOS users alongside PowerShell examples.
  • Explicitly mention cross-platform troubleshooting options (e.g., REST API, sfctl, Service Fabric Explorer web UI) where applicable.
  • For every PowerShell command, provide the corresponding CLI or REST API command, and clarify which platforms each applies to.
  • Avoid Windows-specific paths and prompts in generic examples, or provide Linux/macOS alternatives.
  • Add a section or note at the top clarifying platform support and pointing Linux/macOS users to relevant tools.
GitHub Create Pull Request
Virtual Machine Scale Sets Using Desired State Configuration With Virtual Machine Scale Sets ...l-machine-scale-sets/virtual-machine-scale-sets-dsc.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 Windows and PowerShell Desired State Configuration (DSC). All code examples reference the Microsoft.Powershell.DSC extension and use PowerShell scripts (.ps1), with no mention of Linux equivalents or support for Linux VM extensions. References and links are exclusively for Windows/PowerShell DSC, and there are no Linux-specific instructions or examples.
Recommendations
  • Add sections or notes on using Linux VM extensions for configuration management, such as the Custom Script Extension or Azure Machine Configuration for Linux.
  • Provide equivalent ARM template snippets for configuring Linux VMs or scale sets, using supported Linux extensions.
  • Include references and links to documentation for Linux VM extensions and configuration management tools (e.g., cloud-init, Chef, Puppet, or Ansible on Linux).
  • Clarify in the introduction or notes whether the DSC extension is Windows-only, and guide Linux users to appropriate alternatives.
GitHub Create Pull Request
Virtual Machines Azure Backup for SQL Server running in Azure VM ...extensions/backup-azure-sql-server-running-azure-vm.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 is heavily focused on Windows-based SQL Server workloads in Azure VMs. It exclusively references the 'AzureBackupWindowsWorkload' extension, provides only PowerShell-based deployment instructions, and does not mention or provide examples for Linux-based SQL Server VMs or Linux-native tooling. Windows terminology and tools are presented as the default, with no Linux parity.
Recommendations
  • Clarify in the introduction whether Linux-based SQL Server VMs are supported or not. If supported, add equivalent instructions and examples for Linux VMs.
  • If Linux is not supported, explicitly state this limitation to avoid confusion.
  • Provide CLI (az cli) or REST API examples for registration and deployment, which are cross-platform.
  • Mention any Linux-specific backup extensions or procedures if available.
  • Reorganize examples so that platform-agnostic methods (e.g., ARM templates, REST API) are shown before platform-specific ones like PowerShell.
GitHub Create Pull Request
Virtual Machines Desired State Configuration for Azure overview ...n/articles/virtual-machines/extensions/dsc-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 is heavily focused on Windows and PowerShell Desired State Configuration (DSC), with all examples, tools, and workflows centered around Windows VMs and PowerShell cmdlets. There are no Linux-specific examples, tools, or instructions, and the prerequisites and architecture sections assume Windows Management Framework and PowerShell DSC, which are not natively available on Linux. The Azure CLI section also only provides a Windows VM example.
Recommendations
  • Add explicit guidance for Linux VMs, including whether and how DSC extension can be used or alternatives for Linux configuration management.
  • Provide Linux/macOS equivalent examples for deployment, configuration, and troubleshooting, or clearly state limitations for non-Windows platforms.
  • Mention cross-platform configuration management tools (e.g., Ansible, Chef, Puppet) and how they integrate with Azure VM extensions.
  • Clarify in prerequisites and architecture sections whether Linux VMs are supported and what users should do for Linux environments.
  • If DSC extension is Windows-only, make this limitation clear at the top of the documentation.
GitHub Create Pull Request
Virtual Machines Deploy a VM or Virtual Machine Scale Set with MSP ...tual-machines/metadata-security-protocol/greenfield.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 highlighting a Windows-specific feature (GuestProxyAgent enabled from ARM template) and explicitly noting that Linux requires a more complex, two-step process, but does not provide Linux-specific instructions or examples. All configuration and API examples are generic or Windows-named, with no Linux parity guidance.
Recommendations
  • Add explicit Linux deployment instructions, detailing the two-step process required for enabling GuestProxyAgent on Linux VMs.
  • Provide Linux-specific ARM template and REST API examples, including any necessary post-provisioning steps.
  • Clarify any differences in validation or troubleshooting for Linux VMs.
  • Ensure example resource names are not Windows-centric (e.g., 'GPAWinVM').
GitHub Create Pull Request
Virtual Machines Move resources associated with a maintenance configuration to another region ...nes/move-region-maintenance-configuration-resources.md
Medium 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 examples are given first and in greater detail, with variable definitions using PowerShell syntax. The main migration step links to a Windows-specific tutorial (toc/breadcrumb paths reference Windows), and PowerShell-specific error handling is described. While Azure CLI examples are present, the overall flow and examples favor Windows/PowerShell users, and Linux/macOS users may need to adapt instructions.
Recommendations
  • Provide variable definition examples in Bash syntax alongside PowerShell.
  • Ensure migration tutorial links use platform-neutral or Linux/macOS-specific TOC/breadcrumb paths.
  • Describe error handling for CLI commands, not just PowerShell.
  • Explicitly mention that CLI commands work on Linux/macOS and provide Bash copy-paste examples.
  • Balance the order of examples: show CLI (cross-platform) first, then PowerShell.
  • Add notes or sections for Linux/macOS users where workflows or commands may differ.
GitHub Create Pull Request
Virtual Machines Azure VM Extensions and Features for Linux ...articles/virtual-machines/extensions/features-linux.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
Although the documentation is focused on Linux VM extensions, it consistently presents both Azure CLI and Azure PowerShell examples side-by-side, with PowerShell examples given equal prominence. PowerShell is a Windows-centric tool, and its inclusion throughout may create friction for Linux/macOS users. Additionally, references to ARM templates link to Windows documentation first, and some terminology (such as 'publisher', 'extension type') is not clarified for Linux users. However, Linux-specific details (such as waagent, log locations, and Bash scripts) are present and correct.
Recommendations
  • Prioritize Azure CLI examples over PowerShell, as CLI is cross-platform and native to Linux/macOS.
  • Clearly indicate that PowerShell is optional and primarily for Windows users; consider moving PowerShell examples to a secondary section or appendix.
  • Ensure ARM template links point to Linux-specific documentation when possible.
  • Add explicit notes about tool availability and platform compatibility for each example.
  • Review terminology to ensure it is clear for Linux users and not Windows-centric.
GitHub Create Pull Request
Container Instances Set environment variables in container instance ...instances/container-instances-environment-variables.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 provides both Azure CLI and PowerShell examples for setting environment variables in container instances, but it demonstrates a Windows bias in several ways. PowerShell (a Windows-centric tool) is given a dedicated section with detailed examples, while Linux/macOS equivalents (such as Bash scripting or shell environment variable patterns) are not covered. In the Azure CLI section, instructions for Windows Command Prompt syntax are mentioned, but there is no equivalent guidance for Linux/macOS shells beyond a brief assumption. The portal instructions are platform-neutral, but overall, Linux-specific patterns and troubleshooting are missing.
Recommendations
  • Add explicit Bash and Linux/macOS shell examples for environment variable syntax and command usage.
  • Provide troubleshooting notes for common Linux/macOS issues (e.g., quoting, shell differences).
  • Include links or references to Linux-native tools and workflows for managing containers and environment variables.
  • Balance PowerShell coverage with equivalent Bash or shell scripting guidance.
  • Ensure that CLI instructions are equally clear for both Windows and Linux/macOS users, including syntax nuances.
GitHub Create Pull Request
Container Instances Enable Managed Identity in a Container Group ...iner-instances/container-instances-managed-identity.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_section_last ⚠ī¸ linux_first ⚠ī¸ powershell_example_present ⚠ī¸ windows_tools
Summary
The documentation predominantly provides examples and instructions for Linux-based containers, with Bash and Azure CLI commands throughout. Windows container guidance is relegated to a separate section at the end, with only a brief PowerShell script and curl example. There is no parity in step-by-step walkthroughs for Windows containers, and Windows-specific tooling (PowerShell) is only mentioned in the Windows section. The main flow assumes Linux containers and does not offer equivalent Windows-first or Windows-parallel examples.
Recommendations
  • Add full, step-by-step examples for Windows containers, mirroring the Linux container walkthroughs (resource group creation, identity assignment, key vault access, etc.) using PowerShell and Windows-specific patterns.
  • Present Windows and Linux container instructions in parallel where possible, or clearly indicate which steps differ for each platform.
  • Include notes or tables summarizing differences in managed identity usage between Linux and Windows containers at the start of the article.
  • Provide troubleshooting guidance for common Windows container issues (e.g., lack of metadata server, networking constraints).
GitHub Create Pull Request
Container Instances Create a standby pool for Azure Container Instances ...r-instances/container-instances-standby-pool-create.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 both Azure CLI and PowerShell examples for all major operations, but PowerShell is given equal prominence and detail as CLI, and ARM template deployment instructions reference PowerShell cmdlets alongside CLI. PowerShell is a Windows-centric tool, and its inclusion as a primary method (rather than, for example, Bash or shell scripting) reflects a Windows bias. Additionally, deployment instructions for ARM templates mention PowerShell before CLI in some places, and there are no Linux/macOS-specific notes or examples (such as Bash scripts or platform caveats).
Recommendations
  • Add Bash or shell script examples for Linux/macOS users, especially for tasks currently only shown in PowerShell.
  • Clarify that Azure CLI is cross-platform and recommend it as the primary method for non-Windows users.
  • Move CLI examples before PowerShell in each section to emphasize platform neutrality.
  • Include notes or links for Linux/macOS users regarding installation and usage of Azure CLI.
  • If PowerShell is necessary, mention PowerShell Core (pwsh) compatibility on Linux/macOS.
GitHub Create Pull Request
Virtual Machines MSP via CLI ...hines/metadata-security-protocol/other-examples/cli.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
All CLI examples use the Windows Server image ('Win2022DataCenter') and do not mention or provide examples for Linux VM images. There is no discussion of Linux-specific considerations, nor are Linux images (such as Ubuntu or CentOS) shown in any command. This creates a bias towards Windows usage and may cause confusion or friction for Linux users.
Recommendations
  • Provide equivalent CLI examples using popular Linux images (e.g., '--image UbuntuLTS', '--image CentOS').
  • Add a note clarifying that MSP is supported for both Windows and Linux VMs, if applicable.
  • Mention any Linux-specific configuration steps or caveats, if they exist.
  • Alternate examples between Windows and Linux, or show both side-by-side.
GitHub Create Pull Request
Virtual Machines Metadata Security Protocol (MSP) ...irtual-machines/metadata-security-protocol/overview.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation lists Windows operating systems first in compatibility, and provides a warning that Windows users can enable GuestProxyAgent (GPA) directly from an ARM template, while Linux users must perform a two-step process. However, there are no Linux-specific instructions or examples provided, and no mention of Linux tooling or commands. This creates friction for Linux users who may need more guidance for the additional steps.
Recommendations
  • Add explicit step-by-step instructions for enabling GPA on Linux, including any required commands or configuration files.
  • Provide Linux-specific examples and tooling references (e.g., shell commands, systemd integration) alongside Windows/ARM template examples.
  • List supported operating systems in alphabetical order or group by platform to avoid implicit prioritization.
  • Clarify any differences in process between Windows and Linux with equal detail for both.
GitHub Create Pull Request
Virtual Machines Enable MSP on an Existing Virtual Machine or Virtual Machine Scale Set ...tual-machines/metadata-security-protocol/brownfield.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 more detailed information and examples for Windows VMs, such as showing Windows extension status output and referencing Windows-specific tools and paths. Linux instructions are less explicit, requiring users to infer steps or perform additional REST API calls without concrete examples. Windows extensions and their status outputs are shown, but Linux equivalents are only mentioned in passing, with no example output or explicit validation steps.
Recommendations
  • Provide explicit example output for Linux extension status, similar to the Windows example.
  • Include step-by-step instructions or sample REST API calls for installing and validating the Proxy Agent extension on Linux VMs.
  • Mention Linux tools, file paths, and validation patterns where appropriate, not just Windows equivalents.
  • Ensure parity in troubleshooting and validation guidance for both Windows and Linux users.
GitHub Create Pull Request
Virtual Machines NV series migration guide ...-machines/migration/sizes/nv-series-migration-guide.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 exhibits Windows bias by focusing exclusively on Windows guest OS support for NVv4 VMs, referencing only Windows-specific driver installation guides and extensions, and omitting Linux migration steps, driver instructions, or parity notes. Linux users are left without guidance for migrating NV-series VMs, especially regarding GPU driver installation and support.
Recommendations
  • Explicitly state Linux support status for each VM series, including any limitations.
  • Provide Linux-specific migration steps, including driver installation instructions and links to Linux driver documentation.
  • Include notes or alternatives for Linux users where Windows-only features/extensions are mentioned.
  • Add FAQ entries addressing common Linux migration scenarios.
  • Ensure extension and driver documentation links include Linux equivalents where available.
GitHub Create Pull Request
Container Instances Configure role permissions for standby pools in Azure Container Instances ...container-instances-standby-pool-configure-permissions.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 references the Azure portal UI for role assignment and troubleshooting, which is platform-agnostic but most commonly used on Windows. There are no command-line examples (e.g., Azure CLI, Bash, PowerShell) for role assignment or troubleshooting, and the only SDKs mentioned for API calls are 'PowerShell or CLI' with PowerShell listed first. No explicit Linux/macOS instructions or examples are provided, and no Linux-specific tools or patterns are referenced.
Recommendations
  • Add Azure CLI and Bash examples for role assignment and troubleshooting, alongside or before PowerShell examples.
  • Explicitly mention that all steps can be performed on Linux/macOS using Azure CLI or REST API.
  • Provide links to cross-platform command-line documentation for role assignment and troubleshooting.
  • When referencing SDKs, list CLI and REST API before PowerShell, or mention all platforms equally.
GitHub Create Pull Request
Container Instances Understand the health state of your standby pool for Azure Container Instances ...ances/container-instances-standby-pool-health-state.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 Azure CLI and PowerShell examples for retrieving the health state of a standby pool, but PowerShell is given its own dedicated section alongside CLI and REST. There is no mention of Linux-specific tools or shell patterns, and PowerShell (a Windows-centric tool) is featured equally with CLI, despite CLI being cross-platform. No Linux/macOS shell examples (e.g., curl, jq, Bash) are provided.
Recommendations
  • Add Linux/macOS shell examples using curl to demonstrate REST API usage from Bash.
  • Clarify that Azure CLI commands work identically on Linux/macOS and Windows.
  • Consider adding example output parsing using jq or other common Linux tools.
  • If PowerShell is included, note that PowerShell Core is available cross-platform, or provide Bash alternatives.
GitHub Create Pull Request
Container Instances Standby pools for Azure Container Instances ...instances/container-instances-standby-pool-overview.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page exhibits a moderate Windows bias, primarily through the use of PowerShell for critical resource provider registration and by presenting PowerShell examples before CLI or REST alternatives. The initial prerequisite step for provider registration is shown only with an Azure PowerShell command, which may create friction for Linux/macOS users who typically use Bash/CLI. While later sections do provide Azure CLI and REST examples, the initial focus and lack of Bash/CLI for provider registration suggest a Windows-centric approach.
Recommendations
  • Add Azure CLI (az) and Bash examples for resource provider registration alongside the PowerShell example.
  • Ensure all command-line instructions are provided in both Azure CLI and PowerShell, with CLI examples shown first or side-by-side.
  • Explicitly mention cross-platform compatibility for all tools and commands.
  • Consider adding notes or links for installing Azure CLI and PowerShell on Linux/macOS, if relevant.
GitHub Create Pull Request
Virtual Machines Create and upload an Oracle Linux VHD ...les/virtual-machines/linux/oracle-create-upload-vhd.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 exhibits Windows bias by exclusively referencing Hyper-V (a Windows-only virtualization tool) for creating and managing VHDs, providing links only to Windows/Hyper-V instructions, and omitting Linux-native alternatives (such as KVM, qemu-img, or VirtualBox). All example workflows for VM creation and shutdown use Hyper-V Manager, with no mention of equivalent Linux tools or commands. This may create friction for Linux users who do not have access to Hyper-V.
Recommendations
  • Add instructions and examples for creating and managing VHDs using Linux-native tools such as KVM, qemu-img, or VirtualBox.
  • Provide Linux command-line examples for VM creation, shutdown, and disk conversion (e.g., using qemu-img to convert disk formats).
  • Include links to official documentation for Linux virtualization solutions and disk management tools.
  • Present both Windows and Linux workflows side by side, or clearly indicate which steps are platform-specific.
GitHub Create Pull Request
Container Instances Update or delete a standby pool for Azure Container Instances ...nces/container-instances-standby-pool-update-delete.md
Medium 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 Azure CLI and PowerShell examples for updating and deleting standby pools, but PowerShell (a Windows-centric tool) is given equal prominence as CLI, and is mentioned before Linux alternatives in some places. There are no explicit Linux/macOS shell examples (e.g., Bash), and PowerShell-specific commands and links are included throughout. ARM template and REST examples are platform-neutral, but the presence and prominence of PowerShell and lack of Linux/macOS-specific guidance indicate a moderate Windows bias.
Recommendations
  • Add explicit Bash shell examples for Linux/macOS users alongside PowerShell, especially for common tasks.
  • Clarify that Azure CLI works cross-platform and provide usage notes for Linux/macOS environments (e.g., installation, shell differences).
  • Reorder examples so that platform-neutral or cross-platform tools (CLI, REST, ARM templates) are shown before PowerShell.
  • Include notes or links for Linux/macOS users on how to install and use Azure CLI and ARM templates.
  • Avoid assuming PowerShell is the default automation tool; mention alternatives for Linux/macOS.
GitHub Create Pull Request
Virtual Machines Customer intent: As a cloud administrator, I want to retrieve the encryption type of a specified disk in a resource group, so that I can ensure compliance with security standards for our virtual machines. ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/includes/virtual-machines-disks-encryption-status-powershell.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation provides only a PowerShell example for retrieving disk encryption type, which is specific to Windows environments. There are no equivalent examples for Linux/macOS users (e.g., using Azure CLI or REST API), and the Windows-centric approach is presented first and exclusively.
Recommendations
  • Add equivalent Azure CLI example for Linux/macOS users.
  • Include REST API or SDK examples that are platform-agnostic.
  • Clearly indicate that PowerShell is Windows-specific and provide guidance for non-Windows platforms.
GitHub Create Pull Request
Virtual Machines Export Azure resource groups that contain VM extensions ...ticles/virtual-machines/extensions/export-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 demonstrates a Windows bias by referencing Windows tools and patterns first, such as PowerShell scripts and the BGInfo extension, and by listing Windows extensions before Linux equivalents. The sample deployment scripts are described as 'PowerShell and Azure CLI', with PowerShell mentioned first and no explicit Bash or Linux shell examples provided. The 'ms.collection' metadata is set to 'windows', further reinforcing the bias. Linux-specific instructions, examples, or parity in extension support are not clearly presented.
Recommendations
  • Explicitly mention and provide Bash or Linux shell examples for template deployment, alongside PowerShell.
  • List Linux and Windows VM extensions in parallel or alphabetically, rather than Windows-first.
  • Clarify that Azure CLI is cross-platform and provide Linux/macOS usage notes.
  • Update metadata to reflect cross-platform applicability, not just 'windows'.
  • Include screenshots or instructions from Linux/macOS perspectives where relevant.
GitHub Create Pull Request
Container Instances Override entrypoint in container instance ...ntainer-instances/container-instances-start-command.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 both Linux and Windows shell examples in the shell table, but the command-line syntax and examples focus primarily on Azure CLI (cross-platform) and Azure PowerShell (Windows-centric). The PowerShell cmdlet is mentioned before the Azure portal and template methods, and no Linux-specific command-line tool (e.g., Bash scripts, shell commands outside Azure CLI) is shown. The only Windows-specific tool referenced is PowerShell, and there are no Linux/macOS-specific command-line examples or troubleshooting tips. The shell table does mention Linux shells, but the documentation does not provide parity in examples for Linux-native workflows.
Recommendations
  • Add explicit Linux/macOS command-line examples using Bash or shell scripts, especially for local testing or troubleshooting.
  • Provide parity in example sections: if PowerShell is shown, also show equivalent Bash commands for Linux/macOS users.
  • Include troubleshooting or usage notes for Linux/macOS users, such as file path conventions or shell differences.
  • Clarify that Azure CLI is cross-platform and highlight any OS-specific considerations.
  • Reorder examples so that cross-platform or Linux-native methods are presented before Windows-specific ones.
GitHub Create Pull Request
Container Instances Tutorial - Trigger container group by Azure function ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/container-instances/container-instances-tutorial-azure-function-trigger.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 strongly biased toward Windows and PowerShell. All code examples use PowerShell cmdlets, and the tutorial centers on creating a PowerShell Azure Function. Prerequisites and instructions reference Azure PowerShell and Visual Studio Code, with no mention of Bash, Azure CLI alternatives, or Linux/macOS-specific workflows. Linux users are expected to use PowerShell, which is less common and may not be installed by default. No examples are given for creating the function in other supported languages (e.g., Python, JavaScript), nor for using Bash or Azure CLI to manage resources.
Recommendations
  • Provide equivalent examples using Azure CLI and Bash scripts for resource management steps (e.g., enabling managed identity, assigning roles, creating container groups).
  • Include instructions for creating Azure Functions in other supported languages (e.g., Python, JavaScript) and clarify cross-platform support.
  • Add explicit guidance for Linux/macOS users, including installation and usage of PowerShell Core, or alternatives using native tools.
  • Present CLI/Bash examples alongside PowerShell, or at least link to them.
  • Clarify that PowerShell is cross-platform, but acknowledge that Linux users may prefer CLI/Bash and provide parity.
GitHub Create Pull Request
Service Fabric Azure Service Fabric reverse proxy diagnostics ...ice-fabric/service-fabric-reverse-proxy-diagnostics.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page exhibits Windows bias primarily through references to Windows-specific tools and terminology (e.g., 'Windows Azure Diagnostics', 'ERROR_WINHTTP_TIMEOUT', 'winHttpError'), and by mentioning Windows-centric workflows and tools before any Linux alternatives. There are no explicit Linux or macOS examples, nor are cross-platform diagnostic tools or log collection methods discussed. The examples and troubleshooting steps assume a Windows environment, which may create friction for Linux/macOS users.
Recommendations
  • Include equivalent Linux/macOS error codes and diagnostic patterns alongside Windows-specific ones.
  • Add instructions and examples for collecting and viewing Service Fabric reverse proxy logs on Linux clusters (e.g., using Linux diagnostics agents, journald, or syslog).
  • Reference cross-platform tools (such as Azure Monitor, Log Analytics, or open-source log shippers) for event aggregation and troubleshooting.
  • Clarify which steps or error codes are Windows-only and provide Linux/macOS alternatives where possible.
  • Reorder sections to present cross-platform or OS-neutral approaches first, then provide OS-specific details.
GitHub Create Pull Request
Virtual Machines Create and upload an OpenBSD image ...ticles/virtual-machines/linux/create-upload-openbsd.md
Medium 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 toward Windows by exclusively mentioning Hyper-V and PowerShell for VHD creation and conversion, with no Linux or cross-platform alternatives provided. The only example for converting disk formats uses PowerShell, and instructions for creating the VHD reference Hyper-V and link to Windows-specific documentation. No Linux tools (such as qemu-img or VirtualBox) are mentioned for these steps.
Recommendations
  • Add instructions and examples for creating and converting VHD files using Linux tools such as qemu-img, VBoxManage (VirtualBox), or KVM.
  • Provide Linux/macOS command-line examples for disk conversion (e.g., qemu-img convert -f raw -O vpc ...).
  • Mention cross-platform alternatives to Hyper-V for virtualization and disk preparation.
  • Ensure that examples for critical steps (VHD creation/conversion) are shown for both Windows and Linux/macOS users, or at least link to relevant Linux documentation.
GitHub Create Pull Request
Service Fabric Azure Service Fabric set up reverse proxy ...es/service-fabric/service-fabric-reverseproxy-setup.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 exhibits a moderate Windows bias. Standalone cluster instructions and references are consistently tied to Windows Server and Windows-specific configuration files (ClusterConfig.json), with links and upgrade instructions pointing to Windows Server documentation. There is no mention of Linux-based standalone clusters or how to configure reverse proxy on Linux. The certificate management examples and references are Windows-centric (e.g., X509StoreName: 'My'), and no Linux equivalents or cross-platform notes are provided. While Azure-hosted clusters use platform-agnostic ARM templates, standalone cluster guidance is Windows-only.
Recommendations
  • Add explicit guidance for Linux-based standalone clusters, if supported, including configuration file locations and certificate management steps.
  • Clarify whether standalone clusters can be hosted on Linux and, if so, provide parity in instructions and examples.
  • When referencing certificate stores (e.g., 'My'), note Linux equivalents or provide cross-platform instructions.
  • Update links and references to include Linux/macOS documentation where available.
  • Consider rewording section titles and upgrade instructions to avoid implying Windows-only support unless that is a product limitation.
GitHub Create Pull Request
Service Fabric Migrate from Azure Cloud Services to Service Fabric ...ic/cloud-services-to-service-fabric-migration-guide.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 demonstrates a notable Windows bias. PowerShell is the only command-line example provided for cluster setup and application deployment, with no Azure CLI or Bash equivalents. Visual Studio (Windows-only) is presented as the primary development environment, and the instructions for preparing the development environment reference Windows specifically. There are no explicit Linux/macOS instructions or examples for cluster management, deployment, or development. Windows-specific migration scenarios (IIS, Windows Containers) are discussed, but Linux alternatives are not addressed.
Recommendations
  • Add Azure CLI and Bash examples for cluster creation, node type addition, and application deployment alongside PowerShell.
  • Include instructions for setting up the development environment on Linux/macOS, referencing cross-platform tools like VS Code and .NET CLI.
  • Provide parity in migration guides for Linux-based workloads, including ASP.NET Core on Linux and containerization with Linux containers.
  • Explicitly mention platform support and limitations for Service Fabric Managed Clusters, including Linux compatibility.
  • Reorder examples so that cross-platform tools (Azure CLI, VS Code, .NET CLI) are shown before or alongside Windows-specific tools.
  • Add troubleshooting steps relevant to Linux/macOS environments.
GitHub Create Pull Request
Service Fabric X.509 Certificate-based Authentication in a Service Fabric Cluster ...ticles/service-fabric/cluster-security-certificates.md
Medium 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 moderate Windows bias. Windows terminology (e.g., certificate stores like LocalMachine\My), Windows API references (Win32 CryptoAPI, CertGetCertificateChain), and troubleshooting steps (event logs, CAPI2 logging) are presented first and in detail, while Linux equivalents are mentioned briefly or parenthetically (e.g., 'Linux equivalent path, /var/lib/sfcerts'). There are no explicit Linux/macOS command-line examples, and troubleshooting guidance is focused on Windows tools and logs.
Recommendations
  • Provide Linux/macOS-specific examples for certificate storage, management, and troubleshooting (e.g., using OpenSSL, Linux file paths, systemd journal logs).
  • Include explicit instructions or references for Linux/macOS users on how to locate, install, and validate certificates in Service Fabric clusters.
  • Add troubleshooting steps for Linux clusters, such as where to find Service Fabric logs, how to enable verbose logging, and how to diagnose certificate issues using Linux-native tools.
  • Reference cross-platform APIs and tools where possible, or clarify platform-specific differences in configuration and behavior.
  • Ensure that examples and explanations are presented in a platform-neutral order, or provide parallel examples for both Windows and Linux/macOS.
GitHub Create Pull Request
Service Fabric Configure managed identity support in an existing Service Fabric cluster ...existing-cluster-enable-managed-identity-token-service.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation references viewing upgrade policy settings via PowerShell and the Azure portal, but does not mention or provide examples for Linux/macOS command-line tools (such as Azure CLI or Bash). The order of tool references and lack of Linux-specific guidance may create friction for non-Windows users.
Recommendations
  • Add explicit instructions and examples for performing cluster upgrades and viewing upgrade policies using Azure CLI and Bash, which are cross-platform.
  • Mention Linux/macOS compatibility for all steps, and clarify which tools are available on all platforms.
  • Provide parity in troubleshooting steps, ensuring error investigation can be performed using cross-platform tools.
  • Avoid referencing PowerShell or Windows tools first unless they are the only option; otherwise, present cross-platform options equally.
GitHub Create Pull Request
Service Fabric Manage certificates in a Service Fabric cluster ...vice-fabric/cluster-security-certificate-management.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. PowerShell is the only scripting language shown for certificate enrollment automation, and Windows-specific tooling (such as the Key Vault VM extension for Windows and S-channel APIs) is referenced exclusively or explained in detail. There are no Linux/macOS equivalents or examples for certificate provisioning, automation, or troubleshooting. Windows patterns (e.g., certificate store locations, ACLing, linking on renewal) are described first and in depth, while Linux approaches are absent.
Recommendations
  • Add Linux/macOS examples for certificate enrollment, provisioning, and automation (e.g., using Azure CLI, Bash scripts, or Python SDK).
  • Reference and link to the Key Vault VM extension for Linux, and explain any differences in behavior or configuration.
  • Describe certificate store locations and access control mechanisms for Linux (e.g., /etc/ssl/certs, file permissions) alongside Windows registry/store details.
  • Provide troubleshooting steps and FAQs relevant to Linux/macOS environments.
  • When discussing features that are Windows-only (e.g., S-channel, CERT_RENEWAL_PROP_ID), clearly note their platform specificity and suggest Linux alternatives if available.
GitHub Create Pull Request
Service Fabric Deploy an application to a managed cluster using Azure Resource Manager ...bric/how-to-managed-cluster-app-deployment-template.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 documentation page demonstrates a notable Windows bias. All command-line examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzServiceFabricManagedClusterApplication) with no mention of Azure CLI or Bash equivalents. The application packaging workflow is described using Visual Studio, a Windows-centric tool, and file paths use Windows conventions. There are no Linux/macOS-specific instructions or examples, and Windows tools and patterns are presented exclusively and first.
Recommendations
  • Add Azure CLI examples for deployment, upgrade, and deletion steps alongside PowerShell commands.
  • Include instructions for packaging the application using cross-platform tools (e.g., dotnet CLI, zip utilities) rather than only Visual Studio.
  • Show file path examples using both Windows and Linux/macOS conventions.
  • Explicitly mention that the workflow can be performed on Linux/macOS and provide guidance for those platforms.
  • Reference cross-platform editors (e.g., VS Code) for editing templates and packaging applications.
GitHub Create Pull Request
Service Fabric Deploy application secrets to a Service Fabric managed cluster ...e-fabric/how-to-managed-cluster-application-secrets.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page demonstrates a moderate Windows bias by referencing Windows-specific tools and patterns, such as the Key Vault VM extension for Windows, and using terminology like 'certificate store name on the nodes, e.g.: "MY"' which is a Windows convention. The linked extension documentation is Windows-specific, and there is no mention of Linux/macOS equivalents or instructions for Linux-based Service Fabric clusters. Examples and references to certificate stores and installation methods are Windows-centric, with no Linux parity guidance.
Recommendations
  • Add explicit instructions and examples for deploying certificates and secrets on Linux-based Service Fabric clusters.
  • Reference and link to the Key Vault VM extension for Linux (if available), or provide alternative Linux-compatible methods for certificate management.
  • Clarify certificate store conventions for Linux (e.g., file paths, store names) and provide examples.
  • Ensure that both Windows and Linux approaches are presented side-by-side or in parallel sections.
  • Avoid using Windows-specific terminology without explanation or Linux equivalents.
GitHub Create Pull Request
Service Fabric Deploy app with a user-assigned managed identity ...vice-fabric-application-user-assigned-managed-identity.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation references PowerShell in the link for managing user-assigned managed identities, and does not mention or link to Linux/macOS CLI alternatives. The only external tool mentioned is PowerShell, suggesting a Windows-first approach. No explicit Linux/macOS examples or parity guidance are provided.
Recommendations
  • Include links to Azure CLI and/or REST API documentation for managing user-assigned managed identities, which are cross-platform.
  • Explicitly mention that the steps can be performed on Linux/macOS using Azure CLI or other non-Windows tools.
  • Provide example commands for both PowerShell and Azure CLI where relevant.
  • Review all external links to ensure Linux/macOS users are not directed exclusively to Windows-centric tooling.
GitHub Create Pull Request
Service Fabric Use Application Gateway in a Service Fabric managed cluster ...e-fabric/how-to-managed-cluster-application-gateway.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 notable Windows bias by exclusively providing PowerShell examples for critical steps such as obtaining the Service Principal ID and assigning roles. No equivalent Azure CLI, Bash, or Linux/macOS instructions are offered. The PowerShell commands are presented first and as the only option for command-line interaction, which may create friction for users on Linux or macOS platforms.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, especially for service principal retrieval and role assignment.
  • Explicitly mention that all steps can be performed on Linux/macOS using Azure CLI or Bash, and provide those instructions.
  • Reorder examples so that platform-neutral (ARM template) or CLI instructions are shown before or alongside PowerShell.
  • Include a note clarifying cross-platform support and linking to Azure CLI documentation.
GitHub Create Pull Request
Service Fabric Configure and use applications with managed identity on a Service Fabric managed cluster ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/how-to-managed-cluster-application-managed-identity.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation references PowerShell in the context of managing user-assigned identities and links to a PowerShell-specific guide, without mentioning or providing equivalent examples for Linux/macOS users (e.g., Azure CLI or Bash). No Linux/macOS tools or patterns are discussed, and Windows tooling is implicitly prioritized.
Recommendations
  • Include Azure CLI and Bash examples alongside PowerShell for managing user-assigned identities.
  • Reference cross-platform documentation (e.g., Azure CLI guides) when linking to how-to guides.
  • Explicitly state that all steps can be performed on Linux/macOS and provide relevant command-line examples.
  • Add a section or note clarifying tool parity and platform support.
GitHub Create Pull Request
Service Fabric Import certificates into a container ...s/service-fabric/service-fabric-securing-containers.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 moderate Windows bias. Windows-specific details (such as PFX handling, environment variables, and ACLs) are explained first and in greater depth. The only code example provided is C# code for importing a PFX certificate, which is directly relevant to Windows. Linux handling is described briefly, with no code samples or practical import instructions. Windows tools and patterns (PFX, ACLs, X509Store) are mentioned exclusively, while Linux equivalents (PEM, OpenSSL, file permissions) are not covered.
Recommendations
  • Provide equivalent Linux code samples (e.g., using OpenSSL or Linux certificate stores) for importing PEM certificates and private keys.
  • Describe Linux file permission management for certificate files, analogous to the Windows ACL discussion.
  • Present Windows and Linux instructions/examples in parallel, rather than focusing on Windows first.
  • Mention Linux-specific tools and patterns (such as openssl, chmod, etc.) where appropriate.
  • Clarify differences in certificate handling between platforms, including security implications.
GitHub Create Pull Request
Service Fabric Specifying Service Fabric service endpoints ...ce-fabric/service-fabric-service-manifest-resources.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 demonstrates a moderate Windows bias. The only concrete deployment example uses Windows PowerShell (New-ServiceFabricApplication), and the Service Fabric SDK schema location is referenced using a Windows file path. Linux-specific details are limited to a brief mention of the certificate store location, and no Linux/macOS CLI examples (such as Azure CLI or Bash) are provided. Windows tools and patterns are mentioned first and more prominently.
Recommendations
  • Add Linux/macOS deployment examples using Azure CLI or Bash scripts alongside PowerShell examples.
  • Reference Linux file paths for SDK/schema locations in addition to Windows paths.
  • Explicitly mention cross-platform tools and workflows where possible, and clarify any platform-specific differences.
  • Ensure that all examples and instructions are applicable to both Windows and Linux clusters, or clearly indicate platform limitations.
GitHub Create Pull Request
Virtual Machines Set up Azure HPC or AI VMs .../blob/main/articles/virtual-machines/set-up-hpc-vms.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation generally maintains parity between Linux and Windows, offering links to both Linux and Windows quickstarts, disk attachment guides, and GPU driver installation instructions. However, in the 'Set up VM' section, there is no link to an AMD GPU driver installation guide for Linux, while there is one for Windows. Additionally, in the driver installation section, Windows links are listed before Linux for AMD drivers, which may indicate a slight 'windows_first' bias.
Recommendations
  • Add a link or instructions for installing AMD GPU drivers on Linux VMs, if supported.
  • Ensure that Linux and Windows instructions are presented in parallel order (e.g., always list Linux first or alternate consistently).
  • Explicitly state if certain features (such as AMD GPU drivers) are not supported on Linux, to avoid confusion.
  • Where possible, provide example commands for both Linux (bash/ssh) and Windows (PowerShell/SSH) in sections that discuss connecting or configuring the VM.
GitHub Create Pull Request
Service Fabric Configure autoscaling for Service Fabric managed cluster nodes ...les/service-fabric/how-to-managed-cluster-autoscale.md
Medium 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 significant Windows bias. All command-line examples use PowerShell cmdlets (e.g., New-AzResourceGroup, New-AzResourceGroupDeployment, Remove-AzResource), which are native to Windows and require either Windows or PowerShell Core on Linux/macOS. There are no equivalent Azure CLI or bash examples provided for Linux/macOS users. The troubleshooting section also references PowerShell modules exclusively. The documentation assumes familiarity with Windows tooling and does not mention Linux-native alternatives or provide guidance for non-Windows environments.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, ensuring Linux/macOS users can follow along without installing PowerShell.
  • Explicitly mention that PowerShell Core can be installed on Linux/macOS, or recommend Azure CLI as the preferred cross-platform tool.
  • Reorder examples so that Azure CLI (cross-platform) is shown first, or at least in parallel with PowerShell.
  • Include troubleshooting steps using Azure CLI and reference Linux/macOS compatibility.
  • Clarify any OS-specific limitations or requirements, especially in the context of autoscale metrics and deployment tooling.
GitHub Create Pull Request
Service Fabric Use Azure DDoS Protection in a Service Fabric managed cluster ...rvice-fabric/how-to-managed-cluster-ddos-protection.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 notable Windows bias by providing only Azure PowerShell examples for critical steps, such as retrieving the Service Principal and assigning roles. There is no mention of equivalent Azure CLI commands, which are cross-platform and preferred by many Linux/macOS users. The PowerShell examples are presented first and exclusively, with no alternative instructions for non-Windows environments.
Recommendations
  • Add Azure CLI command examples alongside PowerShell for all steps involving resource management and role assignments.
  • Explicitly mention that Azure CLI is supported and provide links to CLI documentation.
  • Where possible, present CLI and PowerShell examples side-by-side, or indicate which tools are cross-platform.
  • Clarify that ARM templates and Azure Portal are platform-agnostic, and encourage their use for users on Linux/macOS.
GitHub Create Pull Request
Service Fabric Add Azure Dedicated Host to a Service Fabric managed cluster (SFMC) ...rvice-fabric/how-to-managed-cluster-dedicated-hosts.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 notable Windows bias by exclusively providing PowerShell-based examples for all command-line operations, such as authentication, resource group creation, and role assignment. There are no CLI (az) or Bash/Linux/macOS shell equivalents, and PowerShell is assumed as the default automation tool. This creates friction for Linux and macOS users who typically use Azure CLI and Bash. Additionally, Windows-centric terminology (e.g., RDP admin credentials) is presented without Linux alternatives.
Recommendations
  • Add Azure CLI (az) command examples alongside PowerShell for all resource management and deployment steps.
  • Include Bash shell script snippets for Linux/macOS users.
  • Mention SSH as an alternative to RDP for VM access, and clarify admin credential requirements for Linux VMs.
  • Explicitly state that all steps can be performed from Linux/macOS and provide links to cross-platform tooling.
  • Reorder examples so that CLI and PowerShell are presented together, or CLI first, to avoid Windows-first impression.
GitHub Create Pull Request
Service Fabric Delete a Service Fabric cluster in Azure ...rvice-fabric/service-fabric-tutorial-delete-cluster.md
Medium 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 demonstrates a Windows bias by focusing on Windows clusters in the tutorial series, referencing Windows-specific management and monitoring tools, and providing PowerShell examples (which are Windows-centric, though available cross-platform). There is no mention of Linux clusters, and all cluster creation and management examples assume a Windows environment. Linux-specific guidance, such as for Linux-based Service Fabric clusters or Linux node patching, is absent.
Recommendations
  • Include explicit instructions and examples for creating, managing, and deleting Linux-based Service Fabric clusters.
  • Balance references to Windows tools (e.g., Service Fabric Explorer, Windows patching) with Linux equivalents or note differences.
  • Add Linux-specific sections or callouts, especially for cluster node management and diagnostics.
  • Clarify when instructions apply to both Windows and Linux clusters, or provide parallel workflows.
  • Reference documentation for Linux cluster patching and diagnostics where available.
GitHub Create Pull Request
Virtual Machines Creating and configuring a key vault for Azure Disk Encryption with Microsoft Entra ID (previous release) ...irtual-machines/linux/disk-encryption-key-vault-aad.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 extensive PowerShell-based examples and scripts, including advanced scenarios, and references Windows filesystem paths (e.g., C:\certificates\mycert.pfx) and Windows-centric tools. While Azure CLI examples are present for basic operations, advanced and end-to-end scenarios (such as certificate-based authentication and key encryption key setup) are only shown with PowerShell, with no Linux shell or cross-platform alternatives. There are no bash, shell, or Linux-native scripting examples, and some steps (like certificate handling) are described using Windows file paths and tools. Certificate-based authentication is explicitly noted as unsupported on Linux, but the documentation does not offer Linux alternatives or clarify Linux-specific workflows for these advanced tasks.
Recommendations
  • Provide bash or shell script equivalents for all PowerShell examples, especially for advanced scenarios such as KEK setup and certificate management.
  • Use cross-platform file paths and examples (e.g., /home/user/certificates/mycert.pfx) alongside Windows paths.
  • Clearly indicate which steps are Windows-only and provide Linux-specific guidance or workarounds where features are unsupported.
  • Expand Azure CLI coverage to include all advanced scenarios, not just basic key vault creation and policy setting.
  • Add explicit notes or sections for Linux users, detailing any limitations and alternative approaches.
GitHub Create Pull Request
Virtual Machines How to upgrade Azure Disk Encryption on a disk ...cles/virtual-machines/linux/disk-encryption-upgrade.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 exhibits notable Windows bias. The migration process is only documented and supported via Azure PowerShell, with no CLI or Linux-native instructions. All upgrade examples use PowerShell, and the migration section does not mention Linux-specific steps or alternatives, despite referencing Linux ADE versions earlier. This creates friction for Linux users who may not use PowerShell or Windows environments.
Recommendations
  • Provide equivalent Azure CLI instructions for migration, or clearly state if CLI is not supported for this operation.
  • Document Linux-specific considerations or limitations for ADE migration, including any required tools or workarounds.
  • If migration is truly only possible via PowerShell, offer guidance for Linux users on installing and using PowerShell Core on Linux, or accessing Azure Cloud Shell.
  • Present examples for both Windows and Linux platforms, or clarify platform restrictions early in the article.
GitHub Create Pull Request
Virtual Machines Troubleshooting Azure Disk Encryption for Linux VMs ...tual-machines/linux/disk-encryption-troubleshooting.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation is focused on Linux VMs and provides Linux-specific troubleshooting steps. However, when discussing how to check encryption status and disable disk encryption, PowerShell commands are presented first and in greater detail, with Linux/Azure CLI equivalents mentioned only briefly or after the PowerShell examples. This ordering and emphasis may create friction for Linux users who are more likely to use Azure CLI or Bash.
Recommendations
  • Provide Azure CLI examples alongside or before PowerShell examples, especially in sections relevant to Linux users.
  • Include Bash script examples for common troubleshooting tasks, such as checking encryption status.
  • Clarify which commands are platform-agnostic (e.g., Azure CLI) and which are Windows-specific (e.g., PowerShell), and guide Linux users to the most appropriate tools.
  • Ensure parity in detail and explanation between PowerShell and CLI/Bash instructions.
GitHub Create Pull Request
Service Fabric Enable Disk Encryption for Service Fabric managed cluster nodes ...abric/how-to-managed-cluster-enable-disk-encryption.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 documentation page exhibits a notable Windows bias. The introduction and most examples are explicitly for Windows, with ARM template and PowerShell commands shown exclusively or first. Linux support is mentioned only in passing, with no Linux-specific instructions, verification steps, or troubleshooting guidance. The use of PowerShell and references to Windows tools dominate, and Azure CLI is only briefly mentioned for Key Vault creation and update, not for deployment or verification. There are no examples for Linux users on how to deploy, verify, or troubleshoot disk encryption for Service Fabric managed clusters.
Recommendations
  • Add explicit Linux-focused sections, including deployment and verification steps for disk encryption on Linux-based Service Fabric managed cluster nodes.
  • Provide Azure CLI examples for all steps, not just Key Vault creation and update, including deployment and verification.
  • Include troubleshooting tips and verification commands for Linux environments (e.g., using SSH, Linux-native tools, or Azure CLI).
  • Clarify which instructions apply to both Windows and Linux, and highlight any differences.
  • Reference Linux documentation and provide links to Linux-specific guides where appropriate.
GitHub Create Pull Request
Service Fabric Configure maintenance control for Service Fabric managed cluster ...e-fabric/how-to-managed-cluster-maintenance-control.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 exclusively uses PowerShell commands for all deployment and management steps, with no mention of Azure CLI, Bash, or Linux/macOS-compatible workflows. All code examples and instructions assume a Windows environment, creating friction for users on Linux or macOS platforms.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and works natively on Linux/macOS.
  • Explicitly mention that the steps can be performed on Linux/macOS using Azure CLI or REST API.
  • Provide Bash script samples or instructions for Linux users where appropriate.
  • Reorder examples so that cross-platform tools (Azure CLI, REST API) are presented before or alongside PowerShell.
GitHub Create Pull Request
Service Fabric Upgrading Azure Service Fabric managed clusters ...cles/service-fabric/how-to-managed-cluster-upgrades.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 listing only Windows-based Service Fabric cluster versions in its examples and omitting Linux equivalents. The REST API output exclusively references Windows environments, and there are no examples or guidance for Linux-based clusters or their upgrade process. This may cause confusion or friction for users managing Linux clusters.
Recommendations
  • Include examples of Linux-based Service Fabric cluster versions in the REST API output section.
  • Explicitly mention Linux support and provide instructions or examples for upgrading Linux clusters.
  • Clarify whether upgrade procedures differ for Linux clusters and link to relevant documentation if so.
  • Ensure that references to supported versions and operating systems include both Windows and Linux, or state any limitations.
GitHub Create Pull Request
Service Fabric Add a virtual machine scale set extension to a Service Fabric managed cluster node type ...ervice-fabric/how-to-managed-cluster-vmss-extension.md
Medium 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 demonstrates a notable Windows bias: it only provides a PowerShell command for adding VM extensions, omits CLI or Linux/macOS instructions, and uses Windows-specific extension types (e.g., KeyVaultForWindows). Examples and tooling references are Windows-centric, with no parity for Linux users.
Recommendations
  • Add Azure CLI and/or REST API examples for adding VM extensions, which are cross-platform.
  • Include examples of Linux-compatible VM extensions (e.g., KeyVaultForLinux) in ARM template samples.
  • Explicitly mention how Linux/macOS users can perform equivalent operations, including any differences in extension types or setup.
  • Reorder examples or provide parallel examples for both Windows and Linux to avoid Windows-first presentation.
GitHub Create Pull Request
Service Fabric Configure or modify a Service Fabric managed cluster node type ...vice-fabric/how-to-managed-cluster-modify-node-type.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 consistently provides PowerShell examples for command-line operations (add, remove, scale, configure properties), but does not mention or provide equivalent examples for Linux/macOS users (e.g., Azure CLI, Bash, or cross-platform scripting). PowerShell is Windows-centric, and its use is assumed throughout, creating friction for users on other platforms. Additionally, Windows tools and patterns (e.g., drive letters, PowerShell cmdlets) are referenced without Linux alternatives or context.
Recommendations
  • Add Azure CLI examples for all operations currently shown with PowerShell, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that PowerShell cmdlets can be run on Linux/macOS (via PowerShell Core), or provide Bash script equivalents where possible.
  • Where drive letters or Windows-specific concepts are referenced (e.g., diskLetter), clarify behavior on Linux-based node types or note any differences.
  • Ensure that examples and instructions do not assume a Windows environment; include notes or sections for Linux/macOS users where relevant.
  • Consider listing Azure CLI examples before or alongside PowerShell to avoid 'windows_first' bias.
GitHub Create Pull Request
Service Fabric Configure network settings for Service Fabric managed clusters ...es/service-fabric/how-to-managed-cluster-networking.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 exhibits a notable Windows bias, primarily through the exclusive use of PowerShell for command-line examples, frequent references to Windows-specific tools (such as Remote Desktop Connection), and explicit mention of Windows clusters in RDP/NAT sections. There are no CLI/bash examples or guidance for Linux/macOS users, and Windows terminology and screenshots are used without Linux equivalents.
Recommendations
  • Provide Azure CLI (az) and/or Bash examples alongside PowerShell commands for all resource management and deployment steps.
  • Include instructions and screenshots for connecting to Linux-based nodes (e.g., using SSH) in sections discussing remote access and NAT rules.
  • Clarify when steps or features apply to both Windows and Linux clusters, and note any differences.
  • Reference cross-platform tools (e.g., VS Code, SSH clients) where appropriate, not just Windows-only tools.
  • Reorder examples so that platform-neutral or cross-platform approaches are presented first, or side-by-side.
GitHub Create Pull Request
Service Fabric Add a managed identity to a Service Fabric managed cluster node type ...ed-identity-managed-cluster-virtual-machine-scale-sets.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 notable Windows bias by providing only PowerShell-based command-line examples for resource creation, role assignment, and deployment. There are no equivalent examples using Bash, Azure CLI, or Linux/macOS-native tools. Additionally, VM image properties in the ARM template examples exclusively reference Windows Server images, with no mention of Linux-based node types or images. This prioritization of Windows tools and patterns creates friction for Linux/macOS users.
Recommendations
  • Add Azure CLI (az) command examples alongside PowerShell for all resource creation, role assignment, and deployment steps.
  • Include Bash script snippets for template deployments and identity management.
  • Show ARM template examples using Linux VM images (e.g., Ubuntu) in addition to Windows Server.
  • Explicitly mention cross-platform compatibility and provide guidance for Linux/macOS environments.
  • Clarify that PowerShell commands can be run on Linux/macOS via PowerShell Core, or provide alternatives.
GitHub Create Pull Request
Service Fabric Deny assignment policy for Service Fabric managed clusters ...cles/service-fabric/managed-cluster-deny-assignment.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 moderate Windows bias. Azure PowerShell is referenced and linked as the primary example for cluster management tasks (deleting NodeTypes, restarting/reimaging scale sets), with no equivalent Linux/macOS command-line examples (e.g., Azure CLI or sfctl) shown for these operations. PowerShell-based workflows are described first and in detail, while Linux-friendly tools are only listed in a utility table and not exemplified in the main guidance.
Recommendations
  • Add explicit Azure CLI and sfctl command examples for all major management tasks (deleting NodeTypes, restarting/reimaging scale sets) alongside PowerShell examples.
  • When referencing PowerShell, always mention that equivalent operations can be performed with Azure CLI or sfctl, and provide links.
  • In best practices, present Azure CLI and sfctl examples before or alongside PowerShell to avoid Windows-first ordering.
  • Clarify platform compatibility for each tool in the utility table (e.g., note that Azure CLI and sfctl are cross-platform).
GitHub Create Pull Request
Container Instances Config Maps for Azure Container Instances .../container-instances/container-instances-config-map.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 both Azure CLI and PowerShell examples for all major workflows, but PowerShell (a Windows-centric tool) is given equal prominence to CLI, and some advanced object construction is only shown in PowerShell. Additionally, Windows container behavior is described using Windows-specific tools (Invoke-Expression, $Env:ConfigMapURI) without offering Linux equivalents for similar tasks. In the section on how config maps are surfaced in containers, the Windows method is described after the Linux method, but relies solely on Windows-native tooling.
Recommendations
  • Ensure that all PowerShell examples have equivalent Bash or shell script examples for Linux/macOS users, especially for advanced object construction.
  • Where Windows-specific tools (e.g., Invoke-Expression, $Env:ConfigMapURI) are mentioned, provide Linux equivalents or clarify that the method is Windows-only.
  • Consider listing CLI (cross-platform) examples before PowerShell examples to reduce perceived Windows-first bias.
  • Add explicit notes or links for Linux/macOS users on how to perform similar tasks using native tools.
  • Clarify any differences in config map mounting or access between Linux and Windows containers, and provide troubleshooting or workaround guidance for each platform.
GitHub Create Pull Request
Service Fabric Introduction to the Service Fabric Infrastructure Service .../articles/service-fabric/infrastructure-service-faq.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 provides a PowerShell-only example for bypassing the Infrastructure Service, with no equivalent Linux/macOS command or guidance. The use of PowerShell and Service Fabric Explorer (a GUI tool typically used on Windows) further reinforces a Windows-centric approach, while Linux users are left without clear instructions for performing the same operation.
Recommendations
  • Add equivalent CLI examples for Linux/macOS environments, such as using Azure CLI, Bash, or REST API.
  • Clarify whether the PowerShell command can be run from Azure Cloud Shell (which supports both Bash and PowerShell) or provide alternative instructions.
  • Mention cross-platform tools or interfaces for managing Service Fabric clusters, and link to relevant documentation.
  • Explicitly state platform requirements for Service Fabric Explorer and suggest alternatives if available.
GitHub Create Pull Request
Virtual Machines Create SSH keys with the Azure CLI ...b/main/articles/virtual-machines/ssh-keys-azure-cli.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ linux_first ⚠ī¸ missing_windows_example
Summary
The documentation is strongly Linux-oriented, with all command-line examples using Linux paths, Bash commands, and Linux file permission patterns. There are no Windows-specific instructions, examples, or PowerShell/CMD equivalents for generating, storing, or using SSH keys. Windows users may struggle to follow the steps as written.
Recommendations
  • Add Windows-specific examples using PowerShell or CMD, including file paths (e.g., C:\Users\username\.ssh\...) and permission management.
  • Provide guidance on using SSH from Windows (e.g., via PowerShell, Windows Terminal, or PuTTY), especially for connecting to VMs.
  • Include notes about differences in file system paths and permission handling between Linux/macOS and Windows.
  • Ensure parity by presenting both Linux and Windows workflows side-by-side where relevant.
GitHub Create Pull Request
Virtual Machines Tenable One-Click Nessus Extension for Azure VMs ...b/main/articles/virtual-machines/extensions/tenable.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 exhibits a notable Windows bias in its command-line deployment section. Only PowerShell examples are provided, with no equivalent Bash/CLI examples for Linux users. The command-line workflow is described exclusively in PowerShell syntax, and Windows-centric tooling is referenced before any Linux alternatives (which are not mentioned at all). While the UI workflow is cross-platform, Linux users are left without clear CLI guidance.
Recommendations
  • Add Bash/Azure CLI examples for deploying the Nessus Agent extension on Linux VMs.
  • Explicitly mention and demonstrate Linux-compatible command-line tools (e.g., az CLI) alongside PowerShell.
  • Ensure parameter descriptions and workflows are not PowerShell-specific and clarify cross-platform applicability.
  • Present Windows and Linux examples side-by-side or alternate which is shown first.
GitHub Create Pull Request
Virtual Machines Azure support for Generation 2 VMs ...cs/blob/main/articles/virtual-machines/generation-2.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 moderate Windows bias. Windows examples (especially PowerShell) are provided in detail, while Linux equivalents are less prominent or missing in some sections. Windows tools and patterns (e.g., PowerShell, Windows-specific image SKUs) are mentioned first or exclusively in several places, and Linux users may need to infer or search for their own workflows.
Recommendations
  • Provide Linux-specific CLI or scripting examples alongside PowerShell, especially for tasks like creating managed disks from .vhd files and setting Hyper-V Generation property.
  • Ensure that Linux examples are presented with equal prominence and detail as Windows examples, including step-by-step instructions.
  • Reference Linux documentation links directly in relevant sections, not just in 'Next steps'.
  • When listing commands or workflows, alternate the order or present both Windows and Linux options together.
  • Clarify any differences or limitations for Linux users in FAQ and procedural sections.
GitHub Create Pull Request
Service Fabric Deploy a Service Fabric managed cluster using the Azure portal ...es/service-fabric/quickstart-managed-cluster-portal.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 is heavily focused on using the Azure portal GUI for all steps, which is platform-neutral. However, the cluster created uses Windows Server 2019-Datacenter VMs exclusively, and there is no mention of Linux-based clusters or how to access/manage the cluster from Linux/macOS clients. Instructions for importing certificates and accessing Service Fabric Explorer implicitly assume Windows certificate stores and browsers, with no guidance for Linux/macOS users. No PowerShell or CLI examples are given, but the lack of Linux parity in cluster OS and client instructions creates friction for non-Windows users.
Recommendations
  • Explicitly mention whether Linux-based managed clusters are supported, and provide instructions if so.
  • Add guidance for importing and using client certificates on Linux and macOS (e.g., using OpenSSL, browser certificate stores, etc.).
  • Include notes or examples for accessing Service Fabric Explorer from Linux/macOS browsers.
  • If possible, provide parity for cluster OS selection (Windows and Linux) and document the differences.
  • Clarify any limitations for non-Windows users in the quickstart prerequisites.
GitHub Create Pull Request
Service Fabric Monitor a Service Fabric cluster in Azure ...vice-fabric/service-fabric-tutorial-monitor-cluster.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 exhibits a notable Windows bias. It repeatedly references creating and monitoring a 'Windows cluster' without mentioning Linux clusters or providing Linux-specific instructions. Performance counter monitoring is described exclusively for Windows, and PowerShell cmdlets are used for health queries with no Linux or cross-platform CLI alternatives shown. Windows tools and references (e.g., Windows Performance Counters, PowerShell, Windows-specific articles) are mentioned exclusively or before any Linux equivalents, and there are no Linux/macOS examples or guidance for users of those platforms.
Recommendations
  • Add explicit instructions and examples for monitoring Service Fabric clusters running on Linux, including how to set up diagnostics, collect performance counters, and view health reports.
  • Include Azure CLI and REST API examples for health queries, not just PowerShell cmdlets.
  • Reference Linux performance counter collection methods and provide links to relevant documentation.
  • Clarify which steps and tools are Windows-only and provide Linux/macOS alternatives where possible.
  • Update prerequisites to mention Linux clusters and provide links to Linux cluster creation tutorials.
GitHub Create Pull Request
Service Fabric Visualizing your cluster using Azure Service Fabric Explorer ...vice-fabric/service-fabric-visualizing-your-cluster.md
Medium 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 exhibits several instances of Windows bias. While Service Fabric Explorer is described as cross-platform, key features such as EventStore APIs are explicitly stated to be available only for Windows clusters on Azure, with Linux support still in development. Automation examples reference PowerShell and REST API, but do not mention Linux-native tools or provide equivalent Linux/macOS command-line examples. The 'Next steps' section prioritizes Windows-centric tools (Visual Studio, PowerShell) and omits Linux/macOS alternatives. There is also a lack of explicit Linux/macOS usage instructions or screenshots.
Recommendations
  • Provide Linux/macOS command-line examples (e.g., using Bash, CLI tools) alongside PowerShell references.
  • Clarify feature parity and availability for Linux clusters, and update documentation as Linux support improves.
  • Include Linux/macOS-specific troubleshooting and setup instructions where relevant.
  • Add references to cross-platform deployment/management tools (such as Azure CLI, or Service Fabric CLI) in the 'Next steps' section.
  • Ensure screenshots and UI walkthroughs reflect usage on all supported platforms.
GitHub Create Pull Request
Virtual Machines Overview of Maintenance control for OS image upgrades on Azure Virtual Machine Scale Sets ...ines/virtual-machine-scale-sets-maintenance-control.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 emphasizing Azure PowerShell as the primary management option, listing it first among alternatives, and featuring a PowerShell-specific 'Next steps' link. There is no explicit mention or prioritization of Linux-native tools or examples, such as Bash or shell scripting, nor is there guidance tailored for Linux/macOS users.
Recommendations
  • Provide Linux/macOS-specific examples using Azure CLI and Bash scripting.
  • Alternate the order of management options to avoid always listing PowerShell first.
  • Include 'Next steps' links for both PowerShell and Azure CLI to ensure parity.
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Add a section or note highlighting differences or considerations for Linux/macOS environments.
GitHub Create Pull Request
Service Fabric Learn about Azure Service Fabric application security ...ric/service-fabric-application-and-service-security.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 exhibits a moderate Windows bias. Windows-specific tools and patterns (Active Directory, gMSA, BitLocker) are mentioned explicitly, often before or without Linux equivalents. Examples and guidance for running services under specific accounts are detailed for Windows (domain accounts, gMSA), while Linux options are referenced only briefly or left as TODOs. Disk encryption is described with a Windows PowerShell link, but Linux disk encryption is not covered. Some sections (e.g., securing containers) mention Linux support, but details and examples are sparse compared to Windows.
Recommendations
  • Add explicit Linux examples for running services under different user accounts, including how to configure principals and policies on Linux clusters.
  • Provide guidance and examples for encrypting disks on Linux clusters, such as using dm-crypt or Azure Disk Encryption for Linux.
  • Include Linux/macOS equivalents for Windows-specific tools (e.g., alternatives to Active Directory, gMSA) or clarify cross-platform options.
  • Balance examples and walkthroughs so that Linux instructions are presented alongside Windows, not as afterthoughts or TODOs.
  • Where possible, use platform-agnostic language and highlight cross-platform features.
GitHub Create Pull Request
Service Fabric Deploy and upgrade with Azure Resource Manager ...vice-fabric/service-fabric-application-arm-resource.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 page demonstrates a notable Windows bias. PowerShell is the only command-line example provided for resource removal, with no equivalent Bash, Azure CLI, or Linux/macOS instructions. Windows tools and terminology (PowerShell, Remove-AzResource) are referenced exclusively or before alternatives. The 'Next steps' section lists PowerShell before CLI, and the page lacks explicit Linux/macOS guidance for key operations.
Recommendations
  • Provide Azure CLI and Bash examples alongside PowerShell for all command-line operations, especially for resource removal.
  • Explicitly mention that all ARM template operations can be performed from Linux/macOS using Azure CLI or REST API, and link to relevant documentation.
  • In 'Next steps', list cross-platform tools (CLI, REST API) before or alongside PowerShell.
  • Add notes or sections clarifying platform parity and any differences in workflow for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Application lifecycle in Service Fabric ...service-fabric/service-fabric-application-lifecycle.md
Medium 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 notable Windows bias by consistently referencing PowerShell cmdlets and Windows-centric tools for Service Fabric management tasks. While REST API and .NET methods are mentioned, PowerShell examples are given for almost every operation, with no explicit Linux or cross-platform CLI (sfctl, Azure CLI) usage shown in examples or step-by-step instructions. The PowerShell cmdlets are often listed before REST or .NET alternatives, and there are no bash, Linux shell, or macOS-specific instructions or examples. This creates friction for Linux/macOS users, who must infer or seek out equivalent commands.
Recommendations
  • Add explicit examples using sfctl (Service Fabric CLI) and Azure CLI for all major lifecycle operations (deploy, upgrade, remove, test, etc.), alongside PowerShell.
  • Where PowerShell cmdlets are referenced, provide the Linux/macOS equivalent command immediately after or in parallel, not just as a footnote.
  • Include bash or shell script snippets for common tasks, especially in sections about automation and cleanup.
  • Clearly indicate which tools are cross-platform and which are Windows-only, and recommend cross-platform tools for general usage.
  • Reorder examples so that REST API, sfctl, and Azure CLI are shown first or equally with PowerShell, to avoid implicit prioritization of Windows tools.
GitHub Create Pull Request
Service Fabric Application upgrade: data serialization ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-application-upgrade-data-serialization.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 page demonstrates Windows bias primarily in the 'Next steps' section, where upgrade tutorials are provided for Visual Studio and PowerShell—both Windows-centric tools—without mention of Linux/macOS equivalents or cross-platform CLI options. The main body of the article is platform-neutral, focusing on C# and Service Fabric concepts, but the actionable guidance for upgrades is Windows-first and omits Linux-friendly alternatives.
Recommendations
  • Add explicit guidance and tutorials for upgrading applications on Linux/macOS, such as using Azure CLI, Service Fabric CLI (sfctl), or REST APIs.
  • Include links to cross-platform tools and documentation in the 'Next steps' section, ensuring parity with Windows instructions.
  • When listing upgrade methods, present cross-platform options before or alongside Windows-specific tools to avoid implicit prioritization.
  • Clarify which instructions are platform-specific and provide alternatives where possible.
GitHub Create Pull Request
Service Fabric Application upgrade: upgrade parameters ...abric/service-fabric-application-upgrade-parameters.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 by presenting PowerShell and Visual Studio (Windows-only tools) as primary methods for application upgrade, with their parameters described in detail and listed before the cross-platform SFCTL CLI. Examples and parameter tables are heavily focused on PowerShell and Visual Studio, with Linux/macOS equivalents (SFCTL) relegated to a later section and described less thoroughly. There are no direct Linux shell examples, and the structure implies Windows tools are the default or preferred approach.
Recommendations
  • Present SFCTL (cross-platform CLI) examples and parameter tables before or alongside PowerShell/Visual Studio sections to avoid implying Windows-first workflows.
  • Include explicit Linux/macOS shell command examples for SFCTL, demonstrating parity with PowerShell workflows.
  • Add a summary table comparing PowerShell, Visual Studio, and SFCTL parameters to clarify cross-platform equivalence.
  • Reference Linux/macOS upgrade workflows in introductory sections, not only in 'Next steps'.
  • Clarify that PowerShell and Visual Studio are Windows-only, and SFCTL is recommended for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Service Fabric application upgrade ...s/service-fabric/service-fabric-application-upgrade.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 page exhibits a notable Windows bias. The only code example provided uses PowerShell, a Windows-centric tool, with no equivalent Bash, CLI, or Linux-native example. Windows-specific tools and APIs (e.g., http.sys, PowerShell cmdlets) are referenced exclusively or before any cross-platform alternatives. The troubleshooting and next steps sections also prioritize Windows tools (Visual Studio, PowerShell) without mentioning Linux/macOS workflows or tools. There is no guidance for Linux users on how to perform the same upgrade tasks.
Recommendations
  • Add equivalent examples using Azure CLI, Bash scripts, or Service Fabric REST API for Linux/macOS users.
  • Clearly indicate which steps or tools are Windows-only and provide alternatives for Linux/macOS.
  • Reference Linux-native concepts (e.g., Kestrel instead of http.sys) where appropriate.
  • Include links to Linux/macOS-specific documentation or tutorials for Service Fabric application upgrades.
  • Ensure that upgrade instructions and troubleshooting steps cover both Windows and Linux environments.
GitHub Create Pull Request
Service Fabric Understanding periodic backup configuration ...-fabric-backuprestoreservice-configure-periodic-backup.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 exhibits a moderate Windows bias, particularly in the backup storage section. File share examples exclusively use Windows UNC paths (\\StorageServer\BackupStore) and reference Integrated Windows Authentication, with no mention of Linux-compatible storage options (e.g., NFS, SMB mounting on Linux, or Linux authentication methods). The examples and instructions for file share access are Windows-centric and do not provide parity for Linux/macOS users. Additionally, Windows authentication patterns are described first and in detail, while Linux alternatives are absent.
Recommendations
  • Add examples for configuring backup storage using Linux-compatible file shares (e.g., NFS paths, SMB mounts on Linux).
  • Describe how to authenticate to file shares from Linux nodes, including relevant credential formats and mount commands.
  • Clarify whether Service Fabric on Linux supports file share backup, and if so, provide explicit instructions and examples.
  • Present Windows and Linux options side-by-side or indicate platform-specific differences clearly.
  • Reference Linux documentation or tools where applicable.
GitHub Create Pull Request
Virtual Machines Customer intent: "As an IT administrator, I want to troubleshoot common VM extension failures in Azure Resource Manager templates, so that I can ensure the proper deployment and functionality of IaaS infrastructure." ...des/virtual-machines-common-extensions-troubleshoot.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 references authoring extension templates specifically for Windows, with a link to a Windows-focused template description. There is no mention of Linux or cross-platform equivalents, nor are Linux troubleshooting steps or examples provided.
Recommendations
  • Include links to Linux-specific template authoring documentation alongside the Windows link.
  • Provide examples and troubleshooting steps for both Windows and Linux VM extensions.
  • Clarify when instructions apply to all platforms, or specify platform differences where relevant.
GitHub Create Pull Request
Service Fabric Restoring backup in Azure Service Fabric ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-backup-restore-service-trigger-restore.md
Medium 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 biased toward Windows and PowerShell usage. All command-line examples use PowerShell, including REST API calls, and require installation of Windows-specific modules. There are no Linux/macOS shell examples (e.g., Bash, curl), nor are cross-platform alternatives mentioned. Windows tools and patterns are referenced exclusively and first, creating friction for Linux/macOS users.
Recommendations
  • Provide equivalent Bash/curl examples for all REST API interactions.
  • Document how to install and use Service Fabric CLI (sfctl) or REST calls on Linux/macOS.
  • Clarify which steps are Windows-only and offer Linux/macOS alternatives where possible.
  • Mention cross-platform authentication and certificate handling approaches.
  • Add notes or sections for Linux/macOS users, including troubleshooting and environment setup.
GitHub Create Pull Request
Virtual Machine Scale Sets Encrypt disks for Azure scale sets with Azure CLI ...cles/virtual-machine-scale-sets/disk-encryption-cli.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_heavy ⚠ī¸ minor_linux_example
Summary
The documentation is titled and described as focused on Windows Virtual Machine Scale Sets, but the main CLI examples use Linux images and extensions. However, the overall framing, references, and some links (e.g., PowerShell, batch file) are Windows-centric, and Linux parity is not emphasized or clearly separated. Linux is supported, but not highlighted or explained in depth.
Recommendations
  • Clarify in the title and introduction that both Windows and Linux VMSS are supported, or provide separate guides for each.
  • Provide explicit Linux and Windows example sections, with clear instructions for both OS types.
  • Add more Linux-specific context, such as common troubleshooting steps, differences in encryption support, and links to Linux documentation.
  • Avoid referring to batch files for Linux (should use shell scripts), and ensure Linux examples use native Linux tooling and terminology.
  • List Linux examples before or alongside Windows examples to avoid Windows-first bias.
GitHub Create Pull Request
Virtual Machines Use virtual machine restore points ...ual-machines/virtual-machines-create-restore-points.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 subtle Windows bias by describing application consistency primarily in terms of Windows (VSS writers) and only briefly mentioning Linux (pre- and postscripts) without providing equivalent detail or examples. There are no Linux-specific instructions, examples, or tool references, while Windows mechanisms (VSS) are named and explained first.
Recommendations
  • Provide explicit Linux examples for implementing application-consistent restore points, such as sample pre- and post-script templates.
  • Include references to common Linux backup tools or patterns that can be used with Azure VM restore points.
  • Ensure parity in explanation depth for both Windows and Linux, describing how Linux users can achieve application consistency step-by-step.
  • Consider listing Linux and Windows mechanisms side-by-side, or alternating which is mentioned first.
GitHub Create Pull Request
Service Fabric Capacity planning and scaling for Azure Service Fabric ...bric/service-fabric-best-practices-capacity-scaling.md
Medium 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 notable Windows bias, particularly in the scaling procedures. PowerShell commands (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState) are referenced exclusively for manual scaling operations, with no equivalent Linux CLI or bash examples. The step-by-step instructions for scaling in/out are written as if PowerShell is the only available tool, and no mention is made of Service Fabric CLI (sfctl) or REST API alternatives. Windows tools and patterns are assumed, and Windows-centric terminology appears before Linux equivalents. While there are links to Linux cluster creation, the operational guidance is Windows-focused.
Recommendations
  • Provide equivalent Linux examples using Service Fabric CLI (sfctl), bash scripts, or REST API calls for all PowerShell commands.
  • Explicitly mention cross-platform tools and workflows, and clarify which steps apply to both Windows and Linux clusters.
  • Reorder or parallelize instructions so that Linux and Windows approaches are presented side-by-side, rather than Windows-first.
  • Add notes or tables summarizing command equivalence between Windows (PowerShell) and Linux (sfctl/REST).
  • Ensure that all manual and programmatic scaling instructions are accessible to Linux users.
GitHub Create Pull Request
Service Fabric Azure Service Fabric networking best practices ...ice-fabric/service-fabric-best-practices-networking.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 moderate Windows bias. Windows terminology, tools, and examples (such as PowerShell and Windows-specific networking commands) are mentioned before or more prominently than Linux equivalents. Some sections, like API access and DevOps, reference PowerShell and Windows update processes without Linux parity or examples. ARM template and networking references often link to Windows samples first. Linux support is acknowledged but less detailed, and Linux-specific instructions or examples are missing in several areas.
Recommendations
  • Provide Linux CLI (az, bash) examples alongside or before PowerShell examples.
  • Include Linux-specific networking commands (e.g., how to view dynamic port ranges on Linux).
  • Add links to Linux ARM template samples and Linux-focused cluster setup guides where Windows ones are referenced.
  • Clarify when instructions or features differ for Linux clusters, and offer explicit guidance for Linux users.
  • Ensure DevOps and API access sections mention Linux-compatible tools and workflows.
  • Balance references to Windows and Linux containers and their networking modes.
GitHub Create Pull Request
Service Fabric Azure Service Fabric infrastructure as Code Best Practices ...tps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-best-practices-infrastructure-as-code.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 page exhibits several forms of Windows bias. PowerShell examples are provided for critical operations (such as cluster upgrades) without equivalent Linux/bash commands. Windows-specific tools and registry settings are mentioned for update management, while Linux alternatives are omitted. Windows configuration examples (e.g., disabling Windows Update) are shown in detail, but there is no parity for Linux VM configuration. In some sections, Windows instructions or references appear before Linux ones.
Recommendations
  • Provide bash or Linux shell command equivalents for all PowerShell examples, especially for cluster upgrades.
  • Include Linux-specific configuration guidance for VM update management, such as disabling automatic updates or patch orchestration on Linux VMs.
  • Add Linux-focused examples for deploying and managing Service Fabric clusters, not just referencing them in 'Next steps'.
  • Ensure that references to Windows and Linux resources are presented with equal prominence and detail.
  • Mention Linux tools and patterns (e.g., apt/yum, systemd) where relevant alongside Windows registry and configuration settings.
GitHub Create Pull Request
Service Fabric Differences between Cloud Services (extended support) and Service Fabric ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cloud-services-migration-differences.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 mentions Service Fabric running on both Windows and Linux, but examples, tool references, and API mappings are either Windows-centric or ambiguous. The API comparison table references Windows-specific tools (e.g., Connect-WindowsFabricCluster) without Linux equivalents, and there is no explicit guidance or examples for Linux users. Windows is often mentioned first, and Linux support is stated but not demonstrated.
Recommendations
  • Add explicit Linux examples and workflows, especially for cluster management and API usage.
  • Include Linux-specific tools or commands (e.g., Service Fabric CLI, REST API usage) alongside Windows tools like Connect-WindowsFabricCluster.
  • When listing platforms, alternate or balance the order (e.g., 'Windows or Linux' vs. 'Linux or Windows') to avoid subtle prioritization.
  • Clarify any platform-specific differences in deployment, management, or troubleshooting.
  • Provide links to Linux/macOS documentation and migration guides.
GitHub Create Pull Request
Service Fabric Service Fabric cluster capacity planning considerations ...cles/service-fabric/service-fabric-cluster-capacity.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 exhibits mild Windows bias. References to Windows-specific tools and patterns (such as Patch Orchestration Application for Windows updates and standalone clusters hosted in Windows) are present, and instructions for standalone cluster configuration are only provided for Windows. Linux equivalents (e.g., patch orchestration, configuration file locations, upgrade procedures) are missing or not mentioned. Windows scenarios are described before or instead of Linux ones, and PowerShell is referenced for cluster upgrade monitoring without mentioning Linux CLI alternatives.
Recommendations
  • Add explicit instructions and examples for Linux-based Service Fabric clusters, including configuration, upgrade, and patch orchestration procedures.
  • Mention Linux equivalents for standalone cluster management, such as configuration file locations and update automation tools.
  • When referencing tools (e.g., Patch Orchestration Application), clarify their applicability to both Windows and Linux, or provide Linux alternatives.
  • Include cross-platform CLI commands (e.g., Azure CLI, Service Fabric CLI) alongside PowerShell examples.
  • Ensure that Linux/macOS scenarios are described with equal prominence and detail as Windows scenarios.
GitHub Create Pull Request
Service Fabric Create an Azure Service Fabric cluster template ...ric/service-fabric-cluster-creation-create-template.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 exclusively providing PowerShell examples for testing the Resource Manager template, referencing Windows-centric sample templates, and omitting equivalent Linux/macOS CLI instructions. The only mention of Linux is a brief note about Microsoft Entra tenant creation, without actionable guidance or examples for Linux users.
Recommendations
  • Add Azure CLI examples for testing and deploying Resource Manager templates, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include links to Linux-specific Service Fabric sample templates, if available, or clarify Windows-specific aspects in referenced templates.
  • Explicitly state any platform limitations or differences (e.g., certificate store handling) and provide Linux/macOS alternatives where possible.
  • Reorder examples so that cross-platform tools (Azure CLI, REST API) are shown before or alongside PowerShell.
  • Provide guidance for Linux/macOS users on prerequisite setup and troubleshooting.
GitHub Create Pull Request
Virtual Machine Scale Sets Azure Disk Encryption and Azure Virtual Machine Scale Sets extension sequencing ...ine-scale-sets/disk-encryption-extension-sequencing.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 presents extension sequencing for Azure Disk Encryption but features Windows-centric examples: both JSON template samples use PowerShell scripts or Windows-specific extensions (FormatMBRDisk.ps1, VMDiagnosticsSettings for Windows VMs). Linux scenarios are only referenced via a link, with no in-page Linux shell script example or explicit Linux extension sequencing shown. Windows tools and patterns are mentioned and demonstrated before Linux equivalents.
Recommendations
  • Add an in-page example showing extension sequencing with a Linux VM, using a shell script (e.g., Bash) in CustomScriptExtension.
  • Provide a sample template where Azure Disk Encryption is sequenced after a Linux disk preparation step.
  • Include explicit mention and demonstration of Linux diagnostics extensions if relevant.
  • Ensure Linux examples are presented with equal prominence and detail as Windows examples.
  • Consider showing Linux and Windows examples side-by-side for direct comparison.
GitHub Create Pull Request
Service Fabric Set up Microsoft Entra ID for client authentication in the Azure portal ...vice-fabric-cluster-creation-setup-azure-ad-via-portal.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 is heavily focused on Windows and PowerShell for client authentication and cluster connection examples. All code samples for connecting to Service Fabric clusters use PowerShell, with no equivalent Linux/macOS CLI or SDK examples provided. Troubleshooting and workflow guidance also reference PowerShell scripts and patterns, with no mention of Linux-native tools or cross-platform alternatives. While the prerequisites and portal steps are platform-neutral, the operational and connection instructions create friction for Linux/macOS users.
Recommendations
  • Add equivalent connection examples using Azure CLI, REST API, or Service Fabric SDK for Linux/macOS.
  • Explicitly document how Linux users can connect to clusters using Microsoft Entra ID, including required tools and authentication flows.
  • Include troubleshooting steps relevant to Linux environments, such as common errors with Linux Service Fabric nodes and authentication.
  • Clarify any platform-specific limitations (e.g., portal visibility issues for Linux clusters) and provide workarounds or alternatives.
  • Where scripts are referenced (e.g., SetupApplications.ps1), provide or link to cross-platform alternatives.
GitHub Create Pull Request
Service Fabric Set up Microsoft Entra ID for client authentication ...ce-fabric/service-fabric-cluster-creation-setup-aad.md
Medium 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 Windows and PowerShell tooling, with all setup and troubleshooting examples using PowerShell scripts (.ps1) and commands. There are no Linux-native or cross-platform CLI examples, and the only automation path provided is via PowerShell. The documentation references Windows-specific tools and patterns (e.g., PowerShell, Azure Cloud Shell with PowerShell, Windows script files) and does not mention or provide parity for Linux alternatives (such as Bash scripts, Azure CLI, or REST API usage). Linux users are left to run Windows-centric scripts in Cloud Shell or manually adapt them, creating friction and barriers.
Recommendations
  • Provide Linux-native setup instructions using Azure CLI, Bash scripts, or REST API calls for all major steps (app registration, user assignment, cluster configuration).
  • Include explicit Linux/macOS examples for authentication, troubleshooting, and cluster connection, not just PowerShell.
  • Document any limitations or workarounds for Linux users up front, and link to cross-platform helper tools if available.
  • Where PowerShell scripts are referenced, offer equivalent Bash/CLI/REST alternatives or note how to run them in a cross-platform way.
  • Reorder examples so that Linux and Windows instructions are presented with equal prominence, or in parallel sections.
GitHub Create Pull Request
Virtual Machine Scale Sets Enable Azure Disk Encryption for Virtual Machine Scale Sets ...virtual-machine-scale-sets/disk-encryption-overview.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 page demonstrates a Windows bias by highlighting Windows disk encryption support (OS and data volumes) while Linux support is limited to data volumes only. Tutorial links are presented for both Azure CLI and PowerShell, but PowerShell (a Windows-centric tool) is emphasized alongside CLI. There is no explicit Linux-specific example or guidance, and the limitations for Linux (no OS disk encryption) are mentioned without alternative solutions or parity.
Recommendations
  • Provide explicit Linux-focused examples and tutorials, especially for Azure CLI (which is cross-platform).
  • Clarify limitations for Linux users and suggest alternative security approaches where OS disk encryption is not supported.
  • Ensure Linux documentation is presented with equal prominence to Windows, including example commands and workflows.
  • Add a section addressing Linux-specific considerations and future roadmap for parity.
GitHub Create Pull Request
Service Fabric Create an Azure Service Fabric cluster ...vice-fabric/service-fabric-cluster-creation-via-arm.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 exhibits several Windows-centric biases. PowerShell is consistently presented as the primary automation tool, with examples and instructions given before Azure CLI. Windows-specific patterns (e.g., file paths like 'c:\certificates', 'WindowsServer2016DatacenterwithContainers' as default OS) are used in both PowerShell and CLI examples, even when the CLI is cross-platform. While Ubuntu templates are mentioned, the majority of examples and variable names default to Windows conventions, and Linux/macOS-specific guidance (e.g., file paths, certificate handling) is missing. There is little to no discussion of Linux/macOS shell usage or platform-specific considerations, which may create friction for non-Windows users.
Recommendations
  • Provide Linux/macOS-specific examples, including shell commands (bash/zsh) and file paths (e.g., '/home/user/certificates').
  • Alternate the order of PowerShell and CLI examples, or present CLI first to emphasize cross-platform support.
  • Explicitly mention platform requirements and differences (e.g., certificate formats, file system paths, OS parameter values) for both Windows and Linux clusters.
  • Include troubleshooting or setup notes for Linux/macOS users (e.g., how to install Azure CLI, handle certificates, or run commands).
  • Use neutral variable names and examples that do not default to Windows conventions.
GitHub Create Pull Request
Service Fabric Node types and virtual machine scale sets ...les/service-fabric/service-fabric-cluster-nodetypes.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 demonstrates a moderate Windows bias. Windows-specific tools and patterns (such as RDP port changes and admin credential updates) are referenced in the 'Next steps' section, with links to PowerShell scripts and RDP-related guidance, but there are no equivalent Linux/macOS instructions or SSH examples. The JSON extension snippet uses a Windows-style data path (D:\\SvcFab) and certificate store references, with no Linux path or store examples. Linux is mentioned as a possible node type, but practical guidance and examples are Windows-centric.
Recommendations
  • Add Linux/macOS-specific examples for remote connection (e.g., SSH instructions alongside RDP).
  • Provide guidance and scripts for updating SSH port ranges and admin credentials on Linux VMs.
  • Include Linux-style data paths (e.g., /var/svcfab) in extension configuration examples.
  • Clarify certificate store handling for Linux nodes.
  • Ensure that Linux instructions are presented alongside or before Windows instructions where relevant.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Programmatic Scaling ...-fabric/service-fabric-cluster-programmatic-scaling.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a Windows bias by providing PowerShell cmdlet examples for scaling operations, referencing Windows-centric tools and libraries (e.g., PowerShell, .NET SDKs), and omitting equivalent Linux/macOS command-line or scripting examples. PowerShell is mentioned as an alternative for scripting, but no Bash, Azure CLI, or cross-platform scripting examples are provided. The order of presentation also favors Windows tools first.
Recommendations
  • Add Linux/macOS examples for scaling operations using Azure CLI and Bash scripts.
  • Include cross-platform SDK usage, such as Python or Java, for programmatic scaling.
  • Present Azure CLI commands alongside or before PowerShell examples to emphasize platform neutrality.
  • Explicitly note that PowerShell cmdlets are available on Linux/macOS (via PowerShell Core), or clarify platform requirements.
  • Reference and link to documentation for Linux/macOS users where relevant.
GitHub Create Pull Request
Service Fabric Remote connect to an Azure Service Fabric cluster node ...ce-fabric-cluster-remote-connect-to-azure-cluster-node.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 page shows a moderate Windows bias: Windows (RDP) examples and screenshots are presented first and in more detail, with Linux (SSH) mentioned briefly and only as a secondary note. The 'next steps' section links to PowerShell scripts for Windows VM management, with no Linux alternatives. Windows tools (Remote Desktop Connection) are visually emphasized, while Linux connection methods are described only in text.
Recommendations
  • Provide Linux SSH connection screenshots alongside Windows RDP examples.
  • Include step-by-step Linux/macOS instructions for connecting to cluster nodes, not just a single SSH command.
  • Add links to Linux-specific management scripts or CLI documentation in the 'next steps' section.
  • Present Windows and Linux instructions in parallel, rather than Windows-first.
  • Mention cross-platform tools (e.g., Azure CLI, SSH clients for Windows) where relevant.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager: Movement cost ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-movement-cost.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 PowerShell and C# examples for configuring Service Fabric move cost, with no mention of Linux shell equivalents or cross-platform CLI usage. PowerShell is Windows-specific, and its examples are presented before C#. There are no bash, Azure CLI, or REST API examples, which limits accessibility for Linux/macOS users.
Recommendations
  • Add equivalent bash or Azure CLI examples for service creation and updates, demonstrating how Linux/macOS users can configure move cost.
  • Explicitly mention cross-platform tools (e.g., Azure CLI, REST API) where available, and provide usage instructions.
  • Clarify which commands are Windows-only and offer alternatives for non-Windows environments.
  • Reorder examples so that cross-platform options are shown first or side-by-side with Windows-specific ones.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Auto Scaling Services and Containers ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-autoscaling.md
Medium 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 code examples for configuring auto scaling policies in Azure Service Fabric using PowerShell and C# APIs, both of which are primarily Windows-centric. There are no equivalent Linux shell or CLI examples, and PowerShell is featured prominently. The documentation also references Windows-specific activation models and resource monitoring features, with only brief mention of Linux support for containerized applications. Windows tools and patterns are presented first and exclusively, creating friction for Linux/macOS users.
Recommendations
  • Add equivalent Linux CLI (e.g., Bash, Azure CLI) examples for configuring scaling policies.
  • Clarify which features and APIs are supported on Linux and macOS, especially for non-containerized services.
  • Include instructions for using Service Fabric REST APIs or cross-platform tools where available.
  • Reorder examples to present cross-platform or Linux options alongside or before Windows/PowerShell examples.
  • Explicitly note any limitations or differences in feature support between Windows and Linux clusters.
GitHub Create Pull Request
Service Fabric Describe a cluster by using Cluster Resource Manager ...ce-fabric-cluster-resource-manager-cluster-description.md
Medium 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 demonstrates a moderate Windows bias. Configuration examples for clusters and nodes are shown using Windows-centric constructs (ClusterManifest.xml with <WindowsServer>), and PowerShell is the only command-line example provided for service creation and updates. There is no mention of Linux-specific configuration, tools, or command-line examples (such as Bash or CLI), nor is there any reference to Linux node setup or parity in standalone deployments. The documentation implicitly assumes a Windows environment for local/development clusters and omits Linux-specific guidance.
Recommendations
  • Include explicit Linux configuration examples for standalone clusters, such as using <Linux> infrastructure in ClusterManifest.xml.
  • Provide Bash or Azure CLI equivalents for all PowerShell commands shown.
  • Clarify how node properties, placement constraints, and capacities are configured for Linux nodes, including any differences in file formats or deployment steps.
  • Add notes or sections describing Linux/macOS development and deployment workflows, especially for local clusters.
  • Ensure that examples and code snippets are presented for both Windows and Linux environments, or at least indicate when an example is Windows-specific.
GitHub Create Pull Request
Service Fabric Cluster Resource Manager - Management Integration ...fabric-cluster-resource-manager-management-integration.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 detailed example of querying Service Fabric partition health using a PowerShell command, which is specific to Windows environments. There are no equivalent Linux/macOS CLI examples (such as using sfctl or REST API), and the only tool shown for interacting with Service Fabric is PowerShell. This creates friction for Linux/macOS users who cannot use PowerShell natively.
Recommendations
  • Add equivalent examples using sfctl (Service Fabric CLI) for Linux/macOS users.
  • Include REST API example for querying partition health, which is platform-agnostic.
  • When showing command-line examples, present both Windows (PowerShell) and Linux/macOS (sfctl/REST) options side-by-side.
  • Explicitly mention cross-platform tooling and provide links to installation guides for sfctl.
GitHub Create Pull Request
Service Fabric Manage Azure Service Fabric app load using metrics ...ric/service-fabric-cluster-resource-manager-metrics.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 notable Windows bias. All command-line examples use PowerShell cmdlets (e.g., New-ServiceFabricService, Update-ServiceFabricService), with no equivalent Bash, CLI, or Linux-native examples. Windows/PowerShell tooling is referenced exclusively and before any cross-platform alternatives, and there is no mention of how to perform these tasks on Linux or macOS clusters. This creates friction for non-Windows users and may prevent them from easily following the instructions.
Recommendations
  • Provide equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform.
  • Include Bash script examples or instructions for Linux environments where appropriate.
  • Explicitly state whether the described PowerShell cmdlets are available on Linux/macOS, or provide alternatives.
  • Add a section clarifying platform support and differences in tooling between Windows and Linux clusters.
  • Reference Service Fabric REST APIs for cluster management tasks, which are platform-agnostic.
GitHub Create Pull Request
Service Fabric Azure Service Fabric dynamic node tags ...tps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-node-tagging.md
Medium 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 provides command-line examples exclusively using PowerShell, which is a Windows-centric tool. There are no CLI examples for Linux/macOS users (e.g., Bash, Azure CLI, or REST API via curl). The PowerShell examples are presented before any mention of alternatives, and no Linux-specific tools or patterns are discussed. This creates friction for users managing Service Fabric clusters from non-Windows environments.
Recommendations
  • Add equivalent command-line examples using Azure CLI or Bash scripts for Linux/macOS users.
  • Include REST API usage examples with curl or httpie to demonstrate cross-platform management.
  • Clearly indicate which tools are cross-platform and provide installation/setup guidance for Linux/macOS.
  • Reorder examples or provide parallel examples for Windows and Linux/macOS to avoid Windows-first bias.
GitHub Create Pull Request
Service Fabric Manage certificates in an Azure Service Fabric cluster ...https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-security-update-certs-azure.md
Medium 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 notable Windows bias. All command-line examples for deploying and managing certificates use Azure PowerShell, with no mention of Azure CLI or Bash alternatives. Certificate import instructions reference Windows certificate stores and PowerShell cmdlets exclusively. There are no Linux/macOS-specific instructions or examples for certificate management, deployment, or cluster connection, and Windows-centric tools and patterns are presented first and exclusively.
Recommendations
  • Add equivalent Azure CLI examples for template deployment, testing, and resource group management.
  • Provide instructions for importing certificates on Linux/macOS, such as using OpenSSL or system certificate stores.
  • Include Bash or shell script examples for cluster connection and certificate management.
  • Clarify any OS-specific requirements or differences in certificate handling.
  • Present cross-platform options side-by-side or indicate which steps are OS-agnostic.
GitHub Create Pull Request
Service Fabric Service sensitivity ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-sensitivity.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 configuration examples using XML, JSON, PowerShell, and C#. However, all command-line examples use PowerShell, which is Windows-specific, and there are no equivalent CLI or scripting examples for Linux/macOS environments (e.g., Bash, Azure CLI, or REST API). PowerShell examples are presented before C# API examples, reinforcing a Windows-first approach. There is no mention of Linux-native tooling or cross-platform alternatives for managing Service Fabric services.
Recommendations
  • Add equivalent examples using Azure CLI or REST API for service sensitivity and maximum load configuration, which are cross-platform.
  • Provide Bash scripting examples for Linux users where applicable.
  • Clarify which APIs and tools are supported on Linux/macOS and provide guidance for those platforms.
  • Reorder examples to present cross-platform methods (e.g., JSON config, Azure CLI) before Windows-specific tools like PowerShell.
  • Explicitly mention Linux/macOS support and any limitations in the introduction or relevant sections.
GitHub Create Pull Request
Service Fabric Roll over an Azure Service Fabric cluster certificate ...vice-fabric/service-fabric-cluster-rollover-cert-cn.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 a PowerShell script for certificate rollover, with Windows-style file paths and no mention of Linux or cross-platform alternatives. There are no Bash, CLI, or Linux/macOS-specific instructions, and the use of PowerShell and Windows file conventions is assumed throughout.
Recommendations
  • Add equivalent Bash/Azure CLI examples for certificate upload and VMSS update.
  • Use cross-platform file path examples or note differences for Linux/macOS users.
  • Explicitly state whether the process can be completed on Linux/macOS, and provide guidance for those platforms.
  • Mention prerequisites or alternative tooling for non-Windows environments (e.g., Azure CLI, OpenSSL).
GitHub Create Pull Request
Service Fabric Secure an Azure Service Fabric cluster ...cles/service-fabric/service-fabric-cluster-security.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 exhibits a moderate Windows bias. Standalone cluster security is described only for Windows Server, with explicit references to Windows security (Kerberos, group Managed Service Accounts, Windows accounts) and Windows certificate tools. There are no equivalent instructions or references for standalone Linux clusters, nor are Linux-specific security mechanisms or certificate management tools mentioned. Windows scenarios are described in detail, while Linux is only referenced generically or in passing.
Recommendations
  • Add explicit instructions and links for securing standalone Linux clusters, including certificate setup and supported authentication mechanisms.
  • Include Linux-specific examples and references (e.g., using OpenSSL for certificate creation, Linux account management, integration with Linux-based identity providers).
  • Clarify which features and recommendations apply to Linux clusters and which are Windows-only.
  • Present Azure and Linux options before or alongside Windows-specific options to avoid 'windows_first' ordering.
  • Reference cross-platform certificate authorities and tools, not just Windows Server certificate service.
GitHub Create Pull Request
Virtual Machine Scale Sets Customer intent: As a cloud administrator, I want to deploy and customize Virtual Machine Scale Sets, so that I can efficiently manage workloads and optimize resource utilization in my existing infrastructure. ...virtual-machine-scale-sets/includes/mvss-next-steps.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 references deploying templates via the Azure Resource Manager documentation, specifically linking to a PowerShell-based deployment guide. There is no mention of Linux-native tools (such as Azure CLI or bash) for deployment, nor are Linux/macOS workflows or examples provided. The first and only deployment method referenced is PowerShell, which is primarily a Windows tool, creating a Windows-first impression and missing Linux parity.
Recommendations
  • Include links to Azure CLI and bash-based deployment guides alongside the PowerShell reference.
  • Explicitly mention cross-platform options for template deployment, such as Azure CLI, which works on Linux and macOS.
  • Add examples or references for Linux/macOS users to ensure they can follow the documentation without friction.
  • Reorder or balance examples so that Windows and Linux/macOS methods are presented equally.
GitHub Create Pull Request
Virtual Machine Scale Sets Create a Virtual Machine Scale Set with instance mix ...cles/virtual-machine-scale-sets/instance-mix-create.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 examples for Azure Portal, Azure CLI, Azure PowerShell, and REST API. While CLI and REST API are cross-platform, the PowerShell section is extensive and detailed, with multiple example scenarios and advanced usage, whereas Linux/macOS-specific shell examples (e.g., Bash) are absent. The prerequisites mention PowerShell before CLI, and PowerShell commands are given equal or greater prominence than CLI, which may create friction for Linux/macOS users unfamiliar with PowerShell.
Recommendations
  • Add Bash or shell script examples for Linux/macOS users, especially for advanced scenarios currently only covered in PowerShell.
  • In prerequisites, mention CLI before PowerShell or clarify platform applicability for each tool.
  • Balance example depth: provide equally detailed CLI (or Bash) examples as PowerShell, including advanced configuration scenarios.
  • Explicitly state platform compatibility for each tool and example.
  • Consider adding a table summarizing which tools are recommended for each OS.
GitHub Create Pull Request
Service Fabric Upgrade Linux OS for Azure Service Fabric ...es/service-fabric/service-fabric-cluster-upgrade-os.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 page provides a Linux-focused migration guide, but the step-by-step instructions and code samples are heavily reliant on Az PowerShell cmdlets and Windows-centric tooling. PowerShell examples are given for nearly every major operation, with only one section (disabling nodes) using Linux-native tools (ssh, bash, jq, sfctl). There is no parity for Linux CLI (Azure CLI) or bash scripting for the majority of steps, and PowerShell is presented as the default method for both production and non-production clusters.
Recommendations
  • Provide equivalent Azure CLI (az) commands for all PowerShell cmdlets, especially for updating vmImage, adding/removing node types, and querying cluster state.
  • Include bash script examples for common operations, such as node type management and cluster upgrades.
  • Clearly indicate which steps can be performed from Linux/macOS environments and provide guidance for cross-platform users.
  • Reorder examples so that Linux-native tools (Azure CLI, bash, sfctl) are shown before or alongside PowerShell examples.
  • Mention installation and usage of Azure CLI for Linux users, and link to relevant documentation.
GitHub Create Pull Request
Service Fabric Upgrading Azure Service Fabric clusters ...icles/service-fabric/service-fabric-cluster-upgrade.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 demonstrates a moderate Windows bias. While most upgrade concepts are platform-neutral, operational examples and references to tooling (such as PowerShell) are Windows-centric. The section on OS patching links only to Windows-specific guidance, with no mention of Linux patching or Linux Service Fabric clusters. Where command-line tooling is referenced, PowerShell is listed before Azure CLI, and no Linux/macOS shell examples are provided.
Recommendations
  • Add explicit examples and instructions for Linux-based Service Fabric clusters, especially for OS patching and upgrades.
  • When referencing command-line tools, present Azure CLI and PowerShell equally, and provide bash/zsh examples where appropriate.
  • Include links to Linux-specific documentation for cluster management and patching, or clarify platform applicability.
  • Avoid using 'Windows operating system' as the default context; specify when instructions are Windows-only and provide Linux alternatives.
GitHub Create Pull Request
Service Fabric Upgrade an Azure Service Fabric standalone cluster ...ce-fabric/service-fabric-cluster-upgrade-standalone.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 exhibits Windows bias by referencing Windows-specific upgrade guides and tools, such as the Patch Orchestration Application for Windows, and by linking only to Windows Server-specific upgrade instructions. There is no mention of Linux-specific upgrade procedures, tools, or examples, which may leave Linux users without clear guidance.
Recommendations
  • Provide equivalent upgrade guides and documentation for Linux-based Service Fabric clusters, including links to Linux-specific instructions.
  • Mention Linux patch orchestration options or clarify whether POA is available for Linux clusters.
  • Ensure examples and configuration instructions are platform-neutral or include both Windows and Linux variants.
  • Explicitly state any platform limitations or differences in upgrade and patching procedures.
GitHub Create Pull Request
Service Fabric Manage Service Fabric cluster upgrades ...fabric/service-fabric-cluster-upgrade-version-azure.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 exhibits a moderate Windows bias. The only command-line example for validating upgrade paths is provided using PowerShell, with no equivalent Linux/macOS CLI (such as Azure CLI or Bash) example. In the REST API output, Windows environments are listed first, and PowerShell is the only scripting language shown for operational tasks. There is no mention of Linux/macOS-specific tools or workflows, nor are cross-platform alternatives presented.
Recommendations
  • Add Azure CLI or Bash examples alongside PowerShell for upgrade path validation and other cluster management tasks.
  • Explicitly state that the procedures can be performed on Linux/macOS and provide relevant commands.
  • Ensure REST API output examples alternate or equally represent Windows and Linux environments.
  • Include notes or sections addressing cross-platform usage and any OS-specific caveats.
GitHub Create Pull Request
Virtual Machines Use Azure Storage Explorer to manage Azure managed disks ...l-machines/disks-use-storage-explorer-managed-disks.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation presents Azure Storage Explorer as a cross-platform GUI tool, which is available for both Windows and Linux. However, the 'Next steps' section exclusively links to Windows-specific guides, and there are no Linux/macOS-specific follow-up resources or examples. The documentation does not mention or show parity for Linux workflows after disk operations, nor does it provide Linux-specific guidance for common post-upload/download tasks.
Recommendations
  • Add 'Next steps' links for Linux workflows, such as creating or attaching disks to Linux VMs.
  • Ensure parity in follow-up documentation for both Windows and Linux users.
  • Explicitly mention that Storage Explorer is available for Linux and macOS, and provide installation instructions or links for those platforms.
  • Include examples or references for managing disks with Linux VMs after upload/download, such as mounting or formatting disks on Linux.
GitHub Create Pull Request
Service Fabric Azure Service Fabric application resource model ...ervice-fabric/service-fabric-concept-resource-model.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 documentation page demonstrates a notable Windows bias. All command-line examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) with no mention of Azure CLI equivalents, which are cross-platform. The application packaging workflow is described using Visual Studio (Windows-only) and Windows file paths, with no alternative instructions for Linux/macOS users (e.g., using dotnet CLI or other tools). The screenshots and step-by-step instructions are tailored to Windows environments, and there is no guidance for Linux/macOS users on how to perform these tasks.
Recommendations
  • Provide Azure CLI examples alongside PowerShell cmdlets for deployment and resource management.
  • Include instructions for packaging Service Fabric applications using cross-platform tools (e.g., dotnet CLI, manual zipping) instead of relying solely on Visual Studio.
  • Show file paths and commands in both Windows and Linux/macOS formats.
  • Add screenshots or descriptions for Linux/macOS workflows where relevant.
  • Explicitly state which steps are Windows-specific and offer Linux/macOS alternatives.
GitHub Create Pull Request
Virtual Machines Deploy Ephemeral OS disks ...articles/virtual-machines/ephemeral-os-disks-deploy.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation provides both CLI and PowerShell examples, but PowerShell (a Windows-centric tool) is given a dedicated section with multiple examples, while Linux-native scripting (e.g., Bash) is not mentioned. In ARM template examples, Windows image references are used by default. The ordering of sections places PowerShell after CLI, but the template example for VMs uses a Windows image, and there is no explicit Linux template example.
Recommendations
  • Add explicit Linux template examples (e.g., using Ubuntu image references) alongside the Windows ones.
  • Clarify that Azure CLI commands work cross-platform and consider providing Bash shell script examples where appropriate.
  • Balance PowerShell examples with equivalent Bash or shell script snippets for Linux/macOS users.
  • In ARM template examples, show both Windows and Linux imageReference blocks or note how to adapt for Linux.
  • Mention that PowerShell Core is cross-platform, or clarify when examples are Windows-only.
GitHub Create Pull Request
Service Fabric Common questions about Microsoft Azure Service Fabric ...cles/service-fabric/service-fabric-common-questions.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 moderate Windows bias. Several examples and recommendations reference Windows-specific tools (e.g., PowerShell, Windows Server upgrade), and antivirus exclusions list only Windows-style paths and processes. Linux equivalents, where relevant, are missing or not mentioned. Windows-centric terminology and examples are presented first or exclusively in key sections, such as authentication to Key Vault and OS upgrade guidance.
Recommendations
  • Provide Linux-specific instructions and examples alongside Windows ones, especially for OS upgrades and Service Fabric node management.
  • Include Linux paths and process names in the antivirus exclusion section, or clarify if exclusions are only relevant for Windows clusters.
  • Offer Bash or CLI examples for Key Vault authentication, not just PowerShell.
  • Explicitly mention Linux support and parity in sections discussing cluster setup, management, and application deployment.
  • Where Windows terminology is used (e.g., 'Program Files'), add Linux equivalents or clarify platform-specific differences.
GitHub Create Pull Request
Service Fabric Connect securely to an Azure Service Fabric cluster ...ice-fabric/service-fabric-connect-to-secure-cluster.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 extensive PowerShell and Windows-centric instructions and examples for connecting to Azure Service Fabric clusters, including certificate management and cluster connection. Linux/macOS equivalents are missing or only briefly mentioned, with no CLI or scripting examples for certificate installation or management on non-Windows platforms. Windows tools and patterns (PowerShell, certificate stores) are referenced first and in detail, while Linux and macOS users are left with minimal guidance.
Recommendations
  • Add explicit Linux and macOS instructions for installing client certificates (e.g., using openssl, certutil, or browser-specific steps).
  • Provide CLI-based examples for certificate management on Linux/macOS, such as using openssl or keytool.
  • Include cross-platform scripting examples for connecting to clusters, not just PowerShell.
  • Reorder sections or provide parity so that Linux/macOS instructions are presented alongside Windows, not as an afterthought.
  • Clarify browser certificate import steps for Linux, with references to common browsers (Chrome, Firefox) and their certificate management interfaces.
GitHub Create Pull Request
Virtual Machine Scale Sets Maintenance notifications for Virtual Machine Scale Sets in Azure ...tps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-maintenance-notifications.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 moderate Windows bias. PowerShell is featured first and in greater detail than Azure CLI, with explicit PowerShell cmdlets and examples provided before CLI equivalents. There are no Linux/macOS-specific shell examples (e.g., Bash), nor are there references to Linux tooling or patterns. The FAQ and 'Next steps' sections link to Windows-specific documentation for scheduled events, omitting Linux guidance. This may create friction for Linux/macOS users, though CLI commands are present as alternatives.
Recommendations
  • Provide Bash or shell script examples alongside PowerShell for maintenance operations.
  • Ensure CLI examples are given equal prominence and detail as PowerShell, possibly presenting CLI first or side-by-side.
  • Add links to Linux/macOS scheduled events documentation in 'Next steps' and FAQ sections.
  • Explicitly mention cross-platform compatibility for CLI commands and clarify any OS-specific limitations.
  • Where PowerShell is referenced, note that Azure PowerShell is available on Linux/macOS and provide installation guidance if relevant.
GitHub Create Pull Request
Service Fabric Azure Files volume driver for Service Fabric ...ic/service-fabric-containers-volume-logging-drivers.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 demonstrates a moderate Windows bias. Windows-specific prerequisites and limitations are described in detail, with Windows versions listed first and more prominently. PowerShell is the primary scripting tool shown for both Windows and Linux deployments, even though Linux users typically use Bash or other shell environments. Examples and configuration snippets often use Windows paths (e.g., c:\tmp, c:\VolumeTest\Data) and Windows-centric patterns, with Linux equivalents either shown after or omitted. Some sections, such as application manifest examples, only show Windows-style paths and do not provide Linux-specific guidance or examples.
Recommendations
  • Provide Linux-first or side-by-side examples for all commands, especially for deployment and configuration steps.
  • Include Linux-specific prerequisites and limitations with equal detail as Windows.
  • Use Linux-style paths (e.g., /tmp, /mnt/volume) in manifest and configuration examples, or show both Windows and Linux variants.
  • Offer Bash or shell script alternatives to PowerShell scripts for Linux users.
  • Clarify any differences in application manifest structure or deployment steps for Linux clusters.
  • Ensure that documentation sections do not assume Windows as the default environment.
GitHub Create Pull Request
Service Fabric Induce Chaos in Service Fabric clusters ...cles/service-fabric/service-fabric-controlled-chaos.md
Medium 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 provides detailed examples for running Chaos in Service Fabric clusters using C# and PowerShell, both of which are Windows-centric tools. PowerShell is featured heavily, with no equivalent Bash, Linux CLI, or cross-platform shell examples. Windows-specific tools and patterns (e.g., Connect-ServiceFabricCluster, Start-ServiceFabricChaos) are mentioned exclusively, and there is no guidance for Linux/macOS users on how to perform these operations. The REST API is mentioned in passing but not demonstrated, and Windows tooling is presented first and in greater detail.
Recommendations
  • Add explicit examples using the REST API, including sample curl commands and JSON payloads, to demonstrate cross-platform usage.
  • Provide equivalent instructions for Linux/macOS environments, such as using Bash scripts or Service Fabric CLI (sfctl) where available.
  • Clarify which tools are cross-platform and which are Windows-only, and direct users to platform-appropriate tooling.
  • Reorder or balance examples so that Windows and Linux/macOS approaches are presented with equal prominence.
GitHub Create Pull Request
Service Fabric Learn more about Azure Service Fabric ...icles/service-fabric/service-fabric-content-roadmap.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ powershell_heavy
Summary
The documentation page exhibits a moderate Windows bias. Windows terminology, tools, and examples (e.g., PowerShell, Windows services, Visual Studio) are mentioned first or exclusively in several sections. Linux support is acknowledged, but Linux-specific instructions, examples, and parity are often missing or relegated to secondary mentions. Some features (e.g., standalone clusters) are noted as Windows-only, and Windows-centric tools (PowerShell, Visual Studio) are referenced before or instead of Linux alternatives.
Recommendations
  • Provide Linux-specific examples and instructions alongside Windows ones, especially for cluster creation, management, and upgrades.
  • Reference Linux-native tools (e.g., Bash, systemd, Linux CLI) where appropriate, and ensure CLI examples are cross-platform.
  • Clarify feature parity and limitations for Linux users upfront, and link to Linux-specific documentation where available.
  • Avoid using Windows terminology (e.g., 'Windows service') without explaining or providing Linux equivalents.
  • Include Linux-first or at least equal examples in 'Next steps' and quickstart sections.
  • Highlight cross-platform development tools (e.g., VS Code, JetBrains Rider) alongside Visual Studio.
GitHub Create Pull Request
Service Fabric Azure Service Fabric deployment with FabricClient ...service-fabric-deploy-remove-applications-fabricclient.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. It references Visual Studio and PowerShell as the default tools for packaging and deploying Service Fabric applications, provides file paths and examples in Windows format, and omits Linux/macOS equivalents for key steps such as local development, package verification, and troubleshooting. No cross-platform CLI (e.g., sfctl) or Linux/macOS file path examples are given, and all code and troubleshooting examples assume a Windows environment.
Recommendations
  • Add explicit instructions and examples for Linux/macOS users, including file paths and environment setup.
  • Include sfctl (Service Fabric CLI) usage for deployment, package upload, and troubleshooting, as it is cross-platform.
  • Document how to verify and compress packages on Linux/macOS (e.g., using tar/gzip and sfctl commands).
  • Provide troubleshooting steps using CLI tools available on Linux/macOS, not just PowerShell.
  • Clarify which steps are Windows-specific and offer alternatives for other platforms.
  • Mention and link to Service Fabric SDK installation instructions for Linux/macOS.
GitHub Create Pull Request
Service Fabric Deploy an existing executable to Azure Service Fabric ...s/service-fabric/service-fabric-deploy-existing-app.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 Windows bias by presenting Windows/Visual Studio tooling and workflows first and in greater detail, providing PowerShell-only deployment scripts, and referencing Windows-centric tools (Visual Studio, batch files, .cmd scripts) without equivalent Linux examples or alternatives. Linux instructions are brief and lack deployment scripting or detailed guidance, making the process less clear for Linux/macOS users.
Recommendations
  • Provide Linux/macOS deployment instructions and scripts, e.g., using Azure CLI or Bash equivalents for PowerShell commands.
  • Include Linux-first or parallel examples for packaging and deploying guest executables, matching the detail given to Visual Studio workflows.
  • Offer guidance for using Linux-native tools (e.g., Yeoman, Bash scripts) for setup and initialization, and clarify how to handle .sh scripts in place of .cmd/.bat files.
  • Add screenshots or walkthroughs for Linux environments (e.g., terminal output, file locations).
  • Ensure all references to Windows-specific tooling are matched by Linux/macOS alternatives, and avoid presenting Windows-first unless justified by user base.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Diagnose Common Scenarios ...-fabric/service-fabric-diagnostics-common-scenarios.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 generally focuses on Azure-native tools and portal workflows, which are cross-platform. However, there is a notable Windows bias in the 'Monitor performance counters' section, where Windows Performance Counters are described first and in detail, with Linux mentioned only parenthetically and no Linux-specific counter examples provided. The counter examples and screenshots are all Windows-centric. There is also a lack of explicit Linux command-line or tooling examples throughout, and Windows patterns (such as .NET CLR counters) are used exclusively in examples.
Recommendations
  • Add explicit Linux performance counter examples and screenshots, showing how to configure and query Linux counters in Log Analytics.
  • Provide parity in documentation by listing Linux steps and counter formats alongside Windows, not just as a parenthetical note.
  • Include references to Linux diagnostic tools or commands (e.g., collectd, sysstat) where appropriate.
  • Ensure that examples and screenshots alternate between Windows and Linux environments, or show both.
  • Clarify any differences in agent setup or data collection for Linux clusters.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Event Aggregation with EventFlow ...service-fabric-diagnostics-event-aggregation-eventflow.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 exhibits a Windows bias by exclusively referencing Windows development tools (Visual Studio, Solution Explorer), providing setup instructions only for Visual Studio, and omitting any guidance for Linux/macOS users (e.g., command-line NuGet usage, .NET CLI, or cross-platform editors). There are no examples or instructions for Linux or macOS environments, and all screenshots and workflow descriptions assume a Windows/Visual Studio context.
Recommendations
  • Add instructions for installing EventFlow NuGet packages using the .NET CLI (dotnet add package) and/or NuGet command-line tools, which work on Linux/macOS.
  • Include guidance for editing project files and configuration (eventFlowConfig.json) using cross-platform editors (e.g., VS Code, vim, nano) instead of only referencing Visual Studio.
  • Clarify how to set the target framework and build actions in non-Visual Studio environments (e.g., editing .csproj files directly).
  • Provide verification steps that do not rely on Visual Studio (e.g., using dotnet run, checking logs/output on the console, or using cross-platform debugging tools).
  • Explicitly mention Linux/macOS compatibility and any platform-specific considerations for Service Fabric and EventFlow.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Events ...es/service-fabric/service-fabric-diagnostics-events.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 demonstrates a notable Windows bias: it references Windows Event logs, ETW, and the Windows Azure diagnostics agent as primary mechanisms for accessing Service Fabric events. There is no mention of Linux equivalents (e.g., journald, syslog, or Linux diagnostics agents), nor are Linux-specific event access patterns or examples provided. Windows tools and terminology are presented first and exclusively, leaving Linux/macOS users without clear guidance.
Recommendations
  • Add explicit instructions and examples for accessing Service Fabric events on Linux clusters, such as using journald, syslog, or Linux diagnostics agents.
  • Clarify whether the described mechanisms (ETW, Windows Event logs, Windows Azure diagnostics agent) apply to Linux clusters, and if not, provide Linux alternatives.
  • Include parity in documentation for configuring diagnostics and monitoring on Linux, referencing relevant tools and log locations.
  • Present cross-platform guidance, or at minimum, alternate sections for Windows and Linux users.
GitHub Create Pull Request
Service Fabric Set up monitoring with Azure Monitor logs ...service-fabric/service-fabric-diagnostics-oms-setup.md
Medium 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 notable Windows bias: Windows clusters and tools (such as PowerShell and WAD) are referenced first and most extensively, with step-by-step instructions and code samples provided only for Windows. The Service Fabric Analytics solution is explicitly stated as Windows-only, and all example commands use PowerShell. Linux clusters are mentioned only in passing, with users redirected to a separate article for setup, and no Linux-specific instructions, CLI examples, or syslog integration details are present.
Recommendations
  • Provide equivalent step-by-step instructions and code samples for Linux clusters, using Azure CLI and/or Bash scripts.
  • Include direct links and summaries for Linux setup within this page, rather than only redirecting to another article.
  • Clarify which features are Windows-only and offer alternative solutions for Linux users where possible.
  • Present Windows and Linux instructions in parallel sections, or clearly label which steps apply to each platform.
  • Add examples for configuring diagnostics and log integration for Linux clusters, including syslog and OMS agent setup.
GitHub Create Pull Request
Virtual Machines Azure boot diagnostics ...lob/main/articles/virtual-machines/boot-diagnostics.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 provides both Linux and Windows coverage in its scope and screenshots, but there is a subtle Windows bias. PowerShell is given its own section for enabling boot diagnostics, while the CLI section is not explicitly labeled as 'Linux' or 'cross-platform'. References to troubleshooting and configuration (such as the Serial Console link) point to Windows-specific documentation first. Windows screenshot is shown after Linux, but the overall pattern prioritizes Windows tools and workflows (PowerShell, Windows-centric links) over Linux equivalents.
Recommendations
  • Explicitly label the Azure CLI section as cross-platform and highlight its use for Linux/macOS users.
  • Provide Bash or shell script examples alongside PowerShell for enabling boot diagnostics.
  • Ensure links to troubleshooting guides include both Linux and Windows versions, or point to neutral, cross-platform resources.
  • Add a section or note on using boot diagnostics from Linux/macOS environments, including relevant tools and commands.
  • Avoid referencing Windows-specific documentation (e.g., Serial Console) before Linux equivalents.
GitHub Create Pull Request
Virtual Machines Configure VM watch ...b/main/articles/virtual-machines/configure-vm-watch.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides examples for ARM templates, Azure CLI, and PowerShell, with PowerShell (a Windows-centric tool) given its own section and example. While the CLI example is cross-platform, the PowerShell example is Windows-specific and is presented alongside CLI rather than, for example, Bash or shell scripting for Linux. The documentation refers to Visual Studio Code as an IDE, which is cross-platform, but does not mention Linux-specific editors or tools. The instructions for the <application health extension type> do clarify the difference between Windows and Linux, but the overall pattern is to present Windows/PowerShell options as primary.
Recommendations
  • Add explicit Bash or shell scripting examples for Linux users alongside PowerShell.
  • Ensure that CLI examples highlight Linux/macOS compatibility.
  • Mention Linux-native editors (e.g., Vim, Nano) as alternatives to Visual Studio Code.
  • Where PowerShell is referenced, clarify its availability on Linux/macOS or provide alternative commands.
  • Consider ordering examples so that cross-platform or Linux options are presented before or equally with Windows/PowerShell.
GitHub Create Pull Request
Service Fabric Azure Service Fabric DNS service ...n/articles/service-fabric/service-fabric-dnsservice.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 documentation displays several forms of Windows bias. Windows support is described as more complete and is mentioned first in the OS support section. PowerShell is the only CLI tool shown for service creation and DNS name assignment, with no Linux CLI (e.g., Bash, Azure CLI) equivalents. Visual Studio is referenced for editing manifests, which is a Windows-centric tool. There are no Linux-specific instructions or examples for enabling or managing DNS service, and enabling DNS service via the Azure portal is only available for Windows clusters. Linux limitations are mentioned, but Linux workflows are not documented.
Recommendations
  • Provide equivalent Linux/Bash/Azure CLI examples for service creation and DNS name assignment.
  • Include instructions for editing manifests using cross-platform editors (e.g., VS Code, nano, vim) instead of or alongside Visual Studio.
  • Document Linux-specific workflows for enabling DNS service, including ARM template modifications and any required manual steps.
  • Clarify which steps are platform-agnostic and which are Windows- or Linux-specific, and present Linux options alongside Windows ones.
  • Add explicit guidance for Linux users regarding portal limitations and alternative management strategies.
GitHub Create Pull Request
Service Fabric Azure Service Fabric disaster recovery ...les/service-fabric/service-fabric-disaster-recovery.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 for Azure Service Fabric disaster recovery demonstrates a moderate Windows bias. Windows-specific tools and APIs (e.g., PowerShell cmdlets like Repair-ServiceFabricPartition) are referenced exclusively, with no mention of Linux equivalents or cross-platform CLI usage. Standalone cluster setup is linked only for Windows Server, and troubleshooting steps (such as collecting crash dumps and restarting VMs) use terminology and tooling more familiar to Windows users. There are no Linux/macOS-specific examples or guidance, and Windows-centric patterns are presented without cross-platform alternatives.
Recommendations
  • Include equivalent Linux/macOS commands and examples (e.g., using Service Fabric CLI (sfctl) for partition repair, process management, and troubleshooting).
  • Provide links or sections for Linux/macOS cluster setup and management, not just Windows Server.
  • Clarify which instructions are cross-platform and which are Windows-only; add notes or tables for parity.
  • Reference Linux-native tools for crash dump collection, process management, and service recovery.
  • Ensure that API usage examples (such as RecoverPartitionAsync) are shown in cross-platform contexts (e.g., Python, Bash, sfctl), not just PowerShell or .NET.
GitHub Create Pull Request
Virtual Machine Scale Sets Create a scale set from a specialized image version using the Azure CLI ...chine-scale-sets/instance-specialized-image-version.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 PowerShell examples for creating a scale set from a specialized image, with extensive use of Windows-centric tools and patterns. The PowerShell section is significantly longer and more detailed than the CLI section, which is more cross-platform. The networking and load balancer setup is only shown in PowerShell, with no equivalent Bash or Linux-native scripting example. The order of examples also places PowerShell after CLI, but the depth of PowerShell coverage suggests a Windows bias. There are no explicit Linux/macOS-specific instructions or troubleshooting notes.
Recommendations
  • Add equivalent Bash shell scripts for all PowerShell examples, especially for networking and load balancer setup.
  • Explicitly mention that Azure CLI commands work on Linux/macOS and provide OS-specific notes where relevant.
  • Include troubleshooting tips for Linux/macOS users (e.g., file path formats, environment variable usage).
  • Balance example depth: ensure CLI/Bash examples are as comprehensive as PowerShell ones.
  • Reference Linux-native tools or patterns where appropriate (e.g., using SSH instead of RDP for VM access).
GitHub Create Pull Request
Service Fabric Azure Service Fabric Docker Compose Deployment Preview ...ticles/service-fabric/service-fabric-docker-compose.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page presents Windows PowerShell examples first and in greater detail, with multiple PowerShell commands listed for deployment, management, and upgrade scenarios. The CLI (sfctl) examples are provided second, but without explicit mention of Linux or macOS usage, and PowerShell is the only shell-specific example. Windows-specific tools (PowerShell cmdlets) are emphasized, and the 'Isolation' Compose directive is noted as 'only for Windows'. There are no explicit Linux/macOS shell examples or guidance for those platforms.
Recommendations
  • Add explicit Linux/macOS shell examples using sfctl, including installation and usage notes for those platforms.
  • Clarify that sfctl is cross-platform and provide links or instructions for Linux/macOS users.
  • Balance the order of examples: present CLI (sfctl) examples before or alongside PowerShell to avoid Windows-first bias.
  • Mention any platform-specific limitations or differences (e.g., 'Isolation' directive) in a dedicated section.
  • Include troubleshooting or environment setup notes for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Enable disk encryption for Linux clusters ...c/service-fabric-enable-azure-disk-encryption-linux.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 page for enabling disk encryption for Linux clusters in Azure Service Fabric shows a notable Windows bias. PowerShell commands are presented first and in greater detail, with explicit references to Windows filesystem paths (e.g., c:\certificates), and the use of PowerShell-specific cmdlets throughout. While Azure CLI examples are provided, they are often secondary and some instructions (such as certificate handling) assume Windows conventions. There is limited guidance for Linux-native tooling or shell environments, and Linux-specific patterns (e.g., bash scripting, Linux file paths) are not demonstrated.
Recommendations
  • Provide Linux-native command examples (e.g., bash scripts) alongside or before PowerShell examples.
  • Use Linux file path conventions (e.g., /home/user/certificates) in Linux-focused documentation.
  • Include instructions for certificate generation and management using Linux tools (e.g., openssl) rather than only PowerShell.
  • Clarify when commands are platform-agnostic (Azure CLI) and when they are Windows-specific (PowerShell), and recommend CLI for cross-platform use.
  • Add troubleshooting and validation steps using Linux commands (e.g., lsblk, cryptsetup status) where appropriate.
GitHub Create Pull Request
Service Fabric Package an existing executable to Azure Service Fabric ...abric/service-fabric-guest-executables-introduction.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 exhibits a Windows bias by referencing Windows-specific tools and paths (e.g., Visual Studio, C:\Program Files), mentioning Windows tooling before any cross-platform alternatives, and omitting explicit Linux/macOS instructions or examples. There is no mention of Linux packaging workflows, nor are Linux/macOS equivalents for the Service Fabric SDK installation path or packaging tools provided.
Recommendations
  • Include Linux/macOS-specific instructions for packaging and deploying guest executables to Service Fabric.
  • Provide examples using cross-platform command-line tools (e.g., Azure CLI, Service Fabric CLI) rather than focusing on Visual Studio.
  • Document the installation path and usage of Service Fabric SDK on Linux/macOS.
  • Add sample directory structures and file paths using Linux conventions (e.g., /opt/servicefabric/schemas/).
  • Ensure that all referenced samples and quickstarts are compatible with Linux/macOS and clearly indicate platform support.
GitHub Create Pull Request
Service Fabric Azure Service Fabric hosting activation and deactivation life cycle ...les/service-fabric/service-fabric-hosting-lifecycle.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 page demonstrates a moderate Windows bias. PowerShell is referenced as the primary tool for deploying and removing applications, and the only explicit tooling example for downloading a ServicePackage in advance links to a PowerShell cmdlet. No Linux or cross-platform CLI examples are provided, and Windows-centric tools are mentioned before any Linux alternatives (which are absent).
Recommendations
  • Include equivalent Linux/macOS instructions and examples, such as using Azure CLI or Service Fabric CLI (sfctl) for deployment and management tasks.
  • Provide links to documentation for Linux/macOS tooling, not just PowerShell.
  • When referencing tools or commands, present cross-platform options first or side-by-side, rather than defaulting to Windows/PowerShell.
  • Clarify which steps or commands are platform-specific and offer alternatives for other platforms.
GitHub Create Pull Request
Service Fabric Azure Service Fabric hosting model ...rticles/service-fabric/service-fabric-hosting-model.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 demonstrates a notable Windows bias by providing only PowerShell command-line examples for service creation and management, referencing Windows-centric tools and modules (e.g., Service Fabric PowerShell cmdlets), and omitting equivalent Linux/macOS CLI examples (such as Azure CLI, Bash, or cross-platform REST usage). Windows tools and patterns are mentioned exclusively or before any cross-platform alternatives, making it less accessible for users on Linux or macOS.
Recommendations
  • Add Azure CLI examples for service creation and management, which are cross-platform.
  • Include Bash or shell script equivalents for common operations.
  • Explicitly mention REST API usage with sample curl commands for Linux/macOS users.
  • Clarify which tools and commands are available on Linux/macOS, and provide links to relevant documentation.
  • Reorder examples so that cross-platform or REST approaches are presented before or alongside PowerShell.
  • Add a note about Service Fabric CLI (sfctl), which is supported on Linux/macOS.
GitHub Create Pull Request
Service Fabric Azure Service Fabric image store connection string ...fabric/service-fabric-image-store-connection-string.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 exhibits a moderate Windows bias. It references PowerShell and Visual Studio as primary tools for deployment and verification, both of which are traditionally Windows-centric. The 'Next steps' section links only to PowerShell-based deployment instructions, and there are no explicit Linux/macOS CLI or scripting examples. While .NET and REST APIs are mentioned as alternatives for retrieving the cluster manifest, these are listed after PowerShell and lack concrete Linux usage guidance.
Recommendations
  • Add explicit examples for Linux/macOS users, such as using Azure CLI, Bash scripts, or cross-platform tools for deployment and manifest retrieval.
  • Provide links to documentation pages that cover Linux/macOS workflows for Service Fabric, including application deployment and cluster management.
  • Mention and demonstrate how to use REST API calls from Bash/cURL or other cross-platform tools.
  • Include parity in 'Next steps' by linking to Linux/macOS deployment guides alongside PowerShell instructions.
GitHub Create Pull Request
Service Fabric Manage apps for multiple environments ...e-fabric-manage-multiple-environment-app-configuration.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 page demonstrates a moderate Windows bias. PowerShell and Visual Studio (Windows-centric tools) are mentioned first and in more detail, with explicit references to PowerShell cmdlets and scripts. While sfctl and Jenkins (cross-platform tools) are mentioned, their usage is less detailed and appears after Windows tools. There are no explicit Linux/macOS command-line examples or workflows, and the documentation assumes familiarity with Windows tooling.
Recommendations
  • Add explicit Linux/macOS command-line examples for creating applications, such as using sfctl and bash scripts.
  • Provide step-by-step instructions for parameter substitution using Linux tools (e.g., sed, envsubst) alongside Windows/PowerShell examples.
  • Clarify which tools and scripts are cross-platform and which are Windows-only.
  • Ensure that references to Windows tools (PowerShell, Visual Studio) are balanced with equivalent Linux/macOS workflows.
  • Consider reordering examples so that cross-platform tools (sfctl, Jenkins) are presented before or alongside Windows-specific tools.
GitHub Create Pull Request
Service Fabric Reliable services app manifest examples ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-manifest-example-reliable-services-app.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page demonstrates a moderate Windows bias. It references Windows-specific concepts such as running services as local admin accounts, using system groups like 'Administrators', and mentions ServiceFabric PowerShell modules for service creation. Examples use Windows-style batch scripts (Setup.bat) and executables (.exe), with no mention of Linux shell scripts or Linux/macOS user/group management. Windows terminology and tools are presented first and exclusively, with no Linux equivalents or cross-platform notes.
Recommendations
  • Add Linux/macOS equivalents for user/group management and service accounts, including examples using Linux system users and groups.
  • Provide examples of using shell scripts (e.g., Setup.sh) in addition to batch files for SetupEntryPoint.
  • Mention Linux-compatible tools (such as CLI commands) for managing Service Fabric applications, not just PowerShell.
  • Clarify which features and manifest elements are cross-platform and which are Windows-only, ideally with platform compatibility tables.
  • Include notes or links to documentation for deploying Service Fabric applications on Linux clusters.
GitHub Create Pull Request
Service Fabric Azure Service Fabric container application manifest examples ...abric/service-fabric-manifest-example-container-app.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 exhibits a Windows bias by referencing the Windows Server 2016 Container Sample as the basis for all manifest examples, using Windows-specific paths (e.g., 'c:\VolumeTest\Data'), and mentioning Windows tools (e.g., 'winver' command) for OS build identification. There is no mention of Linux container samples, nor are Linux-specific patterns, file paths, or OS build identification methods provided. While some notes acknowledge Linux (e.g., certificate handling), practical Linux examples and instructions are absent.
Recommendations
  • Include Linux-based container sample manifests and reference them alongside Windows samples.
  • Provide Linux-specific file path examples (e.g., '/mnt/VolumeTest/Data') in volume bindings.
  • Document how to obtain the OS build/version on Linux (e.g., 'cat /etc/os-release' or 'uname -r') for image overrides.
  • Clarify any differences in Service Fabric manifest configuration or runtime behavior between Windows and Linux clusters.
  • Ensure all features (e.g., volume drivers, certificate import) are described with both Windows and Linux usage notes and examples.
GitHub Create Pull Request
Service Fabric Configure networking modes for container services ...cles/service-fabric/service-fabric-networking-modes.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 demonstrates a moderate Windows bias. Windows-specific configuration steps (such as NSG rules for DNS, network recreation on VM reboot, and mixing networking modes) are described in detail, while Linux limitations are only briefly mentioned. Examples and instructions often focus on Windows clusters, with Linux support or differences relegated to notes or not covered in equivalent detail. There are no Linux-specific configuration examples, and some features (like mixing networking modes) are explicitly unsupported on Linux but not explained further.
Recommendations
  • Provide explicit Linux configuration examples, especially for networking setup and service manifests.
  • Clarify Linux-specific limitations and offer guidance or workarounds for Linux users.
  • Balance the presentation order: present Windows and Linux instructions side-by-side or in parallel sections.
  • Include troubleshooting tips for Linux clusters, similar to those given for Windows (e.g., handling network resets).
  • Expand on why certain features (like mixing networking modes) are unsupported on Linux and suggest alternatives.
GitHub Create Pull Request
Service Fabric Start and stop cluster nodes .../service-fabric/service-fabric-node-transition-apis.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 page demonstrates a Windows bias by referencing PowerShell cmdlets alongside managed API calls, but does not mention or provide examples for Linux or macOS equivalents. All sample code is in C# and assumes usage of the .NET FabricClient, with no mention of cross-platform CLI tools or REST APIs. PowerShell is referenced before any Linux alternatives, and there are no bash, shell, or Linux-native instructions or code samples.
Recommendations
  • Add equivalent Linux/macOS instructions, such as using Azure CLI, REST API, or Service Fabric CLI (sfctl) where applicable.
  • Provide bash or shell script examples for common node operations.
  • Explicitly mention cross-platform tools and how Linux/macOS users can perform the same tasks.
  • Reorder references so that platform-neutral or cross-platform methods are presented before Windows-specific tools.
  • Include notes about platform compatibility for all APIs and tools mentioned.
GitHub Create Pull Request
Service Fabric Overview of Azure Service Fabric ...ain/articles/service-fabric/service-fabric-overview.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 moderate Windows bias. Windows tools (Visual Studio, PowerShell) are mentioned first and in more detail than Linux equivalents. The Linux development section is shorter and less prominent, with fewer tool examples (Eclipse, Yeoman) and no direct Linux command-line or deployment examples. The quickstart link points to a .NET/Windows-focused guide, and there are no Linux/macOS-specific walkthroughs or parity in example depth.
Recommendations
  • Provide Linux/macOS examples alongside Windows ones, especially in quickstart and deployment sections.
  • Mention Linux tools (e.g., Bash, CLI, VS Code) with equal prominence and detail as Windows tools.
  • Link to Linux/macOS quickstart guides directly from the overview page.
  • Ensure that all critical workflows (development, deployment, monitoring) have step-by-step instructions for both Windows and Linux/macOS.
  • Balance the order of tool mentions (e.g., alternate Windows and Linux first in different sections).
GitHub Create Pull Request
Service Fabric Package an Azure Service Fabric app ...articles/service-fabric/service-fabric-package-apps.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. All command-line and scripting examples use Windows-specific tools (PowerShell, tree, msbuild.exe), and file paths are shown in Windows format. There are no Linux/macOS equivalents or alternative instructions for common tasks such as packaging, validating, or compressing Service Fabric applications. Visual Studio is presented as the primary IDE, with no mention of cross-platform alternatives. This creates friction for Linux/macOS users, who must infer or research equivalent commands and workflows.
Recommendations
  • Provide Linux/macOS equivalents for all command-line examples (e.g., use 'find' or 'ls' instead of 'tree', and show bash/zsh commands).
  • Document how to package and validate Service Fabric applications using cross-platform .NET CLI tools (e.g., 'dotnet build'), or clarify if msbuild is available on Linux/macOS.
  • Include instructions for compressing packages using common Linux/macOS utilities (e.g., 'zip', 'tar').
  • Mention and provide examples for using Service Fabric CLI (sfctl), which is cross-platform, for deployment and validation tasks.
  • Clarify any platform-specific limitations or requirements for Service Fabric tooling.
  • Reorder examples so that cross-platform or Linux/macOS instructions are presented alongside or before Windows-specific ones.
GitHub Create Pull Request
Service Fabric Service Fabric project creation next steps ...ric/service-fabric-project-creation-next-step-tasks.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 shows a notable Windows bias. Tutorials and walkthroughs are exclusively for Windows (e.g., 'C# Reliable Services service on Windows', 'Windows container application'), with no mention of Linux equivalents or cross-platform options. Deployment scripts are referenced with PowerShell, a Windows-centric tool, and the 'Next steps' section highlights creating a Windows cluster, omitting Linux cluster creation. There are no examples, instructions, or links for Linux/macOS users, making it unclear how to proceed on non-Windows platforms.
Recommendations
  • Add Linux/macOS equivalents for all walkthroughs and tutorials, or clearly indicate cross-platform support.
  • Include deployment instructions and scripts for Linux (e.g., Bash, CLI) alongside PowerShell.
  • Provide links to documentation for creating Linux clusters and managing Service Fabric on Linux.
  • Ensure examples and sample applications are labeled with platform compatibility.
  • Present Windows and Linux options side-by-side, or clarify platform requirements at the start of each section.
GitHub Create Pull Request
Service Fabric Change ReliableDictionaryActorStateProvider settings ...e-actors-reliabledictionarystateprovider-configuration.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 Windows bias by referencing Visual Studio (Windows-only) as the primary tool for generating configuration files, mentioning PowerShell commands without Linux equivalents, and using Windows-style file paths in examples. Linux-specific instructions are minimal and relegated to notes, with no Linux/macOS configuration workflows or command-line examples provided.
Recommendations
  • Include instructions for generating and editing settings.xml files on Linux/macOS, such as using the Service Fabric CLI (sfctl) or other cross-platform tools.
  • Provide Linux/macOS equivalents for PowerShell commands, e.g., show how to view the cluster manifest using sfctl or other Linux-native tools.
  • Add sample file paths using Linux conventions (e.g., /var/log/SharedLog.Log) alongside Windows paths.
  • Present Linux/macOS examples and workflows alongside or before Windows examples to ensure parity.
  • Clarify which steps are platform-specific and provide guidance for both environments.
GitHub Create Pull Request
Service Fabric Service communication with the ASP.NET Core ...vice-fabric-reliable-services-communication-aspnetcore.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 exhibits a moderate Windows bias, primarily through its extensive coverage of HTTP.sys, which is Windows-only, and references to Windows-specific tools and APIs (such as netsh and the Windows HTTP Server API). HTTP.sys usage is described in detail, but it is explicitly unavailable on Linux/macOS. While Kestrel, the cross-platform web server, is covered and recommended for Linux, the documentation often presents Windows-specific options (HTTP.sys) first or in greater depth, and does not provide Linux/macOS-specific troubleshooting, configuration, or parity examples. There are no PowerShell-only examples, but Windows-centric patterns and tools are mentioned without Linux equivalents.
Recommendations
  • Clearly mark Windows-only sections at the top and direct Linux/macOS users to relevant Kestrel sections.
  • Provide explicit Linux/macOS configuration and deployment examples, especially for ServiceManifest.xml, port assignment, and firewall configuration.
  • Add troubleshooting tips for Linux/macOS environments (e.g., SELinux, iptables, systemd integration).
  • Balance the order of presentation so that cross-platform (Kestrel) options are shown first or in parallel with Windows-only options.
  • Where Windows tools (e.g., netsh) are mentioned, provide Linux/macOS alternatives or note their irrelevance.
  • Include a summary table mapping features and limitations for both platforms.
GitHub Create Pull Request
Service Fabric Change FabricTransport settings ...service-fabric-reliable-actors-fabrictransportsettings.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 exhibits Windows bias by exclusively referencing Windows certificate store concepts (e.g., 'LocalMachine', 'My'), using Windows-centric certificate subject names (e.g., 'WinFabric-Test-SAN1-Alice'), and omitting concrete Linux configuration examples. Although there is a brief note about PEM certificates for Linux, all XML configuration samples and attribute values are tailored to Windows environments, with no equivalent Linux instructions or examples provided.
Recommendations
  • Add explicit Linux configuration examples, including sample XML with Linux-appropriate values for certificate store location and format.
  • Clarify how parameters like 'CertificateStoreLocation' and 'CertificateStoreName' should be set on Linux nodes (e.g., file paths, environment variables, or other mechanisms).
  • Provide Linux-specific guidance for certificate subject names and thumbprints, including how to obtain and reference them.
  • Ensure that Linux instructions are presented alongside Windows instructions, not only as a side note.
GitHub Create Pull Request
Service Fabric Service Fabric Backup and Restore ...ric/service-fabric-reliable-services-backup-restore.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 page for Service Fabric Backup and Restore demonstrates a moderate Windows bias. The only explicit tooling example for testing backup and restore uses the PowerShell cmdlet 'Start-ServiceFabricPartitionDataLoss', with no mention of Linux/macOS equivalents or cross-platform alternatives. Windows/PowerShell tools are referenced exclusively, and there are no CLI or bash examples. Additionally, the workaround for long file paths references Windows-specific kernel32 APIs. The documentation does not provide guidance for Linux/macOS users on how to perform equivalent operations, nor does it mention Service Fabric CLI (sfctl), which is cross-platform.
Recommendations
  • Include equivalent Linux/macOS instructions for testing backup and restore, such as using the Service Fabric CLI (sfctl) or REST API.
  • Provide bash or shell script examples alongside PowerShell examples.
  • Mention cross-platform tools and patterns before or alongside Windows-specific ones.
  • Clarify which APIs and tooling are available on Linux/macOS clusters and provide links to relevant documentation.
  • For file path limitations, discuss Linux/macOS filesystem behaviors and workarounds, not just Windows kernel32 APIs.
GitHub Create Pull Request
Service Fabric Configure Azure Service Fabric Reliable Services ...bric/service-fabric-reliable-services-configuration.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 several signs of Windows bias. Windows-centric tools and workflows (e.g., PowerShell, Visual Studio) are mentioned first or exclusively, with no Linux equivalents or examples provided. Configuration file paths and security certificate instructions are primarily Windows-oriented, and Linux-specific instructions are minimal or relegated to notes. There are no Linux/macOS command-line examples, nor guidance for editing cluster manifests or settings on non-Windows platforms.
Recommendations
  • Provide Linux/macOS equivalents for all command-line instructions (e.g., show how to view the cluster manifest using Service Fabric CLI or REST API, not just PowerShell).
  • Include examples of editing configuration files and paths using Linux conventions (e.g., use /var/log/servicefabric/SharedLog.Log instead of f:\SharedLog.Log).
  • Offer guidance for developing and debugging Service Fabric applications on Linux/macOS, including alternatives to Visual Studio (e.g., VS Code, CLI tools).
  • Expand certificate configuration instructions for Linux, including command-line steps for PEM certificate management and integration.
  • Reorder examples so that Windows and Linux instructions are presented with equal prominence, or in parallel sections.
GitHub Create Pull Request
Service Fabric Secure service remoting communications with C# ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-reliable-services-secure-communication.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 exclusively on C# service remoting security in Azure Service Fabric, with all code examples and configuration patterns tailored to Windows environments. Windows certificate store concepts (StoreLocation, StoreName) are used throughout, and Linux-specific instructions are limited to a brief note about certificate file placement, with no Linux-oriented code or configuration examples. The page does not provide parity for Linux users running C# services, omitting details on how to configure certificates or settings for Linux clusters.
Recommendations
  • Add explicit C# code and configuration examples for Linux clusters, showing how to reference PEM-formatted certificates and any differences in API usage or configuration.
  • Document the process for installing and referencing certificates on Linux nodes, including directory structure, file permissions, and mapping to Service Fabric APIs.
  • Clarify which settings (e.g., StoreLocation, StoreName) are ignored or replaced on Linux, and provide Linux-specific equivalents or guidance.
  • Present Windows and Linux instructions/examples side-by-side or in parallel sections, rather than focusing solely on Windows.
  • Include troubleshooting tips for common Linux certificate issues in Service Fabric.
GitHub Create Pull Request
Service Fabric Add custom Service Fabric health reports ...rticles/service-fabric/service-fabric-report-health.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 page demonstrates a notable Windows bias. PowerShell is heavily featured for command-line examples, with no mention of Linux/macOS equivalents (such as Bash, CLI, or cross-platform tools). Windows-specific tools and patterns (PowerShell cmdlets, Windows-style paths, and examples) are presented before REST or API options. There is no guidance for Linux users on how to perform health reporting tasks from non-Windows environments, nor are alternative CLI examples (e.g., Azure CLI, Bash) provided.
Recommendations
  • Add explicit examples for Linux/macOS environments, such as using Bash, Azure CLI, or cross-platform .NET Core tools.
  • Clarify whether PowerShell examples work on PowerShell Core (pwsh) on Linux/macOS, and provide installation/setup instructions if so.
  • Include REST API examples with curl or other cross-platform tools, and show how to authenticate and send health reports from Linux.
  • Reorder examples so that cross-platform or REST approaches are presented before or alongside Windows/PowerShell methods.
  • Mention any limitations or requirements for Linux users (e.g., .NET Core support, Service Fabric CLI availability) and provide links to relevant resources.
GitHub Create Pull Request
Container Instances Get prediction results for standby pools for Azure Container Instances (Preview) ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/container-instances/container-instances-standby-pool-prediction-results.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 Azure CLI and PowerShell examples for retrieving prediction results, but PowerShell is featured as a primary tab, and no Linux/macOS-specific shell examples (such as Bash or curl) are provided. The PowerShell example is detailed, reinforcing a Windows-centric approach. REST API usage is shown, but only as a generic HTTP request, without Linux-oriented command-line examples (e.g., curl or wget).
Recommendations
  • Add Linux/macOS shell examples using curl or wget for REST API calls.
  • Include Bash scripts or command-line usage for Azure CLI, demonstrating usage in typical Linux environments.
  • Ensure that CLI examples are shown before or alongside PowerShell, and clarify that Azure CLI is cross-platform.
  • Explicitly mention Linux/macOS compatibility and usage patterns where relevant.
GitHub Create Pull Request
Service Fabric Custom Image .../articles/service-fabric/how-to-deploy-custom-image.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 Windows bias by consistently referencing 'custom windows images' first, providing only PowerShell examples for role assignment, and mentioning Windows/PowerShell tools and patterns before their Linux equivalents. There are no Linux-specific command examples (e.g., Azure CLI or Bash), and the ARM template examples do not clarify Linux image usage. While links to Linux documentation exist, actionable steps and examples are Windows-centric.
Recommendations
  • Provide Azure CLI and Bash examples for role assignment and other operations alongside PowerShell.
  • Explicitly mention and show how to use Linux custom images in ARM templates, including image references and OS configuration differences.
  • Balance the narrative by referring to 'Windows and Linux images' together, rather than defaulting to Windows first.
  • Include Linux-specific troubleshooting tips and considerations for Service Fabric clusters.
  • Ensure that all referenced documentation links (e.g., finding marketplace images) are paired: one for Windows, one for Linux.
GitHub Create Pull Request
Service Fabric Set up IP tags on a Service Fabric managed cluster ...icles/service-fabric/how-to-managed-cluster-ip-tags.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 references provisioning IP tags using a PowerShell-specific Azure module and links to a PowerShell example, without mentioning or providing equivalent instructions for Linux/macOS users (e.g., Azure CLI, ARM template, or REST API). This creates friction for non-Windows users who may not use PowerShell.
Recommendations
  • Include instructions and examples for provisioning IP tags using Azure CLI, which is cross-platform.
  • Reference ARM template and REST API methods for provisioning IP tags, not just PowerShell.
  • Add explicit notes or sections for Linux/macOS users to ensure parity.
  • Order examples so that cross-platform tools (CLI, ARM) are presented before or alongside Windows-specific tools.
GitHub Create Pull Request
Service Fabric Azure Service Fabric container image management .../articles/service-fabric/container-image-management.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 displays a Windows bias by referencing Windows-specific container images (microsoft/windowsservercore, microsoft/nanoserver) as defaults in the 'ContainerImagesToSkip' setting, and mentioning them before any Linux equivalents. There are no Linux container images (e.g., Ubuntu, Alpine) referenced as examples or defaults, nor is there guidance for Linux/macOS users. The examples and explanations focus on Windows images, which may lead Linux users to feel unsupported or unclear about best practices for their platforms.
Recommendations
  • Include Linux container images (e.g., ubuntu, alpine) in examples and defaults for 'ContainerImagesToSkip'.
  • Explicitly mention that the settings and cleanup apply equally to Linux-based images and provide examples.
  • Add a note clarifying platform support and any differences in behavior between Windows and Linux containers.
  • Provide parity in documentation by listing both Windows and Linux images in tables and examples.
GitHub Create Pull Request
Service Fabric Create a Service Fabric managed cluster (SFMC) with Ephemeral OS disks for node types ...ce-fabric/how-to-managed-cluster-ephemeral-os-disks.md
Medium 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 ARM template deployment and referencing RDP (a Windows-specific remote access protocol) for VM administration. There are no CLI or Bash examples for Linux/macOS users, nor are cross-platform tools like Azure CLI mentioned. The use of Windows tools and terminology is prevalent, and Linux alternatives are missing.
Recommendations
  • Add Azure CLI examples for ARM template deployment, showing equivalent steps for Linux/macOS users.
  • Include instructions for SSH access to VMs, alongside RDP, to support Linux/macOS administration.
  • Present cross-platform deployment methods first or in parallel, rather than focusing on PowerShell.
  • Explicitly mention that all steps can be performed from Linux/macOS and provide links to relevant cross-platform documentation.
GitHub Create Pull Request
Service Fabric Deploy a Service Fabric managed cluster across Availability Zones ...ce-fabric/how-to-managed-cluster-availability-zones.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 provides command-line examples and instructions using PowerShell and the Az PowerShell module, with no mention of Linux/macOS equivalents (such as Azure CLI or Bash). Steps for cluster migration and node management reference PowerShell commands and tools exclusively, creating friction for users on non-Windows platforms.
Recommendations
  • Include Azure CLI (az) command examples alongside PowerShell, as Azure CLI is cross-platform and works on Linux/macOS.
  • Explicitly mention that all API calls can be performed using curl or other HTTP clients on any OS, and provide sample curl commands.
  • Clarify which steps require PowerShell and offer alternatives for Linux/macOS users.
  • Add notes or links to documentation for performing equivalent operations on Linux/macOS.
GitHub Create Pull Request
Service Fabric Service Fabric Explorer blocking operations ...ged-cluster-service-fabric-explorer-blocking-operation.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 page primarily references PowerShell cmdlets (e.g., Remove-AzResource, AzSF PowerShell cmdlet) for managing Service Fabric resources, which are traditionally Windows-centric tools. There is no mention of Linux/macOS equivalents, nor are CLI examples (such as Azure CLI) provided alongside PowerShell. This creates friction for users on non-Windows platforms, as PowerShell is less commonly used or installed by default.
Recommendations
  • Include Azure CLI examples (e.g., az resource delete, az servicefabric managed-cluster application create) alongside PowerShell cmdlets for all operations.
  • Explicitly note platform compatibility for each tool and provide installation guidance for Linux/macOS users if PowerShell is required.
  • Where possible, recommend ARM template usage, which is platform-agnostic, and provide sample templates.
  • Add a section clarifying cross-platform management options and best practices.
GitHub Create Pull Request
Service Fabric Manage Azure Service Fabric application secrets ...fabric/service-fabric-application-secret-management.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 both Windows and Linux links for certificate setup, but scripting and automation examples (PowerShell and C#) are Windows-centric. There are no Linux CLI (e.g., Bash, sfctl) examples for creating application instances or overriding parameters, and PowerShell is presented as the default scripting method. Windows tools and patterns are mentioned first and exclusively in critical automation sections.
Recommendations
  • Add equivalent Linux command-line examples using sfctl or Bash scripts for creating application instances and overriding parameters.
  • Explicitly mention cross-platform tools and workflows where possible, not just PowerShell and C#.
  • Present Windows and Linux options side-by-side in automation sections, or clarify platform applicability for each example.
  • Reference Linux documentation links before or alongside Windows links to avoid 'windows_first' ordering.
GitHub Create Pull Request
Service Fabric Monitoring data reference for Azure Service Fabric ...les/service-fabric/monitor-service-fabric-reference.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 demonstrates a notable Windows bias. Performance counter examples and recommendations are exclusively based on Windows-specific counters and tools (e.g., Performance Monitor, Windows performance counters). There is no mention of Linux equivalents, nor are Linux monitoring tools or patterns referenced. The instructions and references assume a Windows environment, leaving Linux users without guidance for collecting similar metrics.
Recommendations
  • Add equivalent Linux performance metrics and counters (e.g., using /proc, sysstat, or collectd).
  • Include examples of how to collect metrics on Linux nodes, such as using common Linux monitoring tools (top, sar, vmstat, etc.).
  • Reference Linux-compatible agents and their configuration for Service Fabric monitoring.
  • Clarify which counters are Windows-only and provide Linux alternatives where possible.
  • Ensure documentation sections explicitly address both Windows and Linux environments.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Central Secret Service ...vice-fabric/service-fabric-application-secret-store.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 REST API usage examples are provided exclusively in PowerShell, with no equivalent Linux/macOS shell (e.g., curl, bash) examples. Windows-specific tools and patterns (such as PowerShell and Windows file paths) are mentioned first and/or exclusively, while Linux equivalents are either absent or relegated to comments. This creates friction for Linux/macOS users attempting to follow the guidance.
Recommendations
  • Add Linux/macOS shell examples (e.g., curl commands) alongside PowerShell for all REST API operations.
  • Present both Windows and Linux file path mount examples equally, not as commented-out alternatives.
  • Explicitly mention cross-platform certificate installation and management steps, including Linux-specific guidance.
  • Ensure all configuration and usage instructions are platform-neutral or provide parallel instructions for both Windows and Linux/macOS.
  • Avoid using Windows tools (e.g., PowerShell) exclusively; offer alternatives or note platform requirements.
GitHub Create Pull Request
Service Fabric Monitor Azure Service Fabric ...main/articles/service-fabric/monitor-service-fabric.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ powershell_heavy
Summary
The documentation page exhibits a moderate Windows bias. Windows-specific tools (EventStore APIs, Diagnostics Agent, Event Viewer, ETW providers) are mentioned before or in more detail than their Linux equivalents. Several tutorials and examples focus on .NET/Windows, with Linux alternatives referenced but not equally explained or linked. Linux monitoring approaches (e.g., Syslog, LTTng) are mentioned but lack step-by-step guidance or parity in example depth. PowerShell and Visual Studio are referenced without cross-platform alternatives.
Recommendations
  • Provide equivalent Linux-focused tutorials and examples, especially for cluster monitoring and application instrumentation.
  • Ensure all tool references (e.g., EventStore, Diagnostics Agent) include Linux-specific setup and usage instructions, not just links.
  • Add explicit Linux command-line examples (e.g., Bash, CLI) alongside PowerShell where automation is discussed.
  • Balance .NET/Windows application monitoring examples with those for Java, Node.js, or other Linux-friendly stacks.
  • Clarify which features/tools are Windows-only and suggest Linux alternatives or workarounds.
  • Include links to Linux documentation pages at parity with Windows references.
GitHub Create Pull Request
Service Fabric Architecture of Azure Service Fabric ...articles/service-fabric/service-fabric-architecture.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 page exhibits Windows bias primarily in the Management subsystem section, where PowerShell cmdlets are mentioned as the main tooling for lifecycle management, with no mention of Linux/macOS equivalents (such as Azure CLI or REST APIs). Additionally, Windows security is referenced as an option for securing transport, but Linux alternatives are not discussed. No Linux-specific examples or tools are provided throughout the page.
Recommendations
  • Explicitly mention and provide examples for Linux/macOS management tools, such as Azure CLI and REST APIs, alongside PowerShell.
  • Clarify how transport security is handled on Linux clusters (e.g., X509 certificates) and provide guidance for non-Windows environments.
  • Ensure that any tooling or command-line references are cross-platform, or provide platform-specific instructions where necessary.
  • Add a section or note on Linux/macOS support and parity for Service Fabric management and security operations.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager - Placement Policies ...ce-manager-advanced-placement-rules-placement-policies.md
Medium 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 provides code samples for configuring Service Fabric placement policies using C# and PowerShell only. PowerShell is a Windows-centric tool, and there are no equivalent examples for Linux/macOS users (e.g., Azure CLI, REST API, or bash). The configuration steps and automation patterns are presented exclusively with Windows tooling, which may create friction for users operating Service Fabric clusters on Linux or in cross-platform environments.
Recommendations
  • Add equivalent examples using Azure CLI and/or REST API for each placement policy configuration.
  • Explicitly mention cross-platform management options and link to relevant documentation for Linux/macOS users.
  • Reorder examples so that cross-platform tools (Azure CLI, REST API) are shown before or alongside PowerShell.
  • Clarify any platform-specific limitations or differences in Service Fabric management between Windows and Linux.
GitHub Create Pull Request
Service Fabric Update a cluster to use certificate common name ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-change-cert-thumbprint-to-cn.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 deployment instructions and examples, which are specific to Windows environments. There are no equivalent examples or guidance for Linux/macOS users, such as using Azure CLI or Bash. The use of Windows file paths in examples further reinforces the Windows-first approach.
Recommendations
  • Add Azure CLI examples for template deployment, suitable for Linux/macOS users.
  • Include Bash shell commands alongside PowerShell, especially for file operations and deployments.
  • Use platform-neutral file paths or clarify path conventions for different operating systems.
  • Explicitly mention cross-platform tooling and provide links to relevant documentation for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Azure Service Fabric security best practices ...rvice-fabric/service-fabric-best-practices-security.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 shows a moderate Windows bias. Windows-specific tools (PowerShell, Windows Defender, DSC) are mentioned and demonstrated before or instead of Linux equivalents. Windows examples (PowerShell commands) are presented first in encryption sections, and Windows-specific security baselines and antivirus are covered in detail, while Linux alternatives are not discussed or are referenced only briefly. Some sections (e.g., Windows Defender, DSC) are Windows-only, with Linux users left to seek their own solutions.
Recommendations
  • Present Linux and Windows examples side-by-side, or alternate which platform is shown first.
  • Include Linux equivalents for Windows-specific tools (e.g., mention Linux security baselines, antivirus solutions, and configuration management tools like Ansible or Chef).
  • Add explicit guidance for Linux users where only Windows instructions are given, especially for security baselines and antivirus.
  • Clarify when a feature or tool is Windows-only and provide recommended Linux alternatives.
  • Ensure all code samples are available for both platforms where possible.
GitHub Create Pull Request
Service Fabric Change Azure Service Fabric cluster settings ...rvice-fabric/service-fabric-cluster-fabric-settings.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 exhibits a moderate Windows bias. Many configuration parameters and descriptions reference Windows-specific concepts, tools, or defaults (e.g., certificate store names like "MY", store locations like "LocalMachine", NTLM authentication, and references to Windows Defender Firewall). Some settings explicitly mention Windows-only applicability, and links or references to further documentation often point to Windows Server guides before Linux equivalents. Linux-specific details are present but less prominent, and Linux alternatives or differences are not always explained in parallel with Windows options.
Recommendations
  • For every Windows-specific parameter (e.g., certificate store names, NTLM authentication, firewall settings), add explicit Linux/macOS equivalents or clarify their applicability.
  • Where defaults differ between Windows and Linux (e.g., ContainerNetworkSetup), highlight both defaults and explain the rationale.
  • Provide links to Linux/macOS documentation alongside or before Windows Server documentation, especially in 'Next steps' and reference sections.
  • Add examples or guidance for Linux/macOS users where only Windows tools or patterns are mentioned (e.g., certificate management, firewall configuration).
  • Review terminology to ensure cross-platform neutrality (e.g., avoid 'Windows Fabric Replicator' when describing platform-agnostic features).
GitHub Create Pull Request
Service Fabric Scale a Service Fabric cluster in or out .../service-fabric/service-fabric-cluster-scale-in-out.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 page exhibits a moderate Windows bias. Most code examples and operational instructions are given using PowerShell cmdlets, which are primarily Windows-centric. Windows-specific tools (e.g., ServiceFabric PowerShell module) are referenced and used extensively, with Linux/macOS equivalents (such as sfctl and Azure CLI) provided but often after the PowerShell examples. Some advanced operations (like node removal) are described in detail for PowerShell, with sfctl commands present but less emphasized. There are no explicit Linux/macOS-only examples or instructions, and the documentation assumes familiarity with Windows tooling.
Recommendations
  • Present Azure CLI and sfctl examples before or alongside PowerShell examples, not after.
  • Expand and clarify instructions for Linux/macOS users, including environment setup and prerequisites.
  • Ensure all operations described with PowerShell have equivalent, fully-detailed sfctl or Azure CLI workflows.
  • Explicitly mention platform compatibility for each tool and example.
  • Add troubleshooting or notes for common Linux/macOS issues (e.g., permissions, path differences).
GitHub Create Pull Request
Service Fabric Create a Service Fabric cluster in the Azure portal ...e-fabric/service-fabric-cluster-creation-via-portal.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 creating a Service Fabric cluster via the Azure portal, which supports both Linux and Windows clusters. However, the examples and instructions are written in a way that assumes Windows usage, such as requiring a username and password for Remote Desktop (RDP) access to VMs, which is a Windows-centric pattern. There are no explicit Linux-specific instructions, nor is SSH mentioned as a remote access method. Additionally, PowerShell is referenced for management operations, but there is no mention of Bash, Azure CLI, or Linux-native tools. This creates friction for Linux users, who may need to adapt Windows-centric steps to their environment.
Recommendations
  • Include explicit instructions for Linux clusters, such as SSH key setup for VM access instead of RDP credentials.
  • Provide examples for both Windows and Linux management operations, referencing Azure CLI and Bash where appropriate.
  • Clarify which steps differ for Linux clusters, especially around remote access and certificate handling.
  • Add notes or sections highlighting Linux-specific considerations and parity with Windows features.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager - Application Groups ...ice-fabric-cluster-resource-manager-application-groups.md
Medium 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 consistently provides PowerShell examples for all command-line operations, with no mention of Linux/macOS equivalents (such as Bash, Azure CLI, or REST API). PowerShell is a Windows-centric tool, and its use is presented first and exclusively for scripting and management tasks. There is no guidance for users on Linux or macOS platforms, nor are alternative tools or commands referenced.
Recommendations
  • Add equivalent examples using Azure CLI, which is cross-platform, for all PowerShell commands.
  • Include REST API sample calls for management operations where applicable.
  • Explicitly mention Linux/macOS support and provide instructions for those platforms.
  • Reorder examples so that cross-platform tools (Azure CLI, REST API) are presented before or alongside PowerShell.
  • Clarify any platform-specific limitations or requirements for Service Fabric management.
GitHub Create Pull Request
Service Fabric Scalability of Service Fabric services .../service-fabric/service-fabric-concepts-scalability.md
Medium 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 notable Windows bias in its examples and tooling references. PowerShell commands are provided for scaling operations, but there are no equivalent Linux CLI or bash examples. Windows-specific tools (PowerShell cmdlets) are referenced as the primary administrative mechanism, and no Linux-native alternatives (such as sfctl or bash scripts) are mentioned. The order of presentation also places Windows tooling before any mention of Linux, and Linux users are left to infer how to perform these tasks without direct guidance.
Recommendations
  • Add equivalent Linux examples using sfctl, bash, or REST API for all PowerShell commands.
  • Explicitly mention Linux administrative tools (e.g., sfctl) alongside PowerShell in all relevant sections.
  • Provide guidance or links for Linux/macOS users on how to perform scaling operations.
  • Ensure that examples alternate or present both Windows and Linux approaches side-by-side.
  • Clarify platform-specific limitations or differences in tooling, and direct users to platform-appropriate documentation.
GitHub Create Pull Request
Service Fabric Deploy a cluster across Availability Zones ...vice-fabric/service-fabric-cross-availability-zones.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 page exhibits a notable Windows bias. All operational examples for cluster migration and management use PowerShell commands, with no equivalent Bash, Azure CLI, or Linux-native instructions. The sample template for the recommended deployment topology is explicitly for Windows, and Windows file paths (e.g., 'D:\\SvcFab') are used in configuration snippets. Linux or macOS users are not provided with direct guidance or parity in tooling, making it harder for them to follow the instructions.
Recommendations
  • Provide Azure CLI and Bash equivalents for all PowerShell commands, especially for cluster deployment, node disabling, and resource removal.
  • Include sample templates and configuration snippets for Linux clusters (e.g., Ubuntu), and reference them equally alongside Windows examples.
  • Use platform-neutral file paths or clarify how to set them for both Windows and Linux environments.
  • Explicitly mention cross-platform support and provide links to Linux/macOS documentation where relevant.
  • Ensure that operational steps (such as migration) are documented for both Windows and Linux users, not just Windows/PowerShell.
GitHub Create Pull Request
Service Fabric Health monitoring in Service Fabric ...s/service-fabric/service-fabric-health-introduction.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 page provides a detailed conceptual overview of Service Fabric health monitoring, but the only concrete example of reporting and evaluating health uses Windows PowerShell cmdlets. There are no equivalent examples for Linux/macOS users (e.g., using REST API, CLI, or SDKs). The tools and patterns referenced (PowerShell, cluster manifest XML) are Windows-centric, and Linux parity is not demonstrated.
Recommendations
  • Add equivalent examples for Linux/macOS environments, such as using the Service Fabric CLI (sfctl), REST API, or SDKs (Python, .NET Core).
  • Explicitly mention cross-platform tools and workflows where PowerShell is referenced.
  • Provide sample commands for reporting and querying health from Linux shells (bash) and macOS.
  • Clarify which tools are available on which platforms, and link to installation/setup guides for Linux/macOS users.
  • Where XML manifests are referenced, note any platform-specific differences in deployment or configuration.
GitHub Create Pull Request
Azure Impact Reporting Azure Impact Reporting: Connectors Troubleshooting Guide ...e-impact-reporting/connectors-troubleshooting-guide.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides troubleshooting steps for both Bash and PowerShell users, but PowerShell (Windows) examples and tools are consistently presented alongside or immediately after Bash, sometimes with additional detail for PowerShell. In some sections, PowerShell-specific troubleshooting (e.g., updating modules, error preferences) is included, while equivalent Linux/macOS guidance is missing. The order of presentation is generally Bash first, but Windows/PowerShell content is given equal or slightly more prominence, and some PowerShell-specific issues are addressed that have no Bash equivalent.
Recommendations
  • Add Linux/macOS-specific troubleshooting steps where only PowerShell/Windows guidance is given (e.g., Bash error handling, module updates).
  • Ensure parity in detail between Bash and PowerShell sections, avoiding extra troubleshooting for PowerShell unless Bash/Linux equivalents are also covered.
  • Where PowerShell-specific advice is given (like $ErrorActionPreference), include Bash/Linux error handling tips (e.g., set -e, error traps).
  • Explicitly mention support for macOS where relevant, and clarify any platform-specific limitations.
  • Consider grouping Bash and PowerShell guidance separately to reduce cognitive friction for non-Windows users.
GitHub Create Pull Request
Container Instances Big containers on Azure container instances ...ob/main/articles/container-instances/big-containers.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 page lists PowerShell as a primary deployment method and mentions it before Linux-friendly tools like Azure CLI and ARM templates. There is no mention of Linux-specific shell examples, nor is there explicit parity in example commands or tooling for Linux/macOS users. The focus on PowerShell and the ordering of tools may create friction for non-Windows users.
Recommendations
  • Provide explicit Linux/macOS shell examples (e.g., Bash) alongside PowerShell.
  • List Azure CLI before PowerShell, as it is cross-platform and preferred by many Linux/macOS users.
  • Clarify that all deployment methods (Azure CLI, ARM templates, PowerShell, Portal) are equally supported on all platforms.
  • Include example commands for both Azure CLI and PowerShell for common tasks.
  • Add a note or section on platform compatibility for each tool.
GitHub Create Pull Request
Service Fabric Networking patterns for Azure Service Fabric ...s/service-fabric/service-fabric-patterns-networking.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 notable Windows bias. All command-line deployment examples use PowerShell, with no mention of Azure CLI, Bash, or Linux/macOS workflows. Even basic connectivity checks use Windows-specific tools (RDP, Windows ping syntax), and there are no Linux/macOS equivalents or guidance. This creates friction for non-Windows users attempting to follow the steps.
Recommendations
  • Provide Azure CLI and Bash examples alongside PowerShell for all deployment commands.
  • Include Linux/macOS connectivity instructions (e.g., using SSH instead of RDP, Linux ping syntax).
  • Explicitly state cross-platform compatibility for templates and tools.
  • Add notes or sections for Linux/macOS users, highlighting any differences or requirements.
  • Where Windows tools are referenced (e.g., RDP), mention alternatives (e.g., SSH) and provide relevant instructions.
GitHub Create Pull Request
Service Fabric Add and remove node types of a Service Fabric managed cluster ...abric/tutorial-managed-cluster-add-remove-node-type.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 is heavily biased towards Windows, with all examples and instructions using Azure PowerShell. There are no CLI or Linux/macOS-specific examples, and PowerShell is listed as a prerequisite, which is primarily a Windows tool. This creates friction for Linux/macOS users who may prefer or require Azure CLI or bash-based workflows.
Recommendations
  • Include equivalent Azure CLI examples for all operations (adding/removing node types).
  • List both PowerShell and CLI as prerequisites, with installation links for Linux/macOS.
  • Explicitly mention cross-platform options and provide bash script examples where relevant.
  • Clarify which steps are platform-agnostic and which require Windows-specific tools.
GitHub Create Pull Request
Virtual Machine Scale Sets Update a Virtual Machine Scale Set with instance mix ...cles/virtual-machine-scale-sets/instance-mix-update.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides examples for Azure CLI, PowerShell, and REST API. However, PowerShell (a Windows-centric tool) is given its own dedicated section with detailed, multi-step examples, while no equivalent is provided for Bash or shell scripting on Linux/macOS. In each major section, PowerShell is presented before REST API, and the CLI examples are generic but do not mention Linux-specific nuances. There are no explicit Linux/macOS shell scripting examples, nor is there guidance for Linux users who may prefer Bash or other native tools.
Recommendations
  • Add Bash shell scripting examples for Linux/macOS users, especially for multi-step operations currently shown only in PowerShell.
  • Clarify that Azure CLI commands work equally on Linux, macOS, and Windows, and note any OS-specific considerations.
  • Consider reordering sections so that cross-platform tools (CLI, REST API) are presented before Windows-specific tools (PowerShell).
  • Explicitly mention Linux/macOS compatibility and provide troubleshooting tips for those platforms.
GitHub Create Pull Request
Service Fabric Deploy a Service Fabric managed cluster ...cles/service-fabric/tutorial-managed-cluster-deploy.md
Medium 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 Windows-specific tools (Service Fabric SDK and PowerShell module, Azure PowerShell), with no mention of Linux/macOS equivalents or cross-platform CLI alternatives. All examples and instructions assume a Windows environment, creating friction for users on Linux or macOS.
Recommendations
  • Provide Azure CLI examples alongside PowerShell commands, as Azure CLI is cross-platform.
  • Clarify whether the Service Fabric SDK and management tools are available for Linux/macOS, and provide installation instructions for those platforms.
  • Explicitly mention platform compatibility and offer guidance for Linux/macOS users.
  • Reorder or parallelize examples so that Windows and Linux/macOS options are presented equally.
GitHub Create Pull Request
Service Fabric Scale out a Service Fabric managed cluster ...icles/service-fabric/tutorial-managed-cluster-scale.md
Medium 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 Azure PowerShell for scaling out a Service Fabric managed cluster, providing only a PowerShell example and listing Azure PowerShell as a prerequisite. There are no CLI, Bash, or Linux/macOS-specific instructions or examples, and Windows tooling is mentioned first and exclusively.
Recommendations
  • Add equivalent Azure CLI examples for scaling out node types, which work cross-platform (Linux, macOS, Windows).
  • List both Azure PowerShell and Azure CLI as supported tools in prerequisites.
  • Explicitly mention that the operation can be performed from Linux/macOS using Azure CLI.
  • Consider providing Bash script examples alongside PowerShell.
  • Clarify any platform-specific limitations, if any exist.
GitHub Create Pull Request
Virtual Machine Scale Sets Proximity placement groups for Virtual Machine Scale Sets ...rtual-machine-scale-sets/proximity-placement-groups.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 page is heavily focused on Windows and PowerShell, with all code examples and step-by-step instructions using Azure PowerShell cmdlets. Linux/Azure CLI equivalents are only mentioned in passing, and no CLI/bash examples are provided. The page title and description specifically reference Windows, and Windows tools (PowerShell) are used exclusively for all practical guidance, leaving Linux/macOS users with minimal actionable information.
Recommendations
  • Add equivalent Azure CLI/bash examples for all PowerShell code snippets, especially for creating, listing, and managing proximity placement groups and VM scale sets.
  • Update the title and description to remove Windows-specific language, making it clear the guidance applies to both Windows and Linux VM Scale Sets.
  • Present CLI and PowerShell examples side-by-side or in separate tabs, ensuring Linux/macOS users have clear, actionable instructions.
  • Reference both Linux and Windows documentation equally in best practices and next steps sections.
GitHub Create Pull Request
Service Fabric Replica soft delete for enhanced data protection in Service Fabric ...s/service-fabric/service-fabric-replica-soft-delete.md
Medium 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 notable Windows bias by exclusively referencing PowerShell-based administrative APIs (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica) and showing only PowerShell command examples. There is no mention of Linux/macOS equivalents, CLI alternatives, or cross-platform SDK usage patterns. Windows tools and terminology are used throughout, and examples are Windows-centric, creating friction for Linux/macOS users.
Recommendations
  • Provide equivalent examples using Service Fabric CLI (sfctl) for Linux/macOS users, where available.
  • Explicitly document how to perform replica soft delete and restore operations using REST APIs or FabricClient SDK in cross-platform languages (e.g., Python, .NET Core).
  • Clarify which APIs and tools are available on Linux clusters and how to access them.
  • Add a section summarizing cross-platform support and differences in administrative tooling.
  • Ensure screenshots and command outputs include Linux/macOS variants where applicable.
GitHub Create Pull Request
Virtual Machine Scale Sets Overview of autoscale with Azure Virtual Machine Scale Sets ...-sets/virtual-machine-scale-sets-autoscale-overview.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 moderate Windows bias. Windows tools (Azure PowerShell) are frequently mentioned and examples are provided for PowerShell before Linux-friendly alternatives. The CLI example is present, but PowerShell is consistently listed first in several sections, and the 'Next steps' and management links focus on PowerShell. There are no explicit Linux/macOS shell examples (e.g., Bash), and no mention of platform-specific nuances for Linux/macOS users. The diagnostics extension section does link to both Linux and Windows instructions, but overall, Windows-centric tools and patterns are prioritized.
Recommendations
  • Ensure that CLI examples (az CLI) are listed before or alongside PowerShell examples.
  • Add explicit Bash or Linux/macOS shell examples where appropriate.
  • Include links to Linux/macOS management documentation in 'Next steps' and management sections.
  • Balance references to Azure PowerShell with Azure CLI throughout the page.
  • Highlight any platform-specific considerations for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Scale a Service Fabric cluster in Azure ...ervice-fabric/service-fabric-tutorial-scale-cluster.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 page exhibits a notable Windows bias. The tutorial repeatedly references creating a secure Windows cluster, with no mention or examples for Linux clusters. All code snippets and template references are for Windows clusters, and the linked sample templates are Windows-only. PowerShell commands are shown first and in greater detail, with Azure CLI as a secondary option. Windows-specific tools and concepts (e.g., RDP, Windows file paths, Windows Service Fabric node extensions) are referenced throughout, while Linux equivalents are not discussed or provided.
Recommendations
  • Add explicit instructions and examples for scaling Linux Service Fabric clusters, including template references and parameter differences.
  • Provide Linux-specific code snippets and clarify any OS-specific steps, especially for VM extensions, file paths, and node management.
  • Include links to Linux sample templates and parameter files.
  • Discuss differences in durability, reliability, and node management between Windows and Linux clusters.
  • Present Azure CLI examples before or alongside PowerShell, and clarify cross-platform compatibility.
  • Avoid Windows-specific terminology (e.g., RDP, Windows file paths) or provide Linux alternatives (e.g., SSH, Linux file paths).
GitHub Create Pull Request
Service Fabric How to view Azure Service Fabric entities' aggregated health ...bric/service-fabric-view-entities-aggregated-health.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 page demonstrates a notable Windows bias. All command-line examples use PowerShell cmdlets, which are native to Windows and not available by default on Linux/macOS. The examples reference Windows file paths (e.g., D:\ServiceFabric, C:\), and there is no mention of Linux/macOS equivalents or cross-platform CLI tools (such as Azure CLI or Service Fabric CLI). Windows tools and patterns are presented exclusively and before REST or API alternatives, and there are no Linux-specific instructions or examples.
Recommendations
  • Add equivalent examples using Azure CLI (az sf) or Service Fabric CLI (sfctl), which are cross-platform and supported on Linux/macOS.
  • Include notes or sections clarifying how Linux/macOS users can perform the same tasks, including installation steps for CLI tools.
  • Avoid using Windows-specific file paths in examples, or provide platform-agnostic alternatives.
  • Explicitly mention the availability of PowerShell Core on Linux/macOS, if relevant, and provide usage instructions.
  • Reorder examples so that REST/API or cross-platform CLI instructions are presented before or alongside PowerShell examples.
GitHub Create Pull Request
Virtual Machine Scale Sets Create a scale set from a generalized image ...chine-scale-sets/instance-generalized-image-version.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 PowerShell examples, which are primarily relevant for Windows users. The PowerShell section is significantly longer and more detailed than the CLI section, including advanced networking and load balancer configuration. Windows-specific tools (PowerShell cmdlets) are featured, and the PowerShell tab appears after CLI but before Linux-native scripting options (none are given). There are no Bash or Linux shell script equivalents for the advanced scenarios, and the CLI examples use generic Azure CLI commands but do not provide parity for the advanced PowerShell scenarios.
Recommendations
  • Add Bash/Linux shell script examples for advanced scenarios currently covered only by PowerShell (e.g., networking, load balancer, and full VMSS configuration).
  • Explicitly mention Linux/macOS compatibility for CLI commands and provide troubleshooting tips for non-Windows environments.
  • Reorder examples to present CLI (cross-platform) before PowerShell, and clarify that PowerShell is Windows-centric.
  • Where PowerShell cmdlets are used for resource creation, provide equivalent Azure CLI or ARM template examples.
  • Highlight SSH key usage and Linux admin practices in examples, not just generic admin/password prompts.
GitHub Create Pull Request
Virtual Machine Scale Sets Configure role permissions for standby pools ...hine-scale-sets/standby-pools-configure-permissions.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 references the Azure portal UI for role assignment and troubleshooting, which is platform-agnostic but most commonly associated with Windows environments. There are no command-line examples (such as Azure CLI or PowerShell) for role assignment, and when SDKs are mentioned, PowerShell is listed before CLI, suggesting a Windows-first approach. No Linux/macOS-specific guidance or parity is provided for key tasks.
Recommendations
  • Add Azure CLI examples for role assignment and troubleshooting alongside or before PowerShell references.
  • Explicitly mention that all steps can be performed from Linux/macOS using Azure CLI or REST API.
  • Provide links to cross-platform command-line documentation for RBAC and Log Analytics tasks.
  • When listing SDKs, mention CLI before PowerShell or present them together to avoid Windows-first bias.
GitHub Create Pull Request
Virtual Machine Scale Sets Use Azure Log Analytics to monitor standby pool events ...achine-scale-sets/standby-pools-monitor-pool-events.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 provides PowerShell and Azure CLI examples for configuring diagnostic settings, but omits explicit Linux shell (bash) or macOS terminal examples. PowerShell is a Windows-centric tool, and its inclusion without parity for Linux-native tools or examples creates friction for non-Windows users. The instructions for creating resources and configuring alerts rely on the Azure portal, which is cross-platform, but the scripting guidance is Windows-biased.
Recommendations
  • Add explicit bash shell examples for Linux/macOS users alongside PowerShell and CLI sections.
  • Clarify that Azure CLI commands work on Linux/macOS and provide installation/setup guidance for these platforms.
  • Include notes or links for Linux/macOS users on how to authenticate and run Azure CLI commands in their environment.
  • Avoid presenting PowerShell examples without Linux equivalents, or present CLI/bash examples first.
GitHub Create Pull Request
Virtual Machine Scale Sets Spot Placement Score ...les/virtual-machine-scale-sets/spot-placement-score.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 provides platform-specific instructions for accessing the Spot Placement Score via Azure CLI, REST API, and Azure PowerShell. The PowerShell example is given its own dedicated section and command, and the Azure CLI example is presented as a separate tab. However, there is no mention of Linux/macOS-specific shell usage (e.g., Bash), nor are there examples for scripting with Bash or other common Linux tools. The PowerShell example is presented after the CLI example, but both are given equal prominence, and there is no explicit prioritization of Linux workflows. The documentation does not mention any Linux-specific considerations or tools, and the troubleshooting and examples sections are platform-neutral.
Recommendations
  • Add explicit Bash shell examples for Linux/macOS users, showing how to invoke the REST API using curl or similar tools.
  • Clarify that Azure CLI is cross-platform and works on Linux/macOS, and provide example commands run in Bash.
  • Include notes or sections on Linux/macOS environment setup for Azure CLI and REST API usage.
  • Ensure parity by mentioning Linux/macOS usage wherever PowerShell is referenced, and avoid implying PowerShell is the default or only scripting option.
  • Consider listing CLI/Bash examples before PowerShell to signal Linux parity.
GitHub Create Pull Request
Virtual Machine Scale Sets Create a standby pool for Virtual Machine Scale Sets ...les/virtual-machine-scale-sets/standby-pools-create.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 both Azure CLI and PowerShell examples for creating a standby pool, but PowerShell is given equal prominence as CLI, and PowerShell-specific deployment commands are referenced in ARM and Bicep sections alongside CLI. There is a slight Windows bias due to the explicit inclusion of PowerShell examples and deployment instructions, while Linux/macOS alternatives (such as Bash scripting or shell-specific notes) are not mentioned. The CLI examples are cross-platform, but the repeated mention of PowerShell and its deployment commands may create friction for Linux/macOS users.
Recommendations
  • Clarify that Azure CLI commands work on Linux/macOS and provide shell-specific notes if needed.
  • In ARM and Bicep sections, mention that 'az deployment group create' is cross-platform and provide examples for Bash or other shells.
  • Consider adding a note for Linux/macOS users that PowerShell is optional and CLI is fully supported.
  • If PowerShell is required for any functionality, explicitly state whether it is available on Linux/macOS via PowerShell Core.
GitHub Create Pull Request
Virtual Machine Scale Sets Deploy an application to an Azure Virtual Machine Scale Set ...ne-scale-sets/virtual-machine-scale-sets-deploy-app.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 provides both Linux and Windows guidance, but Windows/PowerShell examples and tooling are often presented first or in greater detail. Windows-specific tools (PowerShell DSC) receive a full code example, while the Linux equivalent (cloud-init) is described but lacks a direct example file. References to PowerShell management are prominent, and some links or sections prioritize Windows approaches before Linux ones.
Recommendations
  • Ensure Linux and Windows examples are presented with equal prominence and detail, ideally side-by-side.
  • Provide a direct cloud-init example file in the documentation, similar to the PowerShell DSC example.
  • Include links to Linux management guides (e.g., using Azure CLI or SSH) alongside PowerShell management references.
  • Avoid listing Windows/PowerShell tutorials before Linux/CLI ones unless contextually justified.
  • Clarify parity in features and workflows between Windows and Linux, especially for advanced scenarios.
GitHub Create Pull Request
Virtual Machine Scale Sets Use Application Health extension with Azure Virtual Machine Scale Sets ...le-sets/virtual-machine-scale-sets-health-extension.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 exhibits a moderate Windows bias. In multi-platform code tabs, Windows/PowerShell examples are consistently presented first, and REST API examples use Windows-based scale sets by default. PowerShell (a Windows-centric tool) is given prominent coverage, with Linux/CLI examples appearing later. REST and PowerShell examples default to 'ApplicationHealthWindows' and Windows resource names, while Linux examples are only provided under Azure CLI sections. Troubleshooting commands are PowerShell-focused, and Windows log file paths are listed before Linux equivalents.
Recommendations
  • Present Linux and Windows examples with equal prominence, alternating which appears first or grouping by OS rather than tool.
  • In REST API and JSON schema examples, provide both 'ApplicationHealthLinux' and 'ApplicationHealthWindows' variants, or use a neutral placeholder.
  • Include Azure CLI and PowerShell examples for both Linux and Windows scale sets in all relevant sections.
  • In troubleshooting, provide equivalent Linux commands (e.g., using Azure CLI or Bash) alongside PowerShell.
  • List Linux and Windows log file paths together or alternate their order.
  • Use neutral resource names (e.g., 'myVMScaleSet' instead of 'myVMScaleSet' for Windows and 'myLinuxVMScaleSet' for Linux) in examples.
GitHub Create Pull Request
Virtual Machine Scale Sets Use extension sequencing with Azure Virtual Machine Scale Sets ...ets/virtual-machine-scale-sets-extension-sequencing.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 command-line examples for extension sequencing use Windows-centric tools (PowerShell and Azure CLI) and reference Windows-based scale sets. The examples specifically mention and use Windows extensions (ApplicationHealthWindows, CustomScriptExtension for Windows), with no mention or example for Linux-based scale sets or Linux extensions. The PowerShell example is presented before the CLI example, and both are tailored to Windows environments. There are no Linux-specific instructions, examples, or references.
Recommendations
  • Add equivalent examples for Linux-based scale sets, using Linux extensions such as ApplicationHealthLinux and CustomScriptExtension for Linux.
  • Include sample Azure CLI and PowerShell commands for Linux VMSS extension sequencing.
  • Reference Linux extension documentation and provide links to Linux extension resources.
  • Clarify in the text that extension sequencing applies to both Windows and Linux scale sets, and highlight any OS-specific differences.
  • Present examples for both Windows and Linux side-by-side or alternate their order to avoid Windows-first bias.
GitHub Create Pull Request
Virtual Machine Scale Sets Terminate notification for Azure Virtual Machine Scale Set instances ...s/virtual-machine-scale-sets-terminate-notification.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 shows moderate Windows bias: Windows/Powershell examples and links are presented before Linux equivalents, with PowerShell-specific instructions and links to Windows documentation appearing more prominently. Linux-specific examples (e.g., bash scripts, Linux CLI patterns) are less detailed or referenced only via links. The REST API and Azure CLI sections are cross-platform, but the PowerShell section is Windows-centric, and some cross-references (e.g., Scheduled Events) link to Windows docs first.
Recommendations
  • Present Linux and Windows examples side-by-side or alternate their order to avoid Windows-first bias.
  • Add explicit bash or shell script examples for querying/responding to Scheduled Events, not just PowerShell.
  • Ensure all cross-references to Scheduled Events and event properties link to both Windows and Linux documentation equally.
  • Include troubleshooting steps and tips that mention Linux-specific tooling or issues.
  • Highlight Azure CLI as a cross-platform tool and provide parity in example detail with PowerShell.
GitHub Create Pull Request
Virtual Machine Scale Sets Custom metrics for rolling upgrades on Virtual Machine Scale Sets ...tual-machine-scale-sets-rolling-upgrade-custom-metrics.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 provides both Linux (Bash/Python) and Windows (PowerShell) examples for configuring custom metrics and the application health extension. However, there is a notable Windows bias: PowerShell examples are consistently present and sometimes more detailed, Windows-specific extension types (ApplicationHealthWindows) are shown before Linux equivalents, and Windows tooling (PowerShell cmdlets) is given equal or greater prominence than Linux CLI/Bash workflows. In some places, Windows extension types are used as defaults in examples, and PowerShell scripts are more elaborate than Bash equivalents.
Recommendations
  • Ensure Linux and Windows extension types are shown side-by-side in all examples, not defaulting to Windows.
  • Provide equally detailed Bash/Python scripts for Linux as for PowerShell on Windows, including troubleshooting and server setup.
  • Where both CLI and PowerShell are shown, alternate which is presented first, or use neutral ordering.
  • Explicitly mention Linux/macOS compatibility and provide guidance for common Linux distributions.
  • Clarify when examples are OS-specific and provide parity for both platforms in every workflow.
GitHub Create Pull Request
Virtual Machines Automatic Extension Upgrade for VMs and scale sets in Azure ...ticles/virtual-machines/automatic-extension-upgrade.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 documentation exhibits a moderate Windows bias. In code examples for enabling Automatic Extension Upgrade, the 'DependencyAgentWindows' extension type is used in REST, PowerShell, and ARM template samples, while the CLI examples use 'DependencyAgentLinux'. PowerShell examples are provided, but no Bash or Linux shell script equivalents are shown. Windows extension types are shown first in most code blocks, and PowerShell is presented as the only scripting option. There is no explicit mention of Linux-specific considerations or troubleshooting, and Windows-centric tools (PowerShell) are featured without Linux alternatives.
Recommendations
  • Provide parallel examples for both Windows and Linux extension types in all code blocks (REST, PowerShell, CLI, ARM templates), e.g., show both 'DependencyAgentWindows' and 'DependencyAgentLinux' in each section.
  • Include Bash or shell script examples for Linux users, especially in scripting sections.
  • Add explicit notes or troubleshooting tips for Linux users where extension behavior may differ.
  • When listing supported extensions, alternate the order or group by OS to avoid Windows-first presentation.
  • Mention Linux-native tools or commands where relevant, not just PowerShell.
GitHub Create Pull Request
Virtual Machines Automatic Guest Patching for Azure Virtual Machines and Scale Sets ...ticles/virtual-machines/automatic-vm-guest-patching.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 provides extensive coverage for both Windows and Linux VMs, but there is a notable Windows bias in several areas. Windows examples (especially PowerShell and CLI) are more detailed and appear first, with Linux examples often missing or less emphasized. PowerShell commands are provided only for Windows, and Windows-specific tools and registry keys are discussed in detail, while Linux equivalents are less prominent or omitted. The 'Next steps' section links only to Windows VM management.
Recommendations
  • Provide Linux-specific PowerShell/CLI examples where possible, especially in sections where only Windows commands are shown.
  • Ensure Linux examples are presented alongside Windows examples, not after or omitted.
  • Add links to Linux VM management tutorials in the 'Next steps' section.
  • Balance the discussion of OS-specific tools and configuration (e.g., registry keys for Windows, systemd/services for Linux).
  • Where Windows-specific behaviors or limitations are described, include equivalent Linux details or explicitly state differences.
GitHub Create Pull Request
Virtual Machines Azure VM Watch .../blob/main/articles/virtual-machines/azure-vm-watch.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 for Azure VM Watch demonstrates some Windows bias. Several health signals and checks are Windows-specific (e.g., System Errors from Windows event log, Hardware Health Monitor from Windows event log, and fallback to w32tm for clock sync on Windows). Windows tools and patterns (event log, w32tm) are mentioned explicitly, while Linux equivalents are not described or referenced. In some cases, Linux-only metrics are called out, but Windows-only checks are more prevalent and described with more detail. There are no explicit Linux command or tool references (e.g., journalctl, systemd, ntpd), and Windows-specific fallback mechanisms are described without Linux parity.
Recommendations
  • Add Linux equivalents for Windows-specific checks, such as describing how system errors can be collected from Linux logs (e.g., journalctl, /var/log/syslog).
  • Provide Linux-specific fallback mechanisms for clock sync checks (e.g., ntpd, chrony status commands) similar to the Windows w32tm fallback.
  • Balance the documentation by mentioning Linux tools and commands where Windows tools are referenced.
  • Include example commands or references for both platforms when describing health checks or troubleshooting steps.
  • Clarify which signals are platform-specific and provide parity where possible.
GitHub Create Pull Request
Virtual Machines Overview backup options for VMs ...blob/main/articles/virtual-machines/backup-recovery.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation generally presents backup options in a platform-neutral way, but there is a notable bias in the 'Managed snapshots' section: the only example link provided is for Windows ('Create copy of VHD stored as a Managed Disk'), with no equivalent Linux example or mention. This may cause friction for Linux users seeking parity in snapshot operations.
Recommendations
  • Add a Linux-specific example or documentation link for creating managed disk snapshots (e.g., 'Create copy of VHD stored as a Managed Disk on Linux').
  • Ensure that example links and walkthroughs are provided for both Windows and Linux platforms, or clarify when procedures are identical.
  • Review other sections for subtle platform prioritization and explicitly mention Linux support where relevant.
GitHub Create Pull Request
Virtual Machines Associate a virtual machine scale set with Uniform Orchestration to a capacity reservation group. ...pacity-reservation-associate-virtual-machine-scale-set.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 page exhibits moderate Windows bias, particularly in the ARM template section, which is heavily oriented toward Windows VM deployment (Windows OS images, PowerShell DSC, Windows-specific artifacts). PowerShell examples are provided alongside CLI, but Linux-specific scripting or configuration is not addressed. The ARM template parameters and variables default to Windows-centric values and tooling, with no parallel Linux example or guidance. The CLI examples do use Ubuntu images, but the template and scripting guidance are Windows-first.
Recommendations
  • Add ARM template examples and parameters for Linux VM images (e.g., Ubuntu, CentOS) alongside Windows examples.
  • Include Linux-specific configuration options (such as cloud-init or custom script extensions) in ARM templates.
  • Balance PowerShell examples with Bash or shell scripting examples for Linux/macOS users.
  • Clarify in the documentation that both Windows and Linux VMs are supported, and provide explicit guidance for Linux deployments.
  • Provide links to Linux VM scale set quickstarts or reference architectures.
GitHub Create Pull Request
Virtual Machines Associate a virtual machine to a capacity reservation group .../virtual-machines/capacity-reservation-associate-vm.md
Medium 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 claims to apply to both Windows and Linux VMs, and provides Azure CLI, API, Portal, ARM template, and PowerShell instructions for associating VMs with capacity reservation groups. However, there is a notable Windows bias: the ARM template example is exclusively for Windows Server (no Linux image or parameters shown), and password requirements are described in Windows-centric terms. PowerShell examples (a Windows-centric tool) are given equal prominence as CLI, but no bash or Linux shell examples are provided. Windows terminology and tools (e.g., PowerShell, Windows images) are referenced before or instead of Linux equivalents. There are no explicit Linux-focused examples or ARM template snippets for Linux VMs.
Recommendations
  • Add ARM template examples for Linux VM images (e.g., Ubuntu, CentOS) alongside the Windows example.
  • Clarify password requirements for Linux VMs (e.g., SSH key usage) and provide Linux-specific administrator account guidance.
  • Include bash or Linux shell examples for common tasks, especially for users who do not use PowerShell.
  • Ensure that examples and parameter lists are balanced between Windows and Linux, or provide tabs for each OS where relevant.
  • Mention Linux-specific considerations (e.g., SSH authentication, cloud-init) where appropriate.
GitHub Create Pull Request
Virtual Machines Remove a virtual machine scale set association from a capacity reservation group ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/capacity-reservation-remove-virtual-machine-scale-set.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides examples for API, Azure CLI, PowerShell, and Portal. PowerShell is included as a dedicated tab, which is primarily a Windows tool, and is referenced with links and detailed usage. While Azure CLI is cross-platform and shown before PowerShell, the presence of PowerShell as a first-class example and the explicit references to PowerShell commands indicate a moderate Windows bias. There are no Linux-specific shell examples (e.g., Bash), nor is there mention of Linux/macOS-specific considerations. However, the CLI examples are sufficient for Linux/macOS users to complete the tasks.
Recommendations
  • Add explicit notes clarifying that Azure CLI commands work on Linux/macOS as well as Windows.
  • Consider including Bash or shell script examples for Linux users, especially for automation scenarios.
  • If PowerShell is shown, mention that PowerShell Core is available cross-platform, or clarify any Windows-specific limitations.
  • Ensure that CLI examples are as detailed as PowerShell ones, including links to relevant CLI documentation.
  • Avoid presenting PowerShell as the default or preferred method unless necessary.
GitHub Create Pull Request
Virtual Machines Delete a VM and attached resources ...ute-docs/blob/main/articles/virtual-machines/delete.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 provides examples for Azure Portal, CLI, PowerShell, and REST API. PowerShell is featured as a primary scripting option alongside CLI, but there is no mention of Linux shell scripting (e.g., Bash) or Linux-specific patterns. The CLI examples are cross-platform, but PowerShell is Windows-centric and presented as an equal alternative. REST API examples use Windows-centric resource names and images, and the FAQ and backup management instructions reference the portal with Windows-style navigation. There are no explicit Linux/macOS shell examples, and Windows tools (PowerShell) are given equal prominence to CLI, which may create friction for Linux/macOS users.
Recommendations
  • Add explicit Bash shell examples for common operations, especially for updating and deleting VMs and resources.
  • Clarify that Azure CLI commands are cross-platform and can be run on Linux/macOS terminals.
  • In REST API examples, use neutral or Linux-centric image references and OS types where appropriate.
  • In PowerShell sections, add notes for Linux users about alternatives (e.g., Azure CLI, Bash scripting).
  • In FAQ and portal navigation, clarify that the portal is OS-agnostic and accessible from any browser.
  • Consider reordering examples to present CLI (cross-platform) before PowerShell (Windows-centric).
GitHub Create Pull Request
Virtual Machines Copy a snapshot to a new region ...ines/disks-copy-incremental-snapshot-across-regions.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 provides detailed examples for Azure CLI (which is cross-platform) and Azure PowerShell (primarily Windows-focused), with PowerShell examples given equal prominence as CLI. However, there are no explicit Linux/macOS shell examples (e.g., bash), nor are Linux-specific considerations or troubleshooting tips mentioned. The CLI examples use bash syntax, but this is not explicitly stated or explained for Linux users. The manual copy section refers only to .NET sample code, with no mention of Linux-native tooling or languages.
Recommendations
  • Explicitly state that Azure CLI examples use bash syntax and are suitable for Linux/macOS terminals.
  • Add Linux/macOS-specific notes or troubleshooting tips, especially for manual copy scenarios.
  • Provide sample code or references for manual copy using Linux-native tools (e.g., Python, shell scripts) in addition to .NET.
  • Clarify cross-platform compatibility for each method, especially for PowerShell (which is available on Linux but less commonly used).
  • Consider listing CLI (bash) examples before PowerShell to reduce perceived Windows-first bias.
GitHub Create Pull Request
Virtual Machines Deploy a ZRS managed disk ...lob/main/articles/virtual-machines/disks-deploy-zrs.md
Medium 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. While Azure CLI examples (which are cross-platform) are provided and shown before PowerShell, the PowerShell sections are extensive and all examples use Windows-centric patterns (e.g., Windows images, Windows admin credentials, Windows-specific VM configuration). Resource Manager template examples are also presented using PowerShell commands and Windows images. There is no explicit Linux/macOS example in PowerShell or ARM template sections, and Windows tooling (PowerShell) is assumed for feature registration and deployment steps.
Recommendations
  • Add PowerShell examples that use Linux images and Linux-style credential setup.
  • Provide bash or shell script equivalents for ARM template deployment and feature registration, or clarify that Azure CLI can be used for these steps.
  • Explicitly mention cross-platform alternatives for all PowerShell commands, especially for feature registration and template deployment.
  • Balance the examples by including Linux/macOS-specific instructions or notes in sections currently focused on Windows.
  • Clarify that Azure CLI is fully supported on Linux/macOS and highlight its parity with PowerShell for these tasks.
GitHub Create Pull Request
Virtual Machines Ultra disks for VMs - Azure managed disks ...in/articles/virtual-machines/disks-enable-ultra-ssd.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 Windows bias in several ways. In command examples for deploying Ultra Disks using Azure CLI and PowerShell, the VM image used is always 'Win2016Datacenter', with no Linux equivalent shown. The portal instructions link only to the Windows VM quickstart, omitting the Linux VM counterpart. There are no examples or guidance for deploying Ultra Disks with Linux images, nor any Linux-specific configuration or validation steps. This may cause confusion or extra effort for Linux users seeking parity.
Recommendations
  • Provide Linux VM deployment examples alongside Windows, e.g., using Ubuntu or CentOS images in CLI and PowerShell commands.
  • Add links to both Windows and Linux VM quickstart guides in the portal section.
  • Clarify that Ultra Disks are supported for Linux VMs and provide any Linux-specific considerations (e.g., partitioning, formatting, or driver requirements).
  • Ensure screenshots and walkthroughs are not Windows-centric, or provide Linux alternatives where relevant.
GitHub Create Pull Request
Virtual Machines Migrate Standard HDD OS disks by September 08, 2028 ...n/articles/virtual-machines/disks-hdd-os-retirement.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 page mentions both Linux and Windows VMs as affected, but when providing examples for listing affected disks, it references Azure PowerShell before Azure CLI, and the PowerShell example is given first. PowerShell is primarily a Windows tool, while Azure CLI is cross-platform. The Disk Storage Center is also a GUI tool that is most familiar to Windows users. There are no Linux-specific command-line examples or shell scripts, and no mention of Linux-native tooling or patterns.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and preferred by many Linux/macOS users.
  • Include bash shell script examples for listing affected disks, demonstrating usage on Linux/macOS.
  • Explicitly mention that Azure CLI works natively on Linux/macOS and provide installation links.
  • Clarify that Disk Storage Center is accessible via browser on any OS, not just Windows.
  • Add a note about using automation tools (e.g., bash, Python) for Linux users to script migrations.
GitHub Create Pull Request
Virtual Machines Deploy a Premium SSD v2 managed disk ...n/articles/virtual-machines/disks-deploy-premium-v2.md
Medium 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 demonstrates a moderate Windows bias. VM creation examples consistently use Windows images (e.g., 'Win2016Datacenter') and Windows-style authentication (username/password), with no mention of Linux images or SSH authentication. PowerShell is given equal prominence to Azure CLI, but CLI examples are tailored to Windows VM deployment. There are no explicit Linux-specific examples or guidance for deploying Premium SSD v2 disks with Linux VMs, nor are Linux authentication patterns (SSH keys) covered.
Recommendations
  • Add explicit Linux VM deployment examples using Azure CLI and PowerShell, including common Linux images (e.g., UbuntuLTS, CentOS).
  • Show how to use SSH key authentication for Linux VMs in CLI and PowerShell examples.
  • In variable initialization, provide both Windows and Linux image options, and clarify which parameters are OS-specific.
  • When presenting examples, alternate or parallel Windows and Linux scenarios, or provide a table of common images.
  • Clarify that Azure CLI and PowerShell are cross-platform, and provide notes on usage from Linux/macOS terminals.
  • Ensure portal screenshots and instructions mention Linux VM options where relevant.
GitHub Create Pull Request
Virtual Machines Instantly access managed disk snapshots ...les/virtual-machines/disks-instant-access-snapshots.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 provides both Azure CLI (cross-platform) and Azure PowerShell (Windows-centric) examples for creating instant access snapshots, but does not include explicit Linux shell (bash) or macOS-specific examples. The PowerShell example is given equal prominence to the CLI, and the CLI example uses bash syntax but does not clarify Linux/macOS compatibility or provide troubleshooting for those platforms. There are no references to Linux-specific tools or workflows, and the order of examples sometimes places PowerShell before Resource Manager templates, which are platform-neutral. The documentation does not mention any Linux-specific considerations or alternatives for monitoring or scripting.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux/macOS and provide troubleshooting tips for common platform-specific issues (e.g., quoting, environment variables).
  • Add a dedicated Linux/macOS shell example, clarifying any differences in syntax or prerequisites.
  • Include notes or links for Linux users regarding installation of Azure CLI and authentication methods.
  • Balance example order by listing CLI (cross-platform) first, followed by PowerShell (Windows), and clearly label platform compatibility for each.
  • Mention any Linux-specific tools (e.g., jq for JSON parsing) where relevant.
GitHub Create Pull Request
Virtual Machines Convert a disk from LRS to ZRS ...ain/articles/virtual-machines/disks-migrate-lrs-zrs.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 presents Azure Portal (a GUI often associated with Windows) and Azure PowerShell examples before Azure CLI examples in every major section. PowerShell, a Windows-centric tool, is given equal or greater prominence than Azure CLI, which is more common on Linux/macOS. There are no explicit Linux/macOS-specific instructions, nor are Linux shell patterns (e.g., bash, sh) used in examples. The only mention of Linux is in the final VM creation CLI example, which sets --os-type linux, but this is not explained or highlighted for parity.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as CLI is more cross-platform and preferred by Linux/macOS users.
  • Add explicit notes or sections for Linux/macOS users, clarifying that all CLI commands work natively on those platforms.
  • Include bash/sh shell variable syntax in CLI examples (e.g., export, $VAR) instead of PowerShell variable syntax ($var), which may confuse Linux users.
  • Where Portal instructions are given, clarify that the Portal is OS-agnostic and accessible from any browser.
  • Add troubleshooting notes for Linux/macOS users if any step differs from Windows.
  • Consider a dedicated 'Linux/macOS' tab or section if there are platform-specific nuances.
GitHub Create Pull Request
Virtual Machines Restrict managed disks from being imported or exported ...tual-machines/disks-restrict-import-export-overview.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell and Windows-centric links are referenced first or exclusively in several sections (e.g., custom RBAC role creation, secure uploads with Azure AD). Windows tools and terminology (PowerShell, portal) are mentioned before their Linux equivalents, and some links point to Windows-specific guides before CLI/Linux alternatives. However, Linux/CLI options are generally present, and critical tasks can be completed on Linux/macOS.
Recommendations
  • Provide both PowerShell and CLI examples side-by-side in all relevant sections.
  • Link to Linux/CLI documentation before or alongside Windows/PowerShell documentation.
  • Ensure terminology is platform-neutral (e.g., 'Azure CLI or PowerShell' instead of 'PowerShell').
  • Add explicit Linux/macOS instructions for custom RBAC role creation and other tasks currently referencing only PowerShell.
  • Review all links to ensure parity in depth and clarity between Windows and Linux/macOS guides.
GitHub Create Pull Request
Virtual Machines Share an Azure managed disk across VMs ...cs/blob/main/articles/virtual-machines/disks-shared.md
Medium 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 moderate Windows bias. Windows clustering tools (WSFC, CSV, Scale-Out File Server) are described first and in greater detail, with multiple application examples and links to Windows-specific templates. Linux equivalents (Pacemaker, Corosync, ocfs2, gfs2) are mentioned, but with less depth and fewer practical examples. The 'Sample workloads' section lists several Windows scenarios before Linux, and the 'Examples' section provides more detailed Windows cluster configurations. There are no explicit command-line examples for either platform, but Windows tools and patterns are referenced more prominently.
Recommendations
  • Add Linux-first examples and templates, such as step-by-step guides for configuring Pacemaker/Corosync clusters with Azure shared disks.
  • Provide parity in application scenarios for Linux (e.g., clustered file servers, SAP, database failover) with links to relevant templates or walkthroughs.
  • Include practical Linux command-line examples (e.g., using sg_persist, fence_scsi) for disk reservation and failover operations.
  • Ensure that Linux tools and patterns are described with equal detail and prominence as Windows equivalents.
  • Alternate the order of Windows and Linux sections, or present them side-by-side for direct comparison.
GitHub Create Pull Request
Virtual Machines FAQ Ephemeral OS disks ...in/articles/virtual-machines/ephemeral-os-disks-faq.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 detailed PowerShell script for determining VM support for ephemeral OS disks, but does not offer equivalent examples for Linux/macOS users (e.g., Bash, Azure CLI). This creates friction for non-Windows users, who must translate the script or seek alternative methods. The documentation also references PowerShell and ARM templates before CLI, and does not mention Linux-specific tools or workflows.
Recommendations
  • Provide equivalent Azure CLI and/or Bash script examples for checking VM SKU support for ephemeral OS disks.
  • List cross-platform tools (CLI, REST, Templates) before or alongside PowerShell in all relevant sections.
  • Explicitly mention Linux/macOS compatibility and provide guidance for those platforms.
  • Where scripts are provided, offer both PowerShell and Bash/CLI versions side-by-side.
GitHub Create Pull Request
Virtual Machines Use Application Health extension with Azure Virtual Machines ...ticles/virtual-machines/extensions/health-extension.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 frequently presents Windows-based examples first, especially in REST API and PowerShell sections, and provides more detailed PowerShell instructions for Windows than for Linux. While Azure CLI examples are given for Linux, there is a lack of parity in scripting examples (e.g., no Bash or shell script equivalents for Linux users). The troubleshooting and log location sections do mention Linux, but overall, Windows tools and patterns are prioritized or more thoroughly documented.
Recommendations
  • Present Linux and Windows examples side-by-side or alternate which comes first in each section.
  • Provide Bash or shell script examples for Linux users, especially where PowerShell is used for Windows.
  • Expand Linux-specific guidance, such as troubleshooting steps and log analysis, to match the detail given for Windows.
  • Explicitly mention Linux/macOS compatibility and any platform-specific caveats in each relevant section.
  • Ensure that all REST API and Azure CLI examples clearly indicate how to use them for both Linux and Windows VMs, including the correct 'type' property.
GitHub Create Pull Request
Virtual Machines Azure Key Vault VM Extension for Linux ...rticles/virtual-machines/extensions/key-vault-linux.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
While the documentation is focused on the Linux Key Vault VM extension, there are several instances of Windows bias. PowerShell examples are presented before Azure CLI examples in deployment and troubleshooting sections, and PowerShell-specific warnings and patterns are included. References to Windows-centric tools (PowerShell) and links to Windows VM guides appear before or alongside Linux instructions, even though the extension is Linux-specific. This ordering and emphasis may create friction for Linux users who expect bash or CLI-first guidance.
Recommendations
  • Present Azure CLI examples before PowerShell in all deployment and troubleshooting sections, as CLI is cross-platform and native to Linux.
  • Minimize or move PowerShell-specific warnings and notes to a dedicated 'Windows deployment' section or an appendix.
  • Ensure all references to VM identity and Key Vault access policy configuration link to Linux-specific guides or provide Linux CLI instructions.
  • Add explicit bash script examples for common deployment and troubleshooting tasks.
  • Remove or rephrase any references that imply PowerShell is the default or preferred method for Linux VM extension deployment.
GitHub Create Pull Request
Virtual Machines Qualys Cloud Agent Extension for Azure VMs ...ob/main/articles/virtual-machines/extensions/qualys.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 Windows examples and links before Linux equivalents in several sections, and includes a dedicated 'Deploy Cloud Agent via PowerShell' section, which is a Windows-centric tool (even though a Linux PowerShell link is provided). There are no explicit Linux shell or native command-line examples, and the ordering and tool emphasis may create friction for Linux users.
Recommendations
  • Alternate the order of Windows and Linux examples/links in each section, or group them together under neutral headings.
  • Provide native Linux shell (bash) command examples or links, not just PowerShell, for Linux deployments.
  • Clarify in the 'PowerShell' section that PowerShell Core is cross-platform, and provide bash/CLI alternatives where appropriate.
  • Ensure that automation tool examples (e.g., Ansible, Chef, Puppet) include both Windows and Linux usage scenarios.
GitHub Create Pull Request
Virtual Machines Azure FPGA Attestation Service ...machines/field-programmable-gate-arrays-attestation.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 provides both PowerShell and Bash examples for running attestation scripts, but PowerShell is presented first and in more detail (including monitoring status). The monitoring example is only shown for PowerShell, with no Bash or Linux equivalent. There is a slight emphasis on PowerShell and Windows tools, and some steps (like monitoring) lack Linux/Bash parity.
Recommendations
  • Add Bash/Linux examples for monitoring attestation status, similar to the PowerShell Monitor-Validation.ps1 example.
  • Present Bash and PowerShell examples side-by-side or alternate which is shown first to avoid Windows-first ordering.
  • Clarify that all scripts and commands (including monitoring) are available and supported on Linux/macOS, or provide alternative Bash scripts if not.
  • Explicitly mention Linux/macOS compatibility for all steps, not just initial prerequisites.
  • If PowerShell scripts are required for some steps, provide guidance for installing and using PowerShell on Linux/macOS.
GitHub Create Pull Request
Virtual Machines Azure Write Accelerator ...es/virtual-machines/how-to-enable-write-accelerator.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 page demonstrates a moderate Windows bias. PowerShell is the primary scripting example, with detailed, step-by-step scripts provided only for PowerShell. Windows-specific tools (Chocolatey, cmd.exe, PowerShell) are referenced exclusively for installing armclient, with no mention of Linux/macOS alternatives. The PowerShell section precedes Azure CLI and REST API instructions, and the CLI section is brief by comparison. There are no Linux shell (bash) or macOS-specific examples for scripting or tool installation.
Recommendations
  • Provide equivalent bash shell scripts for enabling Write Accelerator using Azure CLI, including disk attachment and update operations.
  • Include instructions for installing armclient on Linux/macOS (e.g., via dotnet, npm, or manual download), not just via Chocolatey.
  • Mention Linux-native package managers (apt, yum, Homebrew) when discussing tool installation, or provide cross-platform installation guidance.
  • Balance the order and depth of examples: present Azure CLI and REST API usage before or alongside PowerShell, and offer parity in example detail.
  • Explicitly call out any OS-specific limitations or differences in the feature, if present.
GitHub Create Pull Request
Virtual Machines Azure VM Image Builder overview ...in/articles/virtual-machines/image-builder-overview.md
Medium 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 generally presents Azure VM Image Builder as supporting both Windows and Linux, but there are several subtle signs of Windows bias. Windows-specific tools (Sysprep, WinRM) and security baselines are mentioned before or more prominently than their Linux equivalents. PowerShell is frequently referenced, sometimes before or in place of Linux-native tools. Some examples and links (e.g., security baseline templates) are Windows-centric, and there are references to Windows-specific features (Azure Hybrid Benefit) without Linux equivalents. Linux examples and tools are present but often secondary.
Recommendations
  • Ensure Linux-specific tools and patterns (e.g., cloud-init, SSH, Linux security baselines) are mentioned with equal prominence and detail as Windows equivalents.
  • Provide Linux-first or parallel examples where Windows examples are given, especially for security, configuration, and registration tasks.
  • Include links to Linux baseline templates and best practices, not only Windows ones.
  • When referencing PowerShell, always provide equivalent Bash/Azure CLI examples and make clear which platforms each applies to.
  • Avoid mentioning Windows tools (Sysprep, WinRM) without also mentioning or explaining the Linux equivalents (cloud-init, SSH).
  • Review the order of examples and tool mentions to avoid consistently listing Windows first.
GitHub Create Pull Request
Virtual Machines Customer intent: As a cloud security administrator, I want to configure Azure Key Vault and Disk Encryption Set so that I can securely manage encryption keys for our managed disks across multiple subscriptions in compliance with security policies. ...-machines-disks-encryption-create-key-vault-powershell.md
Medium 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 Azure PowerShell cmdlets for all examples and instructions, with no mention of Azure CLI, Bash, or cross-platform alternatives. This creates a strong bias towards Windows environments and users familiar with PowerShell, making it difficult for Linux/macOS users to follow the guide without translating commands themselves.
Recommendations
  • Add equivalent Azure CLI examples for each step, as Azure CLI is cross-platform and commonly used on Linux/macOS.
  • Explicitly mention that Azure PowerShell can be installed and used on Linux/macOS, or link to installation guides for non-Windows platforms.
  • Provide Bash script examples where appropriate, especially for automation scenarios.
  • Reorder examples or provide tabs for PowerShell and CLI, so Linux/macOS users do not feel secondary.
GitHub Create Pull Request
Virtual Machines Create an encrypted image version with customer-managed keys .../articles/virtual-machines/image-version-encryption.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 page demonstrates a moderate Windows bias. PowerShell examples are presented first and in greater detail, with explicit references to Windows tools and APIs (such as Cryptography API: Next Generation). While Azure CLI examples are provided and are cross-platform, the prominence and depth of PowerShell instructions, as well as the use of Windows-centric terminology and links, may create friction for Linux/macOS users. There are no explicit Linux shell (bash) examples, and Windows tools are referenced before their Linux equivalents (if any).
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and preferred by many Linux/macOS users.
  • Add bash shell script examples for common tasks, demonstrating parity with PowerShell workflows.
  • Replace or supplement Windows-specific references (e.g., Cryptography API: Next Generation) with platform-neutral or Linux-relevant cryptographic documentation.
  • Clarify that all CLI commands work on Linux/macOS, and provide troubleshooting tips for non-Windows environments.
  • Where possible, avoid language that assumes a Windows environment (e.g., avoid referencing PowerShell as the default).
GitHub Create Pull Request
Virtual Machines Customer intent: "As an IT administrator managing virtual machines, I want to aggregate OS update statuses and availability states across my machines, so that I can efficiently monitor and ensure the health of my infrastructure." ...es/virtual-machines/includes/azure-virtual-machines.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 provides both Azure CLI and Azure PowerShell examples for each query, with PowerShell (a Windows-centric tool) always present and often listed immediately after CLI. There are dedicated sections for Windows Server OS update installation, but Linux-specific queries are less frequent and appear later in the document. There is no mention of Linux-native tools or shell scripting alternatives, and PowerShell is treated as a first-class option throughout, which may create friction for Linux/macOS users who do not use PowerShell. The documentation does not provide bash or shell script equivalents, nor does it discuss Linux-specific patterns outside of a single Linux OS update query.
Recommendations
  • Add bash/shell script examples for each query, especially for Linux/macOS users who may not use PowerShell.
  • Present CLI and PowerShell examples in parallel, or alternate their order to avoid implicit prioritization.
  • Explicitly mention Linux-native tools or alternatives where relevant.
  • Ensure Linux-specific queries (such as OS update installation) are given equal prominence and detail as Windows equivalents.
  • Clarify that Azure CLI is fully cross-platform and highlight its parity for Linux/macOS users.
GitHub Create Pull Request
Virtual Machines Customer intent: As a cloud storage administrator, I want to adjust the expiration settings of Shared Access Signatures for disks and snapshots, so that I can ensure compliance with the upcoming 60-day limit and maintain uninterrupted access for my users. ...articles/virtual-machines/includes/disks-sas-change.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation lists Azure PowerShell as a primary tool for managing SAS on disks and snapshots, alongside REST API and Azure CLI. PowerShell is a Windows-centric tool, and its mention in every step (checking, revoking, creating SAS) may signal a Windows bias. Additionally, PowerShell is listed before Linux-native alternatives (e.g., Bash scripting with Azure CLI), and no explicit Linux/macOS examples or guidance are provided.
Recommendations
  • Provide explicit Linux/macOS examples using Azure CLI and Bash.
  • Clarify that Azure CLI is cross-platform and highlight its usage for non-Windows users.
  • Reorder tool listings to avoid suggesting Windows tools first, or group them by platform.
  • Add notes or links for installing and using Azure CLI on Linux/macOS.
  • Consider including sample commands for both PowerShell and Bash.
GitHub Create Pull Request
Virtual Machines Customer intent: As a system administrator, I want to hibernate and manage virtual machines using various tools, so that I can optimize resource usage and maintain system performance effectively. ...nes/includes/hibernate-resume-platform-instructions.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 demonstrates a moderate Windows bias. PowerShell examples are provided for every operation, often with more detailed output and interaction (e.g., confirmation prompts), while Linux/macOS-specific shell examples are not present. The CLI examples use Azure CLI, which is cross-platform, but there are no bash or shell script examples, nor any mention of Linux-specific considerations. Windows-specific notes (e.g., page file location on C:) are present, but there are no equivalent Linux guest OS configuration notes. PowerShell is given equal or greater prominence than CLI, and Windows terminology/tools are referenced without Linux parity.
Recommendations
  • Add bash or shell script examples for common Linux/macOS workflows, especially for tasks like viewing VM state and managing hibernation.
  • Include Linux guest OS configuration notes for hibernation, similar to the Windows page file note.
  • Ensure that CLI examples explicitly mention their cross-platform nature and provide sample outputs for Linux/macOS terminals.
  • Balance PowerShell and CLI coverage, and avoid giving PowerShell more detailed or interactive examples unless parity is provided for Linux users.
  • Add troubleshooting or configuration tips for Linux-based VMs where relevant.
GitHub Create Pull Request
Virtual Machines Customer intent: As a cloud administrator, I want to expand virtual machine disks efficiently, so that I can manage storage capacity without downtime and ensure optimal performance in my infrastructure. ...al-machines-disks-expand-without-downtime-restrictions.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 lists Azure PowerShell as a primary tool alongside Azure CLI and the portal, but does not provide Linux-specific command examples or mention Linux-native tools. Windows-specific instructions (such as the Windows rescan function) are referenced with direct links, while the Linux equivalent is mentioned but not detailed. The order of presentation often places Windows before Linux, and there is a lack of parity in example depth.
Recommendations
  • Provide explicit Linux command-line examples (e.g., using Azure CLI on Linux, or native disk management commands like 'lsblk', 'fdisk', or 'partprobe').
  • Include step-by-step instructions for Linux disk rescanning, not just a link.
  • Ensure that Linux tools and workflows are described with equal detail and prominence as Windows/PowerShell.
  • Alternate or parallelize the order of Windows and Linux instructions to avoid Windows-first bias.
GitHub Create Pull Request
Virtual Machines Customer intent: As a cloud architect, I want to understand the limitations of shared disks across different disk types, so that I can effectively design and implement scalable virtual machine solutions in the cloud environment. .../includes/virtual-machines-disks-shared-limitations.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation repeatedly references Windows Server Failover Cluster as the only clustering solution discussed, with multiple links to Windows-specific documentation. There is no mention of Linux clustering solutions (such as Pacemaker or Corosync), nor any examples or guidance for Linux users. This creates a bias toward Windows environments and may leave Linux users without clear guidance for implementing shared disks in their scenarios.
Recommendations
  • Include references to Linux clustering solutions (e.g., Pacemaker, Corosync) and their compatibility or limitations with Azure shared disks.
  • Add examples or links to documentation for configuring shared disks in Linux-based clusters.
  • Clarify whether the listed limitations apply only to Windows environments or also to Linux, and provide parity in guidance.
  • Ensure that both Windows and Linux scenarios are addressed in all relevant sections.
GitHub Create Pull Request
Virtual Machines Use infrastructure automation tools ...articles/virtual-machines/infrastructure-automation.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 generally covers both Linux and Windows automation tools, but there are several instances of Windows bias: Windows examples and tools (e.g., PowerShell DSC, Chef on Windows, Puppet on Windows) are sometimes mentioned first or exclusively, while Linux equivalents are missing or less emphasized. Some sections provide only Windows-focused links or examples, and Windows-specific tooling (PowerShell, Windows templates) is highlighted before Linux alternatives.
Recommendations
  • Ensure every Windows example or link has a Linux equivalent, especially in sections like Chef and Puppet where only Windows instructions are provided.
  • Present Linux and Windows examples side-by-side or alternate which is shown first to avoid 'windows_first' bias.
  • Expand the Chef section to include Linux installation and VM creation guides, not just Windows.
  • For Puppet, include links to Linux installation and usage, not just Windows.
  • Where PowerShell is referenced, also mention Bash/CLI alternatives for Linux users.
  • Review all 'Learn how to' lists to ensure parity between Linux and Windows instructions.
GitHub Create Pull Request
Virtual Machines Prepare Linux for imaging ...ticles/virtual-machines/linux/create-upload-generic.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page is focused on Linux preparation for Azure imaging, but it exhibits some Windows bias in the sections discussing VHD conversion and resizing. Windows tools (Hyper-V Manager, PowerShell cmdlets like Convert-VHD and Resize-VHD) are mentioned first and in detail, while Linux alternatives (qemu-img, vbox-manage) are referenced secondarily or as workarounds. The initial guidance for disk conversion and resizing assumes access to Windows environments before suggesting Linux tools. However, the majority of the technical instructions and examples are Linux-centric.
Recommendations
  • Present Linux tools (qemu-img, vbox-manage) alongside or before Windows tools when discussing VHD conversion and resizing.
  • Provide explicit, step-by-step Linux examples for all disk operations, not just as alternatives.
  • Clarify that all required steps can be completed on Linux without needing Windows or Hyper-V.
  • Add troubleshooting notes for Linux tools (e.g., qemu-img bugs, compatibility issues) in parity with Windows tool notes.
  • Consider a dedicated section for Linux-only workflows to reinforce parity.
GitHub Create Pull Request
Virtual Machines Create and upload a CentOS-based Linux VHD ...rticles/virtual-machines/linux/create-upload-centos.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 exhibits Windows bias primarily by referencing Hyper-V (a Windows virtualization tool) as the main method for creating and managing CentOS VHDs. Instructions for VM management (such as shutting down or connecting to the VM) are given using Hyper-V Manager, with no equivalent guidance for Linux-native virtualization platforms like KVM, QEMU, or VirtualBox. The conversion of disk formats is described using Hyper-V Manager or Windows PowerShell (`convert-vhd`), while Linux alternatives (e.g., qemu-img) are not mentioned. This creates friction for Linux/macOS users who may not have access to Hyper-V or Windows tools.
Recommendations
  • Provide parallel instructions for common Linux virtualization platforms (KVM, QEMU, VirtualBox), including how to create, manage, and shut down VMs.
  • Include Linux-native commands for converting disk formats (e.g., using `qemu-img` to convert raw to fixed VHD).
  • Mention macOS-compatible tools and workflows where relevant.
  • Present Windows and Linux options side-by-side, or clearly indicate alternatives for non-Windows users.
  • Clarify that Hyper-V is one option among several, and link to resources for Linux-based virtualization.
GitHub Create Pull Request
Virtual Machines Create and upload an Ubuntu Linux VHD in Azure ...rticles/virtual-machines/linux/create-upload-ubuntu.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 for creating and uploading an Ubuntu Linux VHD in Azure exhibits a moderate Windows bias. Hyper-V (a Windows-only virtualization solution) is presented as the primary example for creating VHDs, with links to Windows documentation and PowerShell cmdlets (Convert-VHD) for disk conversion. There are no equivalent instructions or references for Linux-based tools (such as qemu-img, VirtualBox, or KVM) for creating or converting VHDs, nor are Linux workflows described for these steps. Windows tools and procedures are mentioned first and exclusively in critical steps, which may create friction for Linux/macOS users.
Recommendations
  • Include instructions and examples for creating and converting VHDs using Linux-native tools (e.g., qemu-img, VBoxManage, KVM).
  • Provide links to Linux documentation for virtualization and disk conversion.
  • Present Linux and Windows options side-by-side, or prioritize Linux tools given the Ubuntu/Linux focus of the guide.
  • Clarify that Hyper-V is just one option and explicitly mention alternatives for non-Windows users.
GitHub Create Pull Request
Virtual Machines Creating and configuring a key vault for Azure Disk Encryption ...es/virtual-machines/linux/disk-encryption-key-vault.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 provides both Azure CLI and PowerShell examples and resources, but PowerShell (a Windows-centric tool) is featured equally alongside CLI, despite the article's Linux focus. PowerShell scripts and quickstarts are referenced as primary resources, and PowerShell authentication is described in detail. The CLI and PowerShell scripts are listed together, but PowerShell is not deprioritized or marked as Windows-only, which may confuse Linux users. There is no explicit omission of Linux examples, but the parity between CLI and PowerShell may create friction for Linux users unfamiliar with PowerShell.
Recommendations
  • Prioritize Azure CLI examples and quickstarts for Linux-focused documentation, listing CLI before PowerShell.
  • Clearly indicate that PowerShell is primarily a Windows tool and may require additional setup on Linux.
  • Add explicit notes or sections for Linux users, recommending Azure CLI as the preferred tool.
  • Where PowerShell scripts are referenced, provide equivalent Bash/CLI scripts or clarify their platform compatibility.
  • Review and update links to ensure Linux users are directed to CLI resources first.
GitHub Create Pull Request
Virtual Machines Azure Disk Encryption with Microsoft Entra App Linux IaaS VMs (previous release) ...es/virtual-machines/linux/disk-encryption-linux-aad.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 extensive PowerShell examples and references to Windows-centric tools (such as PowerShell cmdlets and Windows-specific flags), even in sections focused on Linux VMs. PowerShell is presented as a primary method for disk encryption tasks, sometimes before or alongside Azure CLI and ARM templates. There are references to Windows-specific options (e.g., '-Windows' flag in Set-AzVMOSDisk), and some steps (such as disabling encryption) mention Windows VMs in Linux contexts. Linux-native command-line examples (bash, shell scripts) are minimal or absent, and the use of PowerShell for Linux VM management may not be natural for Linux administrators.
Recommendations
  • Provide bash/shell script examples for Linux VM management tasks alongside PowerShell and CLI.
  • Remove or clarify Windows-specific flags and references in Linux-focused sections.
  • Ensure Linux-native tooling (e.g., bash, cloud-init, Linux utilities) is covered where appropriate.
  • Present Azure CLI and ARM template methods before PowerShell in Linux documentation, as CLI is more cross-platform.
  • Review and correct any references to Windows VMs in Linux-specific instructions.
  • Highlight that PowerShell Core is cross-platform, but also offer alternatives for users who prefer native Linux tools.
GitHub Create Pull Request
Virtual Machines Azure Disk Encryption with Microsoft Entra app prerequisites (previous release) ...virtual-machines/linux/disk-encryption-overview-aad.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, while focused on Azure Disk Encryption for Linux VMs, contains notable Windows bias. Windows-specific tools (BitLocker, registry edits, Group Policy) are described in detail, including example registry changes and policy settings, but there are no equivalent Linux-specific examples or troubleshooting steps. Windows instructions are presented first and in more depth, while Linux-specific prerequisites and configuration details are largely omitted or deferred to other linked articles.
Recommendations
  • Add Linux-specific troubleshooting steps and configuration examples, such as SELinux/AppArmor considerations, disk encryption tools (e.g., dm-crypt/LUKS), and relevant system settings.
  • Provide Linux command-line examples for network configuration and key vault connectivity (e.g., using curl, iptables, or firewall-cmd).
  • Include parity for Linux in the 'Group Policy' section by discussing relevant Linux access control or security policy mechanisms.
  • Ensure that Linux instructions are presented with equal prominence and detail as Windows instructions, especially in sections about prerequisites and common issues.
  • Where Windows registry or Group Policy changes are shown, provide analogous Linux configuration steps or explicitly state when they are not applicable.
GitHub Create Pull Request
Virtual Machines Azure Disk Encryption sample scripts ...rtual-machines/linux/disk-encryption-sample-scripts.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 is for Azure Disk Encryption on Linux VMs, but almost all automation and scripting examples use PowerShell cmdlets and scripts, which are Windows-centric. Key operations such as listing encrypted VMs, uploading VHDs, and managing secrets in Key Vault are only shown with PowerShell, with no Bash, Azure CLI, or Linux-native alternatives. Even when Linux VM configuration is described, the upload and management steps revert to PowerShell. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer native tools.
Recommendations
  • Provide equivalent Azure CLI (az) commands for all PowerShell examples, especially for listing encrypted VMs, uploading VHDs, and managing Key Vault secrets.
  • Include Bash script examples for common tasks, such as preparing and uploading encrypted VHDs.
  • Mention and demonstrate cross-platform tools (e.g., azcopy for VHD uploads) where possible.
  • Order examples so that Linux-native methods (CLI/Bash) are shown before or alongside PowerShell.
  • Clarify which steps require PowerShell and suggest alternatives for Linux/macOS users.
GitHub Create Pull Request
Virtual Machines Verify encryption status for Linux - Azure Disk Encryption ...tual-machines/linux/how-to-verify-encryption-status.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 PowerShell and Azure CLI examples for verifying disk encryption status on Linux VMs, but PowerShell instructions are given before Azure CLI, despite CLI being more native to Linux. The PowerShell section is more extensive, with detailed examples and screenshots, while the CLI section, though comprehensive, comes after. There is no evidence of exclusive use of Windows tools, and Linux OS-level commands are included at the end. However, the ordering and emphasis may create friction for Linux users who are less likely to use PowerShell.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is more commonly used on Linux.
  • Clearly indicate that PowerShell commands are optional and primarily for users who have installed PowerShell on Linux.
  • Expand Linux OS-level command examples (e.g., lsblk, cryptsetup) to match the detail given to PowerShell/CLI sections.
  • Add a summary table comparing all methods, highlighting which are native to Linux.
  • Consider removing or de-emphasizing PowerShell for Linux-specific documentation unless there is a strong use case.
GitHub Create Pull Request
Virtual Machines How to Connect to the Azure Image Builder build VM ...al-machines/linux/image-builder-connect-to-build-vm.md
Medium 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 moderate Windows bias. Windows tools and terminology (RDP, WinRM, Reset Password blade) are mentioned first or exclusively in several sections. Examples and links for connecting to Windows VMs are often given before Linux equivalents, and some instructions (such as password reset) reference Windows-centric UI without clarifying Linux differences. Linux-specific connection methods and troubleshooting steps are less detailed or referenced after Windows options.
Recommendations
  • Provide explicit Linux examples and instructions alongside Windows ones, especially for credential management and connection steps.
  • Clarify differences in the Azure portal UI for Linux VMs (e.g., password reset process, SSH key management).
  • Ensure that links to Linux documentation are presented with equal prominence and order as Windows links.
  • Include Linux-specific troubleshooting tips (e.g., SSH connectivity, cloud-init logs) where relevant.
  • Avoid using Windows terminology (e.g., RDP, WinRM) as the default; always mention SSH for Linux first or equally.
GitHub Create Pull Request
Virtual Machines Azure VM Image Builder service DevOps task (preview) ...es/virtual-machines/linux/image-builder-devops-task.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 demonstrates a moderate Windows bias. Windows-specific tools (PowerShell) and terminology are frequently mentioned, often before or more prominently than Linux equivalents. Windows examples (e.g., PowerShell commands, directory paths) are shown first in several sections, and some customization features (like Windows Update) are described only for Windows. Linux examples are present but sometimes less detailed or appear after Windows instructions. There are also references to Windows-only limitations (e.g., lack of support for Windows Restart), but Linux workarounds are not always equally emphasized.
Recommendations
  • Present Linux and Windows examples side-by-side or alternate which comes first to avoid Windows-first ordering.
  • Expand Linux-specific instructions and examples to match the detail given for Windows, especially in customization and artifact handling.
  • Clearly indicate when features are Windows-only and provide Linux alternatives or workarounds where possible.
  • Include more bash or shell script examples for Linux users, especially in sections where PowerShell is heavily featured.
  • Avoid using Windows terminology (e.g., 'C:\buildArtifacts') without immediately providing the Linux equivalent.
GitHub Create Pull Request
Virtual Machines Troubleshoot Azure VM Image Builder ...s/virtual-machines/linux/image-builder-troubleshoot.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 demonstrates a moderate Windows bias. Windows tools (PowerShell, WinRM, Sysprep) are frequently mentioned, often with detailed examples and troubleshooting steps. PowerShell commands are shown alongside Azure CLI, but Windows-specific patterns (e.g., Sysprep, Windows Update, restart customizers) receive more attention and troubleshooting coverage. Linux equivalents (waagent, SSH, shell scripting) are present but less detailed, and sometimes appear after Windows instructions. Some troubleshooting sections and examples are Windows-centric, with Linux guidance either brief or missing.
Recommendations
  • Ensure Linux troubleshooting steps are as detailed as Windows ones, especially for common errors and customizations.
  • Provide Linux-first or parallel examples for all CLI and scripting instructions, not just PowerShell.
  • Expand Linux-specific error messages and solutions (e.g., waagent failures, SSH connectivity, Linux file permissions) to match the coverage of Windows topics.
  • Balance the order of presentation so Linux and Windows instructions appear together or alternate, rather than Windows-first.
  • Include more Linux shell script samples and troubleshooting logs, especially for customization and deprovisioning steps.
  • Reference Linux-specific documentation and support resources as prominently as Windows ones.
GitHub Create Pull Request
Virtual Machines Run scripts in a Linux VM in Azure using managed Run Commands ...articles/virtual-machines/linux/run-command-managed.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 page, while focused on Linux VMs, contains several instances of Windows bias. PowerShell examples and tooling are heavily featured, with many advanced scenarios (such as output streaming, parameter passing, and SAS token generation) described only with PowerShell cmdlets and Windows-centric tools. REST and ARM template examples use PowerShell scripts as sample payloads, and some notes reference Windows-specific behaviors before Linux equivalents. There are missing Linux CLI or bash-native examples for advanced features, and PowerShell is often presented before or instead of Linux alternatives.
Recommendations
  • Provide equivalent Azure CLI or bash script examples for all advanced scenarios currently shown only in PowerShell (e.g., output streaming, parameter passing, SAS token generation).
  • Where REST or ARM template payloads use PowerShell scripts, also show examples with bash scripts.
  • Clarify when instructions or notes are Windows-specific and provide Linux-specific guidance in parallel.
  • Ensure Linux tools and patterns (e.g., az CLI, bash scripting) are presented before or alongside Windows/PowerShell examples, especially in Linux-focused documentation.
  • Add instructions for generating SAS tokens using Azure CLI or portal for Linux users.
GitHub Create Pull Request
Virtual Machines Create and upload a Red Hat Enterprise Linux VHD for use in Azure ...les/virtual-machines/linux/redhat-create-upload-vhd.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 moderate Windows bias. The prerequisites and initial instructions reference Hyper-V Manager and link to Windows documentation first, with Hyper-V-specific steps appearing before KVM, VMware, and Kickstart. Windows/Hyper-V tools and patterns (e.g., Hyper-V Manager, convert-vhd cmdlet) are mentioned before Linux alternatives (qemu-img). However, the page does provide detailed Linux-centric instructions for KVM, VMware, and Kickstart, and includes Linux tooling for image conversion and configuration.
Recommendations
  • In the prerequisites, mention KVM, VMware, and Kickstart options alongside Hyper-V, with links to their respective documentation.
  • Provide Linux-first instructions or parallel instructions for common tasks (e.g., converting disk formats) rather than referencing Windows/Hyper-V tools first.
  • Where possible, avoid assuming Hyper-V as the default workflow; present all supported hypervisors equally.
  • Add explicit guidance for Linux/macOS users in sections that currently reference Windows tools or documentation.
  • Ensure that all steps (including image conversion and VM creation) have clear Linux/macOS equivalents and links.
GitHub Create Pull Request
Virtual Machines Run scripts in an Azure Linux VM ...n/articles/virtual-machines/linux/run-scripts-in-vm.md
Medium 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 is focused on Linux VMs but repeatedly references Windows tools and patterns, such as PowerShell and Windows-specific installation instructions. Examples and descriptions often mention PowerShell scripts and Windows capabilities before or alongside Linux equivalents, but do not provide Linux-specific examples or highlight Linux-native tools. The Hybrid Runbook Worker section is especially Windows-centric, referencing PowerShell and requiring a manual installation link that points to Windows instructions, with no Linux installation guidance.
Recommendations
  • Provide explicit Linux script examples (e.g., Bash, Python) for each feature, especially for Hybrid Runbook Worker.
  • Ensure installation instructions for Hybrid Runbook Worker include Linux steps and links.
  • List Linux-native tools and patterns first in sections focused on Linux VMs.
  • Clarify which features are Linux-compatible and provide parity in documentation structure and detail.
  • Reduce emphasis on PowerShell in Linux contexts; highlight Bash and other Linux scripting languages.
GitHub Create Pull Request
Virtual Machines Create shared Azure Linux VM images using the portal ...rticles/virtual-machines/linux/shared-images-portal.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 focused on Linux VM images and uses the Azure Portal for all steps, which is cross-platform. However, in the 'Before you begin' section, it references a PowerShell-based tutorial for creating a managed image and links to a snapshot guide under a Windows directory, without mentioning or linking to equivalent Linux CLI or Bash instructions. No Linux-specific command-line examples are provided, and Windows/PowerShell resources are referenced first and exclusively.
Recommendations
  • Add links to Linux-specific guides for creating managed images and snapshots, such as those using the Azure CLI or Bash.
  • Reference Linux CLI examples alongside or before PowerShell/Windows examples when discussing prerequisites.
  • Ensure that all referenced tutorials and guides have Linux equivalents and are clearly labeled.
  • Consider including a short section on how to perform prerequisite steps using Linux tools (e.g., Azure CLI) directly in the documentation.
GitHub Create Pull Request
Virtual Machines Advanced Configuration for MSP ...s/metadata-security-protocol/advanced-configuration.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 a Windows-specific example for process identity matching (WinPA) with Windows paths and process names, but does not offer a Linux equivalent. Windows process metadata (exePath, processName, userName) is shown in detail, while Linux examples are limited to a single earlier snippet and not referenced in the main schema expansion. Windows tools and conventions (e.g., C:\Windows paths, SYSTEM user) are mentioned exclusively in the WireServer example, and Windows examples are presented before or instead of Linux ones.
Recommendations
  • Add equivalent Linux/macOS examples for process identity matching, such as using /usr/bin/nginx, processName: nginx, userName: root or www-data.
  • Ensure schema expansions include both Windows and Linux/macOS scenarios side-by-side.
  • Explicitly mention how to obtain process metadata on Linux/macOS (e.g., using ps, /proc, or systemd conventions).
  • Avoid using Windows paths and usernames exclusively; provide cross-platform context.
  • If Windows-specific tools or patterns are referenced, provide Linux/macOS alternatives.
GitHub Create Pull Request
Virtual Machines Maintenance Configurations for Azure Virtual Machines using Bicep ...s/virtual-machines/maintenance-configurations-bicep.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 provides only a Windows/Powershell example for Bicep template deployment, using Windows-style paths (e.g., .\ds.bicep) and does not mention or show Linux/macOS CLI equivalents. There is no explicit Linux/macOS example for running the az deployment command, nor any notes about cross-platform usage. The documentation implicitly assumes a Windows environment for command execution, which may cause confusion or friction for Linux/macOS users.
Recommendations
  • Provide both Windows and Linux/macOS CLI examples for az deployment group create, using appropriate path separators (e.g., ./ds.bicep for Linux/macOS).
  • Add a note clarifying that the Azure CLI works cross-platform and that path syntax differs between Windows (\) and Linux/macOS (/).
  • Consider listing Linux/macOS examples first or side-by-side with Windows examples to reinforce parity.
  • Explicitly mention that all Bicep templates and Azure CLI commands are platform-agnostic, and provide troubleshooting tips for common Linux/macOS issues (e.g., file permissions, shell differences).
GitHub Create Pull Request
Virtual Machines Manage Virtual Machine restore points ...ain/articles/virtual-machines/manage-restore-points.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 exclusively provides Azure PowerShell examples for all command-line operations, with no mention of Linux/macOS alternatives such as Azure CLI, Bash, or REST API usage. Windows-centric tools and syntax are used throughout, and no Linux-specific guidance or parity is offered. This creates friction for users on non-Windows platforms who may not have PowerShell installed or prefer native Linux tools.
Recommendations
  • Add equivalent Azure CLI examples for each PowerShell command.
  • Include Bash scripting examples where appropriate.
  • Explicitly mention that PowerShell is cross-platform, but clarify installation steps for Linux/macOS users.
  • Provide REST API request examples for advanced users.
  • Ensure that Linux/macOS users are not required to install PowerShell unless necessary.
GitHub Create Pull Request
Virtual Machines Overview of Azure Disk Storage ...in/articles/virtual-machines/managed-disks-overview.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 generally covers Azure managed disks for both Linux and Windows VMs, but there are several instances of Windows bias. Windows terminology, tools, and links are often presented first or exclusively, such as references to Sysprep, MBR/GPT partitioning with Windows links, and PowerShell articles. Some sections, like image creation and partitioning, link only to Windows-specific resources or mention Windows tools before Linux equivalents. Linux examples and links are present but sometimes secondary or missing.
Recommendations
  • Ensure all example links (e.g., image creation, partitioning) include both Windows and Linux equivalents, or provide a neutral overview page.
  • When mentioning tools or procedures (e.g., Sysprep, MBR/GPT), include Linux alternatives (e.g., cloud-init, parted, gdisk) and link to relevant Linux documentation.
  • Present Linux and Windows examples side-by-side or in parallel, rather than listing Windows first or exclusively.
  • Review all cross-references to ensure Linux parity, especially in deep links and how-to guides.
  • Clarify terminology to be OS-neutral where possible (e.g., avoid drive letter references without Linux device path equivalents).
GitHub Create Pull Request
Virtual Machines Frequently Asked Questions About MSP ...les/virtual-machines/metadata-security-protocol/faq.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 displays a Windows-first bias in its explanation of provisioning and agent installation. It references the Windows philosophy as the default model and does not provide Linux-specific examples or guidance for checking MSP status or installing the Guest Proxy Agent (GPA). Windows tools and patterns are mentioned as the baseline, while Linux alternatives are discussed only in terms of limitations. There are no Linux command-line examples or instructions, and the guidance for Linux users is limited to stating what is not possible.
Recommendations
  • Provide explicit Linux command-line examples (e.g., using curl, jq, or Azure CLI) for checking MSP status and component health.
  • Offer step-by-step instructions for installing and enabling GPA on Linux VMs, including supported distributions and package managers.
  • Discuss Linux-specific patterns for VM provisioning and agent management, and clarify any differences from Windows workflows.
  • Ensure that Linux guidance is presented alongside Windows guidance, not only as an exception or limitation.
  • Include troubleshooting steps and common issues for Linux users.
GitHub Create Pull Request
Virtual Machines Troubleshoot MSP ...hines/metadata-security-protocol/troubleshoot-guide.md
Medium 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 exhibits a moderate Windows bias. Windows troubleshooting steps and service names are often presented first, and Windows-specific tools (such as 'sc query' and service names like 'eBPFCore', 'NetEbpfExt') are described in detail. In some sections, Linux instructions are less detailed or missing, and Windows command examples are shown without Linux equivalents. Linux users may need to infer or search for analogous commands and troubleshooting steps.
Recommendations
  • Provide Linux command equivalents for all Windows commands (e.g., replace 'sc query' with 'systemctl status' or 'lsmod' for Linux).
  • Present Linux and Windows troubleshooting steps in parallel, or alternate which OS is shown first.
  • Expand Linux troubleshooting sections to match the detail provided for Windows, including explicit error messages, log file locations, and service management commands.
  • Include Linux-specific examples for checking service status, kernel modules, and log analysis.
  • Clarify any OS-specific prerequisites and installation steps, and provide links to relevant Linux documentation.
GitHub Create Pull Request
Virtual Machines Monitoring data reference for Azure Virtual Machines ...main/articles/virtual-machines/monitor-vm-reference.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 moderate Windows bias. Several log tables and data collection methods are Windows-specific (e.g., Windows Event Log, IIS logs, Windows DNS servers, Windows Security Events, Windows Firewall), and these are described before or without equivalent Linux examples. While Linux is mentioned (e.g., Syslog, Linux Daemons), Windows tools and terminology appear more frequently and are often listed first. Some data collection methods and log tables are exclusively for Windows, with no Linux alternatives or examples provided.
Recommendations
  • Add equivalent Linux examples and references for each Windows-specific log table and data collection method (e.g., provide examples for collecting Linux audit logs, firewall logs, and DNS events).
  • Ensure Linux and macOS terminology and tools are mentioned alongside Windows tools, not just as secondary notes.
  • Where possible, reorder tables and examples so that Linux and Windows are presented with equal prominence.
  • Include explicit guidance for Linux/macOS users in sections that currently only mention Windows tools or workflows.
GitHub Create Pull Request
Virtual Machines Convert Audit Logs to an Allowlist ...ecurity-protocol/other-examples/audit-logs-to-rules.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 page exhibits a notable Windows bias. Windows-specific tools (PowerShell, .exe utilities) are featured prominently and in greater detail than Linux equivalents. Windows examples and terminology (e.g., PowerShell commands, .exe files, Windows paths) are presented first and in more depth, while Linux instructions are less detailed or absent (e.g., no Bash or shell scripting examples for Linux users, no mention of Linux-native automation tools). The allowlist generator tool is only available as a Windows executable, with no Linux alternative provided. Sample identities and rules are overwhelmingly Windows-centric, with little coverage of Linux processes or users.
Recommendations
  • Provide Linux-native examples for all major steps, including shell (Bash) or Python scripts for resource creation and management.
  • Offer a cross-platform or Linux-compatible version of the allowlist generator tool, or document manual log parsing methods for Linux.
  • Balance sample identities and rules to include Linux processes and users, not just Windows executables.
  • Present CLI and ARM template methods before or alongside PowerShell, emphasizing cross-platform parity.
  • Explicitly note any limitations or workarounds for Linux users where Windows-only tooling is referenced.
GitHub Create Pull Request
Virtual Machines SCSI to NVMe for Linux VMs ...docs/blob/main/articles/virtual-machines/nvme-linux.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 page for converting SCSI to NVMe for Linux VMs on Azure exhibits a notable Windows bias. Most operational steps, examples, and scripts are presented using PowerShell, a Windows-centric tool, even though the target VMs are running Linux. Instructions for downloading and running the migration script are given exclusively in PowerShell, and PowerShell commands are shown before any Linux-native alternatives. There is minimal coverage of Linux-native CLI workflows for Azure management, and no Bash/Azure CLI script examples are provided for the migration process itself.
Recommendations
  • Provide equivalent Bash/Azure CLI examples for all PowerShell commands, especially for checking VM controller type, downloading scripts, and running migration steps.
  • Document how to run the migration script natively on Linux (e.g., via Azure CLI, Bash, or Python), including prerequisites and environment setup.
  • Clarify whether the migration script can be executed directly from Linux environments (local or Cloud Shell) and provide instructions for doing so.
  • Reorder examples so that Linux-native tools (Azure CLI, Bash) are presented first or alongside PowerShell.
  • Add troubleshooting steps and verification commands using Linux tools (e.g., systemctl, journalctl, dmesg) in addition to PowerShell/Azure Portal.
GitHub Create Pull Request
Virtual Machines Overview of virtual machines in Azure ...e-docs/blob/main/articles/virtual-machines/overview.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 generally aims for cross-platform coverage, but there are several instances of Windows bias. PowerShell is frequently mentioned and often listed before Azure CLI, which is more commonly used on Linux/macOS. Windows tools and terminology (e.g., PowerShell cmdlets) are referenced in tables and examples, sometimes before or without equivalent Linux commands. Some sections provide only Windows-centric instructions or examples, and the order of presentation often favors Windows tools first, creating friction for Linux/macOS users.
Recommendations
  • Ensure that Azure CLI examples are presented before or alongside PowerShell examples, as CLI is cross-platform.
  • Provide explicit Linux/macOS command examples where only PowerShell is shown.
  • Balance tables and lists to show both Windows and Linux tools, or clarify which tools are recommended for each OS.
  • Add more Linux-specific management and troubleshooting examples, especially in sections where only Windows tools are referenced.
  • Review ordering of examples and instructions to avoid consistently listing Windows tools first.
GitHub Create Pull Request
Virtual Machines Tutorial - Move Azure single instance Virtual Machines from regional to zonal availability zones ...achines/move-virtual-machines-regional-zonal-portal.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 page demonstrates a Windows bias by referencing Windows-specific documentation (e.g., PowerShell) for checking VM SKU availability and for next steps, without mentioning or providing equivalent Linux/macOS CLI examples or guidance. The 'Next steps' section links only to a PowerShell/CLI page, but the main tutorial does not show any command-line steps, and the only explicit example for checking VM SKU availability links to a Windows/PowerShell page. There are no Linux/macOS-specific instructions, nor is the Azure CLI (cross-platform) given equal prominence.
Recommendations
  • Include explicit Azure CLI examples and links for all steps where PowerShell is referenced, especially for checking VM SKU availability and performing the move.
  • In the prerequisites and next steps, mention both PowerShell and Azure CLI (with links to respective documentation) to ensure parity for Linux/macOS users.
  • If screenshots or UI steps differ between platforms, clarify any differences or provide platform-agnostic instructions.
  • Avoid referencing Windows/PowerShell documentation exclusively; always provide cross-platform alternatives.
GitHub Create Pull Request
Virtual Machines Customer intent: "As an IT administrator managing Azure IaaS virtual machines, I want to implement a backup and disaster recovery plan for unmanaged disks, so that I can ensure data durability and high availability in the event of localized or regional failures." ...al-machines/page-blobs-backup-and-disaster-recovery.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 moderate Windows bias. Windows-specific tools (e.g., PowerShell, Volume Shadow Service) are mentioned first or exclusively in several sections, and automation examples reference PowerShell before Azure CLI. Application-consistent backup details are richer for Windows (Volume Shadow Service) than Linux (fsfreeze, file-consistent only). Some references and links point to Windows-specific guides, while Linux equivalents are mentioned later or less prominently. There are few explicit Linux command examples, and Linux backup nuances are less detailed.
Recommendations
  • Provide Linux-first or parallel examples for backup and restore automation, using Azure CLI and shell scripts alongside PowerShell.
  • Expand on Linux application-consistent backup strategies, including tools like LVM snapshots, pre/post scripts, or third-party solutions.
  • Ensure all references to backup and restore guides include both Windows and Linux links, not just Windows-specific ones.
  • Add explicit Linux command-line examples for snapshot creation, copying, and recovery (e.g., using Azure CLI, shell commands).
  • Clarify differences in backup consistency between Windows and Linux, and offer best practices for Linux workloads.
GitHub Create Pull Request
Virtual Machines Azure premium storage: Design for high performance ...ticles/virtual-machines/premium-storage-performance.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ sqlserver_heavy
Summary
The documentation page demonstrates moderate Windows bias. Windows tools (PerfMon, Storage Spaces, PowerShell) are mentioned first or exclusively in several sections, and SQL Server (a Windows-centric workload) is used as the primary example throughout. Linux equivalents (iostat, MDADM) are mentioned, but often after Windows tools, and with less detail. The disk striping section provides more configuration detail for Windows (columns, PowerShell) than for Linux (just a link). Benchmarking and performance measurement tools are listed for both platforms, but Windows examples and terminology are more prominent.
Recommendations
  • Provide Linux examples and tools with equal detail and prominence as Windows (e.g., show MDADM configuration steps inline, not just as a link).
  • Use a more balanced set of workload examples (e.g., include Oracle, MySQL, or PostgreSQL on Linux alongside SQL Server).
  • List Linux tools and commands before or alongside Windows tools in tables and explanations.
  • Add more detail on Linux-specific performance tuning (e.g., kernel parameters, file system choices, driver updates).
  • Ensure that all configuration steps (e.g., disk striping, benchmarking) are described for both platforms, not just referenced.
  • Include sample commands and output for Linux tools (iostat, vmstat, MDADM) similar to the PerfMon and PowerShell examples.
GitHub Create Pull Request
Virtual Machines Troubleshoot restore point failures ...cles/virtual-machines/restore-point-troubleshooting.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ powershell_heavy
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific tools (services.msc, Event Viewer, COM+, VSS, Visual C++ Redistributable) are referenced frequently and often without Linux equivalents or alternatives. Troubleshooting steps and error resolutions for Windows are more detailed, with explicit instructions and tool usage, while Linux guidance is more generic and less tool-specific. Windows patterns (such as PowerShell, Control Panel, and .NET requirements) are mentioned before or instead of Linux alternatives. Some sections (e.g., COM+ and VSS troubleshooting) are Windows-only, with no Linux context or equivalent troubleshooting advice.
Recommendations
  • Add equivalent Linux troubleshooting steps for sections that currently only describe Windows tools (e.g., COM+, VSS, Visual C++ Redistributable).
  • Provide Linux-first or side-by-side examples for common operations, rather than listing Windows steps first.
  • Include Linux-specific error codes and troubleshooting for extension failures, disk issues, and agent problems.
  • Reference Linux tools (e.g., systemctl, journalctl, log file locations) where Windows tools (services.msc, Event Viewer) are mentioned.
  • Clarify which troubleshooting steps are OS-specific and provide parity in detail and actionable guidance for both platforms.
GitHub Create Pull Request
Virtual Machines Share Resources in Azure Compute Gallery ...s/blob/main/articles/virtual-machines/share-gallery.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides examples for Azure Portal, Azure CLI, and PowerShell. While CLI examples are cross-platform, PowerShell is Windows-centric and is presented as a primary automation option. The order of examples places PowerShell before any Linux-specific shell scripting, and there are no Bash or Linux shell examples, nor is there mention of Linux-native tools or patterns. This may create friction for Linux/macOS users who do not use PowerShell.
Recommendations
  • Add Bash shell examples using Azure CLI to explicitly demonstrate Linux/macOS workflows.
  • Clarify that Azure CLI commands work on Linux/macOS and Windows, and provide sample shell scripts for Linux users.
  • Reorder examples so that cross-platform CLI instructions are presented before PowerShell.
  • Mention that PowerShell Core is available on Linux/macOS, but also provide native Bash alternatives for common tasks.
GitHub Create Pull Request
Virtual Machines Share Gallery Images Across Tenants by Using an App Registration ...icles/virtual-machines/share-using-app-registration.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 both Azure CLI and PowerShell examples for sharing gallery images across tenants, but the PowerShell section is significantly more detailed, using Windows-centric tools and patterns (e.g., New-AzNetworkSecurityRuleConfig for RDP, Set-AzVMOperatingSystem -Windows, Get-Credential for username/password). The PowerShell example is much longer and more comprehensive than the CLI example, which is brief and omits networking setup. Windows tools and concepts (RDP, Windows OS config) are prominent, and the PowerShell tab appears after the CLI tab, but the CLI example is minimal.
Recommendations
  • Expand the Azure CLI example to include networking setup and VM configuration steps, matching the detail of the PowerShell example.
  • Provide Linux-focused examples, such as configuring SSH access, Linux OS settings, and security rules for SSH (port 22) instead of RDP (port 3389).
  • Include explicit instructions for Linux/macOS users, such as using SSH keys and Linux-friendly credential management.
  • Balance the detail and complexity of CLI and PowerShell sections so Linux users are not disadvantaged.
  • Avoid Windows-specific terminology or provide Linux alternatives in parallel.
GitHub Create Pull Request
Virtual Machines Share VM images in a compute gallery ...in/articles/virtual-machines/shared-image-galleries.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 several signs of Windows bias. PowerShell examples are provided alongside CLI, but references to Windows tools (e.g., Sysprep) and Windows-specific documentation links are more prominent and often appear before Linux equivalents. In some cases, Linux instructions or links are present but less visible or secondary. There are also references to Windows upload guides before Linux ones, and some examples (e.g., image creation from specialized disks) link only to Windows-specific pages. Overall, Linux parity is present but not consistently prioritized or equally represented.
Recommendations
  • Ensure that Linux and Windows examples are presented side-by-side or in parallel tabs, rather than Windows first.
  • When referencing external guides (e.g., uploading VHDs, creating specialized images), always provide both Linux and Windows links together.
  • Expand CLI examples to include Linux-specific scenarios or commands where relevant, especially in troubleshooting and FAQs.
  • Avoid referencing Windows tools (like Sysprep) before Linux equivalents (like waagent); mention both together.
  • Review all linked pages to ensure Linux documentation is equally detailed and accessible.
GitHub Create Pull Request
Virtual Machines Resize a virtual machine ...blob/main/articles/virtual-machines/sizes/resize-vm.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 page exhibits a moderate Windows bias. PowerShell is given a prominent, detailed section with multiple scripts and explanations, while Linux-native tooling (e.g., Bash, shell) is not mentioned outside of Azure CLI. The Terraform example references Windows VM quickstart, and the CLI examples use Bash syntax but do not explicitly address Linux-specific considerations. Windows terminology and tools (PowerShell, Windows VM resource blocks) are introduced before Linux equivalents, and the workaround for temp disk migration links to a Windows-specific article. There are no explicit Linux shell or macOS Terminal examples, and Linux users may need to infer steps from the CLI section.
Recommendations
  • Add explicit Linux/macOS shell examples for resizing VMs using Azure CLI, including notes on environment setup and differences (e.g., quoting, variable syntax).
  • Provide parity in Terraform examples by referencing both Windows and Linux VM quickstarts, or showing a generic example.
  • Ensure workaround and migration links include Linux VM scenarios, not just Windows.
  • Balance PowerShell and CLI coverage, and introduce CLI examples before or alongside PowerShell to avoid Windows-first impression.
  • Clarify that Azure CLI commands work cross-platform and highlight any OS-specific caveats.
GitHub Create Pull Request
Virtual Machines Av1-series retirement ...ual-machines/sizes/retirement/av1-series-retirement.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation provides detailed instructions for resizing VMs using the Azure portal and Azure PowerShell, but omits examples for Azure CLI (which is cross-platform and preferred by many Linux/macOS users). The PowerShell example is given, but no equivalent Azure CLI or Bash example is shown. The ordering also places Windows-centric tools (portal, PowerShell) before mentioning CLI, despite CLI being referenced in the introductory sentence.
Recommendations
  • Add an Azure CLI example for resizing VMs, including listing available sizes and performing the resize.
  • Explicitly mention that Azure CLI works on Linux/macOS and Windows.
  • Consider reordering the examples so that CLI instructions are presented before or alongside PowerShell, or at least equally.
  • Where possible, provide Bash script snippets for common tasks to further support Linux users.
GitHub Create Pull Request
Virtual Machines DCsv2-series retirement ...l-machines/sizes/retirement/dcsv2-series-retirement.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 demonstrates a moderate Windows bias. In the migration steps, examples are given for the Azure portal (which is platform-agnostic but often associated with Windows users), followed by Azure PowerShell, and then Azure CLI. The PowerShell example is detailed and comes before the CLI example, and the CLI authentication example incorrectly uses PowerShell syntax (variables with $), which may confuse Linux/macOS users. There are no explicit Bash or Linux shell examples, nor are Linux-specific considerations (such as shell differences or package installation instructions for Azure CLI) mentioned. The support instructions reference both Windows and Linux VMs, but all command-line examples are Windows-centric or ambiguous.
Recommendations
  • Provide Bash/Linux shell examples for Azure CLI commands, using correct syntax for variable assignment and command chaining.
  • Clarify that Azure CLI is cross-platform and give installation instructions for Linux/macOS.
  • List Azure CLI examples before PowerShell, or present both side-by-side.
  • Explicitly mention that all steps can be performed on Linux/macOS, and note any differences (e.g., authentication methods, environment setup).
  • Correct the CLI authentication example to use Bash syntax (e.g., export, variable assignment without $ prefix).
GitHub Create Pull Request
Virtual Machines Create SSH keys in the Azure portal ...blob/main/articles/virtual-machines/ssh-keys-portal.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 Windows bias primarily in the 'Connect to the VM' section, where only a PowerShell prompt is mentioned for running the SSH command, with no reference to Linux/macOS terminals. Additionally, the example command uses a Windows-style path (/Downloads/...), and there are no Linux/macOS-specific instructions or screenshots. The page also refers users to a guide for connecting to Linux VMs from Windows, further reinforcing a Windows-first perspective. Linux and macOS users are left to infer that the same SSH command applies to their platforms, but this is not made explicit.
Recommendations
  • Add explicit instructions and examples for connecting from Linux and macOS terminals, including typical shell environments (e.g., Bash, Terminal.app).
  • Include screenshots or terminal prompts from Linux/macOS alongside PowerShell examples.
  • Clarify that the SSH command works across platforms and note any path differences (e.g., ~/Downloads/ on Linux/macOS vs. C:\Users\...\Downloads on Windows).
  • Reference Linux/macOS documentation for SSH usage, not only Windows guides.
GitHub Create Pull Request
Virtual Machines Upgrade Gen1 VMs to Trusted launch ...s/virtual-machines/trusted-launch-existing-vm-gen-1.md
Medium 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 several Windows biases: Windows-specific tools (MBR2GPT.exe, BitLocker, Defrag) are discussed in detail, with Linux alternatives mentioned briefly or not at all. Windows instructions and troubleshooting steps are more comprehensive and appear first. The PowerShell example is more detailed than the CLI, and ARM template deployment uses PowerShell. Linux upgrade scenarios are limited to certain distros, with unsupported cases redirected to a registration form rather than providing guidance. There is less troubleshooting and fewer step-by-step instructions for Linux users.
Recommendations
  • Provide Linux-first or parallel examples for disk conversion (MBR to GPT) and EFI partition creation, including common tools (e.g., gdisk, parted, efibootmgr) and step-by-step instructions.
  • Expand troubleshooting sections for Linux, covering common errors and recovery steps.
  • Include parity in backup/encryption guidance for Linux (e.g., LUKS, cryptsetup).
  • Offer ARM template deployment examples using Azure CLI or bash, not just PowerShell.
  • Ensure Linux instructions are as detailed and actionable as Windows, including validation and rollback steps.
  • List Linux tools and commands before or alongside Windows tools where applicable.
GitHub Create Pull Request
Virtual Machines Enable Trusted launch on existing Uniform scale set ...icles/virtual-machines/trusted-launch-existing-vmss.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 page exhibits several Windows biases. Windows examples (e.g., OS image references, ARM template samples) are shown first or exclusively, with Linux equivalents only mentioned in passing (e.g., extension publisher name table). The ARM template and CLI/PowerShell examples use Windows-centric image SKUs and do not provide parallel Linux image examples. PowerShell is featured heavily, and Windows tools/patterns (e.g., WindowsServer image, Azure PowerShell) are prioritized. Linux users are left to infer the correct parameters and images for their scenarios.
Recommendations
  • Provide explicit Linux OS image examples and parameters in ARM template, CLI, and PowerShell sections.
  • Show Linux extension publisher usage in sample code, not just in a table.
  • Alternate or parallelize Windows and Linux examples in all code blocks.
  • Clarify any differences in Trusted launch support or configuration for Linux scale sets.
  • Include links to Linux-specific documentation where relevant.
GitHub Create Pull Request
Virtual Machines Deploy a Trusted Launch VM ...ain/articles/virtual-machines/trusted-launch-portal.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 provides both Linux and Windows guidance for deploying Trusted Launch VMs, but there is a notable Windows bias in several areas. PowerShell examples are exclusively for Windows VMs, with no Linux PowerShell or Bash equivalents. Windows-centric tools and patterns (e.g., RDP, BitLocker, Windows-specific image generalization) are referenced more frequently and in greater detail. In multi-step PowerShell sections, only Windows VM creation is shown, while CLI examples are Linux-focused. In some cases, Windows instructions or terminology appear first or are more detailed, and Linux-specific nuances (such as SSH configuration or Linux image generalization) are less emphasized or referenced only via external links.
Recommendations
  • Provide PowerShell examples for Linux VM deployment, or clarify that PowerShell is Windows-only and offer Bash or shell script alternatives for Linux users.
  • Balance CLI and PowerShell examples: for every Windows-focused example, include a Linux equivalent (e.g., show both Windows and Linux VM creation in PowerShell).
  • When discussing VM configuration (network, security, disk), include Linux-specific considerations (e.g., SSH, Linux disk encryption, SELinux/AppArmor).
  • Avoid Windows-first ordering in examples and instructions; alternate or group by OS where possible.
  • Expand on Linux image generalization and deployment steps within the documentation, not just via external links.
  • Clarify when a step or tool is Windows-only, and provide Linux/macOS alternatives or guidance.
GitHub Create Pull Request
Virtual Machines Enable Trusted launch on existing Gen2 VMs ...rticles/virtual-machines/trusted-launch-existing-vm.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 parity for both Linux and Windows VMs at a high level, but there is a notable bias toward Windows tools and patterns. PowerShell is heavily featured in both the main and template sections, and Windows-specific tools (RDP, PowerShell) are mentioned before their Linux equivalents (SSH, CLI). The CLI examples are cross-platform, but PowerShell is Windows-centric. In several places, PowerShell is presented as the default scripting option, and instructions for tasks like deallocation and template deployment use PowerShell syntax, with no Bash or Linux shell alternatives. The documentation also references Windows tools (RDP, PowerShell) before Linux ones (SSH, CLI) when discussing VM access.
Recommendations
  • Provide Bash or Linux shell script examples alongside PowerShell for template deployments and VM operations.
  • Explicitly mention that Azure CLI is cross-platform and can be run on Linux/macOS, and provide Linux/macOS installation links.
  • When listing access methods, mention SSH (Linux) before or alongside RDP (Windows), or alternate their order.
  • Where PowerShell is used for template deployment, provide equivalent Bash/CLI commands for Linux/macOS users.
  • Clarify that all steps can be performed on Linux VMs, and link to Linux-specific troubleshooting or validation guides.
GitHub Create Pull Request
Virtual Machines FAQ for Trusted Launch ...b/main/articles/virtual-machines/trusted-launch-faq.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 shows a moderate Windows bias. Windows terminology and tools (e.g., Hyper-V, Secure Boot, PowerShell) are frequently mentioned first or exclusively. CLI and PowerShell examples are provided for both Windows and Linux, but PowerShell (a Windows-centric tool) is often shown alongside CLI, and some examples (such as image validation) use Windows images first. Linux-specific troubleshooting and validation are covered, but Windows examples and links (e.g., Secure Boot, Hyper-V) are referenced before Linux equivalents. Some sections lack explicit Linux parity, such as troubleshooting vTPM states and certificate inspection, which do not mention Linux-specific tools.
Recommendations
  • Ensure Linux examples are presented alongside or before Windows examples, especially in command sections.
  • Include Linux-native tooling (e.g., Bash scripts, Linux certificate inspection commands) where PowerShell is used.
  • Reference Linux documentation and tools (e.g., Linux boot troubleshooting, TPM tools) as prominently as Windows/Hyper-V links.
  • Add explicit Linux troubleshooting steps for vTPM and Secure Boot failures, not just generic or Windows-focused advice.
  • Balance terminology: avoid using Windows/Hyper-V terms as the default, and clarify when features/tools are cross-platform.
GitHub Create Pull Request
Virtual Machines Secure Boot UEFI keys ...ual-machines/trusted-launch-secure-boot-custom-uefi.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation frequently mentions Windows tools and patterns (e.g., PowerShell, MicrosoftWindowsTemplate) before or alongside Linux equivalents. PowerShell is listed as a primary method for creating resources, and signature templates include Windows-specific options. However, Linux verification commands and useful links for Linux distributions are provided, mitigating some bias.
Recommendations
  • Provide explicit Linux CLI (e.g., Bash, Azure CLI) examples alongside or before PowerShell examples for resource creation and management.
  • Clarify that all steps can be performed on Linux/macOS, and highlight any platform-specific differences.
  • Include Linux-specific signature template examples if available.
  • Ensure that Linux tools (e.g., OpenSSL, mokutil) are referenced equally or before Windows tools.
  • Add step-by-step Linux/macOS instructions for certificate/key creation and image management.
GitHub Create Pull Request
Virtual Machines Trusted Launch for Azure VMs .../blob/main/articles/virtual-machines/trusted-launch.md
Medium 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 for Trusted Launch for Azure VMs demonstrates a moderate Windows bias. Windows-specific technologies (Secure Boot, vTPM, VBS, HVCI, Credential Guard) are described in detail, often referencing Windows documentation and tools. Example ARM templates for Trusted Launch reference Windows VM deployments first, and Windows-centric features (like driver installation) are discussed before Linux equivalents. Linux-specific instructions (e.g., for Secure Boot and driver installation) are mentioned but are less detailed and sometimes only referenced via external links. There are no direct Linux CLI or shell examples, and Windows tools and patterns (such as Windows Defender, Credential Guard, and PowerShell) are referenced without Linux parity.
Recommendations
  • Provide Linux-specific examples and instructions alongside Windows examples, especially for enabling Trusted Launch, Secure Boot, and vTPM.
  • Include direct Linux CLI or shell commands (e.g., az CLI, bash) for common tasks, not just ARM templates or Windows-centric tools.
  • Reference Linux documentation and troubleshooting guides with equal prominence to Windows resources.
  • Discuss Linux security features (such as kernel module signing, integrity measurement, and alternatives to Credential Guard) in comparable detail.
  • Ensure that Linux driver installation and Secure Boot instructions are as detailed and accessible as Windows equivalents.
GitHub Create Pull Request
Virtual Machines Guest updates and host maintenance overview ...icles/virtual-machines/updates-maintenance-overview.md
Medium 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 generally aims for parity between Windows and Linux, but there are several areas where Windows is prioritized or Linux details are less visible. Windows-specific tools and features (like Hotpatching) are described in detail, while Linux equivalents are not mentioned or are less prominent. In some sections, Windows links/examples are listed before Linux, and PowerShell is mentioned as a primary tool, with less emphasis on Bash/Cloud Shell. Some features (like maintenance control for extensions) mention CLI and PowerShell, but do not clarify Linux support or provide Linux-specific examples.
Recommendations
  • Ensure that Linux and Windows examples/links are always presented together, or alternate their order to avoid implicit prioritization.
  • For every Windows-specific feature (e.g., Hotpatching), explicitly state Linux alternatives or clarify if not available.
  • When referencing tools (e.g., PowerShell, CLI), provide equal emphasis and examples for Bash/Cloud Shell and Linux-native tools.
  • Add explicit Linux examples or links where only Windows ones are present, such as in the 'Scheduled events' section.
  • Clarify in each section which features are Windows-only, Linux-only, or cross-platform, to set user expectations.
  • Where features are not available for Linux, provide workarounds or guidance for Linux users.
GitHub Create Pull Request
Virtual Machines Deploying disks with Azure Resource Manager templates ...l-machines/using-managed-disks-template-deployments.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 consistently uses Windows-centric examples, such as referencing the 'vm-simple-windows' template and showing JSON snippets with Windows-specific image references. There are no Linux-specific template examples or image references in the main body, and all code samples use Windows images. Linux parity is only mentioned in the 'Next steps' section, which links to a Linux template, but no Linux examples are shown directly in the documentation.
Recommendations
  • Include Linux VM examples alongside Windows VM examples in each code snippet, using appropriate image references (e.g., Ubuntu, CentOS).
  • Reference both 'vm-simple-windows' and 'vm-simple-linux' templates in the introduction and throughout the document.
  • Add explicit notes or sections highlighting differences or considerations for Linux VMs when deploying disks.
  • Ensure that all sample JSON includes both Windows and Linux image references, or alternate between them.
  • Provide links to Linux-specific documentation and quickstart templates earlier in the document, not just in 'Next steps'.
GitHub Create Pull Request
Virtual Machines List, update, and delete resources ...in/articles/virtual-machines/update-image-resources.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 Azure CLI and PowerShell examples for all major operations, but PowerShell is given equal prominence as CLI, despite being primarily a Windows tool. There are no Linux-specific examples, and PowerShell examples may not be directly usable on Linux/macOS. In some sections, PowerShell examples are presented immediately after CLI, which can subtly reinforce a Windows-centric workflow. No Linux/macOS shell scripting or tool references are present.
Recommendations
  • Clarify that PowerShell examples are primarily for Windows users, and note cross-platform PowerShell Core support if applicable.
  • Add explicit Bash or shell script examples for Linux/macOS users where scripting is shown for PowerShell.
  • Include notes on installing and using Azure CLI on Linux/macOS, and highlight its cross-platform nature.
  • Where variables or scripting are shown, use POSIX-compliant syntax in CLI examples (e.g., export region=westus instead of region=westus).
  • Consider adding a 'Platform compatibility' section to clarify tool support and usage on different OSes.
GitHub Create Pull Request
Virtual Machines Use Premium SSD v2 with VMs in availability set ...l-machines/use-premium-ssd-v2-with-availability-set.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 provides both Azure CLI and PowerShell examples for deploying Premium SSD v2 disks with VMs in an availability set, but the VM creation examples use a Windows image ('Win2016Datacenter') and PowerShell is presented as a primary automation option. There are no explicit Linux VM image examples, nor are there any bash scripting or Linux-specific instructions. The use of Windows-centric tools and examples may create friction for Linux/macOS users.
Recommendations
  • Include Linux VM image examples (e.g., UbuntuLTS) alongside Windows in CLI and PowerShell sections.
  • Add bash scripting examples for common tasks, especially for disk attachment and VM creation.
  • Clarify that Azure CLI is cross-platform and provide guidance for Linux/macOS users where relevant.
  • Explicitly mention that the instructions apply to both Windows and Linux VMs unless there are platform-specific limitations.
  • Balance the order of examples so that Linux and Windows are presented equally (e.g., alternate or show both in parallel).
GitHub Create Pull Request
Virtual Machines User data for Azure Virtual Machine ...-docs/blob/main/articles/virtual-machines/user-data.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 exhibits a Windows bias in several ways: JSON examples for VM creation and updates consistently use Windows OS images and Windows-specific configuration fields (e.g., 'osType': 'Windows', 'windowsConfiguration', 'timeZone', 'MicrosoftWindowsServer'), with no equivalent Linux examples. Windows-centric fields are shown first and exclusively in code samples. There are no explicit Linux VM configuration examples, nor is there guidance for Linux-specific patterns or fields. While the page references a Linux IMDS sample in a link, the main content and examples are Windows-focused.
Recommendations
  • Add parallel JSON examples for Linux VM creation and updates, using Linux OS images and relevant configuration fields (e.g., 'osType': 'Linux', 'linuxConfiguration').
  • Include Linux-specific fields and patterns in code samples, such as SSH key configuration and Linux image references.
  • Alternate the order of examples or provide both Windows and Linux examples side-by-side.
  • Explicitly mention Linux support and provide guidance for Linux users in each relevant section.
  • Ensure links to Linux documentation are prominent and not just in 'Next steps'.
GitHub Create Pull Request
Virtual Machines Creating Virtual Machine Restore Points using Azure portal ...hines/virtual-machines-create-restore-points-portal.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 using the Azure portal for creating and restoring VM restore points, with references to alternative methods using Azure CLI and PowerShell. However, when it comes to restoring a VM from a restore point, the links provided for creating a new VM and attaching restored disks point to Windows-specific documentation, with no mention or links to equivalent Linux VM instructions. This creates friction for Linux users who may not know where to find the relevant steps for their platform.
Recommendations
  • Add links to Linux VM creation and disk attachment documentation alongside the Windows links.
  • Explicitly mention that the process applies to both Windows and Linux VMs, and provide guidance or examples for Linux users.
  • Ensure parity in examples and instructions for both Windows and Linux throughout the restore process.
  • Consider adding a note or section for platform-specific steps if any differences exist.
GitHub Create Pull Request
Virtual Machines Create and deploy VM Application on Azure ...in/articles/virtual-machines/vm-applications-how-to.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 exhibits a notable Windows bias in several areas. Windows and PowerShell examples are frequently presented first or exclusively (e.g., .EXE, .MSI, .PS install scripts), and Windows-specific tools and patterns (msiexec, powershell.exe, .exe/.msi packaging) are emphasized. In CI/CD pipeline samples (GitHub Actions, Azure DevOps, GitLab, Jenkins), the default application and config file names are always Windows-centric (.exe, .json), and the creation of VM Application definitions defaults to Windows OS type, with no parallel Linux example. While Linux install script examples are present for .tar, .deb, .rpm, and .sh, the overall flow and automation guidance prioritize Windows scenarios, and Linux parity is not consistently maintained.
Recommendations
  • Provide Linux-first or side-by-side examples for all install script types, especially for .deb, .rpm, .sh, and .tar.gz.
  • In CI/CD pipeline samples, alternate or parallelize examples for Linux apps (e.g., use app.sh, app.deb, app-config.yaml) and set --os-type Linux in at least half of the samples.
  • Explicitly show how to create and deploy Linux VM Applications in automation flows (GitHub Actions, DevOps, etc.), not just Windows.
  • Balance the order of presentation so Linux and Windows examples are equally visible and accessible.
  • Avoid defaulting to Windows file types (.exe, .msi, .json) in variable names and sample scripts; use generic or Linux-centric names where appropriate.
  • Add guidance for Linux-specific packaging and deployment nuances (e.g., SELinux, systemd integration, permissions).
GitHub Create Pull Request
Virtual Machines Overview of VM Applications in the Azure Compute Gallery ...blob/main/articles/virtual-machines/vm-applications.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 provides both Windows and Linux guidance for packaging and deploying VM Applications, but several sections display Windows bias. Windows examples and tools (PowerShell, cmd.exe, msiexec) are often presented first or in more detail, and troubleshooting relies heavily on PowerShell commands. Linux instructions are present and reasonably thorough, but Windows-centric tools and patterns are emphasized, and some example scripts and troubleshooting steps are PowerShell-heavy.
Recommendations
  • Present Linux and Windows examples in parallel or alternate order, rather than Windows-first.
  • Expand troubleshooting guidance to include equivalent Linux CLI commands (e.g., Azure CLI, SSH, system logs) for extension status and error investigation.
  • Where PowerShell is referenced for deployment or status, provide Azure CLI or Bash alternatives for Linux/macOS users.
  • In packaging and install sections, ensure Linux examples are as detailed and prominent as Windows ones.
  • For file renaming and manipulation examples, include Linux shell commands alongside Windows cmd/powershell.
  • Clarify that all operations (deployment, management, troubleshooting) can be performed from Linux/macOS environments using Azure CLI or REST API.
GitHub Create Pull Request
Virtual Machines VM vCore Customization ...lob/main/articles/virtual-machines/vm-customization.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 provides both Azure CLI and PowerShell examples for configuring VM vCore customization, but the PowerShell example is detailed and uses Windows-specific SDK objects, while the CLI example is brief and lacks Linux/macOS-specific context. The PowerShell section is given equal prominence to CLI, and there is no explicit mention of Linux/macOS shell usage or examples beyond the CLI. The documentation refers to PowerShell without clarifying cross-platform support, and does not provide bash or shell script equivalents for Linux users. The ordering of examples (CLI, then PowerShell) is reasonable, but the PowerShell example is more verbose and detailed, potentially favoring Windows users.
Recommendations
  • Add explicit bash or shell script examples for Linux/macOS users, especially for ARM template deployment and Azure CLI usage.
  • Clarify that Azure CLI commands work on Linux/macOS and provide sample commands for those environments (e.g., with SSH key handling, environment variables).
  • Note that PowerShell Core is cross-platform, but provide guidance or examples for Linux/macOS users who may not use PowerShell.
  • Ensure parity in example detail: expand CLI examples to match the depth of the PowerShell section, including object manipulation if relevant.
  • Consider adding a table or section comparing the steps for Windows, Linux, and macOS environments.
GitHub Create Pull Request
Virtual Machines Create a VM from a generalized image in a gallery ...icles/virtual-machines/vm-generalized-image-version.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 both Azure CLI and PowerShell examples for most scenarios, but the PowerShell sections are heavily Windows-centric, with all example scripts using Windows-specific parameters (e.g., Set-AzVMOperatingSystem -Windows) and password authentication. There are no PowerShell examples for Linux VM creation, nor any mention of Linux-specific PowerShell patterns. Additionally, network security rules in PowerShell examples focus on RDP (port 3389), which is Windows-specific, and password authentication is shown before SSH key authentication. While CLI and REST examples do show Linux VM creation and SSH, PowerShell coverage is notably biased toward Windows. The order of presentation also often places Windows-centric tools and patterns before Linux equivalents.
Recommendations
  • Add PowerShell examples for creating Linux VMs, including use of Set-AzVMOperatingSystem -Linux and SSH key authentication.
  • In PowerShell networking examples, include rules for SSH (port 22) alongside or before RDP (port 3389).
  • Ensure parity in authentication methods: demonstrate both password and SSH key authentication for both Windows and Linux in all tool examples.
  • When presenting examples, alternate or randomize the order of Windows and Linux scenarios, or explicitly provide both side-by-side.
  • Review and update documentation to avoid implicit prioritization of Windows tools and patterns.
GitHub Create Pull Request
Virtual Machines VM watch Collectors Suite .../articles/virtual-machines/vm-watch-collector-suite.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 for VM watch Collectors Suite demonstrates a moderate Windows bias. Several collectors reference Windows-specific tools (e.g., Windows EventLog, w32tm command, time.windows.com), and Windows eligibility is often described before Linux equivalents. Some collectors are Windows-only (e.g., system_error, hardware_health_monitor), while Linux support is limited or only mentioned in passing (e.g., hardware_health_nvidia_smi for Ubuntu only). There are missing Linux/macOS examples for event log collection and time synchronization, and the default URLs and NTP servers are Windows-centric.
Recommendations
  • Provide equivalent Linux/macOS examples and tooling for collectors that currently reference only Windows tools (e.g., describe how system errors and hardware health can be collected on Linux, such as using syslog, journalctl, or SMART tools).
  • Include Linux-first or cross-platform examples for time synchronization (e.g., use pool.ntp.org or OS-agnostic NTP servers instead of time.windows.com).
  • Clarify eligibility and default behaviors for Linux/macOS in all collectors, not just Windows.
  • Add explicit documentation for macOS support or clarify its limitations.
  • Where a collector is Windows-only, suggest Linux alternatives or note the gap.
  • Reorder examples and descriptions so that Linux and Windows are given equal prominence.
GitHub Create Pull Request
Virtual Machines Implement Oracle Golden Gate on an Azure Linux VM | Microsoft Docs ...hines/workloads/oracle/configure-oracle-golden-gate.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
While the documentation is focused on deploying Oracle Golden Gate on Azure Linux VMs, there is a notable Windows bias in the sections related to X Server setup and file transfer. The instructions require users to create a Windows VM (ggXServer) specifically to run Xming X Server for graphical installation, with no mention of Linux or macOS alternatives (such as X11 forwarding or native X servers). Additionally, PowerShell commands are used for Bastion tunneling and file transfer, with no equivalent Bash or Linux-native instructions provided. The documentation lists Windows paths before Linux ones and assumes Windows tools for critical steps.
Recommendations
  • Provide instructions for running X Server natively on Linux and macOS clients (e.g., using XQuartz on macOS, X11 on Linux, or X11 forwarding via SSH).
  • Include Bash equivalents for Bastion tunneling and SCP file transfer, using az CLI and standard Linux/macOS tools.
  • Offer alternative steps for graphical installer invocation using SSH X11 forwarding, avoiding the need for a dedicated Windows VM.
  • List Linux/macOS paths and tools before or alongside Windows ones when discussing SSH keys and file locations.
  • Clarify that the Windows VM is optional and only needed if users lack access to a local X server.
GitHub Create Pull Request
Virtual Machines Connect Azure ExpressRoute with Oracle Cloud Infrastructure | Microsoft Docs ...nes/workloads/oracle/configure-azure-oci-networking.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 documentation page demonstrates a moderate Windows bias. While it claims applicability to Linux VMs and references Terraform (a cross-platform tool), most step-by-step instructions and screenshots are based on the Azure Portal UI, which is platform-agnostic but often associated with Windows workflows. Notably, when scripting is mentioned, only PowerShell is referenced for ExpressRoute FastPath configuration, with no Bash or Azure CLI example provided. Monitoring is described using Azure Network Performance Monitor, a Windows-centric tool, with no mention of Linux-native alternatives. There is a lack of explicit Linux command-line examples, and PowerShell is presented before any Linux-friendly options.
Recommendations
  • Add Azure CLI and Bash examples alongside PowerShell commands for configuration steps, especially for ExpressRoute FastPath.
  • Include Linux-centric monitoring options or clarify Network Performance Monitor's cross-platform capabilities.
  • Provide explicit Linux command-line instructions for key steps (e.g., resource creation, verification).
  • Ensure screenshots and UI references are supplemented with CLI or script-based alternatives for Linux users.
GitHub Create Pull Request
Virtual Machines Set up Oracle ASM on an Azure Linux virtual machine | Microsoft Docs ...tual-machines/workloads/oracle/configure-oracle-asm.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation is focused on setting up Oracle ASM on Azure Linux VMs, but exhibits notable Windows bias in several areas. The X Server VM is created as a Windows machine, and all instructions for running X Server use Windows-only tooling (Xming, Windows Firewall). The PowerShell example for Bastion tunneling is given, with no Linux/macOS equivalent. SCP instructions are shown in a Windows context. There are no instructions for using a Linux or macOS workstation for X Server or Bastion tunneling, nor are cross-platform alternatives mentioned.
Recommendations
  • Provide instructions for creating the X Server VM as a Linux machine (e.g., Ubuntu with X11), or explain how to use a local Linux/macOS workstation for X11 forwarding.
  • Include Linux/macOS equivalents for Bastion tunneling (e.g., using az network bastion tunnel from bash/zsh, or using SSH ProxyCommand).
  • Offer guidance for running X Server on Linux (e.g., Xorg, XQuartz for macOS) and connecting to the VM using native SSH/X11 forwarding.
  • Show SCP examples for Linux/macOS, not just Windows/PowerShell.
  • Mention cross-platform tools and patterns before or alongside Windows-specific ones, or clearly mark Windows-only steps.
GitHub Create Pull Request
Virtual Machines Red Hat Enterprise Linux bring-your-own-subscription Azure images | Microsoft Docs ...ain/articles/virtual-machines/workloads/redhat/byos.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 provides both Azure CLI (cross-platform) and PowerShell examples for provisioning Red Hat Enterprise Linux BYOS images on Azure. However, the PowerShell section is significantly more detailed, with a full end-to-end script, while the CLI section is more concise and lacks equivalent depth (e.g., full VM creation with networking, SSH keys, etc.). The PowerShell example uses Windows-specific tools and patterns, and appears after the CLI section, but is more comprehensive. There is no explicit Linux/macOS bias, but the richer PowerShell example may create friction for non-Windows users seeking parity.
Recommendations
  • Expand the Azure CLI section to include a full, step-by-step example covering resource group, network, public IP, NSG, NIC, VM creation, and SSH key configuration, matching the PowerShell script's completeness.
  • Add explicit notes or links for Linux/macOS users on how to generate SSH keys and use them in Azure CLI.
  • Ensure that all automation examples (including Terraform) are platform-neutral and provide parity in detail.
  • Consider providing bash shell scripts or guidance for Linux/macOS users where appropriate.
GitHub Create Pull Request
Virtual Machines Quickstart - Create a Linux VM in the Azure portal ...articles/virtual-machines/linux/quick-create-portal.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation provides instructions for connecting to the VM via SSH, mentioning Windows/PowerShell users before Linux/macOS users. However, it does include explicit steps for both platforms and offers Linux-specific package installation instructions. There are no Windows-only tools or missing Linux examples.
Recommendations
  • Present Linux/macOS instructions before Windows/PowerShell, or group them equally.
  • Consider explicitly mentioning macOS alongside Linux when referring to Bash prompts.
  • Ensure screenshots and UI references are platform-neutral or include notes for platform-specific differences if any.
GitHub Create Pull Request
Virtual Machines MSP Feature Configuration ...l-machines/metadata-security-protocol/configuration.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation displays mild Windows bias, notably by referencing Windows in key configuration details before Linux, and by using Windows-centric naming in examples (e.g., 'GPAWinVM'). The automatic GPA installation/uninstallation is described only for Windows, and the VM examples use Windows naming conventions. However, Linux is supported throughout, with audit log paths and security behaviors described for both OS families.
Recommendations
  • Clarify that GPA installation/uninstallation is supported for Linux VMs, or explicitly state any differences.
  • Use neutral example names (e.g., 'GPA-VM') instead of 'GPAWinVM' to avoid implying Windows exclusivity.
  • When describing configuration properties, mention Linux and Windows behaviors equally, or note any OS-specific differences.
  • Provide explicit Linux CLI or scripting examples (e.g., Azure CLI, Bash) alongside PowerShell or Windows-centric instructions if referenced elsewhere.
  • Ensure that any automation or troubleshooting steps are described for both Linux and Windows.
GitHub Create Pull Request
Virtual Machines Move a maintenance configuration to another Azure region ...tual-machines/move-region-maintenance-configuration.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both Azure CLI and PowerShell options for creating, assigning, and deleting maintenance configurations, but PowerShell is mentioned first in each step. This ordering subtly prioritizes Windows tooling and may imply PowerShell is the primary or preferred method, which can create friction for Linux/macOS users who typically use Azure CLI or shell scripting. No Linux-specific examples or shell scripts are provided, but CLI coverage is present.
Recommendations
  • Present Azure CLI instructions before PowerShell, or list both together without implied priority.
  • Explicitly mention that Azure CLI works cross-platform and is recommended for Linux/macOS users.
  • Add bash/shell script examples for common tasks to further support Linux users.
  • Clarify that all steps can be completed using Azure CLI on Linux/macOS.
GitHub Create Pull Request
Virtual Machines InfiniBand driver extension - Azure Linux VMs ...al-machines/extensions/hpc-compute-infiniband-linux.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation is focused on Linux VMs and provides Linux-centric information and examples. However, there is a notable presence of PowerShell examples for deployment and management tasks, which are traditionally Windows tools. While Azure PowerShell is cross-platform, its prominence may create friction for Linux users who typically prefer Bash or native Azure CLI. The documentation does mention an extension for Windows VMs, but does not prioritize Windows content or omit Linux examples.
Recommendations
  • Provide Bash script examples for extension deployment and management, in addition to PowerShell and Azure CLI.
  • Clarify that Azure PowerShell can be used on Linux/macOS, or recommend Azure CLI/Bash as the primary method for Linux users.
  • Consider reordering examples to show Azure CLI or Bash first, as these are more native to Linux workflows.
  • Explicitly mention cross-platform compatibility of PowerShell if it is to be used.
GitHub Create Pull Request
Container Instances Encrypt deployment data ...ontainer-instances/container-instances-encrypt-data.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation references Azure PowerShell and the Azure Portal alongside Azure CLI for resource creation and configuration steps. While Azure CLI is cross-platform and used for all command-line examples, PowerShell and Portal are mentioned as alternatives before Linux-native equivalents (such as Bash scripting or ARM templates via CLI-only). There are no explicit Linux-only or macOS-only instructions, but no critical steps are Windows-exclusive. The documentation does not provide Linux-specific shell examples (e.g., Bash), but the use of Azure CLI ensures cross-platform compatibility.
Recommendations
  • Clarify that all Azure CLI commands work on Windows, Linux, and macOS, and recommend Azure CLI as the primary method for cross-platform users.
  • When listing options for resource creation (e.g., Key Vault), mention Azure CLI first, then Portal and PowerShell, to avoid Windows-first bias.
  • Remove or de-emphasize Azure PowerShell references unless a PowerShell-specific feature is required.
  • Add explicit notes or links for Linux/macOS users where relevant (e.g., uploading files to Cloud Shell from Linux/macOS).
  • Provide Bash shell variable examples alongside PowerShell-style variables where variables are used in CLI commands.
GitHub Create Pull Request
Virtual Machines Project Flash - Advancing Azure Virtual Machine availability monitoring .../blob/main/articles/virtual-machines/flash-overview.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 demonstrates a mild Windows bias. References to scheduled events link specifically to the Windows documentation, and several cross-platform Azure features are described without explicit Linux or macOS examples or links. Activity log and resource graph references mention PowerShell and Azure CLI tabs, but do not provide Linux-specific guidance or highlight parity. There are no examples or guidance tailored for Linux VM monitoring scenarios, nor are Linux-specific troubleshooting or automation tools mentioned.
Recommendations
  • Include links to both Windows and Linux scheduled events documentation when discussing early warning features.
  • Add explicit examples or references for monitoring Linux VMs, such as using Bash, Azure CLI, or Linux-native tools.
  • Ensure all referenced Azure features (Resource Graph, Activity Logs, Monitor) provide parity in example commands for Linux/macOS environments.
  • Where PowerShell is mentioned, also provide equivalent Bash/Azure CLI commands for Linux users.
  • Highlight any differences or considerations for Linux VM availability monitoring, such as OS-specific failure modes or integration points.
GitHub Create Pull Request
Virtual Machines Install VM Watch ...lob/main/articles/virtual-machines/install-vm-watch.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 provides parity for both Windows and Linux in terms of CLI and ARM template instructions. However, there is a mild Windows bias: PowerShell examples are included (which are Windows-centric), and in several places, Windows screenshots and links are presented before Linux equivalents. PowerShell is given as a primary scripting option, while Bash or Linux shell alternatives are not mentioned. The quickstart links list Windows before Linux. Screenshots for Windows installations are shown before Linux ones.
Recommendations
  • Add Bash or shell script examples alongside PowerShell for Linux users.
  • Alternate the order of Windows and Linux examples/screenshots to avoid implicit prioritization.
  • Explicitly mention that PowerShell Core is cross-platform, or provide Linux-native scripting alternatives.
  • Where possible, provide Linux-specific troubleshooting or validation steps, not just generic or Windows-first instructions.
GitHub Create Pull Request
Container Instances Azure Resource Manager template samples .../container-instances/container-instances-samples-rm.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page lists both Windows and Linux container sample templates, but there is a notable Windows bias in the template table: the only Windows-specific application sample (MS NAV with SQL Server and IIS) is highlighted, while Linux application samples are more generic. In the deployment options, Azure PowerShell is listed alongside Azure CLI, but CLI is mentioned first. No explicit PowerShell-heavy bias or missing Linux examples are present, but Windows tools and patterns (IIS, SQL Server) are featured in application samples.
Recommendations
  • Add more Linux-specific application samples to balance the Windows-focused MS NAV example.
  • Ensure parity in examples by providing equivalent Linux-based enterprise app deployments (e.g., ERP, database stacks).
  • Clarify in the deployment section that Azure CLI is cross-platform and recommend it for Linux/macOS users.
  • Consider adding bash or shell script deployment examples for Linux users if relevant.
GitHub Create Pull Request
Virtual Machines Quickstart: Create a Linux VM cluster in Azure using Terraform ...rtual-machines/linux/quick-cluster-create-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. However, PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and is presented immediately after the CLI example, which is cross-platform. There are no explicit Linux shell examples (e.g., Bash), nor is there any mention of Linux-specific tooling or commands for verification. The rest of the documentation is neutral and focused on Terraform, which is cross-platform.
Recommendations
  • Prioritize Azure CLI examples, as it is cross-platform and preferred for Linux/macOS users.
  • Clearly indicate that Azure PowerShell is primarily for Windows users, and suggest Azure CLI for Linux/macOS.
  • Add explicit Bash shell examples for verification steps, if relevant.
  • Consider reordering the tabs to show Azure CLI first, and PowerShell second, with a note about platform compatibility.
GitHub Create Pull Request
Container Instances Request a container from a Standby pool for Azure Container Instances ...https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/container-instances/container-instances-standby-pool-request-container.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for requesting a container group from a standby pool, but PowerShell (a Windows-centric tool) is given its own dedicated section and example. The CLI example is cross-platform, but PowerShell is highlighted as an alternative, which may imply a Windows-first approach. There are no Linux-specific shell examples (e.g., Bash scripts) or explicit mention of Linux/macOS usage. The ARM template and REST sections are platform-neutral, but the presence and prominence of PowerShell may create minor friction for Linux/macOS users.
Recommendations
  • Clarify that Azure CLI commands work on Linux/macOS and Windows equally.
  • Consider adding explicit Bash shell examples or notes for Linux/macOS users.
  • If PowerShell is included, balance with examples using native Linux tools or scripting languages.
  • Reorder examples so cross-platform tools (CLI, REST, ARM templates) are presented before Windows-specific tools like PowerShell.
GitHub Create Pull Request
Virtual Machines Configure Event Hubs for VM watch ...ticles/virtual-machines/configure-eventhub-vm-watch.md
Low 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 mild Windows bias. References to PowerShell and Windows tools are present before Linux equivalents, and examples or instructions for configuring VM watch often mention PowerShell and Windows paths first or exclusively. Linux-specific instructions are limited, and Linux users may need to infer steps or adapt Windows-centric instructions.
Recommendations
  • Provide explicit Linux and macOS examples alongside Windows/PowerShell examples, especially for configuration and troubleshooting steps.
  • List Linux and Windows instructions in parallel tabs or sections, ensuring equal prominence.
  • Include CLI/bash commands for Linux users where PowerShell is referenced.
  • Expand troubleshooting and log location guidance for Linux and macOS, not just Windows.
  • Ensure screenshots and UI references are platform-neutral or include Linux-specific visuals where relevant.
GitHub Create Pull Request
Virtual Machine Scale Sets Azure Virtual Machine Scale Sets Attached Data Disks ...cale-sets/virtual-machine-scale-sets-attached-disks.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 Windows and Linux examples for preparing data disks in scale sets, but the Windows example (PowerShell) is shown first and uses a named script (prepare_vm_disks.ps1) with explicit PowerShell invocation. The Linux example follows, using bash and a .sh script. The initial tutorial links mention Azure CLI and Azure PowerShell, but do not explicitly mention Linux-specific tools or show Linux-first patterns.
Recommendations
  • Alternate the order of Windows and Linux examples, or present them side-by-side to avoid implicit prioritization.
  • Explicitly mention that Azure CLI is cross-platform and provide Linux/macOS-specific command examples where relevant.
  • Include references to Linux-native tools or patterns (e.g., cloud-init, shell scripting) in addition to PowerShell.
  • Clarify that both Windows and Linux are fully supported and provide parity in documentation structure and example depth.
GitHub Create Pull Request
Container Instances Troubleshoot common issues ...ainer-instances/container-instances-troubleshooting.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation provides both Linux and Windows examples for container deployment, but Windows-specific considerations (such as image support, networking delays, and cached images) are given dedicated sections and are often discussed before or in more detail than Linux equivalents. Some instructions reference shell usage and variable assignment with a note to adjust for PowerShell/Command Prompt, but do not provide explicit Linux/Bash alternatives. Windows-specific troubleshooting (e.g., network readiness, image support) is covered in more depth than Linux-specific issues.
Recommendations
  • Ensure Linux and macOS examples are presented with equal prominence and detail as Windows examples.
  • Where shell commands or variable assignments are shown, provide explicit Bash/Linux alternatives alongside Windows/PowerShell syntax.
  • Balance troubleshooting coverage by including Linux/macOS-specific issues (e.g., SELinux/AppArmor, common permission errors, networking differences).
  • When discussing cached images or OS support, provide parity in detail for both Windows and Linux images.
  • Avoid presenting Windows-specific sections before Linux equivalents unless justified by usage statistics.
GitHub Create Pull Request
Virtual Machine Scale Sets Configure rolling upgrades on Virtual Machine Scale Sets ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-configure-rolling-upgrades.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for all major operations, but PowerShell examples are given equal prominence and detail as CLI, which may indicate a Windows bias. PowerShell is a Windows-centric tool, and its inclusion alongside CLI in every section can create friction for Linux/macOS users, especially since PowerShell is not the default shell on those platforms. However, Azure CLI is cross-platform and shown in all cases, so Linux/macOS users can complete all tasks. No Windows-only tools or patterns are present, and examples are not exclusively Windows-focused.
Recommendations
  • Clarify that Azure CLI is the recommended and cross-platform tool for Linux/macOS users.
  • Add a note in each section indicating that PowerShell examples are primarily for Windows users, while CLI is suitable for all platforms.
  • Consider listing CLI examples before PowerShell examples to reinforce CLI as the default for non-Windows environments.
  • Optionally, provide Bash script snippets or highlight CLI usage in Linux/macOS terminals for greater parity.
GitHub Create Pull Request
Service Fabric Create an Azure Load Balancer rule for a cluster ...n/articles/service-fabric/create-load-balancer-rule.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 PowerShell examples for creating Azure Load Balancer rules. However, the PowerShell section is given equal prominence to Azure CLI, despite PowerShell being primarily a Windows tool. There are no Linux/macOS-specific shell examples (e.g., Bash), nor is there mention of Linux-specific considerations. The CLI example is cross-platform, but the inclusion and detailed walkthrough of PowerShell may suggest a Windows bias, especially for users unfamiliar with PowerShell on non-Windows systems.
Recommendations
  • Clarify that Azure CLI is fully cross-platform and recommended for Linux/macOS users.
  • Consider moving the Azure CLI section before PowerShell, or explicitly state CLI is the preferred method for non-Windows platforms.
  • Remove or de-emphasize PowerShell unless there are Windows-specific requirements.
  • Add a note for Linux/macOS users highlighting that PowerShell Core is available cross-platform, but Azure CLI is simpler and native.
  • Include troubleshooting or environment setup notes for Linux/macOS users if needed.
GitHub Create Pull Request
Virtual Machine Scale Sets Use scale-in policies with Azure Virtual Machine Scale Sets ...ale-sets/virtual-machine-scale-sets-scale-in-policy.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 PowerShell and Azure CLI examples for configuring scale-in policies, but PowerShell examples (typically associated with Windows) are presented before CLI examples, and CLI examples do not explicitly highlight Linux/macOS usage. There is no mention of Linux-specific tools or shell environments, nor any guidance for Linux/macOS users regarding prerequisites or differences. The ordering and emphasis may subtly favor Windows users.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or present CLI examples first to better support Linux/macOS users.
  • Explicitly state that Azure CLI works cross-platform and provide example commands in bash/zsh syntax where appropriate.
  • Add a note clarifying that PowerShell Core is available on Linux/macOS, and provide installation links or instructions.
  • Include troubleshooting or environment setup notes for Linux/macOS users (e.g., SSH key generation, shell differences).
  • Where possible, provide examples using native Linux tools or scripts if relevant.
GitHub Create Pull Request
Virtual Machines DCadsv5 size series ...rtual-machines/sizes/general-purpose/dcadsv5-series.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_tools
Summary
The documentation is largely platform-neutral, but there is a subtle Windows bias in the networking section, where the recommended bandwidth/throughput testing tool (NTTTCP) is a Windows-specific utility. No Linux equivalent is mentioned, and the link provided is for a Windows-focused guide. No other Windows-specific examples, tools, or ordering are present.
Recommendations
  • Mention Linux-compatible network testing tools (e.g., iperf, netperf) alongside NTTTCP.
  • Provide links to Linux-focused bandwidth/throughput testing guides.
  • Clarify in the documentation that NTTTCP is Windows-specific and suggest alternatives for Linux/macOS users.
GitHub Create Pull Request
Virtual Machines Dldsv6 size series (Preview) ...irtual-machines/sizes/general-purpose/dldsv6-series.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation is largely platform-neutral, focusing on VM specifications and features. However, there is mild Windows bias in the 'Feature support' section, where 'Nested Virtualization' links only to a Windows/Hyper-V guide, and in the 'Network' section, where bandwidth testing references NTTTCP, a Microsoft tool primarily associated with Windows. There are no Linux-specific examples or equivalent Linux tool references for these features.
Recommendations
  • Add references to Linux/KVM nested virtualization documentation alongside the Windows/Hyper-V link.
  • Mention Linux-compatible network bandwidth testing tools (e.g., iperf, netperf) in the networking section.
  • Where tools or features are platform-specific, clarify applicability and provide parity guidance for Linux/macOS users.
GitHub Create Pull Request
Virtual Machines NC_RTXPRO6000BSE_v6 size series ...s/sizes/gpu-accelerated/nc-rtxpro6000-bse-v6-series.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_tools
Summary
The documentation is largely neutral and platform-agnostic, focusing on VM sizes, specs, and features. However, there is a minor Windows bias in the networking section, where the recommended bandwidth/throughput testing tool (NTTTCP) is a Windows-native utility. No Linux equivalent is mentioned, and no Linux/macOS-specific examples or tools are provided.
Recommendations
  • Include Linux/macOS equivalents for any recommended tools, such as mentioning iperf3 or netperf for bandwidth testing alongside NTTTCP.
  • Explicitly state that performance optimization and testing guidance applies to both Linux and Windows, and provide links to Linux-specific documentation where relevant.
  • If referencing Windows-specific tools, add notes or alternatives for Linux/macOS users to ensure parity.
GitHub Create Pull Request
Virtual Machines Eadsv6 size series ...rtual-machines/sizes/memory-optimized/eadsv6-series.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page is largely neutral and platform-agnostic, focusing on VM specs and features. However, there are minor signs of Windows bias: the 'Nested Virtualization' feature links to a Windows/Hyper-V guide, and the bandwidth/throughput testing resource references NTTTCP, a tool traditionally associated with Windows. These references appear before or without Linux equivalents, which may create minor friction for Linux users seeking parity.
Recommendations
  • Include links to Linux-specific nested virtualization documentation (e.g., KVM/QEMU on Azure).
  • Mention and link to Linux-compatible bandwidth testing tools (e.g., iperf, netperf) alongside NTTTCP.
  • Where possible, clarify platform applicability for referenced tools and features.
  • Ensure that feature support lists and resource links are balanced between Windows and Linux, especially for advanced scenarios.
GitHub Create Pull Request
Virtual Machines Ev5 size series .../virtual-machines/sizes/memory-optimized/ev5-series.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page is mostly platform-neutral, but there is a subtle Windows bias in the 'Feature support' section, where Nested Virtualization is linked to a Windows/Hyper-V guide, and in the 'Network' section, where bandwidth/throughput testing references NTTTCP, a tool primarily associated with Windows. No Linux-specific examples, tools, or guidance are provided, and Windows resources are mentioned first or exclusively where relevant.
Recommendations
  • Include equivalent Linux documentation links for features like Nested Virtualization (e.g., KVM/QEMU guides for Linux VMs).
  • Mention Linux-compatible tools for bandwidth/throughput testing (such as iperf or netperf) alongside NTTTCP.
  • Where feature support is described, clarify if/how features work on Linux and provide relevant links.
  • Ensure that examples and references are balanced between Windows and Linux, or explicitly state platform applicability.
GitHub Create Pull Request
Virtual Machines Azure virtual machine extensions and features .../main/articles/virtual-machines/extensions/overview.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 page presents both Linux and Windows information, but there is a subtle Windows bias. Windows tools (PowerShell) are mentioned before Linux equivalents, and Windows troubleshooting steps are referenced first. The troubleshooting table lists Windows extensions and tools prominently, including PowerShell DSC, while Linux equivalents are present but not highlighted. Windows examples and links are often shown before Linux ones, and some extension namespaces (e.g., powershell.dsc) are Windows-specific.
Recommendations
  • Ensure Linux and Windows examples/tools are presented in parallel, with equal prominence.
  • When listing management options (CLI, PowerShell, ARM templates), clarify which are cross-platform and provide Linux-specific command examples alongside PowerShell.
  • In troubleshooting sections, alternate the order of Windows and Linux entries or group them by OS for clarity.
  • Highlight Linux tools and workflows (e.g., Bash, Azure CLI) as much as PowerShell.
  • Add explicit Linux command examples where only Windows/PowerShell is mentioned.
GitHub Create Pull Request
Service Fabric Configure a Service Fabric managed cluster to use a NAT gateway ...s/service-fabric/how-to-managed-cluster-nat-gateway.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides example commands for ARM templates, Azure CLI, Azure PowerShell, and Azure portal. While Azure CLI is cross-platform, Azure PowerShell examples are given in detail and are presented before the Azure portal steps. There are no Linux-specific shell examples (e.g., Bash scripts), and PowerShell is a Windows-centric tool, though it is available on Linux. The ordering and depth of PowerShell examples may create a perception of Windows bias.
Recommendations
  • Add explicit Bash shell examples for Linux users, especially for Azure CLI usage.
  • Clarify that Azure CLI commands work identically on Linux, macOS, and Windows.
  • If PowerShell is shown, mention that Azure PowerShell is available on Linux and macOS, or provide equivalent Bash/CLI examples.
  • Consider presenting Azure CLI examples before PowerShell, as CLI is more universally cross-platform.
  • Add a note or section for Linux/macOS users to highlight any platform-specific considerations.
GitHub Create Pull Request
Service Fabric Use a Public IP address prefix in a Service Fabric managed cluster ...vice-fabric/how-to-managed-cluster-public-ip-prefix.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 deploying a public IP prefix in a Service Fabric managed cluster. However, the PowerShell example is given equal prominence to the CLI, and PowerShell is a Windows-centric tool, potentially creating friction for Linux/macOS users. The CLI example is cross-platform, but there is a subtle bias in listing PowerShell as a primary method and linking to PowerShell-specific guides. No Linux-specific tools or shell examples are provided, and there is no explicit mention of Linux/macOS compatibility.
Recommendations
  • Clearly state that Azure CLI is cross-platform and recommended for Linux/macOS users.
  • List Azure CLI examples before PowerShell examples to reduce Windows-first perception.
  • Add a note clarifying that PowerShell examples are primarily for Windows users.
  • Consider providing bash shell script examples for ARM template deployment for Linux users.
  • Link to documentation on using Azure CLI on Linux/macOS.
GitHub Create Pull Request
Virtual Machines Mdsv3 Very High Memory size series ...al-machines/sizes/memory-optimized/mdsv3-vhm-series.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation lists compatible OS images for the VM series, mentioning Windows Server first, followed by Linux distributions. No command-line examples, tooling, or configuration steps are provided for either platform, and no Windows-specific tools or PowerShell examples are present. The only minor bias is the ordering of Windows before Linux in the compatibility list.
Recommendations
  • List Linux distributions before or alongside Windows Server in the compatible images section to avoid implicit prioritization.
  • If future documentation includes examples or tooling, ensure both Windows and Linux instructions are provided and presented with parity.
GitHub Create Pull Request
Virtual Machines Best practices for virtual machine cost optimization ...s/virtual-machines/cost-optimization-best-practices.md
Low 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 recommendations (e.g., 'Use at least B2 for Windows machines', 'Azure Hybrid Benefit for Windows Server') are given without equivalent Linux guidance. Windows licensing cost optimization is discussed, but not Linux licensing. In several places, Windows is mentioned before Linux (e.g., VM pricing links). There are no Linux-specific cost-saving tips, and automation examples/tools are generic (Logic Apps, Azure Automation) but lack platform-specific scripts or examples.
Recommendations
  • Add Linux-specific cost optimization tips, such as recommendations for Linux VM series, disk types, and licensing options (e.g., mention that Linux VMs do not incur OS licensing costs).
  • Provide parity in recommendations, e.g., if Azure Hybrid Benefit for Windows Server is mentioned, clarify that Linux does not require similar licensing.
  • When linking to pricing or VM size pages, present Linux and Windows options equally (not Windows first).
  • Include Linux-specific automation examples or scripts where relevant.
  • Explicitly state when recommendations apply to both platforms, or call out differences.
GitHub Create Pull Request
Service Fabric Azure Service Fabric releases ...ocs/blob/main/articles/service-fabric/release-notes.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page for Azure Service Fabric releases demonstrates a mild Windows bias. Several sections, especially in releases 8.x, 9.x, and earlier, reference Windows-specific configuration properties (e.g., 'windowsConfiguration.enableAutomaticUpdates'), Windows-only tools (Web Platform Installer, Visual Studio), and update/patching patterns. Windows configuration options are often mentioned before Linux equivalents, and some features/tools are described as available for Windows clusters with Linux support mentioned as an add-on or afterthought. However, there is evidence of Linux support and parity in recent releases, including explicit mentions of Ubuntu support and Linux configuration options.
Recommendations
  • When describing configuration properties (such as VM scale set OS updates), always mention both Windows and Linux equivalents, or clarify if a feature is Windows-only.
  • For tooling and SDK installation, include Linux/macOS instructions and alternatives alongside Windows tools (e.g., avoid referencing Web Platform Installer without listing Linux package managers or CLI options).
  • If a feature is available on both platforms, present Linux and Windows options side-by-side, rather than listing Windows first.
  • Highlight Linux-specific improvements and support in the same detail as Windows features.
  • Ensure that all code samples, configuration snippets, and operational guidance include Linux/macOS variants where applicable.
GitHub Create Pull Request
Service Fabric Describing Azure Service Fabric apps and services ...ic/service-fabric-application-and-service-manifests.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page exhibits mild Windows bias by recommending Visual Studio (a Windows-centric tool) and referencing a local Windows file path for schema validation. The only tool-specific guidance is for Windows, with no mention of Linux/macOS alternatives for editing or validating manifest files. However, the manifest examples themselves are platform-neutral XML, and most content is conceptual.
Recommendations
  • Add instructions for validating manifest XML schema on Linux/macOS, such as using VS Code, xmllint, or other cross-platform editors.
  • Mention cross-platform locations or methods for accessing the ServiceFabricServiceModel.xsd schema (e.g., via NuGet package or GitHub), not just the Windows SDK path.
  • Include references to Linux/macOS-compatible development environments and tools alongside Visual Studio.
  • If PowerShell or Windows-specific deployment tools are mentioned elsewhere, ensure CLI or REST API alternatives are documented.
GitHub Create Pull Request
Virtual Machines HBv3-series virtual machine (VM) overview, architecture, topology - Azure Virtual Machines | Microsoft Docs ...main/articles/virtual-machines/hbv3-series-overview.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ recommended_windows ⚠ī¸ missing_mac_example
Summary
The documentation is generally cross-platform and provides Linux-centric tooling examples (e.g., lstopo). However, there is a subtle Windows bias: Windows is listed first in OS support and recommendations, and the 'Recommended OS for Performance' is Windows Server 2019+, with no equivalent Linux recommendation. There are no macOS-specific examples or recommendations, and no PowerShell or Windows-only tooling is shown.
Recommendations
  • Provide recommended Linux distributions and versions for optimal performance, similar to the Windows recommendation.
  • List Linux and Windows OS support in alphabetical or neutral order, or explicitly state parity.
  • Include macOS notes if relevant, or clarify its support status.
  • If recommending Windows for performance, explain why and whether Linux can achieve similar results.
  • Add Linux-specific performance tuning tips if available.
GitHub Create Pull Request
Virtual Machines Create a Gallery for Sharing Resources .../blob/main/articles/virtual-machines/create-gallery.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 for Azure Portal, Azure CLI, PowerShell, and REST API. While CLI and REST are cross-platform, PowerShell is Windows-centric and is presented as a primary tab for creating galleries. The order of examples consistently lists PowerShell before REST, and the CLI examples use Bash-style syntax (which is cross-platform but may be less familiar to Windows users). There are no explicit Linux/macOS-specific instructions or troubleshooting notes, but the presence and prominence of PowerShell examples may signal a slight Windows bias.
Recommendations
  • Clarify that Azure CLI commands work on Windows, Linux, and macOS, and provide example shell environments if needed.
  • Consider listing CLI examples before PowerShell to emphasize cross-platform support.
  • Add notes or links for Linux/macOS users about installing and using Azure CLI.
  • If PowerShell is shown, mention that PowerShell Core is available for Linux/macOS, or provide equivalent Bash scripts for resource creation.
  • Ensure troubleshooting and environment setup instructions are not Windows-centric.
GitHub Create Pull Request
Service Fabric Add a node type to an Azure Service Fabric cluster ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/virtual-machine-scale-set-scale-node-type-scale-out.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page demonstrates mild Windows bias: file paths in configuration examples use Windows-style (e.g., 'D:\\SvcFab'), and the only link for standalone cluster scaling refers specifically to Windows Server. There are no explicit Linux/macOS examples, nor are Linux file paths or tools mentioned. However, the main instructions are Azure-centric and not OS-specific.
Recommendations
  • Provide configuration examples using Linux-style file paths (e.g., '/var/svcfab') alongside Windows paths.
  • Clarify whether the steps and configuration apply equally to Linux-based Service Fabric clusters.
  • Include links or instructions for scaling standalone clusters on Linux, if supported.
  • Explicitly mention OS differences, if any, in node type configuration or management.
GitHub Create Pull Request
Virtual Machine Scale Sets Create and encrypt a Virtual Machine Scale Set with Azure Resource Manager templates ...e-scale-sets/disk-encryption-azure-resource-manager.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation lists both Linux and Windows options for template deployment, but in the 'Next steps' section, Windows/PowerShell resources are mentioned before Linux/Azure CLI equivalents. Additionally, the sample template link in the note references a Windows example only, which may create friction for Linux users seeking parity.
Recommendations
  • In 'Next steps', list Azure CLI (Linux-friendly) resources before or alongside PowerShell resources.
  • Provide sample template links for both Linux and Windows scenarios in notes and examples.
  • Ensure that examples and references are balanced between Linux and Windows, or clearly labeled for each platform.
GitHub Create Pull Request
Virtual Machines Best Practices for Azure VM Image Builder ...icles/virtual-machines/image-builder-best-practices.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation references both Shell and PowerShell scripts as customizer artifacts, but does not provide explicit Linux shell examples or mention Linux tools. The examples and guidance are generic, but PowerShell is mentioned alongside Shell, which may imply a Windows-first approach. No Linux-specific patterns or tools are discussed, and no Linux/macOS command examples are given.
Recommendations
  • Provide explicit examples for both Linux shell scripts (e.g., Bash) and Windows PowerShell scripts in customizer/validator sections.
  • Mention Linux-specific tools or patterns where relevant, such as using Bash, sh, or cloud-init for Linux VMs.
  • Ensure that any references to scripts or artifacts clarify which OS they apply to, and offer parity in guidance for both platforms.
  • Include links to Linux documentation or best practices for image customization.
GitHub Create Pull Request
Service Fabric Service Fabric Azure Resource Manager deployment guardrails ...ic/service-fabric-azure-resource-manager-guardrails.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation lists Windows Server cluster creation as the first 'Next steps' link, placing Windows before Linux. However, the main content is platform-neutral and does not provide OS-specific examples or instructions.
Recommendations
  • Present Linux and Windows cluster creation links in parallel or in alphabetical order to avoid implying priority.
  • Explicitly state that the guidance applies equally to both Windows and Linux deployments, if true.
  • Ensure future examples and troubleshooting steps include both Windows and Linux-specific instructions where relevant.
GitHub Create Pull Request
Virtual Machines Azure CLI - Enable customer-managed keys with SSE - managed disks ...chines/linux/disks-enable-customer-managed-keys-cli.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation is primarily Linux-friendly, using Azure CLI and Bash-style scripting throughout, which is cross-platform. However, there is some Windows bias in the 'Next steps' section, where PowerShell-based disaster recovery guides for VMware and Hyper-V are highlighted, and Windows-centric scenarios are mentioned before Linux equivalents. There are no explicit PowerShell examples in the main body, but the linked resources and some terminology (e.g., 'PowerShell' and 'Hyper-V') are Windows-specific.
Recommendations
  • Add equivalent Linux/macOS instructions or links for disaster recovery scenarios currently covered only with PowerShell.
  • Where PowerShell is referenced, clarify that Azure CLI or Bash alternatives exist, and provide those alternatives.
  • Ensure that Linux and macOS users are not required to use Windows-only tools for any critical workflows.
  • Balance the order of presenting Windows and Linux scenarios in 'Next steps' and throughout the documentation.
GitHub Create Pull Request
Virtual Machines Expand Virtual Hard Disks on a Linux VM ...b/main/articles/virtual-machines/linux/expand-disks.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation is strongly Linux-focused throughout, with all main examples and instructions using Linux commands, tools, and distributions. However, there is a single section at the end ('Expand without downtime classic VM SKU support') that provides only a PowerShell script for determining classic VM SKU support, without any Bash/Azure CLI/Linux equivalent. This creates a minor bias for users on Linux/macOS who may not have access to PowerShell.
Recommendations
  • Provide an equivalent Bash/Azure CLI script or command to check classic VM SKU support for expanding disks without downtime.
  • Where PowerShell is used, offer cross-platform alternatives or clarify if the operation is only possible via PowerShell.
  • Explicitly state platform requirements for any Windows-specific tooling or scripts.
GitHub Create Pull Request
Service Fabric Plan an Azure Service Fabric cluster deployment ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-azure-deployment-preparation.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation generally treats Windows and Linux equally in terms of cluster support, but in the 'Next steps' section, the link to creating a Windows cluster is listed before the Linux cluster link. No examples, tools, or patterns are given that are Windows-specific, and there are no PowerShell-heavy or Windows-only instructions. However, the ordering of links could subtly signal a Windows-first bias.
Recommendations
  • List the Linux and Windows cluster creation links together, or alternate their order in different documentation sections.
  • Explicitly state that all configuration and deployment steps apply equally to both Windows and Linux clusters where relevant.
  • If examples or code snippets are added in future, ensure parity by providing both Windows and Linux versions.
GitHub Create Pull Request
Service Fabric Upgrade the configuration of an Azure Service Fabric cluster ...-fabric/service-fabric-cluster-config-upgrade-azure.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page demonstrates mild Windows bias by listing PowerShell-based methods before Azure CLI equivalents and referencing PowerShell-specific commands (Set-AzServiceFabricSetting, Remove-AzServiceFabricSetting) prominently. While Azure CLI options are mentioned, PowerShell is given precedence, which may create friction for Linux/macOS users who typically use CLI tools.
Recommendations
  • List Azure CLI methods before or alongside PowerShell methods to avoid implying preference for Windows tools.
  • Provide explicit examples for both Azure CLI and PowerShell commands, ensuring parity in instructions for Linux/macOS users.
  • Clarify that Azure CLI is cross-platform and suitable for Linux/macOS environments.
  • Avoid referencing PowerShell-specific commands without also providing CLI equivalents.
GitHub Create Pull Request
Virtual Machines VM Snapshot extension using VM restore points ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/virtual-machines-restore-points-vm-snapshot-extension.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page exhibits mild Windows bias by referencing Windows-specific technologies (VSS) first and in more detail, and mentioning Windows extension and log paths before their Linux equivalents. Troubleshooting guidance is focused on VSS writer issues, which are Windows-specific, with no equivalent Linux troubleshooting example or detail.
Recommendations
  • Present Linux and Windows information in parallel, rather than Windows-first.
  • Expand troubleshooting guidance to include common Linux-specific issues and their resolution steps.
  • Provide equal detail for Linux mechanisms (pre-/postscripts) as is given for VSS on Windows.
  • Ensure log file locations and extension names for both platforms are presented together or in a neutral order.
GitHub Create Pull Request
Virtual Machine Scale Sets Creating and configuring a key vault for Azure Disk Encryption ...irtual-machine-scale-sets/disk-encryption-key-vault.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 mentions Azure CLI, Azure PowerShell, and Azure portal as supported tools, but places Azure PowerShell (a Windows-centric tool) prominently alongside Azure CLI. The 'Next steps' section lists PowerShell examples before CLI, and there are no explicit Linux/macOS-specific instructions or examples, nor any mention of platform-specific considerations. There is a subtle bias toward Windows tools and workflows.
Recommendations
  • Ensure Azure CLI examples are shown first, as CLI is cross-platform.
  • Explicitly mention that Azure CLI works on Linux/macOS and provide installation links for those platforms.
  • Add Linux/macOS-specific notes or troubleshooting tips where relevant.
  • Balance PowerShell and CLI coverage, or clarify when PowerShell is required.
  • Consider adding Bash shell examples for common tasks.
GitHub Create Pull Request
Virtual Machine Scale Sets Create virtual machines in a Flexible scale set using Azure portal ...ale-sets/flexible-virtual-machine-scale-sets-portal.md
Low 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 mild Windows bias: password requirements link to a Windows-specific FAQ, and Windows terminology is referenced before Linux equivalents. While Linux options (SSH keys, supported distros) are mentioned, examples and links prioritize Windows resources, and Linux-specific guidance is less detailed.
Recommendations
  • Provide direct links to Linux password/username requirements, not just Windows FAQ.
  • Ensure Linux and Windows examples are presented with equal detail and prominence.
  • Include explicit Linux-focused screenshots or walkthroughs where applicable.
  • Reference Linux documentation first or alongside Windows resources when discussing OS-specific features.
GitHub Create Pull Request
Virtual Machines Create Virtual Machine restore points ...ain/articles/virtual-machines/create-restore-points.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 page demonstrates mild Windows bias by referencing PowerShell and Windows-specific features before Linux equivalents. PowerShell is mentioned as a primary tool for interacting with restore points, while Linux CLI options are only referenced later and less prominently. The documentation also highlights application consistency for Windows VMs and file system consistency for Linux VMs, suggesting more robust support for Windows. No Linux-specific command-line examples or tools are provided, and Windows terminology (PowerShell) appears before CLI or REST API options.
Recommendations
  • Provide Linux-specific CLI examples (e.g., Azure CLI commands) alongside or before PowerShell examples.
  • Include explicit instructions or links for Linux users, such as Bash shell usage and relevant tools.
  • Balance the discussion of consistency models by clarifying support levels for both Windows and Linux.
  • Ensure that REST API usage is presented as the primary, cross-platform method, with platform-specific tools as secondary options.
GitHub Create Pull Request
Virtual Machines Enable shared disks for Azure managed disks .../main/articles/virtual-machines/disks-shared-enable.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for all disk types and operations, but PowerShell examples are given equal prominence and detail as CLI, and in some cases, PowerShell is listed first (e.g., in 'Share an existing disk' and 'Using Azure shared disks with your VMs'). PowerShell is a Windows-centric tool, and its heavy usage and occasional ordering before CLI may create friction for Linux/macOS users. However, Azure CLI examples are present for all operations, and no critical steps are Windows-only.
Recommendations
  • Ensure Azure CLI examples are always listed before PowerShell, as CLI is cross-platform.
  • Explicitly state that all CLI commands work on Linux/macOS and Windows.
  • Add bash scripting examples for common Linux automation scenarios.
  • Where PowerShell is used for VM operations, provide equivalent Azure CLI or ARM template examples.
  • Clarify in the prerequisites that PowerShell is optional and not required for Linux/macOS users.
GitHub Create Pull Request
Virtual Machines Ephemeral OS disks ...b/main/articles/virtual-machines/ephemeral-os-disks.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ minor_windows_example
Summary
The documentation is generally cross-platform and includes both Linux and Windows information. However, there are minor instances of Windows bias: Windows examples or references are sometimes presented before Linux equivalents, and Windows-specific tools (e.g., PowerShell) are mentioned before Linux tools (CLI). There are also a few sections where Windows-specific details are highlighted without a Linux counterpart, such as page file placement.
Recommendations
  • Ensure that Linux and Windows examples are always presented together or alternate which comes first.
  • Where Windows-specific details are given (e.g., page file placement), provide equivalent Linux information or explicitly state if not applicable.
  • In sections referencing tools (e.g., PowerShell, CLI), always mention both platforms' tools together and provide parallel links/examples.
  • Review tables and feature lists to ensure Linux-specific behaviors or caveats are equally documented.
GitHub Create Pull Request
Virtual Machines Azure Linux VM Agent Overview ...in/articles/virtual-machines/extensions/agent-linux.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_reference
Summary
The documentation is strongly Linux-focused and does not provide Windows/Powershell examples or prioritize Windows tools. However, there is a notable mention of Windows-specific tooling (putty.exe) and a reference to a Windows VM deployment tutorial in the Ubuntu Cloud Images section. These inclusions may distract Linux users or create minor confusion, but do not prevent Linux users from completing tasks.
Recommendations
  • Remove or clarify the reference to putty.exe in the SSH key section, or provide equivalent Linux SSH client guidance.
  • Replace or supplement the Windows VM deployment tutorial link in the Ubuntu Cloud Images section with a Linux-focused deployment tutorial.
  • Ensure all external links and examples are relevant to Linux users, especially in sections explicitly about Linux VM management.
GitHub Create Pull Request
Service Fabric Overview of Service Fabric and containers ...s/service-fabric/service-fabric-containers-overview.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation generally presents Windows and Linux parity, but there is a slight Windows bias: Windows container scenarios and tools (IIS, Windows Server, Mirantis Container Runtime) are described in more detail, and Windows examples or links are often listed before Linux equivalents. The IIS lift-and-shift scenario is Windows-specific, and references to Windows container images and tools are more prominent than Linux alternatives. There is no evidence of missing Linux examples, but Windows-centric tools and patterns are mentioned first or exclusively in some sections.
Recommendations
  • Ensure Linux examples and tutorials are listed before or alongside Windows equivalents, not after.
  • Add equivalent Linux-specific scenarios (e.g., Apache/Nginx lift-and-shift) to balance the IIS example.
  • Mention Linux container runtimes and tools (e.g., Podman, containerd) where relevant, not just Docker.
  • Provide parity in detail for both Windows and Linux container orchestration and deployment workflows.
  • Highlight Linux-specific capabilities or challenges in Service Fabric where applicable.
GitHub Create Pull Request
Virtual Machines Availability options for Azure Virtual Machines ...cs/blob/main/articles/virtual-machines/availability.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation is generally cross-platform, but there is mild Windows bias in the Load Balancer section, where PowerShell is mentioned as an example tool alongside CLI, and the PowerShell example link is listed after the CLI link. No Linux-specific tools (e.g., Bash, shell scripts) are mentioned, and there is no explicit parity in example coverage for Linux/macOS users. However, the overall content applies to both Linux and Windows VMs, and most links and next steps reference Linux-focused guides.
Recommendations
  • Explicitly mention Linux/macOS tools (e.g., Bash, Azure CLI in Bash) where PowerShell is referenced.
  • Ensure example links for both CLI and PowerShell are provided for all major tasks, and clarify which are cross-platform.
  • Consider listing CLI (cross-platform) examples before PowerShell (Windows-centric) examples to reduce perceived bias.
  • Add a note clarifying that Azure CLI works on Linux/macOS and Windows, and provide links to installation guides for all platforms.
GitHub Create Pull Request
Virtual Machines Boot integrity monitoring overview ...virtual-machines/boot-integrity-monitoring-overview.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: Windows examples and terminology (such as PowerShell and Windows extension publisher names) are presented before Linux equivalents. The PowerShell section is included as a top-level tab, while there is no equivalent Bash or shell scripting tab for Linux. The troubleshooting section references Windows extension names in error messages, and screenshots consistently show Windows-centric UI elements. However, Linux template examples are provided, and CLI instructions are generally cross-platform.
Recommendations
  • Present Linux and Windows examples side-by-side, or alternate which is shown first.
  • Add a Bash or shell scripting tab alongside PowerShell for parity.
  • In troubleshooting, mention both Windows and Linux extension names in error messages.
  • Include screenshots or instructions that reflect Linux environments where relevant.
  • Clarify that CLI instructions apply to both Windows and Linux, and note any platform-specific differences.
GitHub Create Pull Request
Virtual Machines Use xrdp with Linux .../articles/virtual-machines/linux/use-remote-desktop.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation is primarily focused on Linux, but in the section about creating a Network Security Group rule for Remote Desktop traffic, both Azure CLI and Azure PowerShell examples are provided. The PowerShell example is given equal prominence, which may be unnecessary for Linux users. Additionally, references to using SSH from Windows are present before Linux equivalents, and links to Windows-specific documentation are included. However, the core instructions for installing and configuring xrdp are Linux-centric and do not rely on Windows-only tools.
Recommendations
  • Move Linux/Azure CLI examples before PowerShell examples, or clearly mark PowerShell as optional for Windows users.
  • Add explicit notes clarifying that PowerShell is primarily for Windows administrators, and that Linux users should use Azure CLI.
  • Ensure that links to SSH documentation for Linux/macOS are provided before or alongside Windows links.
  • Consider removing or de-emphasizing Windows-specific tooling in Linux-focused documentation unless strictly necessary.
GitHub Create Pull Request
Virtual Machines vCPU quotas ...ute-docs/blob/main/articles/virtual-machines/quotas.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 PowerShell examples for checking vCPU quotas, but the PowerShell example is given equal prominence despite being primarily a Windows tool. There is no explicit Linux bias, but the presence of PowerShell examples may suggest a Windows-centric approach, especially since PowerShell is traditionally associated with Windows environments, even though it is now cross-platform. The CLI example is shown first, which is positive for Linux parity.
Recommendations
  • Clarify that PowerShell is available cross-platform, or note its installation on Linux/macOS if relevant.
  • Consider adding Bash shell scripting examples for Linux users, especially for automation.
  • Explicitly mention that Azure CLI works natively on Linux/macOS and Windows.
  • If possible, provide example outputs from Linux/macOS terminals to reinforce cross-platform support.
GitHub Create Pull Request
Virtual Machines Proximity placement groups ...ocs/blob/main/articles/virtual-machines/co-location.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 page demonstrates mild Windows bias. In sections discussing how to check colocation status, PowerShell is mentioned before CLI, and the PowerShell cmdlet is described in more detail. In the best practices section, the Windows accelerated networking guide is listed after the Linux guide, but both are present. References to PowerShell and CLI are present throughout, but there are no Linux shell script examples or explicit parity for Linux-specific tooling. The next steps section links to both Linux (CLI) and Windows (PowerShell) guides, but the page does not provide in-page command examples for either platform.
Recommendations
  • When listing tools or commands, alternate the order (e.g., CLI before PowerShell in some sections) or present them together.
  • Include explicit Linux shell (bash) examples where relevant, not just CLI references.
  • Ensure that Linux and macOS users are addressed in all command-line instructions, not just via CLI.
  • Add a note clarifying parity between Windows and Linux workflows, especially for tasks that can be completed using either CLI or PowerShell.
  • Consider adding a table summarizing commands for both platforms side-by-side.
GitHub Create Pull Request
Virtual Machines Support matrix for VM restore points ...n/articles/virtual-machines/concepts-restore-points.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation presents Windows operating system support details before Linux, listing specific Windows versions and then referencing Linux distributions. No command-line examples or tooling are provided in this page, but the ordering prioritizes Windows information. There is no evidence of exclusive Windows tools, PowerShell-heavy examples, or missing Linux equivalents in this page.
Recommendations
  • Present Windows and Linux operating system support in parallel or alphabetical order to avoid perceived prioritization.
  • Ensure that any referenced 'Next steps' documentation (CLI, Portal, PowerShell) includes Linux-friendly examples and tools, such as Bash/CLI commands.
  • Explicitly mention Linux-specific considerations or features where relevant, to provide parity in detail.
GitHub Create Pull Request
Virtual Machine Scale Sets Resilient create and delete for Virtual Machine Scale Sets (Preview) ...rtual-machine-scale-sets/resilient-vm-create-delete.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides examples for enabling Resilient create and delete using Azure Portal, CLI, PowerShell, and REST API. PowerShell is presented as a distinct tab, which is primarily a Windows tool, and its presence may indicate a slight Windows bias. However, the CLI examples use Azure CLI, which is cross-platform, and REST API examples are platform-agnostic. The documentation does not provide Linux-specific shell examples (e.g., bash scripts), but the CLI commands are suitable for Linux/macOS. There is a minor bias in that PowerShell is given equal prominence to CLI, and no explicit Linux shell scripting guidance is provided.
Recommendations
  • Add explicit bash or shell script examples for Linux/macOS users, especially for automation scenarios.
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows.
  • Consider mentioning cross-platform compatibility in the prerequisites or introduction.
  • If PowerShell is shown, consider also showing equivalent bash scripting for parity.
GitHub Create Pull Request
Virtual Machine Scale Sets Create a scale set that uses Azure Spot Virtual Machines ...b/main/articles/virtual-machine-scale-sets/use-spot.md
Low 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 provides examples for Azure CLI, PowerShell, ARM templates, and REST API. While Azure CLI and ARM templates are cross-platform, PowerShell is Windows-centric and is given equal prominence. The REST API example references a Windows-specific documentation link for further information. There is a slight Windows bias in the ordering and references, and Linux-specific examples or troubleshooting are missing, especially in the PowerShell and REST API sections.
Recommendations
  • Add explicit Linux/macOS troubleshooting or usage notes, especially for PowerShell (e.g., mention Azure PowerShell on Linux, or alternatives).
  • Ensure REST API follow-up links include both Linux and Windows examples, not just Windows.
  • Where PowerShell is mentioned, clarify cross-platform support or provide Bash/shell alternatives if available.
  • In the ARM template section, provide a direct Linux-focused example, not just a generic template.
  • Review ordering so that cross-platform tools (CLI, ARM) are presented before Windows-centric tools (PowerShell).
GitHub Create Pull Request
Service Fabric Create a Linux container app on Service Fabric in Azure ...e-fabric/service-fabric-quickstart-containers-linux.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_example_in_cleanup
Summary
The documentation is strongly focused on Linux, with all main examples and instructions using Linux tools and workflows. However, in the 'Clean up resources' section, Windows certificate removal is described first and in more detail than macOS or Ubuntu, and the Windows-specific Certificates MMC snap-in is mentioned. This is a minor instance of Windows bias in an otherwise Linux-centric guide.
Recommendations
  • Provide equally detailed instructions for removing certificates on Ubuntu and macOS, possibly with step-by-step screenshots or commands.
  • List Linux/macOS certificate removal instructions before Windows, or present all platforms in parallel for parity.
  • Ensure that any references to Windows tools are matched with equivalent Linux/macOS instructions throughout the documentation.
GitHub Create Pull Request
Container Instances Execute commands in running container instance ...ticles/container-instances/container-instances-exec.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation provides both Linux (Bash) and Windows (Command Prompt) examples for executing commands in running Azure container instances. However, the Windows example is given equal prominence and detail, and Windows-specific tools (cmd.exe) are mentioned explicitly. There is a slight tendency to present Windows patterns and terminology (e.g., Command Prompt, Windows output) alongside or before Linux equivalents, and no mention of macOS-specific considerations.
Recommendations
  • Ensure Linux examples are presented first, as Linux containers are more common in cloud scenarios.
  • Include macOS-specific notes if there are differences in Azure CLI usage or terminal behavior.
  • Clarify that Azure CLI works cross-platform and highlight any platform-specific caveats.
  • Balance example output: provide more Linux container outputs, as these are typical for most users.
  • Add troubleshooting tips for Linux/macOS users if there are known issues with az container exec.
GitHub Create Pull Request
Container Instances Get standby pool for Azure Container Instances details ...tances/container-instances-standby-pool-get-details.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides examples for Azure CLI, PowerShell, and REST API. PowerShell, a Windows-centric tool, is given its own tab and example, which may not be directly usable on Linux/macOS. The CLI example is cross-platform, but PowerShell is listed before REST, and no Bash or Linux shell-specific examples are provided. There is a slight Windows bias due to the inclusion and prominence of PowerShell.
Recommendations
  • Add explicit Bash or shell script examples for Linux/macOS users, especially for parsing CLI output.
  • Clarify that Azure CLI commands work on all platforms and highlight platform-neutral approaches.
  • Consider listing CLI examples before PowerShell to emphasize cross-platform usage.
  • If PowerShell is included, mention PowerShell Core compatibility for Linux/macOS.
GitHub Create Pull Request
Container Instances Quickstart - create a container instance - Bicep ...iner-instances/container-instances-quickstart-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 examples for all commands, but PowerShell (a Windows-centric tool) is given equal prominence to the cross-platform CLI, and is always shown immediately after the CLI example. There are no Linux-specific shell examples (e.g., bash scripting), but the CLI is cross-platform. No Windows-only tools are required, and Linux users can complete all tasks using the CLI commands provided.
Recommendations
  • Clearly indicate that Azure CLI is fully supported on Linux/macOS and is the recommended tool for cross-platform use.
  • Consider listing Azure CLI examples first and PowerShell second, or grouping PowerShell in a separate section to emphasize CLI as the default.
  • Add a note clarifying that PowerShell examples are primarily for Windows users, and that Linux/macOS users should use the CLI.
  • Optionally, provide bash script snippets for common automation scenarios to further support Linux users.
GitHub Create Pull Request
Azure Impact Reporting Azure Impact Reporting Connectors for Azure Monitor: FAQ ...main/articles/azure-impact-reporting/connectors-faq.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 examples for enabling debug mode and verifying connector creation, but PowerShell is mentioned alongside Bash in every example, and the PowerShell example uses the Az PowerShell module, which is Windows-centric. There is no explicit mention of Linux-specific tools or troubleshooting, and PowerShell is presented as the alternative to Bash, which may imply a Windows-first approach. However, Bash examples are present and shown first in each case.
Recommendations
  • Include explicit Linux/macOS troubleshooting steps or notes where relevant.
  • Mention cross-platform compatibility of Azure CLI and PowerShell Core.
  • Add examples using native Linux tools (e.g., curl, jq) for REST API calls.
  • Clarify that PowerShell examples are compatible with PowerShell Core on Linux/macOS.
  • Consider adding a table summarizing commands for Windows, Linux, and macOS.
GitHub Create Pull Request
Service Fabric Develop .NET Core applications with Visual Studio Code ...ervice-fabric-develop-csharp-applications-with-vs-code.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation provides both Windows and Linux instructions for opening VS Code with elevated privileges, but Windows instructions are consistently presented before Linux equivalents. All other steps and examples are OS-agnostic, leveraging VS Code's integrated terminal and cross-platform commands. No PowerShell-specific commands, Windows-only tools, or missing Linux examples are present.
Recommendations
  • Present Linux and Windows instructions in parallel or in the order matching the stated cross-platform intent.
  • Explicitly confirm that all subsequent steps (build, deploy, debug) are identical across platforms, or note any differences.
  • Where possible, use neutral language (e.g., 'terminal window' instead of 'command window on Windows') and clarify any platform-specific terminology.
GitHub Create Pull Request
Service Fabric Create an Azure Service Fabric container application on Linux ...-fabric/service-fabric-get-started-containers-linux.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 is generally Linux-focused, but there are a few instances of Windows bias. The most notable is the instruction to 'Open a PowerShell window' for Docker commands, which is not appropriate for Linux users. There are also references to Windows-specific concepts (e.g., named pipes for Docker daemon communication) and some minor ordering bias (Windows selector appears before Linux). However, all critical steps and examples are provided for Linux, and Linux tools are used throughout.
Recommendations
  • Replace 'Open a PowerShell window' with 'Open a terminal window' or 'Open a shell' for Linux instructions.
  • Ensure all command-line examples use Linux shell syntax and terminology.
  • Where Windows-specific concepts are mentioned (e.g., named pipes), clarify the Linux equivalent (e.g., unix domain sockets) and provide Linux-specific instructions first.
  • Consider listing Linux before Windows in selectors and examples, especially on Linux-focused pages.
  • Audit for any lingering references to Windows tools or patterns and replace with Linux equivalents.
GitHub Create Pull Request
Azure Impact Reporting Azure Impact Reporting: Create an Azure Monitor Alert Connector ...ure-impact-reporting/create-azure-monitor-connector.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 provides both Bash and PowerShell script examples for connector creation, but PowerShell examples are listed before Bash, and the script naming conventions (e.g., .ps1) may imply a Windows-first approach. There is no explicit mention of Linux/macOS compatibility or requirements for running Bash scripts, nor troubleshooting guidance specific to Linux/macOS environments. The portal instructions are platform-neutral, but command-line sections could better address Linux parity.
Recommendations
  • List Bash and PowerShell examples side-by-side or alternate which is shown first to avoid implicit prioritization.
  • Explicitly state that Bash scripts are supported on Linux/macOS and provide any prerequisites (e.g., required Azure CLI version, permissions).
  • Add troubleshooting steps or notes for common Linux/macOS issues (e.g., script execution permissions, shell compatibility).
  • Clarify that both Bash and PowerShell scripts are available and supported equally, and provide links to platform-specific setup guides if needed.
GitHub Create Pull Request
Service Fabric Reliable Collection object serialization ...c-reliable-services-reliable-collections-serialization.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 page demonstrates a mild Windows bias, primarily in the 'Next steps' section. It lists Windows-centric tools (Visual Studio and PowerShell) for application upgrades, with no mention of Linux/macOS equivalents or cross-platform alternatives. The main content is platform-neutral, focusing on .NET APIs and serialization concepts, but the guidance for upgrade workflows assumes Windows environments.
Recommendations
  • Add instructions or links for upgrading applications using cross-platform tools such as Azure CLI or Service Fabric CLI.
  • Include references to Linux/macOS-compatible development environments (e.g., VS Code, JetBrains Rider) alongside Visual Studio.
  • Provide parity in example workflows for application upgrades on Linux/macOS, not just PowerShell and Visual Studio.
  • Clarify which features and APIs are cross-platform, and note any platform-specific limitations.
GitHub Create Pull Request
Virtual Machine Scale Sets Migrate deployments and resources to Virtual Machine Scale Sets in Flexible orchestration ...lexible-virtual-machine-scale-sets-migration-resources.md
Low 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 scenarios (such as VM activation and Windows updates) are mentioned before Linux equivalents, and troubleshooting links are provided only for Windows activation. There are no explicit Linux-focused migration examples, nor are Linux-specific tools or troubleshooting resources referenced. The Azure CLI is used for examples, which is cross-platform, but no Linux-specific shell commands or package manager details are given.
Recommendations
  • Add explicit Linux migration scenarios and troubleshooting resources, such as links to common Linux VM issues or activation steps.
  • Include examples or notes for Linux package manager outbound connectivity (e.g., apt, yum, zypper) and how to ensure access for updates.
  • Provide parity in troubleshooting links, such as a reference to Linux VM connectivity or update problems.
  • When listing outbound connectivity requirements, mention Linux package manager access before or alongside Windows activation and updates.
  • Consider including bash or shell script examples for common tasks, not just Azure CLI.
GitHub Create Pull Request
Virtual Machine Scale Sets Understand the health state of your standby pool ...rtual-machine-scale-sets/standby-pools-health-state.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides example commands for Azure CLI, PowerShell, and REST API. While Azure CLI is cross-platform and shown first, PowerShell (a Windows-centric tool) is given its own section and example, which may imply Windows preference. There are no explicit Linux/macOS shell examples (e.g., Bash/cURL), nor is there mention of Linux-specific usage patterns. REST API usage is shown generically, but without Linux-oriented command-line examples.
Recommendations
  • Add explicit Bash/cURL examples for Linux/macOS users in the API section.
  • Clarify that Azure CLI works on Linux/macOS and provide sample output for those platforms.
  • Consider including links or notes about installing Azure CLI and PowerShell on non-Windows platforms.
  • Ensure parity in troubleshooting and next steps for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Azure Service Fabric versions ...ain/articles/service-fabric/service-fabric-versions.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation presents Windows information and tables before Linux equivalents, both in navigation and in the order of sections. Windows OS support details are more extensive and appear first, while Linux support is covered later and with less detail. There are no Windows-only examples or tools, and Linux parity is generally maintained in the version tables.
Recommendations
  • Present Windows and Linux sections in parallel or alternate their order to avoid implicit prioritization.
  • Ensure Linux OS support tables are as detailed as Windows ones (e.g., include more distributions if supported).
  • Add explicit navigation aids for Linux users at the top of the page.
  • Review and balance the depth of OS lifecycle information for both platforms.
GitHub Create Pull Request
Virtual Machine Scale Sets Delete or update a standby pool for Virtual Machine Scale Sets ...tual-machine-scale-sets/standby-pools-update-delete.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 provides both Azure CLI and PowerShell examples for updating and deleting standby pools, but PowerShell examples are presented alongside CLI in every section, and deployment instructions for ARM and Bicep templates mention PowerShell's New-AzResourceGroupDeployment before CLI's az deployment group create. This ordering and emphasis on PowerShell and Windows-centric tools may create friction for Linux/macOS users, though CLI and REST options are available.
Recommendations
  • Present CLI examples before PowerShell examples, as CLI is cross-platform and preferred by many Linux/macOS users.
  • When listing deployment commands for ARM and Bicep templates, mention az deployment group create before New-AzResourceGroupDeployment.
  • Add explicit notes clarifying that all CLI commands work on Linux/macOS, and link to installation guides for Azure CLI on those platforms.
  • Consider adding bash script examples or references to shell scripting for Linux users.
  • Review screenshots and UI instructions to ensure they are not Windows-specific (e.g., avoid showing Windows-only features in portal screenshots).
GitHub Create Pull Request
Container Instances Configure custom DNS settings for container group in Azure Container Instances .../container-instances/container-instances-custom-dns.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation page is generally Linux/Bash-focused, but the main container example uses the official PowerShell image (mcr.microsoft.com/powershell) and names the container 'pwsh-vnet-dns', which may signal a Windows/PowerShell bias. However, all CLI instructions are Bash-formatted and the container is explicitly set to Linux. There are no Windows-only instructions, but the choice of PowerShell as the demonstration image may be confusing or less relevant for Linux-first users.
Recommendations
  • Use a more neutral or Linux-native container image (e.g., Ubuntu, Alpine, or nginx) for the example YAML.
  • Provide alternative YAML examples using a common Linux image.
  • Clarify that the PowerShell image is cross-platform and not Windows-specific, or explain why it was chosen.
  • Consider renaming the container and resource to something less PowerShell-specific.
  • Explicitly mention that all steps are applicable to Linux/macOS users and provide any necessary adjustments for Windows users (e.g., line continuation characters).
GitHub Create Pull Request
Virtual Machine Scale Sets Change the upgrade policy mode on Virtual Machine Scale Sets ...ts/virtual-machine-scale-sets-change-upgrade-policy.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides separate tabs for Portal, CLI, PowerShell, and ARM Template methods. While CLI and ARM Template are cross-platform, PowerShell is Windows-centric and is given equal prominence. There is no explicit Linux shell example (e.g., Bash), and PowerShell is presented as a primary method, which may imply Windows bias. The CLI example is cross-platform, but PowerShell is a Windows-first tool and its inclusion without a Linux shell equivalent may create friction for Linux/macOS users.
Recommendations
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows, and consider adding a Bash shell example or note for Linux/macOS users.
  • Indicate that PowerShell is primarily for Windows users, or provide guidance for using PowerShell Core on Linux/macOS if relevant.
  • Consider reordering tabs so that cross-platform methods (CLI, ARM Template) are shown before Windows-centric ones (PowerShell).
  • Add explicit statements about platform compatibility for each method.
GitHub Create Pull Request
Virtual Machine Scale Sets Attach or detach a virtual machine to or from a Virtual Machine Scale Set ...le-sets/virtual-machine-scale-sets-attach-detach-vm.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ minor_windows_links
Summary
The documentation provides parity between Azure CLI and Azure PowerShell examples for all major operations (attach, detach, update), and both are cross-platform tools. However, PowerShell (traditionally Windows-centric) is always presented as a primary scripting alternative, and some troubleshooting links and migration steps reference Windows-specific documentation (e.g., converting unmanaged disks, proximity placement groups) that point to Windows VM docs. Azure CLI is shown before PowerShell, which is positive, but the persistent inclusion of PowerShell and Windows documentation links introduces a mild Windows bias.
Recommendations
  • Ensure all troubleshooting and migration links have Linux equivalents or point to OS-agnostic documentation (e.g., proximity placement group removal, disk conversion).
  • Where possible, clarify that Azure CLI and PowerShell are both cross-platform, and consider adding Bash or shell script examples for common tasks to reinforce Linux parity.
  • Audit linked documentation to ensure Linux users are not redirected to Windows-only guides.
  • Explicitly state that Azure CLI and PowerShell are available on Linux/macOS, and provide installation links for these platforms.
  • If referencing PowerShell, consider also referencing Bash or other Linux-native scripting where appropriate.
GitHub Create Pull Request
Virtual Machine Scale Sets Set the upgrade policy mode on Virtual Machine Scale Sets ...-sets/virtual-machine-scale-sets-set-upgrade-policy.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation presents Windows-centric tools (PowerShell) and lists PowerShell examples before ARM template examples, but does include Azure CLI examples, which are cross-platform. There is a mild ordering bias, with PowerShell (Windows) shown before ARM templates, and no explicit mention of Linux/macOS alternatives for scripting or automation. However, the CLI section uses Ubuntu in its example, which helps Linux parity.
Recommendations
  • Explicitly state that Azure CLI is cross-platform and can be used on Linux/macOS/Windows.
  • Consider listing CLI examples before PowerShell to emphasize cross-platform support.
  • Add a note clarifying that PowerShell Core is available on Linux/macOS, or provide Bash scripting examples for Linux users.
  • Ensure ARM template examples are given equal prominence as scripting options for all platforms.
GitHub Create Pull Request
Virtual Machine Scale Sets Get high availability and cost savings with Spot Priority Mix for Virtual Machine Scale Sets ...ticles/virtual-machine-scale-sets/spot-priority-mix.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides platform-specific instructions for configuring Spot Priority Mix via the Azure Portal, Azure CLI, and Azure PowerShell. The CLI examples use Ubuntu images, which is Linux-friendly, but the PowerShell examples are given equal prominence and detail. The tab order presents Portal first (cross-platform), then CLI (Linux/macOS/Windows), then PowerShell (Windows-only), but PowerShell is included throughout. There are no Linux shell-specific examples (e.g., Bash scripts), and no mention of Linux-specific tools or patterns. However, the CLI instructions are fully usable on Linux/macOS, and the ARM template method is platform-neutral.
Recommendations
  • Add explicit Bash shell examples for Linux users, especially for scripting or automation.
  • Clarify that Azure CLI is cross-platform and can be used on Linux/macOS/Windows.
  • Consider moving PowerShell examples after CLI examples, or labeling them as Windows-only.
  • Add a note about platform compatibility for each method.
  • Include troubleshooting tips for Linux users (e.g., CLI installation on Linux).
GitHub Create Pull Request
Virtual Machine Scale Sets Get standby pool and instance details ...irtual-machine-scale-sets/standby-pools-get-details.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for all major operations, but PowerShell is given equal prominence as CLI, and is the only shell scripting example shown (no Bash, Linux shell, or macOS-specific guidance). PowerShell is a Windows-centric tool, and its inclusion alongside CLI can create a perception of Windows bias, especially as there are no Linux/macOS-specific shell examples or troubleshooting notes. However, the Azure CLI examples are cross-platform and shown first, mitigating the severity.
Recommendations
  • Add Bash or shell scripting examples for Linux/macOS users, especially for parsing JSON output or automating tasks.
  • Explicitly state that Azure CLI commands work on Windows, Linux, and macOS.
  • Include troubleshooting notes for Linux/macOS environments (e.g., authentication, environment setup).
  • Clarify that PowerShell examples are optional and primarily for Windows users.
  • Consider adding links to platform-specific setup guides for Azure CLI and PowerShell.
GitHub Create Pull Request
Virtual Machine Scale Sets Get Prediction Results for Standby pools for Virtual Machine Scale Sets (Preview) ...machine-scale-sets/standby-pools-prediction-results.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides examples for Azure CLI, PowerShell, and REST API. However, the PowerShell example is given equal prominence to the CLI, and PowerShell is a Windows-centric tool. There is no mention of Linux/macOS-specific shell usage (e.g., Bash), nor are there examples tailored for Linux users (such as using curl for REST calls or jq for parsing). The ordering of examples (CLI, then PowerShell, then REST) is common, but the inclusion of PowerShell as a primary tab can be seen as Windows-first. No explicit Windows-only tools are referenced, but the lack of Linux/macOS-specific guidance or troubleshooting tips is notable.
Recommendations
  • Add Bash and curl examples for REST API calls to demonstrate Linux/macOS usage.
  • Include notes or examples using jq for parsing JSON output in Linux/macOS environments.
  • Clarify that Azure CLI is cross-platform and provide troubleshooting tips for Linux/macOS users if relevant.
  • Consider reordering tabs or explicitly stating cross-platform compatibility to avoid perceived Windows-first bias.
  • Add a section or note for Linux/macOS users about environment setup or differences, if any.
GitHub Create Pull Request
Virtual Machine Scale Sets Automatic instance repairs with Azure Virtual Machine Scale Sets ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-automatic-instance-repairs.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides examples and instructions for Azure PowerShell, Azure CLI, REST API, and Azure Portal. However, PowerShell examples are consistently present and detailed, and in several sections (especially creation and update flows), PowerShell is listed before CLI. The documentation references PowerShell-specific cmdlets and patterns, which are primarily Windows-centric, and does not mention Linux/macOS-specific shell usage (e.g., bash, zsh) or alternative scripting environments. There are no explicit Linux/macOS shell script examples, nor any mention of OS-specific considerations for CLI usage.
Recommendations
  • Add explicit bash/zsh shell script examples for Azure CLI commands, showing usage on Linux/macOS (e.g., environment variable syntax, quoting, file redirection).
  • Clarify that Azure CLI commands work cross-platform and provide notes or tips for Linux/macOS users (e.g., installation, authentication differences, file path conventions).
  • Balance the order of examples so that CLI and REST API instructions are shown before or alongside PowerShell, not after.
  • Where PowerShell is referenced, note that it is available cross-platform, but provide links or instructions for Linux/macOS installation if relevant.
  • If there are any OS-specific caveats (e.g., for health extension endpoints, networking, or authentication), call them out explicitly.
GitHub Create Pull Request
Virtual Machine Scale Sets Automatic OS image upgrades with Azure Virtual Machine Scale Sets ...e-sets/virtual-machine-scale-sets-automatic-upgrade.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ minor_windows_config_details
Summary
The documentation provides both Windows and Linux information, but there is a mild Windows bias. Windows-specific configuration details (e.g., enableAutomaticUpdates property, drive letter reassignment) are mentioned explicitly and sometimes before Linux equivalents. PowerShell examples are given alongside Azure CLI, but PowerShell is a Windows-centric tool. ARM template and Bicep examples default to Windows images. No Linux-specific troubleshooting or configuration nuances are discussed, and Windows configuration properties are described in more detail.
Recommendations
  • Add Linux-specific configuration details and troubleshooting steps, such as handling /etc/fstab for data disk mounting after upgrades.
  • In ARM template and Bicep examples, alternate between Windows and Linux images or provide parallel examples for both.
  • Clarify that Azure CLI is cross-platform and highlight its parity with PowerShell for Linux/macOS users.
  • When discussing OS-specific properties (e.g., enableAutomaticUpdates), explicitly state the Linux equivalent or clarify that it is not needed.
  • Include Linux-first or at least Linux-equal examples in all code sections, especially where Windows properties or behaviors are described.
  • Add notes or links to Linux-specific upgrade behaviors, such as package manager updates, disk mounting, and extension compatibility.
GitHub Create Pull Request
Virtual Machine Scale Sets Autoscale Virtual Machine Scale Sets in the Azure portal ...le-sets/virtual-machine-scale-sets-autoscale-portal.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page primarily describes how to configure autoscale rules for Azure Virtual Machine Scale Sets using the Azure portal, which is cross-platform. However, references to command-line alternatives (Azure PowerShell and Azure CLI) consistently list PowerShell before CLI, and the 'Next steps' section links only to PowerShell-based management documentation, omitting CLI or Linux-native options. This ordering and emphasis may subtly favor Windows users and workflows.
Recommendations
  • When mentioning command-line alternatives, list Azure CLI before or alongside PowerShell to reflect cross-platform parity.
  • In the 'Next steps' section, include links to both Azure CLI and PowerShell management guides.
  • Explicitly state that both Azure CLI and PowerShell are available on Windows, Linux, and macOS, and provide links to installation guides for each platform.
  • Where possible, provide example links for both PowerShell and CLI in parallel, rather than only PowerShell.
GitHub Create Pull Request
Virtual Machine Scale Sets Reimage a virtual machine in a scale set ...https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-reimage-virtual-machine.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 for Azure Portal, Azure CLI, Azure PowerShell, and REST API. While the CLI and REST API are cross-platform, the PowerShell example is Windows-centric and is presented as a top-level tab alongside CLI, rather than as a secondary or alternative option. The ordering of tabs places PowerShell before REST, and the PowerShell example is not explicitly marked as Windows-only, which may imply parity or preference. There are no Linux-specific shell examples (e.g., Bash), nor is there mention of Linux/macOS nuances for CLI usage.
Recommendations
  • Clarify that PowerShell examples are primarily for Windows users and suggest alternatives for Linux/macOS users.
  • Add explicit Bash shell examples for the Azure CLI to demonstrate usage on Linux/macOS.
  • Consider reordering tabs so that cross-platform tools (CLI, REST) appear before Windows-specific tools (PowerShell).
  • Include notes or callouts about platform compatibility for each example.
GitHub Create Pull Request
Virtual Machine Scale Sets Rolling upgrades with MaxSurge for Virtual Machine Scale Sets ...hine-scale-sets/virtual-machine-scale-sets-maxsurge.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides configuration instructions for rolling upgrades with MaxSurge using the Azure Portal, Azure CLI, PowerShell, and ARM templates. The PowerShell example is included as a dedicated tab, which is primarily a Windows tool. The CLI example uses Azure CLI, which is cross-platform, but the PowerShell example is given equal prominence, suggesting a Windows-centric approach. No Linux-specific tools or shell examples (e.g., Bash scripts) are provided, nor are there any references to Linux/macOS-specific considerations. The order of examples places Portal (web), CLI, PowerShell, and ARM Template, with PowerShell appearing before ARM Template, which may subtly prioritize Windows users.
Recommendations
  • Add explicit Bash shell examples for Linux/macOS users, demonstrating equivalent Azure CLI commands.
  • Clarify that Azure CLI works on Linux/macOS and provide any OS-specific notes if needed.
  • Consider adding a note about PowerShell Core availability on Linux/macOS, or clarify if the PowerShell example is Windows-only.
  • Review the ordering of examples to avoid implicit prioritization of Windows tools.
  • Include troubleshooting or configuration notes relevant to Linux/macOS environments if applicable.
GitHub Create Pull Request
Virtual Machine Scale Sets Networking for Azure Virtual Machine Scale Sets ...ne-scale-sets/virtual-machine-scale-sets-networking.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 provides both Azure CLI and PowerShell examples for most networking tasks, but PowerShell (a Windows-centric tool) is frequently presented before CLI, and some sections (such as querying public IPs) give more detailed PowerShell examples. Windows-specific scenarios (like Windows VM activation) are mentioned explicitly, while Linux/macOS equivalents are not discussed. There is a slight tendency to mention or demonstrate Windows tools and patterns before their cross-platform or Linux alternatives.
Recommendations
  • Present CLI examples before PowerShell, or side-by-side, to emphasize cross-platform parity.
  • Ensure all PowerShell examples have equivalent CLI examples, especially for querying and management tasks.
  • Include Linux/macOS-specific notes or troubleshooting where Windows-specific scenarios are discussed (e.g., VM activation).
  • Add explicit statements that all CLI commands work on Linux/macOS, and clarify any platform-specific differences.
  • Review example links and references to ensure Linux templates/examples are as visible as Windows ones.
GitHub Create Pull Request
Virtual Machine Scale Sets Performing manual upgrades on Virtual Machine Scale Sets ...https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-perform-manual-upgrades.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides parity across Azure Portal, CLI, PowerShell, and REST API, but the PowerShell section is given equal prominence to the CLI, and PowerShell is a Windows-centric tool. The CLI section uses Azure CLI, which is cross-platform, but PowerShell is not as common on Linux/macOS. The 'Next steps' section lists Azure CLI before PowerShell, but both are mentioned. There are no Linux-specific tools or shell examples (e.g., bash scripts), but the CLI example is sufficient for Linux users.
Recommendations
  • Clarify that Azure CLI commands work cross-platform and are recommended for Linux/macOS users.
  • Consider adding a bash script example or explicitly noting that the CLI example is suitable for Linux/macOS.
  • If PowerShell is included, mention that it is primarily for Windows users (unless cross-platform PowerShell is supported and common).
  • Ensure that Linux/macOS users are not left uncertain about which method to use.
GitHub Create Pull Request
Virtual Machine Scale Sets Create an Azure scale set that uses Availability Zones ...s/virtual-machine-scale-sets-use-availability-zones.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 provides both Azure CLI and Azure PowerShell examples for creating and updating scale sets with Availability Zones, but PowerShell (Windows-centric) examples are given equal prominence and detail as CLI. The ARM template section references both Linux and Windows, but the main walkthroughs and update instructions do not show explicit Linux shell commands or workflows. The order of presentation often puts PowerShell before REST API or ARM templates, and there are no bash-specific or Linux-native instructions for updating scale sets. This creates mild friction for Linux/macOS users, who may prefer bash or native shell commands over PowerShell.
Recommendations
  • Add explicit bash/Linux shell examples for all CLI commands, including update operations.
  • Clarify that Azure CLI is fully cross-platform and highlight its use for Linux/macOS users.
  • Consider presenting CLI (bash) examples before PowerShell in each section to signal parity.
  • Include troubleshooting or environment setup notes for Linux/macOS users where relevant.
  • Where PowerShell is used, note that it is available cross-platform, but provide bash alternatives.
GitHub Create Pull Request
Virtual Machines Customer intent: "As a cloud architect, I want to develop a robust backup and disaster recovery strategy for my Azure VMs and their managed disks, so that my organization can ensure data availability and minimize downtime during outages or data loss incidents." ...s/backup-and-disaster-recovery-for-azure-iaas-disks.md
Low 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 mild Windows bias in several areas. Windows tools and patterns (e.g., Volume Shadow Service, SQL Server Always On) are mentioned before or in more detail than their Linux equivalents. Application-consistent backup for Windows (VSS) is described with more specificity, while Linux alternatives (fsfreeze) are mentioned briefly and with less clarity. SQL Server (Windows-centric) is referenced repeatedly, with less coverage of Linux database backup strategies. There are no explicit PowerShell examples, but the overall framing and tool references favor Windows environments.
Recommendations
  • Provide equal detail for Linux backup tools (e.g., describe how to use fsfreeze, LVM snapshots, or other Linux-native mechanisms for application-consistent backups).
  • Include examples and references for Linux database backup strategies (e.g., PostgreSQL, MySQL, MongoDB), not just SQL Server and Oracle.
  • When discussing coordinated backup, offer step-by-step Linux procedures alongside Windows VSS explanations.
  • Add links to Linux-specific documentation for backup and disaster recovery on Azure.
  • Ensure that both Windows and Linux scenarios are presented with parity in detail and guidance.
GitHub Create Pull Request
Virtual Machines Share a Capacity Reservation Group in Azure ...s/virtual-machines/capacity-reservation-group-share.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 provides examples for API, Azure CLI, PowerShell, and ARM templates for all major operations. PowerShell is featured as a primary automation tool, and PowerShell examples are present for every operation, sometimes with more detail than CLI. References to PowerShell commands and modules are frequent, and links to PowerShell documentation are provided before or alongside CLI links. There is no explicit Linux shell scripting (e.g., Bash) or macOS-specific guidance, and PowerShell is a Windows-native tool (though cross-platform now), which may signal a Windows-centric approach. However, Azure CLI is cross-platform and is included for all tasks, mitigating the bias somewhat.
Recommendations
  • Add explicit Bash shell script examples for Linux/macOS users, especially for automation scenarios.
  • Clarify that Azure CLI commands work equally on Linux, macOS, and Windows, and provide platform-specific notes if there are differences.
  • Reorder examples to present CLI (cross-platform) before PowerShell, or alternate the order to avoid implicit prioritization.
  • Include troubleshooting or environment setup notes for Linux/macOS users (e.g., installing Azure CLI, using Bash, etc.).
  • Mention that PowerShell Core is available cross-platform, but provide Bash alternatives for users who prefer native Linux/macOS tools.
GitHub Create Pull Request
Virtual Machines Migrate from Azure Disk Encryption to encryption at host ...n/articles/virtual-machines/disk-encryption-migrate.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ minor_example_ordering
Summary
The documentation generally provides parity for both Windows and Linux, with clear callouts for OS-specific limitations and steps. However, there is a subtle Windows bias in the ordering of examples and instructions: Windows steps and PowerShell commands are often listed before Linux equivalents, and Windows-specific tools (e.g., manage-bde, Remove-Computer) are mentioned first. PowerShell is used heavily for both OSes, but Linux-specific shell commands are present. There are no critical missing Linux instructions, but the structure and ordering may create minor friction for Linux users.
Recommendations
  • Alternate the order of Windows and Linux instructions/examples to avoid always presenting Windows first.
  • Where possible, provide Bash/shell script examples for Linux tasks alongside PowerShell for Windows, especially in verification and management steps.
  • Highlight Linux-specific tools and commands with equal prominence as Windows tools (e.g., give 'cryptsetup' and 'lsblk' the same emphasis as 'manage-bde').
  • Consider adding a summary table or section at the top outlining the differences and steps for both OSes, so Linux users can quickly find relevant information.
  • Ensure that all PowerShell-based instructions for Linux are complemented with native Bash/SSH alternatives where appropriate.
GitHub Create Pull Request
Virtual Machines Server-side encryption of Azure managed disks ...blob/main/articles/virtual-machines/disk-encryption.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ minor_windows_reference
Summary
The documentation generally maintains parity between Windows and Linux, referencing both Azure PowerShell and Azure CLI for most tasks. However, there are several instances of Windows bias: Windows/PowerShell links and examples are consistently listed before Linux/CLI equivalents, PowerShell is mentioned more frequently (e.g., for revoking access), and Windows-specific tools (BitLocker, CNG API) are referenced with less emphasis on Linux equivalents (DM-Crypt). Some conceptual sections link to Windows documentation or tools first, and the automatic key rotation walkthrough is only linked to a Windows/PowerShell guide.
Recommendations
  • Alternate the order of Windows and Linux examples/links so Linux is not always second.
  • Ensure every PowerShell example or link is paired with an equivalent CLI/bash example or link.
  • Add explicit references to Linux tools (e.g., DM-Crypt) wherever Windows tools (BitLocker, CNG API) are mentioned.
  • Provide a Linux/CLI guide for automatic key rotation, not just a Windows/PowerShell version.
  • Where possible, use neutral language (e.g., 'Azure CLI or PowerShell') rather than listing Windows tools first.
  • Include Linux/macOS-specific troubleshooting or caveats if any exist.
GitHub Create Pull Request
Virtual Machines Benchmark your application on Azure Disk Storage ...lob/main/articles/virtual-machines/disks-benchmarks.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation mentions both Windows and Linux VMs are supported, and references both DiskSpd (Windows) and FIO (Linux) as benchmarking tools. However, DiskSpd (Windows) is mentioned first, and the introductory text gives slightly more prominence to Windows by listing its tool before Linux. There are no explicit examples shown for either platform, but the ordering and tool references suggest a mild Windows-first bias.
Recommendations
  • Alternate the order of tool mentions (e.g., 'FIO and DiskSpd') or mention both together to avoid implicit prioritization.
  • Provide explicit example commands for both Windows (DiskSpd) and Linux (FIO) to ensure parity.
  • Include links to installation and usage guides for both tools, not just their homepages.
  • Consider a table or side-by-side comparison of benchmarking steps for Windows and Linux.
GitHub Create Pull Request
Virtual Machines Convert managed disks storage between different disk types .../main/articles/virtual-machines/disks-convert-types.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 provides both Azure PowerShell and Azure CLI examples for all major disk conversion tasks, ensuring cross-platform coverage. However, PowerShell (a Windows-centric tool) is consistently presented first in code example tabs, and PowerShell scripts are shown before CLI scripts in every section. There are references to converting unmanaged disks with 'CLI' (Linux) or 'PowerShell' (Windows), but the links are clearly separated. The documentation does not use Windows-only tools or patterns in the actual conversion steps, but the ordering and prominence of PowerShell may subtly favor Windows users.
Recommendations
  • Alternate the order of example tabs so that Azure CLI is shown first in some sections, especially for tasks commonly performed on Linux.
  • Explicitly state that both PowerShell and CLI are fully supported on Windows, Linux, and macOS, and clarify that CLI is cross-platform.
  • Add a short note at the top explaining that the examples are equivalent and users should choose the tool that matches their environment.
  • Consider including Bash or shell script snippets for common Linux workflows if relevant.
  • Ensure parity in documentation links for converting unmanaged disks, perhaps by grouping them together and clarifying platform applicability.
GitHub Create Pull Request
Virtual Machines Use a disk encryption set across Microsoft Entra tenants ...l-machines/disks-cross-tenant-customer-managed-keys.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 referencing PowerShell and Windows installation instructions before Linux alternatives, and by linking specifically to 'Install Azure PowerShell on Windows with PowerShellGet'. However, all major tasks are also covered with Azure CLI and ARM/REST API examples, which are cross-platform. No critical functionality is locked to Windows-only tools.
Recommendations
  • Add explicit instructions or links for installing Azure PowerShell on Linux/macOS alongside the Windows instructions.
  • Clarify that both Azure PowerShell and Azure CLI are cross-platform, and provide parity in example ordering (e.g., alternate which is shown first or present both together).
  • Where installation instructions are referenced, link to the general Azure PowerShell installation page, not just the Windows-specific guide.
  • Consider adding a note that all shown CLI/PowerShell commands work on Linux/macOS unless otherwise stated.
GitHub Create Pull Request
Virtual Machines Create an incremental snapshot ...ticles/virtual-machines/disks-incremental-snapshots.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 (cross-platform) and Azure PowerShell (Windows-centric) examples for all major tasks, but consistently presents PowerShell examples immediately after CLI and with equal prominence. There is no explicit Linux shell scripting or macOS-specific guidance, and PowerShell examples are detailed and assume familiarity with Windows tooling. No Linux-specific tools or troubleshooting are mentioned, and the CLI examples use Bash syntax, which is cross-platform but not explicitly called out as Linux/macOS friendly.
Recommendations
  • Add explicit Linux/macOS shell scripting notes, such as mentioning that Azure CLI commands work natively in Bash/Zsh on Linux/macOS.
  • Provide troubleshooting or environment setup notes for Linux/macOS users (e.g., permissions, package managers, etc.).
  • Clarify that PowerShell examples are primarily for Windows users, and suggest alternatives for Linux/macOS users where appropriate.
  • Consider adding example scripts using other popular Linux tools (e.g., curl, jq) for querying Azure APIs.
  • Where possible, present CLI examples before PowerShell, or clearly mark CLI as the recommended cross-platform approach.
GitHub Create Pull Request
Virtual Machines Enable end-to-end encryption using encryption at host - Azure portal - managed disks ...-machines/disks-enable-host-based-encryption-portal.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 Azure PowerShell (commonly used on Windows) examples before Azure CLI in command sections, referencing PowerShell in links and resource samples, and providing links to PowerShell-based guides and samples. However, Azure CLI examples are present for all commands, and the portal instructions are platform-neutral. No critical Linux functionality is missing.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or present CLI examples first to better support Linux/macOS users.
  • Include direct links to Linux/macOS-specific guides and samples alongside PowerShell resources.
  • Clarify that Azure CLI is cross-platform and highlight its usage for Linux/macOS users.
  • Ensure parity in referenced sample repositories (e.g., provide CLI-based sample templates).
GitHub Create Pull Request
Virtual Machines Change the performance of Azure managed disks ...n/articles/virtual-machines/disks-performance-tiers.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 provides parallel examples for Azure CLI and Azure PowerShell, with PowerShell being a Windows-centric tool. While Azure CLI is cross-platform, the presence of PowerShell examples and terminology throughout the page reflects a Windows bias. There is no explicit mention of Linux/macOS shell usage (e.g., bash, zsh), and PowerShell instructions are given equal prominence to CLI, which may not be relevant for Linux users. The documentation does not provide Linux-specific command-line nuances or highlight Linux shell scripting patterns. However, Azure CLI examples are present and shown first in each section, which helps mitigate the bias.
Recommendations
  • Add explicit notes clarifying that Azure CLI commands work on Linux/macOS and Windows, while PowerShell is primarily for Windows.
  • Include Linux/macOS shell-specific instructions or troubleshooting tips where relevant (e.g., environment variable syntax differences).
  • Consider adding bash/zsh script examples for common tasks, or at least mention that Azure CLI commands can be run in those shells.
  • Clarify that PowerShell is optional and not required for Linux/macOS users.
  • Ensure parity in troubleshooting and advanced usage sections for Linux users.
GitHub Create Pull Request
Virtual Machines What's new in Azure Disk Storage ...blob/main/articles/virtual-machines/disks-whats-new.md
Low 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 is mostly a changelog and summary of new features, but there are several instances where Windows-specific links, terminology, or examples are presented before or instead of Linux equivalents. For example, links to Windows documentation (e.g., /azure/virtual-machines/windows/expand-disks) are given before Linux links, and some references point only to Windows-specific tools (PowerShell, Windows portal) or documentation. There are also cases where Linux parity is implied but not directly addressed, and some links or examples are missing Linux-specific guidance.
Recommendations
  • Ensure that every feature or example referencing Windows has a corresponding Linux/macOS example or documentation link.
  • When listing links for expanding disks or other operations, present Linux and Windows options together, or alternate which is listed first.
  • Avoid referencing Windows-specific tools (e.g., PowerShell) without mentioning equivalent Linux/macOS tools (e.g., Azure CLI, Bash scripts).
  • Audit linked documentation to ensure Linux/macOS users can complete all tasks described.
  • Add explicit notes when a feature is Windows-only or has different instructions for Linux/macOS.
GitHub Create Pull Request
Virtual Machines Azure Disk Encryption for Linux ...es/virtual-machines/extensions/azure-disk-enc-linux.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation is focused on Azure Disk Encryption for Linux and provides Linux-centric schema and deployment examples. However, in the warning section, the PowerShell cmdlet (Get-AzVMDiskEncryptionStatus) is mentioned before the Azure CLI equivalent (az vm encryption show) for checking encryption status. PowerShell is primarily a Windows tool, and listing it first may suggest a Windows-centric approach, even though the CLI is cross-platform. No Linux-specific command-line examples (e.g., bash, shell scripts) are provided for interacting with the extension or troubleshooting, and the troubleshooting/support sections do not reference Linux-native tools.
Recommendations
  • List Azure CLI commands before PowerShell cmdlets when describing cross-platform tasks, as CLI is natively supported on Linux/macOS.
  • Provide Linux-native command-line examples (e.g., bash, shell scripts) for interacting with the extension and troubleshooting.
  • Explicitly mention that PowerShell Core is available on Linux, if PowerShell examples are retained.
  • Reference Linux troubleshooting tools (e.g., journalctl, dmesg, systemctl) for diagnosing extension issues.
GitHub Create Pull Request
Virtual Machines Enable InfiniBand on HPC VMs - Azure Virtual Machines | Microsoft Docs ...icles/virtual-machines/extensions/enable-infiniband.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 provides both Linux and Windows guidance for enabling InfiniBand on Azure HPC VMs. However, there is a mild Windows bias in the VM extension section, where Azure PowerShell is mentioned as the tool for adding extensions without an equivalent Linux CLI example (such as Azure CLI or ARM template). Windows tools and deployment models are referenced before Linux alternatives. Linux manual installation and configuration steps are well-covered, but Windows users are directed to download drivers without detailed installation steps.
Recommendations
  • Provide Azure CLI and/or ARM template examples for adding VM extensions alongside PowerShell.
  • Mention Linux tools (e.g., az CLI) before or alongside Windows tools when discussing VM extension management.
  • Add more detailed Windows installation steps for Mellanox OFED drivers, similar to the Linux section.
  • Ensure parity in troubleshooting and operational guidance for both platforms.
GitHub Create Pull Request
Virtual Machines Create an image definition and image version ...s/blob/main/articles/virtual-machines/image-version.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides parity between Linux and Windows in most CLI and REST examples, but there is a subtle Windows bias in the PowerShell section, where Windows is used as the default example and Linux is mentioned only as an alternative. Additionally, PowerShell examples are given equal prominence to CLI, which is more cross-platform, but PowerShell is primarily a Windows tool. In the 'Before you begin' section, Linux guidance is more extensive, but Windows instructions are presented as a single block, potentially implying Windows as the default. The ordering of examples sometimes places Windows first.
Recommendations
  • Alternate the order of Linux and Windows examples so neither is always first.
  • Provide explicit Linux PowerShell (pwsh) compatibility notes, or clarify that CLI is recommended for Linux/macOS users.
  • In PowerShell examples, use Linux as the default in at least one example, or provide parallel Linux and Windows examples.
  • Add a note at the start of the PowerShell section clarifying its platform support and recommending CLI for Linux/macOS.
  • Ensure that all example code blocks and parameter tables clearly indicate which OS they apply to, and provide Linux/macOS equivalents where relevant.
GitHub Create Pull Request
Virtual Machines Dedicated hosts include file ...es/virtual-machines/includes/dedicated-hosts-resize.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 for three interfaces: Portal, CLI, and PowerShell. The PowerShell section is given its own tab and detailed example, which is a Windows-centric tool. The CLI instructions use Azure CLI, which is cross-platform, but the PowerShell example is included as a primary method, potentially suggesting Windows as a first-class platform. There are no Linux/macOS-specific shell examples (e.g., Bash), nor is there mention of platform-specific considerations for non-Windows users.
Recommendations
  • Add explicit Bash or shell examples for Linux/macOS users, especially for scripting resize operations.
  • Clarify that Azure CLI commands work identically on Linux, macOS, and Windows.
  • If PowerShell is mentioned, note that PowerShell Core is available cross-platform, or provide Bash alternatives.
  • Consider reordering tabs or examples so that cross-platform methods (CLI) are presented before Windows-specific ones (PowerShell).
GitHub Create Pull Request
Virtual Machines Customer intent: As a system administrator, I want to restrict uploads and downloads for Azure managed disks using identity verification, so that I can enforce security policies and ensure only authorized users can access sensitive data. ...ines/includes/disks-azure-ad-upload-download-portal.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page presents PowerShell examples and references before Azure CLI, and mentions PowerShell as a primary method for role assignment and disk configuration. While Azure CLI examples are provided, the ordering and emphasis suggest a Windows-first approach, which may create friction for Linux/macOS users who typically prefer CLI or Bash-based workflows.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples, as CLI is cross-platform.
  • Explicitly mention Linux/macOS compatibility for CLI commands.
  • Add Bash or shell script examples where appropriate.
  • Clarify that PowerShell is available on Linux/macOS, or link to installation instructions if PowerShell is required.
  • Ensure screenshots and UI references are not Windows-specific.
GitHub Create Pull Request
Virtual Machines Customer intent: As a cloud administrator, I want to benchmark disk performance using custom I/O workloads, so that I can optimize storage configurations for maximum read and write IOPS in my virtual machines. ...ncludes/virtual-machines-managed-disks-benchmarking.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation presents Windows (DISKSPD) benchmarking instructions and examples before Linux (FIO) equivalents, but both platforms are covered with detailed, parallel guidance. No critical Linux omissions or Windows-only tooling are present.
Recommendations
  • Reorder sections to present Linux (FIO) examples before or alongside Windows (DISKSPD) examples.
  • Add a brief comparison table summarizing tool usage for both platforms at the top.
  • Explicitly mention cross-platform alternatives for each tool where relevant.
  • Clarify that both DISKSPD and FIO are platform-specific and provide links to installation guides for both.
GitHub Create Pull Request
Virtual Machines Connect to a Linux VM ...lob/main/articles/virtual-machines/linux-vm-connect.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 provides both Linux/macOS and Windows instructions for connecting to a Linux VM via SSH. However, in the Windows tab, the example for validating the SSH fingerprint uses Azure PowerShell (Invoke-AzVMRunCommand), while the Linux tab uses a direct SSH command. The Windows section also references PowerShell and Windows-specific paths. The main page and prerequisites mention Windows tools (WSL, Win32 OpenSSH) and provide guidance for Windows users before Linux/macOS equivalents. The overall structure does not exclude Linux users, but Windows tools and patterns are mentioned first or in more detail in some places.
Recommendations
  • Provide parity in fingerprint validation: Offer a direct Azure CLI example for Windows users, not just PowerShell.
  • When referencing SSH clients, mention Linux/macOS tools first or equally alongside Windows tools.
  • Ensure that troubleshooting and next steps include Linux/macOS-specific guidance where relevant.
  • Balance the order of examples so Linux/macOS instructions are not always after Windows-specific notes.
  • Where possible, avoid assuming the user is on Windows when describing general Azure portal steps.
GitHub Create Pull Request
Virtual Machines Azure Instance Metadata Service for virtual machines ...articles/virtual-machines/instance-metadata-service.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 provides both Windows (PowerShell) and Linux (bash/curl) examples for all core usage scenarios, including requests and responses. However, in several places, Windows/PowerShell examples are presented before Linux equivalents, and some troubleshooting and advanced scenarios (e.g., routing table checks, Azure CLI usage) use PowerShell syntax or Windows tools first, with Linux instructions following. There is a slight emphasis on Windows tools and PowerShell, but Linux parity is generally maintained.
Recommendations
  • Alternate the order of Windows and Linux examples, or present them side-by-side to avoid implicit prioritization.
  • Ensure troubleshooting steps and CLI examples are equally detailed for Linux (e.g., use Azure CLI and bash for interface and routing checks, not just PowerShell).
  • Where Windows-specific tools (e.g., route print, ipconfig) are mentioned, ensure Linux equivalents (e.g., ip, netstat, ifconfig) are listed with equal prominence.
  • Consider adding macOS-specific notes or examples where applicable, especially for curl/jq usage.
  • Review the language in troubleshooting and FAQs to avoid assuming Windows as the default platform.
GitHub Create Pull Request
Virtual Machines Prepare a Debian Linux VHD ...les/virtual-machines/linux/debian-create-upload-vhd.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation mentions Windows-specific tools (Hyper-V, convert-vhd cmdlet) for VHD creation and conversion before introducing Linux alternatives. While the main workflow is Linux-centric, Windows tools are referenced first and exclusively in some places, which may create confusion or friction for Linux users.
Recommendations
  • Explicitly mention Linux-native tools for VHD creation and conversion (e.g., qemu-img, VBoxManage) alongside or before Windows tools.
  • Provide links or brief instructions for using Linux tools to create and convert VHDs.
  • Reorder sections so Linux methods are presented first, given the page's Linux focus.
  • Clarify that Hyper-V is only one option and highlight Linux alternatives for each step.
GitHub Create Pull Request
Virtual Machines Azure Disk Encryption scenarios on Linux VMs ...ticles/virtual-machines/linux/disk-encryption-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 both Azure CLI and PowerShell examples for all major operations, but PowerShell (a Windows-centric tool) is frequently mentioned first, and some backup/encryption workflows are described primarily in terms of PowerShell cmdlets. Resource Manager template parameter retrieval also shows PowerShell before CLI. There is no evidence of missing Linux examples or exclusive use of Windows tools, but the ordering and emphasis may create friction for Linux/macOS users.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and more natural for Linux/macOS users.
  • Where PowerShell is referenced for parameter retrieval or scripting, ensure equivalent Azure CLI commands are shown first or side-by-side.
  • Clarify that both CLI and PowerShell are supported on Linux/macOS, and recommend CLI for Linux users.
  • Audit for any workflow steps that are described only in PowerShell and add CLI equivalents if missing.
  • In tables and lists, show CLI commands before PowerShell, or group by platform.
GitHub Create Pull Request
Virtual Machines Enable Azure Disk Encryption for Linux VMs ...les/virtual-machines/linux/disk-encryption-overview.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 is focused on enabling Azure Disk Encryption for Linux VMs and is generally Linux-centric. However, there is evidence of Windows bias: PowerShell is referenced multiple times as a primary tool for managing Azure resources, and PowerShell examples/scripts are given equal prominence to Azure CLI (which is more native to Linux). The terminology table includes 'PowerShell cmdlets' as a core concept, while no Linux-specific shell tools (e.g., Bash, Shell scripts) are mentioned. In the 'Next steps' section, PowerShell is listed alongside CLI, and the PowerShell script is referenced before the CLI script in the quickstart links. This may create friction for Linux users who expect Bash or CLI-first workflows.
Recommendations
  • Prioritize Azure CLI and Bash examples/scripts over PowerShell for Linux documentation, as CLI is more native to Linux environments.
  • Move PowerShell references and scripts after CLI/Bash examples in lists and quickstart links.
  • Clarify that PowerShell is cross-platform, but recommend CLI/Bash for Linux users.
  • Add a note in the terminology table about Bash/shell scripting for Linux users.
  • Ensure that all critical workflows have CLI/Bash equivalents and are presented first.
GitHub Create Pull Request
Virtual Machines Azure CLI - Restrict import/export access to managed disks with Private Links ...achines/linux/disks-export-import-private-links-cli.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 is primarily focused on Azure CLI, which is cross-platform and suitable for Linux, macOS, and Windows. However, in the 'Next steps' section, Windows and PowerShell resources are mentioned before Linux equivalents, and PowerShell is given as an alternative to Azure CLI for uploading VHDs, suggesting a Windows-centric approach. Additionally, the download VHD links list Windows before Linux. No Linux-specific tools or shell examples are provided, but the CLI examples themselves are platform-neutral.
Recommendations
  • List Linux/macOS resources and examples before or alongside Windows equivalents in 'Next steps'.
  • Provide Bash or Linux-specific command examples where appropriate, especially for tasks like downloading VHDs.
  • Include references to Linux-native tools (e.g., dd, wget, azcopy) where relevant.
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows equally, and provide explicit instructions for Linux users if any steps differ.
  • Balance PowerShell references with Bash or shell script alternatives.
GitHub Create Pull Request
Virtual Machines Upload a VHD to Azure or copy a disk across regions - Azure CLI ...machines/linux/disks-upload-vhd-to-managed-disk-cli.md
Low 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 in the upload example, where only a Windows-style AzCopy.exe command is shown (with a Windows path and executable), and no explicit Linux/macOS AzCopy usage is demonstrated. The AzCopy tool is referenced using its Windows executable and path format, and Linux/macOS command-line equivalents are not provided. However, most Azure CLI examples use bash syntax and variables, which are cross-platform.
Recommendations
  • Add explicit Linux/macOS AzCopy example, e.g., `azcopy copy /home/user/mydisk.vhd "sas-URI" --blob-type PageBlob`.
  • Mention that AzCopy is available on Linux/macOS and provide installation instructions or a link.
  • Use generic command syntax (e.g., `azcopy` instead of `AzCopy.exe`) and file paths in examples.
  • Clarify that the process is identical on Linux/macOS, and note any OS-specific considerations.
GitHub Create Pull Request
Virtual Machines Learn about hibernating your Linux virtual machine ...icles/virtual-machines/linux/hibernate-resume-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 both Azure CLI and PowerShell examples for enabling hibernation on Linux VMs, but PowerShell examples are always present and shown alongside CLI, sometimes with more detail. In some sections, PowerShell is listed before REST or other Linux-native tools, and the use of PowerShell for Linux VM management is emphasized, which may not be the preferred or most familiar tool for Linux users. However, Linux-specific instructions (bash, package installation) are present and detailed for guest OS configuration.
Recommendations
  • Prioritize Azure CLI and bash examples before PowerShell in all sections, as CLI is more platform-neutral and familiar to Linux users.
  • Clearly indicate that PowerShell is optional and primarily for users who prefer it, rather than presenting it as a default or primary method.
  • Add explicit bash-only examples for VM creation and management where possible, especially for steps that can be completed outside Azure CLI/PowerShell.
  • Consider adding a summary table comparing CLI, PowerShell, and REST options, with recommendations for Linux users.
  • Where REST API is mentioned, include curl/bash examples for Linux users.
  • Remove references to 'git bash' for Ubuntu/Debian instructions, as native bash is standard.
GitHub Create Pull Request
Virtual Machines Azure VM Image Builder networking options ...les/virtual-machines/linux/image-builder-networking.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page presents both Windows and Linux options, but there is a subtle Windows bias. Windows examples and links are often listed before Linux equivalents, and PowerShell is given equal prominence to Azure CLI, despite CLI being more cross-platform. Some sections (e.g., permissions and checklist) consistently show PowerShell examples alongside CLI, but do not provide Bash or Linux-native alternatives. The 'IMPORTANT' note specifically addresses Windows WinRM configuration, with no equivalent Linux SSH note.
Recommendations
  • List Linux/Azure CLI examples before Windows/PowerShell examples to reduce perceived Windows-first bias.
  • Add Bash or Linux-native command examples where only PowerShell is shown.
  • Include notes about Linux-specific configuration changes (e.g., SSH) if Windows-specific notes (WinRM) are present.
  • Clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Ensure parity in troubleshooting and configuration notes for both OS types.
GitHub Create Pull Request
Virtual Machines Run scripts in a Linux VM in Azure using action Run Commands ...ob/main/articles/virtual-machines/linux/run-command.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 is focused on Linux VMs and provides Azure CLI examples as the primary method for running scripts. However, it also includes PowerShell examples and references to PowerShell cmdlets, which are traditionally associated with Windows environments. The PowerShell example is given its own section, and PowerShell is mentioned alongside Azure CLI in several places. There is some implicit Windows bias in the inclusion and prominence of PowerShell, and in the troubleshooting section, Windows logging differences are discussed before Linux specifics. However, the page does not provide Windows-only instructions, and Linux users can complete all tasks described.
Recommendations
  • Clarify that PowerShell examples are cross-platform and can be run on Linux/macOS as well as Windows.
  • Add explicit Bash or shell script examples where appropriate, especially in sections that mention PowerShell.
  • Reorder sections so that Azure CLI and Bash/shell examples appear before PowerShell, emphasizing Linux-native tools.
  • Minimize references to Windows-specific tools or patterns unless directly relevant to Linux VM management.
  • In troubleshooting, lead with Linux log details and only mention Windows differences as a footnote.
GitHub Create Pull Request
Virtual Machines Time sync for Linux VMs in Azure ...blob/main/articles/virtual-machines/linux/time-sync.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_reference
Summary
The documentation is focused on Linux VM time synchronization in Azure and provides thorough Linux-specific guidance and examples. However, there is a notable Windows bias in the introductory sections: Windows Server 2016 time sync improvements are discussed first and in detail, and multiple references to Windows documentation are provided. No Windows-only tools or examples are present, and all configuration instructions and code samples are Linux-centric. The only PowerShell example is for base64 encoding a cloud-init file, which is relevant for Azure ARM template usage and not for time sync configuration itself.
Recommendations
  • Move or minimize Windows Server 2016 details to a background or architecture section, focusing the introduction on Linux VM time sync challenges and solutions.
  • Provide parity in references: link to Linux time sync architecture documentation (e.g., chrony, ntpd, systemd-timesyncd) in the introduction, not just Windows resources.
  • Clarify that the PowerShell example is for Azure deployment and not for time sync configuration, and offer a Linux shell equivalent for base64 encoding if relevant.
  • Ensure that 'Next steps' and reference sections include Linux-focused resources as prominently as Windows ones.
GitHub Create Pull Request
Virtual Machines Use a template to deploy Azure Spot Virtual Machines .../main/articles/virtual-machines/linux/spot-template.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation provides a cross-platform Resource Manager template example for deploying Azure Spot VMs, with explicit mention that it applies to Linux VMs. However, in the 'Next steps' section, the link to the Azure PowerShell method (Windows-centric) is listed before the Azure CLI method (cross-platform), indicating a minor 'windows_first' bias. No PowerShell-heavy content, exclusive Windows tools, or missing Linux examples are present.
Recommendations
  • List Azure CLI (cross-platform) before Azure PowerShell in the 'Next steps' section to avoid implying Windows is the primary platform.
  • Consider adding explicit instructions or links for Linux/macOS users where relevant, especially in sections referencing command-line tools.
  • Maintain parity in example ordering and tool recommendations to ensure equal visibility for Linux/macOS users.
GitHub Create Pull Request
Virtual Machines Maintenance and updates ...n/articles/virtual-machines/maintenance-and-updates.md
Low 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 mild Windows bias by consistently listing Windows tools (PowerShell) before Linux equivalents (CLI), referencing Windows-specific documentation and examples first, and occasionally linking to Windows-specific pages before Linux ones. There are also references to 'Scheduled Events for Windows' before Linux, and some examples or instructions are only linked for Windows, with Linux equivalents mentioned as 'corresponding article' rather than directly linked. The CLI (cross-platform) is mentioned, but PowerShell is often listed first, and there are no explicit Linux shell examples or screenshots.
Recommendations
  • Alternate the order of CLI and PowerShell mentions, or list CLI (cross-platform) first to reduce perceived Windows-first bias.
  • Provide direct links to Linux-specific documentation and examples alongside Windows ones, rather than referencing 'corresponding article'.
  • Include explicit Linux shell examples (bash, etc.) where PowerShell examples are given.
  • Clarify that the Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Add screenshots or step-by-step instructions for Linux environments where applicable.
GitHub Create Pull Request
Virtual Machines Overview of Maintenance Configurations for Azure virtual machines ...rticles/virtual-machines/maintenance-configurations.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 mentions both Linux and Windows VMs as supported, but there are subtle signs of Windows bias. Azure PowerShell is listed before Azure CLI in management options, and the only sample code linked is a PowerShell-based Azure Functions sample. There is no explicit Linux shell or Bash example, nor are Linux-specific tools or patterns mentioned. The documentation refers to 'Windows Server and Linux machines' together, but examples and tooling references lean toward Windows-first approaches.
Recommendations
  • Provide Bash or Linux shell examples alongside PowerShell samples, especially in code sample links.
  • List Azure CLI before Azure PowerShell in management options, or present them together to avoid perceived prioritization.
  • Include references to Linux-native tools or workflows where relevant, such as cron for scheduling or systemd for service management.
  • Add explicit Linux/macOS command-line walkthroughs in the documentation or link to them.
  • Ensure parity in troubleshooting and usage guides for Linux environments.
GitHub Create Pull Request
Virtual Machines Export an image version to a managed disk ...es/virtual-machines/managed-disk-from-image-version.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 PowerShell examples for exporting an image version to a managed disk. The CLI section is presented first and uses Bash-style syntax, which is cross-platform and suitable for Linux/macOS users. However, the PowerShell section is extensive and detailed, with multiple code blocks and explanations, potentially giving the impression of a Windows-centric approach. There are no Linux-specific tools or shell examples beyond Azure CLI, and PowerShell is presented as an equal alternative, but with more step-by-step detail.
Recommendations
  • Ensure parity in the depth of explanation between CLI and PowerShell sections. The CLI section could include more detailed variable assignment and step-by-step breakdowns, matching the PowerShell section.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide example shell environments (e.g., Bash, zsh) where appropriate.
  • If possible, add a short Linux/macOS-specific note or troubleshooting tip for common issues (e.g., environment variable syntax differences, authentication).
  • Consider including a table summarizing cross-platform compatibility of each method.
GitHub Create Pull Request
Virtual Machines Azure Dedicated Host SKU Retirement Migration Guide ...l-machines/migration/dedicated-host-migration-guide.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation provides migration steps for Azure Dedicated Host SKUs and includes instructions for stopping and starting VMs using PowerShell, CLI, and Portal. In the 'Stop the VM(s) or virtual machine scale set' and 'Start the VM(s) or virtual machine scale set' sections, PowerShell instructions are listed before CLI instructions, which may subtly prioritize Windows users. However, Azure CLI is cross-platform and no Windows-only tools or patterns are exclusively referenced. No explicit Linux/macOS bias or missing Linux examples are present.
Recommendations
  • Alternate the order of PowerShell and CLI instructions, or present CLI instructions first to better reflect cross-platform usage.
  • Explicitly mention that Azure CLI works on Linux/macOS and provide links to installation guides for those platforms.
  • Add brief notes or examples for common Linux/macOS shell usage where relevant, such as bash scripting for automation.
  • Ensure that any referenced scripts or commands are tested and documented for both Windows and Linux environments.
GitHub Create Pull Request
Virtual Machines Migrate Managed image to Compute gallery ...igration/migration-managed-image-to-compute-gallery.md
Low 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 Azure CLI and PowerShell examples, but the PowerShell section is present and detailed, which can indicate a slight bias toward Windows users. The CLI example uses Azure CLI, which is cross-platform, but the PowerShell example is given equal prominence. The portal instructions use Windows-style screenshots and terminology (e.g., backticks in CLI, which is a PowerShell convention), and the page metadata includes 'devx-track-azurepowershell', suggesting a Windows-centric approach. No Linux/macOS-specific shell examples (like bash/zsh) or notes are provided.
Recommendations
  • Add explicit bash/zsh shell examples for Linux/macOS users, using appropriate syntax (e.g., line continuation with \ instead of backticks).
  • Clarify that Azure CLI commands are cross-platform and provide any Linux/macOS-specific notes if needed.
  • Ensure screenshots and UI references are not Windows-specific, or add notes for Linux/macOS users if the experience differs.
  • Balance the prominence of PowerShell and CLI sections, possibly listing CLI first as it is more cross-platform.
  • Remove or clarify the 'devx-track-azurepowershell' metadata if not relevant to Linux/macOS users.
GitHub Create Pull Request
Virtual Machines Monitor Azure Virtual Machines ...docs/blob/main/articles/virtual-machines/monitor-vm.md
Low 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 mild Windows bias. Windows-specific terminology (e.g., 'Windows events', 'IIS logs') is mentioned before Linux equivalents, and some examples (such as log collection levels and Performance Diagnostics) are described in more detail for Windows. There is a lack of concrete Linux command-line or syslog configuration examples, and Windows tools (like IIS logs and Windows event levels) are referenced without similar detail for Linux alternatives. However, Linux is acknowledged throughout, and most features are described as available for both OS types.
Recommendations
  • Provide explicit Linux examples alongside Windows ones, such as syslog configuration, log levels, and performance counter collection.
  • List Linux equivalents (e.g., Apache/Nginx logs) when mentioning Windows tools like IIS logs.
  • Ensure Linux terminology (e.g., syslog, journald, SNMP, application logs) is given equal prominence and detail.
  • When describing alerting or diagnostics, include Linux-specific guidance and screenshots.
  • Avoid listing Windows examples or tools before Linux ones; present both in parallel or alternate order.
GitHub Create Pull Request
Virtual Machines Network security group test ...ticles/virtual-machines/network-security-group-test.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation page demonstrates a mild Windows bias by using RDP (Remote Desktop Protocol) as the primary example for testing inbound connections, which is specific to Windows VMs. Although both Linux and Windows VM creation links are provided in prerequisites, the step-by-step example focuses solely on RDP and does not offer a Linux-relevant protocol (such as SSH) as an equivalent example. No PowerShell commands or Windows-specific tools are mentioned, and the instructions are primarily portal-based and cross-platform, but the example choice centers Windows use cases.
Recommendations
  • Add an SSH example for inbound connection testing to demonstrate Linux VM scenarios (e.g., test port 22/TCP for SSH).
  • Explicitly mention that the same steps can be used for Linux VMs by selecting SSH as the service type.
  • Consider alternating or presenting both Windows (RDP) and Linux (SSH) examples side-by-side to improve parity.
  • Clarify that the portal-based workflow applies equally to both Linux and Windows VMs.
GitHub Create Pull Request
Virtual Machines Isolated Image Builds for Azure VM Image Builder ...chines/security-isolated-image-builds-image-builder.md
Low 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 mild Windows bias. While the main content is platform-neutral and references Linux-specific guides, the only explicit command-line example for registering the Microsoft.ContainerInstance provider is given in both Azure CLI and PowerShell, with PowerShell shown second but not omitted. There are no Linux shell (bash) equivalents for resource provider registration, and no macOS-specific notes. The troubleshooting and template references point to Linux-specific documentation, but the main page does not provide direct Linux command examples or clarify cross-platform differences for key steps.
Recommendations
  • Add bash (Linux/macOS) equivalents for all command-line examples, especially for resource provider registration.
  • Explicitly state that Azure CLI commands work on Linux/macOS and provide usage context.
  • Where PowerShell is mentioned, clarify its availability on Linux/macOS or provide alternatives.
  • Ensure that all critical steps (e.g., troubleshooting, template updates) have platform-agnostic or platform-specific instructions as needed.
GitHub Create Pull Request
Virtual Machines Secure and use policies ...blob/main/articles/virtual-machines/security-policy.md
Low 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 mild Windows bias in several areas. Windows terminology and tools (e.g., PowerShell) are mentioned first or exclusively in some sections, such as Key Vault setup and Azure RBAC. The use of Windows-specific technologies (BitLocker) is described before Linux equivalents (dm-crypt), and PowerShell is referenced for Windows VM management, while Linux instructions rely on Azure CLI. Some cross-platform parity is present, but Windows examples and tools are often prioritized or described first.
Recommendations
  • Present Linux and Windows examples side-by-side or alternate which platform is described first in each section.
  • Explicitly mention Linux tools (e.g., Bash, cloud-init) where relevant, not just Azure CLI.
  • Provide PowerShell and CLI commands for both platforms in all sections, ensuring parity.
  • Clarify when features/tools are Windows-only and offer Linux alternatives or workarounds.
  • Include links to Linux-specific documentation as prominently as Windows links.
GitHub Create Pull Request
Virtual Machines Ebdsv6 size series ...rtual-machines/sizes/memory-optimized/ebdsv6-series.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation is mostly platform-neutral, but there is mild Windows bias in the 'Feature support' section, where nested virtualization is linked to a Windows-specific guide, and in the 'Network' section, where the NTTTCP bandwidth testing tool is referenced without mentioning Linux alternatives. Windows features and tools are mentioned before Linux equivalents, and some links are Windows-centric.
Recommendations
  • In the 'Feature support' section, provide links to nested virtualization documentation for Linux (e.g., KVM/QEMU) if relevant, or clarify if only Windows is supported.
  • In the 'Network' section, mention Linux-compatible bandwidth testing tools (such as iperf3) alongside NTTTCP, and provide links to their usage.
  • Where features are not supported for either OS (e.g., disk encryption), list Linux and Windows together, or clarify parity.
  • Review all external links to ensure Linux documentation is referenced where available.
  • Explicitly state OS support for features that may differ between Windows and Linux.
GitHub Create Pull Request
Virtual Machines Edsv6 size series ...irtual-machines/sizes/memory-optimized/edsv6-series.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation is largely platform-neutral, focusing on VM specifications and features. However, there is mild Windows bias in the 'Feature support' section, where 'Nested Virtualization' links to a Windows-specific Hyper-V guide, and in the 'Bandwidth/Throughput testing' section, which references NTTTCP—a Microsoft tool primarily documented for Windows. Linux equivalents or parity are not provided or mentioned first.
Recommendations
  • Include links to Linux-specific nested virtualization documentation, such as KVM/QEMU guides for Azure.
  • Mention and link to Linux-compatible network throughput testing tools (e.g., iperf, netperf) alongside NTTTCP.
  • Where Windows-specific tools or guides are referenced, provide Linux/macOS alternatives or note cross-platform usage.
  • Ensure that feature support links (e.g., for nested virtualization) include both Windows and Linux documentation if available.
GitHub Create Pull Request
Virtual Machines Epdsv6 size series ...rtual-machines/sizes/memory-optimized/epdsv6-series.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation is mostly platform-neutral, but there is mild Windows bias in the 'Feature Support' section, where nested virtualization is referenced via a Windows/Hyper-V link, and in the networking section, where the bandwidth testing tool NTTTCP is mentioned (a Microsoft/Windows tool) without reference to Linux alternatives. Windows and Linux are both mentioned in support statements, but Windows tools are referenced first and exclusively in some cases.
Recommendations
  • When referencing nested virtualization, include links or notes about Linux/KVM alternatives or clarify that the feature is not supported for either OS.
  • For bandwidth testing, mention Linux-compatible tools (e.g., iperf, netperf) alongside NTTTCP and provide links to their usage in Azure.
  • Ensure that any tooling or example is presented for both Windows and Linux, or clarify platform-specific limitations.
  • Review all resource links to ensure parity between Windows and Linux documentation.
GitHub Create Pull Request
Virtual Machines Create an Azure snapshot of a virtual hard disk ...rticles/virtual-machines/snapshot-copy-managed-disk.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ minor_linux_example
Summary
The documentation provides parity in the main snapshot creation steps for both Windows and Linux users via Azure CLI and PowerShell, but exhibits mild Windows bias: PowerShell (a Windows-centric tool) is presented before Azure CLI, and references to Windows-specific VM creation guides appear before Linux equivalents in the 'Next steps' section. The PowerShell section is more detailed, and links to Windows VM creation guides are more prominent than Linux ones.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and more commonly used on Linux/macOS.
  • Ensure equal detail and step-by-step guidance for both PowerShell and CLI sections.
  • In 'Next steps', list Linux and Windows VM creation guides side-by-side, or present Linux first for parity.
  • Add explicit notes clarifying that both CLI and PowerShell methods work for Linux and Windows VMs.
  • Consider adding Bash scripting examples for advanced Linux users.
GitHub Create Pull Request
Virtual Machines Troubleshoot problems with shared images in Azure ...cles/virtual-machines/troubleshooting-shared-images.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation mentions both Azure CLI and PowerShell for troubleshooting, but lists PowerShell's '-Debug' switch alongside Azure CLI's '--debug' switch in the introductory troubleshooting section. This subtly prioritizes PowerShell (a Windows-centric tool) and does not mention Bash or shell scripting alternatives for Linux/macOS users. No explicit Linux/macOS command examples or troubleshooting patterns are provided, and the only command-line tooling referenced is Azure CLI and PowerShell, with PowerShell mentioned first. However, the error tables and mitigations are platform-neutral and do not show overt Windows bias in the technical content.
Recommendations
  • Explicitly mention Bash/shell scripting for Linux/macOS users when discussing troubleshooting commands.
  • Provide examples for enabling debug mode in Azure CLI on Linux/macOS (e.g., using Bash).
  • If PowerShell is referenced, clarify its cross-platform availability or provide parity examples for Bash.
  • Ensure that any command-line instructions are not Windows-centric and are equally applicable to Linux/macOS environments.
  • Consider listing Azure CLI (which is cross-platform) before PowerShell, or clarify that both are supported on all OSes.
GitHub Create Pull Request
Virtual Machines Understand VM reboots ...ain/articles/virtual-machines/understand-vm-reboots.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation generally addresses both Linux and Windows VMs, but there is a subtle bias in the ordering and example coverage. In the 'Reduce downtime' section, scheduled events for Linux are mentioned after Windows, and there are no concrete examples or Linux-specific tools/patterns provided elsewhere in the document. The page does not provide command-line or tooling examples for either OS, but the ordering and lack of Linux-specific guidance may create minor friction for Linux users.
Recommendations
  • Present Linux and Windows examples/tools in parallel or alternate order to avoid implicit prioritization.
  • Provide explicit examples or links for both Linux and Windows scheduled events, ensuring parity in detail and guidance.
  • Include Linux-specific best practices or references (e.g., handling reboots, using cloud-init, systemd, etc.) where relevant.
  • Ensure that any future tooling or command-line instructions include both PowerShell and Bash equivalents.
GitHub Create Pull Request
Virtual Machines We're retiring Azure unmanaged disks by March 31, 2026 ...ticles/virtual-machines/unmanaged-disks-deprecation.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation demonstrates mild Windows bias by referencing PowerShell as a primary method for querying affected VMs and listing the Windows migration guide before the Linux equivalent. While both Linux and Windows migration guides are linked, the example for querying VMs uses PowerShell and does not mention CLI or Bash alternatives for Linux/macOS users.
Recommendations
  • Include Azure CLI and Bash examples for querying affected VMs, alongside PowerShell.
  • Present Windows and Linux migration links together or alternate their order to avoid implicit prioritization.
  • Explicitly mention cross-platform tools and commands where possible, ensuring parity in instructions for Linux/macOS users.
GitHub Create Pull Request
Virtual Machines Copy VM restore points to another region ...achines/virtual-machines-copy-restore-points-how-to.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation is largely platform-neutral in its API focus, but there is a subtle Windows bias in the ordering and detail of OS-specific configuration examples. Windows configuration fields (e.g., 'windowsConfiguration', 'certificateStoreName on Windows', 'additionalUnattendContent', 'winRM') are described first and in more detail than their Linux equivalents. Linux configuration is present but less detailed and always appears after Windows. There are no PowerShell-only examples or Windows-exclusive tools, but the documentation does not provide parity in example depth for Linux.
Recommendations
  • Provide equally detailed examples and explanations for Linux VM configuration fields, such as common SSH settings, cloud-init usage, and Linux-specific restore scenarios.
  • Alternate the order of Windows and Linux configuration blocks, or present them side-by-side for parity.
  • Add notes or examples for Linux-specific restore point considerations (e.g., file system consistency, SELinux contexts, etc.) where relevant.
  • Ensure that any references to certificate stores or VM agent provisioning are matched with Linux equivalents (e.g., trusted CA bundles, waagent settings).
GitHub Create Pull Request
Virtual Machines Manage, Update, and Delete VM Applications on Azure ...in/articles/virtual-machines/vm-applications-manage.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides parity between Azure CLI and Azure PowerShell for all major tasks, but PowerShell examples are present throughout and sometimes referenced in CLI scripting notes. PowerShell is a Windows-centric tool, and its inclusion and scripting examples may create friction for Linux/macOS users. In one CLI scripting note, PowerShell syntax is used for iterating over VMSS instance IDs, rather than Bash. The documentation does not show explicit Bash scripting examples, and PowerShell is listed as a primary tab in all code sections. However, Azure CLI is cross-platform and is given equal coverage, so Linux users can complete all tasks using CLI or REST. No critical steps are Windows-only, but the presence and occasional preference for PowerShell and Windows scripting patterns indicate a mild Windows bias.
Recommendations
  • Replace PowerShell scripting examples in CLI notes with Bash equivalents, especially in sections referencing scripting for VMSS instance status.
  • Add explicit Bash scripting examples for tasks that require iteration or advanced scripting, to help Linux/macOS users.
  • Clarify in introductory sections that Azure CLI is fully cross-platform and recommend it for Linux/macOS users.
  • Consider listing CLI examples before PowerShell in each section to signal platform neutrality.
  • Where possible, avoid referencing PowerShell in CLI sections unless strictly necessary.
GitHub Create Pull Request
Virtual Machines Create a VM from a specialized image version ...icles/virtual-machines/vm-specialized-image-version.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 provides both Azure CLI and PowerShell examples for all major workflows, but the PowerShell examples are extensive and use Windows-centric tools and patterns (e.g., New-AzNetworkSecurityRuleConfig for RDP, Windows-style variable naming, and PowerShell-specific networking setup). The PowerShell sections are much longer and more detailed than the CLI sections, which are more cross-platform. There is also a tendency to mention RDP and Windows networking rules before SSH or Linux equivalents. However, the CLI examples are sufficient for Linux/macOS users, and the portal instructions are platform-agnostic.
Recommendations
  • Add Bash or shell script examples for network setup and VM creation to match the detail of PowerShell examples.
  • Ensure networking examples mention SSH (port 22) before or alongside RDP (port 3389), especially in PowerShell sections.
  • Clarify that PowerShell examples are primarily for Windows users and recommend CLI for Linux/macOS users.
  • Balance the length and detail of CLI and PowerShell sections to avoid perceived preference.
  • Explicitly state cross-platform compatibility for CLI commands at the start of the article.
GitHub Create Pull Request
Virtual Machines Quickstart: Deploy WebLogic Server on Azure Virtual Machines (VMs) ...kloads/oracle/weblogic-server-azure-virtual-machine.md
Low 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 deploying WebLogic Server using the Azure portal, with no explicit bias toward Windows or Windows-only tools. However, there is a subtle 'windows_first' bias: authentication defaults to password-based login (common for Windows), and SSH key authentication is referenced only as an alternative with a link out to Linux/macOS instructions. There are no command-line examples (e.g., PowerShell, Bash), and no explicit mention of Windows-specific tools, but Linux parity is not fully addressed in the authentication section. The documentation does not provide Linux-specific deployment or management examples, nor does it clarify OS-specific differences in the workflow.
Recommendations
  • Provide explicit instructions and examples for both password and SSH key authentication, including direct steps for Linux/macOS users rather than linking out.
  • Clarify any OS-specific differences in the deployment workflow, especially regarding VM management and authentication.
  • Include a brief section or note on how the process applies to both Windows and Linux VMs, with screenshots or examples for each where relevant.
  • If command-line management is relevant, offer both PowerShell (Windows) and Bash (Linux/macOS) examples.
GitHub Create Pull Request