← Back to Dashboard
1642
Pages Scanned
475
Pages Flagged
1642
Changed Pages
28.9%
% Pages Flagged

Scan Information

Started At: 2026-01-13 06:17:07

Finished At: 2026-01-13 07:16:05

Status: completed

Target Repo: Azure Compute

Current Phase: discovery

Files Queued: 1642

Files Completed: 1642

Problematic Pages

475 issues found
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 code examples use PowerShell, including certificate creation and deployment steps. The certificate helper script is a PowerShell script (.ps1), and there is no mention of Linux or macOS equivalents for certificate generation or deployment. Windows terminology and tooling are used exclusively, and instructions for critical steps (certificate creation, deployment) are not provided for Linux/macOS users.
Recommendations
  • Provide equivalent instructions and scripts for Linux/macOS users, such as using OpenSSL for certificate creation and Azure CLI for deployment.
  • Include Azure CLI examples alongside PowerShell for all deployment steps.
  • Mention cross-platform tools and workflows explicitly, and clarify which steps are Windows-specific.
  • Add a section or callout for Linux/macOS users, detailing any differences or additional requirements.
  • Ensure that all critical steps (certificate creation, resource deployment) have platform-agnostic or platform-specific guidance.
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
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, and the required tooling (Microsoft.ServiceFabric.Powershell.Http Module) is Windows-centric. There are no Linux or cross-platform CLI examples, nor is there guidance for using bash, curl, or other Linux-native tools. The prerequisites and workflow assume a Windows environment, creating friction for Linux/macOS users.
Recommendations
  • Provide equivalent examples using Azure CLI, bash, or curl for REST API calls.
  • Clarify whether the PowerShell modules are available and supported on PowerShell Core (pwsh) for Linux/macOS.
  • Document any Linux/macOS prerequisites and installation steps for Service Fabric tooling.
  • Explicitly mention cross-platform alternatives for connecting to clusters and invoking REST APIs.
  • Reorder examples so that REST API (platform-agnostic) usage is shown before or alongside PowerShell.
  • Add troubleshooting notes for Linux/macOS users, especially around certificate handling and authentication.
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 ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ 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. It references Windows-specific tools (Visual Studio, Cloud Explorer), requires running as Administrator, and includes PowerShell script usage. There are no Linux/macOS equivalents or alternative instructions, and no mention of cross-platform debugging tools or workflows.
Recommendations
  • Add equivalent instructions for debugging Service Fabric applications on Linux/macOS, including supported IDEs (e.g., VS Code, Eclipse) and command-line workflows.
  • Provide examples using Linux shell scripts (e.g., bash) alongside PowerShell scripts.
  • Include screenshots and step-by-step guides for Linux/macOS environments.
  • Clarify platform prerequisites and limitations at the top of the page.
  • Reference cross-platform Service Fabric SDKs and debugging tools where available.
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: 2 bias types
Detected Bias Types
⚠ī¸ windows_only ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a strong Windows bias: EventStore APIs and UX are currently only available for Azure Windows clusters, with explicit notes that Linux and Standalone clusters are not supported yet. All instructions and examples are implicitly for Windows clusters, with no Linux-specific guidance, examples, or parity. Linux users cannot currently utilize the EventStore functionality described.
Recommendations
  • Clearly indicate Windows-only limitations at the top of the page.
  • Provide estimated timelines or roadmap for Linux/Standalone support.
  • Add alternative monitoring/diagnostics options for Linux clusters.
  • Update documentation with Linux examples and instructions as soon as support is available.
  • Link to Linux-compatible diagnostic tools or APIs where possible.
GitHub Create Pull Request
Service Fabric Run an Azure Service Fabric service as an AD user or group ...bric/service-fabric-run-service-as-ad-user-or-group.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation is heavily focused on Windows environments, specifically referencing Windows Server standalone clusters and Active Directory. All examples and instructions use Windows-centric tools (e.g., PowerShell's Invoke-ServiceFabricEncryptText), and there is no mention of Linux or cross-platform equivalents. The page does not provide guidance for Linux clusters or non-Windows authentication mechanisms.
Recommendations
  • Clarify in the introduction whether Linux clusters are supported for this scenario, and if not, explicitly state the limitation.
  • If Linux support exists, add equivalent instructions and examples for Linux clusters, including authentication mechanisms and secret management.
  • Provide alternative tools or commands for encrypting secrets on Linux (e.g., using OpenSSL or Service Fabric CLI).
  • Mention whether group Managed Service Accounts (gMSA) or similar concepts are available or supported on Linux.
  • Add cross-platform notes or links to Linux-specific documentation 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 cluster removal using Windows-specific tools and patterns: RDP, PowerShell, and a .ps1 script. There are no instructions or examples for Linux or macOS users, nor mention of SSH or Bash alternatives. The workflow assumes a Windows environment, which may exclude or confuse users managing clusters from Linux/macOS VMs.
Recommendations
  • Add instructions for connecting to the VM via SSH for Linux/macOS users.
  • Provide equivalent Bash or shell script examples for cluster removal.
  • Clarify whether the removal script can be run on Linux (e.g., via PowerShell Core) or provide a cross-platform alternative.
  • Explicitly state OS requirements and offer parity guidance for non-Windows environments.
GitHub Create Pull Request
Service Fabric Deploy a Service Fabric managed cluster ...cles/service-fabric/tutorial-managed-cluster-deploy.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation exclusively uses PowerShell commands and references Windows-centric tools (Service Fabric SDK and PowerShell module, Azure PowerShell). There are no CLI, Bash, or Linux/macOS instructions or examples, making it difficult for non-Windows users to follow the tutorial. All steps assume a Windows environment and do not mention cross-platform alternatives.
Recommendations
  • Provide equivalent Azure CLI commands for all steps, as Azure CLI is cross-platform.
  • Include installation instructions for Service Fabric SDK and Azure CLI on Linux and macOS.
  • Add Bash shell examples alongside PowerShell, or clearly indicate which steps are Windows-only.
  • Mention platform requirements and limitations explicitly in the prerequisites section.
  • Link to cross-platform documentation where available.
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 examples use the Microsoft.Powershell.DSC extension, reference PowerShell scripts (.ps1), and mention Windows Management Framework (WMF) requirements. There is no mention of Linux support, Linux equivalents, or cross-platform DSC options. Linux users are not provided with guidance or examples, making the documentation Windows-centric.
Recommendations
  • Add a section describing DSC support for Linux, including any limitations or prerequisites.
  • Provide ARM template examples for Linux VM Scale Sets using the Linux DSC extension (OmsAgentForLinux or equivalent).
  • Include links to Linux DSC documentation and examples.
  • Clarify in the introduction that the page currently covers only Windows VMs, if Linux is not supported.
  • If Linux is supported, show Linux examples alongside Windows examples, not just after.
  • Mention Linux configuration management alternatives if DSC is not supported for Linux VMSS.
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 focused on Windows and PowerShell Desired State Configuration (DSC). All examples use PowerShell scripts (.ps1), reference Windows Management Framework (WMF), and the extension publisher is 'Microsoft.Powershell'. There are no examples or guidance for Linux VMs, nor mention of Linux equivalents or cross-platform DSC scenarios. The documentation assumes the reader is deploying DSC to Windows VMs only.
Recommendations
  • Add explicit guidance for deploying DSC extension to Linux VMs, if supported, or clarify that it is Windows-only.
  • Include Linux-specific examples or note that Linux uses a different configuration management extension (such as Azure VM Custom Script Extension or Ansible).
  • Mention cross-platform configuration management options in Azure and link to relevant documentation.
  • If DSC extension is not supported on Linux, state this clearly at the top of the page.
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 is heavily focused on Windows, providing only Windows container examples, Windows-specific Docker images, and Windows file paths and commands. There are no Linux container examples, nor any mention of Linux-compatible images, file paths, or shell commands. The only complete example assumes Windows containers and omits Linux parity.
Recommendations
  • Add equivalent examples for Linux containers, using Linux-based images (e.g., Ubuntu, Alpine) and Linux shell commands.
  • Include Linux file paths and volume mount syntax in ApplicationManifest examples.
  • Clarify in the introduction whether Initializer CodePackages are supported for Linux containers, and if so, provide guidance.
  • If Linux is not supported, explicitly state this limitation early in the documentation.
  • Provide links or references to Linux container documentation for Service Fabric if available.
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, instructions, and referenced tools (e.g., PowerShell, Windows Server 2022) are Windows-specific, with no mention of Linux equivalents or guidance for Linux users. The article repeatedly notes the lack of Linux support and omits any Linux/macOS examples, commands, or migration paths.
Recommendations
  • Clearly indicate Linux support roadmap and expected timelines for TLS 1.3 in Service Fabric clusters.
  • Provide alternative instructions or workarounds for Linux users, if any exist.
  • Add a dedicated section for Linux/macOS users explaining current limitations and possible actions.
  • Ensure future updates include Linux parity in examples, tools, and migration steps.
  • Reference Linux-specific tools (e.g., Bash, Linux Service Fabric CLI) where appropriate.
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 toward Windows and PowerShell. All code examples use PowerShell, including certificate generation and resource deployment. The certificate helper script is a PowerShell (.ps1) script, and there are no Linux/macOS equivalents or CLI/bash alternatives provided. Windows terminology and tools are referenced exclusively or before any cross-platform options, making it difficult for Linux/macOS users to follow the quickstart without significant adaptation.
Recommendations
  • Provide Azure CLI examples alongside PowerShell for all deployment steps, including resource group creation, Key Vault setup, and ARM template deployment.
  • Offer a cross-platform certificate generation method (e.g., using OpenSSL and Azure CLI) instead of relying solely on the PowerShell script.
  • Explicitly mention Linux/macOS prerequisites and provide instructions for installing the Service Fabric SDK and Azure CLI on those platforms.
  • Reorder sections to present cross-platform methods first or in parallel with Windows-specific instructions.
  • Include notes or links to relevant Linux/macOS documentation for users on those platforms.
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, Windows path conventions, and PowerShell scripts for deployment. There are no instructions or examples for Linux/macOS users, nor are alternative tools or workflows mentioned. The prerequisites and steps assume a Windows environment throughout.
Recommendations
  • Add instructions for deploying from Linux/macOS, including using Service Fabric CLI (sfctl) and/or Azure CLI.
  • Provide examples using VS Code or command-line workflows for non-Windows platforms.
  • Include Linux/macOS path conventions and address long path issues for those platforms.
  • Mention alternative deployment scripts (e.g., Bash) or cross-platform approaches.
  • Clarify which steps are Windows-only and offer parity where possible.
GitHub Create Pull Request
Service Fabric Add application cert to a cluster in PowerShell ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/scripts/service-fabric-powershell-add-application-certificate.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 exclusively focused on PowerShell, a tool most commonly associated with Windows, and provides no examples or guidance for Linux/macOS users. All code samples, instructions, and referenced tools are PowerShell-specific, with no mention of Bash, Azure CLI, or cross-platform alternatives. The certificate store reference ('LocalMachine\My') is Windows-centric, and there is no discussion of Linux certificate handling or equivalent workflows.
Recommendations
  • Add equivalent Azure CLI or Bash script examples for each step, ensuring Linux/macOS users can follow along.
  • Include notes on certificate store locations and handling for Linux-based VMSS instances.
  • Explicitly mention cross-platform support and link to relevant documentation for non-Windows environments.
  • Reorder or parallelize examples so that Linux/macOS options are presented alongside Windows/PowerShell instructions.
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 ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation page exhibits a strong Windows bias. All code examples use Windows containers and Windows-specific commands (cmd, set, exit, etc.), with no mention of Linux container equivalents. The only tooling example for querying deployment status is PowerShell, and the introductory note assumes familiarity with Windows container development. There is no guidance for Linux/macOS users or parity in examples.
Recommendations
  • Add equivalent Linux container examples using popular base images (e.g., Ubuntu, Alpine) and shell commands (bash, echo, exit, etc.).
  • Include instructions for querying deployment status using cross-platform tools (e.g., Azure CLI, REST API) or Linux-native commands.
  • Provide notes on compatibility and differences between Windows and Linux containers in Service Fabric.
  • Rephrase introductory notes to reference both Windows and Linux container development.
  • Ensure that examples and tooling are presented in a platform-neutral order or provide both options side-by-side.
GitHub Create Pull Request
Service Fabric Update the RDP username and password in PowerShell ...ts/service-fabric-powershell-change-rdp-user-and-pw.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation exclusively uses Azure PowerShell and provides only PowerShell script examples and references. There are no Bash, Azure CLI, or Linux/macOS-specific instructions or examples. The focus on RDP (a Windows protocol) and PowerShell commands creates a strong Windows-centric bias, making it difficult for Linux/macOS users to follow or adapt the instructions.
Recommendations
  • Add equivalent Azure CLI or Bash script examples for updating VMSS admin credentials.
  • Include instructions for Linux/macOS users, such as how to install and use Azure CLI.
  • Mention SSH access and credential management for Linux-based clusters.
  • Clarify whether the process applies only to Windows VMSS or provide Linux VMSS alternatives.
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 account types (LocalUser, NetworkService, LocalService, LocalSystem), Active Directory domain accounts, and group managed service accounts, all of which are Windows-specific. There is no mention of Linux equivalents, nor any guidance or examples for running Service Fabric applications under Linux user accounts or groups. All examples and terminology are Windows-centric, and there is no indication of how these features work (or if they are supported) on Linux clusters.
Recommendations
  • Explicitly state whether these RunAs and security account features are supported on Linux clusters, and if not, clarify the limitations.
  • Provide Linux-specific guidance and examples for running services under local or system accounts, including how to configure user/group principals on Linux.
  • Mention Linux user/group management tools and patterns (e.g., /etc/passwd, /etc/group, useradd, groupadd) where appropriate.
  • If features are Windows-only, add a clear note at the top of the page to inform Linux users.
  • Ensure parity in documentation structure: for every Windows example, provide a Linux equivalent or explain the differences.
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. There is no mention of Linux/macOS equivalents, such as Service Fabric CLI (sfctl), nor are there bash or cross-platform examples. Windows tooling (PowerShell, Visual Studio) is referenced first and often exclusively, leaving Linux users without clear guidance on how to perform the same tasks.
Recommendations
  • Add equivalent examples using sfctl (Service Fabric CLI) for Linux/macOS users alongside PowerShell examples.
  • Include bash shell command examples where appropriate.
  • Explicitly mention cross-platform support and link to relevant Linux/macOS documentation.
  • Reorder sections or provide parallel instructions so that Windows and Linux/macOS users are equally supported.
  • Reference Visual Studio Code or other cross-platform IDEs in addition to Visual Studio.
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_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The tutorial is heavily focused on Windows development environments, specifically Visual Studio, and does not provide any guidance or examples for Linux/macOS users. All instructions and screenshots are for Visual Studio, a Windows-only tool, and there are no alternative steps for Linux/macOS users or cross-platform CLI tools. The only mention of PowerShell (which is available on Linux, but typically used in Windows contexts) is in the 'Next steps' section, and there are no Linux-native tools or workflows described.
Recommendations
  • Add equivalent instructions for upgrading Service Fabric applications using cross-platform tools such as the Service Fabric CLI (sfctl) or Azure CLI.
  • Provide examples and screenshots for Linux/macOS environments, including how to build, version, and upgrade applications without Visual Studio.
  • Clearly indicate which steps are Windows/Visual Studio-specific and offer alternative workflows for other platforms.
  • Reference documentation for Linux/macOS users earlier in the tutorial, not only in 'Next steps'.
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 is heavily biased towards Windows and PowerShell. All command-line examples use PowerShell, and there is no mention of Linux or macOS equivalents (such as Bash, curl, or Azure CLI). The prerequisite steps require installing a PowerShell module, and REST API usage is demonstrated exclusively via PowerShell cmdlets and scripts. There is no guidance for Linux users or alternative tooling, which may cause confusion or block non-Windows users from completing the documented tasks.
Recommendations
  • Provide equivalent examples using Bash, curl, or Azure CLI for Linux/macOS users.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is available or supported on Linux/macOS, and offer alternatives if not.
  • Include REST API examples using generic HTTP tools (curl, wget) and JSON payloads.
  • Add a section outlining cross-platform support and any limitations for non-Windows environments.
  • Present examples for both Windows and Linux/macOS side by side, or at least alternate which platform is shown first.
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 toward Windows environments. All command-line examples use PowerShell and Windows-specific modules (Microsoft.ServiceFabric.PowerShell.Http). Prerequisites and instructions reference Windows-only articles and tools, and there is no mention of Linux equivalents or cross-platform alternatives. The limitation section explicitly states that Service Fabric PowerShell cmdlets are in preview and not supported on Linux, but no Linux guidance or parity is offered.
Recommendations
  • Clearly state at the top of the page that the documented procedures are Windows-only and not supported on Linux.
  • Provide alternative instructions or note for Linux users, including any REST API usage via curl or other cross-platform tools.
  • Reference Linux cluster creation and management documentation where relevant.
  • If possible, add examples using bash, curl, or other Linux-native tools for REST API calls.
  • Clarify which features are unavailable on Linux and provide a roadmap or workaround if possible.
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 macOS CLI examples, nor any mention of equivalent Linux tools or workflows. The documentation explicitly states that Service Fabric PowerShell cmdlets are in preview and that there is no support for Service Fabric clusters on Linux, making it impossible for Linux users to follow the documented procedures.
Recommendations
  • Provide equivalent examples using cross-platform tools such as Azure CLI, REST API (with curl), or other scripting languages available on Linux/macOS.
  • Clearly document which features are Windows-only and provide alternative workflows for Linux clusters where possible.
  • Add explicit guidance for Linux users, including any limitations and possible workarounds.
  • If the feature is not supported on Linux, state this clearly at the top of the documentation and link to relevant feature requests or roadmap items.
GitHub Create Pull Request
Service Fabric Set up Microsoft Entra ID for client authentication ...ce-fabric/service-fabric-cluster-creation-setup-aad.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 toward Windows and PowerShell. All setup and configuration examples use PowerShell scripts (.ps1), with no equivalent bash, shell, or Linux-native instructions. The prerequisites and troubleshooting sections assume use of PowerShell and Windows tools, and there is no guidance for Linux users on how to perform these steps without PowerShell. While the documentation mentions Linux clusters and some Linux-specific limitations, it does not provide Linux-friendly alternatives for the core configuration tasks.
Recommendations
  • Provide equivalent bash or shell scripts for Linux users to perform Microsoft Entra ID setup and configuration.
  • Include Azure CLI examples for all major steps (app registration, user assignment, ARM template modification) alongside PowerShell examples.
  • Clearly indicate which steps can be performed from Azure Portal or CLI, and which are strictly PowerShell-only.
  • Add a dedicated section for Linux/macOS users outlining a workflow that does not require PowerShell.
  • Document any limitations or workarounds for Linux users, and link to community or official resources for Linux-based Service Fabric cluster management.
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 oriented toward Windows environments, with examples, tooling, and configuration paths specific to Windows. There are no Linux or macOS equivalents provided for key steps such as IP address discovery, diagnostics/log storage, or cluster creation. Windows security and tools (e.g., ipconfig, netsh, C:\ paths, ETW tracing) are referenced exclusively or before alternatives, and all sample files and links are Windows-centric.
Recommendations
  • Add explicit Linux/macOS sections or examples for each configuration step, including sample ClusterConfig.json files for Linux clusters.
  • Provide Linux/macOS equivalents for commands (e.g., use 'ip addr' or 'ifconfig' for IP discovery, show Linux file paths like '/var/lib/servicefabric').
  • Reference Linux-compatible diagnostic and logging tools, such as syslog, journald, or Linux crash dump utilities.
  • Clarify which features and settings are Windows-only and which are cross-platform, and link to Linux-specific documentation where available.
  • Include instructions for creating and managing clusters on Linux, with links to relevant guides.
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 ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation is heavily biased towards Windows, with all instructions, requirements, and examples focused exclusively on Windows Server environments. There is no mention of Linux or macOS support, no Linux equivalents for tools or configuration steps, and all validation scripts and downloads are Windows-specific (e.g., PowerShell scripts, NTFS requirement, Windows services, Windows-only antivirus exclusions). This creates significant friction for users on non-Windows platforms.
Recommendations
  • Clearly state platform support at the beginning, including whether Linux/macOS are supported or not.
  • If Linux is supported, provide equivalent instructions, requirements, and examples for Linux environments (e.g., supported distributions, required packages, file system requirements, service equivalents).
  • Offer Linux-compatible validation scripts (e.g., Bash or Python alternatives to PowerShell scripts).
  • List Linux-specific antivirus exclusions and service requirements where applicable.
  • Provide download links and configuration templates for Linux clusters if supported.
  • If Service Fabric Standalone is Windows-only, make this explicit and guide Linux users to alternative supported deployment options.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Standalone Package for Windows Server ...https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-standalone-package-contents.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 focused on Windows, with all tools and scripts provided in PowerShell (.ps1) format and references to Windows-specific features (e.g., Windows identities, Group Managed Service Accounts). There are no Linux or macOS equivalents, examples, or instructions, and all configuration templates and runtime packages are tailored for Windows Server. This creates significant friction for users on non-Windows platforms.
Recommendations
  • Provide equivalent scripts and instructions for Linux (e.g., Bash scripts or cross-platform CLI commands).
  • Include Linux/macOS-specific configuration templates and security scenarios.
  • Clearly indicate platform limitations and offer guidance for Linux/macOS users, including links to relevant documentation.
  • If the package is Windows-only, state this explicitly at the top of the documentation and direct Linux users to alternative solutions.
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_first ⚠ī¸ missing_linux_example
Summary
The documentation page is notably Windows-centric. It explicitly states that the EventStore APIs are GA only for Windows clusters on Azure, with no mention of Linux cluster support or examples. All sample queries, code snippets, and scenarios assume a Windows cluster environment, and there are no Linux-specific instructions, examples, or clarifications. This creates ambiguity and friction for Linux users, who may not know if or how these APIs apply to their environments.
Recommendations
  • Clearly state whether Linux clusters support the EventStore APIs, and if not, provide guidance or alternatives.
  • If Linux support exists, add explicit examples and instructions for querying EventStore APIs from Linux clusters, including any differences in endpoints, authentication, or tooling.
  • Include sample code and REST queries tested on Linux environments, and clarify any platform-specific caveats.
  • If only Windows is supported, make this limitation prominent at the top of the documentation and link to Linux alternatives or roadmap information.
GitHub Create Pull Request
Service Fabric Set up a Windows development environment .../articles/service-fabric/service-fabric-get-started.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation is heavily focused on Windows, with all examples and instructions tailored exclusively to Windows environments. PowerShell commands are used throughout, and Windows-specific tools (Visual Studio, Docker for Windows) are referenced without Linux/macOS alternatives or parity. Linux and Mac are only mentioned in navigation, with no actual instructions or examples provided for those platforms.
Recommendations
  • Add equivalent installation and setup instructions for Linux and macOS, including shell commands and package managers (e.g., apt, yum, Homebrew).
  • Provide examples using Bash or other common Linux/macOS shells alongside PowerShell.
  • Reference Linux/macOS-compatible tools (e.g., VS Code, Docker for Linux/macOS) and provide guidance for their setup.
  • Clearly indicate platform-specific steps and link to corresponding Linux/macOS documentation sections where appropriate.
  • Avoid assuming Visual Studio or PowerShell as the default; mention cross-platform alternatives.
GitHub Create Pull Request
Service Fabric Create an Azure Service Fabric container application ...ervice-fabric/service-fabric-get-started-containers.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 toward Windows environments. All examples, prerequisites, and instructions are specific to Windows, including the use of Windows containers, Windows Server, Visual Studio, PowerShell, and Windows-specific Docker images. There is no guidance for Linux/macOS users, and the article explicitly states it applies only to Windows development environments. Linux equivalents, tools, and workflows are missing, and the documentation does not provide parity for non-Windows users.
Recommendations
  • Add equivalent Linux/macOS instructions and examples, including Dockerfile and deployment steps for Linux containers.
  • Provide guidance for using cross-platform tools (e.g., VS Code, CLI) instead of only Visual Studio.
  • Include Linux-specific prerequisites, such as Docker for Linux, Service Fabric SDK for Linux, and relevant OS compatibility notes.
  • Offer PowerShell alternatives using Bash or other Linux-native tools.
  • Clearly link to the Linux version of the guide at the top and throughout, ensuring users can easily find Linux-specific documentation.
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 Visual Studio, a Windows-centric tool, and all instructions assume usage of Windows (e.g., launching Visual Studio as administrator, .exe file references). There are no examples or guidance for Linux-native development workflows (such as using VS Code, CLI, or Linux-based build/publish steps). Linux users are expected to use Windows tooling to target Linux clusters, with no parity for Linux/macOS development environments.
Recommendations
  • Add instructions for creating and publishing .NET Core Service Fabric apps using cross-platform tools like VS Code or the .NET CLI.
  • Provide Linux/macOS-specific examples for project creation, build, and publish steps.
  • Clarify which steps are Windows-only and offer alternatives for Linux/macOS users.
  • Include screenshots and walkthroughs for Linux-native development environments.
  • Mention and link to Service Fabric CLI or PowerShell alternatives for Linux users.
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_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation is heavily biased towards Windows environments. All command-line examples are provided in PowerShell, with no Bash or Linux equivalents. The workflow is built around Visual Studio (Windows-only), Docker Desktop for Windows, and Service Fabric clusters running Windows containers. There is no mention of Linux/macOS alternatives, nor guidance for users on those platforms. Critical steps (containerization, debugging, deployment) rely on Windows-specific tools and patterns.
Recommendations
  • Provide equivalent Bash/Azure CLI scripts for all PowerShell commands, especially for Azure resource creation and management.
  • Include instructions for containerizing and deploying .NET Core/ASP.NET Core applications in Linux containers, using cross-platform tools like VS Code, Docker CLI, and Azure CLI.
  • Clarify early in the prerequisites and introduction that the tutorial is Windows-specific, and link to Linux/macOS alternatives if available.
  • Add guidance for users on Linux/macOS for local development, debugging, and deployment, or explicitly state limitations.
  • Mention and provide examples for using Service Fabric clusters with Linux nodes and containers, if supported.
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 biased towards Windows, with all setup, cluster creation, and debugging instructions assuming the use of Windows tools (Visual Studio, PowerShell, Windows-specific SDK paths). There are no instructions or examples for Linux or macOS users, and critical steps (such as cluster creation and debugging) rely on Windows-only tools and scripts.
Recommendations
  • Add equivalent instructions for Linux/macOS users, including how to install the Service Fabric SDK and create a local cluster using CLI tools.
  • Provide examples using cross-platform editors (e.g., VS Code) and .NET CLI commands for building and debugging.
  • Document how to deploy and debug Service Fabric applications on Linux clusters, including any differences in configuration or tooling.
  • List Linux prerequisites and provide parity in step-by-step guides for non-Windows platforms.
  • Clearly indicate platform-specific limitations and link to Linux/macOS documentation where available.
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 parameters, and operational details are specific to Windows Update and Windows NT services. Deployment, upgrade, and removal instructions exclusively use PowerShell scripts and cmdlets. There is no guidance or parity for Linux clusters, except for a brief FAQ link redirecting Linux users elsewhere. The documentation does not mention Linux equivalents for patch orchestration, nor does it provide any examples or instructions for Linux Service Fabric clusters.
Recommendations
  • Add a dedicated section for Linux clusters, including supported patch orchestration methods and integration with Service Fabric Repair Manager.
  • Provide Linux-specific deployment, upgrade, and removal instructions, including sample scripts (e.g., Bash, systemd, apt/yum integration).
  • Include examples of configuring patch orchestration for Linux nodes, such as using package managers or OS-native update tools.
  • Clarify POA's applicability and limitations for Linux clusters early in the documentation.
  • Where possible, present examples for both Windows and Linux side-by-side, or clearly indicate when content is Windows-only.
GitHub Create Pull Request
Service Fabric Create a Windows container application on Service Fabric in Azure ...service-fabric/service-fabric-quickstart-containers.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, with all examples, tools, and instructions tailored to Windows environments. Visual Studio and PowerShell are required, and only Windows container images are discussed. Linux equivalents are mentioned only as a link to a separate quickstart, with no Linux instructions or parity in the main content.
Recommendations
  • Provide Linux/macOS equivalents for each major step, including cluster creation, certificate management, and deployment.
  • Include CLI or Bash examples alongside PowerShell scripts.
  • Reference cross-platform tools (e.g., Azure CLI, Docker CLI) where possible.
  • Show Linux container image packaging and deployment steps, or link to them more prominently.
  • Clarify which steps are Windows-specific and offer alternatives for non-Windows users.
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: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation is heavily oriented toward Windows development, specifically using Visual Studio and PowerShell. All examples and instructions assume a Windows environment, with no guidance for Linux/macOS users on how to create, build, or debug actor-based services in C#. Linux equivalents (such as using VS Code, CLI tools, or Bash) are not mentioned, and the only NuGet installation example uses PowerShell. The page does not provide parity for Linux/macOS users wishing to follow the C# workflow.
Recommendations
  • Add instructions for creating and managing Service Fabric actor projects using cross-platform tools like .NET CLI and VS Code.
  • Include Linux/macOS-specific steps for installing dependencies (e.g., using 'dotnet add package' instead of PowerShell).
  • Provide alternative debugging and deployment instructions for non-Windows environments.
  • Explicitly state platform requirements and link to Linux/macOS documentation where available.
  • Present examples for both Windows and Linux/macOS side-by-side, or clearly indicate which steps are platform-specific.
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 focused on Windows development, specifically using Visual Studio and PowerShell scripts. All examples and instructions are for C# on Windows, with no Linux/macOS equivalents shown. The use of Windows-specific tools (Visual Studio, ETW, Diagnostic Events window) and deployment scripts (PowerShell) further reinforces the bias. There is a mention of a Java on Linux guide, but this page provides no Linux/macOS instructions or parity for C# developers.
Recommendations
  • Provide equivalent instructions and examples for developing Service Fabric applications in C# on Linux/macOS, including supported IDEs (e.g., VS Code, JetBrains Rider) and command-line workflows.
  • Include Linux/macOS deployment steps, using bash scripts or Service Fabric CLI instead of PowerShell.
  • Mention and demonstrate cross-platform diagnostic and debugging tools, such as sfctl, Service Fabric Explorer, or container logs.
  • Avoid assuming Visual Studio is the only development environment; offer alternatives and clarify platform requirements.
  • Ensure that all critical steps (project creation, deployment, debugging) have Linux/macOS equivalents or clear guidance.
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 page is heavily biased towards Windows environments. All example scripts use Windows batch files (.bat), and PowerShell is the only scripting language demonstrated. Visual Studio is referenced for project setup, and all file paths and debugging instructions use Windows conventions. Linux is mentioned only briefly in a note about AccountType, with no concrete Linux shell script or deployment examples provided.
Recommendations
  • Add equivalent Linux examples using shell scripts (e.g., MySetup.sh) and demonstrate how to set environment variables and output files in bash.
  • Provide instructions for including startup scripts in non-Visual Studio workflows, such as using CLI tools or editing files directly.
  • Show Linux file paths and locations for output and log files, not just Windows paths.
  • Include PowerShell alternatives for Linux (e.g., bash, sh) and demonstrate how to run those scripts from the SetupEntryPoint.
  • Clarify any differences in user/account configuration for Linux clusters, with concrete manifest examples.
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 page exhibits a strong Windows bias. All step-by-step examples use Windows-centric tools (PowerShell, Windows file paths, Windows certificate stores) and reference Windows Server OS upgrades. Linux is mentioned only briefly, with minimal guidance and no concrete Linux shell commands or examples. There are no bash/CLI equivalents for certificate management, cluster connection, or resource deployment, and the workflow assumes a Windows environment throughout.
Recommendations
  • Provide parallel Linux/macOS examples for all PowerShell commands, using Azure CLI and bash scripting.
  • Include instructions for certificate generation and management on Linux (e.g., using openssl, Azure CLI, and Linux file paths).
  • Show how to connect to Service Fabric clusters from Linux/macOS, including certificate import and cluster health checks.
  • Explicitly document differences in OS image parameters for Linux clusters, with concrete ARM template snippets and deployment commands.
  • Reorder or balance examples so Linux and Windows are presented with equal prominence.
  • Clarify which steps are OS-agnostic and which require platform-specific handling.
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 strong Windows bias. The reverse proxy feature is explicitly stated as unavailable for Linux clusters, making the entire functionality Windows-only. All examples, configuration instructions, and referenced tools (such as http.sys-based servers and Windows-specific environment variables) are tailored to Windows environments. There are no Linux equivalents or workarounds provided, and Linux users are unable to utilize the reverse proxy feature or follow the documented steps.
Recommendations
  • Clearly indicate the lack of Linux support at the top of the documentation and in the prerequisites.
  • Provide alternative guidance or recommended approaches for Linux clusters, such as using other proxy solutions or service discovery mechanisms.
  • If possible, prioritize development of Linux support for the reverse proxy feature and update documentation accordingly.
  • Include links to Linux-specific documentation for related networking and service communication patterns in Service Fabric.
  • Offer sample code and configuration for Linux environments where feasible, or explicitly state when features are Windows-only.
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 toward Windows environments, focusing exclusively on Windows Server standalone clusters and gMSA accounts, which are a Windows/Active Directory-specific feature. All examples use PowerShell cmdlets and Windows tools, with no mention of Linux or cross-platform alternatives. There are no instructions or guidance for Linux or macOS users, nor is it clarified whether Service Fabric clusters on Linux can use similar security models.
Recommendations
  • Clarify whether gMSA and RunAsPolicy are supported on Linux clusters, and if not, explicitly state this limitation.
  • If Linux support exists, provide equivalent instructions and examples for configuring service accounts on Linux clusters, including relevant tools and commands (e.g., systemd, Linux user management).
  • If only Windows is supported, add a prominent note at the top indicating that the procedure is Windows-only.
  • Consider providing alternative security recommendations for Linux clusters, such as using managed identities or local service accounts.
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, Windows file paths, and Windows-centric tooling. There are no equivalent instructions or examples for Linux/macOS users, nor any mention of cross-platform alternatives (e.g., Azure CLI, Bash). The VM upgrade scenario exclusively references Windows Server SKUs, further reinforcing the Windows focus.
Recommendations
  • Provide Azure CLI (az) command equivalents for all PowerShell commands, as Azure CLI is cross-platform.
  • Include Linux/macOS-specific instructions for certificate generation, file paths, and resource management.
  • Mention and demonstrate how to perform Service Fabric cluster operations from Bash or other non-Windows shells.
  • Reference Linux VM SKUs and show how to upgrade node types running Linux, not just Windows Server.
  • Add notes or links to cross-platform tooling and documentation for users on non-Windows systems.
GitHub Create Pull Request
Service Fabric Standalone Service Fabric clusters overview ...-fabric/service-fabric-standalone-clusters-overview.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 presents Service Fabric clusters as supporting both Windows Server and Linux, but the details and examples are almost exclusively focused on Windows environments. Security sections reference Windows authentication and Active Directory, and the 'Supported operating systems' list only includes Windows Server versions, with a note that Linux isn't yet supported. There are no Linux-specific instructions, examples, or references to Linux tools or patterns.
Recommendations
  • Add explicit Linux support status and roadmap, if Linux support is planned.
  • Include Linux-specific examples and instructions for cluster setup, security, and management.
  • Reference Linux authentication and security mechanisms (e.g., PAM, certificate management tools) where relevant.
  • List supported Linux distributions and versions when Linux support becomes available.
  • Ensure parity in documentation structure and depth for both Windows and Linux environments.
GitHub Create Pull Request
Service Fabric Monitor and diagnose Windows containers ...ic/service-fabric-tutorial-monitoring-wincontainers.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation is heavily focused on Windows containers and clusters, with all examples, templates, and instructions tailored to Windows environments. Windows-specific tools and patterns (e.g., PowerShell deployment, Windows Diagnostics agent, Windows performance counters) are mentioned exclusively, and Linux equivalents are only referenced briefly at the end, without concrete examples or walkthroughs.
Recommendations
  • Provide parallel, step-by-step instructions and Resource Manager template examples for Linux clusters and containers.
  • Include Linux-specific agent installation and configuration details (e.g., OMS agent for Linux, Linux performance counters).
  • Show how to deploy templates using cross-platform tools (e.g., Azure CLI, Bash) in addition to PowerShell.
  • Add screenshots and dashboard examples from Linux container monitoring.
  • Ensure that all referenced sample templates for Linux are linked and described in the main tutorial flow, not just in 'Next steps'.
GitHub Create Pull Request
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 ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation is heavily biased towards Windows, with all examples, scripts, and tools (such as PowerShell scripts, Windows file paths, and Windows-specific configuration) tailored exclusively for Windows environments. There are no Linux or macOS instructions, examples, or references, despite the initial claim of 'any OS, any cloud'. This makes it difficult or impossible for Linux/macOS users to follow the tutorial.
Recommendations
  • Provide equivalent instructions and examples for Linux (and macOS) environments, including how to download, extract, and configure the Service Fabric standalone client on those platforms.
  • Include bash or shell script alternatives to the PowerShell scripts, or clarify if Linux is unsupported for standalone clusters.
  • Mention Linux-specific tools and file paths where relevant.
  • Explicitly state OS limitations if the standalone client is Windows-only, to avoid misleading users.
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 is heavily focused on Windows-centric tools and workflows, specifically Visual Studio and PowerShell. All upgrade instructions and examples reference Visual Studio dialogs and PowerShell cmdlets, with no mention of Linux/macOS alternatives such as CLI commands, cross-platform editors, or Bash scripts. There is no guidance for users who do not have access to Visual Studio or PowerShell, making it difficult for Linux/macOS users to follow the documented procedures.
Recommendations
  • Add instructions for upgrading Service Fabric applications using the Service Fabric CLI (sfctl), which is cross-platform.
  • Provide examples for configuring upgrade parameters and health policies using CLI commands or editing manifest files directly.
  • Include guidance for performing manual upgrades on Linux/macOS, such as using Bash or shell scripts.
  • Reference cross-platform editors (e.g., VS Code) for editing manifest files, not just Visual Studio.
  • Clearly indicate which steps are Windows-specific and offer Linux/macOS alternatives where possible.
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
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation is heavily biased towards Windows, with all command-line examples provided exclusively in PowerShell. The workflow and examples assume Windows VMs and Windows-specific tooling, with no mention of Linux or cross-platform alternatives such as Azure CLI or Bash. There are no Linux-specific instructions, and the documentation does not address how to attach a Linux OS disk or considerations for Linux VMs.
Recommendations
  • Add equivalent Azure CLI and/or Bash examples for all PowerShell commands to support Linux/macOS users.
  • Include a section or tab specifically for Linux VMs, outlining any differences in process or considerations (e.g., SSH instead of RDP, Linux disk attachment flags).
  • Clarify in the introduction that the instructions are Windows-specific, and provide links or guidance for Linux VM scenarios.
  • Ensure parity in documentation structure and detail for both Windows and Linux workflows.
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 ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation is heavily biased toward Windows environments. All VM creation instructions specify Windows Server, connection steps use RDP (Windows Remote Desktop), and configuration commands are exclusively PowerShell and Windows Command Prompt. There are no examples or guidance for Linux VM images, SSH connectivity, or Linux firewall/network configuration. This creates significant friction for users wishing to deploy Service Fabric clusters on Linux VMs.
Recommendations
  • Add parallel instructions for creating Linux VM instances, including recommended images (e.g., Ubuntu, CentOS).
  • Provide SSH-based connection steps for Linux VMs instead of only RDP.
  • Include Linux equivalents for firewall and SMB configuration (e.g., using ufw, firewalld, Samba).
  • Show Linux command-line examples (bash, shell) for connectivity checks (e.g., ping, smbclient, mount).
  • Clarify which steps are Windows-specific and which are required for Linux, or provide separate sections for each OS.
GitHub Create Pull Request
Virtual Machine Scale Sets Tutorial - Install applications in a scale set with Azure PowerShell ...machine-scale-sets/tutorial-install-apps-powershell.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation is heavily biased towards Windows and PowerShell. All examples use Azure PowerShell cmdlets and focus on deploying IIS (a Windows-only web server) via PowerShell scripts. There are no Linux or Bash examples, nor any mention of deploying Linux applications or using Linux-native tools. The tutorial assumes Windows as the default platform for both scripting and application deployment.
Recommendations
  • Add parallel examples using Azure CLI and Bash for Linux users.
  • Provide a Linux-focused scenario, such as installing Apache or Nginx on Ubuntu VMSS instances.
  • Include links to the Custom Script Extension documentation for Linux.
  • Explicitly mention that the tutorial is Windows-specific and provide guidance or links for Linux users.
  • Show how to use shell scripts (.sh) with the Custom Script Extension on Linux VMSS.
GitHub Create Pull Request
Virtual Machines Add monitoring & diagnostics to an Azure virtual machine ...es/virtual-machines/extensions/diagnostics-template.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation is heavily focused on Windows virtual machines, with all examples, configuration snippets, and explanations tailored exclusively to Windows (WAD) diagnostics extension. There is no Linux (LAD) diagnostics extension example, nor any mention of Linux-specific configuration, counters, or XML schema. Windows terminology and tools (e.g., WindowsEventLog, Windows performance counters, Visual Studio) are used throughout, and the only sample template referenced is for Windows VMs. Although the deprecation notice mentions Linux, the rest of the page provides no guidance for Linux users.
Recommendations
  • Add parallel examples for configuring diagnostics on Linux VMs, including LAD extension and its settings.
  • Include Linux-specific performance counters and log collection configuration.
  • Reference Linux sample templates and provide links to Linux-focused quickstart resources.
  • Clarify which sections apply only to Windows and provide equivalent instructions for Linux.
  • Mention Linux deployment tools (e.g., Azure CLI, cloud-init) alongside Windows tools like PowerShell and Visual Studio.
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 strongly biased toward Windows environments, with exclusive use of PowerShell DSC, Windows Management Framework, and Windows-specific tools and paths. All examples, prerequisites, and deployment instructions assume Windows VMs, with no mention of Linux support, alternatives, or parity. Linux users are left without guidance or examples for using DSC or equivalent configuration management on Azure VMs.
Recommendations
  • Explicitly state whether the DSC extension supports Linux VMs, and if not, provide alternatives for Linux configuration management (e.g., Ansible, Chef, Puppet, or Azure Machine Configuration).
  • Add Linux-specific examples for configuration management on Azure VMs, including CLI commands and ARM template snippets.
  • Clarify prerequisites and supported operating systems, listing Linux support status.
  • Provide links to documentation for Linux configuration management tools and how to integrate them with Azure VM extensions.
  • If PowerShell DSC is not supported on Linux, suggest cross-platform alternatives and migration paths.
GitHub Create Pull Request
Virtual Machines Azure Disk Encryption sample scripts ...rtual-machines/linux/disk-encryption-sample-scripts.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, while focused on Azure Disk Encryption for Linux VMs, exhibits a strong bias towards Windows tooling and PowerShell. All automation and scripting examples for interacting with Azure resources (listing encrypted VMs, uploading VHDs, managing Key Vault secrets, attaching disks) use PowerShell cmdlets, with no Bash/CLI or Azure CLI equivalents provided. The use of PowerShell is pervasive, and Windows-centric tools (e.g., Add-AzVhd) are referenced without Linux alternatives. In several cases, the only way to complete a step is via PowerShell, which is not natively available on most Linux distributions. The Linux-specific instructions are limited to OS-level configuration and encryption setup, but all Azure-side operations are Windows/PowerShell-centric.
Recommendations
  • Provide Azure CLI (az) equivalents for all PowerShell cmdlets and scripts, especially for listing encrypted VMs, uploading VHDs, managing Key Vault secrets, and attaching disks.
  • Include Bash script examples for interacting with Azure resources, demonstrating parity for Linux users.
  • Clearly indicate when a step can be performed using Azure CLI or REST API, and link to relevant documentation.
  • Reorder examples so that Linux-native tools (Azure CLI, Bash) are presented before or alongside PowerShell.
  • Note any limitations or differences between PowerShell and CLI approaches, and provide guidance for Linux/macOS users.
GitHub Create Pull Request
Virtual Machines How to upgrade Azure Disk Encryption on a disk ...cles/virtual-machines/linux/disk-encryption-upgrade.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates a Windows bias by providing migration instructions exclusively via Azure PowerShell, with no equivalent CLI or Linux-native method. The upgrade process is only described using PowerShell cmdlets, which are primarily used on Windows. Linux users are left without direct instructions or examples for upgrading ADE, creating friction and possible blockers for non-Windows environments.
Recommendations
  • Provide Azure CLI-based migration instructions if supported, or clarify if migration is not possible on Linux.
  • Explicitly state platform limitations and offer alternative approaches for Linux users.
  • Include Linux-specific examples or workflows for both version determination and migration steps.
  • If PowerShell is required, document how to use Azure PowerShell on Linux/macOS (e.g., via PowerShell Core).
GitHub Create Pull Request
Virtual Machines Use a VHD snapshot to create multiple identical managed disks (Windows) - PowerShell ...al-machines-powershell-sample-create-snapshot-from-vhd.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation is heavily biased towards Windows and PowerShell, providing only Windows-specific instructions and examples. There are no references to Linux or macOS workflows, nor are alternative tools or commands (such as Azure CLI or Bash) mentioned. The page title, sample script, and next steps all focus exclusively on Windows and PowerShell, making it difficult for Linux/macOS users to follow or replicate the process.
Recommendations
  • Add equivalent instructions and sample scripts using Azure CLI and Bash for Linux/macOS users.
  • Include links to Linux/macOS documentation or script samples where available.
  • Clearly indicate platform-specific steps and provide parity for all major operating systems.
  • Update the title and description to reflect cross-platform applicability if possible.
GitHub Create Pull Request
Virtual Machines Copy snapshot of managed disk to subscription (Windows) - PowerShell ...sample-copy-snapshot-to-same-or-different-subscription.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation is heavily biased towards Windows and PowerShell, with all examples, tools, and references centered on Windows environments. There are no Bash, Azure CLI, or Linux/macOS instructions, and the page title and content explicitly target Windows users. Linux users are left without guidance for completing the task.
Recommendations
  • Add equivalent Azure CLI and Bash script examples for copying managed disk snapshots.
  • Include a section or page for Linux/macOS users, detailing steps and commands relevant to those platforms.
  • Reference cross-platform tools and documentation (e.g., Azure CLI, REST API) alongside PowerShell.
  • Update navigation and 'Next steps' links to include Linux/macOS resources.
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 and detailed coverage. The ARM template section references PowerShell deployment commands before CLI equivalents. There are no Linux/macOS-specific shell examples (e.g., Bash), and PowerShell is featured as a primary method, which may create friction for non-Windows users.
Recommendations
  • Add explicit Bash examples for Linux/macOS users, especially for tasks that use Azure CLI.
  • In ARM template deployment instructions, list Azure CLI commands before PowerShell commands to avoid Windows-first ordering.
  • Clarify that Azure CLI works cross-platform and highlight its use for Linux/macOS users.
  • Consider removing or de-emphasizing PowerShell examples in favor of CLI for parity, or add equivalent Bash scripting examples.
  • Add notes or sections addressing Linux/macOS users, including troubleshooting tips for non-Windows environments.
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 key steps, such as retrieving the Service Principal and assigning roles. There are no equivalent Azure CLI or Bash examples, and PowerShell commands are presented first and exclusively. This may create friction for Linux/macOS users who typically use Azure CLI or Bash scripts.
Recommendations
  • Add equivalent Azure CLI commands for all PowerShell examples, especially for service principal retrieval and role assignment.
  • Explicitly mention that both Azure PowerShell and Azure CLI can be used, and provide links to relevant CLI documentation.
  • Where possible, show CLI/Bash examples before or alongside PowerShell to ensure parity and inclusivity.
  • Clarify that ARM templates are platform-agnostic and can be deployed from any OS.
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 shows bias toward Windows environments by referencing Windows-specific container images (microsoft/windowsservercore, microsoft/nanoserver) as defaults to skip during cleanup, with no mention of Linux equivalents. The examples and descriptions prioritize Windows images, and there are no Linux-specific examples or guidance. This may cause confusion or extra effort for Linux/macOS users managing Service Fabric clusters.
Recommendations
  • Include Linux container images (e.g., Ubuntu, Alpine, CentOS) in the 'ContainerImagesToSkip' examples and documentation.
  • Clarify whether the cleanup logic applies equally to Linux-based images and provide explicit examples for those platforms.
  • Add notes or sections addressing Linux/macOS environments, including any differences in behavior or configuration.
  • Ensure that examples and defaults do not exclusively reference Windows images, or present Linux and Windows examples side by side.
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 page exclusively provides PowerShell-based examples and commands for configuring maintenance control on Service Fabric managed clusters. There are no CLI, Bash, or Linux/macOS-specific instructions, and all command-line steps assume the use of PowerShell and Azure PowerShell modules, which are most commonly used on Windows. This creates friction for Linux/macOS users who typically use Azure CLI or Bash scripts.
Recommendations
  • Add equivalent Azure CLI (az) command examples for all PowerShell steps, including resource group creation, cluster deployment, and maintenance configuration assignment.
  • Include Bash script snippets for Linux/macOS users where appropriate.
  • Explicitly mention cross-platform alternatives and clarify which tools are supported on each OS.
  • Reorder examples so that CLI/Bash and PowerShell are presented together or in parallel, rather than PowerShell-only.
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 notable 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 a Windows environment or installation of PowerShell Core on Linux/macOS. There are no equivalent examples using Azure CLI, Bash, or other cross-platform tools. The troubleshooting section also references PowerShell modules (Get-AzMetric) exclusively. Windows terminology and tools are presented first and exclusively, with no mention of Linux/macOS alternatives or parity.
Recommendations
  • Provide equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that PowerShell Core can be installed on Linux/macOS, but recommend Azure CLI for native experience.
  • Add Bash script examples for resource group and cluster deployment steps.
  • Include troubleshooting steps using Azure CLI or REST API, not just PowerShell.
  • Clarify any OS-specific limitations (e.g., the note about Windows OS image and Hyper-V) and provide Linux-specific guidance where relevant.
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 only listing Windows-based cluster versions in its REST API example output, with no mention of Linux equivalents. There are no explicit Linux-specific instructions, examples, or references to Linux cluster versions, which may lead Linux users to believe that only Windows clusters are supported or relevant for these upgrade operations.
Recommendations
  • Include examples of Linux cluster versions in the REST API output, showing both Windows and Linux entries.
  • Explicitly mention that Service Fabric managed clusters can be Linux-based, and clarify any differences in upgrade procedures or supported versions.
  • Add references or links to documentation about Linux cluster management and upgrade processes.
  • Where OS-specific properties or behaviors exist, document them for both Windows and Linux clusters.
GitHub Create Pull Request
Service Fabric Deploy a Service Fabric cluster using the Azure portal ...es/service-fabric/quickstart-classic-cluster-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 exclusively guides users to deploy a Service Fabric cluster using Windows Server 2019-Datacenter virtual machines, with no mention of Linux-based clusters or instructions for deploying on Linux. The operating system selection is hardcoded to Windows, and there are no examples, notes, or alternatives for Linux users. This creates friction for users who prefer or require Linux environments.
Recommendations
  • Include instructions and screenshots for deploying a Service Fabric cluster using Linux-based VM images (e.g., Ubuntu).
  • Add a section or note explaining the differences and considerations between Windows and Linux clusters.
  • Provide parity in certificate management steps for Linux (e.g., how to import and use certificates on Linux systems).
  • Ensure that the operating system dropdown selection is discussed, and both Windows and Linux options are shown.
  • Clarify any limitations or feature differences between Windows and Linux clusters.
GitHub Create Pull Request
Service Fabric Create clusters on Windows Server and Linux ...rvice-fabric/service-fabric-azure-clusters-overview.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 describes Service Fabric clusters on both Windows Server and Linux, but the technical details and examples are heavily skewed toward Windows. The only runtime process mentioned is FabricHost.exe and related Windows executables, with no mention of Linux equivalents or processes. There are no Linux-specific examples, commands, or operational notes, and Windows terminology and tooling are presented first and exclusively.
Recommendations
  • Include Linux-specific details, such as the names of equivalent Service Fabric processes and how they are managed on Linux (e.g., systemd services, process names).
  • Provide examples or notes for both Windows and Linux environments, especially in sections describing node setup and runtime behavior.
  • Add guidance or links for Linux users regarding cluster creation, management, and troubleshooting.
  • Ensure parity in operational instructions, such as how to start/stop Service Fabric services on Linux.
  • Explicitly mention any differences or considerations for Linux deployments, including supported distributions and configuration nuances.
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 exhibits a notable Windows bias. All command-line examples for interacting with the Central Secret Service REST API use PowerShell and Windows-specific tooling (Invoke-WebRequest, CertificateThumbprint), with no equivalent Linux/macOS examples (e.g., curl, openssl). Windows paths (C:\secrets) are shown first and in mainline examples, while Linux paths (/mnt/secrets) are relegated to comments. There is no guidance for Linux authentication or certificate handling, and no mention of Linux/macOS shell usage for API calls.
Recommendations
  • Provide REST API usage examples using curl for Linux/macOS, including authentication with client certificates.
  • Document how to obtain and use certificate thumbprints or equivalents on Linux/macOS.
  • Show Linux file paths and container mount points in main examples, not just as commented alternatives.
  • Clarify any OS-specific requirements or differences in Service Fabric cluster setup and secret management.
  • Ensure all critical workflows (create, set, examine secrets) have both Windows and Linux/macOS instructions.
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 references Service Fabric running on both Windows and Linux, but examples and tool mentions (e.g., Connect-WindowsFabricCluster) are Windows-centric. There is no mention of Linux-specific tools, commands, or migration considerations, and Windows tools are referenced before any Linux alternatives. No Linux/macOS command-line examples or parity notes are provided.
Recommendations
  • Include Linux/macOS equivalents for any Windows-specific tools or commands mentioned (e.g., reference Service Fabric CLI or REST APIs usable on Linux).
  • Add explicit examples or notes for Linux deployments, such as package management, cluster setup, and service management.
  • Where Windows tools are mentioned, provide Linux alternatives in parallel and clarify any platform-specific differences.
  • Ensure that API usage and migration steps are described in a cross-platform manner, highlighting any OS-specific considerations.
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 page exhibits a moderate Windows bias. Configuration examples and code samples frequently use Windows-centric formats (ClusterManifest.xml with <WindowsServer>), and PowerShell is the only CLI shown for service creation and updates. There are no Linux-specific examples, nor is there mention of Linux tools or shell commands. The documentation assumes familiarity with Windows constructs and does not provide parity for Linux/macOS users, especially in operational scenarios.
Recommendations
  • Add explicit examples for Linux clusters, such as configuration snippets using <Linux> infrastructure in ClusterManifest.xml.
  • Provide equivalent Bash/CLI commands for service creation and updates, using Service Fabric CLI (sfctl) or REST API, alongside PowerShell.
  • Clarify which configuration formats and tools are cross-platform, and note any differences or requirements for Linux/macOS clusters.
  • Include notes or links to Linux/macOS setup guides for standalone Service Fabric clusters.
  • Ensure that all operational instructions (service creation, updates, cluster configuration) have Linux/macOS equivalents.
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 page demonstrates a Windows bias by providing only PowerShell deployment examples, referencing Windows-style file paths, and omitting equivalent Linux/macOS command-line instructions. There are no Bash, Azure CLI, or cross-platform examples for deploying the updated ARM template, which may create friction for users on non-Windows platforms.
Recommendations
  • Add Azure CLI examples for deploying ARM templates, which work on Linux, macOS, and Windows.
  • Include Bash shell command examples for template deployment.
  • Use platform-neutral file path examples or clarify usage for different OSes.
  • Explicitly mention that all steps can be performed from Linux/macOS using Azure CLI or other supported tools.
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, but does not include equivalent Linux/macOS command-line examples (such as Bash, Azure CLI, or REST API). PowerShell is Windows-centric, and its exclusive use in examples creates friction for Linux/macOS users. The page also presents PowerShell before C#, reinforcing a Windows-first approach.
Recommendations
  • Add Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform.
  • Include REST API examples for service creation and updates, which are platform-agnostic.
  • Explicitly mention Linux/macOS support for Service Fabric management tasks and link to relevant cross-platform tooling.
  • Reorder examples to present cross-platform options (CLI, REST) before or alongside PowerShell.
  • Clarify any platform-specific limitations or requirements for Service Fabric management.
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 in Azure using the portal, which supports both Linux and Windows clusters. However, the examples and instructions consistently reference Windows-centric concepts (e.g., Remote Desktop username/password for VMs, PowerShell for management operations) and do not provide Linux-specific guidance (e.g., SSH access, Linux CLI commands). There are no explicit Linux management or connection examples, and Windows terminology appears first or exclusively in key sections.
Recommendations
  • Include explicit instructions for connecting to Linux-based cluster nodes, such as SSH access, and clarify differences in authentication (e.g., SSH keys vs. RDP credentials).
  • Provide Linux/macOS CLI examples for cluster management alongside PowerShell examples.
  • When mentioning VM access, specify both Windows (RDP) and Linux (SSH) scenarios, and offer guidance for setting up SSH keys in the portal.
  • Ensure that screenshots and terminology are inclusive of both OS types, or clearly indicate when steps differ for Linux clusters.
  • Add notes or sections for Linux-specific troubleshooting and operational patterns.
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 equivalents or examples, and all upgrade/configuration references point to Windows-focused documentation.
Recommendations
  • Include explicit instructions, examples, and links for upgrading and configuring Service Fabric clusters on Linux.
  • Reference or create documentation for Linux patch orchestration and OS management within Service Fabric clusters.
  • Ensure that all major sections (upgrade, configuration, patching) provide parity between Windows and Linux, with side-by-side examples or clear navigation to Linux-specific guides.
  • Avoid using 'Windows Server' in link titles unless a Linux equivalent is also provided.
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 using application manifests, C# APIs, and PowerShell. PowerShell is a Windows-centric tool, and no equivalent Linux/macOS CLI examples (such as Bash, Azure CLI, or REST API) are provided. The use of PowerShell is shown in every example section, and there is no mention of Linux-native tools or workflows. Additionally, resource monitoring for noncontainerized applications is explicitly stated as Windows-only, with Linux support limited to containerized workloads.
Recommendations
  • Add Linux/macOS-friendly examples using Azure CLI, Bash scripts, or REST API for configuring scaling policies.
  • Clarify cross-platform support for Service Fabric management tools and provide links to Linux-compatible alternatives.
  • Explicitly document any feature limitations for Linux clusters and suggest workarounds or alternatives where possible.
  • Present examples in a platform-neutral order (e.g., manifest, CLI, then PowerShell), or group by OS to avoid Windows-first bias.
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 exhibits moderate Windows bias. While most upgrade concepts are platform-neutral, specific operational examples and linked resources (such as OS patching) focus on Windows, and PowerShell is mentioned as a management tool without equivalent Linux/macOS command examples. The section on OS image upgrades links only to Windows patching guidance, omitting Linux. References to PowerShell/Azure CLI do not clarify parity or provide Linux-specific instructions.
Recommendations
  • Add explicit Linux/macOS examples for cluster management tasks, including Azure CLI and bash commands.
  • Include links to Linux patching guidance for Service Fabric clusters alongside Windows patching documentation.
  • Clarify that Azure CLI is cross-platform and provide sample commands for both Windows (PowerShell) and Linux/macOS (bash).
  • Ensure that all operational sections (e.g., certificate management, port opening) show both Windows and Linux workflows.
  • Review linked documents to ensure Linux parity and update cross-references as needed.
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 provides PowerShell-only instructions for validating upgrade paths, with no equivalent CLI, Bash, or Linux-native examples. Windows environments are listed first in cluster version outputs, and the only upgrade path validation steps are Windows-centric. Linux users are left to infer or research their own approach, creating friction for non-Windows administrators.
Recommendations
  • Add Azure CLI and/or Bash examples for upgrade path validation alongside PowerShell.
  • Explicitly mention Linux/macOS compatibility for all steps, especially scripting and automation.
  • Provide example outputs and instructions for both Windows and Linux environments in all relevant sections.
  • Ensure that Linux cluster version information is presented with equal prominence to Windows.
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 exhibits a moderate Windows bias. Windows tooling (Visual Studio, PowerShell) is described first and in greater detail, with step-by-step instructions and feature explanations. Linux alternatives (Yeoman, shell) are mentioned later and with less detail. The deployment section provides only PowerShell scripts for deploying the application, with no Linux CLI or Bash equivalents. Examples and screenshots are Windows-centric, and batch/PowerShell scripts are referenced without Linux shell script alternatives.
Recommendations
  • Provide Linux/Bash equivalents for all PowerShell deployment scripts, using Service Fabric CLI (sfctl) or REST API.
  • Include step-by-step instructions for Yeoman that match the detail given for Visual Studio.
  • Add examples of Linux shell scripts for setup and initialization, alongside batch/PowerShell examples.
  • Ensure screenshots and file paths include Linux variants (e.g., /home/user/app instead of C:\Dev\...).
  • Present Linux and Windows tooling in parallel, rather than Windows-first ordering.
  • Clarify any platform-specific limitations or differences in Service Fabric Explorer and related tools.
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 Windows bias by referencing Windows Event logs, ETW, and the Windows Azure diagnostics agent as primary mechanisms for accessing Service Fabric events. There are no explicit examples or guidance for accessing events on Linux-based clusters, nor are Linux-native tools or logging channels mentioned. The order and emphasis favor Windows approaches, potentially leaving Linux/macOS users without clear instructions.
Recommendations
  • Add explicit instructions and examples for accessing Service Fabric events on Linux clusters, including references to Linux-native logging systems (e.g., journald, syslog).
  • Mention cross-platform tools and APIs (such as REST APIs and the Service Fabric Client Library) as primary options, and clarify their applicability to both Windows and Linux clusters.
  • Reorder sections to present platform-neutral or cross-platform methods first, followed by platform-specific guidance.
  • Provide parity in diagnostic agent configuration instructions for Linux clusters, referencing the Linux diagnostics agent and its integration with Azure Monitor.
  • Include a comparison table or section outlining differences and similarities in event access between Windows and Linux clusters.
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 exhibits 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 using Azure CLI, Service Fabric CLI (sfctl), or REST API where applicable.
  • Provide examples for deploying, removing, and managing applications on Linux clusters.
  • Add references to Linux-specific documentation, tools, or scripts alongside PowerShell links.
  • Clearly indicate which steps or tools are platform-specific and offer alternatives for other platforms.
GitHub Create Pull Request
Service Fabric Report and check health with Azure Service Fabric ...ric-diagnostics-how-to-report-and-check-service-health.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: all setup, deployment, and health-check examples rely on Windows-specific tools (Visual Studio, PowerShell, Local Cluster Manager in the notification area). There are no Linux/macOS equivalents or instructions, and the examples and screenshots exclusively reference Windows environments and workflows. This creates friction for non-Windows users, who must find alternative tools and approaches not documented here.
Recommendations
  • Add instructions for setting up a local Service Fabric dev cluster on Linux/macOS, including required tools and commands.
  • Provide deployment and health-check examples using cross-platform tools (e.g., Azure CLI, REST API, Service Fabric CLI (sfctl)), and show how to use them on Linux/macOS.
  • Include Linux/macOS-specific prerequisites (e.g., .NET SDK, VS Code, or JetBrains Rider) and alternative project creation steps.
  • Show how to access Service Fabric Explorer from browsers on Linux/macOS, rather than relying on Windows notification area icons.
  • Present PowerShell and Windows examples alongside Linux/macOS equivalents, or use cross-platform commands first.
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 development tools (Visual Studio, PowerShell, .NET SDK) are mentioned first and in more detail than Linux equivalents. Linux tooling is referenced briefly (Eclipse, Yeoman, Java SDK), but without examples or parity in explanation. The quickstart link points to a .NET (Windows-centric) guide, with no visible Linux or cross-platform quickstart alternative. No Linux-specific examples or walkthroughs are provided.
Recommendations
  • Add Linux/macOS quickstart links alongside the Windows/.NET quickstart.
  • Provide example workflows and tooling for Linux (e.g., command-line deployment, SDK installation, cluster management) with equal detail.
  • Mention Linux tools (Eclipse, Yeoman, Java SDK) before or alongside Windows tools, and provide example usage.
  • Ensure all critical steps (deployment, management, monitoring) have both Windows and Linux/macOS instructions and examples.
  • Highlight cross-platform parity in the introduction and throughout the page.
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
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 Windows-centric tooling for all operational steps, with no mention of Linux/macOS equivalents or cross-platform alternatives. All code examples and instructions assume a Windows environment, creating friction for users on Linux or macOS who may not have access to PowerShell or the same command-line tools.
Recommendations
  • Provide equivalent instructions and examples using Azure CLI, which is cross-platform and widely used on Linux/macOS.
  • Explicitly mention how Linux/macOS users can perform each step, including any required setup (e.g., installing Azure CLI, using Bash scripts).
  • Add notes or sections clarifying platform requirements and offering guidance for non-Windows environments.
  • Where PowerShell is required, link to instructions for installing PowerShell Core on Linux/macOS, or offer alternative approaches.
  • Ensure that resource management steps (such as removing VM scale sets) are shown with both PowerShell and Azure CLI commands.
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 demonstrates a moderate Windows bias. The only explicit tooling example for testing backup/restore uses the PowerShell cmdlet 'Start-ServiceFabricPartitionDataLoss', with no mention of Linux/macOS alternatives. References to .NET APIs and kernel32 (Windows-specific) for file operations further reinforce the Windows-centric approach. There are no examples or guidance for Linux/macOS users, such as using Service Fabric CLI (sfctl) or Bash scripts, and Windows tools are mentioned exclusively and first.
Recommendations
  • Add equivalent Linux/macOS instructions for testing backup/restore, such as using the Service Fabric CLI (sfctl) or REST API.
  • Provide Bash or cross-platform script examples alongside PowerShell.
  • Clarify which APIs and file operations are cross-platform, and offer alternatives for Linux/macOS (e.g., using standard Unix file utilities instead of kernel32).
  • Explicitly mention platform compatibility for all tools and APIs.
  • Reorder examples to present cross-platform or platform-neutral options first, or side-by-side.
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 exhibits a moderate Windows bias. Windows-specific instructions (such as NSG rules for UDP/53 and network recreation on VM reboot) are provided in detail, while Linux-specific guidance is minimal or absent. The ability to mix networking modes is highlighted for Windows clusters, but Linux clusters are explicitly limited without further explanation or workaround. Most examples and configuration snippets are generic, but Windows-specific scenarios are called out and explained, whereas Linux equivalents are not.
Recommendations
  • Provide explicit Linux-specific instructions for networking setup, including any required NSG rules or configuration differences.
  • Clarify limitations for Linux clusters and suggest possible workarounds or alternatives.
  • Include Linux-focused examples and troubleshooting steps, especially where Windows-specific behavior is described.
  • Balance documentation by presenting Linux and Windows scenarios side-by-side where differences exist.
  • Expand on the implications of not supporting mixed networking modes on Linux, and offer guidance for Linux users.
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 ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by referencing Windows tools (PowerShell, Visual Studio) and providing examples and instructions that assume a Windows development environment. Linux-specific instructions are minimal and only mentioned in passing (e.g., certificate format), with no Linux/macOS equivalents for key tasks like viewing the cluster manifest or editing configuration files. The use of Windows-style file paths and reliance on Visual Studio further reinforces the bias.
Recommendations
  • Provide Linux/macOS equivalents for commands such as viewing the cluster manifest (e.g., using sfctl or REST API).
  • Include examples of editing configuration files on Linux (e.g., using nano/vim and Linux file paths).
  • Offer guidance for configuring and deploying Service Fabric applications from Linux/macOS environments, including references to cross-platform tools.
  • Ensure parity in instructions for certificate management, debugging, and configuration, with clear Linux/macOS steps.
  • Avoid assuming the use of Visual Studio; mention alternatives such as VS Code or command-line workflows.
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: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation page exhibits a notable Windows bias. Tutorials and walk-throughs are exclusively for Windows, with no mention of Linux or macOS equivalents. Examples and quickstarts are labeled as 'on Windows', and deployment instructions reference PowerShell scripts without alternatives for Bash or Linux environments. The 'Next steps' section also prioritizes Windows clusters, with no guidance for Linux cluster creation or management.
Recommendations
  • Add Linux/macOS equivalents for all tutorials and walk-throughs, including reliable services, actors, guest executables, and container applications.
  • Include deployment instructions and scripts for Bash/CLI alongside PowerShell, or provide cross-platform alternatives.
  • Ensure that cluster creation and management guidance covers both Windows and Linux clusters, with parity in examples and links.
  • When listing examples or quickstarts, alternate or group by platform, rather than listing Windows first or exclusively.
  • Explicitly mention platform support and limitations at the top of the page, so users know if content is Windows-only.
GitHub Create Pull Request
Service Fabric Azure Service Fabric CLI- sfctl chaos .../articles/service-fabric/service-fabric-sfctl-chaos.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 'sfctl chaos' shows evidence of Windows bias primarily in its use of Windows-specific terminology and references. The arguments for time ranges (--start-time-utc, --end-time-utc) are described as 'Windows file time', and the documentation links to .NET's DateTime.ToFileTimeUtc method, which is Windows/.NET-centric. There are no Linux/macOS-specific examples, nor is there any mention of how to obtain or format these time values on non-Windows platforms. The documentation does not provide parity for Linux/macOS users in these critical areas.
Recommendations
  • Provide equivalent instructions or examples for generating 'Windows file time' values on Linux/macOS (e.g., using Python, date commands, or other cross-platform tools).
  • Add references or links to cross-platform methods for working with time formats required by the CLI.
  • Clarify whether the CLI accepts standard Unix timestamps or ISO8601 formats, or provide conversion utilities/scripts.
  • Avoid referencing Windows/.NET methods exclusively; include alternatives for other platforms.
  • Explicitly state platform compatibility for all arguments and commands.
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: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation shows a notable Windows bias: it references only the creation of a Windows cluster, links to Windows-specific cluster management and diagnostics, and omits any mention of Linux clusters or Linux-specific guidance. While the deletion steps use cross-platform Azure CLI and PowerShell, the overall context and examples are Windows-centric, and Linux users may be left uncertain about parity or applicability.
Recommendations
  • Explicitly mention and link to instructions for creating and managing Linux-based Service Fabric clusters.
  • Include Linux-specific examples or clarify that the deletion steps apply equally to Linux clusters.
  • Add references to Linux diagnostics and management tools (e.g., how to patch Linux nodes, aggregate events for Linux clusters).
  • Balance the 'Next steps' section with Linux-focused resources and guides.
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 exhibits a Windows bias by providing detailed Windows-specific implementation details and code examples, while Linux instructions are less explicit and lack equivalent code samples. Windows terminology and tools (e.g., PFX, ACLs, X509Store) are described in depth, whereas Linux procedures are mentioned only briefly. The only code sample is for Windows, and there is no Linux shell or code example for certificate import.
Recommendations
  • Add equivalent Linux code samples (e.g., using OpenSSL or shell scripts) for importing PEM certificates into the container.
  • Provide step-by-step instructions for Linux users, including how to handle PEM and private key files inside containers.
  • Ensure that Linux-specific environment variables and certificate handling are explained as thoroughly as Windows.
  • Balance the order of presentation so that Linux and Windows instructions/examples are given equal prominence.
  • Clarify any platform-specific caveats or differences in certificate handling.
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 example commands for Azure CLI, PowerShell, and REST API. However, the PowerShell section is given equal prominence to CLI, despite PowerShell being primarily a Windows tool. The PowerShell examples are extensive and detailed, while there are no equivalent examples for Linux-native scripting (e.g., Bash). Additionally, PowerShell is listed before REST API, and there is no mention of Linux/macOS-specific considerations or alternative tools. The CLI examples are cross-platform, but the presence and depth of PowerShell examples indicate a moderate Windows bias.
Recommendations
  • Clarify that Azure CLI examples work on Linux, macOS, and Windows.
  • Add Bash shell scripting examples for Linux/macOS users, especially for more complex update scenarios.
  • Consider moving PowerShell examples after CLI and REST API, or grouping them in a 'Windows-specific' section.
  • Explicitly mention platform compatibility for each example (e.g., 'Works on Linux/macOS/Windows').
  • Provide troubleshooting tips for Linux/macOS users if there are known differences.
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 primarily references Azure Resource Manager deployment via PowerShell, which is a Windows-centric tool. There are no explicit Linux or cross-platform CLI examples, and the initial deployment instructions point to PowerShell documentation. While there is a mention of deploying a Linux scale set, the overall guidance and examples favor Windows tools and patterns.
Recommendations
  • Include Azure CLI examples alongside PowerShell for deployment steps, as Azure CLI is cross-platform.
  • Reference Bash or shell scripting options for Linux/macOS users.
  • Add links to Linux/macOS-specific documentation for deploying and managing scale sets.
  • Ensure that examples and instructions are presented in a platform-neutral order or explicitly note alternatives for non-Windows users.
GitHub Create Pull Request
Virtual Machine Scale Sets Get standby pool and instance details ...irtual-machine-scale-sets/standby-pools-get-details.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 operations, but PowerShell (a Windows-centric tool) is given equal prominence as CLI, and is presented immediately after CLI in every section. There are no Linux-specific shell examples (e.g., Bash, curl), nor are there notes about running PowerShell on Linux/macOS. The examples and instructions do not mention Linux/macOS environments or tools, and PowerShell is implicitly assumed to be available.
Recommendations
  • Add explicit Bash/curl examples for REST API calls to demonstrate Linux/macOS usage.
  • Clarify that PowerShell examples can be run on Linux/macOS using PowerShell Core, or provide instructions for installing PowerShell on non-Windows platforms.
  • Consider listing CLI (cross-platform) examples before PowerShell, and add notes about CLI being available on all platforms.
  • Include troubleshooting or environment setup notes for Linux/macOS users where relevant.
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
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 Azure Spot Virtual Machines in scale sets, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and is presented with a full example. There is no explicit Linux shell (bash) example, and the PowerShell section references a Windows-specific getting started article. The simulated eviction section links only to a Windows/PowerShell article for further information, omitting Linux guidance. The ARM template section references both Linux and Windows, but the example is generic. Overall, Windows tools and patterns are featured as primary or equal options, with Linux-specific instructions and examples underrepresented.
Recommendations
  • Add explicit bash/Linux shell examples for key tasks, especially for simulating eviction and deploying scale sets.
  • Provide links to Linux-specific documentation for simulated eviction and other advanced tasks, not just Windows/PowerShell articles.
  • Ensure that Azure CLI (cross-platform) examples are presented before PowerShell, or clarify CLI as the recommended cross-platform approach.
  • Where PowerShell is referenced, include a note about its availability on Linux/macOS, or provide alternative Linux-native instructions.
  • Balance references to getting started articles so both Linux and Windows users are equally supported.
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: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation shows a notable Windows bias in deployment examples and tooling. In multi-tabbed deployment sections, Windows/PowerShell examples are consistently presented first, with Linux/Azure CLI examples following. PowerShell is the only scripting language shown for imperative scripting, and all PowerShell examples target Windows-based scale sets. REST API examples also default to Windows. Linux-specific examples are only present in the Azure CLI sections, and there are no Linux PowerShell or Bash scripting examples. Troubleshooting commands are PowerShell-centric, and Windows log paths are listed before Linux equivalents. This ordering and tooling focus create friction for Linux/macOS users.
Recommendations
  • Present Linux and Windows examples in parallel, or alternate which is shown first to avoid implicit prioritization.
  • Provide imperative scripting examples for Linux users (e.g., Bash scripts using Azure CLI, or cross-platform PowerShell with ApplicationHealthLinux).
  • Ensure REST API examples alternate or include both ApplicationHealthLinux and ApplicationHealthWindows in the 'type' property.
  • In troubleshooting, show Linux log paths before or alongside Windows paths, and provide Azure CLI commands for health state retrieval.
  • Explicitly state that all extension operations are supported on both Linux and Windows, and clarify any differences in behavior or support.
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 demonstrates a moderate Windows bias. Windows and PowerShell examples are presented before Linux/Azure CLI equivalents, and Windows-specific links and terminology (e.g., referencing Windows scheduled events documentation first) are used throughout. PowerShell is given a dedicated section with detailed examples, while Linux-specific scripting (such as Bash or Python) is only briefly referenced, with no explicit Bash example for querying/responding to scheduled events. The REST API and Azure CLI sections are platform-neutral, but the overall structure and example ordering favor Windows users.
Recommendations
  • Present Linux/Azure CLI examples before or alongside Windows/PowerShell examples to ensure parity.
  • Include explicit Bash or Python examples for querying and responding to scheduled events, not just links.
  • Reference both Windows and Linux scheduled events documentation equally in all relevant sections.
  • Add troubleshooting steps specific to Linux environments (e.g., curl/jq usage, common errors).
  • Clarify that Azure CLI commands work cross-platform and highlight any OS-specific considerations.
GitHub Create Pull Request
Virtual Machines Share a Capacity Reservation Group in Azure ...s/virtual-machines/capacity-reservation-group-share.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 examples for API, Azure CLI, PowerShell, and ARM templates. PowerShell is featured as a primary automation tool throughout, and PowerShell examples are included in every tabbed section, sometimes with explicit links to Windows-specific modules. While Azure CLI is cross-platform, PowerShell is a Windows-centric tool (though it is available on Linux, usage is far less common among Linux users). There is no mention of Linux-native scripting or automation patterns (e.g., Bash, shell scripts), nor are Linux-specific considerations or examples provided. In several places, PowerShell is referenced before CLI, and links to PowerShell modules are given more prominence. No Linux/macOS-specific tools or workflows are discussed.
Recommendations
  • Add Bash/shell script examples for key operations, especially for Linux users who may prefer native scripting over PowerShell.
  • Clarify that Azure CLI is fully cross-platform and provide explicit instructions for Linux/macOS environments (e.g., installation, usage tips).
  • Where PowerShell is referenced, note its availability on Linux/macOS and provide guidance for those platforms.
  • Ensure CLI examples are shown before PowerShell, or at least alternate the order to avoid Windows-first perception.
  • Include troubleshooting or environment setup notes for Linux/macOS users, such as file path conventions, authentication, or package installation.
  • Consider referencing Linux-native automation tools (e.g., Ansible, Terraform) if relevant to the audience.
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 consistently provides examples using Windows images (Win2016Datacenter) for VM creation in both Azure CLI and PowerShell sections, with no equivalent Linux VM examples. The only quickstart linked for portal deployment is for Windows VMs. There are no Linux-specific instructions or examples for deploying or managing Ultra Disks, despite the feature being available for Linux VMs. This creates friction for Linux users, who must adapt Windows-centric instructions to their own environments.
Recommendations
  • Add Linux VM creation examples (e.g., using Ubuntu or CentOS images) alongside Windows examples in CLI and PowerShell sections.
  • Provide links to Linux VM quickstart guides in the portal deployment section.
  • Explicitly mention any Linux-specific considerations for Ultra Disk usage, partitioning, and formatting.
  • Ensure all code snippets and walkthroughs are presented for both Windows and Linux scenarios, or clarify when instructions are OS-agnostic.
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 page provides a detailed PowerShell script for checking VM SKU support for ephemeral OS disks, but does not offer equivalent examples or scripts for Linux/macOS users (e.g., Bash, Azure CLI). The only code sample is in PowerShell, and Windows tooling is referenced exclusively for critical tasks.
Recommendations
  • Add equivalent Azure CLI and/or Bash script examples for checking VM SKU support for ephemeral OS disks.
  • Present cross-platform instructions and scripts side-by-side, or indicate which tools are available on all platforms.
  • Explicitly mention how Linux/macOS users can perform the same tasks, including installation or usage notes for Azure CLI.
  • Where PowerShell is referenced, clarify if it can be used on Linux/macOS, or provide alternatives.
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 ⚠ī¸ missing_linux_example
Summary
The documentation shows a moderate Windows bias. Powershell and Windows-centric links/examples are referenced before Linux/CLI equivalents, especially in the custom RBAC role section. The custom role creation links only to a PowerShell page, with no Linux/CLI alternative. In other sections, both CLI and PowerShell are mentioned, but Windows tools or examples are often listed first. There is no explicit Linux example for custom role creation, and the overall flow assumes familiarity with Windows tooling.
Recommendations
  • Add links and examples for creating custom RBAC roles using Azure CLI or REST API, not just PowerShell.
  • Ensure that Linux/CLI documentation is referenced alongside or before Windows/PowerShell documentation in each section.
  • Provide explicit Linux/macOS command examples where possible, not just links.
  • Review the order of tool references to avoid Windows-first bias.
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 provides only PowerShell command-line examples, which are primarily relevant for Windows users. There are no Linux shell (bash/CLI) examples, and the command-line section is explicitly described as 'available through PowerShell.' This creates friction for Linux users, who must adapt Windows-centric instructions to their environment. The UI instructions are platform-neutral, but the lack of Linux command-line guidance is a notable gap.
Recommendations
  • Add equivalent Linux CLI examples using Azure CLI (az) or bash scripts for deploying the extension to Linux VMs.
  • Clarify in the command-line section that PowerShell can be used cross-platform, or explicitly mention how Linux users should proceed.
  • Provide step-by-step instructions for Linux users, including any prerequisites or differences in extension deployment.
  • Ensure parameter examples and explanations are not Windows-centric and are applicable to both platforms.
GitHub Create Pull Request
Virtual Machines Customer intent: "As a cloud administrator, I want to create and manage incremental snapshots of virtual disks, so that I can efficiently utilize storage and ensure data integrity while complying with the snapshot limitations and performance impacts." ...tual-machines-disks-incremental-snapshots-restrictions.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation references Azure PowerShell samples before Azure CLI, and links to PowerShell-specific scripts for checking disk status and background copy progress. This ordering and emphasis may create friction for Linux/macOS users, as PowerShell is primarily a Windows tool, and the CLI is more cross-platform.
Recommendations
  • Present Azure CLI examples and links before or alongside PowerShell equivalents.
  • Ensure all referenced scripts and samples have Linux/macOS compatible CLI versions.
  • Explicitly mention cross-platform compatibility and provide guidance for non-Windows users.
  • Add Bash or shell script examples where appropriate.
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_tools
Summary
The documentation provides only a PowerShell example for retrieving the encryption type of a disk in Azure, which is primarily a Windows tool. There are no equivalent examples for Linux/macOS users (e.g., using Azure CLI or Bash), and the documentation implicitly assumes the user is on Windows or using PowerShell Core.
Recommendations
  • Add Azure CLI (az) example for retrieving disk encryption type, which works natively on Linux/macOS.
  • Explicitly mention cross-platform alternatives and clarify which tools are supported on each OS.
  • Consider presenting CLI/Bash examples before or alongside PowerShell to improve parity.
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
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation is largely cross-platform and uses Azure CLI examples, which are suitable for both Linux and Windows. However, in the 'Next steps' section, disaster recovery scenarios are linked only to PowerShell-based guides (which are Windows-centric), and Hyper-V/VMware are Windows technologies. Additionally, Windows VM scenarios are referenced before Linux in some links and examples.
Recommendations
  • Provide equivalent Bash or Azure CLI-based guides for disaster recovery scenarios, especially for VMware and Hyper-V environments.
  • Include explicit Linux/macOS instructions or links where PowerShell is referenced.
  • Where possible, mention Linux alternatives or clarify cross-platform compatibility in linked guides.
  • Ensure Linux VM scenarios are given equal prominence in example sections and links.
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-specific tools (PowerShell, WinRM, Sysprep) and troubleshooting steps are frequently mentioned, often before or in more detail than their Linux equivalents. Examples and error logs for Windows (e.g., PowerShell commands, Windows Update, Sysprep) are more extensive, while Linux instructions (e.g., waagent, SSH) are present but less detailed. Some troubleshooting sections and DevOps logs focus on Windows paths and tools, with Linux alternatives either briefly mentioned or omitted.
Recommendations
  • Ensure Linux examples are provided alongside Windows ones, especially for troubleshooting steps and command-line instructions.
  • Present Linux and Windows instructions in parallel, rather than Windows-first ordering.
  • Expand Linux-specific troubleshooting guidance (e.g., common waagent issues, SSH connectivity problems, Linux log file locations).
  • Include Linux error log samples and solutions where only Windows examples are shown.
  • Balance the use of PowerShell and Bash/shell script examples for customizations and automation.
  • Reference Linux documentation and support resources as prominently as Windows ones.
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 page is focused on Linux VM images, but in the 'Before you begin' section, it references a tutorial for creating a managed image using Azure PowerShell (which is Windows-centric) and links to a snapshot guide under a Windows-specific path. No explicit Linux CLI or shell examples are provided, and Windows/PowerShell tools are mentioned before any Linux alternatives.
Recommendations
  • Provide explicit Linux CLI (e.g., Bash, Azure CLI) examples for creating managed images and snapshots.
  • Reference Linux-specific documentation for creating snapshots and images, rather than Windows paths.
  • Include parity in tooling instructions, such as showing both PowerShell and Bash/Azure CLI commands side-by-side.
  • Clarify that Azure PowerShell is cross-platform, or suggest Azure CLI as an alternative for Linux/macOS users.
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 guidance for Linux-specific configuration, nor any mention of Linux image names or considerations. This may cause confusion or friction for users deploying Linux VMs.
Recommendations
  • Include parallel examples using popular Linux images (e.g., 'UbuntuLTS', 'CentOS', 'Debian') alongside Windows examples.
  • Add notes clarifying whether MSP configuration steps differ for Linux VMs, or explicitly state if the process is identical.
  • Provide guidance on selecting Linux images and any Linux-specific flags or considerations.
  • Ensure screenshots and references are not Windows-centric, or provide Linux equivalents.
GitHub Create Pull Request
Virtual Machines Overview of Maintenance Configurations for Azure virtual machines ...rticles/virtual-machines/maintenance-configurations.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 mentions both Linux and Windows VMs are supported, and most content is platform-neutral. However, there is evidence of Windows bias: management options list Azure PowerShell before CLI, and the only code sample referenced is a PowerShell-based Azure Functions sample. No Linux-specific tools or shell examples are provided, and PowerShell is mentioned before CLI in several places. This may create friction for Linux users who prefer bash or native Linux tools.
Recommendations
  • Provide Linux/bash examples alongside or before PowerShell examples.
  • Reference CLI-based samples and repositories, not just PowerShell.
  • Explicitly mention that Azure CLI is cross-platform and provide links to Linux/macOS installation guides.
  • Ensure that management options and code samples are presented in a platform-neutral or Linux-first order.
  • Include troubleshooting steps or examples relevant to Linux environments.
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 examples and references that prioritize Windows environments. For instance, the WireServer schema example uses Windows-specific paths (e.g., 'C:\Windows\OEM\Unattend.wsf.exe') and process names ('winpa.exe', 'SYSTEM'), without offering equivalent Linux examples. The Linux-oriented example is limited to a generic Apache process, and there is no parity for common Linux provisioning agents or system users. Windows terminology and tooling are mentioned explicitly, while Linux equivalents are absent or less detailed.
Recommendations
  • Add Linux-specific examples for WireServer schema, such as using Linux provisioning agents (e.g., 'cloud-init', '/usr/bin/cloud-init', 'root' user).
  • Ensure that examples for process metadata, identities, and privileges include both Windows and Linux scenarios side-by-side.
  • Reference Linux system paths, users, and processes where applicable, not just Windows ones.
  • Clarify any platform-specific differences in GPA behavior or RBAC enforcement between Windows and Linux.
  • Avoid using Windows paths and process names exclusively in critical configuration examples.
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 displays a notable Windows bias. NVv4 VMs are stated to support only Windows guest OS, and all driver installation/setup links point to Windows-specific guides. There are no Linux migration steps, examples, or references to Linux driver installation or compatibility. FAQ and extension links are all Windows-focused, and Linux users are not provided with guidance or parity.
Recommendations
  • Explicitly state Linux support status for each VM series, including any limitations.
  • Provide Linux-specific migration steps, including driver installation and troubleshooting.
  • Add links to Linux GPU driver setup guides and extension documentation.
  • Include notes or tables comparing Windows and Linux support for each VM series.
  • If NVv4 does not support Linux, clarify this early and suggest alternatives for Linux users.
GitHub Create Pull Request
Virtual Machines Secure and use policies ...blob/main/articles/virtual-machines/security-policy.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 some Windows bias, notably by referencing Windows tools (PowerShell) before Linux equivalents (CLI), and by occasionally presenting Windows examples or terminology first. In the Key Vault section, Azure PowerShell is mentioned for Windows VMs before Azure CLI for Linux VMs. The Azure RBAC section lists the Azure portal and PowerShell before CLI. Some links and examples are Windows-first or Windows-only, and antimalware coverage is discussed only for Windows, with Linux support explicitly excluded.
Recommendations
  • Present Linux and Windows examples side-by-side, or alternate which is listed first.
  • When mentioning tools, list Azure CLI and PowerShell together, or highlight CLI for cross-platform parity.
  • Where features are Windows-only (e.g., antimalware), provide Linux alternatives or clarify Linux best practices.
  • Ensure all linked guides and walkthroughs have Linux equivalents and are equally visible.
  • Avoid language that implicitly prioritizes Windows (e.g., 'for Windows VMs, use PowerShell; for Linux, use CLI').
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 examples using Linux paths, Bash commands, and Linux file permission patterns. There are no Windows-specific examples, nor guidance for Windows users on how to generate, store, or use SSH keys (e.g., using PowerShell, Windows file paths, or PuTTY). This creates friction for Windows users who may not have Bash or native SSH tools available.
Recommendations
  • Add Windows-specific instructions and examples, such as using PowerShell or Windows Command Prompt to generate and use SSH keys.
  • Include guidance for using Windows-native tools like PuTTY or Windows OpenSSH client.
  • Show Windows file path formats in examples (e.g., C:\Users\username\.ssh\...).
  • Clarify any differences in workflow or prerequisites for Windows users (e.g., installing OpenSSH, using chmod alternatives).
  • Provide parity in example order, alternating or grouping by OS.
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 coverage for Azure Trusted Launch VMs, but there are several signs of Windows bias. PowerShell examples are exclusively for Windows (no Linux PowerShell Core parity), and Windows-specific tools and patterns (like RDP, BitLocker, and Windows image generalization) are mentioned more frequently and in greater detail. In PowerShell sections, only Windows VM creation is shown, with no Linux VM PowerShell example. In several places, Windows terminology and workflows are described first or in more depth than Linux equivalents.
Recommendations
  • Add PowerShell examples for Linux VM deployment (using PowerShell Core on Linux/macOS).
  • In PowerShell code samples, provide both Windows and Linux VM creation flows, or clarify which OS is being targeted.
  • When discussing image generalization, provide equal detail for Linux and Windows (currently, Windows is described more thoroughly).
  • Avoid Windows-first ordering in lists and examples; alternate or group by OS.
  • Where Windows-specific features (e.g., BitLocker, RDP) are mentioned, provide Linux equivalents or clarify their applicability.
  • Explicitly note when a tool or workflow is Windows-only, and suggest Linux/macOS alternatives where possible.
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 ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation exhibits a moderate Windows bias. Many code samples, especially in CI/CD pipeline sections (GitHub Actions, Azure DevOps, GitLab, Jenkins), default to Windows application file types (e.g., app.exe, app-config.json) and set --os-type Windows by default, even when running on Linux agents. PowerShell examples are abundant and sometimes precede or outnumber Linux/bash equivalents. Some install script examples for Windows (.exe, .msi, .ps1) are more detailed than their Linux counterparts. In multi-platform sections, Windows tools and patterns (msiexec, powershell.exe, .exe installers) are mentioned first or exclusively, while Linux equivalents (e.g., .deb, .rpm, .sh) are present but less emphasized. There are cases where Linux-specific examples or instructions are missing or less detailed, especially in automation pipelines.
Recommendations
  • In CI/CD pipeline examples (GitHub Actions, Azure DevOps, GitLab, Jenkins), provide parallel Linux-centric samples (e.g., using .sh, .deb, .rpm files and --os-type Linux) and clarify how to deploy Linux applications.
  • When showing install script examples, ensure Linux formats (.sh, .tar, .deb, .rpm) are given equal prominence and detail as Windows formats.
  • Avoid defaulting to Windows file types (app.exe, app-config.json) in generic examples; use neutral or alternate Linux file types (app.sh, app-config.yaml) or show both.
  • In sections where --os-type is set, explain how to set for Linux and Windows, and provide both examples.
  • Balance PowerShell and bash examples, and avoid placing Windows/PowerShell instructions before Linux/bash unless contextually justified.
  • Explicitly call out Linux prerequisites, tools, and patterns where Windows tools are mentioned (e.g., mention unzip/tar for Linux when msiexec/tar for Windows is shown).
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 creating VMs from gallery images, but PowerShell examples are significantly more detailed and tailored to Windows workflows. Windows-specific parameters and patterns (e.g., Set-AzVMOperatingSystem -Windows, RDP security rules, password creation dialogs) are prominent in PowerShell sections, and Windows VM creation is shown before Linux in several places. Linux examples are present, especially in CLI and REST, but PowerShell guidance is almost exclusively Windows-oriented, with little mention of Linux-specific PowerShell usage.
Recommendations
  • Add PowerShell examples for creating Linux VMs, including use of Set-AzVMOperatingSystem -Linux and SSH key authentication.
  • Ensure parity in parameter explanations for both Windows and Linux in PowerShell sections.
  • When showing VM creation steps, alternate or parallelize Windows and Linux examples, rather than presenting Windows first.
  • Clarify in PowerShell sections how to adapt commands for Linux VMs, not just Windows.
  • Review security group rules to include SSH (port 22) alongside RDP (port 3389) in PowerShell networking examples.
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 in several sections, PowerShell examples and instructions are given equal or greater prominence than Bash/Linux equivalents. Some troubleshooting steps (e.g., updating modules, error handling preferences) are specific to PowerShell/Windows and lack direct Linux/Bash analogs or guidance. In some cases, PowerShell instructions are presented before Bash, and additional details are given for PowerShell users (e.g., file locking).
Recommendations
  • Ensure that Bash/Linux instructions are presented first or in parallel with PowerShell/Windows instructions.
  • Where PowerShell-specific troubleshooting is given (e.g., module updates, error handling), provide equivalent Bash/Linux guidance (e.g., updating Azure CLI, handling errors in Bash scripts).
  • Add notes for Linux/macOS users where Windows-specific issues (like file locking) are mentioned, clarifying if/how these issues may differ.
  • Where possible, unify instructions so that both Bash and PowerShell users receive parity in troubleshooting detail and order.
  • Consider adding a table or clear separation for Bash/Linux vs. PowerShell/Windows steps to avoid confusion.
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 operations, but PowerShell (a Windows-centric tool) is given equal prominence as CLI, and is referenced in ARM template deployment options. There are explicit instructions and code for Windows containers (using PowerShell/Invoke-Expression), while Linux containers are described with a simple file path. The documentation does not provide Linux shell (bash) equivalents for Windows-specific PowerShell commands, and PowerShell is mentioned as a deployment method for ARM templates before any Linux-native alternatives.
Recommendations
  • Add bash or Linux shell script examples alongside PowerShell for users who prefer native Linux tooling.
  • Clarify that Azure CLI is cross-platform and highlight its usage for Linux/macOS users.
  • For ARM template deployment, mention Linux-native tools (such as curl, jq, or bash scripts) for REST API calls and template deployment.
  • For Windows container config map access, provide a Linux equivalent (e.g., using curl or cat) for parity.
  • Consider listing CLI (cross-platform) examples before PowerShell in each section to reduce Windows-first perception.
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_first ⚠ī¸ windows_tools
Summary
The documentation provides both Azure CLI and PowerShell examples for all major tasks, but PowerShell (a Windows-centric tool) is given equal prominence and detailed usage. ARM template deployment instructions mention both az CLI and PowerShell, but PowerShell is referenced first in some places. There is no explicit mention of Linux/macOS-specific shell usage (e.g., Bash), nor any guidance for Linux users regarding PowerShell compatibility or alternatives. The examples do not show any Linux/macOS shell-specific nuances, and the presence of PowerShell throughout may create friction for non-Windows users.
Recommendations
  • Clarify that Azure CLI commands work natively on Linux/macOS and provide Bash-specific usage notes where relevant.
  • Add explicit Bash shell examples or notes for Linux/macOS users, especially for scripting or environment setup.
  • In ARM template deployment instructions, mention az CLI (cross-platform) before PowerShell, or provide separate sections for Linux/macOS and Windows users.
  • Add a note about PowerShell Core compatibility on Linux/macOS, or link to installation instructions for non-Windows platforms.
  • Consider including troubleshooting or environment setup guidance for Linux/macOS users.
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 provides step-by-step instructions for configuring permissions using the Azure portal, which is a graphical interface accessible from any OS, but does not include any command-line examples (such as Azure CLI or PowerShell). The only mention of SDKs is 'PowerShell or CLI' in the context of querying the Runtime View API, but no concrete CLI or PowerShell examples are given. The portal workflow is described first and exclusively, which may disadvantage Linux/macOS users who prefer or require command-line automation.
Recommendations
  • Add Azure CLI examples for all role assignment steps, ensuring Linux/macOS users can follow along without relying on the portal.
  • Provide PowerShell examples as an alternative, but ensure CLI examples are shown first or side-by-side for parity.
  • Explicitly mention that all steps can be performed using Azure CLI or PowerShell, and link to relevant documentation.
  • For API queries, provide sample curl or az rest commands in addition to portal navigation.
  • Consider a table or section comparing portal, CLI, and PowerShell workflows for each major task.
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: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. The only provider registration example uses Azure PowerShell, and PowerShell is featured as a primary example in the availability zones section. While Azure CLI is also shown, PowerShell examples are presented first in the prerequisites and are given equal prominence in the tabbed example section. There is no explicit Bash or Linux shell example for provider registration, nor is there guidance for Linux/macOS users on alternative commands or tools.
Recommendations
  • Add Azure CLI and Bash examples for provider registration, not just PowerShell.
  • Ensure CLI examples are shown before or alongside PowerShell, especially in prerequisites.
  • Explicitly mention that Azure CLI works cross-platform and provide Linux/macOS usage notes where relevant.
  • Consider adding a table or section comparing command syntax for Windows (PowerShell), Linux (Bash/CLI), and macOS.
  • Review all code blocks to ensure Linux/macOS users are not required to use PowerShell.
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
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 requesting a container group from a standby pool, but PowerShell (a Windows-centric tool) is given equal prominence as CLI, and is presented before ARM template and REST examples. There are no Linux-specific shell examples (e.g., Bash scripts), and PowerShell is referenced without noting its limited support on Linux/macOS. Windows tools and patterns (PowerShell, New-AzContainerGroup) are mentioned without Linux alternatives or parity notes.
Recommendations
  • Add explicit Bash/Linux shell examples alongside Azure CLI, highlighting cross-platform usage.
  • Clarify that PowerShell examples are primarily for Windows users, and note PowerShell Core support on Linux/macOS if relevant.
  • Present CLI (cross-platform) examples first, before PowerShell, to emphasize platform neutrality.
  • Include notes or links for Linux/macOS users regarding installation and usage of Azure CLI and PowerShell Core.
  • Where possible, provide parity for scripting and automation on Linux/macOS (e.g., Bash, Python).
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 predominantly references PowerShell cmdlets (e.g., Remove-AzResource, AzSF PowerShell cmdlet) for managing Service Fabric resources, which are primarily associated with Windows environments. There is no mention of Linux/macOS equivalents, nor are CLI examples (such as Azure CLI) provided for common operations. This creates friction for users on non-Windows platforms who may not use PowerShell.
Recommendations
  • Include Azure CLI examples for all operations (e.g., az resource delete, az servicefabric managed-cluster application create) alongside PowerShell cmdlets.
  • Explicitly state platform compatibility for each tool or command, clarifying which are cross-platform.
  • Add notes or links to Linux/macOS installation guides for required tools.
  • Where possible, provide ARM template snippets as platform-neutral alternatives.
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 heavily focused on PowerShell and Windows-centric tooling. All code examples use Azure PowerShell cmdlets, and the tutorial centers on creating a PowerShell Azure Function. There are no examples or guidance for using other supported Azure Functions languages (such as Python or JavaScript), nor are there CLI-based alternatives for resource management. The use of Visual Studio Code is cross-platform, but the workflow assumes PowerShell familiarity and does not mention Linux/macOS shell patterns or alternatives. Linux users may face friction due to lack of Bash/CLI examples and the PowerShell-centric approach.
Recommendations
  • Provide equivalent examples using Azure CLI (az) commands for resource management, especially for enabling managed identity and assigning roles.
  • Include a parallel tutorial for creating an Azure Function using a cross-platform language (e.g., Python or JavaScript), or at least mention how Linux/macOS users can use PowerShell Core.
  • Explicitly state that PowerShell Core is supported on Linux/macOS and provide installation instructions or links.
  • Offer alternative code snippets for Bash or other shells where possible.
  • Add notes or sections highlighting differences or considerations for Linux/macOS users, such as authentication and environment setup.
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 exhibits a notable Windows bias. PowerShell is the only command-line example provided for cluster deployment and application packaging, with no Azure CLI or Bash equivalents. Visual Studio (Windows-only) is the sole IDE mentioned for development, and the 'Prepare your development environment' link points to Windows setup. There are no Linux/macOS-specific instructions or examples for cluster creation, deployment, or development, and Windows-centric tools and workflows are referenced first and exclusively throughout critical migration steps.
Recommendations
  • Add Azure CLI and Bash examples for cluster deployment, resource group creation, and application packaging/deployment.
  • Include instructions for setting up a Service Fabric development environment on Linux/macOS (e.g., using VS Code, .NET CLI, or JetBrains Rider).
  • Reference cross-platform tools and workflows alongside or before Windows-specific ones.
  • Provide parity in migration steps and troubleshooting for Linux/macOS users, including links to relevant documentation.
  • Explicitly note OS requirements and alternatives for each major step.
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, tools, and APIs (e.g., Win32 CryptoAPI, Windows certificate store paths, Windows event logs, CAPI1/CNG providers) are mentioned first and in detail, with Linux equivalents only briefly referenced or omitted. Troubleshooting and operational examples are Windows-centric, and there are no explicit Linux/macOS command-line or troubleshooting examples. This may create friction for Linux/macOS users managing Service Fabric clusters.
Recommendations
  • Provide explicit Linux/macOS equivalents for certificate store paths, certificate management, and troubleshooting steps (e.g., mention /var/lib/sfcerts, use of openssl, journalctl, syslog, etc.).
  • Include Linux/macOS command-line examples for certificate installation, validation, and troubleshooting alongside Windows/Powershell examples.
  • Clarify how Service Fabric interacts with certificates on Linux/macOS, including supported crypto providers and any platform-specific limitations.
  • Reference Linux/macOS documentation for certificate management and troubleshooting.
  • Ensure troubleshooting sections cover Linux/macOS log locations, error codes, and diagnostic tools.
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 for deploying and deleting Service Fabric applications use PowerShell cmdlets (e.g., New-AzResourceGroupDeployment, Get-AzResource, Remove-AzServiceFabricManagedClusterApplication) without mentioning or providing equivalent Azure CLI commands, which are cross-platform. The application packaging workflow is described using Visual Studio, a Windows-centric tool, with no mention of alternatives for Linux/macOS users. There are no Linux/macOS-specific instructions or examples, and Windows tools and patterns are presented exclusively and first.
Recommendations
  • Provide Azure CLI equivalents for all PowerShell deployment and deletion commands, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include instructions for packaging Service Fabric applications using cross-platform tools (e.g., dotnet CLI, SFCTL, or manual zip commands), not just Visual Studio.
  • Explicitly mention and demonstrate workflows for Linux/macOS users, including file path conventions and tool installation guidance.
  • Reorder examples or provide parallel examples for both Windows and Linux/macOS environments to avoid Windows-first presentation.
  • Add notes or links to official documentation for Linux/macOS development environments.
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
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a notable Windows bias. PowerShell is the only scripting language shown for programmatic certificate enrollment, and all automation examples use PowerShell cmdlets. The Key Vault VM extension is described and referenced exclusively in its Windows variant, with no mention of the Linux equivalent or cross-platform alternatives. The documentation references Windows-specific concepts (such as S-channel, ACLing, and certificate store locations like 'LocalMachine' and 'MY') without providing Linux analogs or guidance. Troubleshooting and FAQ sections also omit Linux-specific instructions or examples.
Recommendations
  • Provide equivalent Bash/CLI examples for certificate enrollment and management, using Azure CLI or REST API calls that work on Linux/macOS.
  • Reference and link to the Key Vault VM extension for Linux, and clarify differences or parity between Windows and Linux extensions.
  • Discuss Linux certificate store locations and access control mechanisms (e.g., file permissions, OpenSSL, etc.) alongside Windows concepts like ACLing and S-channel.
  • Ensure that automation and scripting examples are available for both PowerShell and Bash/CLI, and present them side-by-side or in separate sections.
  • Explicitly state platform-specific limitations or differences, and offer guidance for Linux/macOS users where Windows-only features are discussed.
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_tools ⚠ī¸ windows_first
Summary
The documentation references Service Fabric Explorer (a Windows-centric tool) and the Azure portal for cluster management tasks. It mentions viewing upgrade policies via PowerShell and resources.azure.com, but does not provide Linux/macOS equivalents or CLI examples. Windows tools and patterns are mentioned first or exclusively, with no parity for Linux users.
Recommendations
  • Provide equivalent instructions using Azure CLI and/or REST API for all management tasks, including viewing and updating cluster settings.
  • Mention cross-platform tools (e.g., Service Fabric CLI, az sf commands) and provide examples for Linux/macOS users.
  • Clarify which steps are platform-agnostic and which require Windows-only tools, offering alternatives where possible.
  • Include troubleshooting steps that use cross-platform commands, not just portal or PowerShell.
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 demonstrates a notable Windows bias: it refers to 'custom windows images' exclusively in the introduction, provides only PowerShell (Windows-centric) examples for role assignment, and links to Windows-specific resources before Linux equivalents. Linux examples, tools, and terminology are either missing or referenced secondarily, making it less accessible for Linux/macOS users.
Recommendations
  • Include explicit references to both Windows and Linux custom images in the introduction and throughout the documentation.
  • Provide equivalent CLI (az CLI) examples for role assignment and other operations alongside PowerShell commands.
  • Ensure that links to Linux documentation are presented alongside or before Windows links where appropriate.
  • Add ARM template examples and usage notes that clarify any OS-specific differences, especially for Linux-based images.
  • Clearly state support for Linux images and provide guidance for their creation and deployment.
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 as the primary tool for managing user-assigned managed identities, specifically linking to a PowerShell-centric guide. No Linux or cross-platform CLI alternatives (such as Azure CLI) are mentioned, and the only external tool reference is Windows-specific. However, the main deployment instructions are platform-neutral, focusing on ARM templates and XML manifests.
Recommendations
  • Include links and examples for Azure CLI commands to manage user-assigned managed identities, as Azure CLI is cross-platform.
  • Reference both PowerShell and CLI documentation when mentioning external guides.
  • Explicitly state that ARM template and manifest steps are platform-agnostic.
  • Add a note or section for Linux/macOS users, clarifying tool parity and usage.
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 provides only PowerShell-based command examples for critical steps such as retrieving service principal information and assigning roles. No CLI, Bash, or Linux/macOS-friendly alternatives are mentioned. PowerShell commands are presented as the default method, and there is no guidance for users on Linux or macOS platforms, which may create friction for non-Windows users.
Recommendations
  • Add equivalent Azure CLI (az) command examples for all PowerShell steps, especially for service principal retrieval and role assignment.
  • Include Bash script snippets or instructions for Linux/macOS users.
  • Clearly indicate that both PowerShell and CLI methods are supported and provide links to relevant cross-platform tooling documentation.
  • Consider presenting CLI examples before or alongside PowerShell to avoid Windows-first bias.
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: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page shows subtle Windows bias, primarily through references and links to Windows-specific tooling (notably PowerShell) and by omitting Linux/macOS equivalents. The only external command-line example is a link to a PowerShell-based guide for managing user-assigned managed identities, with no mention of Azure CLI or Bash alternatives. No explicit Linux/macOS instructions or examples are provided, and the documentation does not clarify cross-platform compatibility for deployment or management tasks.
Recommendations
  • Add Azure CLI and Bash examples for managing user-assigned managed identities alongside PowerShell references.
  • Explicitly mention that ARM template deployment and Service Fabric management can be performed from Linux/macOS, and provide links to relevant cross-platform documentation.
  • Where external guides are linked (e.g., for creating user-assigned identities), ensure both Windows (PowerShell) and Linux/macOS (Azure CLI) options are presented.
  • Consider a section or note on platform-agnostic workflows for Service Fabric managed clusters.
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 demonstrates a Windows bias by providing PowerShell-based examples for cluster management tasks (e.g., using Select-AzSubscription and Invoke-AzResourceAction), referencing PowerShell commands for node management, and omitting equivalent CLI or Bash examples for Linux/macOS users. The use of 'Az Module' and explicit PowerShell command links further reinforces this bias. No Linux/macOS-specific instructions or parity examples are given for critical operations.
Recommendations
  • Provide Azure CLI (az) command examples alongside or instead of PowerShell for all management tasks, as Azure CLI is cross-platform.
  • Explicitly mention that all API calls and ARM template operations can be performed from any OS, and provide Bash/cURL examples for REST API calls.
  • Where PowerShell commands are referenced (e.g., az sf cluster node add/remove), clarify that these are available via Azure CLI and show usage in Bash.
  • Add a section or callouts for Linux/macOS users, ensuring parity in instructions and tooling.
  • Avoid referencing 'Az Module' or PowerShell-specific tooling as the primary or only method for resource management.
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 and instructions for key deployment and role assignment steps. There are no CLI or Bash examples, and PowerShell is referenced as the primary automation tool, which is most commonly used on Windows. This may create friction for Linux/macOS users who prefer or require cross-platform tools like Azure CLI or Bash scripts.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, especially for authentication, resource group creation, deployment, and role assignment.
  • Explicitly mention that ARM template deployments and role assignments can be performed using Azure CLI or REST API, and link to relevant documentation.
  • Reorder examples so that cross-platform (CLI, portal) options are presented before or alongside PowerShell.
  • Include troubleshooting steps or notes relevant to Linux/macOS environments, such as certificate management or file path conventions.
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: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page demonstrates a moderate Windows bias. The only command-line deployment example provided uses PowerShell cmdlets, which are native to Windows. The instructions for admin access reference RDP, a Windows-specific protocol, and the admin credentials are described in a Windows-centric way. No equivalent Linux/macOS CLI (e.g., Azure CLI or Bash) deployment instructions are provided, nor are SSH-based admin access patterns mentioned. Windows tools and terminology are presented first and exclusively.
Recommendations
  • Add Azure CLI (az deployment group create) and/or Bash examples for ARM template deployment.
  • Include instructions for SSH-based admin access to VMs, and clarify that Linux-based admin accounts are supported.
  • Present Windows and Linux/macOS deployment options side-by-side, or alternate which is shown first.
  • Explicitly mention cross-platform support and provide links to Linux/macOS tooling documentation.
GitHub Create Pull Request
Service Fabric Upgrade the configuration of an Azure Service Fabric cluster ...-fabric/service-fabric-cluster-config-upgrade-azure.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 by listing PowerShell-based methods and tools before their Azure CLI equivalents, and by referencing Windows-centric tooling (PowerShell cmdlets) more prominently. While Azure CLI options are mentioned, PowerShell commands are given more detail and appear first, which may create friction for Linux/macOS users who are more likely to use CLI. No explicit Linux/macOS examples or guidance are provided.
Recommendations
  • Present Azure CLI and PowerShell options in parallel, with equal detail and prominence.
  • Add explicit examples for Linux/macOS users, such as CLI commands run in bash.
  • Clarify that all operations can be performed cross-platform using Azure CLI.
  • Avoid listing PowerShell commands before CLI commands unless there is a technical reason.
  • Include notes or links for installing and using Azure CLI on Linux/macOS.
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: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a moderate Windows bias. It references Windows-specific tools (such as the Key Vault VM extension for Windows), omits explicit Linux/macOS instructions or examples, and links primarily to Windows-focused resources. There are no PowerShell-only examples, but the lack of Linux parity in certificate installation and management steps may create friction for non-Windows users.
Recommendations
  • Include explicit instructions and examples for Linux and macOS environments, especially for certificate installation and management.
  • Reference and link to the Key Vault VM extension for Linux (if available), or provide alternative steps for Linux clusters.
  • Clarify whether the 'certificate store' concept applies to Linux nodes and, if so, provide guidance on equivalent locations and commands.
  • Present cross-platform CLI examples (e.g., Azure CLI, bash) alongside or before Windows-specific tools.
  • Add a section or note addressing Linux/macOS users and any differences in workflow.
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 ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a notable Windows bias. The introduction and instructions focus on enabling disk encryption for Service Fabric managed cluster nodes 'in Windows'. All deployment and verification examples use PowerShell commands, and references point to Windows-specific documentation. While Azure CLI is briefly mentioned for Key Vault steps, the overall workflow, including cluster deployment and status verification, is presented only with PowerShell. There is no guidance or examples for Linux/macOS users, nor is there mention of Linux-specific tooling or patterns for cluster management.
Recommendations
  • Add explicit instructions and examples for Linux/macOS users, including Bash/Azure CLI equivalents for all PowerShell commands.
  • Reference Linux-specific documentation where appropriate, especially for disk encryption verification and management.
  • Clarify which steps are OS-agnostic and which require Windows, and provide alternatives for non-Windows platforms.
  • Present Azure CLI and Bash examples alongside PowerShell, or in a tabbed format, for all deployment and verification steps.
  • Update the page title and description to reflect cross-platform applicability if supported.
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: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation references provisioning IP tags using a PowerShell module (Az.Network), which is a Windows-centric tool, and does not provide equivalent instructions or examples for Linux/macOS users (e.g., Azure CLI or REST API). No Linux/macOS-specific guidance or parity is offered.
Recommendations
  • Include instructions and examples for provisioning IP tags using Azure CLI, which is cross-platform.
  • Reference REST API methods for provisioning IP tags, suitable for all platforms.
  • Explicitly state that PowerShell is one option and provide alternatives for Linux/macOS users.
  • Add links to Azure CLI documentation for creating public IP addresses with IP tags.
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
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 example commands for Azure CLI, Azure PowerShell, ARM templates, and the Azure portal. However, the PowerShell example is detailed and multi-step, while the Azure CLI example is a single command with minimal explanation. There is no mention of Linux/macOS-specific considerations, nor is there parity in example depth for CLI usage on Linux. PowerShell is a Windows-centric tool, and its example is given more prominence and detail than the CLI, which is cross-platform. The ordering of examples also places PowerShell before the portal, which is more OS-neutral.
Recommendations
  • Expand the Azure CLI section to include step-by-step instructions equivalent to the PowerShell example, ensuring Linux/macOS users have clear guidance.
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Add notes or links for installing and using Azure CLI on Linux/macOS.
  • Consider reordering examples to present CLI before PowerShell, or group them as 'cross-platform' and 'Windows-specific'.
  • If PowerShell Core is supported on Linux/macOS, clarify this and provide installation guidance.
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 node types), but does not offer equivalent examples for Linux/macOS users (e.g., Azure CLI, Bash, or cross-platform scripting). PowerShell is a Windows-centric tool, and its exclusive use creates friction for users on other platforms. Additionally, PowerShell examples are presented before any mention of alternatives, and no Linux/macOS-specific instructions or notes are provided.
Recommendations
  • Add Azure CLI examples for all command-line operations alongside PowerShell, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that PowerShell Core is available for Linux/macOS, if relevant, and provide installation guidance or links.
  • Where possible, provide Bash script examples or note how ARM template deployments can be performed using Azure CLI on any OS.
  • Structure command-line sections to present cross-platform options first, or in parallel, rather than defaulting to Windows/PowerShell.
  • Add a note clarifying platform compatibility for all tools mentioned.
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
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation demonstrates a moderate Windows bias, primarily through the exclusive use of PowerShell for all command-line examples, frequent references to Windows-specific concepts (such as RDP and Remote Desktop Connection), and the absence of equivalent Linux/macOS CLI or tooling instructions. Windows clusters and tools are mentioned first or exclusively in several sections, and screenshots are Windows-centric. Linux users are left to infer how to adapt instructions, which may create friction but does not block completion of tasks.
Recommendations
  • Provide Azure CLI (az) command examples alongside PowerShell for all resource management tasks, especially for role assignments, resource group creation, and deployments.
  • Include SSH instructions and screenshots for remote access to Linux-based clusters, in addition to RDP/Windows examples.
  • Clarify which steps and properties apply to Linux clusters, and note any differences in port mappings, NAT rules, or networking behavior.
  • Add explicit guidance for Linux/macOS users on how to verify public IPs, connect to nodes, and deploy ARM templates using cross-platform tools.
  • Reorder sections or examples so that Windows and Linux approaches are presented with equal prominence.
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. All command-line examples use PowerShell cmdlets (New-AzResourceGroup, New-AzUserAssignedIdentity, etc.) with no equivalent Azure CLI or Bash examples for Linux/macOS users. The VM image example uses Windows-specific values (MicrosoftWindowsServer, WindowsServer, 2019-Datacenter) without mention of Linux alternatives. The troubleshooting section references the Azure portal but does not discuss cross-platform command-line troubleshooting. There is no guidance for users who prefer or require Linux/macOS tools.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all resource creation and deployment steps.
  • Include ARM template snippets for Linux node types (e.g., using Ubuntu or other Linux images).
  • Explicitly mention Linux/macOS compatibility and provide Bash/CLI commands where possible.
  • Reorder examples so that cross-platform (ARM template, Azure CLI) options are shown before or alongside PowerShell.
  • Add troubleshooting steps using Azure CLI for role assignments and identity management.
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 command example for bypassing Infrastructure Service throttling, with no mention of Linux/macOS equivalents or cross-platform alternatives. The use of Service Fabric Explorer (a GUI tool) is referenced, but command-line guidance is Windows-centric. There are no bash, CLI, or REST API examples for Linux users.
Recommendations
  • Include equivalent bash or Azure CLI commands for Linux/macOS users.
  • Document REST API or cross-platform alternatives for cluster management tasks.
  • Clarify whether the PowerShell cmdlet is available via Azure CLI or other non-Windows tools.
  • Add explicit notes about platform compatibility for all command examples.
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 page demonstrates notable Windows bias. The only CLI command provided is a PowerShell cmdlet (Add-AzServiceFabricManagedNodeTypeVMExtension), with no mention of Azure CLI, Bash, or cross-platform alternatives. The ARM template examples exclusively use the 'KeyVaultForWindows' extension type and do not show Linux equivalents (e.g., KeyVaultForLinux). Windows-specific extension types and patterns are referenced before any Linux options, and no guidance is given for Linux/macOS users.
Recommendations
  • Provide Azure CLI and Bash examples alongside PowerShell commands for adding VM extensions.
  • Include ARM template examples using Linux-compatible extension types (e.g., KeyVaultForLinux) and clarify when to use each.
  • Explicitly mention Linux/macOS support and any differences in extension configuration or behavior.
  • List both Windows and Linux extension types in documentation, with guidance on choosing the appropriate one.
  • Ensure that instructions for critical tasks (e.g., disk encryption) include Linux-specific steps or references.
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 multiple times as the primary example for cluster management actions, with direct links to PowerShell cmdlets. There are no explicit Linux/macOS command examples or callouts for cross-platform usage, and PowerShell is mentioned before Azure CLI or other platform-neutral tools. The best practices section and examples focus on PowerShell, which is traditionally associated with Windows, despite the existence of cross-platform alternatives.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, especially for deleting, restarting, or reimaging NodeTypes/VMSS.
  • Explicitly mention that Azure CLI and Bicep are cross-platform and suitable for Linux/macOS users.
  • Reorder tool recommendations to list platform-neutral tools (Azure CLI, Bicep, ARM templates) before PowerShell.
  • Provide sample workflows or command snippets for Linux/macOS users using Azure CLI and sfctl.
  • Clarify that PowerShell is available cross-platform, but highlight CLI and sfctl as alternatives.
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 exhibits a Windows bias by referencing Windows-specific tools (Performance Monitor), listing Windows performance counters exclusively, and omitting Linux equivalents or instructions. There are no examples or guidance for monitoring Service Fabric on Linux clusters, nor mention of Linux performance metrics or tools.
Recommendations
  • Add equivalent Linux performance counter categories and metrics (e.g., using /proc, sysstat, or collectd).
  • Include instructions or examples for collecting metrics on Linux nodes, such as using Azure Monitor agent on Linux.
  • Reference Linux monitoring tools (e.g., atop, htop, sar) alongside Windows Performance Monitor.
  • Clarify which metrics and counters are available on Linux clusters and how to access them.
  • Provide parity in documentation structure, ensuring Linux and Windows are both covered in each section.
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: 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 (EventStore APIs, Diagnostics Agent, Event Viewer, ETW) are mentioned before or in more detail than their Linux equivalents. Some features, such as EventStore APIs and Diagnostics Agent, are explicitly stated to be Windows-only, with Linux alternatives referenced only briefly or in separate documentation. Examples and tutorials focus on .NET/Windows scenarios, with Linux-specific guidance often relegated to separate links or notes. Linux monitoring options are mentioned, but not with the same depth or clarity as Windows options.
Recommendations
  • Provide parallel Linux examples and tutorials for all monitoring scenarios, especially where Windows-only guides are referenced.
  • Clarify Linux equivalents for Windows tools (e.g., show how to access and query Service Fabric events on Linux clusters, including LTTng and Syslog usage).
  • Ensure that Linux monitoring configuration steps are included inline, not just as links to other pages.
  • Highlight cross-platform tools and approaches first, then discuss OS-specific details.
  • Add explicit Linux/macOS instructions for agent setup, event querying, and application logging where currently only Windows/.NET examples are given.
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 the Azure portal GUI and does not provide any command-line examples for certificate management, cluster deployment, or resource cleanup. The only mention of operating systems is that the deployed nodes are Windows Server 2019 VMs; there is no discussion of Linux-based clusters or how Linux/macOS users can interact with the cluster (e.g., importing certificates, accessing Service Fabric Explorer, or using CLI tools). Steps like importing certificates assume familiarity with Windows certificate stores, and there is no guidance for Linux/macOS users on equivalent procedures.
Recommendations
  • Provide command-line instructions (using Azure CLI, Bash, or PowerShell) for all major steps, including resource group creation, Key Vault setup, certificate generation, and cluster deployment.
  • Include guidance for importing and using certificates on Linux and macOS systems, such as using OpenSSL and browser certificate stores.
  • Clarify whether Service Fabric managed clusters can be deployed with Linux nodes, and if so, provide instructions and examples.
  • Explicitly mention cross-platform compatibility in prerequisites and throughout the guide.
  • Add screenshots or instructions for Linux/macOS environments where relevant (e.g., browser certificate prompts, certificate import steps).
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 demonstrates a moderate Windows bias. Windows-specific features (Active Directory, gMSA, BitLocker) are described in detail, while Linux equivalents are either missing, referenced only in passing, or marked as TODO. Examples and guidance for Linux users (e.g., disk encryption, service accounts) are notably absent or less prominent. Windows tools and patterns (e.g., PowerShell, BitLocker) are mentioned without Linux alternatives.
Recommendations
  • Add explicit Linux examples for service account management, including how to run services under different Linux users/groups.
  • Provide guidance and examples for encrypting disks/data at rest on Linux clusters, referencing supported Linux technologies (e.g., dm-crypt, LUKS).
  • Include Linux-specific instructions for certificate management and container security, such as how to import certificates into Linux containers.
  • Balance references to Windows-only features (Active Directory, gMSA, BitLocker) with Linux equivalents or note their absence and provide workarounds.
  • Ensure that examples and walkthroughs are provided for both Windows and Linux environments, ideally side-by-side.
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
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page presents a platform-agnostic overview but exhibits Windows bias in several areas. The only concrete scripting example for deploying secrets uses PowerShell, with no equivalent Linux CLI (e.g., Bash, sfctl) example. Windows tools and patterns (PowerShell, C#) are mentioned first and exclusively in scripting contexts. While certificate setup is split between Windows and Linux, the main body of the documentation and code samples are Windows-centric, with Linux parity implied but not demonstrated.
Recommendations
  • Add explicit Linux/Bash/sfctl examples for application deployment and parameter overrides, parallel to the PowerShell example.
  • Mention Linux tools and workflows alongside Windows tools, not just in separate setup links.
  • Clarify any platform-specific differences in manifest handling or secret injection.
  • Ensure scripting and automation guidance is provided for both platforms in all relevant sections.
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 exhibits a Windows bias by prioritizing PowerShell and Visual Studio (Windows-only tools) in both structure and examples. The parameters sections for PowerShell and Visual Studio are presented first and in greater detail, with example formats specific to PowerShell (e.g., hashtable syntax). Linux/macOS equivalents (SFCTL CLI) are covered in a separate, later section, with less emphasis and no example commands. There are no explicit Linux/macOS shell examples, and the documentation does not mention cross-platform usage patterns or differences. The 'Next steps' section also lists Windows-centric tutorials before Linux equivalents.
Recommendations
  • Present SFCTL (CLI) examples and parameters alongside PowerShell/Visual Studio, not in a separate section.
  • Provide explicit Linux/macOS shell command examples for SFCTL, including parameter usage.
  • Add a table or summary comparing PowerShell, Visual Studio, and SFCTL usage for each parameter.
  • Mention platform compatibility and highlight any differences in behavior or syntax between Windows and Linux/macOS tools.
  • Ensure 'Next steps' lists Linux/macOS tutorials with equal prominence and order.
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 tooling (PowerShell, Remove-AzResource) is referenced exclusively and prominently, while Linux-friendly alternatives (Azure CLI, Bash, REST via curl) are only mentioned in passing or not at all. The 'Next steps' section lists PowerShell before CLI, further reinforcing Windows-first patterns.
Recommendations
  • Add Azure CLI and Bash examples for all PowerShell commands, especially for resource removal and management.
  • Explicitly mention cross-platform tools and workflows, such as using Azure CLI or REST API via curl.
  • Reorder or parallelize 'Next steps' to show CLI and PowerShell equally, or mention CLI first to balance.
  • Clarify that all operations can be performed from Linux/macOS environments and provide links to relevant cross-platform documentation.
  • Where PowerShell is referenced, note its availability on Linux/macOS, or suggest alternatives if features differ.
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: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page demonstrates a notable Windows bias, primarily through the heavy use of PowerShell cmdlets for operational examples and automation. Windows-specific tools (PowerShell) are consistently mentioned alongside .NET APIs and REST operations, but Linux equivalents (such as Azure CLI or Service Fabric CLI 'sfctl') are rarely referenced directly in the main workflow steps. In most cases, PowerShell is listed before REST or other cross-platform options, and there are no explicit Linux/macOS command examples or instructions, which may create friction for non-Windows users.
Recommendations
  • Include Azure CLI and Service Fabric CLI (sfctl) command examples for each operational step, especially for deployment, upgrade, removal, and cleanup tasks.
  • Explicitly mention cross-platform tools (CLI, REST) before or alongside PowerShell, rather than after.
  • Add Linux/macOS-specific instructions or notes where workflows differ, or where additional setup is required.
  • Provide example scripts for common Linux shell environments (bash/zsh) where automation is discussed.
  • Clarify which tools are cross-platform and which are Windows-only, to help users choose the right approach.
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 exhibits Windows bias by listing Visual Studio and PowerShell upgrade tutorials as the only explicit next steps, both of which are primarily Windows tools. There are no Linux/macOS equivalents or cross-platform CLI examples provided, and Windows-centric tools are mentioned before any alternatives.
Recommendations
  • Add explicit instructions or links for upgrading applications using cross-platform tools such as Azure CLI or Service Fabric CLI (sfctl), which work on Linux/macOS.
  • Include Linux/macOS-specific examples or tutorials alongside Visual Studio and PowerShell guides.
  • Reorder the 'Next steps' section to present cross-platform options first or in parallel with Windows-specific tools.
  • Clarify which tools are Windows-only and suggest alternatives for non-Windows 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
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 using PowerShell commands and outputs for all troubleshooting examples, with no mention of Linux or cross-platform CLI equivalents. All command-line instructions rely on PowerShell cmdlets, which are traditionally Windows-centric, and there is no guidance for users running Service Fabric on Linux or macOS. The 'Next steps' section also prioritizes Visual Studio (Windows-only) and PowerShell tutorials, further reinforcing the Windows-first approach.
Recommendations
  • Provide equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • Add explicit instructions and troubleshooting steps for Linux-based Service Fabric clusters, including relevant commands and expected outputs.
  • Clarify which commands are Windows-only and offer alternatives for non-Windows environments.
  • Reorder or balance 'Next steps' to include Linux/macOS tooling (e.g., sfctl, REST API) alongside Windows tools.
  • Note any platform-specific limitations or differences in troubleshooting workflows.
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 demonstrates a notable Windows bias. The only code example provided uses PowerShell, a Windows-centric tool, with no equivalent example for Linux/macOS users (e.g., using Azure CLI, REST API, or Service Fabric CLI). Windows-specific tools and APIs (PowerShell cmdlets, http.sys) are referenced exclusively or first, and there is no mention of Linux-compatible upgrade workflows. The troubleshooting and next steps sections also prioritize Windows tools (Visual Studio, PowerShell) without Linux alternatives.
Recommendations
  • Add equivalent Linux/macOS examples using Azure CLI, Service Fabric CLI (sfctl), or REST API for application upgrade operations.
  • Explicitly mention cross-platform tools and workflows where possible, and clarify which steps are platform-specific.
  • Provide troubleshooting and upgrade guidance for Linux clusters, including links to relevant documentation.
  • Avoid referencing Windows-specific APIs (e.g., http.sys) without noting their platform limitations or providing Linux context.
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 page demonstrates a Windows bias primarily in the backup storage section, where file share examples and authentication methods are described exclusively using Windows paths (\\StorageServer\BackupStore) and Windows authentication mechanisms. There is no mention of Linux-compatible file share paths (e.g., NFS mounts), nor are Linux authentication patterns or examples provided. The documentation also refers to 'Integrated Windows Authentication' without alternatives for Linux environments. This can create friction for Linux users deploying Service Fabric clusters outside Windows environments.
Recommendations
  • Add examples for Linux-compatible file share paths (e.g., NFS mounts like /mnt/backupstore) and clarify support for SMB/NFS on Linux clusters.
  • Document authentication options for file shares on Linux, such as using mount credentials or Kerberos, and provide example configurations.
  • Explicitly state platform compatibility for each backup storage type and clarify any limitations or required steps for Linux/macOS clusters.
  • Reorder examples to present platform-neutral or Linux options alongside Windows, rather than Windows-first.
  • Include troubleshooting or notes for Linux users regarding file share integration and authentication.
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 demonstrates a Windows bias in the Management subsystem section, where PowerShell cmdlets are mentioned as the primary tooling for provisioning, deploying, and managing Service Fabric applications. There is no mention of equivalent Linux/macOS tools or CLI commands, nor are cross-platform alternatives discussed. The transport subsystem also references 'Windows security' alongside X509 certificates, but does not clarify Linux support. No explicit Linux/macOS examples or parity are provided throughout the page.
Recommendations
  • Include references to cross-platform management tools, such as Azure CLI or REST APIs, alongside PowerShell cmdlets.
  • Add explicit examples or documentation links for Linux/macOS users to perform management tasks (provision, deploy, patch, upgrade, de-provision).
  • Clarify the transport subsystem's support for Linux security mechanisms and provide details on certificate management for non-Windows platforms.
  • Ensure that tooling and command references are presented in a platform-neutral or platform-inclusive manner.
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 provides both Azure CLI and PowerShell examples for deploying Service Fabric clusters, but PowerShell (a Windows-centric tool) is given a dedicated section and is used for cluster upgrades without Linux alternatives. Windows-specific configuration (e.g., registry keys, Windows Update settings) is described in detail, while Linux equivalents are missing. Upgrade instructions and examples focus on Windows tools and patterns, with Linux instructions relegated to links in the 'Next steps' section.
Recommendations
  • Provide equivalent Linux shell (bash) examples for all PowerShell commands, especially for cluster upgrades.
  • Include Linux-specific configuration guidance for VM OS upgrades (e.g., disabling unattended-upgrades or apt settings).
  • Mention Linux tools and patterns alongside Windows ones, not just in 'Next steps'.
  • Add instructions for handling Linux package formats (deb/rpm) in upgrade scenarios.
  • Ensure that Windows-specific registry/configuration advice is paired with Linux equivalents or notes.
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 demonstrates a notable Windows bias. Critical operational steps (such as scaling in/out nodes) are described exclusively with PowerShell commands and Windows-centric tools, with no equivalent Linux CLI or script examples. The only manual command-line instructions use PowerShell, and references to Service Fabric Explorer and related commands assume a Windows environment. Linux alternatives (e.g., Service Fabric CLI, Bash, or REST API) are not mentioned, and Windows tools/patterns are presented first and exclusively in operational sections.
Recommendations
  • Add equivalent Linux/Bash/Service Fabric CLI (sfctl) examples for all PowerShell commands (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState).
  • Explicitly mention and link to Linux operational guides for scaling and node management.
  • Clarify which steps are OS-agnostic and which require platform-specific tooling.
  • Where C# SDK examples are given, note cross-platform compatibility and provide guidance for Linux users.
  • Reorder or parallelize instructions so that Linux and Windows approaches are presented together, not Windows-first.
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 exhibits several instances of Windows bias. Windows and PowerShell tools are referenced before or more prominently than Linux equivalents, especially in API and DevOps sections. Some examples and ARM templates are Windows-specific, and PowerShell is mentioned as the primary client API use case. Linux-specific instructions and examples are less detailed or referenced after Windows. Windows container networking and update scenarios are described in detail, while Linux equivalents are less emphasized.
Recommendations
  • Provide Linux CLI (az, bash) examples alongside or before PowerShell examples, especially for networking and API access.
  • Include Linux-specific ARM template samples and reference them equally with Windows ones.
  • Clarify when instructions or port rules differ for Linux clusters, and provide explicit Linux guidance.
  • Add more detail for Linux container networking scenarios, including best practices and troubleshooting.
  • Balance references to Windows and Linux in introductory and summary sections, ensuring parity in guidance and links.
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 demonstrates a moderate Windows bias. Windows-specific tools (PowerShell, Windows Defender, DSC) are mentioned first or exclusively in several sections, with Windows examples often preceding Linux equivalents. Some features, such as Windows Defender and security baselines, are only discussed for Windows, and Linux alternatives are not provided. While Linux instructions are present for certificate encryption, other areas lack Linux parity or present Windows as the default platform.
Recommendations
  • Ensure Linux examples are presented alongside Windows examples, not after them.
  • Provide Linux equivalents or alternatives for Windows-specific tools (e.g., suggest Linux antimalware solutions where Windows Defender is discussed).
  • Avoid language that implies Windows is the default or preferred platform.
  • Add references to Linux security baselines and configuration management tools (e.g., CIS benchmarks, Ansible, Chef) where Windows DSC and baselines are mentioned.
  • Where Windows-specific features are described, explicitly state Linux support status and link to Linux documentation.
  • Balance example ordering so Linux and Windows are treated equally.
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 provides detailed instructions and examples for configuring Microsoft Entra ID authentication for Service Fabric clusters, but all command-line connection examples use PowerShell, which is primarily a Windows tool. There are no equivalent Linux/macOS CLI examples (e.g., Azure CLI, REST API, or cross-platform SDK usage), and troubleshooting steps reference PowerShell scripts. Windows-specific options (such as configuring authentication for existing clusters) are mentioned, while Linux users are directed to do setup only before cluster creation. There is a known issue noted for Linux clusters, but no Linux-specific guidance or workarounds are provided.
Recommendations
  • Add equivalent Azure CLI or REST API examples for connecting to Service Fabric clusters with Microsoft Entra ID authentication on Linux/macOS.
  • Include instructions or references for using cross-platform SDKs (e.g., .NET Core, Python) to connect to clusters.
  • Provide troubleshooting steps for Linux users, including common issues and solutions.
  • Clarify any platform-specific limitations and offer alternative workflows for Linux/macOS users.
  • Ensure that examples and instructions are presented in a platform-neutral order, or provide parallel guidance for both Windows and Linux/macOS.
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 and deploying 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, with no actionable guidance or examples for Linux users.
Recommendations
  • Include Azure CLI examples for testing and deploying Resource Manager templates, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Reference or provide sample templates for Linux clusters, not just Windows-based ones.
  • Add explicit instructions or links for Linux/macOS users on how to perform certificate management and parameter population tasks.
  • Ensure that any PowerShell-specific guidance is paired with Azure CLI or Bash alternatives.
  • Clarify any platform-specific requirements or differences in the workflow.
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 demonstrates a moderate Windows bias. PowerShell is featured heavily and almost always shown first, with Windows-centric examples and tools (e.g., use of c:\ paths, WindowsServer OS, ConvertTo-SecureString). While Azure CLI examples are provided and Ubuntu templates are referenced, Linux/macOS users may encounter friction due to Windows-first ordering, Windows-only tooling, and lack of explicit Linux/macOS shell examples (e.g., bash, file paths, certificate handling).
Recommendations
  • Alternate example ordering so Linux/Ubuntu is shown first in some sections.
  • Provide explicit bash examples for Linux/macOS users, including file path conventions (e.g., /home/user/certificates).
  • Clarify that PowerShell examples are for Windows, and provide equivalent bash commands for Linux/macOS.
  • Note any OS-specific requirements or differences (e.g., certificate formats, file permissions).
  • Ensure all referenced templates and commands work equally on Linux/macOS, and document any caveats.
  • Use neutral language and tooling where possible (e.g., avoid Windows-only features like ConvertTo-SecureString).
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 exhibits a moderate Windows bias. Windows-centric concepts such as RDP port management and admin username/password changes are highlighted in the 'Next steps' section, with links to PowerShell scripts and RDP-specific instructions. The example configuration uses a Windows-style data path (D:\\SvcFab) and certificate store references, and does not provide Linux-specific paths or guidance. Linux equivalents for remote connection, user management, or file paths are missing or not mentioned.
Recommendations
  • Add Linux/macOS-specific examples for remote connection (e.g., SSH instructions) and user management.
  • Provide Linux-style file paths (e.g., /var/svcfab) in configuration examples alongside Windows paths.
  • Include references to Linux tools and commands where Windows/PowerShell tools are mentioned.
  • Ensure that guidance for changing admin credentials and port ranges covers both Windows (RDP) and Linux (SSH) scenarios.
  • Reorder examples so that Windows and Linux are presented with equal prominence, or alternate which comes first.
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 demonstrates a Windows bias by presenting Windows (RDP) connection details and screenshots first, using Windows terminology and tools (Remote Desktop Connection), and referencing PowerShell scripts for post-connection tasks. Linux connection (SSH) is mentioned, but only briefly and after the Windows example, with no screenshots or detailed instructions.
Recommendations
  • Present Linux (SSH) connection instructions and screenshots alongside or before Windows examples to ensure parity.
  • Include references to Linux command-line tools and scripts for post-connection tasks, not just PowerShell.
  • Provide equivalent step-by-step instructions for Linux/macOS users, including troubleshooting tips and credential management.
  • Link to Linux-specific documentation for managing cluster nodes and updating SSH settings.
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
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a notable Windows bias. PowerShell cmdlets are referenced as the only scripting alternative to the .NET SDK, with no mention of Linux/macOS equivalents (such as Bash, Azure CLI, or REST API usage). All code examples are in C#/.NET, which is most commonly used on Windows. Windows tools and patterns (PowerShell, .NET libraries) are mentioned exclusively and before any cross-platform alternatives. There are no Linux/macOS-specific instructions or examples, and the documentation does not clarify cross-platform compatibility for the SDK or scripting approaches.
Recommendations
  • Add Azure CLI and Bash examples for scaling operations, showing how to query and update VMSS capacity from Linux/macOS.
  • Mention REST API options for programmatic scaling, which are platform-agnostic.
  • Clarify whether the .NET Fluent SDK and FabricClient can be used on Linux/macOS (e.g., via .NET Core), and provide guidance if so.
  • Include a section comparing scripting options across platforms (PowerShell, Azure CLI, Bash, REST API).
  • Ensure that references to PowerShell are accompanied by equivalent Azure CLI commands, especially for credential management and scaling.
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 consistently provides PowerShell command examples for configuring Service Fabric placement policies, with no equivalent examples for Linux/macOS users (e.g., Bash, CLI, or REST API). PowerShell is a Windows-centric tool, and its exclusive use in examples creates friction for users on non-Windows platforms. Additionally, the documentation does not mention or prioritize Linux-native tools or workflows, and Windows/PowerShell examples are presented first and exclusively.
Recommendations
  • Add Azure CLI examples for each placement policy configuration, as Azure CLI is cross-platform and commonly used on Linux/macOS.
  • Include REST API or ARM template snippets where applicable, which are platform-agnostic.
  • Explicitly mention Linux/macOS support for Service Fabric and provide guidance or links for non-Windows users.
  • If PowerShell is required, clarify whether PowerShell Core (cross-platform) is supported and provide installation instructions for Linux/macOS.
  • Reorder examples so that platform-agnostic methods (CLI, REST) are shown before or alongside PowerShell.
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 consistently provides PowerShell examples for all operations related to Application Groups, with no mention of Linux/macOS command-line equivalents (such as Azure CLI, Bash, or REST API). PowerShell is a Windows-centric tool, and its use is presented first and exclusively in all code snippets, followed by C# SDK examples. There is no guidance for users on Linux or macOS platforms regarding how to perform these tasks, nor any mention of cross-platform alternatives.
Recommendations
  • Add Azure CLI examples for all operations (creating, updating, querying, and removing Application Groups/Capacity).
  • Include REST API sample calls for relevant operations, as these are platform-agnostic.
  • Explicitly state PowerShell's cross-platform availability if relevant, or clarify any limitations.
  • Provide Bash or shell script examples where possible.
  • Reorder examples so that platform-agnostic methods (CLI, REST) are presented before or alongside PowerShell.
  • Add a note or section addressing Linux/macOS users and how they can perform these tasks.
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 health reports using PowerShell (Get-ServiceFabricPartitionHealth), which is a Windows-centric tool. There are no equivalent examples or instructions for Linux or macOS users, such as using Service Fabric CLI (sfctl) or REST APIs. The only command-line example is Windows PowerShell, and the documentation does not mention Linux management tools or provide parity in operational guidance.
Recommendations
  • Include equivalent Linux/macOS examples using sfctl or REST API for querying partition health.
  • Explicitly mention cross-platform management options and tools where PowerShell is referenced.
  • Add notes or sections clarifying how Linux users can perform the same tasks, with sample commands.
  • Ensure that all operational examples are provided for both Windows and Linux environments.
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 exhibits a Windows bias by providing PowerShell examples exclusively for command-line operations, with no equivalent Linux or cross-platform CLI examples (such as Azure CLI or Bash). Windows/PowerShell commands are presented as the only way to create and manage Service Fabric services via the command line, and these examples appear before any mention of alternatives. There is no guidance for Linux users on how to perform these tasks, nor are Linux tools or patterns referenced.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and works on Linux, macOS, and Windows.
  • Include Bash script examples or instructions for Linux environments where applicable.
  • Explicitly mention Linux/macOS support and provide links or references to Service Fabric documentation for those platforms.
  • Clarify which tools and APIs are available on Linux clusters, and provide guidance for users operating outside Windows.
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 extensive PowerShell examples for managing dynamic node tags and service requirements in Azure Service Fabric, but omits equivalent Linux/macOS command-line examples (e.g., Bash, CLI). PowerShell is a Windows-centric tool, and its prominence, along with the lack of Linux-native instructions, creates friction for non-Windows users. Windows tools and patterns are mentioned exclusively for command-line operations.
Recommendations
  • Add Azure CLI or Bash examples for all PowerShell commands, demonstrating how to add/remove node tags and set service tag requirements from Linux/macOS.
  • Explicitly mention cross-platform alternatives to PowerShell, such as REST API usage via curl or Azure CLI.
  • Reorder examples so that cross-platform or Linux-native methods are presented before or alongside Windows/PowerShell examples.
  • Clarify which tools are available on Linux/macOS and provide installation or usage guidance.
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: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides only a Windows PowerShell script for rolling over a Service Fabric cluster certificate, with file paths and commands tailored to Windows environments. There are no equivalent examples or instructions for Linux or macOS users, nor are cross-platform Azure CLI alternatives mentioned. This creates friction for users on non-Windows platforms.
Recommendations
  • Provide equivalent Azure CLI examples for certificate rollover steps, which work on Linux/macOS as well as Windows.
  • Include Linux/macOS-specific instructions for file paths and certificate handling.
  • Explicitly state cross-platform options and clarify which steps are OS-agnostic.
  • Add a note or section on how to perform these tasks from Linux/macOS terminals.
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: 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 used extensively for examples and instructions, with Windows-specific cmdlets (e.g., Get-AzVmss, Remove-ServiceFabricNodeState) featured prominently and often before CLI or cross-platform alternatives. While Azure CLI and sfctl (cross-platform tools) are included, PowerShell examples are more detailed and appear first in several sections. There are no explicit Linux shell (bash) or macOS-specific examples, and no mention of Linux-specific considerations or troubleshooting. The documentation assumes familiarity with Windows tools and patterns, which may create friction for Linux/macOS users.
Recommendations
  • Provide bash shell equivalents for all PowerShell examples, especially for tasks like listing nodes, scaling sets, and removing node state.
  • Ensure Azure CLI and sfctl examples are as detailed and comprehensive as PowerShell ones, including error handling and step-by-step logic.
  • Explicitly mention that all Azure CLI and sfctl commands work on Linux/macOS, and clarify any OS-specific differences or limitations.
  • Reorder examples so that cross-platform tools (Azure CLI, sfctl) appear before or alongside PowerShell, not after.
  • Add troubleshooting notes or tips for Linux/macOS environments, such as common permission issues or environment setup steps.
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 management steps reference Windows certificate stores (e.g., Cert:\CurrentUser\TrustedPeople), and instructions for importing certificates are provided only for Windows environments. There are no Linux/macOS-specific instructions or examples for certificate handling, deployment, or cluster connection. The documentation assumes familiarity with Windows tooling and does not offer parity for users on Linux or macOS.
Recommendations
  • Add equivalent Azure CLI and Bash examples for template deployment and certificate management.
  • Include instructions for importing certificates on Linux/macOS (e.g., using openssl, update-ca-certificates, or keytool).
  • Document how to connect to Service Fabric clusters from Linux/macOS, including certificate usage.
  • Reference cross-platform tools and avoid assuming the use of Windows certificate stores.
  • Present examples for both Windows and Linux/macOS, or explicitly state platform requirements.
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 detailed PowerShell examples for configuring service sensitivity and maximum load, but does not offer equivalent command-line instructions for Linux/macOS users (e.g., Bash, CLI, or REST API). PowerShell is a Windows-centric tool, and its exclusive use in examples creates friction for users on other platforms. The ordering also places PowerShell before C# API, reinforcing Windows-first patterns.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • Include REST API examples for service sensitivity and maximum load configuration.
  • Explicitly mention platform compatibility for each method (PowerShell, CLI, C# API).
  • Reorder examples so that platform-neutral or cross-platform methods (CLI, REST) appear before Windows-specific ones.
  • Add notes or links for Linux/macOS users on how to perform these operations without PowerShell.
GitHub Create Pull Request
Service Fabric Azure Service Fabric standalone cluster scaling ...ce-fabric/service-fabric-cluster-scaling-standalone.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 on scaling Azure Service Fabric standalone clusters demonstrates a notable Windows bias. It references PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) as the primary tooling for cluster management, without mentioning Linux equivalents or cross-platform alternatives. The linked 'scale a standalone cluster' guide is explicitly for Windows Server, and there are no examples or instructions for Linux-based clusters or tools. This creates friction for users managing Service Fabric clusters on Linux or non-Windows environments.
Recommendations
  • Include examples and instructions for scaling standalone clusters on Linux, using Bash, CLI, or REST APIs.
  • Reference cross-platform tools (such as Azure CLI or Service Fabric REST APIs) alongside PowerShell cmdlets.
  • Provide parity in documentation links, ensuring Linux-specific guides are available and visible.
  • Clearly indicate which steps or tools are Windows-specific and offer alternatives for Linux/macOS users.
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 page exhibits a moderate Windows bias. Standalone cluster scenarios are described only for Windows Server, with explicit references to Windows authentication (Kerberos), Windows security, and Windows certificate services. Instructions and links for securing clusters on-premises are exclusively for Windows, with no mention of Linux equivalents or guidance for Linux-based standalone clusters. Windows tools (e.g., MakeCert.exe) are referenced for certificate creation, and Windows terminology (Active Directory, group Managed Service Accounts) is used without Linux alternatives. While Azure-based clusters are described in a platform-neutral way, standalone cluster security is presented as Windows-only.
Recommendations
  • Add explicit guidance and examples for securing standalone Service Fabric clusters running on Linux, including certificate management and authentication options.
  • Reference Linux-compatible certificate creation tools (e.g., OpenSSL) alongside or instead of Windows tools like MakeCert.exe.
  • Clarify whether standalone Linux clusters are supported and, if so, provide links and instructions for their security configuration.
  • Include Linux-specific terminology and patterns (e.g., PAM, system users, Linux file permissions) where relevant.
  • Ensure that examples and instructions are presented in a platform-neutral order, or provide parallel sections for Windows and Linux.
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 for upgrading Linux OS in Azure Service Fabric is heavily focused on PowerShell and Az PowerShell cmdlets for cluster management tasks. Most step-by-step instructions and code samples use PowerShell, with only a single section (node disablement for Bronze durability) providing Linux-native (bash/ssh) commands. Windows-centric tools and patterns (PowerShell, Az PowerShell, Service Fabric Explorer) are mentioned first and/or exclusively in critical steps, with minimal guidance for Linux-native alternatives.
Recommendations
  • Provide equivalent CLI (az CLI) and REST API examples for all management tasks currently shown only in PowerShell.
  • Include bash scripts or Linux-native command sequences for cluster and node type management, not just for node disablement.
  • Mention Linux tools (e.g., az CLI, sfctl) before or alongside PowerShell in all relevant steps.
  • Clarify which steps can be performed entirely from Linux/macOS and provide explicit instructions for those environments.
  • Add troubleshooting guidance using Linux-native tools (e.g., sfctl, az CLI, SSH) instead of or in addition to Service Fabric Explorer.
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 exhibits several signs of Windows bias. Windows-specific tools and patterns (such as PowerShell and Visual Studio) are mentioned exclusively or before Linux equivalents. Examples for tasks like authenticating to Key Vault reference PowerShell scripts and Windows MSI hosts, with no Linux alternatives provided. Antivirus exclusions list only Windows-style paths and processes. The development experience is described in terms of Visual Studio and Windows node configurations, with no mention of Linux/macOS workflows or tools. Linux-specific instructions, examples, or parity are generally missing throughout the page.
Recommendations
  • Provide Linux/macOS equivalents for PowerShell and MSI-based authentication workflows, such as Bash scripts or Azure CLI examples.
  • Include Linux-specific antivirus exclusion paths and processes, or clarify cross-platform requirements.
  • Mention Linux/macOS development workflows and tools (e.g., VS Code, CLI) alongside Visual Studio.
  • Ensure examples and instructions for cluster management, upgrades, and patching are available for both Windows and Linux environments.
  • Where Windows tools or patterns are referenced, add Linux/macOS alternatives or note platform differences.
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 ⚠ī¸ minor_windows_path_examples
Summary
The documentation demonstrates a moderate Windows bias. Windows prerequisites are listed first and in more detail, PowerShell is the primary scripting tool for both Windows and Linux deployments (even for Linux clusters), and Windows paths and application manifest examples dominate. Linux equivalents (sfctl, bash) are present but often secondary, and Linux-specific patterns or troubleshooting are not covered in depth.
Recommendations
  • Present Linux and Windows instructions in parallel, giving equal prominence to both.
  • Provide bash scripts or native Linux command examples for Linux clusters, rather than relying on PowerShell for Linux deployments.
  • Include Linux-specific troubleshooting notes and configuration details, especially for application manifests and volume mappings.
  • Use platform-agnostic paths and examples in documentation snippets, or provide both Windows and Linux variants.
  • Clarify when instructions apply to Linux, Windows, or both, and avoid assuming PowerShell is available 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 demonstrates a notable Windows bias. It uses Visual Studio for packaging applications, provides only PowerShell examples for deployment and deletion, and omits Linux/macOS equivalents (such as Azure CLI or cross-platform packaging methods). Windows tools and workflows are referenced exclusively, making it harder for Linux/macOS users to follow the instructions without additional research.
Recommendations
  • Add Azure CLI examples for deployment and deletion alongside PowerShell commands.
  • Include instructions for packaging Service Fabric applications without Visual Studio (e.g., using dotnet CLI or other cross-platform tools).
  • Mention and demonstrate Linux/macOS-compatible workflows for zipping and renaming files.
  • Clearly state which steps are platform-specific and provide alternatives where possible.
  • Reorder examples so that cross-platform methods (Azure CLI, REST API) are shown before or alongside Windows-specific tools.
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. Code examples for scaling Service Fabric services are provided in C# and PowerShell only, with no equivalent Linux shell (bash/CLI) examples. References to administrative actions and tooling (e.g., New-ServiceFabricService) are PowerShell-centric, which is native to Windows. There is no mention of Linux command-line tools or scripts, nor are Linux-specific workflows or examples presented. Additionally, Windows tooling is mentioned first and exclusively in several sections, and Linux parity is only briefly discussed in the context of platform differences, not in practical usage or examples.
Recommendations
  • Add equivalent Linux CLI (bash/az CLI) examples alongside PowerShell for all code snippets.
  • Explicitly mention Linux tooling and workflows where administrative actions are described.
  • Where PowerShell cmdlets are referenced, provide links or examples for Linux users (e.g., az servicefabric CLI commands).
  • Ensure that Linux examples are presented with equal prominence and detail as Windows/PowerShell examples.
  • Clarify any platform-specific limitations or differences in the context of scaling operations, not just in logging.
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 page demonstrates a notable Windows bias: PowerShell is the only shell shown for command-line examples outside of sfctl, and Windows certificate management tools and patterns (e.g., certificate stores, Import-PfxCertificate) are described in detail, while Linux equivalents are missing. Windows instructions and tools are presented first and in greater detail than those for Mac or Linux. Linux users are left to infer steps for certificate installation and management, and there are no Linux-specific CLI or API examples for connecting to clusters.
Recommendations
  • Add explicit Linux instructions for installing client certificates (e.g., using openssl, certutil, or browser settings for certificate import).
  • Provide Linux/macOS equivalents for PowerShell commands, such as using OpenSSL, keytool, or other native tools.
  • Include Linux/macOS examples for connecting to clusters using the Service Fabric CLI and APIs, especially for certificate management and authentication.
  • Balance the order and detail of Windows and Linux/macOS instructions to ensure parity and reduce friction for non-Windows users.
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 provides detailed examples for running Chaos in Service Fabric using C# and PowerShell, both of which are Windows-centric. PowerShell is a Windows-native tool, and no Linux/macOS command-line examples (e.g., Bash, Azure CLI, or cross-platform REST usage) are provided. Windows tools and patterns (PowerShell cmdlets, .NET types) are mentioned exclusively and before any Linux equivalents, which are absent. This creates friction for Linux/macOS users who cannot use PowerShell and may not be familiar with .NET APIs.
Recommendations
  • Add Linux/macOS-friendly examples using Bash and curl to demonstrate REST API usage for Chaos operations.
  • Include Azure CLI examples if available for Service Fabric Chaos management.
  • Explicitly mention cross-platform options and clarify which tools/APIs work on Linux/macOS.
  • Reorder examples so REST API or cross-platform methods are shown first, followed by platform-specific (Windows/PowerShell) examples.
  • Provide guidance on installing and using Service Fabric SDK/tools on Linux/macOS.
GitHub Create Pull Request
Service Fabric Create a cluster using certificate common name ...-fabric/service-fabric-create-cluster-using-cert-cn.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 exclusively provides PowerShell-based instructions and examples for certificate management, key vault operations, and deployment, all using Windows file paths and tools. There are no CLI, Bash, or Linux/macOS-specific examples or guidance. The template references and deployment steps assume a Windows environment, creating friction for Linux/macOS users.
Recommendations
  • Add equivalent Azure CLI (az) commands for certificate upload, resource group creation, and template deployment.
  • Provide Bash shell examples for Linux/macOS users, including file path conventions.
  • Explicitly mention cross-platform support and note any differences or limitations for Linux/macOS users.
  • Include a section or links for Linux/macOS certificate generation and handling.
  • Ensure template instructions do not assume Windows-only paths or tools.
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 demonstrates a notable Windows bias, especially in migration and operational steps. All command-line examples use PowerShell cmdlets, with no Bash, Azure CLI, or Linux-native instructions. The sample templates referenced are Windows-first, and Windows-centric tools (PowerShell, Windows file paths) are used exclusively. Linux equivalents are missing, and the only explicit Linux reference is a template link, not a walkthrough.
Recommendations
  • Provide Azure CLI and Bash examples alongside PowerShell for all deployment, migration, and operational steps.
  • Include Linux/macOS-specific instructions for connecting to clusters, managing nodes, and updating resources.
  • Reference and walk through Linux-based sample templates with equal prominence as Windows ones.
  • Avoid Windows-specific file paths (e.g., D:\SvcFab) in generic configuration examples, or provide Linux equivalents.
  • Clearly indicate which steps or scripts are OS-specific, and provide alternatives where needed.
GitHub Create Pull Request
Service Fabric Overview of Azure and standalone Service Fabric clusters ...icles/service-fabric/service-fabric-deploy-anywhere.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation mentions both Windows Server and Linux as supported platforms for Service Fabric clusters, but it highlights that standalone clusters are not available on Linux. There are no Linux-specific examples, tools, or operational patterns discussed, and the limitations for Linux are referenced only via a link. Windows is mentioned first and appears to be the primary focus for standalone clusters.
Recommendations
  • Explicitly state the limitations for Linux standalone clusters in the main text, not just via a link.
  • Provide examples or guidance for Linux users regarding Service Fabric cluster deployment and management on Azure.
  • Include a comparison table or section summarizing feature parity and gaps between Windows and Linux clusters.
  • If possible, offer alternative solutions or workarounds for Linux users who require standalone clusters.
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 exhibits a notable Windows bias. It references Visual Studio and PowerShell as the primary tools for packaging and deploying Service Fabric applications, with file paths and workflows specific to Windows environments. All example paths use Windows conventions (e.g., C:\Users\...), and troubleshooting steps rely on PowerShell cmdlets and Windows SDK modules. There are no Linux/macOS equivalents or cross-platform CLI examples for key steps such as package verification, upload, or troubleshooting. The documentation does not mention how to perform these tasks on Linux/macOS, nor does it provide guidance for non-Windows environments.
Recommendations
  • Add explicit instructions and examples for Linux/macOS users, including file path conventions and alternative tools.
  • Provide Service Fabric CLI (sfctl) examples for all major steps (upload, register, remove, troubleshoot) alongside or before PowerShell examples.
  • Clarify how to verify and compress application packages using cross-platform tools (e.g., zip, tar, sfctl).
  • Include troubleshooting steps using CLI or REST API methods that work on Linux/macOS.
  • Avoid assuming Visual Studio or PowerShell as the default workflow; mention cross-platform development environments.
  • Use generic or platform-neutral file paths in code samples where possible.
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 exhibits a moderate Windows bias. Windows-specific tools and patterns (such as PowerShell cmdlets and Visual Studio) are mentioned before or more prominently than their Linux equivalents. Examples and instructions for cluster creation and management often default to Windows, with Linux support described as secondary or unavailable (e.g., standalone clusters). Windows services and executables are referenced without Linux equivalents or explanations. Linux support is acknowledged but not given equal example coverage.
Recommendations
  • Provide Linux-specific examples and instructions alongside Windows ones, especially for cluster creation, management, and lifecycle operations.
  • Mention Linux CLI tools (e.g., sfctl) and scripting options before or alongside PowerShell, not after.
  • Include references to Linux service management (systemd, etc.) and equivalents for Windows services like FabricHost.exe.
  • Clarify feature parity and limitations for Linux up front, and link to Linux-specific guides where relevant.
  • Add sample workflows for Linux users, including container orchestration and application deployment.
  • Avoid listing Windows tools (PowerShell, Visual Studio) first; present both platforms equally.
GitHub Create Pull Request
Service Fabric Event Aggregation with Microsoft Azure Diagnostics ...ic/service-fabric-diagnostics-event-aggregation-wad.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a notable Windows bias. Windows-specific tools (WAD, PowerShell, Visual Studio) are referenced throughout, with configuration examples and instructions focused almost exclusively on Windows clusters. The main body, code snippets, and step-by-step guides all assume use of Windows diagnostics (WAD) and ETW, with no Linux-specific configuration or troubleshooting guidance. While a Linux selector is present at the top, the actual content and examples are Windows-centric, and Linux equivalents (such as LAD, Bash, or Linux logging patterns) are missing or relegated to a separate page.
Recommendations
  • Integrate Linux (LAD) examples and configuration steps directly into the main documentation, not just as a separate page.
  • Provide equivalent Bash/CLI commands for cluster deployment and diagnostics extension management, alongside PowerShell.
  • Include Linux logging and event collection patterns, such as syslog, journald, or LAD configuration, with sample templates.
  • Reference Linux troubleshooting and monitoring tools (e.g., journalctl, logrotate) where Visual Studio or ETW is mentioned for Windows.
  • Ensure parity in guidance for Application Insights and Azure Monitor integration for both Windows and Linux clusters.
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 (Service Fabric Analytics, WAD, PowerShell) are mentioned first and in detail, with step-by-step instructions and code samples. Linux clusters are referenced only in notes or as links to separate articles, with no direct examples or walkthroughs. All command-line examples use PowerShell, and Windows-specific tooling (WAD, Service Fabric Analytics) is emphasized, while Linux equivalents (OMS Syslog, Linux agent setup) are not described or shown.
Recommendations
  • Provide parallel Linux examples and walkthroughs directly in this page, not just as external links.
  • Include command-line instructions using Bash/CLI for Linux users, alongside PowerShell.
  • Clarify which steps are Windows-only and offer Linux alternatives where possible.
  • Describe Linux-specific tools and patterns (e.g., OMS Syslog, Linux diagnostics agent) with equal detail.
  • Ensure sample templates and code snippets are available for both Windows and Linux clusters.
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 page demonstrates a mild Windows bias, primarily by listing Windows performance counters and examples first, referencing Windows-specific counter formats, and providing more detailed examples for Windows than Linux. Linux is mentioned as an alternative in some places, but Linux-specific examples, counter formats, and troubleshooting steps are not provided. The documentation assumes familiarity with Windows tools and patterns, which may create friction for Linux/macOS users.
Recommendations
  • Provide Linux-specific examples for performance counters, including typical Linux counter names and formats.
  • Include screenshots or walkthroughs from Linux environments (e.g., Azure portal views for Linux clusters).
  • Clarify any differences in setup or troubleshooting steps for Linux clusters, especially where agent configuration or counter collection differs.
  • List Linux options and examples before or alongside Windows ones, rather than after.
  • Explicitly mention macOS where relevant, or clarify if steps apply equally to macOS.
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 demonstrates a Windows bias by exclusively referencing Visual Studio and its Solution Explorer for NuGet package management, and by instructing users to observe the Debug output window in Visual Studio for verification. There are no instructions or examples for Linux/macOS users, such as using the dotnet CLI for package management or alternative methods for log verification. The documentation assumes a Windows development environment and omits guidance for cross-platform scenarios.
Recommendations
  • Add instructions for installing EventFlow NuGet packages using the dotnet CLI (e.g., 'dotnet add package') for Linux/macOS users.
  • Include guidance on editing and placing configuration files using cross-platform tools and editors.
  • Provide verification steps that do not rely on Visual Studio, such as using command-line tools or viewing logs in the terminal.
  • Explicitly mention that Service Fabric development can be performed on Linux/macOS and link to relevant cross-platform setup guides.
  • Present examples and instructions for both Windows and Linux/macOS environments, or clearly indicate when steps are Windows-specific.
GitHub Create Pull Request
Service Fabric Performance monitoring with Azure Diagnostics .../service-fabric/service-fabric-diagnostics-perf-wad.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 is heavily focused on Windows clusters, specifically using the Windows Azure Diagnostics (WAD) extension and ARM templates with Windows performance counters. Linux clusters are mentioned only briefly, with a link to a separate page for Log Analytics agent setup, and no Linux-specific configuration or counter examples are provided. All code samples and deployment instructions (e.g., PowerShell commands) are Windows-centric, with no equivalent Linux or cross-platform guidance.
Recommendations
  • Add parallel Linux-specific examples for performance counter collection, including sample configuration for the Log Analytics agent.
  • Include Linux performance counter specifiers and typical metrics relevant to Service Fabric on Linux.
  • Provide deployment instructions using Azure CLI or other cross-platform tools, not just PowerShell.
  • Clearly separate Windows and Linux workflows, or provide a unified table comparing both approaches.
  • Reference Linux documentation and tools earlier and more prominently, not just as a side note.
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: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page demonstrates moderate Windows bias. It references Windows-specific tools and APIs (such as Repair-ServiceFabricPartition PowerShell cmdlet and .NET APIs), links to Windows Server setup for standalone clusters, and omits explicit Linux or cross-platform command-line examples. Windows terminology and tools are mentioned before or instead of Linux equivalents, and there is no guidance for Linux users on how to perform equivalent operations (e.g., troubleshooting, cluster creation, recovery).
Recommendations
  • Add Linux-specific examples and instructions for key operations, such as partition repair, cluster creation, and troubleshooting.
  • Reference cross-platform Service Fabric tools (e.g., Service Fabric CLI) and provide parity in examples for both Windows and Linux environments.
  • Clarify which APIs and commands are available on Linux and macOS, and provide alternatives where necessary.
  • Include links to Linux cluster setup documentation alongside Windows Server references.
  • Explicitly mention support and limitations for Linux-based Service Fabric clusters in relevant sections.
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 PowerShell-based deployment instructions first and in greater detail, with multiple example commands for creating, managing, upgrading, and rolling back Docker Compose deployments on Azure Service Fabric. PowerShell is a Windows-centric tool, and its prominence suggests a Windows-first approach. While the Service Fabric CLI (sfctl), which is cross-platform, is mentioned as an alternative, it is introduced only after the PowerShell section. There are no explicit Linux/macOS shell examples (e.g., Bash), nor is there guidance for Linux-specific scenarios or troubleshooting. The mention of 'Isolation (only for Windows)' in supported Compose directives further highlights Windows-specific features.
Recommendations
  • Present CLI (sfctl) instructions before or alongside PowerShell examples to emphasize cross-platform support.
  • Include explicit Linux/macOS shell examples and troubleshooting notes for non-Windows environments.
  • Clarify which tools are supported on which platforms, and provide installation/setup guidance for Linux/macOS users.
  • Highlight any platform-specific limitations or differences (e.g., 'Isolation' only for Windows) in a dedicated section.
  • Ensure parity in example depth and coverage for both PowerShell and CLI instructions.
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 exhibits a moderate Windows bias. Windows support is broader and described first, with Linux limitations emphasized. PowerShell is the only CLI example for setting DNS names, with no Linux CLI (e.g., Bash, Azure CLI) alternatives. Visual Studio is mentioned for editing manifests, a Windows-centric tool. Enabling DNS service via Azure portal is only available for Windows clusters, with Linux users required to use ARM templates, but no Linux-specific guidance or examples are provided.
Recommendations
  • Add Linux-specific instructions and examples for enabling DNS service, including ARM template steps tailored for Linux clusters.
  • Provide CLI examples for Linux users, such as Azure CLI, Bash, or REST API commands, for setting DNS names and managing services.
  • Mention cross-platform editors (e.g., VS Code) alongside Visual Studio for editing manifests.
  • Clarify any differences in service deployment and management for Linux clusters, and provide troubleshooting steps for common Linux issues.
  • Ensure examples and screenshots are relevant to both Windows and Linux environments, or clearly label them as platform-specific.
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: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page for enabling disk encryption for Linux clusters in Azure Service Fabric exhibits several Windows-centric biases. PowerShell commands are presented first and in greater detail, with explicit references to Windows file paths (e.g., 'c:\certificates'), and the use of PowerShell-specific cmdlets throughout. Azure CLI examples are provided, but often as secondary or 'equivalent' commands, and they also use Windows-style paths. There is minimal coverage of Linux-native tooling or shell scripting, and no examples using bash or Linux file system conventions. The documentation assumes familiarity with PowerShell and Windows patterns, which may create friction for Linux/macOS users.
Recommendations
  • Provide Linux-first examples, using bash shell and Linux file paths (e.g., '/home/user/certificates') in CLI commands.
  • Include step-by-step instructions for Linux environments, such as certificate generation using OpenSSL and file management in Linux.
  • Avoid presenting PowerShell commands before CLI or bash examples; alternate or parallelize examples for both platforms.
  • Clarify which commands are platform-agnostic (Azure CLI) and which are Windows-specific (PowerShell), and recommend CLI for cross-platform use.
  • Add notes or sections for Linux/macOS users highlighting any differences or additional steps required.
  • Remove or supplement Windows-specific references (e.g., 'c:\templates') with Linux equivalents.
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_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing Windows file paths (e.g., C:\Program Files\...), mentioning Visual Studio as a primary tool, and omitting explicit Linux/macOS equivalents or examples. There are no instructions or examples for packaging or deploying guest executables from Linux/macOS environments, nor are alternative tools or directory paths mentioned for non-Windows platforms.
Recommendations
  • Add explicit instructions and examples for Linux/macOS users, including command-line utilities and directory paths.
  • Mention cross-platform tools (such as Azure CLI, Service Fabric CLI) and provide parity in examples for both Windows and Linux/macOS.
  • Reference the location of schema files or SDK installation paths for Linux/macOS, not just Windows.
  • Include sample workflows for packaging and deploying guest executables using Linux/macOS environments.
  • Clarify whether Visual Studio is required or if alternatives exist for non-Windows platforms.
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 ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides a detailed conceptual overview of Service Fabric health monitoring, but the only concrete example of interacting with the health system uses PowerShell cmdlets, which are Windows-centric. There are no equivalent examples for Linux/macOS users (e.g., using REST API, CLI, or SDKs), and PowerShell is presented as the default/primary method for reporting and querying health. This creates friction for users running Service Fabric clusters on Linux or managing them from non-Windows environments.
Recommendations
  • Add equivalent examples using cross-platform tools, such as Azure CLI, REST API, or SDKs (e.g., Python, .NET Core) for reporting and querying health.
  • Explicitly mention Linux/macOS support and provide guidance for those platforms where relevant.
  • Reorder or supplement examples so that Windows/PowerShell is not presented as the only or primary method.
  • Link to documentation or guides for Linux-based Service Fabric cluster management.
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_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by providing PowerShell as the only command-line example for service creation and management, referencing Windows-centric tools and cmdlets throughout. There is no mention of Linux equivalents (such as Azure CLI, Bash, or cross-platform tools), and PowerShell is presented as the primary or sole method for operational tasks. This may create friction for Linux/macOS users who do not use PowerShell or Windows tools.
Recommendations
  • Add equivalent Linux/macOS command-line examples using Azure CLI, Bash, or REST API calls.
  • Explicitly mention cross-platform management options and tools, and provide links to relevant documentation.
  • Clarify which tools are available on which platforms, and avoid presenting Windows/PowerShell as the default or only option.
  • Where PowerShell is referenced, also show how to perform the same operation using REST API, Azure CLI, or SDKs 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 demonstrates a moderate Windows bias. It references PowerShell and Visual Studio as primary tools for interacting with Service Fabric clusters, both of which are traditionally Windows-centric. The 'Next steps' section links only to PowerShell-based deployment instructions, and there are no explicit examples or guidance for Linux or macOS users (e.g., using Bash, CLI, or cross-platform tools). The documentation mentions .NET and REST APIs as alternatives for retrieving cluster manifests, but these are listed after PowerShell and without concrete Linux/macOS usage examples.
Recommendations
  • Add explicit examples for Linux/macOS users, such as using Azure CLI or Bash scripts to interact with Service Fabric clusters.
  • Include links to cross-platform deployment guides alongside PowerShell instructions in the 'Next steps' section.
  • Mention and demonstrate how to retrieve and configure the ImageStoreConnectionString using tools available on Linux/macOS.
  • Clarify whether Visual Studio is required or if alternatives (e.g., VS Code, command-line tools) are supported for non-Windows environments.
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: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples and tools (New-ServiceFabricApplication, Deploy-FabricApplication.ps1) are mentioned first and in more detail, with Visual Studio workflows highlighted. Linux alternatives (sfctl, install.sh) are referenced but receive less explanation and are not shown first. There is a heavier emphasis on Windows-centric tools and patterns, which may create friction for Linux/macOS users.
Recommendations
  • Present Linux/macOS tools (sfctl, install.sh) before or alongside Windows/PowerShell examples.
  • Provide equivalent step-by-step examples for Linux/macOS users, including shell commands and scripts.
  • Expand on Linux/macOS workflows, such as using sfctl and shell scripts, with clear instructions and parity with Windows examples.
  • Mention cross-platform editors and deployment tools, not just Visual Studio.
  • Clarify which steps or tools are platform-specific and offer alternatives where needed.
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 its examples, using Windows-specific paths (e.g., 'c:\VolumeTest\Data'), and mentioning Windows tools (e.g., 'winver' command) for OS build detection. The certificate import section describes Windows behavior first and in more detail, while Linux is mentioned only as an aside. There are no explicit Linux container manifest examples, nor are Linux-specific patterns or tools discussed. The examples and explanations are tailored to Windows environments, with Linux support implied but not demonstrated.
Recommendations
  • Include explicit Linux-based container manifest examples, such as referencing Ubuntu or other Linux container samples.
  • Provide Linux-specific instructions for tasks like OS build detection (e.g., using 'uname -a' or '/etc/os-release').
  • Show Linux file system paths (e.g., '/mnt/VolumeTest/Data') in volume binding examples.
  • Describe certificate handling in Linux with equal detail, including how PEM files are managed and accessed.
  • Balance explanations so that Linux and Windows behaviors are presented side-by-side, rather than Windows-first.
  • Reference Linux container images and registry authentication patterns where applicable.
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 command-line usage. All sample code is in C#, which is cross-platform, but there are no bash, CLI, or Linux-native instructions. Windows/PowerShell tools are mentioned first and exclusively, with no Linux equivalents or parity.
Recommendations
  • Add equivalent examples using Azure CLI or bash scripts for Linux/macOS users.
  • Reference Linux-compatible Service Fabric tools (e.g., sfctl) where PowerShell cmdlets are mentioned.
  • Explicitly state cross-platform support and provide guidance for Linux/macOS environments.
  • Reorder documentation to present cross-platform or Linux examples alongside or before Windows/PowerShell examples.
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 demonstrates a notable Windows bias: all directory listing examples use Windows 'tree' command syntax, all command-line packaging and validation examples use PowerShell and Windows paths, and only Windows tools (Visual Studio, msbuild.exe, PowerShell cmdlets) are mentioned. There are no Linux/macOS equivalents, nor are cross-platform alternatives or instructions provided. This creates friction for non-Windows users attempting to package and validate Service Fabric applications.
Recommendations
  • Add Linux/macOS equivalents for directory listing (e.g., 'ls -R' or 'tree' on Linux).
  • Provide examples using Bash or cross-platform .NET CLI tools where possible.
  • Document how to package and validate Service Fabric applications on Linux/macOS, including any required tools or scripts.
  • Clarify which steps are Windows-only and suggest alternatives or workarounds for Linux/macOS.
  • Mention cross-platform editors (e.g., VS Code) and build tools (e.g., dotnet CLI) where applicable.
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 ⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page demonstrates a Windows bias in several ways: it references Windows-specific tools and concepts (such as ServiceFabric PowerShell module, .bat scripts, EXE files, and Windows account types like NetworkService and Administrators), and examples are tailored to Windows environments (e.g., Setup.bat, VotingWeb.exe). There is no mention of Linux equivalents, nor are Linux/macOS-specific patterns or examples provided. The documentation assumes familiarity with Windows conventions and omits guidance for Linux deployments.
Recommendations
  • Add Linux/macOS-specific examples, such as using shell scripts (.sh) instead of batch files (.bat), and ELF binaries instead of .exe.
  • Document how Service Fabric manifests and policies map to Linux environments, including supported account types and security principals.
  • Reference Linux-native tools and deployment patterns, and clarify any differences in resource governance, endpoint configuration, and user/group management.
  • Explicitly state platform compatibility for each feature and example, and provide parity in guidance for both Windows and Linux clusters.
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: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a notable Windows bias. All deployment and management command-line examples use PowerShell, with no mention of Azure CLI, Bash, or Linux/macOS-compatible workflows. Windows tools (PowerShell, RDP, Windows-style paths) are referenced exclusively and shown first, while Linux equivalents (SSH, Azure CLI, Bash) are absent. This creates friction for Linux/macOS users who cannot directly use the provided examples and must translate them to their environment.
Recommendations
  • Add Azure CLI and Bash examples alongside PowerShell for all deployment steps.
  • Include Linux/macOS-compatible instructions for accessing VMs (e.g., SSH instead of RDP).
  • Use platform-neutral file paths in examples, or show both Windows and Linux paths.
  • Explicitly state cross-platform support and link to relevant Azure CLI documentation.
  • Provide guidance for Linux users on prerequisites and environment setup.
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 exhibits Windows bias primarily through the use of Windows-specific tooling and examples. The only explicit deployment example uses PowerShell (New-ServiceFabricApplication), and the Service Fabric SDK schema path is given only in Windows format. Linux-specific details are minimal and appear later in the document, such as the mention of the certificate store location. There are no Linux CLI or deployment examples, and Windows tools and patterns are referenced before their Linux equivalents (if any).
Recommendations
  • Provide equivalent Linux/macOS deployment examples using Azure CLI or Service Fabric CLI (sfctl), alongside PowerShell examples.
  • Mention Linux file paths and tooling (e.g., where the ServiceManifest schema is located on Linux) alongside Windows paths.
  • Clarify cross-platform differences in endpoint configuration and certificate management earlier in the document.
  • Add explicit notes or sections for Linux/macOS users, especially for steps that differ from Windows.
  • Ensure that all code snippets and instructions are platform-neutral or provide alternatives for each platform.
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 exhibits several Windows-centric biases. It references Visual Studio and its solution structure as the default workflow for configuration, mentions the Get-ServiceFabricClusterManifest PowerShell command as the way to view the cluster manifest, and uses Windows-style file paths (e.g., f:\SharedLog.Log) in examples. Linux-specific instructions are minimal, limited to a note about PEM-formatted certificates, and there are no Linux/macOS equivalents for key tasks such as viewing the cluster manifest or configuring the environment outside Visual Studio. No Linux/macOS configuration file locations, tools, or command-line examples are provided.
Recommendations
  • Provide Linux/macOS equivalents for all Windows-specific commands, such as how to view the cluster manifest (e.g., using sfctl or direct file access).
  • Include Linux/macOS file path examples alongside Windows paths in configuration samples.
  • Describe how to locate and edit configuration files when not using Visual Studio, such as with cross-platform editors or command-line tools.
  • Add explicit Linux/macOS workflow steps for configuring ReliableDictionaryActorStateProvider, including where files are located and how to deploy changes.
  • Ensure parity in security configuration examples, showing both Windows and Linux certificate handling.
GitHub Create Pull Request
Service Fabric Reliable Collection object serialization ...c-reliable-services-reliable-collections-serialization.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. In the 'Next steps' section, upgrade tutorials are provided for Visual Studio and PowerShell—both Windows-centric tools—without mention of Linux/macOS alternatives or cross-platform CLI options. No Linux-specific instructions, examples, or tooling are referenced, and Windows tools are listed before any potential alternatives. The main content does not reference platform-specific code, but the guidance and linked resources favor Windows environments.
Recommendations
  • Add equivalent upgrade tutorials for Linux/macOS users, such as using Azure CLI or Service Fabric CLI (sfctl).
  • Include references to cross-platform tools and workflows in the 'Next steps' section.
  • Ensure that examples and linked resources cover both Windows and Linux environments, or explicitly state platform requirements.
  • Where PowerShell is mentioned, also mention Bash or other Linux shell alternatives if available.
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 ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a notable Windows bias. PowerShell is the only CLI example provided, and all command-line snippets use Windows paths and conventions (e.g., 'PS C:\>'). There is no mention of Linux or macOS equivalents, nor are cross-platform CLI tools or shell examples (such as Bash or Azure CLI) provided. The use of PowerShell cmdlets and Windows-centric terminology appears before REST or API options, and there is no guidance for users running Service Fabric on Linux clusters or accessing the health reporting features from non-Windows environments.
Recommendations
  • Add equivalent examples using Bash or shell commands for Linux/macOS environments.
  • Include Azure CLI or cross-platform CLI examples for health reporting.
  • Explicitly mention how Linux-based Service Fabric clusters can report health, including any differences in tooling or authentication.
  • Reorder sections so REST and API examples are presented before or alongside PowerShell, emphasizing platform neutrality.
  • Clarify which commands and tools are Windows-only and provide alternatives for other 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 naming conventions (e.g., 'WinFabric-Test-SAN1-Alice'), and omitting concrete Linux configuration examples. Although there is a brief mention that Linux nodes require PEM-formatted certificates and a link to Linux certificate configuration, all XML configuration samples and parameter values are tailored to Windows environments, with no Linux equivalents or guidance on Linux-specific settings (such as file paths, store locations, or certificate handling patterns).
Recommendations
  • Add explicit XML configuration examples for Linux, showing how to specify PEM file paths and relevant parameters.
  • Document Linux-specific values for parameters like CertificateStoreLocation and CertificateStoreName, or clarify which parameters are ignored on Linux.
  • Provide sample certificate naming conventions and common names for Linux environments.
  • Include a table comparing Windows and Linux configuration differences for FabricTransport security settings.
  • Reference Linux tools or commands for certificate management alongside Windows concepts.
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: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ powershell_heavy
Summary
The documentation demonstrates a moderate Windows bias, primarily through its extensive focus on HTTP.sys, a Windows-only web server, and references to Windows-specific tools (e.g., netsh). HTTP.sys is described in detail, with code samples and configuration guidance, but it is explicitly stated to be unavailable on Linux. While Kestrel, the cross-platform web server, is also covered and recommended for Linux, the documentation gives HTTP.sys significant attention and places Windows-specific instructions before Linux alternatives. There are no Linux/macOS-specific configuration or troubleshooting examples, and Windows tools are referenced without Linux equivalents.
Recommendations
  • Add explicit Linux/macOS sections or examples, especially for endpoint configuration and troubleshooting.
  • Where Windows tools (e.g., netsh) are mentioned, provide Linux/macOS alternatives or clarify that they are not needed for Kestrel.
  • Reorder sections so that cross-platform solutions (Kestrel) are presented before Windows-only solutions (HTTP.sys).
  • Include notes or tables summarizing platform compatibility for each approach.
  • Add troubleshooting guidance for Linux/macOS environments, including common issues and solutions.
  • Clarify in all configuration examples which are Windows-only and which are cross-platform.
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 securing service remoting communications for C# services, with all code samples and configuration instructions tailored to Windows environments. Windows certificate store concepts (StoreLocation, StoreName) are used throughout, and there are no Linux-specific code examples or configuration patterns for C# on Linux. Linux is only mentioned in passing regarding certificate file location, with no parity in code or workflow examples.
Recommendations
  • Provide C# code examples and configuration instructions for Linux environments, including how to reference PEM certificates and any differences in API usage or deployment.
  • Include explicit Linux/macOS setup steps for certificate management, such as how to generate, store, and reference certificates in the Service Fabric cluster.
  • Clarify which settings or APIs are platform-specific and offer alternatives or notes for cross-platform compatibility.
  • Present examples for both Windows and Linux side-by-side, or clearly indicate platform differences in each step.
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 command-line examples. There is no mention of Linux or cross-platform equivalents, nor are there examples using Linux-native tools or CLI patterns. The documentation assumes the use of PowerShell and Windows tooling, which may create friction for Linux/macOS users managing Service Fabric clusters.
Recommendations
  • Include equivalent Linux/macOS command-line examples using Service Fabric CLI (sfctl) or REST APIs where available.
  • Explicitly mention cross-platform management options and provide links to relevant documentation for Linux/macOS users.
  • Clarify whether the described APIs (e.g., Restore-ServiceFabricReplica) are available via sfctl or REST, and provide usage examples.
  • Reorder examples or explanations so that cross-platform options are presented alongside or before Windows/PowerShell-specific instructions.
  • Add notes or sections addressing Linux/macOS cluster management workflows for replica soft delete.
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 demonstrates a moderate Windows bias. Standalone cluster instructions and references (e.g., ClusterConfig.json, certificate management) are written for Windows environments, with links and examples pointing to Windows Server-specific guides. There is no mention of Linux-based standalone clusters, nor are Linux-specific certificate store details or upgrade instructions provided. The documentation refers to Windows paths (e.g., D:\SvcFab) and store names (e.g., 'My'), and upgrade instructions for standalone clusters link to Windows Server documentation. No Linux/macOS command-line examples or configuration patterns are given for standalone clusters.
Recommendations
  • Add explicit instructions and examples for Linux-based standalone clusters, including certificate management and configuration file locations.
  • Provide parity in upgrade instructions for standalone clusters running on Linux, with links to relevant Linux documentation.
  • Clarify which steps or settings are OS-specific, and offer alternatives or notes for Linux/macOS users.
  • Include Linux/macOS command-line examples where PowerShell or Windows tools are referenced.
  • Avoid using Windows paths or store names exclusively; mention Linux equivalents where relevant.
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 demonstrates a moderate Windows bias. Diagnostic error codes and terminology (e.g., ERROR_WINHTTP_TIMEOUT, ERROR_SUCCESS, winHttpError) are Windows-centric, and troubleshooting examples reference Windows-specific APIs and error codes. The 'Next steps' section prioritizes Windows Azure Diagnostics and Visual Studio for event viewing, with no mention of Linux equivalents or cross-platform tools. There are no explicit Linux/macOS examples or guidance for collecting or viewing logs on non-Windows platforms.
Recommendations
  • Add Linux/macOS-specific troubleshooting examples, including common error codes and log formats.
  • Include instructions for collecting and viewing Service Fabric reverse proxy logs using Linux-native tools (e.g., journald, syslog, Azure Monitor on Linux).
  • Reference cross-platform log aggregation and viewing solutions, such as Azure Monitor, Log Analytics, or open-source tools.
  • Balance the 'Next steps' section by mentioning Linux-compatible tools and IDEs (e.g., VS Code, CLI-based monitoring).
  • Clarify which error codes/messages are Windows-specific and provide Linux equivalents where applicable.
GitHub Create Pull Request
Service Fabric Define Service Configuration in StartupServices.xml for a Service Fabric Application ...service-fabric/service-fabric-startupservices-model.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. It repeatedly references Visual Studio-specific workflows (Build/Rebuild/F5/Ctrl+F5/Publish), which are only available on Windows. The only command-line tooling mentioned is PowerShell, with no mention of Linux/macOS equivalents (such as Bash, CLI, or cross-platform tools). There are no examples or guidance for deploying or managing Service Fabric applications from Linux or macOS environments, nor is there any mention of how StartupServices.xml fits into non-Windows workflows. The documentation assumes the use of Visual Studio and Windows-centric deployment patterns throughout.
Recommendations
  • Add explicit guidance for Linux/macOS users, including how to deploy Service Fabric applications without Visual Studio.
  • Provide examples using Azure CLI, Bash, or other cross-platform tools for managing Service Fabric applications and manifests.
  • Clarify whether StartupServices.xml is relevant or supported in non-Windows environments, and if not, suggest alternatives.
  • Reorder examples or add parallel sections for Linux/macOS workflows to avoid Windows-first presentation.
  • Mention any limitations or differences for users working outside Windows/Visual Studio.
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 and provides only PowerShell-based examples for scaling out a Service Fabric managed cluster. There is no mention of Linux/macOS-compatible tools (such as Azure CLI), nor are alternative commands or instructions provided for non-Windows platforms. The prerequisites and example code assume a Windows environment, creating friction for Linux/macOS users.
Recommendations
  • Include Azure CLI examples for scaling node types, as Azure CLI is cross-platform and works on Linux/macOS.
  • Update prerequisites to mention both Azure PowerShell and Azure CLI, with links to installation instructions for all platforms.
  • Explicitly state platform compatibility for each method, and recommend the most cross-platform approach first.
  • Consider providing bash or shell script examples alongside PowerShell.
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 toward Windows, with all examples and instructions using Azure PowerShell. There are no CLI (az) or Linux/macOS-specific instructions or examples, despite mentioning that CLI is an option. The prerequisites only list Azure PowerShell, which is primarily used on Windows, and do not mention the Azure CLI or Bash alternatives.
Recommendations
  • Add equivalent Azure CLI examples for adding and removing node types, as Azure CLI is cross-platform and works natively on Linux/macOS.
  • Update the prerequisites section to mention both Azure PowerShell and Azure CLI, including installation instructions for Linux/macOS users.
  • Explicitly state which commands are platform-agnostic and provide guidance for users on non-Windows platforms.
  • Consider reordering or presenting examples for both PowerShell and CLI side-by-side, or defaulting to CLI for cross-platform parity.
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: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page presents Windows-centric examples, such as PowerShell scripts and Windows disk formatting, in the main template samples. Linux-specific guidance is relegated to a single external link, and no Linux shell script example is shown inline. Windows tools and extensions are referenced first and exclusively in the main body, creating friction for Linux users.
Recommendations
  • Include an inline example of extension sequencing using a Linux shell script (e.g., bash) for disk formatting, not just as an external link.
  • Present both Windows and Linux scenarios side-by-side or in parallel sections to ensure equal visibility.
  • Reference Linux tools and patterns (e.g., bash scripts, Linux disk utilities) in the main template samples.
  • Clarify which examples apply to Windows and which to Linux in the text, to avoid confusion.
  • Ensure that Linux-specific extensions and workflows are documented with the same level of detail as Windows.
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 moderate Windows bias. While it mentions both Windows and Linux support, it highlights Windows capabilities (OS and data disk encryption) before Linux (data disks only, with OS disk encryption explicitly unsupported). The tutorials referenced include both Azure CLI (cross-platform) and PowerShell (Windows-centric), but do not explicitly mention Linux-specific guidance or examples. There is no direct Linux command-line example or parity in instructions, and the limitations for Linux are stated after Windows features.
Recommendations
  • Add explicit Linux command-line examples (e.g., Bash, Azure CLI on Linux) and clarify Linux-specific steps.
  • Present Linux and Windows capabilities side-by-side, rather than listing Windows features first.
  • Include a section or link for Linux troubleshooting and workarounds for unsupported features (e.g., OS disk encryption).
  • Ensure tutorial links specify which platforms they target, and provide equivalent Linux-focused tutorials where possible.
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
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 scenarios (such as VM activation and Windows updates) are mentioned before Linux equivalents, and troubleshooting links are provided only for Windows. There are no explicit Linux-focused migration or troubleshooting examples, and Linux package manager access is mentioned only briefly and after Windows scenarios. Command-line examples use Azure CLI, which is cross-platform, but PowerShell is referenced as an alternative without Linux shell equivalents. There are no Linux/macOS-specific instructions or considerations.
Recommendations
  • Add explicit Linux migration scenarios and troubleshooting links (e.g., for Linux VM activation, package manager connectivity).
  • Provide Linux/macOS command-line examples (e.g., bash scripts) alongside Azure CLI and PowerShell.
  • Mention Linux-specific tools or patterns where relevant, such as cloud-init or SSH key management.
  • Ensure Linux scenarios (e.g., updates, connectivity) are described with equal detail and priority as Windows scenarios.
  • Reference Linux documentation for common tasks (e.g., troubleshooting, updates) in the same way as Windows.
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 detailed PowerShell examples for creating scale sets, including both simplified and extended parameter sets, which are specific to Windows environments. The CLI examples are present and generally cross-platform, but the PowerShell section is much more extensive, with advanced networking and load balancer configuration shown only in PowerShell. There is no mention of Linux shell scripting or equivalent advanced automation for Linux/macOS users. Additionally, the PowerShell tab is placed after CLI and Portal, but the depth of PowerShell coverage and the use of Windows-centric tools (e.g., Get-Credential, New-AzResourceGroup) indicate a bias toward Windows users.
Recommendations
  • Add equivalent advanced examples using Bash shell scripting and Azure CLI for Linux/macOS users, covering networking and load balancer configuration.
  • Explicitly mention that PowerShell examples are for Windows and provide links or guidance for Linux/macOS automation.
  • Ensure that all advanced scenarios shown in PowerShell are also available in CLI or ARM template examples.
  • Consider adding a section on using Azure CLI in Bash scripts for automation, including credential management and resource configuration.
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 page demonstrates a mild Windows bias by exclusively referencing the Azure portal (a web GUI most commonly used on Windows) for role assignment steps and troubleshooting, without providing equivalent CLI or automation examples (such as Azure CLI or Bash scripts) that are platform-agnostic and preferred by many Linux/macOS users. The only mention of SDKs includes 'PowerShell' before 'CLI', and no explicit Linux/macOS tooling or examples are given.
Recommendations
  • Add step-by-step instructions for assigning roles using Azure CLI and/or Azure PowerShell, with example commands.
  • Provide troubleshooting examples using Azure CLI (az monitor, az role assignment, etc.) alongside portal-based instructions.
  • Explicitly mention that all steps can be performed on Linux/macOS using CLI tools, and provide links to relevant cross-platform documentation.
  • List SDKs in a neutral order (e.g., 'CLI or PowerShell') or highlight cross-platform options first.
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 Azure CLI is cross-platform and shown before PowerShell, the PowerShell section is extensive and detailed, with multiple example scenarios and advanced usage. There is a slight bias toward Windows tooling, as PowerShell is a Windows-first tool and its coverage is more comprehensive than the CLI section. Additionally, prerequisites mention PowerShell before CLI, and the CLI examples use Ubuntu images but do not discuss Linux-specific considerations or parity with PowerShell features.
Recommendations
  • Expand Azure CLI examples to cover advanced scenarios currently only shown for PowerShell, such as using configuration objects.
  • Add notes or examples for Bash scripting and Linux shell environments, especially for tasks like credential management and network configuration.
  • Ensure that CLI and PowerShell sections have parity in terms of depth and complexity of examples.
  • Explicitly mention that Azure CLI is fully supported on Linux/macOS and highlight any differences or limitations compared to PowerShell.
  • In prerequisites, list CLI before PowerShell to signal platform neutrality.
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, including extensive networking and load balancer configuration, while the CLI (cross-platform) examples are much simpler and lack equivalent depth. The PowerShell section uses Windows-centric tooling and patterns, and is presented before the CLI in the main specialized image scenario. There is no mention of Linux/macOS-specific considerations or parity in scripting depth.
Recommendations
  • Expand the Azure CLI section to include more comprehensive examples, matching the depth of the PowerShell walkthrough (e.g., networking, load balancer setup).
  • Explicitly mention that Azure CLI works cross-platform and is recommended for Linux/macOS users.
  • Add notes or examples for Linux/macOS users where PowerShell is referenced, including alternative commands or scripts.
  • Consider presenting CLI examples before PowerShell, or side-by-side, to avoid Windows-first impression.
  • Highlight any OS-specific requirements or differences in resource creation, if applicable.
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: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a notable Windows bias: all code examples use PowerShell cmdlets, with no Azure CLI or Linux/macOS shell equivalents provided inline. Windows tools and patterns (PowerShell, cmdlets) are mentioned and demonstrated exclusively and before any reference to Linux alternatives. The only mention of Azure CLI is in a 'Next steps' link, rather than integrated examples. This creates friction for Linux/macOS users, who must seek out separate documentation or translate PowerShell examples themselves.
Recommendations
  • Add inline Azure CLI examples alongside PowerShell for all key tasks (creating/listing proximity placement groups, creating scale sets, checking status).
  • Explicitly mention Linux/macOS support and provide bash shell snippets where appropriate.
  • Reorganize examples so that CLI and PowerShell approaches are presented together or in parallel sections.
  • Ensure references to Linux documentation are as prominent as Windows/PowerShell equivalents.
  • Clarify that all operations are cross-platform and not limited to Windows/PowerShell.
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
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation provides both Azure CLI and PowerShell examples, but PowerShell is given its own dedicated tab and is mentioned alongside deployment tools for ARM and Bicep templates. Windows-centric tools (PowerShell, New-AzResourceGroupDeployment) are referenced as primary deployment options, and PowerShell is presented before Linux-native alternatives in several places. There are no explicit Linux/macOS examples or notes about cross-platform usage for CLI commands.
Recommendations
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • List CLI examples before PowerShell examples to reduce Windows-first impression.
  • For ARM and Bicep template deployment, highlight az deployment group create (CLI) as the primary method, and mention PowerShell as an alternative.
  • Add notes or links for Linux/macOS users, clarifying that all CLI commands work natively on those platforms.
  • Consider including bash script examples or references to shell usage for Linux/macOS users.
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 ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a moderate Windows bias. Windows-centric tools (PowerShell) are frequently mentioned, often before cross-platform alternatives (Azure CLI). Examples for manual scaling are provided for Azure Portal, Azure CLI, and Azure PowerShell, but no explicit Linux shell or macOS terminal examples are given. References to management and next steps prioritize PowerShell, and links to PowerShell tutorials and management guides are listed before CLI or template options. There is a lack of parity in example ordering and tool coverage for Linux/macOS users.
Recommendations
  • Provide explicit Linux/macOS shell examples (e.g., Bash) alongside PowerShell, especially for common tasks.
  • Order cross-platform tools (Azure CLI) before Windows-specific tools (PowerShell) in examples and next steps.
  • Include links to Linux/macOS management guides and tutorials where available.
  • Clarify that Azure CLI commands work on Windows, Linux, and macOS, and provide platform-specific notes if needed.
  • Balance references to PowerShell and CLI throughout the documentation to ensure equal visibility.
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 Windows bias by providing examples and instructions primarily for Windows-based scale sets, referencing Windows-specific extensions (ApplicationHealthWindows, CustomScriptExtension for Windows), and using Windows-centric tools (PowerShell, Windows extension types) without showing equivalent Linux examples or mentioning Linux extension types. Both the Azure PowerShell and Azure CLI examples are explicitly for Windows-based scale sets, and there is no guidance for Linux-based scale sets or Linux extensions.
Recommendations
  • Add parallel examples for Linux-based scale sets, using Linux-specific extensions (e.g., ApplicationHealthLinux, CustomScriptExtension for Linux).
  • Explicitly mention the applicability of extension sequencing to Linux VMSS and provide sample ARM templates, REST API payloads, PowerShell, and CLI commands for Linux scenarios.
  • Ensure that documentation references both Windows and Linux extension types and links to their respective documentation.
  • Where possible, present examples for both platforms side by side or clarify platform-specific differences.
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 deployment options, but there is a notable Windows bias: Windows/PowerShell examples and tools (PowerShell DSC, PowerShell cmdlets) are described in greater detail and appear before Linux equivalents. The Windows section includes a full PowerShell script, while the Linux section refers users to external documentation for cloud-init and does not provide an inline example. Windows management tools (PowerShell DSC, Update-AzVmss, etc.) are highlighted, while Linux alternatives (such as Ansible or native Linux configuration management) are not mentioned. Some links and next steps also prioritize PowerShell/Windows management.
Recommendations
  • Provide inline, detailed cloud-init examples for Linux, similar to the PowerShell DSC example for Windows.
  • Mention and link to Linux-native configuration management tools (e.g., Ansible, Chef, Puppet) as alternatives to PowerShell DSC.
  • Ensure Linux examples are presented with equal prominence and detail as Windows examples.
  • Balance references to management tools (CLI, PowerShell) by including Linux-friendly options and workflows.
  • In 'Next steps', include links to Linux management guides, not just PowerShell/Windows guides.
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 provides detailed PowerShell examples and references, with CLI examples included but presented after PowerShell. There is a notable lack of explicit Linux/macOS shell examples or discussion of platform-specific considerations. The 'scheduled events' link and section reference Windows documentation, and there is no mention of Linux-specific tools or patterns. This creates friction for Linux/macOS users, though most tasks can be completed using the Azure CLI.
Recommendations
  • Provide Bash or shell script examples alongside PowerShell for all command-line instructions.
  • Reference both Windows and Linux/macOS scheduled events documentation, not just Windows.
  • Clarify that Azure CLI commands work cross-platform and highlight any platform-specific differences.
  • Add notes or examples for Linux users where PowerShell is mentioned, such as using Azure CLI or REST API.
  • Ensure links to scheduled events and other features point to both Windows and Linux documentation.
GitHub Create Pull Request
Virtual Machine Scale Sets Networking for Azure Virtual Machine Scale Sets ...ne-scale-sets/virtual-machine-scale-sets-networking.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 Azure CLI and PowerShell examples for most networking tasks, but PowerShell (a Windows-centric tool) is often presented before CLI, and some sections (such as querying public IPs) give more detailed PowerShell examples. References to Windows-specific scenarios (e.g., Windows VM activation) are present, and PowerShell is used heavily in example scripts. Linux/macOS users may find parity, but Windows tools and patterns are often prioritized or more deeply covered.
Recommendations
  • Present CLI examples before PowerShell, as CLI is cross-platform.
  • Ensure all PowerShell examples have equivalent, fully detailed CLI examples.
  • Add Bash script examples where scripting is shown for PowerShell.
  • When referencing OS-specific scenarios (e.g., Windows VM activation), also mention Linux equivalents or clarify when not applicable.
  • Avoid referring to PowerShell as the default or primary automation tool; emphasize CLI for cross-platform parity.
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 the application health extension response. However, there is a notable Windows bias: PowerShell examples are consistently present and detailed, sometimes appearing before or alongside Linux equivalents. Windows-specific extension types (ApplicationHealthWindows) are used in several code samples and REST payloads, often as the default or first shown. The PowerShell tab is always present and sometimes more verbose than the Bash/Linux tab. REST API examples also default to Windows extension types. While Linux users are not blocked from completing the task, Windows tools and patterns are emphasized, and Linux parity could be improved.
Recommendations
  • Ensure Linux and Windows examples are presented with equal prominence and detail, alternating which is shown first.
  • In REST API and JSON configuration samples, use ApplicationHealthLinux as the default or provide both Linux and Windows variants.
  • Expand Bash/Python/Linux examples to match the depth and clarity of PowerShell examples, including troubleshooting and verification steps.
  • Explicitly mention cross-platform compatibility and clarify when a step or tool is OS-specific.
  • Provide macOS-specific notes or examples where relevant, especially for scripting and endpoint configuration.
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
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 Azure PowerShell examples for creating and updating scale sets with Availability Zones, but PowerShell (a Windows-centric tool) is given equal prominence to CLI, and is sometimes listed before or alongside CLI. There are no explicit Linux shell (bash) examples, nor are Linux-specific considerations or tools mentioned. The ARM template section references both Linux and Windows, but does not provide a Linux shell example for deployment. The overall pattern is to treat Windows/PowerShell as a first-class or default environment, with limited explicit Linux parity.
Recommendations
  • Add explicit bash shell examples for Linux/macOS users alongside Azure CLI and PowerShell sections.
  • Ensure CLI examples are shown before PowerShell, as CLI is cross-platform and more commonly used on Linux/macOS.
  • Clarify that Azure CLI commands work natively on Linux/macOS and provide installation links or notes for those platforms.
  • Where PowerShell is mentioned, add a note that PowerShell Core is available cross-platform, but CLI is recommended for Linux/macOS.
  • Provide a sample ARM template deployment using Azure CLI on Linux/macOS, not just the template JSON.
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 Windows bias in several areas. In code examples for enabling Automatic Extension Upgrade, the extension type shown is 'DependencyAgentWindows' in REST API, PowerShell, and ARM template samples, with Linux equivalents either omitted or shown only in CLI examples. PowerShell examples are provided, but Bash or Linux-native scripting is not. Windows extension types and tools (PowerShell cmdlets) are mentioned first or exclusively in several sections, and Linux examples are less prominent or missing, especially in PowerShell and template sections.
Recommendations
  • Provide parallel examples for both Windows and Linux extension types in all code samples (REST API, PowerShell, ARM templates), not just CLI.
  • Include Bash or Linux-native scripting examples alongside PowerShell for automation tasks.
  • Alternate the order of Windows and Linux examples to avoid Windows-first presentation.
  • Explicitly mention Linux support in all procedural steps, not just in summary tables.
  • Where PowerShell is used, add equivalent instructions for Linux users (e.g., Azure CLI, Bash scripts).
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 described as Windows-only (e.g., System Errors from Windows event log, Hardware Health Monitor via Windows event log), while their Linux equivalents are either missing or less detailed. In the Clock section, the fallback check for time sync is described specifically for Windows (w32tm), with no Linux equivalent mentioned. Windows tools and event logs are referenced directly, while Linux alternatives (such as syslog, journalctl, or chrony/ntpd for time sync) are not discussed. Although the page claims compatibility with both Linux and Windows, some critical monitoring features appear to be Windows-centric or lack Linux parity.
Recommendations
  • Add equivalent Linux examples and details for system error/event log collection (e.g., using syslog, journalctl, or /var/log/messages).
  • Describe how clock skew is checked on Linux VMs (e.g., using chrony, ntpd, or timedatectl), not just Windows (w32tm).
  • For hardware health monitoring, specify how disk and hardware events are collected on Linux (e.g., using SMART tools, dmesg, or syslog), not only via Windows event logs.
  • Ensure that all monitoring signals and checks have Linux equivalents or clearly state any platform limitations.
  • Present examples and tool references for both platforms side-by-side, rather than focusing on Windows tools first.
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 for both Windows and Linux VMs, but 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 guidance. This creates a subtle bias, as Linux users may not find direct instructions or parity in example coverage.
Recommendations
  • Add a Linux-specific example or documentation link for creating managed disk snapshots, ensuring parity with the Windows example.
  • Explicitly mention that the snapshot process applies equally to Linux VMs, or clarify any differences if they exist.
  • Review other sections for example parity and ensure both platforms are equally represented in hands-on guides and references.
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 demonstrates a moderate Windows bias. Windows examples (especially PowerShell and CLI) are more detailed and appear first in several sections. There are multiple PowerShell examples for Windows, but no equivalent Bash or Linux-native scripting examples. CLI examples for Linux are present but less emphasized. Windows-specific tools and registry keys are mentioned in detail, while Linux equivalents (such as disabling automatic updates) are less thoroughly covered. The 'Next steps' section links only to Windows VM management.
Recommendations
  • Add Linux-native scripting examples (e.g., Bash) for enabling/disabling patching and for on-demand patch assessment/installation.
  • Present Linux and Windows examples in parallel, or alternate which OS is shown first in each section.
  • Expand coverage of Linux-specific patching tools and configuration steps (e.g., how to disable automatic updates for various distros, not just RHEL).
  • Include 'Next steps' links for both Linux and Windows VM management.
  • Where registry keys or Windows Update settings are discussed, provide Linux equivalents (e.g., apt/yum/dnf/zypper settings).
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
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 mild Windows bias by mentioning Windows-specific backup mechanisms (Volume Shadow Service, SQL Server Always On) before Linux equivalents, and linking to Windows-focused SQL Server articles. Linux tools (like fsfreeze) are referenced but with less detail and after Windows solutions. There are no Linux/Powershell command examples, but Windows technologies are described more thoroughly. No explicit Linux backup workflows or application-consistent backup examples are provided.
Recommendations
  • Provide equal detail for Linux backup tools and workflows (e.g., describe how to use fsfreeze or LVM snapshots for application-consistent backups on Linux).
  • Include links to Linux-focused documentation for database backup and disaster recovery (e.g., Oracle on Linux, PostgreSQL, MySQL).
  • Add example backup/restore commands for both Windows (PowerShell) and Linux (bash/CLI) environments.
  • Mention Linux-first solutions and tools in parallel with Windows ones, not after.
  • Clarify application-consistent backup options for Linux workloads, with practical guidance.
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: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates a moderate Windows bias, especially in the ARM template section, which is heavily Windows-centric (Windows images, PowerShell DSC, Windows admin credentials). PowerShell examples are provided alongside CLI, but there is no equivalent Bash scripting or Linux-specific automation. The ARM template does not show how to deploy a Linux VMSS, and Windows terminology/tools (PowerShell DSC, WebDeploy) are referenced without Linux alternatives. CLI examples do use Ubuntu images, but the template and supporting text focus on Windows.
Recommendations
  • Add ARM template examples for Linux VMSS deployments, including Linux image references and configuration.
  • Provide Bash shell scripting examples for automation tasks, not just PowerShell.
  • In ARM template parameters, include both Windows and Linux OS options, with documentation on how to select and configure each.
  • Mention Linux equivalents for configuration management (e.g., cloud-init, custom script extension) instead of only PowerShell DSC.
  • Ensure examples and explanations are OS-neutral or show both Windows and Linux options side-by-side.
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 provides both Windows and Linux parity in CLI/API/Portal instructions, but there are notable signs of Windows bias. PowerShell examples (Windows-only) are given equal prominence as Azure CLI (cross-platform), and ARM template examples focus exclusively on Windows VM images and parameters. The ARM template omits any Linux image or configuration, and the password complexity guidance is tailored to Windows. In several places, Windows terminology and tools (PowerShell, Windows images) are mentioned before or instead of Linux equivalents.
Recommendations
  • Add ARM template examples for Linux VMs, including imageReference for popular Linux distributions (e.g., Ubuntu, CentOS).
  • In ARM template parameters, include both Windows and Linux OS options, with clear documentation for each.
  • Where password complexity is discussed, clarify differences for Linux VMs (e.g., SSH keys vs. passwords).
  • Ensure examples and instructions alternate or balance Windows and Linux references, rather than defaulting to Windows first.
  • Consider adding Bash shell examples for common operations, especially for Linux users.
  • Review terminology and ensure it is inclusive of both Windows and Linux workflows.
GitHub Create Pull Request
Virtual Machines Proximity placement groups ...ocs/blob/main/articles/virtual-machines/co-location.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 references both Linux and Windows VMs as supported, but there are several signs of Windows bias. PowerShell is mentioned explicitly and described before CLI in sections about checking colocation status, and the PowerShell cmdlet is given with more detail than the CLI equivalent. There are no explicit Linux-specific examples or commands, and the CLI is mentioned only after PowerShell. The best practices section links to both Linux and Windows accelerated networking guides, but the Windows (PowerShell) link is listed second. There are no Bash or Linux-native command examples, and no mention of Linux-specific tooling or workflows.
Recommendations
  • Provide Linux/Bash command examples alongside PowerShell, especially for common tasks like checking colocation status.
  • Mention Azure CLI before or alongside PowerShell to avoid Windows-first bias.
  • Include explicit Linux workflow guidance (e.g., using Bash, cloud-init, or Linux-native tools) where relevant.
  • Ensure parity in detail and clarity between CLI and PowerShell instructions.
  • Add Linux-specific troubleshooting tips if any exist.
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 equal prominence to Azure CLI. The mention of Visual Studio Code as the IDE is neutral, but PowerShell is listed as a primary method for accessing vmWatchSettings, which may create friction for Linux/macOS users who typically use Bash or shell scripting. There are no explicit Bash or Linux shell examples, and PowerShell is referenced before any Linux-specific alternatives.
Recommendations
  • Add explicit Bash or shell examples for Linux/macOS users alongside PowerShell examples.
  • Clarify that Azure CLI commands work cross-platform and provide sample Linux/macOS shell usage (e.g., with environment variables, piping, etc.).
  • If PowerShell is mentioned, also mention Bash or other common Linux shells to ensure parity.
  • Consider listing CLI (cross-platform) examples before PowerShell (Windows-centric) examples.
  • Note any platform-specific differences in command syntax or required tools.
GitHub Create Pull Request
Virtual Machines Create Virtual Machine restore points ...ain/articles/virtual-machines/create-restore-points.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 moderate Windows bias. Windows-specific features (application consistency) are mentioned before Linux equivalents (file system consistency). PowerShell is referenced multiple times, both in the main text and in the 'Next steps' section, with no equivalent Bash or Linux CLI examples. The only tool specifically linked for scripting is PowerShell, and there are no Linux/macOS shell or CLI examples provided, nor is the Azure CLI highlighted equally. This creates friction for Linux/macOS users who may prefer Bash or cross-platform tools.
Recommendations
  • Add Azure CLI examples and links alongside PowerShell references.
  • Explicitly mention Linux/macOS compatibility and provide Bash or shell script examples where possible.
  • Ensure that references to scripting tools (PowerShell, CLI) are presented in parallel, not with PowerShell first or exclusively.
  • Highlight Linux-specific features and parity, such as file system consistency, with equal prominence as Windows features.
  • Include a section or note on how Linux users can perform these tasks using their preferred tools.
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
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation provides examples for Azure Portal, CLI, PowerShell, and REST API, but PowerShell (a Windows-centric tool) is given equal prominence to CLI, and is detailed throughout. REST API examples use Windows-centric values (e.g., Windows images, Windows-specific OS types). There is no explicit Linux/macOS shell scripting example (e.g., Bash), nor are Linux-specific considerations or patterns discussed. The FAQ and general guidance do not mention Linux-specific behaviors, and the only reference to Linux is a link in 'Next steps', which is not integrated into the main content.
Recommendations
  • Add explicit Bash examples for Linux/macOS users, especially for scripting VM deletion and resource cleanup.
  • In REST API examples, alternate between Windows and Linux VM configurations, or provide both.
  • Clarify that CLI commands work cross-platform and highlight any OS-specific differences.
  • Balance PowerShell and CLI coverage, and consider moving PowerShell examples after CLI/Bash to reduce Windows-first perception.
  • In the FAQ and general guidance, mention any Linux-specific considerations (e.g., differences in VM images, OS disk handling).
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 both Azure CLI (cross-platform) and Azure PowerShell (Windows-centric) examples for copying snapshots, but the PowerShell section is detailed and includes installation instructions, while the CLI section assumes familiarity. There are no explicit Linux/macOS shell script examples, nor is there mention of Linux-specific considerations. The .NET sample code referenced is also Windows-oriented. The ordering of examples places Azure CLI first, but the PowerShell section is more verbose and instructional.
Recommendations
  • Add explicit Bash/Linux/macOS shell script examples for Azure CLI usage, including environment setup and authentication steps.
  • Include notes on cross-platform compatibility for all CLI commands, clarifying that Azure CLI works natively on Linux/macOS.
  • Provide sample code or links for Linux/macOS automation (e.g., Bash scripts, Python) for the manual copy process.
  • Reference cross-platform SDKs (e.g., Python, Java) in addition to .NET for sample code.
  • Balance instructional detail between PowerShell and CLI sections, ensuring Linux/macOS users have equal guidance.
GitHub Create Pull Request
Virtual Machines Migrate from Azure Disk Encryption to encryption at host ...n/articles/virtual-machines/disk-encryption-migrate.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 generally provides both Windows and Linux guidance, but there are several signs of Windows bias. Windows examples and considerations are often listed first, and PowerShell/Windows-specific tools are more prominently featured. Some sections, especially around domain-joined VM migration and disk operations, provide more detailed or explicit steps for Windows than for Linux. There are also places where Linux instructions are less detailed or refer users to external links for critical steps, while Windows instructions are more self-contained.
Recommendations
  • Alternate the order of Windows and Linux instructions to avoid always presenting Windows first.
  • Provide equally detailed, step-by-step Linux examples for all major operations, especially for domain join/removal and disk migration.
  • Where PowerShell is used for Windows, provide Bash or native Linux command alternatives for Linux users, not just Azure CLI.
  • Expand Linux-specific troubleshooting and verification steps to match the depth provided for Windows.
  • Ensure all sections (e.g., domain join, disk verification) have clear, in-place Linux examples rather than referring out to other docs.
  • Where possible, use cross-platform tools (like Azure CLI) as the primary example, and supplement with OS-specific tools as needed.
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: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation exhibits a moderate Windows bias. VM creation examples in both Azure CLI and PowerShell use Windows images (Win2016Datacenter) and Windows-centric parameters (adminPassword, adminUserName), with no Linux VM examples or Linux-specific configuration guidance. PowerShell examples (a Windows-only tool) are given equal prominence to Azure CLI, and in some cases, Windows patterns (like credential handling) are shown without Linux equivalents. There are no explicit Linux VM deployment examples, and the documentation does not mention Linux-specific considerations for disk attachment or sector size compatibility.
Recommendations
  • Add Linux VM deployment examples in both Azure CLI and PowerShell sections, using popular Linux images (e.g., UbuntuLTS, CentOS).
  • Include Linux-specific parameters and authentication patterns (e.g., SSH keys instead of passwords) in CLI examples.
  • Discuss any Linux-specific considerations for disk attachment, sector size, and compatibility.
  • Clarify that PowerShell is Windows-only and suggest cross-platform alternatives where appropriate.
  • Ensure Linux and Windows examples are presented with equal prominence, or alternate which is shown first.
GitHub Create Pull Request
Virtual Machines Enable on-demand disk bursting ...ain/articles/virtual-machines/disks-enable-bursting.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 detailed examples for enabling on-demand disk bursting using the Azure Portal, Azure PowerShell, Azure CLI, and ARM templates. PowerShell examples (a Windows-centric tool) are given prominent coverage and are mentioned before Azure CLI, which is more cross-platform. There is no mention of Linux-specific shell scripting or guidance for Linux/macOS users, and the use of PowerShell and references to Windows tools may create friction for non-Windows users.
Recommendations
  • Add explicit Bash shell examples for Linux/macOS users, especially for scripting with Azure CLI.
  • Reorder example sections to present Azure CLI before PowerShell, as CLI is cross-platform.
  • Clarify that Azure CLI commands work natively on Linux/macOS and provide installation links for those platforms.
  • Avoid referring to PowerShell as the primary scripting method; instead, present it as one of several options.
  • Include notes or tips for Linux/macOS users where workflows or prerequisites may differ.
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: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits notable Windows bias. PowerShell and Windows-centric tools (e.g., Register-AzProviderFeature, ConvertTo-SecureString) are used extensively, especially in the Resource Manager Template and PowerShell tabs. Windows VM images are the default in PowerShell examples, and Windows-specific configuration (e.g., -Windows flag, WindowsServer images) is shown without Linux alternatives. Feature registration and deployment steps are only shown with PowerShell, with no Bash/Azure CLI equivalent. The Azure CLI examples use Ubuntu images, but the PowerShell and ARM template examples are Windows-only. There are no Linux/macOS-specific instructions for feature registration or template deployment.
Recommendations
  • Provide Bash/Azure CLI equivalents for feature registration and template deployment steps.
  • Include Linux VM image examples in PowerShell and Resource Manager Template sections, or show both Windows and Linux options.
  • Avoid using Windows-specific flags (e.g., -Windows) without mentioning Linux alternatives.
  • Add notes or examples for macOS/Linux users where PowerShell commands are required, or reference cross-platform tools.
  • Ensure all critical steps (e.g., feature registration) have platform-neutral or cross-platform instructions.
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 ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation page presents examples and instructions for Azure Portal, Azure PowerShell, and Azure CLI. While Azure CLI is cross-platform, the ordering consistently places Azure PowerShell (a Windows-centric tool) before CLI, and there is a notable absence of explicit Linux/macOS shell examples (e.g., bash, zsh). References to disk deletion link to a Windows-specific page. The documentation does not mention Linux/macOS-specific considerations, nor does it provide parity in example ordering or tool recommendations.
Recommendations
  • Present Azure CLI examples before Azure PowerShell, as CLI is cross-platform and more accessible to Linux/macOS users.
  • Include explicit bash/zsh shell examples where variable assignment or command chaining is shown, to clarify syntax differences for Linux/macOS users.
  • Replace or supplement links to Windows-specific documentation (e.g., disk deletion) with platform-neutral or Linux/macOS equivalents.
  • Add notes clarifying that Azure CLI works on Linux/macOS and provide installation links for those platforms.
  • Where PowerShell is referenced, clarify that PowerShell Core is available cross-platform, or recommend CLI for Linux/macOS users.
GitHub Create Pull Request
Virtual Machines Enable shared disks for Azure managed disks .../main/articles/virtual-machines/disks-shared-enable.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 disk types and operations, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and in some sections (such as 'Share an existing disk' and 'Using Azure shared disks with your VMs'), PowerShell examples are listed first. There are no Linux-specific shell examples (e.g., Bash), nor are there any notes about Linux-specific considerations or parity for command-line usage. The documentation assumes PowerShell is equally available to all users, which is not the case for many Linux/macOS environments.
Recommendations
  • List Azure CLI examples before PowerShell, as CLI is cross-platform and native to Linux/macOS.
  • Add explicit Bash shell examples for common operations, especially for mounting disks to VMs.
  • Include notes or links about installing and using Azure PowerShell on Linux/macOS, or clarify when PowerShell is required.
  • Provide Linux-specific guidance for post-attach steps (e.g., mounting disks, SCSI PR usage) where relevant.
  • Ensure screenshots and portal instructions do not assume Windows conventions (e.g., file paths, UI terminology).
GitHub Create Pull Request
Virtual Machines Create an incremental snapshot ...ticles/virtual-machines/disks-incremental-snapshots.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI (cross-platform) and Azure PowerShell (Windows-centric) examples for all major operations. However, PowerShell examples are given equal prominence and detail as CLI, and in some sections, PowerShell is presented before or alongside CLI without clarifying platform relevance. There are no Linux-specific shell examples (e.g., Bash), and no mention of Linux-native tools or patterns. The documentation does not explicitly favor Windows-only tools, but the heavy inclusion of PowerShell may create friction for Linux/macOS users.
Recommendations
  • Clarify that Azure PowerShell is primarily for Windows users, and recommend CLI for Linux/macOS.
  • Present Azure CLI examples first in each section, as it is cross-platform.
  • Add explicit Bash script examples where appropriate, especially for Linux users.
  • Include notes on platform compatibility for each tool (CLI, PowerShell, Portal).
  • Consider adding troubleshooting or usage notes for Linux/macOS environments.
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 examples for Azure CLI, Azure PowerShell, Azure Portal, and Resource Manager templates, but omits explicit Linux/macOS shell examples and does not mention Linux-specific tools or workflows. PowerShell examples are given equal prominence to CLI, and Windows-centric terminology (PowerShell, Portal) is used throughout. No bash-specific or Linux-native scripting guidance is provided, and Windows/PowerShell examples are not clearly marked as Windows-only.
Recommendations
  • Add explicit bash/Linux shell examples for all CLI commands, including variable declarations and usage.
  • Clarify that PowerShell examples are for Windows users, and provide equivalent bash scripts for Linux/macOS.
  • Mention Linux-native tools (e.g., curl, jq) where relevant for API or data inspection.
  • Ensure that CLI examples use cross-platform syntax and note any OS-specific differences.
  • Add a section or note on how Linux/macOS users can perform snapshot operations, including troubleshooting tips for those platforms.
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 exhibits a moderate Windows bias. Windows clustering tools (WSFC) and workloads are described first and in greater detail, with specific references to Windows features (CSV, Scale-Out File Server, RDS UPD) and links to Windows-centric guides. Linux equivalents are mentioned, but with less detail and fewer concrete examples. Windows sample workloads are listed before Linux, and the examples section provides more detailed Windows scenarios (including CSV/non-CSV) versus a single Linux example. No command-line examples (e.g., PowerShell or Bash) are present, but Windows tools and patterns are referenced more prominently.
Recommendations
  • Provide Linux sample workloads with equal detail and specificity, including links to step-by-step guides for setting up Pacemaker/Corosync clusters with Azure shared disks.
  • Add concrete Linux configuration examples, such as using sg_persist or fence_scsi, and reference Linux-specific clustering patterns (e.g., OCFS2/GFS2 setup).
  • Present Windows and Linux sample workloads in parallel, or alternate their order to avoid Windows-first bias.
  • Include Linux/macOS command-line examples for disk management and reservation flows, not just Windows tools.
  • Reference Linux documentation and templates as prominently as Windows equivalents.
GitHub Create Pull Request
Virtual Machines Ephemeral OS disks ...b/main/articles/virtual-machines/ephemeral-os-disks.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. Windows-specific details (such as page file placement and image sizing) are often mentioned before Linux equivalents. PowerShell is referenced before CLI in the customer-managed key section, and some links point to Windows/PowerShell docs first. There are more detailed examples for Windows (e.g., cache sizing), while Linux examples are less emphasized or absent. The documentation does mention Linux support and provides some Linux-specific information, but parity in examples and tool references is lacking.
Recommendations
  • Provide Linux examples alongside Windows examples, especially in sections discussing image sizing and disk placement.
  • When referencing tools for configuration (e.g., enabling customer-managed keys), mention Azure CLI and PowerShell together, or list CLI first for neutrality.
  • Ensure that Linux-specific details (such as swap file placement, common distributions, or image sizes) are given equal prominence.
  • Add explicit Linux walkthroughs or code snippets where only Windows/PowerShell is currently referenced.
  • Review all links to ensure Linux and Windows documentation are equally accessible.
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 is generally cross-platform, focusing on Azure Storage Explorer, which is available for Windows, Linux, and macOS. However, the 'Next steps' section exclusively links to Windows VM guides, and there are no Linux-specific follow-up links or examples. There is also no mention of Linux-specific considerations or parity in workflows, which may leave Linux users without clear guidance for subsequent steps.
Recommendations
  • Add Linux-specific links in the 'Next steps' section, such as guides for creating VMs from VHDs or attaching managed disks to Linux VMs.
  • Ensure parity by including references to both Windows and Linux workflows wherever relevant, especially in follow-up resources.
  • Explicitly mention that Azure Storage Explorer is available on Linux/macOS and provide installation instructions or links for those platforms.
  • If there are any platform-specific behaviors or requirements (e.g., file paths, permissions), document these for Linux/macOS users.
GitHub Create Pull Request
Virtual Machines Azure Backup for SQL Server running in Azure VM ...extensions/backup-azure-sql-server-running-azure-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 exhibits a notable Windows bias. The extension discussed is named AzureBackupWindowsWorkload, with no mention of a Linux equivalent or support for SQL Server on Linux VMs. All deployment and registration instructions use PowerShell and Windows-centric tooling, with no CLI, Bash, or Linux-native examples. The documentation does not clarify whether Linux VMs or SQL Server on Linux are supported, nor does it provide guidance for non-Windows environments.
Recommendations
  • Clarify whether Azure Backup supports SQL Server running on Linux VMs, and if so, document the process and any required extensions.
  • Provide Azure CLI, Bash, or REST API examples for registering and managing backups, alongside PowerShell.
  • If Linux is not supported, explicitly state this in the prerequisites or introduction.
  • If Linux is supported, add equivalent instructions and examples for Linux users, including any differences in extension names or deployment steps.
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 page demonstrates a Windows bias by referencing Windows tools and patterns first, such as PowerShell scripts and the BGInfo extension. The sample deployment scripts are described as 'PowerShell and Azure CLI scripts', listing PowerShell first and not mentioning Bash or Linux shell scripts. The supported extensions list places Windows extensions before Linux equivalents in several cases. There are no explicit Linux/macOS command-line examples, and the documentation does not provide parity for Linux users in terms of deployment or scripting guidance.
Recommendations
  • List Azure CLI and Bash examples before or alongside PowerShell, and clarify cross-platform usage.
  • Explicitly mention Linux/macOS compatibility for export and deployment steps.
  • Provide sample Bash or shell scripts for template deployment, not just PowerShell.
  • Ensure supported extensions are listed in a neutral or alphabetical order, not Windows-first.
  • Add a section or note for Linux/macOS users on how to perform the export and deployment steps.
  • Reference Linux tools and patterns where relevant, such as using Azure CLI in Bash.
GitHub Create Pull Request
Virtual Machines Use Azure Policy to restrict VM extension installation (Windows) ...al-machines/extensions/extensions-rmpolicy-howto-ps.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 is heavily focused on Windows environments, using Azure PowerShell and Windows-specific paths and examples throughout. There are no Linux or Bash examples, and all instructions assume the user is working with Windows VMs and PowerShell, both in Cloud Shell and locally. The page title and customer intent reinforce a Windows-centric approach, and there is no mention of Linux VM extension management or equivalent CLI commands.
Recommendations
  • Add equivalent examples for Linux VMs, including how to restrict extensions on Linux VMs using Azure Policy.
  • Provide Azure CLI (az) and Bash examples alongside PowerShell, especially for policy creation, assignment, and testing.
  • Clarify which steps are universal and which are Windows-specific; add notes or sections for Linux/macOS users.
  • Include Linux file path examples and instructions for editing files in Linux environments.
  • Update the page title and customer intent to reflect cross-platform applicability if the policy applies to both Windows and Linux VMs.
GitHub Create Pull Request
Virtual Machines Enable InfiniBand on HPC VMs - Azure Virtual Machines | Microsoft Docs ...icles/virtual-machines/extensions/enable-infiniband.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 instructions for enabling InfiniBand, but there is a notable Windows bias in several areas. The use of Azure PowerShell cmdlets is mentioned as the primary method for adding VM extensions, with no equivalent CLI or Linux-native tooling referenced. Windows-specific tools and extensions are described in greater detail, and the Windows installation section, while brief, is present. In the VM extension section, Windows is discussed first and at greater length than Linux. However, Linux examples are present and detailed, especially for manual driver installation.
Recommendations
  • Include Azure CLI examples for adding VM extensions, especially for Linux users.
  • Mention Linux-native tools (e.g., cloud-init, shell scripts) for extension management alongside PowerShell.
  • Balance the order and detail of Windows and Linux instructions, presenting Linux examples first or in parallel.
  • Provide more detailed Windows installation steps, or link to equivalent Linux installation guides for parity.
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
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation is generally focused on Linux VM extensions, but there is a consistent pattern of presenting both Azure CLI and Azure PowerShell examples side-by-side, with PowerShell (a Windows-centric tool) given equal prominence. In some cases, links and references point to Windows documentation first (e.g., ARM template reference). There are no explicit Linux shell or native Linux tool examples beyond Azure CLI, and PowerShell is not natively available on most Linux distributions. The documentation does not provide guidance for Linux-native workflows outside Azure CLI and ARM templates.
Recommendations
  • Prioritize Azure CLI examples, as it is cross-platform and more commonly used on Linux.
  • Provide native Bash or shell script examples where possible, especially for troubleshooting and automation tasks.
  • Avoid referencing Windows documentation (such as ARM template docs under Windows) when describing Linux workflows; link to Linux-specific docs instead.
  • Clarify that PowerShell is optional and not required for Linux users, and provide alternatives.
  • Add troubleshooting steps using native Linux tools (e.g., journalctl, systemctl) in addition to Azure CLI.
  • Ensure that all example outputs and screenshots are from Linux environments.
GitHub Create Pull Request
Virtual Machines Salt Minion for Linux or Windows Azure VMs ...in/articles/virtual-machines/extensions/salt-minion.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ linux_first ⚠ī¸ linux_examples_only ⚠ī¸ missing_windows_example
Summary
The documentation page demonstrates a bias towards Linux by providing detailed examples for Linux VM extension installation using ARM templates and Terraform, while omitting equivalent examples for Windows. The Azure CLI section does mention both Linux and Windows, but the ARM template and Terraform sections only show Linux usage. There is no evidence of Windows tools or PowerShell-specific instructions, and Linux is consistently presented first.
Recommendations
  • Add ARM template examples for installing the Salt Minion extension on Windows VMs (using 'salt-minion.windows').
  • Include Terraform resource examples for Windows VM extensions, mirroring the Linux example.
  • Ensure both Linux and Windows are equally represented in all code samples and instructions.
  • Consider alternating the order of examples or grouping them by OS for parity.
GitHub Create Pull Request
Virtual Machines Troubleshooting Windows VM extension failures ...n/articles/virtual-machines/extensions/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 is heavily focused on Windows VM extension troubleshooting, with most examples, error messages, and solutions tailored to Windows environments. PowerShell commands and Windows-specific tools (Task Manager, Control Panel, certmgr.msc) are used exclusively or presented first, while Linux troubleshooting steps and examples are minimal or absent. Linux users may find it difficult to follow some procedures due to lack of equivalent instructions.
Recommendations
  • Add Linux-specific troubleshooting examples and commands (e.g., using Bash, systemctl, journalctl, etc.) alongside PowerShell examples.
  • Present Azure CLI commands before or alongside PowerShell to ensure cross-platform parity.
  • Include Linux error messages and log file locations with sample outputs.
  • Provide Linux equivalents for Windows tools (e.g., how to restart the Linux Guest Agent, check environment variables, manage certificates).
  • Clearly separate Windows and Linux instructions, or provide parallel sections for each OS.
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: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides both PowerShell and Bash examples for running attestation scripts, but the PowerShell example is presented first and is more detailed. Monitoring attestation status is only described using a PowerShell script, with no equivalent Bash or Linux-native example. The documentation references PowerShell scripts and tools more frequently, and some steps (like monitoring) lack Linux-specific guidance.
Recommendations
  • Provide Bash or Linux-native examples for monitoring attestation status, similar to the PowerShell Monitor-Validation.ps1 script.
  • Present Bash and PowerShell examples side-by-side or alternate which is shown first to avoid implicit prioritization.
  • Clarify that all scripts and tools are cross-platform where applicable, and explicitly mention Linux/macOS compatibility for each step.
  • If a Bash/Linux script for monitoring does not exist, provide instructions for using the HTTP endpoint from Bash (e.g., using curl or httpie) to check status.
GitHub Create Pull Request
Virtual Machines Project Flash - Advancing Azure Virtual Machine availability monitoring .../blob/main/articles/virtual-machines/flash-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 page shows a subtle Windows bias by referencing Windows-specific scheduled events documentation and linking to activity log tabs that default to PowerShell (a Windows-centric tool). There is no explicit mention of Linux or macOS equivalents, nor are Linux-specific examples or guidance provided. The scheduled events link points to a Windows documentation page, and activity log examples default to PowerShell, with no clear parity for Linux users.
Recommendations
  • Include links to both Windows and Linux scheduled events documentation, or clarify applicability to all platforms.
  • Provide Linux/macOS command-line examples (e.g., Azure CLI, Bash) alongside PowerShell examples for activity logs and other monitoring tasks.
  • Explicitly mention platform support for each monitoring solution and clarify any differences in implementation or usage between Windows and Linux VMs.
  • Ensure that documentation navigation (tabs, links) does not default to Windows tools, but offers equal visibility for Linux/macOS options.
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 exhibits a moderate Windows bias. Windows examples and PowerShell commands are presented before Linux equivalents, and Windows-centric tools (PowerShell, WindowsServer SKUs) are referenced more frequently and in greater detail. Linux instructions are present but often less detailed or appear after Windows examples. Some advanced tasks (e.g., bringing a .vhd from on-premises) are only shown with Windows PowerShell, with no Linux CLI or Bash equivalent.
Recommendations
  • Provide Linux/Bash/Azure CLI examples alongside PowerShell for all major workflows, especially for importing .vhd files and setting VM properties.
  • Ensure Linux images and instructions are presented with equal prominence and detail as Windows examples.
  • Where PowerShell is used, offer equivalent Azure CLI or Bash commands for Linux/macOS users.
  • Explicitly mention Linux-specific considerations or differences in advanced scenarios (e.g., disk import, managed disk creation).
  • Balance the order of examples so Linux and Windows are alternated or grouped, rather than consistently leading with Windows.
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 exhibits a moderate Windows bias. The PowerShell method is presented first and in greatest detail, with multiple example scripts and cmdlet explanations. Windows-specific tooling (Chocolatey, cmd.exe, PowerShell) is referenced exclusively for installing armclient, with no mention of Linux/macOS alternatives. While Azure CLI and REST API methods are included, the CLI section is brief and the REST API instructions assume Windows environments for installation. There are no Linux/macOS-specific command-line examples or installation instructions for armclient.
Recommendations
  • Provide Linux/macOS installation instructions for armclient (e.g., via dotnet, npm, or manual download).
  • Include Bash shell examples for Azure CLI usage, showing Linux/macOS command syntax.
  • Present Azure CLI examples before PowerShell, or in parallel, to avoid Windows-first ordering.
  • Clarify that PowerShell cmdlets can be run on Linux/macOS via PowerShell Core, if applicable.
  • Add notes or examples for Linux disk/volume managers (LVM, MDADM) in scripting sections.
  • Ensure all tooling references (e.g., Chocolatey) have cross-platform alternatives or links.
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 and references are presented first and in greater detail, with explicit mention of Windows-specific tools and APIs (e.g., 'Cryptography API: Next Generation'). Linux parity is present via Azure CLI examples, but PowerShell (a Windows-centric tool) is prioritized and referenced more often, and Windows terminology/tools are mentioned before Linux equivalents.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples to prioritize cross-platform usage.
  • Include explicit notes or examples for Linux/macOS users, such as bash scripts or command-line patterns.
  • Reduce references to Windows-specific APIs (e.g., CNG) or provide equivalent Linux cryptography documentation links.
  • Clarify that Azure CLI is fully supported on Linux/macOS and highlight any platform-specific considerations.
  • Ensure that prerequisite and limitation sections mention both PowerShell and CLI options equally.
GitHub Create Pull Request
Virtual Machines Create an image definition and image version ...s/blob/main/articles/virtual-machines/image-version.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 parity between Windows and Linux in most CLI and REST examples, but PowerShell examples are exclusively Windows-focused, and Windows terminology (e.g., Sysprep, PowerShell cmdlets) is often mentioned before or more prominently than Linux equivalents. The PowerShell section uses Windows as the default, with Linux only mentioned as an alternative. Windows-specific tools and patterns (Sysprep, PowerShell) are referenced without equivalent Linux detail, and Windows is sometimes presented first in guidance.
Recommendations
  • Add Linux-focused PowerShell examples (e.g., using -OsType Linux in PowerShell commands).
  • Ensure Linux terminology (e.g., waagent -deprovision) is given equal prominence and order as Windows (Sysprep) in all sections.
  • Where Windows tools or patterns are referenced, provide direct Linux equivalents and examples side-by-side.
  • Consider alternating the order of Windows and Linux references to avoid 'Windows first' bias.
  • Explicitly mention cross-platform compatibility for PowerShell commands, or clarify when commands are Windows-only.
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 ⚠ī¸ windows_specific_note
Summary
The documentation provides parity between Azure Portal, CLI, PowerShell, and REST API for most VM hibernation tasks. However, PowerShell (a Windows-centric tool) is given equal prominence as Azure CLI, and some examples (e.g., PowerShell output) are more detailed. There is a Windows-specific note about page file location, but no equivalent Linux-specific guidance. The PowerShell example for image definition uses Windows as the OS type, while the CLI example uses Linux, but there is no explicit parity or explanation for Linux-specific requirements. The documentation does not mention Linux/macOS shell scripting or tools (e.g., Bash), nor does it provide troubleshooting or configuration notes for Linux guests.
Recommendations
  • Add Linux-specific notes where Windows-specific configuration is discussed (e.g., page file location for hibernation).
  • Provide Bash or shell scripting examples alongside PowerShell for users on Linux/macOS.
  • Ensure that CLI and PowerShell examples are equally detailed, and clarify any OS-specific differences in output or behavior.
  • Include troubleshooting or configuration steps for Linux guests, similar to the Windows note about page file location.
  • Explicitly state OS support and requirements for both Windows and Linux in relevant sections.
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 a Windows-specific template authoring guide and links to a Windows-focused resource, without mentioning or providing equivalent Linux guidance. This creates a subtle bias toward Windows, as Linux users may not find relevant information for their platform.
Recommendations
  • Include links to Linux-specific template authoring documentation alongside Windows resources.
  • Explicitly mention that extensions and troubleshooting steps may differ for Linux VMs and provide guidance or examples for Linux scenarios.
  • Ensure that troubleshooting advice and examples cover both Windows and Linux VM extensions.
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 for all examples and instructions, with no mention of Azure CLI, Bash, or Linux/macOS workflows. All commands and setup steps are tailored to PowerShell, which is traditionally a Windows-centric tool, and there is no guidance for users on Linux or macOS platforms. This creates friction for non-Windows users and may prevent them from easily following the documentation.
Recommendations
  • Provide equivalent Azure CLI examples for each PowerShell command, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Add a section describing platform requirements and alternatives, clarifying that PowerShell Core is available cross-platform but Azure CLI may be preferable for Linux/macOS users.
  • Reorder or parallelize examples so that both PowerShell and CLI/Bash instructions are presented side-by-side or in separate tabs.
  • Explicitly mention installation and authentication steps for Azure CLI, not just PowerShell.
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 ⚠ī¸ windows_tools
Summary
The documentation lists Azure PowerShell and the Azure Portal (which is Windows-centric) as primary tools for disk expansion, with Azure CLI mentioned but not emphasized. Windows rescan instructions and links are provided before Linux equivalents, and Windows-specific tools (like devcon) are referenced. Linux instructions are present but less detailed and appear after Windows instructions.
Recommendations
  • Provide Linux examples and instructions with equal detail and prominence as Windows.
  • List cross-platform tools (Azure CLI) first, and clarify their parity for both OSes.
  • Include explicit Linux command-line examples (e.g., using 'lsblk', 'partprobe', or 'udevadm') for rescanning disks.
  • Avoid referencing Windows-only tools (like devcon) without Linux equivalents.
  • Ensure that troubleshooting steps and links are equally comprehensive for Linux users.
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, linking exclusively to Windows-specific resources. There is no mention of Linux clustering solutions (e.g., Pacemaker, Corosync), nor are Linux-specific limitations or examples provided. This creates the impression that shared disk scenarios are primarily or only relevant for Windows environments.
Recommendations
  • Include references to Linux clustering solutions such as Pacemaker or Corosync, and discuss their compatibility or limitations with Azure shared disks.
  • Provide links to Linux documentation or guides for setting up shared disks in Linux-based clusters.
  • Clarify whether the listed limitations apply equally to Linux and Windows, or specify any differences.
  • Add examples or scenarios for Linux users to ensure parity.
GitHub Create Pull Request
Virtual Machines Install VM Watch ...lob/main/articles/virtual-machines/install-vm-watch.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 installing VM Watch, but the PowerShell examples are extensive and detailed, while Linux-specific shell examples (e.g., Bash) are absent. Screenshots and references to Windows installations are consistently presented before Linux equivalents. PowerShell, a Windows-centric tool, is given equal or greater prominence than CLI, and no Linux-native scripting or automation patterns are discussed.
Recommendations
  • Add Bash or shell script examples for Linux users alongside PowerShell, especially for automation tasks.
  • Present Linux and Windows screenshots in alternating order, or group them together to avoid Windows-first bias.
  • Explicitly mention that PowerShell Core is cross-platform, or clarify when examples are Windows-only.
  • Include troubleshooting or validation steps specific to Linux environments (e.g., using SSH, checking extension status via Linux commands).
  • Highlight Linux-specific considerations in prerequisites and installation steps, such as package requirements or permissions.
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 several sections show Windows bias. Windows-specific tools (PowerShell DSC) are highlighted, and in some cases, only Windows examples or links are provided (e.g., Chef and Puppet). Windows examples are sometimes listed before Linux equivalents, and some sections provide more detailed Windows instructions or links than for Linux.
Recommendations
  • Ensure every tool section provides both Linux and Windows usage examples or links, especially for Chef and Puppet.
  • Where possible, present Linux and Windows examples side-by-side or in parallel, rather than listing Windows first.
  • Expand Chef and Puppet sections to include Linux installation/configuration links and examples.
  • Balance the coverage of PowerShell DSC with equivalent Linux configuration management tools (e.g., more emphasis on cloud-init, Ansible, etc.).
  • Review all 'Learn how to' lists to ensure parity in depth and number of examples for both platforms.
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 demonstrates a notable Windows bias by exclusively referencing Hyper-V (a Windows virtualization tool) for VHD creation and management, providing links to Windows-centric instructions, and using Hyper-V Manager for VM operations. There are no examples or guidance for equivalent Linux virtualization tools (such as KVM, QEMU, or VirtualBox) for creating, managing, or converting VHDs, nor are Linux-native commands or workflows shown for these tasks. Windows tools and patterns are mentioned first and exclusively throughout the critical steps.
Recommendations
  • Add equivalent instructions and examples for creating and managing VHDs using Linux-native virtualization tools (e.g., KVM, QEMU, VirtualBox).
  • Include Linux command-line examples for converting disk formats (e.g., using qemu-img to convert raw disks to fixed VHD format).
  • Provide parity in VM management steps, such as how to shut down or deprovision a VM using Linux tools.
  • Reference Linux documentation and resources alongside or before Windows/Hyper-V links.
  • Explicitly state that Hyper-V is optional and list alternative Linux-based workflows.
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 ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias primarily in the VHD creation and conversion steps. It exclusively recommends Hyper-V (a Windows virtualization tool) and provides only PowerShell examples for converting VHDX to VHD, with no mention of Linux/macOS alternatives (e.g., qemu-img, VirtualBox, or VBoxManage). The Windows/Hyper-V approach is presented first and as the default, potentially creating friction for Linux/macOS users who may not have access to Hyper-V or PowerShell.
Recommendations
  • Add instructions and examples for creating and converting VHD files using Linux/macOS tools such as qemu-img and VBoxManage.
  • Mention cross-platform virtualization solutions (e.g., VirtualBox, KVM, qemu) alongside Hyper-V, and provide links to their documentation.
  • Present Linux/macOS alternatives before or alongside Windows-specific tools to avoid implying Windows is required.
  • Include sample commands for VHD conversion on Linux/macOS (e.g., qemu-img convert -f raw -O vpc disk.img disk.vhd).
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 both Azure CLI and PowerShell examples for Linux VM disk encryption, but PowerShell (a Windows-centric tool) is heavily emphasized, with more detailed scripts and explanations. Some sections (e.g., pre-encrypted VHDs) only show PowerShell examples, and references to using PowerShell sessions are frequent. The use of Windows terminology (e.g., BitLocker, PowerShell cmdlets) and the lack of native Linux shell (bash) or platform-agnostic examples creates friction for Linux/macOS users. In some places, PowerShell is mentioned before CLI, and there are no bash or Linux-native command examples for tasks like mounting disks, formatting, or interacting with Azure APIs outside of CLI/PowerShell.
Recommendations
  • Add bash and Linux-native shell examples for all major steps, especially for disk operations and Azure API interactions.
  • Provide parity in detail between Azure CLI and PowerShell sections, ensuring CLI examples are as comprehensive as PowerShell ones.
  • Avoid assuming users have PowerShell available; clarify when PowerShell is required and offer alternatives for Linux/macOS users.
  • Where possible, use platform-agnostic language and tools (e.g., Azure CLI, REST API) before Windows-specific tools.
  • Explicitly state when a step or tool is Windows-only, and offer Linux/macOS alternatives.
  • Add a section on using Azure REST API or SDKs from Linux for advanced scenarios.
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 Linux VMs, contains notable Windows bias. Critical configuration details (TLS registry changes, BitLocker Group Policy) are provided only for Windows, with no Linux equivalents or guidance. Windows tools (PowerShell scripts) are mentioned explicitly, while Linux CLI scripts are listed after. There is no discussion of Linux-specific encryption tooling or troubleshooting.
Recommendations
  • Add Linux-specific configuration guidance for TLS and encryption prerequisites, or clarify if these steps are not required for Linux.
  • Provide Linux equivalents for registry changes, or explicitly state that these steps are Windows-only and not applicable to Linux.
  • Include Linux-first examples and troubleshooting steps, especially for common issues encountered during disk encryption.
  • List Linux CLI scripts before PowerShell scripts, or group them together with clear OS applicability.
  • Expand on Linux encryption mechanisms (e.g., dm-crypt, cryptsetup) and how they interact with Azure Disk Encryption.
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 demonstrates a moderate Windows bias by referencing Hyper-V (a Windows-only virtualization solution) as the primary example for creating VHDs, linking to Windows-specific instructions, and providing PowerShell/Hyper-V tools for VHD conversion without mentioning Linux alternatives. There are no examples or guidance for Linux-native tools (e.g., qemu-img, VirtualBox, KVM) for creating or converting VHDs, which may create friction for Linux/macOS users.
Recommendations
  • Add instructions and examples for creating and converting VHDs using Linux-native tools such as qemu-img, VirtualBox, or KVM.
  • Provide links to Linux documentation for virtualization and disk conversion processes.
  • Present Linux and Windows options side-by-side, or list Linux alternatives before or alongside Windows tools.
  • Clarify that Hyper-V is just one option and explicitly mention cross-platform alternatives.
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 certificate management and disk encryption workflows, which are inherently Windows-centric. Many advanced scenarios (KEK, certificate-based authentication) are only shown with PowerShell, and some steps (like certificate handling) use Windows file paths and tools. While Azure CLI examples are present for basic operations, advanced examples and automation scripts are PowerShell-only. There is little to no mention of Linux-native tooling, shell scripting, or cross-platform certificate management, and certificate-based authentication is explicitly stated as unsupported on Linux VMs.
Recommendations
  • Provide equivalent Bash/shell scripts for advanced scenarios, especially for KEK setup and disk encryption extension management.
  • Include Linux-native certificate management instructions (e.g., using OpenSSL, PEM files, and Linux file paths) for certificate-based workflows.
  • Clarify which steps are cross-platform and which are Windows-only, and offer alternative approaches for Linux users where possible.
  • Reorder examples so that Azure CLI (cross-platform) instructions are presented before PowerShell, or at least in parallel.
  • Explicitly state limitations for Linux users earlier in the document, and link to Linux-specific guidance or workarounds.
GitHub Create Pull Request
Virtual Machines Expand Virtual Hard Disks on a Linux VM ...b/main/articles/virtual-machines/linux/expand-disks.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation is strongly focused on Linux, with all operational examples using Linux commands and tools (bash, growpart, xfs_growfs, etc.). However, there is a single section at the end that provides a PowerShell script for determining classic VM SKU support for expanding disks without downtime. This script is Windows/PowerShell-specific and lacks a Linux CLI or Bash equivalent, which could hinder Linux users needing this information.
Recommendations
  • Provide an equivalent Azure CLI or Bash script for Linux users to determine classic VM SKU support for expanding disks without downtime.
  • If PowerShell is required for some Azure queries, clarify that PowerShell Core can be installed on Linux/macOS and provide installation guidance.
  • Ensure that any critical information available only via PowerShell is also accessible via Azure CLI or REST API, with examples for Linux/macOS 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
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples and scripts, but PowerShell is mentioned frequently and is given equal prominence to CLI, despite the Linux focus. PowerShell scripts and modules are referenced alongside CLI scripts, and PowerShell connection instructions are shown immediately after CLI, which may create friction for Linux users who are less likely to use PowerShell. There is also a slight tendency to mention Windows-centric tools (PowerShell) and scripts, rather than focusing solely on Linux-native approaches.
Recommendations
  • Prioritize Azure CLI examples and scripts in the main flow, as CLI is native to Linux.
  • Move PowerShell references to a dedicated section for Windows users or as an alternative, rather than presenting them alongside CLI for Linux-focused documentation.
  • Clarify that PowerShell is optional and primarily relevant for Windows users.
  • Ensure that all automation and scripting examples are available in Bash/CLI and clearly marked as Linux-compatible.
  • Highlight Linux-native installation and usage patterns before mentioning PowerShell.
GitHub Create Pull Request
Virtual Machines Azure Disk Encryption scenarios on Linux VMs ...ticles/virtual-machines/linux/disk-encryption-linux.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 Azure CLI and PowerShell examples for all major tasks, but PowerShell (a Windows-centric tool) is frequently mentioned first, and its cmdlets are referenced in critical workflow descriptions. There is a notable emphasis on PowerShell usage, including variable initialization and script blocks, which may be less familiar or accessible to Linux/macOS users. Additionally, references to 'PowerShell session' and the use of PowerShell-specific terminology (cmdlets, parameters) reinforce a Windows-centric approach, even though the content is for Linux VMs.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and native to Linux/macOS.
  • Minimize PowerShell-specific terminology in general workflow descriptions; use neutral or CLI-focused language.
  • Clarify that Azure CLI is the recommended tool for Linux/macOS users and highlight its parity with PowerShell.
  • Where variable initialization or scripting is shown, provide equivalent bash shell script examples alongside PowerShell.
  • Review backup and snapshot instructions to ensure CLI and portal methods are equally emphasized, not PowerShell-first.
GitHub Create Pull Request
Virtual Machines Enable Azure Disk Encryption for Linux VMs ...les/virtual-machines/linux/disk-encryption-overview.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
While the documentation is focused on Linux VMs and provides Linux-centric technical details and examples, it repeatedly references Azure PowerShell as a primary tool for managing disk encryption, including quickstart links and scripts. PowerShell is traditionally a Windows-first tool, and its prominence may create friction for Linux/macOS users who prefer native Linux tools or Azure CLI. Additionally, PowerShell is mentioned before Azure CLI in some places, and the terminology table includes 'PowerShell cmdlets' as a core concept, reinforcing the Windows-centric tooling bias.
Recommendations
  • Prioritize Azure CLI examples and links before PowerShell, as CLI is natively supported on Linux/macOS.
  • Clarify that PowerShell is cross-platform, but emphasize CLI as the default for Linux workflows.
  • Expand terminology to include Bash scripting and Linux-native tools relevant to disk encryption.
  • Ensure all scripts and automation examples are available in Bash/CLI as well as PowerShell.
  • Add explicit guidance for Linux/macOS users on installing and using Azure CLI.
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, but when discussing how to check encryption status and disable disk encryption, it consistently presents Azure PowerShell (Windows-centric) commands first and in detail, with Linux-friendly Azure CLI commands mentioned only briefly and after PowerShell. All example output is shown using PowerShell, and no CLI output or Linux-native tooling is demonstrated.
Recommendations
  • Provide Azure CLI examples and output alongside or before PowerShell examples, as CLI is cross-platform and preferred by many Linux users.
  • Explicitly mention that Azure CLI can be used on Linux/macOS and provide equivalent commands for all PowerShell instructions.
  • Include sample output for Azure CLI commands to match the detail given for PowerShell.
  • Where possible, reference Linux-native troubleshooting tools (e.g., shell commands, log locations) relevant to disk encryption status.
  • Review the order of presentation so Linux-first or CLI-first examples are shown in documentation targeting Linux VMs.
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, but PowerShell (a Windows-centric tool) is introduced before Azure CLI, despite the Linux focus. The PowerShell section is more detailed and extensive, with multiple scenarios and verbose output formatting, while Azure CLI examples are somewhat less emphasized. No Linux-native tools (other than basic OS-level checks) are mentioned for interacting with Azure resources, and PowerShell is not natively available on most Linux distributions. The OS-level section uses Linux commands appropriately.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and native to Linux.
  • Ensure Azure CLI coverage matches PowerShell in detail and scenarios.
  • Clarify that PowerShell is optional and not required for Linux users.
  • Consider removing or de-emphasizing PowerShell for Linux-focused documentation, or add a note about its installation on Linux.
  • Add more Linux-native tooling or scripting examples for interacting with Azure resources, if available.
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 first or exclusively, especially in code examples and customization sections. Windows scenarios (such as Windows Update and PowerShell scripts) are described in detail, while Linux equivalents are sometimes less detailed or presented after Windows. Some sections (e.g., Windows Update task) are Windows-only, and troubleshooting steps reference Windows paths and behaviors. However, Linux support is present, and most critical steps include Linux examples.
Recommendations
  • Ensure Linux examples are presented alongside or before Windows examples, especially in code blocks.
  • Expand Linux-specific guidance, such as handling build artifacts and customization scripts, to match the detail given for Windows.
  • Avoid Windows-first ordering in lists and instructions; alternate or group by OS.
  • Include troubleshooting steps and tips for Linux users, not just Windows.
  • Clarify when features or limitations apply only to Windows or Linux, and provide parity where possible.
GitHub Create Pull Request
Virtual Machines Create an Azure Image Builder Bicep file or ARM template JSON template .../articles/virtual-machines/linux/image-builder-json.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 Windows and Linux coverage, but there is a notable Windows bias: Windows-specific tools (PowerShell, WindowsUpdate, WindowsRestart) are described in detail, often with examples and troubleshooting guidance, while Linux equivalents are less emphasized or missing (e.g., no LinuxRestart customizer). PowerShell commands and references to Windows tools (Get-FileHash, Sysprep) appear before Linux alternatives (sha256sum, waagent), and some sections (such as validation and generalization) provide more comprehensive Windows examples. The documentation also introduces Windows-only features (WindowsRestart, WindowsUpdate) without Linux counterparts.
Recommendations
  • Add Linux-first examples in sections where Windows examples are currently shown first, especially for validation and generalization.
  • Provide parity in troubleshooting and guidance for Linux users (e.g., more details on waagent, Linux image generalization issues, and troubleshooting).
  • Explicitly state when a feature is Windows-only and suggest Linux alternatives or workarounds (e.g., for restart customizer).
  • Include Linux CLI commands and tools (e.g., sha256sum, wget/curl) alongside or before Windows tools.
  • Balance the order of presentation so Linux and Windows are treated equally in all example blocks and explanations.
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 exhibits a moderate Windows bias: Windows terminology (RDP, WinRM) is frequently mentioned, sometimes before or alongside Linux equivalents (SSH). Several links and instructions reference Windows-specific documentation or tools first, and Linux-specific instructions/examples are less detailed or appear later. The password reset instructions reference the Azure portal's 'Reset Password' blade, which is more commonly used for Windows VMs. The Azure Bastion section refers to connecting to a Windows VM using SSH or RDP, but does not provide explicit Linux SSH examples. The Serial Console documentation link points to a Windows-focused page. Linux connection methods are mentioned, but not as thoroughly or prominently.
Recommendations
  • Provide explicit Linux SSH connection examples and links alongside Windows RDP/WinRM instructions.
  • Ensure documentation links for Serial Console and Bastion include both Linux and Windows guides, or point to OS-neutral pages.
  • Clarify that the 'Reset Password' blade works for both Linux and Windows, and provide Linux-specific instructions if there are differences.
  • Present Linux and Windows options in parallel, rather than listing Windows tools or documentation first.
  • Add troubleshooting notes or caveats specific to Linux VMs where relevant (e.g., SSH key management, password reset differences).
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 a Windows bias in several ways. Hyper-V (a Windows virtualization tool) is mentioned as the primary example for creating VHDs, with instructions and links provided only for Hyper-V. Steps for interacting with the VM (such as shutting down and connecting) are described exclusively using Hyper-V Manager, with no mention of Linux-native virtualization tools (like KVM, QEMU, or VirtualBox). There are no examples or guidance for Linux users on how to create, manage, or convert VHDs using Linux tools, nor are Linux alternatives mentioned alongside Windows-centric instructions.
Recommendations
  • Add instructions and examples for creating and managing VHDs using Linux-native tools such as KVM, QEMU, or VirtualBox.
  • Provide guidance on converting disk formats to fixed VHD using Linux command-line tools (e.g., qemu-img).
  • Include steps for shutting down and managing VMs using Linux virtualization platforms.
  • Mention Linux alternatives alongside Hyper-V throughout the documentation, ensuring parity in tool recommendations and instructions.
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: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
While the documentation is focused on Linux VMs and provides extensive Azure CLI examples (which are cross-platform), the PowerShell section is much longer, more detailed, and introduces Windows-centric tools and terminology (e.g., New-AzStorageBlobSASToken, PowerShell script examples, references to Windows VM behaviors). Some examples and notes reference Windows-specific patterns before Linux equivalents, and certain explanations (such as parameter passing) discuss Windows first. REST and ARM template examples sometimes use PowerShell scripts (.ps1) as the default, even in Linux contexts.
Recommendations
  • Balance the depth of Azure CLI and PowerShell sections, ensuring Linux users have equally detailed CLI examples for all advanced scenarios (e.g., output streaming, parameter passing, long-running scripts).
  • Replace or supplement PowerShell-specific notes and examples with Bash or shell script equivalents, especially in REST and ARM template sections.
  • When discussing parameter passing, present Linux patterns first or side-by-side with Windows patterns.
  • Avoid referencing Windows-only tools (e.g., New-AzStorageBlobSASToken) without Linux alternatives or CLI equivalents.
  • Ensure all examples referencing scripts use .sh files for Linux contexts, not .ps1.
  • Add explicit Bash/shell script examples for advanced scenarios currently only shown in PowerShell.
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 presents instructions for preparing a Red Hat Enterprise Linux VHD for Azure, covering multiple hypervisors (Hyper-V, KVM, VMware, Kickstart). However, there is a notable Windows bias: Hyper-V (a Windows-only hypervisor) is consistently presented first in all tabbed sections and referenced in the prerequisites and workflow steps. Windows-centric tools and links (such as Hyper-V Manager and PowerShell cmdlets like convert-vhd) are mentioned before Linux alternatives (like qemu-img). The prerequisites and initial guidance direct users to Windows documentation and tools, even though Linux-native workflows are fully supported and described later in the page.
Recommendations
  • Reorder tabbed sections so that Linux-native hypervisors (KVM, VMware, Kickstart) are presented before or alongside Hyper-V, especially since the target audience is preparing Linux VMs.
  • In the prerequisites, mention both Windows (Hyper-V) and Linux (KVM, qemu-img) tools and workflows equally, with direct links to Linux documentation and resources.
  • Where disk conversion is discussed, present qemu-img (Linux) and convert-vhd (Windows/PowerShell) side by side, rather than prioritizing Windows tools.
  • Clarify that all steps can be performed on Linux hosts, and provide explicit guidance for Linux-only environments.
  • Avoid language that assumes Windows as the default platform for virtualization or image preparation.
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, while focused on Linux VMs, repeatedly references Windows-specific tools (PowerShell, PowerShell Workflow) and installation instructions for Windows (Hybrid Runbook Worker). In several sections, PowerShell and Windows scripting are mentioned before Bash/Linux equivalents. There are no concrete Linux script examples, and some features (like Hybrid Runbook Worker) link only to Windows installation guides, creating friction for Linux users.
Recommendations
  • Provide explicit Bash and Python script examples for Linux VMs in each section.
  • Ensure installation instructions for Hybrid Runbook Worker include Linux-specific steps and links.
  • Mention Linux tools and patterns (e.g., shell scripts, cron jobs) before or alongside Windows/PowerShell references.
  • Clarify which features are cross-platform and which are Windows-only, with clear guidance for Linux users.
  • Balance references to PowerShell with Bash and Python, especially in lists and feature descriptions.
GitHub Create Pull Request
Virtual Machines Time sync for Linux VMs in Azure ...blob/main/articles/virtual-machines/linux/time-sync.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_reference ⚠ī¸ powershell_example
Summary
The documentation is focused on Linux VM time sync in Azure and provides comprehensive Linux-specific guidance, examples, and tooling. However, there is a notable Windows bias in the introductory sections, which discuss Windows Server 2016 time sync improvements in detail and link to Windows documentation before any Linux-specific technical content is introduced. Additionally, a PowerShell example is provided for base64 encoding cloud-init data, rather than a Linux shell equivalent, which may create friction for Linux users.
Recommendations
  • Move Windows-specific background information to a separate section or appendix, and begin the main content with Linux-relevant details.
  • Provide Linux shell (e.g., base64) examples alongside or instead of PowerShell for tasks like encoding cloud-init data.
  • Ensure that all external links in 'Next steps' and 'Notes' include Linux-relevant resources, not just Windows documentation.
  • If referencing Azure infrastructure, clarify its relevance to Linux users and avoid implying that Windows features directly affect Linux VM configuration.
  • Consider adding a brief comparison table of time sync mechanisms across platforms if cross-platform context is needed.
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 a single example of template execution using PowerShell syntax (with Windows-style paths and backslashes), and does not offer a Linux/macOS equivalent (e.g., Bash or CLI with forward slashes). The only command-line example is Windows-centric, which may cause friction for Linux/macOS users. The Bicep templates themselves are cross-platform, but the operational instructions favor Windows.
Recommendations
  • Include equivalent Azure CLI example using Bash syntax (forward slashes, suitable for Linux/macOS terminals).
  • Add a note clarifying that the az CLI works on all platforms and provide platform-specific command examples.
  • Show both Windows and Linux/macOS command-line examples side-by-side for template deployment.
  • Avoid using only backslashes in file paths; show both .\ds.bicep (Windows) and ./ds.bicep (Linux/macOS).
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 ⚠ī¸ windows_examples_in_schema
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific tools (PowerShell, .exe allowlist generator) and examples are presented first and in greater detail. The allowlist generator tool is only available as a Windows executable, and sample schemas and identities are Windows-centric. PowerShell instructions are extensive, while Linux/macOS alternatives (such as Bash or cross-platform scripting) are not provided. CLI instructions do include Linux, but the overall workflow and examples favor Windows.
Recommendations
  • Provide a cross-platform version of the allowlist generator tool (e.g., a Python script or .NET Core binary).
  • Add Bash or shell script examples for Linux/macOS users, especially for tasks currently covered only by PowerShell.
  • Include Linux-specific sample identities and process names in the rules schema examples.
  • Present CLI instructions before or alongside PowerShell instructions to emphasize platform neutrality.
  • Explicitly mention macOS support and provide relevant examples if applicable.
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: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page exclusively provides Azure PowerShell examples for managing VM restore points, with no CLI, Bash, or Linux/macOS-specific instructions. All code samples use PowerShell syntax, and there is no mention of cross-platform tools or alternative workflows for non-Windows users. This creates friction for Linux/macOS users, who must translate or research equivalent commands themselves.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all operations (e.g., creating restore point collections, restore points, tracking status).
  • Explicitly mention that Azure CLI and REST API are cross-platform and provide sample commands for Linux/macOS users.
  • Where possible, provide Bash script snippets for common workflows.
  • Clarify tool requirements and installation steps for both Windows and Linux/macOS environments.
  • Consider reordering examples so that cross-platform tools (CLI/REST) are presented before or alongside PowerShell.
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 ⚠ī¸ windows_heavy_linking
Summary
The documentation is generally cross-platform, but there are several instances of Windows bias. Windows terminology and links are often presented first or exclusively (e.g., MBR/GPT partitioning, Sysprep, drive letters, and Windows-centric links). Windows tools and concepts (Sysprep, drive C/D, Windows Server Failover Cluster) are mentioned before or more prominently than Linux equivalents. Some links and examples are Windows-specific, with Linux alternatives referenced but not always equally detailed.
Recommendations
  • Ensure Linux examples and terminology are presented alongside Windows, not after or as an afterthought.
  • Provide equal detail and linking for Linux workflows (e.g., partitioning, imaging, cluster managers like Pacemaker).
  • Use neutral language where possible (e.g., 'OS disk' instead of 'drive C').
  • Where Windows-specific tools are mentioned (Sysprep, MBR/GPT links), include Linux equivalents (cloud-init, parted, fdisk, etc.) and relevant documentation.
  • In sections like 'Upload your VHD', ensure Linux and Windows guides are equally visible and detailed.
  • For cluster management, give equal prominence to Linux options like Pacemaker, with links to setup guides.
GitHub Create Pull Request
Virtual Machines Specify Marketplace purchase plan information using Azure PowerShell ...b/main/articles/virtual-machines/marketplace-images.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 Azure PowerShell for all examples, including resource creation and plan specification. No Azure CLI, Bash, or Linux-native command examples are provided, despite the page stating applicability to Linux VMs. The referenced 'Find and use Azure Marketplace images' link also points to a Windows/PowerShell-specific page. This creates friction for Linux/macOS users who typically use Azure CLI or Bash scripts.
Recommendations
  • Add equivalent Azure CLI examples for all major steps (getting VM info, creating image definitions, creating VMs, etc.).
  • Include Bash script snippets for Linux users where appropriate.
  • Reference both Windows/PowerShell and Linux/CLI documentation in 'Next steps' and throughout the page.
  • Clearly indicate when a step is platform-agnostic or provide platform-specific instructions side-by-side.
  • Ensure ARM template examples are accompanied by CLI deployment instructions (e.g., using 'az deployment').
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, including explicit extension names, status messages, and sample output. Linux instructions are less detailed, lacking concrete examples or output samples. Windows extension details and validation steps are shown first and in greater depth, while Linux equivalents are only mentioned briefly.
Recommendations
  • Add explicit examples and sample output for Linux VMs, similar to the Windows section.
  • Provide step-by-step instructions for installing and validating the Proxy Agent extension on Linux, including REST API payloads and expected status messages.
  • Present Windows and Linux instructions in parallel sections or tables to ensure equal visibility.
  • Include troubleshooting tips specific to Linux environments.
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: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page generally avoids platform-specific examples, but in the section about provisioning Linux VMs with MSP, it frames the limitation in terms of Windows philosophy and does not provide parity guidance for Linux users. There are no explicit Linux or Windows command-line examples, but the explanation prioritizes Windows deployment patterns and omits step-by-step Linux instructions for GPA installation or MSP enablement.
Recommendations
  • Provide explicit Linux instructions or examples for enabling MSP, including GPA installation steps.
  • Avoid framing Linux limitations in terms of Windows philosophy; instead, clarify the technical differences objectively.
  • Add parity examples for Linux users, such as using cloud-init, shell scripts, or VM extensions for GPA deployment.
  • Include troubleshooting or verification steps specific to Linux environments.
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 exhibits Windows bias by explicitly describing a simpler, single-step process for enabling GuestProxyAgent (GPA) on Windows, while noting that Linux requires a more complex, two-step process. However, no Linux-specific example or guidance is provided for the Linux workflow, and the main example uses a Windows VM name ('GPAWinVM'), further reinforcing the Windows-centric approach.
Recommendations
  • Add explicit, step-by-step instructions for enabling GPA on Linux, including any required post-provisioning configuration.
  • Provide Linux-specific ARM template or REST API examples, using Linux VM names and images.
  • Clarify any differences in validation steps for Linux VMs, if applicable.
  • Ensure parity in troubleshooting and advanced configuration guidance for Linux environments.
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 frequently presents Windows-specific tools, services, and troubleshooting steps before their Linux equivalents. Windows service names and commands (e.g., 'sc query', 'C:\WindowsAzure\ProxyAgent\Logs') are shown first or exclusively, while Linux examples are sometimes missing or less detailed. Some troubleshooting steps reference Windows-only tools (e.g., 'sc query' for eBPF services), and Linux instructions are less explicit or require more manual setup.
Recommendations
  • Provide Linux command equivalents wherever Windows commands are shown (e.g., use 'systemctl status' for Linux eBPF services instead of only 'sc query').
  • Present Linux and Windows instructions side-by-side or in parallel sections, rather than Windows-first.
  • Expand Linux troubleshooting steps with concrete examples, such as how to check service status, logs, and install required components.
  • Clarify installation and setup steps for Linux, including how to add the GPA extension and verify its health.
  • Ensure error code explanations and recovery steps are equally detailed for both platforms.
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 exhibits a moderate Windows bias. Several log tables and data collection methods reference Windows-specific tools (e.g., Windows Event Log, IIS logs, Windows DNS servers, Windows Security Events, Windows Firewall) and mention Windows services and patterns before or more prominently than Linux equivalents. While Linux is supported in some areas (e.g., Syslog, Linux Daemons), Windows-centric examples and terminology appear more frequently, and some log types are Windows-only. The only explicit example link provided is for Linux, but the overall reference material leans toward Windows-first presentation and tool coverage.
Recommendations
  • Ensure Linux and macOS equivalents are mentioned alongside Windows tools in all tables (e.g., highlight Linux audit logs, Linux firewall logs, Linux DNS server monitoring where applicable).
  • Add explicit Linux/macOS examples for data collection, especially for tables currently referencing only Windows sources.
  • Balance the order and prominence of Windows and Linux references in tables and descriptions.
  • Clarify which features are Windows-only and provide alternative guidance for Linux/macOS users.
  • Include more cross-platform agent and log collection scenarios, not just Windows-centric ones.
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: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples are presented first and in detail, with CLI examples following. The migration instructions link to a Windows-specific tutorial (toc/breadcrumb paths reference Windows), potentially confusing Linux users. While CLI examples are provided, the overall flow and references favor Windows tools and patterns.
Recommendations
  • Ensure migration instructions link to OS-neutral or Linux-specific tutorials where appropriate.
  • Alternate the order of PowerShell and CLI examples, or present CLI examples first to better support Linux/macOS users.
  • Explicitly state that CLI commands work on Linux/macOS and provide any necessary environment setup notes.
  • Add troubleshooting notes for Linux/macOS users if there are differences in error messages or command behavior.
  • Review linked resources to ensure they are not Windows-centric unless necessary.
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 the compatibility section and provides a warning that Windows users can enable GuestProxyAgent (GPA) directly from an ARM template, while Linux users must follow a more complex, two-step process. No Linux-specific examples or guidance are provided for the Linux configuration workflow, and no Linux tools or commands are mentioned.
Recommendations
  • Provide step-by-step instructions or examples for enabling GPA on Linux, including relevant commands and configuration files.
  • List supported operating systems in alphabetical order or group by platform to avoid implicit prioritization.
  • Explicitly mention Linux tools or automation options for GPA configuration, such as cloud-init or shell scripts.
  • Clarify any differences in the process for Linux users and provide troubleshooting guidance specific to Linux environments.
GitHub Create Pull Request
Virtual Machines Migrate Managed image to Compute gallery ...igration/migration-managed-image-to-compute-gallery.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 three migration methods: Portal, CLI, and PowerShell. The CLI example uses Azure CLI, which is cross-platform, but the PowerShell example is Windows-centric and presented as a primary tab. The use of PowerShell and the 'devx-track-azurepowershell' custom tag indicate a Windows bias. There are no explicit Linux/macOS-specific instructions or troubleshooting tips, and the PowerShell example may not be as accessible to Linux/macOS users. The Portal section is platform-neutral, but the overall structure and emphasis favor Windows tools.
Recommendations
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows, and consider making CLI the first or default example tab.
  • Add explicit notes or troubleshooting for Linux/macOS users, especially for authentication steps.
  • Reduce emphasis on PowerShell unless there are unique capabilities not available in CLI.
  • Ensure all screenshots and UI references are platform-neutral or provide Linux/macOS variants if relevant.
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, while not providing equivalent Linux/macOS CLI examples or links. The page also mentions PowerShell before CLI in the 'Next steps' section, and does not include any Linux/macOS-specific instructions or screenshots.
Recommendations
  • Include Azure CLI examples and links alongside PowerShell references, especially for tasks like checking VM SKU availability and performing the move.
  • Ensure that 'Next steps' and prerequisite links reference both PowerShell and CLI documentation, or provide a combined page with parity for both platforms.
  • Add explicit instructions or notes for Linux/macOS users where workflows or commands differ.
  • Balance screenshots and UI instructions to clarify that the Azure Portal is cross-platform, and avoid language that implies Windows-only usage.
GitHub Create Pull Request
Virtual Machines Network security group test ...ticles/virtual-machines/network-security-group-test.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 focusing its main example on testing RDP (Remote Desktop Protocol) connectivity, which is relevant only for Windows VMs. There are no equivalent Linux-specific connectivity examples (such as SSH), and the step-by-step instructions for testing inbound connections exclusively reference RDP. Although the prerequisites mention both Linux and Windows VMs, the actual test scenarios and screenshots are Windows-centric.
Recommendations
  • Add a parallel example for Linux VMs, such as testing SSH (port 22) connectivity, alongside the RDP example.
  • Explicitly state that the inbound connection test can be used for other protocols/services, and provide a table or section with common Linux scenarios.
  • Ensure screenshots and walkthroughs include both Windows and Linux VM contexts.
  • Present Windows and Linux examples with equal prominence, or alternate which is shown first.
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, while focused on Linux VMs, relies heavily on PowerShell-based workflows and examples for the migration process. The main migration script is a PowerShell script, and most step-by-step instructions (checking controller type, preparing environment, running the script, reverting changes, checking results) are given using PowerShell commands. There is minimal coverage of Linux-native tooling or shell scripting, and the use of PowerShell is presented as the default, even for Linux users. Azure CLI is mentioned briefly, but not as a primary workflow. Windows-centric tools and patterns (e.g., Set-ExecutionPolicy, PowerShell installation, Windows-style paths) are referenced before any Linux alternatives.
Recommendations
  • Provide equivalent Bash/shell script workflows for Linux users, including migration, verification, and rollback steps.
  • Offer Azure CLI-based examples for all major tasks, especially for checking VM properties and running migration scripts.
  • Document how to run the migration script natively on Linux (e.g., via Azure Cloud Shell, or using pwsh on Linux), and clarify prerequisites for Linux environments.
  • Reorder examples so that Linux-native commands and workflows are shown first or in parallel with PowerShell/Windows examples.
  • Explicitly note any limitations or differences when running the migration process on Linux vs. Windows.
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 generally covers both Windows and Linux VMs, but there is a noticeable Windows bias in several areas. Windows tools and patterns (e.g., PowerShell, Volume Shadow Service, SQL Server Always On) are mentioned first or exclusively, while Linux equivalents are referenced later or in less detail. Automation and scripting examples focus on PowerShell, with Azure CLI only briefly mentioned. Some linked guides and examples (e.g., incremental snapshots) point to Windows-specific pages, and Linux-specific instructions are less prominent or missing.
Recommendations
  • Provide Linux-first or Linux-parity examples for backup and restore operations, especially for scripting and automation (e.g., Bash, Azure CLI, cron).
  • Include explicit Linux tooling and patterns (e.g., fsfreeze, LVM snapshots, application-consistent backup strategies for Linux workloads) alongside Windows tools like Volume Shadow Service.
  • Ensure all referenced guides (such as incremental snapshots) have clear Linux equivalents and links.
  • Add Linux-specific database backup and DR examples (e.g., PostgreSQL, MySQL, MongoDB) in addition to SQL Server.
  • Where PowerShell is mentioned for automation, also provide Azure CLI and Bash script examples, and clarify cross-platform compatibility.
  • Review and update links to ensure Linux documentation is as discoverable as Windows documentation.
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 ⚠ī¸ sql_server_bias
Summary
The documentation page demonstrates a moderate Windows bias. Windows-centric examples (notably SQL Server) are used throughout, and Windows tools (PerfMon, Storage Spaces, PowerShell) are mentioned first or in greater detail than their Linux equivalents. Linux alternatives (iostat, MDADM) are present but often referenced after Windows, and some sections (e.g., disk striping) provide more step-by-step detail for Windows than Linux. The overall guidance is applicable to both platforms, but Windows users receive slightly more direct support and examples.
Recommendations
  • Provide Linux-first or side-by-side examples for key operations, such as disk striping and performance monitoring.
  • Include more detailed Linux guidance for disk striping (e.g., MDADM usage, recommended RAID levels, and stripe size configuration).
  • Balance SQL Server examples with equivalent Linux-first database workloads (e.g., PostgreSQL, MySQL) and their configuration tips.
  • Expand on Linux benchmarking and monitoring tools (e.g., explain vmstat, sar, atop, etc.) alongside iostat.
  • Ensure that Linux tools and commands are given equal prominence and detail as Windows tools.
  • Add links to Linux-specific best practices for disk performance and caching.
  • Consider using neutral, cross-platform examples where possible, or alternate between Windows and Linux in illustrative scenarios.
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 page demonstrates a moderate Windows bias. Windows-specific tools (services.msc, Event Viewer, COM+, MSDTC, VSS, Visual C++ Redistributable, .NET) 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-oriented. Windows examples and terminology (such as PowerShell, Control Panel, regsvr32.exe) are presented first or exclusively in several sections. Some troubleshooting steps (e.g., COM+ and VSS writer issues) are only applicable to Windows, with no mention of Linux analogs.
Recommendations
  • Provide equivalent Linux troubleshooting steps and examples where Windows tools are referenced (e.g., suggest systemctl, journalctl, or Linux log file paths instead of services.msc/Event Viewer).
  • Add Linux-specific error codes and resolutions for common extension/agent failures, matching the detail given for Windows.
  • Where PowerShell or Windows portal steps are given, include Azure CLI or Linux shell alternatives, and present them side-by-side.
  • Clarify which troubleshooting steps are Windows-only and provide Linux alternatives or explicitly state when no Linux equivalent exists.
  • Expand Linux troubleshooting for extension failures, agent issues, and network/DHCP configuration, with concrete commands and log locations.
GitHub Create Pull Request
Virtual Machines PowerShell Sample - Export/Copy snapshot as VHD to a storage account in different region ...nes-powershell-sample-copy-snapshot-to-storage-account.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 focused on PowerShell, providing only Windows/PowerShell-based examples and commands. There are no Bash, Azure CLI, or Linux-native instructions for exporting/copying snapshots as VHDs. All tooling and workflow are described in terms of PowerShell cmdlets, which are most familiar and accessible to Windows users. Linux alternatives are not mentioned or linked.
Recommendations
  • Add equivalent Azure CLI or Bash script examples for exporting/copying snapshots as VHDs.
  • Include a section describing how to perform the same task on Linux/macOS, using native tools or cross-platform Azure CLI.
  • Reference Linux/macOS documentation and provide links to relevant guides.
  • Clarify platform requirements and note PowerShell Core compatibility on Linux/macOS if relevant.
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 Azure Compute Gallery images across tenants. However, the PowerShell section is significantly more detailed, including steps for networking and VM configuration, while the CLI section is minimal and omits these details. The PowerShell examples use Windows-centric patterns (e.g., RDP port, Windows OS configuration), and the networking setup is only shown in PowerShell. PowerShell is a Windows-native tool, and its prominence and detail suggest a bias toward Windows environments. Additionally, the PowerShell tab appears after the CLI tab, but the CLI example is much less comprehensive.
Recommendations
  • Expand the Azure CLI example to include all steps shown in the PowerShell section, such as networking setup, credential creation, and VM configuration.
  • Provide Linux/macOS-specific guidance, such as using SSH instead of RDP, and show examples for creating Linux VMs.
  • Ensure parity in detail and completeness between CLI and PowerShell sections.
  • Mention cross-platform compatibility explicitly, and avoid Windows-centric terminology where possible.
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 demonstrates a moderate Windows bias: PowerShell examples and references are given equal or greater prominence than Azure CLI, with some links and examples (e.g., finding images in the Azure Marketplace, sharing images) referencing Windows-specific pages or PowerShell first. Windows tools and terminology (Sysprep, Hyper-V generation) are mentioned before or more thoroughly than their Linux equivalents. Linux-specific instructions (e.g., waagent for generalization, Linux upload VHD) are present but often referenced after Windows or in less detail. Some example links and troubleshooting guides default to Windows/PowerShell, and Linux CLI parity is not always explicit.
Recommendations
  • Ensure all example commands are provided in both Azure CLI and PowerShell, with CLI (cross-platform) examples shown first.
  • Where Windows-specific tools (Sysprep, Hyper-V) are mentioned, provide equivalent Linux instructions (waagent, etc.) with equal prominence and detail.
  • Avoid linking primarily to Windows/PowerShell documentation; provide direct links to Linux/CLI documentation where available.
  • Explicitly call out Linux/macOS compatibility and provide troubleshooting steps/examples for those platforms.
  • Review and update references to ensure Linux and Windows are treated equally in all scenarios, including FAQs and advanced scenarios.
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 three example tabs for sharing resources via RBAC: Portal, CLI, and PowerShell. The PowerShell example is Windows-centric and is presented as a first-class method alongside the cross-platform Azure CLI. There are no Linux/macOS-specific instructions or mentions of platform differences, and PowerShell is shown before any Linux shell scripting alternatives.
Recommendations
  • Explicitly mention that Azure CLI works on Linux/macOS and provide bash/zsh shell examples where appropriate.
  • Clarify that PowerShell examples are primarily for Windows users, and suggest alternatives for Linux/macOS users.
  • Consider adding a note about platform compatibility for each method.
  • If relevant, provide instructions for using Azure CLI in bash/zsh, and highlight any differences in authentication or environment setup for Linux/macOS.
  • List CLI (cross-platform) examples before PowerShell (Windows-centric) to reduce perceived Windows-first bias.
GitHub Create Pull Request
Virtual Machines Dlsv6 size series (Preview) ...virtual-machines/sizes/general-purpose/dlsv6-series.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation references Windows-specific technologies (such as Hyper-V nested virtualization) and tools (NTTTCP for bandwidth testing) without mentioning Linux equivalents or alternatives. In the networking section, Windows is mentioned before Linux when discussing optimization, and the bandwidth testing tool referenced is Windows-centric. No explicit Linux examples or tools are provided.
Recommendations
  • Include Linux equivalents for referenced Windows tools, such as suggesting iperf or netperf for bandwidth testing alongside NTTTCP.
  • Provide links to Linux-specific documentation for nested virtualization (e.g., KVM or QEMU guides) in addition to Hyper-V.
  • When listing OSes, mention Linux/macOS first or equally with Windows to avoid ordering bias.
  • Add explicit examples or optimization tips for Linux VMs where appropriate.
GitHub Create Pull Request
Virtual Machines Ev5 size series .../virtual-machines/sizes/memory-optimized/ev5-series.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 largely platform-neutral, focusing on VM specifications and features. However, there is a subtle Windows bias in the 'Feature support' section, where Nested Virtualization links specifically to a Windows/Hyper-V guide, and in the 'Network' section, where bandwidth testing references NTTTCP (a Microsoft tool primarily associated with Windows). Linux equivalents or guidance are not mentioned, and Windows tools are referenced first or exclusively.
Recommendations
  • Include links or references to Linux-specific nested virtualization documentation (e.g., KVM/QEMU guides for nested virtualization on Azure).
  • In the bandwidth testing section, mention and link to Linux-compatible tools such as iperf or netperf, and provide guidance for Linux users.
  • Where Windows-specific tools are referenced, add Linux alternatives and usage notes to ensure parity.
  • Review all feature support links to ensure Linux documentation is equally represented where applicable.
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 extensive coverage with multiple detailed scripts, including both Cloud Shell and local usage, and special handling for availability sets. The CLI section is present and functional, but less detailed and lacks explicit Linux/macOS shell context (e.g., bash vs. PowerShell). The Terraform example references a Windows VM quickstart and does not provide a Linux VM example or parity. There are references to Windows-specific migration scenarios and links. Overall, Windows tools and patterns are mentioned first and in greater detail, while Linux-specific guidance is minimal or absent.
Recommendations
  • Add explicit Linux/macOS shell examples in the CLI section, clarifying shell syntax and environment differences.
  • Provide a Terraform example for resizing a Linux VM, not just referencing the Windows quickstart.
  • Ensure migration workaround links and instructions cover both Windows and Linux VMs equally.
  • Balance PowerShell and CLI coverage, possibly by offering bash scripts or Azure CLI examples with Linux context first or equally.
  • Review and update references and quickstarts to include Linux VM scenarios and links.
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
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. Migration instructions are provided for the Azure portal (GUI), Azure PowerShell, and Azure CLI. The PowerShell example is detailed and presented before the CLI example. The CLI example is labeled as 'powershell' in the code block, and uses variable syntax ($var) that is typical for PowerShell, not Bash, which may confuse Linux/macOS users. No explicit Bash/Linux shell example is provided, and there is no mention of Linux-specific tools or patterns. The documentation assumes familiarity with PowerShell and Windows-centric workflows, potentially creating friction for Linux/macOS users.
Recommendations
  • Provide explicit Bash/Linux shell examples for Azure CLI commands, using correct Bash variable syntax (e.g., $resourceGroup without curly braces, or using export).
  • Ensure code blocks for CLI examples are labeled as 'bash' or 'sh' rather than 'powershell' when appropriate.
  • Add notes clarifying that Azure CLI works cross-platform and provide any OS-specific instructions if needed.
  • Consider presenting CLI (cross-platform) examples before PowerShell (Windows-centric) examples to reduce perceived bias.
  • Mention Linux/macOS compatibility in migration steps and highlight any differences or prerequisites for those platforms.
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 a moderate Windows bias. The only example for connecting to a VM uses PowerShell, with no mention of Linux/macOS terminals or their usage patterns. The instructions for using the SSH key after download are Windows-centric, and Linux/macOS users are not given explicit guidance or examples. References to further documentation also point to a page about connecting from Windows, reinforcing the bias.
Recommendations
  • Add explicit Linux/macOS terminal examples for connecting to the VM using SSH, e.g., using the Terminal app or bash.
  • Include notes on file permissions for the downloaded .pem file (e.g., chmod 600 on Linux/macOS).
  • Provide parity in instructions for moving the .pem file on Linux/macOS systems.
  • Reference documentation for connecting from Linux/macOS, not just Windows.
  • When showing SSH commands, avoid specifying PowerShell unless necessary, or present both Windows and Linux/macOS options side by side.
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 page exhibits a moderate Windows bias. Windows-specific tools (MBR2GPT.exe, Defrag, BitLocker, PowerShell) are described in detail, with step-by-step instructions and troubleshooting. Linux instructions are present but less detailed, often limited to validation steps and lacking guidance for disk conversion or troubleshooting. Windows examples and tools are frequently mentioned first or exclusively, while Linux equivalents are referenced briefly or omitted.
Recommendations
  • Provide detailed Linux disk conversion steps (e.g., using gdisk, parted, or other tools) for MBR to GPT and EFI partition creation, including troubleshooting.
  • Include Linux-specific troubleshooting guidance for common upgrade issues.
  • Balance example order: present Linux and Windows instructions with equal prominence, or alternate which comes first.
  • Reference Linux-native tools for disk management and encryption, not just Windows tools.
  • Expand Linux upgrade support beyond Marketplace images, or clarify the process for custom images.
  • Where PowerShell is used for ARM template deployment, offer Bash/CLI alternatives for Linux/macOS users.
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 resizing instructions for the Azure portal and Azure PowerShell, but omits equivalent examples for the Azure CLI, which is more commonly used on Linux/macOS. The PowerShell example is given before any mention of CLI, and no bash or Linux-native commands are shown. This creates friction for Linux/macOS users who may not use PowerShell.
Recommendations
  • Add Azure CLI (bash) examples for resizing VMs, including listing available sizes and performing the resize.
  • Present CLI and PowerShell examples side-by-side or in parallel sections, rather than PowerShell only.
  • Explicitly mention that CLI is cross-platform and suitable for Linux/macOS users.
  • Consider providing links to both PowerShell and CLI documentation in the main migration section.
GitHub Create Pull Request
Virtual Machines Create an Azure snapshot of a virtual hard disk ...rticles/virtual-machines/snapshot-copy-managed-disk.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. PowerShell examples and references are prominent, and Windows-centric tools and patterns (e.g., PowerShell cmdlets, Windows VM creation links) are mentioned before or more extensively than Linux equivalents. The 'Next steps' section links to Windows-specific guides first, with the Linux CLI example only appearing last. There is no explicit Linux-specific PowerShell example, and the CLI example is generic, not tailored for Linux VMs.
Recommendations
  • Ensure Linux examples are presented with equal prominence and detail as Windows examples, especially in the 'Next steps' section.
  • Provide Linux-specific PowerShell examples if relevant, or clarify PowerShell usage on Linux.
  • Alternate the order of Windows and Linux examples/links to avoid implicit prioritization.
  • Include explicit Linux VM creation and recovery steps in both PowerShell and CLI sections.
  • Add notes clarifying cross-platform compatibility for each tool and command.
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 in terms of Azure CLI, Portal, and ARM template instructions. However, PowerShell examples are given for all automation scenarios, which is a Windows-centric tool. Additionally, PowerShell is used for ARM template deployment and VM deallocation, with no mention of Bash or cross-platform alternatives. The documentation also references RDP (Windows) and SSH (Linux) equally, but PowerShell is the only scripting language shown for template deployment and roll-back, which may create friction for Linux/macOS users. The order of examples sometimes places PowerShell before CLI, and the template deployment steps use PowerShell commands exclusively.
Recommendations
  • Provide Bash or cross-platform shell examples for ARM template deployment and VM deallocation/start, alongside PowerShell.
  • Explicitly mention that Azure CLI and ARM templates can be used from Linux/macOS, and provide sample commands for those platforms.
  • Where PowerShell is used, add equivalent Bash/CLI instructions to ensure Linux/macOS users can follow without needing PowerShell.
  • Clarify that PowerShell is optional and not required for Linux/macOS users.
  • Consider reordering examples so that CLI or cross-platform methods appear before PowerShell, or present them side-by-side.
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 a moderate Windows bias. Windows OS images are used as the primary example in ARM template, CLI, and PowerShell sections. All code snippets for enabling Trusted launch use Windows-centric SKUs (e.g., '2022-datacenter-azure-edition'), and there are no explicit Linux image examples or Linux-specific command variations. The Guest Attestation extension publisher for Linux is mentioned, but not demonstrated in any code. PowerShell is given a dedicated section, and Windows tools/patterns (e.g., Azure PowerShell, Windows image SKUs) are referenced before or instead of Linux equivalents.
Recommendations
  • Include explicit Linux OS image examples (e.g., Ubuntu, Red Hat) in ARM template, CLI, and PowerShell sections.
  • Demonstrate use of the Linux Guest Attestation extension publisher in code snippets.
  • Add notes or sections clarifying any differences or additional steps for Linux scale sets.
  • Alternate or parallelize Windows and Linux examples to ensure parity and visibility.
  • Reference cross-platform installation instructions for CLI and PowerShell, not just Windows.
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 page exhibits several Windows biases: Windows concepts (Secure Boot, Hyper-V Shielded VM) are introduced first and referenced with Windows-centric links; PowerShell examples are consistently provided alongside CLI, sometimes before Linux-specific instructions; Windows tools and terminology (such as COM ports, Secure Boot links) are mentioned without Linux equivalents; and some troubleshooting and validation sections lack parity in Linux-specific guidance, especially for certificate inspection and VM image validation. Although Linux instructions are present for some tasks (e.g., SBInfo tool installation), Windows patterns and examples are more prominent and detailed.
Recommendations
  • Ensure Linux examples are provided for every CLI and PowerShell example, especially for certificate inspection and VM image validation.
  • Present Linux and Windows instructions in parallel, or alternate which is shown first, to avoid Windows-first ordering.
  • Include Linux-specific troubleshooting steps and links where only Windows tools or documentation are referenced.
  • Expand certificate inspection guidance to include Linux-native tools (e.g., openssl, certtool) and workflows.
  • Reference Linux documentation for Secure Boot and UEFI concepts, not just Windows hardware links.
  • Add more explicit Linux automation examples (e.g., Bash scripts, cloud-init) where PowerShell is used.
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: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits mild Windows bias. Windows tools and terminology (e.g., PowerShell, MicrosoftWindowsTemplate) are mentioned before or alongside Linux equivalents. While Linux is referenced in the 'Useful links' section and verification steps use Linux tools (mokutil), there are no explicit Linux command-line examples for creating or managing UEFI keys, and Windows-centric signature templates are highlighted. Instructions for creating certificates/keys refer users to external links for Linux, rather than providing direct examples, whereas Windows templates are named and described in the main scenarios.
Recommendations
  • Add explicit Linux command-line examples for creating and managing UEFI keys (e.g., using openssl, sbsigntool).
  • Provide step-by-step Linux instructions for certificate/key creation within the documentation, not just in external links.
  • Describe Linux-specific signature templates or clarify cross-platform applicability of existing templates.
  • Ensure Linux tools and patterns are mentioned alongside Windows ones, not only in 'Useful links'.
  • Consider reordering examples so that Linux and Windows scenarios are presented with equal prominence.
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: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation page for Trusted Launch in Azure VMs generally covers both Windows and Linux platforms, but there are several signs of Windows bias. Windows examples and references (such as ARM templates for Windows VMs) are given before Linux equivalents, and links to Windows-specific documentation (e.g., Secure Boot, TPM, VBS, Credential Guard) are prevalent. The 'Secure Boot' and 'vTPM' sections reference Windows documentation and features almost exclusively, with Linux details being less prominent or relegated to notes. Example templates are Windows-focused, and there is a lack of Linux-specific deployment examples or tooling references (e.g., cloud-init, Linux CLI usage).
Recommendations
  • Add Linux-focused deployment examples (e.g., ARM templates for Ubuntu or RHEL, cloud-init scripts).
  • Provide links to Linux documentation for Secure Boot, TPM, and attestation, not just Windows/MS docs.
  • Include Linux CLI and scripting examples alongside or before Windows/PowerShell examples.
  • Balance references to Windows tools/features with equivalent Linux security features and workflows.
  • Ensure that Linux-specific limitations and workarounds are documented with the same depth as Windows.
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 covers both Windows and Linux VMs, but there are several instances of Windows bias. Windows examples and links are often mentioned first, and some features (like Hotpatch) are described as Windows-only without Linux equivalents or alternatives. Maintenance control via CLI and PowerShell is mentioned, but no explicit Linux shell examples are provided. References to 'PowerShell' and 'Windows Server' are more prominent, and some links (e.g., scheduled events) default to Windows documentation before Linux. Linux users may need to search for their relevant instructions, causing friction.
Recommendations
  • Ensure that Linux and Windows examples/links are presented together or alternate which is shown first.
  • Provide explicit Linux shell (bash/CLI) examples where PowerShell is mentioned.
  • For Windows-only features (e.g., Hotpatch), clearly state the lack of Linux support and suggest Linux alternatives if available.
  • Balance the mention of Windows and Linux tools and terminology throughout the documentation.
  • Where links to both Windows and Linux documentation exist, present them side-by-side rather than defaulting to Windows first.
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 command-line examples for Azure CLI and PowerShell, with the PowerShell examples being Windows-specific. VM creation examples use Windows images (Win2016Datacenter) by default, and there are no explicit Linux VM image examples or Linux-specific guidance. The PowerShell tab is present, but there is no Bash or Linux shell scripting equivalent. The Azure CLI examples are cross-platform, but the overall pattern and examples favor Windows and Windows tooling.
Recommendations
  • Include explicit Linux VM image examples (e.g., UbuntuLTS, CentOS) alongside Windows VM examples in Azure CLI and PowerShell sections.
  • Add a Bash/Linux shell scripting tab or section, especially for users who prefer Bash over PowerShell.
  • Clarify that Azure CLI commands work on Linux/macOS and Windows, and provide any platform-specific notes if needed.
  • Ensure parity in examples and guidance for both Windows and Linux users, including troubleshooting and disk attachment scenarios.
  • Avoid using only Windows-centric VM images in examples; alternate or show both OS types.
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 shows a notable Windows bias: JSON examples for VM creation and updates consistently use Windows OS images and Windows-centric fields (e.g., 'osType': 'Windows', 'windowsConfiguration', 'adminPassword'), with no Linux equivalents or examples. Linux-specific configuration fields (like 'linuxConfiguration') are absent, and the only reference to Linux is in a link to IMDS sample code, not in the main examples. This may cause confusion or extra effort for Linux users.
Recommendations
  • Provide parallel JSON examples for Linux VMs, including 'osType': 'Linux', 'linuxConfiguration', and relevant image references.
  • Include Linux-specific fields and remove unnecessary Windows-only fields in generic examples.
  • Ensure example ordering is balanced or alternates between Windows and Linux.
  • Clarify in text that user data applies equally to Linux and Windows, and link to both Linux and Windows sample code.
  • Add a section explicitly showing how to retrieve and use user data on Linux VMs, not just via external links.
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 demonstrates a Windows bias by consistently using Windows VM examples and references throughout. All JSON template examples use Windows images (MicrosoftWindowsServer) and Windows-specific parameters, with no Linux equivalents shown. The main template referenced is 'vm-simple-windows', and even the SSD disk example specifies 'osType': 'Windows'. Linux VMs are mentioned only in the 'Applies to' section and in a single link at the end, but no Linux-specific template snippets or image references are provided.
Recommendations
  • Provide parallel Linux VM template examples, using Linux image references (e.g., Ubuntu, CentOS) and Linux-specific parameters.
  • Alternate or balance the use of Windows and Linux examples throughout the documentation, not just in links.
  • Include explicit notes or sections for Linux users, highlighting any differences in template structure or parameters.
  • Reference both Windows and Linux quickstart templates equally in the main text, not just in 'Next steps'.
GitHub Create Pull Request
Virtual Machines Maintenance control for OS image upgrades on Azure Virtual Machine Scale Sets using Azure portal ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/virtual-machine-scale-sets-maintenance-control-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 exclusively describes how to use the Azure portal GUI for maintenance control, with screenshots and instructions that are platform-agnostic but implicitly Windows-centric due to the Azure portal's design and common usage patterns. There are no examples or references to command-line tools, such as Azure CLI or PowerShell, nor any mention of Linux/macOS workflows or tools. This creates a subtle bias by omitting Linux-friendly automation and scripting options.
Recommendations
  • Add equivalent instructions for configuring maintenance control using Azure CLI, which is cross-platform and widely used on Linux/macOS.
  • Include sample scripts or commands for both PowerShell and Bash, demonstrating automation of maintenance configuration and assignment.
  • Explicitly mention that the Azure portal is accessible from any OS/browser, and link to CLI documentation for users preferring non-GUI workflows.
  • Provide troubleshooting or tips for Linux/macOS users if there are any known differences or limitations.
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: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by describing application consistency primarily in terms of Windows (VSS writers) before mentioning Linux (pre- and postscripts). It references Windows-specific tooling (Volume Shadow Copy Service) and does not provide concrete Linux examples or guidance for implementing pre- and postscripts, leaving Linux users with less actionable information.
Recommendations
  • Include explicit Linux examples for application-consistent restore points, such as sample pre- and postscripts.
  • Provide links or references to best practices for Linux application consistency in Azure.
  • Present Windows and Linux guidance in parallel, rather than Windows-first.
  • Clarify any differences in restore point creation or troubleshooting for Linux VMs.
GitHub Create Pull Request
Virtual Machines Manage, Update, and Delete VM Applications on Azure ...in/articles/virtual-machines/vm-applications-manage.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 all operations, but PowerShell (a Windows-centric tool) is given equal prominence and sometimes referenced for scripting even in CLI sections. Windows terminology and tools (PowerShell, Select-Object, ConvertTo-Json, etc.) are used throughout, and PowerShell scripting is shown for tasks that could be done with Bash or other Linux-native tools. There are no explicit Bash or Linux shell script examples, and PowerShell is referenced in CLI scripting notes, implying a Windows-first approach. However, the Azure CLI examples are cross-platform, and REST API usage is platform-neutral.
Recommendations
  • Add Bash/Linux shell script equivalents alongside PowerShell examples, especially in scripting sections.
  • When showing scripting with Azure CLI, use Bash syntax for loops and data extraction, not just PowerShell.
  • Clarify that Azure CLI commands work on Linux/macOS and provide OS-specific notes where relevant.
  • Avoid referencing PowerShell in CLI sections unless also providing a Linux shell alternative.
  • Consider reordering examples so that cross-platform tools (CLI, REST) are shown before Windows-specific tools (PowerShell).
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 shows a notable Windows bias: PowerShell is mentioned first among management options, and the 'Next steps' section exclusively links to a PowerShell-based guide. There is no direct example or link for Linux/macOS users (e.g., Azure CLI or Bash), and Windows-centric tools/patterns are prioritized.
Recommendations
  • Present Azure CLI and PowerShell options side-by-side, or alternate their order to avoid implicit prioritization.
  • Include direct links to Azure CLI and portal guides in the 'Next steps' section, not just PowerShell.
  • Add explicit examples or walkthroughs for Linux/macOS users using Azure CLI or Bash.
  • Clarify that all management options are cross-platform where applicable.
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, which is cross-platform. However, in the 'Restore a VM from a restore point' section, the links provided for creating a new VM and attaching disks point to Windows-specific guides, with no mention or links to equivalent Linux VM documentation. There are no Linux-specific instructions or examples, and Windows documentation is referenced first and exclusively.
Recommendations
  • Add links to Linux VM creation and disk attachment guides alongside the Windows links.
  • Explicitly mention that the process applies to both Windows and Linux VMs, or provide platform-specific notes where relevant.
  • Ensure parity by including examples or screenshots for both Windows and Linux VM scenarios, especially in restore workflows.
  • Where PowerShell or CLI alternatives are mentioned, clarify their cross-platform support and provide Linux/macOS usage notes if needed.
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 more detailed and uses Windows-centric SDK objects. The CLI example uses Ubuntu as the image, but does not provide any Linux-specific shell scripting or guidance. The PowerShell section is presented after CLI, but is more verbose and assumes familiarity with Windows tooling. There are no Bash or Linux shell script examples, nor is there mention of Linux-specific considerations beyond the image name in the CLI example.
Recommendations
  • Add explicit Bash/Linux shell script examples for VM creation using Azure CLI.
  • Provide guidance for Linux users on how to automate these settings (e.g., with shell scripts, cloud-init, etc.).
  • Balance the detail level between PowerShell and CLI sections, ensuring Linux users have equally comprehensive instructions.
  • Mention Linux-specific considerations (such as verifying vCPU count in Linux OS, e.g., using lscpu or /proc/cpuinfo).
  • If possible, provide macOS-specific notes for CLI usage.
GitHub Create Pull Request
Virtual Machines Create a VM from a specialized image version ...icles/virtual-machines/vm-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 both Azure CLI and PowerShell examples for all scenarios, but the PowerShell sections are significantly more detailed, with full resource creation steps and network configuration, while CLI examples are minimal. PowerShell is a Windows-centric tool, and the detailed guidance for it may disadvantage Linux/macOS users who rely on Bash or other shells. Additionally, network security examples focus on RDP (Windows remote access) rules, and PowerShell examples are always shown after CLI but are much more extensive, suggesting a bias toward Windows tooling and workflows.
Recommendations
  • Expand Azure CLI examples to include full resource creation and network configuration steps, matching the detail provided in PowerShell sections.
  • Add Bash shell script examples for Linux/macOS users, especially for multi-step VM and network setup.
  • Include explicit instructions or examples for configuring SSH (port 22) access in network security rules, not just RDP (port 3389).
  • Clarify that PowerShell examples are primarily for Windows users, and provide parity for Linux/macOS users.
  • Consider adding cross-platform scripting guidance (e.g., using Bash, Python, or Terraform) for advanced scenarios.
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, but several sections show Windows bias. Windows tools (PowerShell, cmd.exe, msiexec) are referenced more frequently and sometimes before Linux equivalents. Troubleshooting and status-checking examples use PowerShell exclusively, with no Linux CLI or Bash alternatives. File renaming and installer command examples are shown for Windows first, and Windows-specific patterns (registry, batch scripting) are explained in detail, while Linux sections are less comprehensive. The Linux packaging section is robust, but Windows-centric tools and examples dominate in troubleshooting and command interpreter discussions.
Recommendations
  • Add Linux CLI (az CLI, Bash) equivalents for all PowerShell troubleshooting/status commands.
  • Provide Linux-first or side-by-side examples for file renaming, installer invocation, and troubleshooting.
  • Expand Linux troubleshooting guidance (e.g., using az CLI, checking extension status via Bash/SSH).
  • Ensure parity in depth of explanation for Linux installer scenarios (e.g., handling .deb/.rpm uninstall, error handling).
  • Reference Linux tools (e.g., dpkg, apt, yum, zypper) in troubleshooting and management sections where appropriate.
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_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page for VM watch Collectors Suite demonstrates a moderate Windows bias. Windows-specific tools (e.g., w32tm, Windows EventLog) are referenced exclusively or before Linux equivalents, and some collectors are only eligible or described for Windows environments. Linux-specific details are sparse or missing, with some collectors lacking Linux parity or examples.
Recommendations
  • Provide equivalent Linux/macOS examples and tool references (e.g., mention ntpd/chrony for clock skew checks, syslog/journalctl for system errors).
  • Clarify eligibility and behavior for all collectors on Linux/macOS, especially where currently only Windows is described.
  • Add Linux/macOS-specific configuration parameters and troubleshooting steps where relevant.
  • Ensure that collector descriptions and examples are presented for both platforms, not just Windows.
  • Where a collector is Windows-only, explicitly state the lack of Linux/macOS support and suggest alternatives if possible.
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 generally Linux-focused for the Oracle ASM setup, but there is notable Windows bias in the sections describing the X Server VM. The X Server is deployed on a Windows VM using Windows-only tools (Xming), and all graphical installer steps require a Windows workstation. PowerShell is used for Bastion tunnel setup, and SCP instructions are given in a Windows context. There are no instructions for using a Linux or macOS workstation for X server or tunneling, nor are Linux X server alternatives mentioned.
Recommendations
  • Provide instructions for setting up X server on Linux and macOS workstations (e.g., using XQuartz for macOS, native X11 for Linux).
  • Include Linux/macOS equivalents for Bastion tunnel setup (e.g., using az CLI in Bash, SSH port forwarding).
  • Offer SCP command examples for Linux/macOS shells.
  • Clarify that the X Server VM does not need to be Windows, and describe how to use Linux-based X server if preferred.
  • Reorder examples to present Linux/macOS options first or alongside Windows options.
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: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation, while focused on deploying Oracle Golden Gate on Azure Linux VMs, demonstrates notable Windows bias in several areas. The X Server setup is exclusively described using a Windows VM and Windows-only tools (Xming), with no Linux or macOS alternatives mentioned. Bastion tunnel and SCP file transfer examples use PowerShell commands, with no Bash or Linux-native equivalents. The workflow assumes access to Windows for critical steps, potentially blocking Linux/macOS-only users.
Recommendations
  • Provide instructions for setting up X Server on Linux (e.g., using Xorg, X11 forwarding via SSH) and macOS (e.g., XQuartz).
  • Include Bash/Linux-native commands for Bastion tunnel setup and SCP file transfers, not just PowerShell.
  • Mention cross-platform alternatives for X Server and clarify that Windows VM is optional, not required.
  • Reorder examples so Linux-native approaches are presented first or alongside Windows methods.
  • Explicitly state any platform requirements and offer parity guidance for non-Windows users.
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: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. While the page claims applicability to Linux VMs and references Terraform (a cross-platform tool), it consistently presents Azure portal and PowerShell workflows for critical steps, such as configuring ExpressRoute FastPath, without providing equivalent Linux CLI (Azure CLI) examples. PowerShell is mentioned as an automation option, but Azure CLI is only referenced in the context of Terraform authentication, not for core network configuration tasks. The ordering of examples and instructions generally favors Windows-centric tools and workflows, with Linux alternatives either omitted or mentioned later.
Recommendations
  • Add Azure CLI command examples alongside PowerShell for all configuration steps, especially for ExpressRoute FastPath and network gateway setup.
  • Explicitly mention that all steps can be performed from Linux/macOS using Azure CLI and provide links to relevant CLI documentation.
  • Where screenshots are shown of the Azure portal, clarify that the portal is accessible from any OS/browser.
  • Ensure Terraform scripts are highlighted as the primary automation method for cross-platform parity.
  • Review and update any references to Windows-only tools to include Linux/macOS equivalents.
GitHub Create Pull Request
Virtual Machines Architectures for Oracle applications with database on Azure Virtual Machines ...ads/oracle/deploy-application-oracle-database-azure.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page discusses deploying Oracle applications on Azure Virtual Machines but does not provide explicit examples, instructions, or considerations for Linux environments. Windows is mentioned directly in the PeopleSoft section as a required OS for certain components, and there are no Linux-specific recommendations, examples, or parity notes. The general guidance and architecture are OS-agnostic, but the lack of Linux examples and the explicit mention of Windows create a subtle bias.
Recommendations
  • Add explicit examples and guidance for deploying Oracle applications on Linux-based Azure VMs, including OS-specific considerations for RHEL, Oracle Linux, or Ubuntu.
  • Where Windows is mentioned as a requirement (e.g., PeopleSoft Process Scheduler), clarify if Linux alternatives exist or provide instructions for Linux-based deployments.
  • Include sample architecture diagrams and migration steps for both Windows and Linux environments.
  • List common Linux administration tools and patterns alongside Windows ones (e.g., SSH, SELinux, systemd, Linux patching tools).
  • Ensure that any references to OS-specific features (such as Azure Disk Encryption or patch management) include both Windows and Linux options.
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 extensive, with a full script for VM creation, while the CLI section is more concise and lacks equivalent depth (e.g., no full end-to-end Linux shell script). Windows-specific tools (PowerShell, Az PowerShell module) are featured, and the PowerShell example is given after the CLI but is much more detailed. There is no explicit Linux shell (bash) or macOS Terminal example for automation, and no mention of Linux-native tools for scripting beyond Azure CLI.
Recommendations
  • Add a full Linux shell (bash) script example for end-to-end VM provisioning, matching the detail of the PowerShell script.
  • Explicitly mention that Azure CLI works on Linux/macOS and provide links to installation instructions for those platforms.
  • Balance the depth of CLI and PowerShell sections so Linux/macOS users have parity in automation guidance.
  • Consider adding Terraform or Ansible examples, which are popular in Linux automation.
  • Clarify that PowerShell Core is cross-platform, but most users on Linux/macOS will prefer bash/CLI.
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 includes a sample template that is Windows-specific (MS NAV with SQL Server and IIS), and lists Azure PowerShell as a deployment option alongside Azure CLI, but does not provide Linux/macOS-specific deployment guidance or highlight cross-platform compatibility. The Windows container example is more specialized than the Linux examples, and PowerShell is mentioned as a primary deployment tool, which may suggest a slight Windows bias.
Recommendations
  • Add equivalent Linux/macOS-focused sample templates for complex applications, such as a multi-container Linux application with similar complexity to the MS NAV example.
  • Clarify that Azure CLI is fully cross-platform and provide explicit instructions or links for Linux/macOS users.
  • Ensure deployment instructions and examples are presented in a way that does not prioritize Windows tools (e.g., PowerShell) over cross-platform alternatives.
  • Consider listing Azure CLI before PowerShell to emphasize cross-platform support.
  • If possible, add notes or callouts for Linux/macOS users regarding any platform-specific considerations.
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 is included as a first-class example, which is primarily a Windows tool, and is presented before REST. There are no Linux/macOS-specific shell examples (e.g., Bash, curl), and PowerShell is shown as a separate tab, potentially implying parity with CLI, despite CLI being cross-platform. No explicit Linux/macOS instructions or troubleshooting are provided.
Recommendations
  • Add Bash/curl examples for REST API usage to demonstrate Linux/macOS workflows.
  • Clarify that Azure CLI works on Windows, Linux, and macOS, and consider listing it first.
  • If PowerShell is shown, mention PowerShell Core compatibility for Linux/macOS, or provide Bash equivalents.
  • Include troubleshooting notes or tips for Linux/macOS users if there are platform-specific considerations.
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 page lists Windows Server cluster creation as the first 'Next steps' link, placing Windows before Linux. However, the main technical content is platform-neutral and does not use Windows-specific tools or examples.
Recommendations
  • List Linux and Windows cluster creation links in parallel or alphabetical order, or clarify that both platforms are supported equally.
  • Explicitly mention that the ARM template examples and mitigation steps apply to both Windows and Linux clusters.
  • If there are platform-specific differences in guardrails or error messages, provide examples for both Windows and Linux.
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 provides parity between Linux and Windows in terms of template links and deployment instructions. However, in the 'Next steps' section, PowerShell is mentioned before CLI, and a sample template link references a Windows deployment. This ordering and example selection may subtly prioritize Windows users and tools.
Recommendations
  • Alternate the order of Linux and Windows examples in lists to avoid implicit prioritization.
  • Provide sample template links for both Linux and Windows, or use a Linux example if referencing only one.
  • List Azure CLI before PowerShell in 'Next steps' or present both together to avoid tool bias.
  • Explicitly state that instructions and templates are available for both platforms throughout the documentation.
GitHub Create Pull Request
Virtual Machine Scale Sets Spot Placement Score ...les/virtual-machine-scale-sets/spot-placement-score.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 accessing the Spot Placement Score via Azure CLI and Azure PowerShell, with PowerShell (a Windows-centric tool) given its own dedicated section and example. The ordering of examples places Azure CLI before PowerShell, but both are presented as separate tabs. No explicit Linux/macOS shell examples (e.g., Bash) are provided, nor is there mention of Linux-specific considerations or parity for command-line usage. The REST API section is platform-neutral, but the lack of explicit Linux/macOS shell examples and the inclusion of PowerShell may create mild friction for non-Windows users.
Recommendations
  • Add explicit Bash or Linux/macOS shell examples for calling the REST API (e.g., using curl or httpie).
  • Clarify that Azure CLI is cross-platform and works on Linux/macOS, and provide example installation links for those platforms.
  • Consider reordering or grouping CLI and PowerShell examples under a general 'Command-line' heading, with notes about platform compatibility.
  • Mention that PowerShell Core is available on Linux/macOS if PowerShell usage is recommended.
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: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides examples for Azure PowerShell, Azure CLI, REST API, and Azure Portal. However, PowerShell examples are consistently presented before CLI examples, and there is a notable emphasis on PowerShell cmdlets throughout the page. There are no explicit Linux/macOS shell script examples, nor are there references to Linux-specific tools or environments. The CLI examples use generic Azure CLI commands, which are cross-platform, but the ordering and prominence of PowerShell may create a perception of Windows bias.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as CLI is natively cross-platform.
  • Explicitly mention that Azure CLI commands work on Linux/macOS and Windows.
  • Add example shell scripts for Linux/macOS environments where appropriate.
  • Clarify that PowerShell Core is available on Linux/macOS, if PowerShell examples are retained.
  • Balance the number and detail of CLI and PowerShell examples.
  • Avoid language such as 'PowerShell and Azure CLI' when referring to cross-platform tools; use 'Azure CLI and PowerShell' or clarify cross-platform support.
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 both Azure CLI and PowerShell examples, but PowerShell is given equal prominence as CLI and is presented before REST. PowerShell is a Windows-centric tool, and its inclusion as a primary example may indicate a bias toward Windows users. There are no Linux-specific shell examples (such as Bash or curl), nor is there explicit mention of Linux/macOS usage patterns. The CLI example is cross-platform, but the absence of Linux/macOS-specific guidance or troubleshooting tips suggests a mild Windows bias.
Recommendations
  • Add explicit Bash/curl examples for REST API usage to help Linux/macOS users.
  • Clarify that Azure CLI is cross-platform and provide installation/troubleshooting links for Linux/macOS.
  • Consider listing CLI examples before PowerShell, as CLI is more universally available.
  • Include notes or sections addressing Linux/macOS users, especially for command-line usage.
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 consistently presented immediately after CLI, and PowerShell-specific deployment commands (New-AzResourceGroupDeployment) are mentioned alongside CLI for ARM/Bicep templates. There is a notable emphasis on PowerShell and Windows-centric tools, with no explicit mention of Linux/macOS alternatives for PowerShell or deployment commands. The ordering and tool selection may subtly favor Windows users and workflows.
Recommendations
  • Explicitly state that Azure CLI is cross-platform and highlight its use for Linux/macOS users.
  • Clarify that PowerShell Core is available on Linux/macOS, or provide Bash script examples where appropriate.
  • When listing deployment commands for ARM/Bicep templates, mention az deployment group create first, or provide a Linux/macOS workflow example.
  • Consider alternating the order of CLI and PowerShell examples, or grouping cross-platform tools together.
  • Add a note about platform compatibility for each tool, especially for PowerShell.
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 (PowerShell) example is shown first and references a PowerShell script, while the Linux (bash) example follows. The initial tutorial links mention Azure CLI and PowerShell, but do not explicitly mention Linux-specific tools or examples. There is a slight preference for Windows tools and ordering.
Recommendations
  • Alternate the order of Windows and Linux examples, or present them side-by-side.
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Include links or references to Linux/macOS-specific documentation or troubleshooting guides.
  • Add a note clarifying parity between Windows and Linux support for all features discussed.
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 tooling (PowerShell) as a primary option, with a dedicated tab for PowerShell examples. The order of tabs places PowerShell before ARM Template, and the PowerShell example is detailed. However, Azure CLI examples (cross-platform) are present and shown before PowerShell, and there are no exclusive Windows-only tools or missing Linux/macOS instructions.
Recommendations
  • Clarify that Azure CLI works on Windows, Linux, and macOS, and highlight its cross-platform nature.
  • Consider moving the PowerShell tab after ARM Template to reduce perceived Windows prioritization.
  • Add a note for Linux/macOS users that Azure CLI is the recommended tool for cross-platform automation.
  • Explicitly mention that PowerShell Core is available on Linux/macOS if users prefer PowerShell.
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 on Azure Virtual Machine Scale Sets using the Azure Portal, Azure CLI, PowerShell, and ARM templates. While the CLI and ARM template examples are cross-platform, the PowerShell example is Windows-centric and is given equal prominence as the CLI. There is no explicit Linux/macOS bias, but PowerShell is a Windows-first tool and its inclusion may suggest a slight Windows bias. The CLI example is platform-neutral and appears before PowerShell, which helps mitigate bias.
Recommendations
  • Clarify that Azure CLI commands work on Windows, Linux, and macOS.
  • Consider mentioning that PowerShell Core is available cross-platform, or clarify if the example is for Windows PowerShell only.
  • If relevant, add Bash or shell script examples for Linux/macOS users, especially for automation scenarios.
  • Explicitly state platform compatibility for each tool in the documentation tabs.
GitHub Create Pull Request
Virtual Machines Modify a capacity reservation in Azure ...ticles/virtual-machines/capacity-reservation-modify.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 API, Portal, CLI, and PowerShell for all major operations. PowerShell is featured as a first-class automation option alongside Azure CLI, but PowerShell is a Windows-centric tool, and its examples are presented with equal prominence to the cross-platform CLI. In several places, PowerShell commands are shown after CLI, but the documentation does not show any Linux-specific shell scripting or mention Linux-native tools. There is no explicit Windows-only bias, but the parity between CLI and PowerShell may create a subtle bias toward Windows users, especially since PowerShell is not pre-installed on most Linux distributions.
Recommendations
  • Clarify that Azure CLI is fully cross-platform and recommended for Linux/macOS users, while PowerShell is more common on Windows.
  • Add example shell scripts (bash) for Linux users where appropriate, especially for automation scenarios.
  • Explicitly mention installation requirements for PowerShell on Linux/macOS if users wish to use those examples.
  • Consider listing CLI examples before PowerShell in each tabbed section to reinforce cross-platform parity.
  • Add a note that all CLI commands work identically on Linux, macOS, and Windows.
GitHub Create Pull Request
Virtual Machines Increase performance of Premium SSDs and Standard SSD/HDDs .../articles/virtual-machines/disks-enable-performance.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 steps, but the PowerShell examples are given equal prominence and detail as the CLI, despite PowerShell being primarily a Windows-centric tool. The prerequisites mention Azure PowerShell before Azure CLI, and the custom metadata ('devx-track-azurepowershell') suggests a PowerShell focus. There are no Linux-specific shell examples (e.g., bash-only, or Linux-native tools), and PowerShell is not natively available on most Linux distributions. However, the Azure CLI examples are fully cross-platform and shown first in each section, mitigating the bias.
Recommendations
  • Clarify that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
  • Add a note that PowerShell is available for Linux, but CLI is more commonly used on Linux/macOS.
  • Consider including bash-only or Linux-native shell examples for scripting tasks, especially for disk management.
  • Remove or balance metadata and authoring cues that suggest PowerShell is the primary method.
  • Explicitly state that all CLI examples work on Linux/macOS, and link to installation guides for those platforms.
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: PowerShell examples and links are presented before Azure CLI/Linux equivalents, and the 'Next steps' section links to a PowerShell-focused sample repository. While both Windows and Linux are marked as supported and CLI examples are provided, the ordering and external resources favor Windows users.
Recommendations
  • Present Azure CLI (Linux/macOS-friendly) examples before or alongside PowerShell examples.
  • Include links to Linux/macOS-focused sample repositories in the 'Next steps' section.
  • Ensure parity in screenshots and walkthroughs for Linux/macOS environments where relevant.
  • Explicitly mention cross-platform compatibility in all command-line instructions.
GitHub Create Pull Request
Virtual Machines Chef extension for Azure VMs ...blob/main/articles/virtual-machines/extensions/chef.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation provides examples and instructions for both Linux and Windows platforms, but there is a subtle bias toward Windows. The publisher value uses 'Chef.Bootstrap.WindowsAzure', which is Windows-centric branding. The extension type for Linux ('LinuxChefClient') is mentioned after the Windows type ('ChefClient'), and the directory paths for extension logs are listed with Windows first in the troubleshooting section. However, the Azure CLI example is Linux-focused, and there is a clear effort to address Linux users.
Recommendations
  • List Linux and Windows examples side by side or in parallel sections, rather than mentioning Windows first.
  • Provide explicit Linux and Windows deployment examples in Azure CLI and ARM templates.
  • Use neutral publisher naming or clarify that 'Chef.Bootstrap.WindowsAzure' applies to both platforms.
  • Ensure troubleshooting sections alternate or start with Linux examples if the documentation is intended for both audiences.
  • Add a Linux-specific troubleshooting section (e.g., common issues, permissions, SELinux notes) to match Windows parity.
GitHub Create Pull Request
Virtual Machines Azure Key Vault VM Extension for Linux ...rticles/virtual-machines/extensions/key-vault-linux.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 focused on Linux, but several sections exhibit Windows bias. PowerShell deployment instructions and troubleshooting commands are presented before or alongside Azure CLI equivalents, even though Linux users are more likely to use Azure CLI or shell scripts. References to Windows-specific tools and patterns (such as PowerShell and ARM template caveats referencing Windows VM configuration) appear in places where Linux alternatives could be emphasized or presented first.
Recommendations
  • Present Azure CLI examples before PowerShell examples in all deployment and troubleshooting sections.
  • Clearly mark PowerShell instructions as primarily for Windows users, and Azure CLI as the recommended approach for Linux.
  • Remove or move Windows-specific notes (such as ARM template caveats referencing Windows VM configuration) to a dedicated Windows section.
  • Add bash/shell script examples for common operations (such as settings file manipulation, troubleshooting, etc.) where appropriate.
  • Ensure all troubleshooting and operational guidance is Linux-centric, with Windows alternatives in a separate section.
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 generally maintains Linux-centric content. However, in the warning section, Windows tooling (PowerShell cmdlet Get-AzVMDiskEncryptionStatus) is mentioned before the cross-platform Azure CLI command (az vm encryption show) for checking encryption status. This subtly prioritizes Windows/PowerShell tooling and may cause friction for Linux/macOS users who are less likely to use PowerShell.
Recommendations
  • List the Azure CLI command before the PowerShell cmdlet when describing how to check encryption status, as Azure CLI is cross-platform and more relevant to Linux/macOS users.
  • Explicitly state that Azure CLI is recommended for Linux/macOS environments.
  • Consider providing bash script examples or direct Linux shell commands where appropriate.
  • Review troubleshooting and support sections to ensure no implicit prioritization of Windows tools.
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 presents three usage tabs: Portal, CLI, and PowerShell. The PowerShell section is given equal prominence to the CLI, despite PowerShell being primarily a Windows tool. There are no Linux/macOS-specific shell examples (e.g., Bash), and PowerShell is presented as a main method for automation, which may bias Windows users. However, the CLI examples use the Azure CLI, which is cross-platform and suitable for Linux/macOS users.
Recommendations
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows.
  • Add explicit Bash shell examples or notes for Linux/macOS users, such as how to install and use Azure CLI on those platforms.
  • Consider adding a note that PowerShell Core is available cross-platform, but most Linux/macOS users will prefer Azure CLI.
  • If possible, provide example scripts for Linux automation (e.g., Bash) alongside PowerShell scripts.
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
Low 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 examples for Azure CLI, Azure PowerShell, and the Azure Portal for each query. Azure PowerShell is a Windows-centric tool, and its inclusion alongside Azure CLI (which is cross-platform) is standard in Azure docs. However, the documentation does not provide any Linux/macOS-specific shell examples (e.g., Bash scripts, shell pipelines), nor does it mention Linux-native tools or patterns. In sections about OS update installation, Windows Server and Linux are treated separately, but the Windows example appears after the Linux one. There is a slight bias toward Windows tools (PowerShell) and the lack of Linux-specific command-line patterns.
Recommendations
  • Add explicit Bash/shell examples for Linux/macOS users, especially for common tasks like parsing or post-processing query results.
  • Clarify that Azure CLI is fully cross-platform and highlight usage on Linux/macOS, possibly with screenshots or terminal output.
  • Where PowerShell is mentioned, consider also referencing Linux-native scripting approaches (e.g., jq, grep, awk) for processing output.
  • For OS update queries, ensure parity in detail and placement between Windows and Linux sections.
  • Add notes or links to Linux/macOS installation and usage guides for Azure CLI and PowerShell Core.
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 page exhibits mild Windows bias. Windows is mentioned first in several places (e.g., 'automatic GPA installation (when true) or uninstallation (when false) on a Windows VM'), and the example VM names use 'GPAWinVM', which implies a Windows-centric example. The configuration and audit log locations are provided for both Linux and Windows, but Windows is often referenced first or exclusively in explanatory text. No PowerShell-heavy examples or missing Linux instructions are present, and Linux audit log paths are documented.
Recommendations
  • Use neutral VM names in examples (e.g., 'GPAExampleVM' instead of 'GPAWinVM').
  • When describing agent installation/uninstallation, clarify Linux behavior explicitly and avoid mentioning Windows first.
  • Ensure that all configuration steps and examples are equally applicable to Linux and Windows, and highlight any OS-specific differences.
  • Alternate the order of OS references in tables and explanations to avoid implicit prioritization.
  • Add explicit notes about GPA installation/uninstallation on Linux VMs where relevant.
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 (NSG) rule for Remote Desktop traffic, both Azure CLI and Azure PowerShell examples are provided. The PowerShell example is shown after the CLI, but PowerShell is a Windows-centric tool. There is also a reference to using SSH from Windows before mentioning Linux SSH key creation in the prerequisites and next steps. No Linux-specific firewall tools (like ufw or firewalld) are mentioned for opening port 3389, and the NSG rule creation references a Windows documentation link for portal instructions.
Recommendations
  • Add examples for configuring Linux firewalls (e.g., ufw, firewalld) to open port 3389, alongside the Azure NSG rule.
  • Reference Linux SSH documentation before Windows SSH documentation, or present both equally.
  • Clarify that Azure PowerShell is cross-platform, but highlight CLI and Linux-native tools for Linux users.
  • Provide links to Linux-native RDP clients and troubleshooting steps for those clients.
  • Ensure that documentation links for portal instructions do not point to Windows-specific pages.
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 details (e.g., unattend XML, WinRM, certificateStore) are described first and in greater depth than Linux equivalents. The only certificate store example is for Windows, and the 'windowsConfiguration' section is more elaborate than 'linuxConfiguration'.
Recommendations
  • Provide Linux configuration examples with equal detail, such as sample SSH configuration, cloud-init customData, and Linux-specific disk or boot diagnostics options.
  • Include certificate store examples for Linux (e.g., location of PEM files, integration with Linux keyrings).
  • Alternate the order of OS-specific configuration sections, or present them side-by-side for parity.
  • Clarify any platform-specific limitations or behaviors for both Windows and Linux VMs.
GitHub Create Pull Request
Virtual Machines List, update, and delete resources ...in/articles/virtual-machines/update-image-resources.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 tasks, but PowerShell is given equal prominence as CLI, despite being a Windows-centric tool. In some sections, PowerShell examples are present where Linux/macOS users would not benefit. The CLI examples are cross-platform, but PowerShell is not, and its inclusion may create confusion or friction for non-Windows users. No Linux-specific tools or shell examples (e.g., bash scripting) are provided, and PowerShell is presented as a primary alternative to CLI, which may imply Windows bias.
Recommendations
  • Clearly indicate that PowerShell examples are intended for Windows users and that Azure CLI is cross-platform.
  • Consider providing bash or shell script examples for Linux/macOS users where scripting is relevant.
  • Where PowerShell is used, add notes or links for Linux/macOS users to install PowerShell Core if needed, or recommend CLI as the preferred cross-platform tool.
  • If possible, reorder examples so CLI appears before PowerShell, emphasizing its cross-platform nature.
  • Explicitly mention that all CLI commands work on Linux/macOS and Windows.
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_tools ⚠ī¸ windows_first
Summary
The documentation demonstrates mild Windows bias by referencing Windows-specific technologies (VSS) and mentioning Windows patterns before Linux equivalents. While both Windows and Linux are acknowledged, Windows tooling (VSS) is described in more detail, and troubleshooting links focus on Windows scenarios. Linux is mentioned as using pre-/postscripts, but no further guidance or troubleshooting is provided for Linux-specific issues.
Recommendations
  • Provide equal detail for Linux restore point mechanisms, including common issues and troubleshooting steps.
  • Include links or sections for Linux-specific troubleshooting, analogous to the VSS writer troubleshooting for Windows.
  • Present Windows and Linux examples side-by-side or in parallel, rather than listing Windows first.
  • Expand on how pre-/postscripts work for Linux, with examples and best practices.
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 commands are shown immediately after Bash. There is no evidence of exclusive Windows tooling or missing Linux examples, but the presence of PowerShell in every example and the order of presentation may subtly favor Windows users.
Recommendations
  • Explicitly state that Bash examples work on Linux/macOS and PowerShell examples are for Windows (or PowerShell Core on Linux/macOS).
  • Where possible, provide examples for Linux/macOS-specific tools or clarify cross-platform compatibility.
  • Alternate the order of Bash and PowerShell examples to avoid implicit prioritization.
  • Add a note about using Azure CLI and Resource Graph Explorer being available cross-platform.
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 first and in more detail, which may subtly prioritize Windows users. There is no explicit mention of Linux/macOS prerequisites, nor troubleshooting guidance for Bash users. The portal instructions are platform-neutral, but command-line sections show a slight Windows-first bias.
Recommendations
  • Alternate the order of Bash and PowerShell examples, or present Bash first to balance representation.
  • Explicitly mention Linux/macOS compatibility and prerequisites for Bash scripts.
  • Add troubleshooting steps specific to Bash/Linux environments.
  • Clarify that both Bash and PowerShell scripts are equally supported and provide parity in example detail.
GitHub Create Pull Request
Container Instances Big containers on Azure container instances ...ob/main/articles/container-instances/big-containers.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 lists 'PowerShell' as a primary deployment method for Big Containers, mentioning it before Linux-friendly alternatives like Azure CLI. No Linux/macOS-specific examples or tools are provided, and there is no mention of Bash or shell scripting. The guidance is generic but subtly prioritizes Windows-centric tools and patterns.
Recommendations
  • Explicitly mention Linux/macOS compatibility and provide Bash/Azure CLI examples alongside PowerShell.
  • List Azure CLI before PowerShell when describing deployment options, or present them together.
  • Include links or references to Linux/macOS setup guides for Azure Container Instances.
  • Clarify that all major platforms (Windows, Linux, macOS) are supported for deployment.
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 ⚠ī¸ windows_image_example
Summary
The documentation is generally Linux-focused, with Bash/Azure CLI examples and explicit mention of Linux containers. However, the main container image used in the YAML example is 'mcr.microsoft.com/powershell', which is a Windows-centric tool, and the container name is 'pwsh-vnet-dns', suggesting a PowerShell context. No Linux-native images (such as Ubuntu, Alpine, or nginx) are shown, and PowerShell is used as the default shell in the example, which may be unfamiliar or less relevant for Linux users.
Recommendations
  • Provide example YAML using a common Linux image (e.g., Ubuntu, Alpine, nginx) instead of PowerShell.
  • Show how to validate DNS using standard Linux tools (e.g., dig, nslookup) in the container, not just PowerShell.
  • Clarify that PowerShell can run on Linux, but offer alternatives for users who prefer native Linux shells.
  • Consider renaming the example container from 'pwsh-vnet-dns' to something more neutral, like 'dns-test'.
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 management, but does not provide explicit Linux/macOS-specific examples or mention Bash scripting. The order of tool mention is 'Azure portal', 'Azure CLI', 'Azure PowerShell', which slightly favors Windows tools by listing PowerShell before Bash or shell scripting. However, all command-line examples use Azure CLI, which is cross-platform. There are no examples that are exclusive to Windows or PowerShell, and no critical steps require Windows-only tools.
Recommendations
  • Clarify that Azure CLI commands work on Windows, Linux, and macOS, and recommend Cloud Shell as a cross-platform option.
  • When listing tool options, mention Bash/shell scripting or Linux-native tools explicitly if relevant.
  • If referencing PowerShell, provide equivalent Bash or shell commands where possible, or link to Linux/macOS-specific guides.
  • Consider listing Azure CLI before PowerShell to emphasize cross-platform parity.
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: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
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 as the Linux example, and Windows-specific tools (cmd.exe) are explicitly mentioned. There is a slight bias in presenting Windows tooling and examples alongside Linux, but Linux users are not prevented from completing the task.
Recommendations
  • Ensure Linux examples are presented first, as Linux containers are more common in cloud scenarios.
  • Explicitly mention macOS compatibility where relevant, as macOS users also use Bash/zsh shells.
  • Add a note clarifying that the Azure CLI works identically on Linux, macOS, and Windows, and that the exec-command should match the shell available in the container.
  • Consider providing a table or section summarizing common shell commands for Linux, Windows, and macOS containers.
GitHub Create Pull Request
Container Instances Set environment variables in container instance ...instances/container-instances-environment-variables.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 Azure PowerShell examples, but the PowerShell section is prominent and detailed, and Windows-specific instructions (such as quoting syntax for environment variables in Windows Command Prompt) are mentioned before Linux equivalents. The CLI examples assume Bash/Azure Cloud Shell, but Windows-specific notes are given more explicit attention. There is no explicit Linux/macOS example section, and PowerShell (a Windows-centric tool) is given equal or greater coverage than CLI, which is more cross-platform.
Recommendations
  • Add a dedicated section or notes for Linux/macOS users, including shell-specific syntax for environment variables (e.g., zsh, bash).
  • Present CLI examples first and make them the primary example, as CLI is cross-platform.
  • Minimize Windows Command Prompt-specific instructions, or move them to a dedicated 'Windows notes' subsection.
  • Include explicit Linux/macOS command-line examples where quoting or syntax differs.
  • Clarify that PowerShell is available on Linux/macOS, or indicate when examples are Windows-only.
GitHub Create Pull Request
Container Instances Enable Managed Identity in a Container Group ...iner-instances/container-instances-managed-identity.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_section_segregation
Summary
The documentation provides comprehensive examples for enabling and using managed identities in Azure Container Instances, but the only explicit Windows-specific guidance is segregated into a dedicated section at the end. This section describes a Windows-only pattern for obtaining tokens, using Windows environment variables and PowerShell, and notes that standard Linux patterns (metadata server, az login) do not work in Windows containers. The main body of the documentation uses Bash and Azure CLI, which are cross-platform but more natural for Linux/macOS users. There are no Linux-specific tools or examples, but the Linux pattern is presented as the default throughout.
Recommendations
  • Add explicit notes at the beginning clarifying that the main examples use Linux containers, and that Windows containers require a different approach.
  • Provide equivalent Linux/macOS examples wherever Windows/PowerShell examples are given, even if the Linux pattern is already the default.
  • Include a table or summary comparing Linux and Windows container managed identity patterns for quick reference.
  • Clarify which commands and patterns are cross-platform (e.g., Azure CLI in Windows containers via mcr.microsoft.com/azure-cli image).
  • Consider adding a short Linux container example in the Windows section for parity.
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 CLI, and is always listed immediately after CLI. There are no Linux/macOS-specific instructions or mentions of Bash, and PowerShell is not clearly marked as Windows-only. However, Azure CLI is cross-platform and shown first, so Linux/macOS users can follow the instructions without major issues.
Recommendations
  • Clarify that Azure PowerShell examples are primarily for Windows users, and that Azure CLI is recommended for cross-platform (Linux/macOS/Windows) usage.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, while PowerShell is most common on Windows.
  • Consider providing Bash script examples or notes for Linux/macOS users where relevant.
  • If possible, add a short section or callout for Linux/macOS users confirming that all steps are supported on their platforms via Azure CLI.
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
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 retrieving prediction results, but PowerShell is featured as a primary method alongside CLI and REST. PowerShell is a Windows-centric tool, and its inclusion as a top-level example (with a dedicated tab) reflects a Windows bias. There are no Linux/macOS-specific shell examples (e.g., Bash scripts, curl commands), and PowerShell is listed before REST, which is platform-neutral. However, the Azure CLI example is cross-platform, mitigating the bias somewhat.
Recommendations
  • Add explicit Bash/curl examples for Linux/macOS users under a separate tab or within the REST section.
  • Clarify that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
  • Consider listing CLI and REST examples before PowerShell, or at least clarify PowerShell's platform limitations.
  • If PowerShell is mentioned, note that PowerShell Core is available on Linux/macOS, but provide native shell examples for those platforms.
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 and troubleshooting, but Windows-specific considerations (such as image support, networking delays, and cached images) are often mentioned before or in more detail than Linux equivalents. Windows-specific tools and patterns (e.g., PowerShell, Windows image tags, Windows networking delays) are described, while Linux details are sometimes less emphasized. In some cases, instructions for shell commands note Bash as the default, but only briefly mention the need to adjust for PowerShell/Command Prompt, without providing explicit Linux/macOS alternatives.
Recommendations
  • Ensure Linux/macOS examples are presented with equal detail and prominence as Windows examples.
  • When mentioning shell commands, provide explicit Bash and PowerShell/Command Prompt syntax side-by-side.
  • Expand troubleshooting sections to cover Linux/macOS-specific issues (e.g., SELinux/AppArmor, common Linux container errors).
  • Balance the order of presentation so that Linux and Windows considerations are alternated or grouped, rather than Windows-first.
  • Provide links to Linux/macOS documentation and tools where relevant.
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
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides command-line examples for Azure CLI, PowerShell, and REST API. The PowerShell example is given equal prominence to the CLI, and there is no mention of Linux/macOS-specific tools or shell environments (e.g., Bash). The CLI example is cross-platform, but PowerShell is a Windows-centric tool, and its inclusion without a Bash or shell script example suggests a mild Windows bias. The ordering of examples (CLI first, then PowerShell) is neutral, but the lack of explicit Linux/macOS shell examples or notes about cross-platform usage is a subtle bias.
Recommendations
  • Add explicit Bash or shell script examples for Linux/macOS users, especially for REST API calls (e.g., using curl).
  • Clarify that Azure CLI is cross-platform and can be used on Linux/macOS.
  • Note that PowerShell Core is available on Linux/macOS, or provide guidance for those platforms.
  • Include troubleshooting or environment setup notes for Linux/macOS users if any differences exist.
GitHub Create Pull Request
Container Instances Override entrypoint in container instance ...ntainer-instances/container-instances-start-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 provides both Linux and Windows shell examples in the shell table, but there is a notable emphasis on Azure PowerShell (Windows-centric) as a primary tool alongside Azure CLI. Windows tools and conventions (cmd, PowerShell) are mentioned explicitly and sometimes before Linux equivalents. However, Linux shell usage is demonstrated in examples, and the Azure CLI (cross-platform) is used for all step-by-step instructions. There are no exclusive Windows-only instructions, but the presence of PowerShell and Windows shell references may create mild friction for Linux/macOS users.
Recommendations
  • Add explicit Linux/macOS PowerShell alternatives or clarify that Azure CLI is cross-platform and preferred for non-Windows users.
  • Reorder shell table to list Linux shells first (e.g., Ubuntu, Alpine) before Windows (cmd) to reduce Windows-first perception.
  • Provide a Linux/macOS-specific example for Resource Manager templates or YAML files, showing command-line overrides in a native editor or workflow.
  • Clarify that PowerShell is optional and not required for Linux/macOS users.
  • Add a note that Azure CLI commands work identically on Linux, macOS, and Windows.
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. While Azure CLI is cross-platform, PowerShell is primarily associated with Windows, and its section is given equal prominence. There is a slight Windows bias in that PowerShell is featured as the only alternative to Azure CLI, with no mention of Linux/macOS-specific tools or workflows (e.g., Bash, scripting, or REST API usage). The CLI example appears first, which is positive, but the PowerShell section may imply Windows-centric workflows for users seeking alternatives.
Recommendations
  • Clarify that Azure CLI works on Windows, Linux, and macOS.
  • Add explicit Bash shell examples or mention that the Azure CLI commands work identically on Linux/macOS.
  • Consider including REST API or ARM template examples for users who prefer declarative or non-shell approaches.
  • If PowerShell is included, note that PowerShell Core is available cross-platform, or provide guidance for Linux/macOS users.
  • Avoid implying that PowerShell is a required or preferred alternative to Azure CLI.
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 example, and PowerShell is a Windows-centric tool. There are no explicit Linux/macOS-specific instructions or examples (e.g., Bash scripting, Linux-specific notes), and the ordering of examples places PowerShell immediately after CLI, which may suggest parity but still reflects a Windows-first mindset by including PowerShell as a primary method.
Recommendations
  • Clarify that Azure CLI works cross-platform and is recommended for Linux/macOS users.
  • Add explicit Bash or shell script examples for Linux/macOS users, if relevant.
  • Note that PowerShell Core is available on Linux/macOS, but most users on those platforms will prefer Azure CLI.
  • Consider reordering examples to present CLI first, then PowerShell, and explicitly mention platform compatibility.
  • Add a short section or note for Linux/macOS users to confirm that all steps are supported and provide links to platform-specific guidance if needed.
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 shows a mild Windows bias. Several release notes and key announcements reference Windows-specific configuration properties (e.g., 'windowsConfiguration.enableAutomaticUpdates'), Windows Server support, and Windows tools (such as Web Platform Installer and Visual Studio). These references often appear before or without equivalent Linux/macOS details. However, the page also mentions Linux support and features, and does not include command-line or scripting examples that would further increase bias.
Recommendations
  • When mentioning configuration properties (such as 'windowsConfiguration.enableAutomaticUpdates'), also include Linux equivalents or clarify if not applicable.
  • Ensure that announcements about OS support (e.g., Windows Server 2022, Ubuntu 20.04) are presented in parallel, not with Windows first.
  • Where Windows-specific tools (WebPI, Visual Studio) are referenced, add information about Linux/macOS alternatives (e.g., CLI, VS Code, package managers).
  • Explicitly mention Linux/macOS support for features and releases where applicable.
  • Consider adding a summary table or section that highlights cross-platform compatibility for each release.
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 referencing Windows-specific tools and paths (Visual Studio, C:\Program Files\Microsoft SDKs\Service Fabric\schemas\ServiceFabricServiceModel.xsd) as the primary method for schema validation and IntelliSense. No Linux or cross-platform alternatives are mentioned for authoring or validating manifest files. Additionally, the only tooling guidance is Windows-centric and appears early in the article.
Recommendations
  • Include instructions or examples for validating and editing manifest XML files on Linux/macOS, such as using VS Code, JetBrains Rider, or command-line tools like xmllint.
  • Mention the location of Service Fabric SDK schemas on Linux/macOS installations, if available.
  • Provide cross-platform guidance for authoring manifests, such as using platform-agnostic editors or CLI tools.
  • Avoid referencing Windows paths and tools exclusively; offer parity for non-Windows environments.
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 maintains OS neutrality throughout most of the content, mentioning both Windows and Linux as supported platforms for Service Fabric clusters. However, in the 'Next steps' section, the link to 'Create a Service Fabric cluster running Windows' is presented before the link to the Linux equivalent, indicating a subtle 'windows_first' bias. No examples or tooling are specific to Windows or PowerShell, and Linux is not omitted from any critical instructions.
Recommendations
  • Present links to Windows and Linux cluster creation in parallel or alphabetically, rather than listing Windows first.
  • Where possible, alternate the order of OS mentions throughout documentation to avoid implicit prioritization.
  • Explicitly state that all configuration steps and templates apply equally to both Windows and Linux clusters, unless otherwise noted.
GitHub Create Pull Request
Service Fabric Service Fabric cluster capacity planning considerations ...cles/service-fabric/service-fabric-cluster-capacity.md
Low 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 mild Windows bias by referencing Windows-specific tools and patterns (such as Patch Orchestration Application and standalone clusters hosted in Windows), and by providing instructions for Windows before Linux equivalents. There is a lack of explicit Linux/macOS examples or guidance for non-Windows environments, especially regarding cluster configuration and maintenance tasks.
Recommendations
  • Include explicit instructions and examples for Linux/macOS environments, especially for standalone clusters (e.g., how to upgrade cluster settings on Linux).
  • Mention Linux equivalents for Windows-specific tools (such as alternatives to Patch Orchestration Application for automating OS updates).
  • Provide parity in documentation structure by listing Linux/macOS procedures alongside Windows procedures, rather than Windows-first.
  • Clarify which steps or tools are cross-platform and which are Windows-only, to help users identify relevant guidance.
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 page presents a generally balanced overview of Service Fabric container support for both Linux and Windows. However, there are subtle signs of Windows bias: Windows container scenarios (e.g., IIS lift and shift) are described in more detail and referenced first in some lists; Windows-specific tools (IIS, Mirantis Container Runtime, DockerEE) are mentioned, while Linux equivalents are not elaborated. The page also links to Windows tutorials and resources before Linux ones in several places. There is no explicit PowerShell example, but the focus on Windows tools and scenarios may create friction for Linux users.
Recommendations
  • Ensure Linux tutorials and resources are listed before or alongside Windows equivalents.
  • Provide Linux-specific container scenarios (e.g., Apache/Nginx lift and shift) to match the IIS example for Windows.
  • Mention Linux container runtime alternatives (e.g., containerd, Podman) if supported, not just Docker.
  • Balance the detail level in scenario descriptions for both platforms.
  • Include explicit Linux command-line examples or references where Windows tools are mentioned.
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 generally presents a cross-platform workflow, but in the 'Open the application in VS Code' section, Windows instructions are presented before Linux instructions. There are no exclusive Windows tools or missing Linux examples; both platforms are covered for all critical steps.
Recommendations
  • Present Linux and Windows instructions in parallel (side-by-side or in tabs), or alternate which platform is listed first.
  • Explicitly mention macOS if supported, or clarify its parity with Linux.
  • Ensure that all screenshots and instructions are clearly marked for the relevant platform if there are differences.
GitHub Create Pull Request
Service Fabric Monitor Linux cluster events in Azure Service Fabric ...ervice-fabric/service-fabric-diagnostics-oms-syslog.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 focused on Linux clusters and Syslog integration, but several configuration parameters and consumer/producer names reference Windows-centric tools (e.g., AzureWinFabCsv, AzureWinFabCrashDump, AzureTableWinFabEtwQueryable, WinFabLttProducer). These are listed before the Linux-specific SyslogConsumer, and no Linux-native equivalents or explanations are provided for these Windows-named components. However, the main instructions and examples are Linux-focused, and there are no PowerShell or Windows-only command examples.
Recommendations
  • Clarify the purpose of Windows-named consumer/producer instances in the configuration and whether they are required or optional for Linux clusters.
  • Provide Linux-native equivalents or explicitly state which components are relevant only for Windows clusters.
  • Reorder configuration examples to list Linux-relevant components first, or separate Windows and Linux configuration sections for clarity.
  • Add a note explaining the cross-platform nature of Service Fabric diagnostics and which settings apply to Linux clusters.
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, as intended, but there are a few instances of Windows bias: the instructions for logging into Docker and building the image reference opening a PowerShell window, which is a Windows-specific tool. Additionally, the example commands are not always explicitly shown in a Linux shell context (e.g., 'Open a PowerShell window' instead of 'Open a terminal'). The 'Windows' option is listed before 'Linux' in the platform selector, and some references to Windows-specific patterns (such as named pipes) appear in generic configuration guidance.
Recommendations
  • Replace 'Open a PowerShell window' with 'Open a terminal window' or specify Linux shell usage.
  • Ensure all command-line examples use Linux shell syntax and context.
  • Move Linux before Windows in platform selectors when the page is Linux-focused.
  • Clarify any configuration instructions that mention Windows-specific tools or patterns, and provide Linux equivalents first or exclusively.
  • Audit for any lingering references to Windows tools (e.g., PowerShell, named pipes) and replace with Linux alternatives.
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_first
Summary
The documentation is focused on deploying Linux containers and uses Linux-centric commands and tools throughout. However, in the 'Clean up resources' section, Windows certificate management is described first and in more detail than the Linux/macOS equivalents, with a direct link to the MMC snap-in instructions. The Linux and Mac instructions are brief and lack direct links or step-by-step guidance. Additionally, PowerShell is mentioned as a Service Fabric management option in the 'Configure your environment' section, but is not used in examples.
Recommendations
  • Provide equally detailed instructions and direct links for certificate removal on Linux (e.g., using certutil or manual file removal) and macOS (Keychain Access).
  • When listing management tools, mention Linux/macOS options first or in parallel, and avoid putting Windows tools before their Linux equivalents.
  • Add step-by-step guidance for certificate management on Linux and macOS, similar to the Windows MMC instructions.
  • If mentioning PowerShell, clarify its cross-platform availability or provide Linux/macOS alternatives.
GitHub Create Pull Request
Service Fabric Create a Linux Service Fabric cluster in Azure ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-tutorial-create-vnet-and-linux-cluster.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_path_example ⚠ī¸ windows_file_path ⚠ī¸ windows_certificate_path
Summary
The documentation is focused on deploying a Linux Service Fabric cluster using Azure CLI and templates, and does not provide Windows-specific examples for the main task. However, several example commands use Windows-style file paths (e.g., C:\MyCertificates\MyCertificate.pem), which may confuse Linux/macOS users. There is a clear separation between Linux and Windows cluster creation, with a link to a separate Windows tutorial, and no PowerShell or Windows-only tools are used in the main instructions.
Recommendations
  • Provide Linux/macOS file path examples (e.g., /home/user/MyCertificates/MyCertificate.pem) alongside or instead of Windows-style paths.
  • Add a note clarifying that file paths should be adapted to the user's OS.
  • Ensure all CLI examples are OS-agnostic or provide both Windows and Linux/macOS variants where file paths are involved.
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: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page presents Windows information and tables before Linux, both in navigation and in detail. Windows OS versions are listed with lifecycle details, while Linux equivalents are only provided for Ubuntu and are placed after the Windows section. There are references to Windows-specific upgrade procedures and links, with Linux equivalents not always equally highlighted. The overall structure and ordering favor Windows users, though Linux information is present and reasonably complete.
Recommendations
  • Present Windows and Linux sections in parallel, or default to a neutral order (e.g., alphabetical) rather than Windows first.
  • Ensure upgrade procedures and links are equally highlighted for Linux, not just Windows.
  • Provide lifecycle tables for other supported Linux distributions if applicable, not just Ubuntu.
  • Review all cross-references and ensure Linux parity in guidance and linked documentation.
  • Add a summary table at the top comparing Windows and Linux support/features for quick reference.
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
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_heavy ⚠ī¸ minor_linux_example
Summary
The documentation page is titled and described as focusing on Windows Virtual Machine Scale Sets, but the main CLI examples use Linux images and Linux-specific extensions (Custom Script Extension for Linux, .sh scripts). However, the overall framing, title, and some references (such as the PowerShell link and batch file example for Linux) suggest a Windows-first approach. Linux is supported in the examples, but parity is not fully clear, and Linux-specific guidance is less prominent.
Recommendations
  • Update the title and description to clarify that the instructions apply to both Windows and Linux VMSS, or provide separate sections/examples for each OS.
  • Provide explicit examples for both Windows and Linux VMSS creation and disk encryption, including Windows-specific extensions and scripts where relevant.
  • Include clear guidance on OS-specific prerequisites and supported scenarios, referencing both Windows and Linux documentation equally.
  • Move or duplicate the Linux batch file example into the main body, not just as a 'next steps' link.
  • Ensure references to PowerShell and ARM templates are balanced with Bash/shell scripting and Linux automation options.
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 exhibits mild Windows bias by referencing Windows password requirements first and linking to a Windows-specific FAQ for password complexity. The Linux SSH key option is mentioned second, with its documentation link provided after the Windows reference. No explicit Linux-specific examples or screenshots are given, and the password requirements section is Windows-centric.
Recommendations
  • Present Linux and Windows options with equal prominence and order, e.g., 'For Windows, use a password; for Linux, use SSH keys or a password.'
  • Link to both Windows and Linux documentation for password and SSH key requirements, not just Windows.
  • Include Linux-specific screenshots or examples where relevant.
  • Clarify that password requirements apply to both Windows and Linux VMs, or specify differences if any.
  • Ensure that Linux users are not directed to Windows-only documentation for critical steps.
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
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 provides both Azure CLI and PowerShell examples for configuring diagnostic settings, but PowerShell (a Windows-centric tool) is given equal prominence as CLI. There is no explicit mention of Linux-specific tools or guidance, and the instructions for creating resources and querying logs are focused on the Azure portal, which is platform-agnostic but often associated with Windows environments. The absence of Bash or Linux shell-specific examples, and the lack of explicit Linux/macOS parity checks, indicate a mild Windows bias.
Recommendations
  • Add explicit Bash/Linux shell examples for configuring diagnostic settings (e.g., using az CLI from Bash).
  • Clarify that Azure CLI commands work cross-platform and provide any Linux/macOS-specific notes if needed.
  • Consider mentioning or linking to documentation for using Azure CLI on Linux/macOS.
  • If PowerShell is shown, also show Bash equivalents or note cross-platform PowerShell Core usage.
  • Explicitly state that all steps can be performed from Linux/macOS environments.
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 operating system support for application consistency with Windows listed first, followed by Linux. However, both platforms are covered with appropriate details and limitations. No examples, tools, or instructions are given in this page, so there is no evidence of PowerShell-heavy bias, missing Linux examples, or exclusive mention of Windows tools.
Recommendations
  • Consider listing Linux and Windows operating system support in parallel or alphabetically to avoid perceived prioritization.
  • Ensure that referenced 'Next steps' links (CLI, Portal, PowerShell) provide parity in instructions and examples for both Windows and Linux environments.
  • Explicitly mention that CLI instructions are cross-platform and highlight any platform-specific caveats if present.
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 both Azure CLI and Azure PowerShell examples for configuring and updating Spot Priority Mix, but PowerShell examples are always present and shown after CLI. There is no explicit mention of Linux/macOS shell scripting or tools, nor are Bash-specific instructions or cross-platform notes provided. The Azure CLI examples use Ubuntu images, but the CLI itself is cross-platform. The PowerShell examples may imply a Windows-centric audience, especially since Azure PowerShell is most commonly used on Windows. No Linux-specific tools or patterns are mentioned, and the documentation does not clarify CLI usage on Linux/macOS.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows.
  • Add Bash shell script examples for common tasks, or clarify that CLI examples are suitable for Bash/zsh.
  • Add a note about installing and using Azure CLI on Linux/macOS.
  • Consider moving CLI examples before PowerShell to reduce perceived Windows-first bias.
  • If relevant, mention cross-platform automation options (e.g., Terraform, Ansible) for advanced users.
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
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides example commands for Azure CLI, PowerShell, and REST API. PowerShell is featured as a primary example, which is a Windows-centric tool, and is presented immediately after the CLI example. There is no mention of Linux/macOS-specific shell usage (e.g., Bash), nor are there examples tailored for Linux environments (such as using curl for REST API calls or jq for parsing output). The CLI example is cross-platform, but the PowerShell example and its prominence indicate a mild Windows bias.
Recommendations
  • Add explicit Bash/Linux/macOS shell examples, such as using curl to query the REST API and jq to parse the output.
  • Clarify that Azure CLI works on Linux/macOS and Windows, and provide sample commands for those platforms (e.g., Bash syntax).
  • Consider reordering examples so that cross-platform tools (CLI, REST) appear before Windows-specific tools (PowerShell).
  • Add notes or links for Linux/macOS users about installing and using Azure CLI.
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: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation provides examples for Azure Portal, Azure CLI, and Azure PowerShell for all operations. While Azure CLI is cross-platform and shown before PowerShell, PowerShell examples are always present, and there are no explicit Bash or Linux shell script examples. Some troubleshooting links and migration steps reference Windows-specific documentation (e.g., converting unmanaged to managed disks and proximity placement group docs under 'windows'). This subtly prioritizes Windows tools and patterns, and may create friction for Linux/macOS users.
Recommendations
  • Add explicit Bash or Linux shell script examples where relevant, especially for common automation tasks.
  • Where documentation links reference Windows-specific guides (e.g., converting disks, proximity placement groups), provide equivalent Linux documentation links or clarify if the process is identical.
  • Clarify that Azure CLI commands are cross-platform and suitable for Linux/macOS users.
  • Consider adding a short section or callout for Linux/macOS users, highlighting any OS-specific considerations or best practices.
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 ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ minor_windows_config_notes
Summary
The documentation provides both Windows and Linux parity in terms of supported OS images and configuration methods (REST API, Azure CLI, PowerShell, ARM templates, Bicep). However, there are signs of Windows bias: PowerShell examples are given before CLI, ARM/Bicep template defaults use Windows images, and configuration notes often reference Windows-specific properties (e.g., enableAutomaticUpdates, drive letters) without equivalent Linux notes. Windows terminology and tools (PowerShell, Windows Update) are referenced more frequently and sometimes exclusively in requirements and troubleshooting sections.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or present CLI first to better serve Linux/macOS users.
  • In ARM/Bicep template examples, provide Linux image defaults alongside Windows defaults.
  • Add Linux-specific configuration notes where relevant (e.g., handling device naming, custom boot scripts for Linux).
  • Clarify that PowerShell is Windows-specific and recommend Azure CLI for cross-platform use.
  • Ensure troubleshooting and requirements sections include Linux equivalents (e.g., how Linux handles disk reattachment, patching, and health probes).
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 presents the Azure portal workflow for autoscaling VM Scale Sets in a platform-neutral way, but consistently references Azure PowerShell before Azure CLI when mentioning alternative methods. The 'Next steps' section links only to PowerShell-based management documentation, omitting CLI or Linux-native alternatives. This ordering and emphasis subtly prioritize Windows tools and workflows, potentially creating friction for Linux/macOS users.
Recommendations
  • When listing alternative methods, mention Azure CLI first or equally alongside PowerShell, as CLI is cross-platform and preferred by many Linux/macOS users.
  • In the 'Next steps' section, add links to equivalent Azure CLI documentation for managing VM Scale Sets.
  • Explicitly state that both PowerShell and CLI are supported on all platforms, and provide guidance for Linux/macOS users where relevant.
  • Consider including a brief comparison table or note highlighting platform compatibility for each tool.
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: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides examples for Azure Portal, Azure CLI, ARM Template, and PowerShell. PowerShell examples are given equal prominence to CLI, and PowerShell is a Windows-centric tool. In each major section (setting/updating policy, getting status, canceling, restarting), PowerShell examples are presented as a primary method alongside CLI, but there are no explicit Linux/macOS shell or scripting examples (e.g., Bash, Cloud Shell specifics). The CLI examples are cross-platform, but the presence and prominence of PowerShell throughout the documentation indicate a Windows bias. There is no mention of Linux-specific tooling or workflows, and PowerShell is listed before ARM Template in most cases.
Recommendations
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows equally, and consider showing Bash-specific usage (e.g., environment variables, piping, jq for JSON parsing).
  • Add explicit Bash or shell script examples for common operations, especially for status checking and automation.
  • Mention Azure Cloud Shell as a cross-platform option for both CLI and PowerShell, and clarify its OS-agnostic nature.
  • If PowerShell is shown, note that PowerShell Core is available on Linux/macOS, or provide links/instructions for Linux/macOS users.
  • Consider listing CLI (Bash) examples before PowerShell to reduce Windows-first perception.
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 examples for Azure Portal, Azure CLI, PowerShell, and ARM templates. While the CLI example is cross-platform, PowerShell is Windows-centric and is given equal prominence as CLI. There is no explicit Linux/macOS bias, but PowerShell is not natively available on Linux/macOS, and no Bash or shell script examples are provided. The ordering places PowerShell before ARM templates, which may subtly prioritize Windows workflows.
Recommendations
  • Clarify that Azure CLI works on Windows, Linux, and macOS, and is the recommended cross-platform tool.
  • Consider providing Bash or shell script examples for Linux/macOS users, especially for automation scenarios.
  • Note that PowerShell Core is available on Linux/macOS, but most users on those platforms prefer CLI or Bash.
  • Reorder examples to put CLI before PowerShell, emphasizing cross-platform parity.
  • Add a brief section or note about tool availability and platform compatibility.
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
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides parity across Azure Portal, CLI, PowerShell, and REST API. However, PowerShell is given a dedicated section, and the 'Next steps' section lists Azure CLI before PowerShell, but the presence of a PowerShell tab and examples may indicate a slight Windows bias. There are no Linux/macOS-specific instructions or notes, but the Azure CLI example is cross-platform. No critical tasks are Windows-only.
Recommendations
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows to reassure non-Windows users.
  • Add a note clarifying that PowerShell examples are for users on Windows or those who have PowerShell Core installed on Linux/macOS.
  • Consider including Bash or shell scripting examples for common automation scenarios, or at least reference that Azure CLI is the recommended cross-platform tool.
  • If possible, add a short section or FAQ addressing platform compatibility for each method.
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 presents both Azure PowerShell and Azure CLI examples for configuring scale-in policies, but PowerShell (a Windows-centric tool) is shown before CLI in each section. There are no Linux/macOS-specific shell examples (e.g., Bash scripts), and PowerShell is highlighted as a primary method, which may create friction for Linux/macOS users who typically use CLI or ARM templates. However, Azure CLI and ARM template examples are present and fully functional for Linux/macOS users.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and preferred by many Linux/macOS users.
  • Explicitly note that Azure CLI commands work on Linux/macOS and Windows, while PowerShell is primarily for Windows.
  • Add Bash script examples for common tasks to further support Linux/macOS users.
  • Clarify in introductory sections that all operations can be performed using CLI, ARM templates, or REST API, not just 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, CLI, PowerShell, and REST API. The PowerShell example is given equal prominence to the CLI example, but PowerShell is a Windows-centric tool. The ordering of examples places PowerShell before REST API, and the CLI example does not explicitly mention Linux or macOS usage, nor does it provide any Linux-specific context. There is no explicit Windows-only bias, but the inclusion and prominence of PowerShell may create a subtle Windows bias.
Recommendations
  • Clarify that Azure CLI commands are cross-platform and can be used on Linux, macOS, and Windows.
  • Add notes or examples showing CLI usage on Linux/macOS terminals (e.g., bash), including any OS-specific considerations.
  • Consider moving PowerShell examples after CLI and REST API, or label them as Windows-specific.
  • If there are any differences in behavior or prerequisites for Linux/macOS users, document them explicitly.
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 page demonstrates mild Windows bias. Windows examples and terminology (such as 'WindowsAttestation' publisher, PowerShell tab, and Windows error messages) are presented before or more prominently than Linux equivalents. The troubleshooting section references Windows-specific extension names and error messages, and PowerShell is given its own tab, while Linux CLI examples are not as detailed. However, Linux parity is maintained in the template section, and CLI instructions are generally OS-neutral.
Recommendations
  • Ensure Linux and macOS examples are presented with equal prominence and detail as Windows examples.
  • In troubleshooting sections, include Linux-specific error messages and extension names (e.g., 'LinuxAttestation') where relevant.
  • Provide Bash or shell script examples alongside PowerShell, especially in sections where PowerShell is highlighted.
  • Avoid using Windows extension names or terminology exclusively in generic error messages; clarify when errors apply to both platforms.
  • Explicitly mention macOS support or limitations if 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_first ⚠ī¸ powershell_heavy
Summary
The documentation page is generally cross-platform, but in the Load Balancer section, PowerShell is mentioned before CLI, and both are linked as quickstart options. This ordering may subtly favor Windows users, as PowerShell is primarily a Windows tool, though it is available cross-platform. No Linux-specific tools (such as Bash or shell scripts) are mentioned, and examples are not shown for Linux commands. The rest of the page is neutral and covers both Linux and Windows VMs equally.
Recommendations
  • List CLI examples before PowerShell to avoid implicit Windows-first bias.
  • Explicitly mention Bash or shell script options for Linux users where relevant.
  • Provide example commands for both Linux (Bash/CLI) and Windows (PowerShell) in sections involving VM management or load balancing.
  • Clarify that PowerShell is available cross-platform, but CLI is often preferred on Linux.
GitHub Create Pull Request
Virtual Machines Azure boot diagnostics ...lob/main/articles/virtual-machines/boot-diagnostics.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 Windows and Linux coverage, but there is a subtle Windows bias: PowerShell is given its own section for enabling boot diagnostics, while Linux users must infer that the CLI section applies to them. Additionally, references to troubleshooting with the Serial Console link to a Windows-specific page, and PowerShell is mentioned before ARM templates, which are platform-neutral. No Linux-specific tools or examples are provided.
Recommendations
  • Add explicit Bash or Linux shell examples for enabling boot diagnostics, alongside PowerShell.
  • Clarify that Azure CLI instructions apply to both Windows and Linux users.
  • Provide links to Linux-specific troubleshooting guides for Serial Console and boot diagnostics.
  • Ensure that references to platform-specific tools (e.g., PowerShell) are balanced with Linux alternatives.
GitHub Create Pull Request
Virtual Machines Create a capacity reservation in Azure ...ticles/virtual-machines/capacity-reservation-create.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 examples for Azure Portal, Azure CLI, and Azure PowerShell for all major operations. However, PowerShell is given equal prominence to CLI, despite being primarily a Windows tool, and PowerShell examples are detailed and referenced with links to specific cmdlets. There is a slight Windows bias in the inclusion and emphasis of PowerShell, which is not natively available on Linux/macOS (though it can be installed). The CLI examples are cross-platform, but PowerShell is often presented as a first-class option, which may create friction for Linux/macOS users. No Linux/macOS-specific tools or shell examples (e.g., Bash scripts) are provided, and PowerShell is mentioned before CLI in some sections.
Recommendations
  • Clarify that Azure CLI is the recommended cross-platform tool for scripting and automation, and mention that PowerShell is primarily for Windows users (with installation instructions for Linux/macOS if referenced).
  • Ensure CLI examples are shown before PowerShell in tabbed sections to reinforce CLI as the default for non-Windows platforms.
  • Add Bash script equivalents for common operations, or provide notes for Linux/macOS users on how to adapt CLI commands in shell scripts.
  • Explicitly state the cross-platform nature of Azure CLI and ARM templates, and provide links to installation guides for Linux/macOS.
  • Consider reducing the prominence of PowerShell unless there are Windows-specific steps.
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
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 API, Azure CLI, PowerShell, and Portal instructions for removing a VM scale set association from a capacity reservation group. PowerShell examples are given equal prominence to CLI, and explicit references to Azure PowerShell cmdlets are included. PowerShell is a Windows-centric tool, and its inclusion as a primary method (with detailed examples and links) reflects a Windows bias. Additionally, the CLI examples use Azure CLI, which is cross-platform, but PowerShell is mentioned before Portal in the tab order, and the documentation links to PowerShell modules without similar links for Bash or Linux shell scripting. There are no Bash or Linux shell script examples, nor are there references to Linux-specific tools or workflows.
Recommendations
  • Add Bash or Linux shell script examples where appropriate, especially for users who prefer scripting outside Azure CLI.
  • Clarify that Azure CLI is cross-platform and can be used on Linux/macOS equally.
  • Provide links to Azure CLI documentation similar to the PowerShell links.
  • Consider reordering tabs so that CLI appears before PowerShell, or alternate tab order based on detected platform.
  • Explicitly mention Linux/macOS compatibility in the CLI sections.
GitHub Create Pull Request
Virtual Machines Remove a virtual machine association from a capacity reservation group ...les/virtual-machines/capacity-reservation-remove-vm.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 parity between Azure CLI and PowerShell examples, but PowerShell (a Windows-centric tool) is given equal prominence to CLI, and is referenced with additional command links. There is a slight bias toward Windows tooling, as PowerShell is not natively available on Linux/macOS and is traditionally associated with Windows environments. The documentation also references Azure PowerShell commands in 'Learn more' sections, but does not offer equivalent Bash or shell scripting resources for Linux/macOS users. The ordering of tabs (API, Portal, CLI, PowerShell) puts PowerShell before Bash or Linux-specific examples, which may subtly prioritize Windows workflows.
Recommendations
  • Clarify that Azure CLI commands work cross-platform (Windows, Linux, macOS) and recommend it as the default for non-Windows users.
  • Add explicit Bash or shell scripting examples for Linux/macOS users, especially for automation scenarios.
  • In 'Learn more' sections, provide links to Azure CLI documentation alongside PowerShell references.
  • Consider reordering tabs so CLI appears before PowerShell, or add a note about platform compatibility.
  • Mention that PowerShell Core is available on Linux/macOS, but CLI is often more familiar for Linux users.
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 demonstrates mild Windows bias. Windows-specific recommendations (e.g., 'Use at least B2 for Windows machines', Azure Hybrid Benefit for Windows Server) are mentioned without equivalent Linux guidance. Windows licensing optimization is discussed, but no Linux licensing or cost-saving features are highlighted. In some cases, Windows is mentioned before Linux (e.g., VM size pricing links), and Linux-specific examples or parity are missing for automation and cost-saving strategies.
Recommendations
  • Include Linux-specific cost optimization tips, such as leveraging reserved instances, optimizing OS licensing, or using open-source automation tools.
  • When mentioning VM sizes or pricing, present Windows and Linux options together or alternate which is listed first.
  • Discuss Linux equivalents for Azure Hybrid Benefit, or clarify if none exist.
  • Provide automation examples relevant to Linux environments (e.g., using cron jobs, cloud-init, or Ansible for VM scheduling/shutdown).
  • Ensure parity in recommendations for both Windows and Linux, especially in sections about licensing, automation, and VM selection.
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 mild Windows bias. References to PowerShell and Windows tools are present before Linux equivalents, and links to configuration instructions list PowerShell before CLI or ARM templates. Examples for configuring VM watch are platform-neutral (JSON), but troubleshooting/logging instructions are split by OS only at the end. There are no explicit Linux/macOS command-line examples, and the overall flow assumes familiarity with Windows patterns.
Recommendations
  • Ensure that Azure CLI and ARM template instructions are listed before or alongside PowerShell, not after.
  • Provide explicit Linux/macOS command-line examples (e.g., using Azure CLI on Linux, bash environment variable settings) where relevant.
  • Where screenshots or tool references are given, include both Windows and Linux/macOS equivalents (e.g., Azure CLI output on Linux terminal).
  • In troubleshooting sections, provide parity in log file locations and diagnostic steps for both platforms, and consider including sample commands for viewing logs (e.g., 'cat' for Linux, 'type' for Windows).
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. However, PowerShell is included as a top-level example for creating a gallery, while there is no equivalent example for Bash scripting or Linux-native tools. The order of examples also places PowerShell before REST, and the CLI examples use generic syntax but do not explicitly mention Linux/macOS compatibility. This subtly prioritizes Windows/PowerShell users and may create friction for Linux/macOS users.
Recommendations
  • Add explicit Bash shell scripting examples alongside PowerShell, especially for resource creation tasks.
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows, and provide OS-specific notes or examples where relevant.
  • Reorder example tabs so that CLI (cross-platform) appears before PowerShell, or group PowerShell and Bash together as scripting options.
  • Where PowerShell is shown, offer a Bash/Linux shell alternative for parity.
  • Explicitly mention that REST API calls are OS-agnostic and can be used from any platform.
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 a mild Windows bias by referencing PowerShell and Windows-specific installation instructions before Linux alternatives. The PowerShell section links only to Windows installation instructions, and PowerShell is presented before Azure CLI in some places. However, Azure CLI examples are provided, and no critical steps are Windows-only.
Recommendations
  • Add explicit instructions or links for installing Azure PowerShell on Linux/macOS.
  • Ensure parity in example ordering: present Azure CLI and PowerShell examples side-by-side or alternate which comes first.
  • Clarify that both Azure CLI and PowerShell work cross-platform, and provide troubleshooting tips for Linux/macOS users.
  • Where possible, avoid language like 'Install Azure PowerShell on Windows' and use 'Install Azure PowerShell' with platform-specific links.
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, but introduces DiskSpd (Windows) before FIO (Linux) and links to DiskSpd first. The description of benchmarking tools starts with the Windows tool, and the overall tone and ordering slightly favor Windows. However, both platforms are acknowledged and tools for each are named and linked.
Recommendations
  • Present Linux and Windows tools in parallel, e.g., 'We have used common benchmarking tools: FIO for Linux and DiskSpd for Windows.'
  • Alternate the order of tool presentation or use a table to show parity.
  • Provide explicit example commands for both FIO (Linux) and DiskSpd (Windows) in the main documentation, not just in linked includes.
  • Ensure that any referenced steps or linked articles also provide Linux-specific guidance.
  • Add a note clarifying that both platforms are equally supported and that examples for both are available.
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: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page provides both Windows (PowerShell) and Linux (CLI) references for enabling encryption features, but there is a consistent pattern of listing Windows/PowerShell examples and links before Linux/CLI equivalents. Some references, such as to the Cryptography API: Next Generation, are Windows-specific. The main walkthroughs and 'Next steps' sections repeatedly mention PowerShell before CLI, and some deep links for advanced features (e.g., automatic key rotation) point to Windows/PowerShell guides first. There is no outright omission of Linux instructions, but the ordering and tool emphasis suggest a Windows-centric approach.
Recommendations
  • Alternate the order of Windows and Linux examples and links throughout the documentation, or present them side-by-side.
  • Provide equal prominence and detail for both Azure PowerShell and Azure CLI instructions, ensuring Linux users do not need to scroll past Windows content to find relevant guidance.
  • Where referencing platform-specific cryptography APIs (e.g., CNG for Windows), also mention Linux equivalents (e.g., dm-crypt, cryptsetup) or clarify their relevance.
  • Ensure that deep links for advanced features (e.g., automatic key rotation) are available for both PowerShell and CLI, and referenced equally.
  • Consider adding explicit callouts or sections for Linux/macOS users where workflows or tooling differ.
GitHub Create Pull Request
Virtual Machines Migrate Standard HDD OS disks by September 08, 2028 ...n/articles/virtual-machines/disks-hdd-os-retirement.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 PowerShell and Azure CLI examples for listing affected disks, but the PowerShell example is presented first, and the command syntax is more detailed for PowerShell. The use of 'Disk Storage Center' (a portal tool) is platform-agnostic, but the overall pattern prioritizes Windows-centric tools and examples before Linux equivalents. There is no explicit Linux shell example (e.g., Bash), and the CLI example is less prominent.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and preferred by many Linux/macOS users.
  • Include explicit Bash shell examples for Linux users, showing how to use Azure CLI in a Linux terminal.
  • Clarify that both CLI and PowerShell are available on all platforms, and link to installation guides for Linux/macOS users.
  • Add a note or section specifically addressing Linux/macOS users, highlighting any differences or considerations.
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_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation provides both Azure CLI and PowerShell examples for all tasks, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and is presented before the Azure portal steps. There is a slight 'windows_first' bias in the order and prominence of PowerShell, and the use of PowerShell-specific instructions may be less familiar to Linux/macOS users. However, Azure CLI examples are present and fully functional for Linux/macOS users. No critical steps are Windows-only, and Linux is explicitly supported.
Recommendations
  • Consider listing Azure CLI examples before PowerShell in each section, as CLI is cross-platform and more natural for Linux/macOS users.
  • Add explicit notes clarifying that Azure CLI commands work natively on Linux/macOS, while PowerShell may require installation.
  • Where possible, provide bash-specific tips or troubleshooting for Linux users (e.g., environment variable usage, shell differences).
  • Ensure screenshots and portal instructions do not use Windows-specific terminology or UI elements.
  • Highlight Linux parity in the introduction, reassuring users that all steps are cross-platform.
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 feature and update summary, but there are several instances of Windows bias. Windows links and examples are sometimes listed before Linux equivalents (e.g., expanding disks without downtime), and some references point to Windows-specific documentation or tools (such as PowerShell and Windows disk management articles) without equal Linux coverage. In some cases, Linux examples are missing or referenced only as secondary options.
Recommendations
  • Ensure that all feature documentation links reference both Windows and Linux guides equally, ideally side-by-side.
  • Avoid listing Windows examples or documentation before Linux equivalents; use neutral ordering or group by OS.
  • Where Windows tools (e.g., PowerShell) are mentioned, also mention Linux tools (e.g., Bash, CLI) and provide equivalent instructions.
  • Audit linked articles to confirm Linux parity and update this summary page to clarify when features or instructions differ by OS.
GitHub Create Pull Request
Virtual Machines Deploy Ephemeral OS disks ...articles/virtual-machines/ephemeral-os-disks-deploy.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ minor_windows_example
Summary
The documentation provides a balanced overview of deploying ephemeral OS disks using multiple methods (Portal, ARM template, CLI, REST, PowerShell). However, there is a mild Windows bias: PowerShell (a Windows-centric tool) is given its own section with detailed examples, while Linux-native scripting tools (like Bash) are not. In the ARM template example for VMs, the image reference is for Windows Server by default, and no explicit Linux image example is shown. The CLI section is platform-neutral, but PowerShell is highlighted separately. No Linux-specific tools or workflows are mentioned.
Recommendations
  • Add explicit Linux image references in ARM template examples (e.g., Ubuntu or CentOS) alongside the Windows example.
  • Include Bash scripting examples for Linux users where PowerShell is shown.
  • Clarify that the Azure CLI commands work cross-platform and are recommended for Linux/macOS users.
  • If PowerShell is given a dedicated section, consider adding a Bash or shell scripting section for parity.
  • Mention that Azure PowerShell is available cross-platform, but CLI is often preferred on Linux/macOS.
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 overwhelmingly Linux-focused, as expected for the Azure Linux VM Agent. However, there is a minor Windows bias in the section describing SSH key types, where *putty.exe* (a Windows SSH client) is mentioned as not supporting ecdsa keys, and users are advised to use rsa or dsa if connecting from Windows. Additionally, in the Ubuntu Cloud Images section, a link to a Windows VM deployment tutorial is included alongside Linux resources, which may be confusing or unnecessary for Linux users.
Recommendations
  • Move or rephrase the mention of *putty.exe* so that Windows-specific advice is in a dedicated interoperability section, not in the main Linux configuration documentation.
  • Remove or clarify the link to the Windows VM deployment tutorial in the Ubuntu Cloud Images section. If the link is relevant for cross-platform automation, explain its purpose; otherwise, replace it with a Linux-specific resource.
  • When discussing SSH key types, provide parity by mentioning popular Linux SSH clients and their supported key types.
  • Ensure that all examples and references are Linux-centric unless explicitly discussing cross-platform scenarios.
GitHub Create Pull Request
Virtual Machines Azure Compute - Linux diagnostic extension 4.0 ...icles/virtual-machines/extensions/diagnostics-linux.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 Linux, but there are several instances of Windows bias. PowerShell examples are given alongside Azure CLI, sometimes with more detail. Windows terminology and links (such as 'Configure managed identities' pointing to Windows VM docs) appear before or instead of Linux equivalents. Windows tools like Visual Studio Server Explorer are mentioned before cross-platform alternatives. However, Linux users can complete all tasks, and Linux-specific instructions are present.
Recommendations
  • Ensure Linux examples (Azure CLI, bash) are presented before or at least equally with PowerShell, especially in installation and configuration sections.
  • Replace or supplement Windows-centric links (e.g., 'Configure managed identities' for Windows VM) with Linux-specific documentation.
  • Mention cross-platform tools (e.g., Azure Storage Explorer) before Windows-only tools like Visual Studio Server Explorer.
  • Clarify when instructions or screenshots apply to Linux VMs, and avoid referencing Windows VM docs unless strictly necessary.
  • Review all sample code and ensure parity in detail and explanation between CLI and PowerShell examples.
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 Azure CLI and ARM template examples, but PowerShell is featured prominently for deployment and troubleshooting. PowerShell is a Windows-centric tool, and its inclusion may suggest a Windows-first workflow, even though the extension is for Linux. However, Linux-native tools (Azure CLI, bash log paths) are also covered, and no critical steps are Windows-only.
Recommendations
  • Move Azure CLI examples before PowerShell examples to prioritize Linux-native workflows.
  • Explicitly mention that PowerShell can be used on Linux/macOS, or provide Bash/Cloud Shell alternatives for all PowerShell commands.
  • Add more context for Linux users about using Azure CLI and bash scripting for automation.
  • Clarify that the extension is not installable via native Linux package managers (apt, yum) to avoid confusion.
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: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation generally maintains parity between Windows and Linux, but there are subtle signs of Windows bias. Windows tools (PowerShell) are mentioned before Linux equivalents (Azure CLI), and troubleshooting guidance for Windows VM extensions is called out before Linux. In some sections, Windows examples or terminology appear first, which may create a perception of Windows being the primary platform.
Recommendations
  • Alternate the order of Windows and Linux references throughout the documentation, or present Linux examples first in some sections.
  • Explicitly mention Linux management tools (e.g., Azure CLI, SSH) before or alongside PowerShell when listing extension management options.
  • Provide direct troubleshooting links for Linux VM extensions in the same way as for Windows.
  • Ensure that all extension examples and lifecycle instructions include both Linux and Windows commands/scripts, or link to them equally.
  • Review and balance the order of 'Next steps' links so Linux and Windows are treated equally.
GitHub Create Pull Request
Virtual Machines Qualys Cloud Agent Extension for Azure VMs ...ob/main/articles/virtual-machines/extensions/qualys.md
Low 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, and highlights PowerShell as a deployment tool for both Windows and Linux, which may not be the most natural or common tool for Linux users. However, Linux deployment methods are present and linked, and alternative Linux-native tools (like Ansible) are mentioned.
Recommendations
  • Alternate the order of Windows and Linux examples/links to avoid always listing Windows first.
  • When describing PowerShell as a deployment method for Linux, clarify that native Linux shell options (bash, sh) are also supported if applicable, or provide equivalent bash/CLI examples.
  • Explicitly mention and link to Linux-native deployment methods (e.g., bash scripts, cloud-init) alongside PowerShell.
  • Where possible, provide side-by-side code snippets for both Windows (PowerShell) and Linux (bash) in the main documentation body, not just via external links.
GitHub Create Pull Request
Virtual Machines Use Application Health extension with Azure Virtual Machines ...ticles/virtual-machines/extensions/health-extension.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 frequently presents Windows-based examples first, especially in REST API and PowerShell sections, with explicit references to 'ApplicationHealthWindows' and Windows VM scenarios. PowerShell (a Windows-centric tool) is given its own section with detailed examples, while Linux examples are only provided in Azure CLI sections and are not as prominent. The troubleshooting/logging section lists Windows log paths before Linux equivalents. Overall, there is a subtle but consistent prioritization of Windows tools and patterns throughout the page.
Recommendations
  • Alternate the order of Windows and Linux examples so that Linux is shown first in some sections.
  • Provide parity in example detail for both Windows and Linux, including explicit Linux VM scenarios in REST API and PowerShell sections (where possible).
  • Add Bash scripting examples for Linux users alongside PowerShell, or clarify that PowerShell Core can be used cross-platform.
  • List Linux log paths before or alongside Windows paths in troubleshooting sections.
  • Explicitly mention macOS compatibility or usage where relevant, especially for CLI tools.
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_macos_example
Summary
The documentation generally maintains cross-platform neutrality, with explicit applicability to both Linux and Windows VMs. However, there is a subtle Windows bias: Windows Server is listed first and is the only OS called out in the 'Recommended OS for Performance' row, and the only explicit recommendation for performance is Windows Server 2019+. Linux distributions are listed for SRIOV RDMA support, but no Linux distribution is recommended for performance. There are no macOS examples or mentions. All command-line topology examples use Linux tools (lstopo), not Windows or PowerShell, which is positive for Linux parity.
Recommendations
  • Add a recommended Linux distribution for performance, or clarify if Windows Server 2019+ is uniquely recommended.
  • List Linux distributions first or equally in tables and recommendations.
  • If possible, provide equivalent Windows tooling or commands for topology inspection, or clarify that lstopo is available on Windows via WSL or other means.
  • Explicitly mention macOS support status if relevant, or clarify that macOS is not supported.
GitHub Create Pull Request
Virtual Machines Azure VM Image Builder overview ...in/articles/virtual-machines/image-builder-overview.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_baseline_reference ⚠ī¸ powershell_heavy ⚠ī¸ minor_windows_tools
Summary
The documentation generally maintains OS parity, but there are subtle signs of Windows bias: Windows security baseline is referenced explicitly while Linux equivalents are not; PowerShell is often mentioned first in command examples and permissions configuration; and some references to Windows-specific tools (Sysprep) and features appear before Linux alternatives. However, Linux is supported throughout, and CLI examples are provided alongside PowerShell.
Recommendations
  • Explicitly mention Linux security baseline options or reference equivalent Linux hardening templates.
  • Alternate the order of PowerShell and CLI examples, or present CLI first to reflect cross-platform usage.
  • Provide Linux-specific configuration and customization examples where Windows-specific tools (like Sysprep) are mentioned.
  • Ensure that documentation links and references for Linux image building are as prominent as those for Windows.
  • Add references to Linux configuration management tools (e.g., cloud-init, Ansible) alongside Windows tools.
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 presents both PowerShell and Azure CLI examples, but PowerShell (a Windows-centric tool) is listed before CLI in both role assignment and disk update instructions. This ordering subtly prioritizes Windows workflows. There are no explicit Linux/macOS examples or notes, and no mention of platform-specific considerations for CLI usage on non-Windows systems.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or present CLI examples first to better support Linux/macOS users.
  • Explicitly mention that Azure CLI works cross-platform and provide installation/use links for Linux/macOS.
  • Add notes or examples for Linux/macOS environments where relevant, such as shell syntax or authentication differences.
  • Consider including Bash or other Linux-native scripting examples if applicable.
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
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation consistently lists Azure PowerShell as a primary tool alongside REST API and Azure CLI, and refers to the Azure PowerShell module by name and link in every example. This creates a subtle Windows bias, as PowerShell is traditionally a Windows-centric tool, even though cross-platform support exists. The PowerShell option is always mentioned, sometimes before or alongside CLI, but never after a Linux-specific tool. No Linux/macOS-specific examples or shell scripts are provided.
Recommendations
  • Explicitly note that Azure CLI is fully cross-platform and provide Bash or shell script examples for Linux/macOS users.
  • Clarify that PowerShell Core is available on Linux/macOS, or link to installation instructions for non-Windows platforms.
  • Consider listing Azure CLI before PowerShell in examples, or alternate the order to avoid implicit prioritization.
  • Add a note or section for Linux/macOS users, highlighting any differences or best practices.
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 examples and explanations before Linux (FIO) equivalents. Both platforms are covered with detailed, parity examples, but Windows is introduced first and in greater detail initially, which may create a perception of Windows prioritization.
Recommendations
  • Present Linux and Windows benchmarking tools in parallel, or alternate which platform is introduced first.
  • Add a short comparison table at the top showing both DISKSPD and FIO, their platforms, and installation commands.
  • Ensure equal detail and prominence for both sets of examples, including introductory context and explanations.
  • Explicitly state that both Windows and Linux are supported and provide links to further resources for each.
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: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation provides parity between Linux/macOS and Windows users by offering separate tabs for each platform, with clear instructions and examples. However, in the Windows section, the host fingerprint validation step uses a PowerShell/Azure PowerShell command (Invoke-AzVMRunCommand), while the Linux/macOS section uses a direct SSH command. This introduces a slight bias towards Windows tools and PowerShell, as Linux users may not be shown an equivalent Azure CLI method for host fingerprint retrieval. Additionally, the Windows section references PowerShell and cmd.exe, but does not mention third-party SSH clients for Windows.
Recommendations
  • Provide an Azure CLI example for host fingerprint retrieval in the Linux/macOS section, similar to the PowerShell example in the Windows section.
  • Mention third-party SSH clients for Windows (e.g., PuTTY, MobaXterm) for users who prefer alternatives to cmd.exe/PowerShell.
  • Ensure troubleshooting steps and advanced scenarios (e.g., Bastion, file transfer) include both Azure CLI and PowerShell options for all platforms.
  • Consider listing Linux/macOS instructions before Windows instructions in general documentation, unless usage statistics justify otherwise.
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 and Linux examples for all core operations, but consistently lists Windows (PowerShell) examples before Linux (bash/curl) ones. In troubleshooting and routing sections, Windows tools (route print, ipconfig, PowerShell CLI) are described in greater detail and appear first, with Linux equivalents following. Some advanced PowerShell scripting is shown for Windows, while Linux examples are simpler. The documentation does not omit Linux examples, but the ordering and depth of Windows coverage indicate a mild Windows bias.
Recommendations
  • Alternate the order of Windows and Linux examples so Linux is shown first in some sections.
  • Provide equally detailed troubleshooting steps for Linux, including advanced commands and scripting where appropriate.
  • Ensure Linux tools (e.g., netstat, ip, ifconfig, nmcli) are referenced with the same depth as Windows tools.
  • Where PowerShell scripting is shown, consider providing equivalent bash or Python scripting for Linux.
  • Explicitly mention macOS compatibility and provide examples where Linux commands would work on macOS.
GitHub Create Pull Request
Virtual Machines Prepare Linux for imaging ...ticles/virtual-machines/linux/create-upload-generic.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 focused on preparing Linux for imaging in Azure, but it exhibits some Windows bias in the sections discussing disk conversion and resizing. Windows tools (Hyper-V Manager, Convert-VHD, Resize-VHD PowerShell cmdlets) are mentioned first and in detail, with Linux alternatives (qemu-img, vbox-manage) presented afterward. The explanations and examples for Linux tools are present and fairly comprehensive, but the initial framing and tool recommendations prioritize Windows environments.
Recommendations
  • Present Linux-native tools (qemu-img, vbox-manage) before or alongside Windows tools when discussing disk conversion and resizing.
  • Provide explicit step-by-step guides for Linux users for all disk operations, matching the detail given for Windows tools.
  • Clarify that all required steps can be completed fully on Linux, and highlight any platform-specific caveats or bugs (as is done for qemu-img).
  • Consider adding a summary table comparing Windows and Linux toolchains for common imaging tasks.
  • Ensure that Linux examples are not only present but also given equal prominence and clarity as Windows examples.
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 page is generally Linux-focused, but there is mild Windows bias in the 'Prerequisites' and 'Installation notes' sections. Hyper-V (a Windows tool) is mentioned as the only example for creating VHDs, and instructions for converting disk formats reference Hyper-V Manager and the Windows-only convert-vhd cmdlet before Linux alternatives. However, the main workflow and examples are entirely Linux-based, and Linux tools (qemu-img, azcopy, etc.) are used throughout.
Recommendations
  • In the 'Prerequisites' section, mention Linux-native tools (e.g., qemu-img, VBoxManage, dd) for creating VHDs alongside Hyper-V.
  • In 'Installation notes', provide Linux commands for converting disk formats (e.g., qemu-img convert) before or alongside Windows/Hyper-V instructions.
  • Clarify that Hyper-V is just one of several options and link to Linux-based VHD creation guides.
  • Consider reordering examples so Linux tools are presented first, given the Linux context of the page.
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 section, where only a Windows-style AzCopy command ('AzCopy.exe') with a Windows file path is shown, and no explicit Linux/macOS AzCopy example is provided. The use of 'AzCopy.exe' and Windows paths may confuse Linux/macOS users. However, the rest of the CLI instructions and scripting are cross-platform and use bash syntax, which is more Linux/macOS friendly.
Recommendations
  • Add a Linux/macOS AzCopy example (e.g., 'azcopy copy /home/user/mydisk.vhd ...') alongside the Windows example.
  • Clarify that AzCopy is available for Linux/macOS and provide installation instructions or a link for those platforms.
  • Use platform-neutral file paths in examples, or provide both Windows and Linux/macOS paths.
  • Explicitly mention that the CLI and AzCopy commands work on Linux/macOS, not just Windows.
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 consistently presented alongside or immediately after CLI examples, and sometimes with more detail. The REST API is also covered. There is no evidence of missing Linux-specific examples or exclusive use of Windows tools, but the prominence of PowerShell (a Windows-centric tool) and its parity with CLI may create minor friction for Linux/macOS users, especially as PowerShell is less commonly used on those platforms.
Recommendations
  • Present Azure CLI examples before PowerShell examples in all sections, as CLI is more native to Linux/macOS.
  • Clearly indicate that PowerShell is optional and primarily relevant for users who have it installed on Linux/macOS.
  • Add explicit notes or links for installing/configuring PowerShell on Linux/macOS if PowerShell examples are retained.
  • Consider providing Bash script examples for guest OS configuration steps, especially where CLI is used.
  • Review screenshots and UI references to ensure they do not assume a Windows environment.
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 presents both Windows and Linux options, but Windows examples and tools (PowerShell) are frequently mentioned first or in parallel, sometimes with more prominence. PowerShell examples are provided for most tasks, and Windows-specific configuration notes (e.g., WinRM) are highlighted. However, Linux parity is generally maintained with CLI examples and links.
Recommendations
  • Alternate the order of Windows and Linux examples so Linux is sometimes presented first.
  • Ensure Linux-specific notes (e.g., SSH configuration) are included where Windows-specific notes (e.g., WinRM) are present.
  • Add Bash or shell script examples alongside PowerShell where appropriate.
  • Clarify that Azure CLI is cross-platform and highlight its use for both Linux and Windows.
  • Review linked example pages to ensure Linux instructions are as detailed as Windows ones.
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, the PowerShell example is included alongside the CLI example, which may suggest a slight Windows bias, especially since PowerShell is primarily a Windows tool (though now cross-platform). The CLI example is shown first, which helps reduce bias. No explicit Windows-only tools or instructions are present, and all Terraform code is platform-agnostic. There are no missing Linux/macOS examples, and no Windows-specific patterns or tools are mentioned elsewhere.
Recommendations
  • Clarify that Azure PowerShell is available cross-platform, or note its primary use on Windows.
  • Consider explicitly mentioning that all steps (including verification and cleanup) can be performed on Linux/macOS using the Azure CLI.
  • If possible, add a Bash script example for verification to further reinforce Linux parity.
  • Ensure that any references to PowerShell do not imply Windows exclusivity.
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: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides instructions for connecting to the VM via SSH, mentioning Windows/PowerShell first and giving explicit instructions for Windows users before Linux/macOS. The use of PowerShell is referenced for Windows, while Bash is referenced for Linux/macOS. However, the rest of the documentation is focused on Linux VMs, and installation instructions are provided for multiple Linux distributions. There are no Windows-only tools or patterns, and Linux users are able to complete all tasks.
Recommendations
  • Present connection instructions for Linux/macOS and Windows in parallel, rather than mentioning Windows/PowerShell first.
  • Explicitly mention that Linux/macOS users can use the terminal directly, and provide equal detail for both platforms.
  • Consider providing screenshots or command examples for both Bash and PowerShell, or clarify that the SSH command is the same across platforms.
  • Avoid language that prioritizes Windows users (e.g., 'If you're on a Windows machine...' before 'If you're on a Mac or Linux machine...').
GitHub Create Pull Request
Virtual Machines Scheduled Events for Linux VMs in Azure ...in/articles/virtual-machines/linux/scheduled-events.md
Low 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 Bash and Python examples, but PowerShell samples are included and are consistently presented before Linux Bash equivalents in code blocks. This ordering may subtly prioritize Windows tooling, despite the Linux context. There are no sections that are Windows-only, and Linux users can complete all tasks, but the inclusion and ordering of PowerShell examples may create minor friction for Linux/macOS users.
Recommendations
  • List Bash (Linux) examples before PowerShell in all code blocks to reinforce Linux-first orientation.
  • Clearly mark PowerShell examples as 'for Windows users' and Bash as 'for Linux/macOS users'.
  • Consider omitting PowerShell examples from documentation focused on Linux VMs, or move them to an appendix or separate section for cross-platform reference.
  • Ensure all CLI instructions reference Azure CLI (cross-platform) rather than PowerShell where possible.
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, but it frequently references PowerShell and Windows-centric tooling. PowerShell examples are provided alongside Azure CLI, and the PowerShell section refers to running PowerShell scripts (which is uncommon for Linux VMs). The troubleshooting section compares Linux logs to Windows logs, and Windows terminology (e.g., RDP, PowerShell) is mentioned before Linux equivalents (e.g., SSH, Bash). The extension removal instructions also present PowerShell before CLI. There are no missing Linux examples, but the presence and ordering of Windows tools and patterns create mild friction for Linux users.
Recommendations
  • Prioritize Azure CLI and Bash examples over PowerShell for Linux VM documentation.
  • Clarify that PowerShell examples are for cross-platform use, and provide Bash script examples when discussing script execution.
  • Reduce references to Windows-specific tools and terminology unless directly relevant to Linux VM management.
  • When comparing Linux and Windows logs, focus on Linux-specific troubleshooting steps and avoid unnecessary Windows log details.
  • Ensure that Linux-native tools and workflows are presented first in all example sections.
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: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation mentions Azure PowerShell (Windows-centric) before Azure CLI in the 'Next steps' section, and links to a Windows-specific PowerShell guide. There are no Linux/macOS-specific examples or references to Linux-native tooling, although the template itself is for a Linux VM and the page is marked as Linux-related.
Recommendations
  • List Azure CLI before Azure PowerShell in 'Next steps', as CLI is cross-platform.
  • Include direct links to Linux/macOS-specific guides or CLI usage examples.
  • Clarify that Azure CLI works on Linux/macOS and provide installation instructions or links.
  • If PowerShell is mentioned, note that it is available cross-platform, or provide parity examples for Bash/CLI.
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: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page demonstrates mild Windows bias by consistently listing Windows tools (PowerShell) before Linux equivalents (CLI), referencing Windows-specific scheduled events before Linux, and linking to Windows documentation first. While Linux support is present and referenced, Windows examples and tools are given priority in ordering and mention.
Recommendations
  • Alternate the order of CLI and PowerShell references so that Linux tools are sometimes listed first.
  • Explicitly mention Linux/macOS compatibility for CLI commands and provide direct Linux/macOS usage examples where possible.
  • Ensure that links to Linux documentation are given equal prominence and are not always listed after Windows links.
  • Add explicit examples or callouts for Linux users in sections discussing tooling (e.g., show both CLI and PowerShell commands side-by-side).
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. While the CLI section is presented first and is cross-platform, the PowerShell section is detailed and uses Windows-centric tools. There is a slight Windows bias in the prominence and depth of PowerShell instructions, but Linux users can fully complete the task using the CLI examples provided.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows.
  • Add a note clarifying that PowerShell examples are primarily for Windows users, and suggest using Azure CLI on Linux/macOS.
  • Consider providing Bash script examples for Linux users, especially for tasks involving variables and loops.
  • Ensure parity in explanation depth between CLI and PowerShell sections.
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 presents PowerShell (Windows-centric) instructions before CLI (cross-platform) instructions in sections for stopping and starting VMs and scale sets. No Linux/macOS-specific tools or examples are provided, but the CLI instructions do offer parity for non-Windows users. The bias is minor and mainly in ordering.
Recommendations
  • Present CLI (az CLI) instructions before PowerShell, as CLI is cross-platform and more widely used on Linux/macOS.
  • Explicitly mention that CLI commands work on Linux/macOS, and provide links to installation guides for those platforms.
  • Add a brief note clarifying that PowerShell Core is available on Linux/macOS, if relevant, or clarify which instructions are Windows-only.
  • Consider including example commands for both CLI and PowerShell in parallel, or in a tabbed format, to emphasize platform parity.
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 ⚠ī¸ powershell_heavy
Summary
The documentation page demonstrates mild Windows bias. Windows terminology (such as 'Windows events', 'IIS logs', and references to Windows-specific log levels) is mentioned before Linux equivalents, and Windows tools (e.g., IIS logs, Windows event logs) are referenced more explicitly than Linux alternatives. The troubleshooting section links to a Windows-specific diagnostics guide, and some recommendations are phrased with Windows-first language. Linux is supported and mentioned, but often as a secondary consideration.
Recommendations
  • Present Linux and Windows examples side-by-side, or alternate which OS is mentioned first.
  • Include explicit Linux equivalents for Windows tools (e.g., mention Apache/Nginx logs alongside IIS logs).
  • Provide links to Linux-specific troubleshooting guides (not just Windows).
  • Clarify log collection recommendations for Linux (e.g., which syslog facilities and levels are most useful).
  • Ensure all advanced/custom monitoring examples include both Windows and Linux scenarios.
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
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation consistently mentions PowerShell before CLI when describing how to create, assign, and delete maintenance configurations. This ordering suggests a Windows-first approach and may imply PowerShell is the primary or preferred method, even though Azure CLI is cross-platform and suitable for Linux/macOS users. No Linux-specific tools or shell examples (e.g., Bash) are provided, and PowerShell is not explicitly marked as Windows-only, potentially causing confusion for Linux users.
Recommendations
  • List Azure CLI instructions before PowerShell, as CLI is cross-platform and more accessible to Linux/macOS users.
  • Explicitly state that PowerShell examples are primarily for Windows users, and recommend CLI for Linux/macOS.
  • Add Bash shell script examples where appropriate, especially for tasks like saving lists or mapping configurations.
  • Clarify tool compatibility in each step (e.g., 'Use PowerShell on Windows, or CLI on any platform').
GitHub Create Pull Request
Virtual Machines Overview of virtual machines in Azure ...e-docs/blob/main/articles/virtual-machines/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 provides examples and references for both Linux and Windows virtual machines, but there is a subtle Windows bias. In several tables and lists, Windows-centric tools (PowerShell) are mentioned before Linux equivalents (Azure CLI), and PowerShell examples are given equal or greater prominence. Some sections, such as those listing ways to query locations or images, consistently list PowerShell before CLI, which is more commonly used by Linux/macOS users. There are no sections that are strictly Windows-only, and Linux-specific features like cloud-init are covered, but the ordering and emphasis may create friction for Linux users.
Recommendations
  • Alternate the order of tool references so that Azure CLI (Linux/macOS friendly) is listed before or alongside PowerShell.
  • Ensure that every example or instruction given for PowerShell is also provided for Azure CLI, with equal detail and prominence.
  • Add explicit Linux/macOS context or notes where relevant, especially in sections discussing management tools.
  • Consider grouping instructions by platform, or clearly labeling them, to avoid implicit prioritization of Windows tools.
  • Review tables and lists for ordering bias and adjust to be platform-neutral or Linux-first where appropriate.
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 Windows-specific. The CLI example is cross-platform, but the documentation does not clarify that PowerShell is Windows-centric or suggest Linux alternatives for PowerShell users. The ordering of examples is neutral, but the inclusion of PowerShell as a primary method may create friction for Linux/macOS users.
Recommendations
  • Explicitly state that PowerShell examples are intended for Windows users and that Azure CLI is recommended for Linux/macOS.
  • Add a note clarifying platform compatibility for each example.
  • Consider placing the Azure CLI example first, as it is cross-platform.
  • Provide links or guidance for installing Azure CLI on Linux/macOS.
  • If possible, include bash or shell script examples for common quota queries.
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
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page displays mild Windows bias by listing PowerShell commands before Linux equivalents (Azure CLI), referencing Windows-specific tools (PowerShell), and mentioning WinRM (a Windows remote management protocol) in network isolation discussions. However, Linux/Azure CLI commands are present, and most instructions are platform-neutral. The page references Linux-specific troubleshooting and template documentation, but Windows tools and patterns are still presented first or exclusively in some cases.
Recommendations
  • List Azure CLI commands before or alongside PowerShell commands to avoid Windows-first impression.
  • Explicitly mention Linux/macOS compatibility for all command-line instructions.
  • Provide Bash or shell script examples where PowerShell is shown.
  • Clarify that WinRM is Windows-specific and provide SSH details for Linux VMs.
  • Ensure all referenced troubleshooting and template documentation have Linux and Windows parity.
GitHub Create Pull Request
Virtual Machines Ddsv6 size series ...virtual-machines/sizes/general-purpose/ddsv6-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, focusing on VM size specifications and performance metrics. However, there is a subtle Windows bias in the 'Feature support' section, where nested virtualization is linked only to the Windows/Hyper-V documentation, and in the 'Bandwidth/Throughput testing' section, which references NTTTCP—a Microsoft tool with primary Windows support—without mentioning Linux alternatives or parity. Windows terminology and links appear before or instead of Linux equivalents in these cases.
Recommendations
  • Include links to nested virtualization documentation for Linux (e.g., KVM/QEMU on Azure) if supported.
  • Mention and link to Linux-compatible bandwidth/throughput testing tools (such as iperf or Linux NTTTCP builds) alongside NTTTCP.
  • Where features/tools are Windows-specific, clarify Linux support status and provide Linux alternatives or guidance.
  • Ensure that documentation for features relevant to both OSes provides parallel instructions and references.
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: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page is largely platform-neutral, focusing on VM specifications and features. However, there is a subtle Windows bias in the 'Feature support' section, where the only linked resource for Nested Virtualization is a Windows/Hyper-V guide. Additionally, in the 'Network' section, the recommended bandwidth testing tool (NTTTCP) is a Microsoft/Windows-centric utility, and no Linux alternatives are mentioned. There are no command-line examples, but where tooling is referenced, Windows tools are prioritized or exclusively mentioned.
Recommendations
  • Include links to Linux/KVM nested virtualization documentation or clarify if the feature is unavailable for all platforms.
  • Mention Linux-compatible network bandwidth testing tools (e.g., iperf, netperf) alongside NTTTCP.
  • Where platform-specific features are discussed, explicitly state applicability to Linux and Windows, and provide parity in references and resources.
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 page is mostly neutral and platform-agnostic, focusing on VM specifications and performance metrics. However, there is mild Windows bias in the 'Feature support' section, where nested virtualization is linked to a Windows-specific guide, and in the 'Networking' section, where bandwidth testing references NTTTCP—a Microsoft/Windows-centric tool—without mentioning Linux alternatives. Windows terminology and resources are mentioned before or instead of Linux equivalents.
Recommendations
  • For nested virtualization, provide or link to equivalent Linux documentation or clarify Linux support status.
  • In bandwidth testing, mention Linux-compatible tools (such as iperf3 or netperf) alongside NTTTCP, and provide links to relevant Linux usage guides.
  • Where Windows-specific resources are referenced, ensure Linux/macOS equivalents are also listed, or clarify any platform limitations.
  • Review all feature support links to ensure Linux parity in documentation coverage.
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: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page is largely neutral and platform-agnostic, focusing on VM sizes and specifications. However, there are subtle signs of Windows bias: the only specific tool mentioned for bandwidth/throughput testing is NTTTCP, which is a Microsoft-developed tool primarily associated with Windows. Additionally, the link for nested virtualization points to a Windows/Hyper-V user guide, with no mention of Linux/KVM equivalents. In both cases, Linux alternatives or parity are not provided.
Recommendations
  • Include Linux/KVM equivalents or references for nested virtualization, or clarify if the feature is Windows-only.
  • When mentioning NTTTCP for bandwidth testing, also reference Linux-native tools such as iperf or netperf, and provide links to relevant guides.
  • Where features are described as supported or unsupported, clarify platform-specific limitations (e.g., if a feature is only available on Windows, state so explicitly).
  • Ensure that any tooling or optimization advice is provided for both Windows and Linux environments.
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, 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 the bandwidth testing tool NTTTCP is referenced (a Microsoft/Windows-centric tool) without mentioning Linux alternatives. Windows and Linux disk encryption are both noted as unsupported, but the Windows reference appears first.
Recommendations
  • For 'Nested Virtualization', add or link to Linux/KVM nested virtualization documentation if supported, or clarify platform limitations.
  • In the 'Network' section, mention Linux-compatible bandwidth testing tools (e.g., iperf, netperf) alongside NTTTCP.
  • When listing platform-specific features or restrictions, alternate the order or present both platforms together to avoid Windows-first bias.
  • Explicitly state platform support or limitations for features where relevant (e.g., nested virtualization, disk encryption).
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 size specifications and features. However, there is mild Windows bias in the 'Feature support' section, where the link for Nested Virtualization points only to the Windows/Hyper-V guide, and in the 'Bandwidth/Throughput testing' resource, which references NTTTCP—a Windows-centric tool—without mentioning Linux alternatives. Windows and Linux disk encryption restrictions are listed separately but equally. No command-line examples or PowerShell-specific instructions are present.
Recommendations
  • For Nested Virtualization, add or link to equivalent Linux/KVM documentation if supported, or clarify platform limitations.
  • In the Bandwidth/Throughput testing section, mention Linux-compatible tools (e.g., iperf, netperf) alongside NTTTCP.
  • Where platform-specific features or limitations exist, clarify them for both Windows and Linux users.
  • Ensure all referenced guides/tools have Linux equivalents or alternatives, and present them with equal prominence.
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 Mdsv3-VHM series with Windows Server mentioned first, followed by Linux distributions. No usage examples, commands, or tooling are provided, so there is no evidence of Windows-only instructions or tools. The ordering of Windows before Linux is a minor bias.
Recommendations
  • List Linux distributions before or alongside Windows Server when describing compatible images.
  • Explicitly mention that all features and specifications apply equally to Linux and Windows unless noted.
  • If future documentation adds usage examples or commands, ensure parity between Windows (PowerShell, CMD) and Linux (Bash, CLI) instructions.
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: 1 bias type
Detected Bias Types
⚠ī¸ windows_tools
Summary
The documentation is largely neutral and platform-agnostic, focusing on VM specifications and features. However, there is a minor Windows bias in the 'Feature support' section, where nested virtualization is linked only to a Windows-specific (Hyper-V) guide, and in the 'Network' section, bandwidth testing references NTTTCP, a tool that originated on Windows. No Linux/macOS-specific examples, tools, or guides are provided in these contexts.
Recommendations
  • In the 'Feature support' section, add references to nested virtualization guides for Linux (such as KVM/QEMU) if supported, or clarify platform limitations.
  • In the 'Network' section, mention Linux-native bandwidth testing tools (e.g., iperf3) alongside NTTTCP, and provide links to relevant Linux documentation.
  • Where platform-specific features are discussed, explicitly state support or limitations for Linux/macOS and provide parity in documentation links.
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: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page references both Azure CLI and PowerShell for troubleshooting, but explicitly calls out PowerShell's '-Debug' switch alongside Azure CLI's '--debug'. This gives prominence to Windows/PowerShell tooling, and the mention of PowerShell occurs before any Linux-specific shell or tool. No Linux/macOS-specific troubleshooting commands or examples are provided, and there is no mention of Bash, shell scripting, or Linux-native tools. All error messages and mitigations are generic and do not show platform-specific examples, but the initial troubleshooting guidance is slightly Windows-biased.
Recommendations
  • Explicitly mention Bash or Linux shell equivalents for troubleshooting, such as using Azure CLI in Bash or Zsh.
  • Provide example commands for both PowerShell and Bash (Linux/macOS) when discussing troubleshooting steps.
  • Clarify that Azure CLI works cross-platform and provide links or notes for installing and using it on Linux/macOS.
  • If PowerShell is referenced, also mention PowerShell Core (pwsh) for Linux/macOS, or clarify platform compatibility.
  • Consider listing Azure CLI (cross-platform) before PowerShell in troubleshooting steps to avoid Windows-first perception.
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 presents information in a platform-neutral way, but there is a subtle bias in the ordering and linking of resources: Windows and Linux scheduled events are mentioned together, but the Windows link is listed second. There are no command-line examples or tooling references for either platform, and no explicit examples for Linux or Windows. However, the lack of Linux-specific troubleshooting or operational examples (such as how to check for downtime or maintenance events on Linux VMs) may leave Linux users with less actionable guidance compared to what could be provided.
Recommendations
  • Provide explicit examples or references for both Linux and Windows users, such as commands to check system logs for reboots or maintenance events.
  • Ensure parity in documentation depth for both platforms, including troubleshooting steps and operational guidance.
  • If mentioning scheduled events, briefly summarize the differences or considerations for Linux and Windows, rather than only linking out.
  • Consider listing Linux and Windows resources in alternating order or together to avoid perceived prioritization.
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 page demonstrates mild Windows bias by listing Windows migration resources and examples before Linux equivalents and referencing PowerShell as a primary tool for querying affected VMs. Linux migration is mentioned, but Windows is consistently presented first, and no Linux-specific CLI or scripting examples are provided.
Recommendations
  • Present Linux and Windows migration resources in parallel or alternate their order to avoid 'Windows first' bias.
  • Include examples for querying affected VMs using Azure CLI or Bash scripts, which are more common for Linux users.
  • Explicitly mention Linux-friendly tools and workflows alongside PowerShell, such as Azure CLI commands.
  • Ensure links to migration guides for both Windows and Linux are equally prominent and described.
GitHub Create Pull Request
Virtual Machines Understanding Azure virtual machine usage ...e-docs/blob/main/articles/virtual-machines/vm-usage.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_examples ⚠ī¸ windows_terms
Summary
The documentation references both Linux and Windows VMs, but Windows-related terms and examples appear more frequently and are often listed before Linux equivalents. For example, image types and usage examples mention Windows Server and SQL Server on Windows before Linux distributions. Tagging instructions link to both CLI and PowerShell, but the PowerShell link is labeled as 'tag-portal', which may suggest a Windows-centric approach. There are no explicit Linux-only examples, and Windows terminology (BYOL, Hybrid Benefit) is explained in detail, while Linux licensing or usage is not.
Recommendations
  • Ensure Linux distributions and usage scenarios are given equal prominence in examples and explanations.
  • Provide explicit Linux CLI examples and links alongside PowerShell instructions, not just as an afterthought.
  • Balance the order of Windows and Linux references in lists and tables (e.g., image types, usage scenarios).
  • Include details about Linux licensing, cost management, and marketplace images similar to the Windows explanations.
  • Clarify that tagging and other features work equally for Linux and Windows VMs, and provide parallel instructions.
GitHub Create Pull Request