← Back to Dashboard
1646
Pages Scanned
145
Pages Flagged
1646
Changed Pages
8.8%
% Pages Flagged

Scan Information

Started At: 2026-01-09 19:00:50

Finished At: 2026-02-10 18:00:39

Status: completed

Target Repo: Azure Compute

Current Phase: discovery

Files Queued: 1646

Files Completed: 1646

Problematic Pages

145 issues found
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
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides command-line examples for Azure CLI, PowerShell, and REST. However, the PowerShell example is given its own dedicated section, and there is no explicit mention or example of using Bash or Linux shell environments. The CLI example is generic but does not clarify Linux compatibility or provide Bash-specific context. There is a clear PowerShell focus, and the documentation does not address Linux users directly or provide parity in example commands or environment notes.
Recommendations
  • Add explicit Bash/Linux shell examples alongside the Azure CLI example, clarifying that the CLI commands work cross-platform.
  • Include a note that PowerShell examples are primarily for Windows users, and provide equivalent Bash/Linux commands where appropriate.
  • Reorder the examples to present the Azure CLI (cross-platform) first, followed by Bash/Linux, then PowerShell, to avoid implicit Windows-first bias.
  • Mention any OS-specific requirements or differences, if applicable, to help Linux users understand how to adapt the instructions.
  • Consider adding a 'Bash' or 'Linux' tab in the example sections to ensure Linux users see themselves represented.
GitHub Create Pull Request
Container Instances Override entrypoint in container instance ...ntainer-instances/container-instances-start-command.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page demonstrates some Windows bias by referencing Windows tools (PowerShell) and cmd.exe, mentioning PowerShell before Linux equivalents, and providing explicit PowerShell examples while not providing equivalent Bash or Linux shell examples. The 'Default shell' table lists Windows/cmd after Linux shells, but the only non-CLI tool-specific example is for PowerShell. There are no explicit Bash or Linux shell command-line examples for resource creation (e.g., using Bash scripts or Linux-native tools).
Recommendations
  • Add explicit Bash or Linux shell examples for creating container instances, especially for scripting scenarios.
  • Provide Linux-native equivalents for PowerShell examples, such as using Bash with Azure CLI.
  • Where PowerShell cmdlets are mentioned, also mention Bash scripting or Linux automation options.
  • Ensure that Linux tools and patterns are presented with parity to Windows/PowerShell, both in order and in detail.
  • Consider adding a section or table that summarizes both Windows and Linux approaches side by side for common tasks.
GitHub Create Pull Request
Service Fabric Upgrading Azure Service Fabric managed clusters ...cles/service-fabric/how-to-managed-cluster-upgrades.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 Windows bias by exclusively showing examples and references for Windows environments. The REST API output only lists Windows cluster versions, with no mention or examples of Linux equivalents. There are no Linux-specific instructions, examples, or references to Linux tools or operating systems throughout the page.
Recommendations
  • Include examples and instructions for Linux-based Service Fabric clusters, such as showing REST API output for Linux cluster versions.
  • Explicitly mention Linux support where relevant, including in the 'Query for supported cluster versions' section.
  • Add guidance for managing upgrades on Linux clusters, including any differences in configuration or supported features.
  • Ensure parity in documentation by providing both Windows and Linux examples side-by-side where applicable.
GitHub Create Pull Request
Azure Impact Reporting Azure Impact Reporting: Create an Azure Monitor Alert Connector ...ure-impact-reporting/create-azure-monitor-connector.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation demonstrates a mild Windows bias. While both Bash (Linux) and PowerShell (Windows) scripts are provided for command-line deployment, Windows/PowerShell is often mentioned first (e.g., 'AzCLI, Azure PowerShell, or the Azure portal'), and PowerShell examples precede Bash examples in the script usage section. The documentation also references PowerShell and Windows-centric tools (e.g., PowerShell, Azure portal) before their Linux equivalents. However, Bash scripts are available and referenced, so Linux support is present but not always given equal prominence.
Recommendations
  • Alternate the order of Bash and PowerShell examples, or present Bash examples first in some sections to avoid consistently prioritizing Windows tools.
  • Explicitly mention Linux and macOS compatibility where Bash scripts are referenced, to reassure non-Windows users.
  • Where possible, use neutral language such as 'command-line tools (Bash or PowerShell)' instead of listing PowerShell or Windows tools first.
  • Add a short section or note confirming that all features and scripts are supported on Linux, macOS, and Windows.
  • Ensure screenshots and UI instructions are not overly Windows-centric (e.g., referencing Windows-specific UI elements or terminology).
GitHub Create Pull Request
Container Instances Set environment variables in container instance ...instances/container-instances-environment-variables.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. The Azure PowerShell example is given equal prominence to the Azure CLI, and PowerShell-specific patterns (such as array construction and command syntax) are detailed extensively. Windows Command Prompt quoting is mentioned before Linux/Bash conventions in the CLI section. There is no explicit Linux shell or scripting example (e.g., Bash script), nor are Linux-native tools (like curl, grep, or shell environment variable patterns) referenced. The YAML section does specify osType: Linux, but the main procedural examples focus on Windows-centric tools and patterns.
Recommendations
  • Add explicit Bash shell script examples for setting environment variables and querying container logs, demonstrating Linux-native patterns.
  • Mention Linux/Bash quoting conventions before or alongside Windows Command Prompt conventions in CLI examples.
  • Include references to Linux-native tools or commands (e.g., using curl or grep inside containers) to show environment variable usage.
  • Balance PowerShell and CLI coverage by providing equivalent Linux shell automation examples.
  • Clarify that Azure CLI is cross-platform and provide guidance for both Windows and Linux users where syntax differs.
GitHub Create Pull Request
Container Instances Execute commands in running container instance ...ticles/container-instances/container-instances-exec.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation provides both Linux and Windows examples for executing commands in running Azure container instances. However, the Windows (cmd.exe) example is given equal prominence to the Linux (bash) example, and there is no mention of Linux-specific tools or troubleshooting patterns beyond Bash. The documentation refers to 'Command Prompt' and Windows-specific output, and does not mention PowerShell or Linux shells beyond Bash. There is a slight bias towards Windows by providing detailed Windows output and terminology, and by not mentioning Linux alternatives (e.g., sh, zsh) or common Linux troubleshooting tools.
Recommendations
  • Add examples using other common Linux shells (e.g., sh, zsh) to show parity with the Windows cmd.exe example.
  • Include Linux-specific troubleshooting patterns or tools (e.g., using top, ps, or tail inside the container) in the examples.
  • When showing example output, provide both Linux and Windows outputs in parallel, or alternate their order to avoid implicit prioritization.
  • Mention that the Azure CLI commands work identically on both Windows and Linux containers, and clarify any differences in shell invocation.
  • Consider referencing PowerShell as a Windows shell alternative to cmd.exe for completeness.
GitHub Create Pull Request
Container Instances Configure custom DNS settings for container group in Azure Container Instances .../container-instances/container-instances-custom-dns.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_image_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a subtle Windows bias primarily through the use of a Windows-centric container image (mcr.microsoft.com/powershell) as the main example for deploying a container group with custom DNS settings. The example YAML file and subsequent commands focus on deploying a PowerShell container, which is a Microsoft/Windows tool, even though the container is running on Linux. There is no mention or example of using a typical Linux container image (e.g., Ubuntu, Alpine, nginx), and the only container image shown is PowerShell. Additionally, the container group is named 'pwsh-vnet-dns', further reinforcing the Windows/PowerShell focus. While the CLI instructions are Bash-oriented and the OS type is Linux, the choice of container image and naming conventions prioritize Windows tools over Linux equivalents.
Recommendations
  • Provide additional example YAML files using popular Linux container images (e.g., Ubuntu, nginx, Alpine) to demonstrate DNS configuration in a more Linux-native context.
  • Rename example container groups and images to use neutral or Linux-centric names (e.g., 'ubuntu-vnet-dns', 'nginx-vnet-dns') to avoid implicit Windows/PowerShell prioritization.
  • Include a note or section explicitly showing how to configure DNS for a Linux container image, including troubleshooting tips for common Linux distributions.
  • Balance the documentation by offering both PowerShell and Linux shell container examples, or default to a Linux image given the stated Linux OS type and the target audience for container workloads.
GitHub Create Pull Request
Service Fabric Manage Azure Service Fabric application secrets ...fabric/service-fabric-application-secret-management.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a Windows-first bias by referencing Windows and PowerShell tooling before Linux equivalents, and providing only PowerShell and C# examples for application deployment and parameter overrides. There are no Linux-specific command-line examples (e.g., Bash, CLI), and the use of PowerShell is presented as the default scripting option. The section on setting up encryption certificates does link to both Windows and Linux guides, but all in-page examples and automation references are Windows-centric.
Recommendations
  • Provide equivalent Linux command-line examples (e.g., Bash scripts using Azure CLI or Service Fabric CLI) for creating application instances and overriding parameters.
  • Mention Linux tooling (such as sfctl or Azure CLI) alongside PowerShell, and present both options in parallel.
  • Avoid language that implies PowerShell is the default or only automation method; clarify cross-platform alternatives.
  • Ensure that all steps and code samples have Linux equivalents, or explicitly note platform differences where parity is not possible.
  • Consider alternating the order of Windows and Linux references, or present them side-by-side to reinforce platform neutrality.
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
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a strong Windows bias. All command-line examples for deploying and managing certificates use PowerShell, with no mention of Linux shell equivalents (such as Bash or Azure CLI). The instructions assume use of Windows tools (PowerShell, certificate stores like 'Cert:\CurrentUser\TrustedPeople'), and there are no examples or guidance for Linux users. The workflow and troubleshooting steps are written from a Windows-centric perspective, and Linux patterns are omitted entirely.
Recommendations
  • Provide equivalent Azure CLI and Bash examples for all PowerShell commands, especially for template deployment and certificate management.
  • Include instructions for importing certificates on Linux, such as using 'openssl' or Linux certificate stores.
  • Mention platform differences explicitly, and offer guidance for both Windows and Linux administrators.
  • Reference cross-platform tools and patterns (e.g., Azure CLI, REST API) before or alongside Windows-specific tools.
  • Add troubleshooting notes for Linux environments, such as common certificate store locations and access methods.
GitHub Create Pull Request
Service Fabric Set up monitoring with Azure Monitor logs ...service-fabric/service-fabric-diagnostics-oms-setup.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a Windows bias by prioritizing Windows-specific solutions (Service Fabric Analytics), providing PowerShell-heavy deployment examples, referencing Windows tools (WAD), and omitting equivalent Linux-focused examples or instructions. Linux users are redirected to separate documentation, and the main workflow and examples are tailored for Windows environments.
Recommendations
  • Include Linux-specific deployment steps and examples directly in this page, not just as a redirect.
  • Provide equivalent Bash/CLI examples for deploying and configuring Azure Monitor logs and Log Analytics workspaces.
  • Clarify which features or solutions are Windows-only and offer Linux alternatives or workarounds.
  • Mention Linux diagnostic tools (e.g., syslog, OMS agent) alongside Windows tools like WAD, and explain how to connect Linux cluster logs to Log Analytics.
  • Ensure parity in instructions and screenshots for both Windows and Linux clusters.
GitHub Create Pull Request
Virtual Machines Create an incremental snapshot ...ticles/virtual-machines/disks-incremental-snapshots.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for creating and managing incremental snapshots, but there is a noticeable bias toward Windows and PowerShell. PowerShell examples are given equal prominence to CLI, despite CLI being more universally available across platforms. The PowerShell sections use Windows-centric scripting and tools, and the documentation refers to Azure PowerShell modules and patterns that are most familiar to Windows users. There are no explicit Linux shell script examples (e.g., Bash), nor are Linux-specific considerations or troubleshooting steps mentioned. The CLI examples, while cross-platform, are not explicitly contextualized for Linux users, and the PowerShell examples are presented with the same level of detail and priority, which can reinforce a Windows-first mindset.
Recommendations
  • Add explicit Bash shell script examples for Linux users, showing how to use Azure CLI in typical Linux environments.
  • Clarify in the CLI sections that the commands are suitable for both Linux and Windows, and provide notes on any OS-specific differences (e.g., environment variable syntax, quoting).
  • Reduce the prominence of PowerShell by presenting CLI examples first, or by grouping PowerShell as a Windows-specific alternative.
  • Include troubleshooting tips or common issues for Linux users (e.g., permissions, shell differences, package installation).
  • Reference Linux-native tools or patterns where appropriate, such as cron jobs for automation, or integration with Linux backup utilities.
  • Ensure that portal and ARM template instructions are clearly marked as OS-agnostic.
GitHub Create Pull Request
Virtual Machines AMD GPU Driver Extension - Azure Linux VMs ...irtual-machines/extensions/hpccompute-amd-gpu-linux.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page is focused on Linux VMs and AMD GPU drivers, but it presents Windows-centric tools (PowerShell) alongside Linux-native tools (Azure CLI) for extension deployment and troubleshooting. PowerShell examples are given equal prominence to Azure CLI, and PowerShell is mentioned before Azure CLI in several sections. There is no explicit Linux shell scripting example (e.g., Bash), and some troubleshooting steps reference PowerShell before CLI. The documentation does not exclusively use Windows tools, but the inclusion and ordering of PowerShell may signal a subtle Windows bias.
Recommendations
  • Prioritize Azure CLI and Bash examples before PowerShell in all sections, as CLI is cross-platform and native to Linux.
  • Add explicit Bash shell scripting examples for common tasks (e.g., checking extension status, parsing logs).
  • Clarify that PowerShell is optional and primarily for users on Windows, while Azure CLI is recommended for Linux users.
  • Ensure troubleshooting and deployment instructions are Linux-first, with Windows tools mentioned only as alternatives.
  • Review and update screenshots and UI references to ensure they reflect Linux usage where possible.
GitHub Create Pull Request
Container Instances Create a standby pool for Azure Container Instances ...r-instances/container-instances-standby-pool-create.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides both Azure CLI and PowerShell examples for all operations, but PowerShell (a Windows-centric tool) is given equal prominence and is mentioned before ARM template and REST options. There are no explicit Linux shell (bash) or native Linux tool examples, and PowerShell is referenced as a primary automation method. The use of PowerShell cmdlets and deployment patterns (e.g., New-AzResourceGroupDeployment) reflects a Windows-oriented approach. No Linux-specific instructions, troubleshooting, or parity notes are present.
Recommendations
  • Add explicit bash/Linux shell examples for all CLI commands, including sample scripts and environment setup notes for Linux users.
  • Clarify that Azure CLI is fully cross-platform and recommend it as the default for Linux/macOS users, while PowerShell is optional.
  • Reorder sections to present CLI (bash) examples before PowerShell, or clearly indicate platform applicability for each example.
  • Include troubleshooting tips or notes for Linux environments, such as file permissions, environment variables, or common issues.
  • Mention and link to Azure Cloud Shell as a cross-platform, browser-based alternative for both Windows and Linux users.
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
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides explicit examples for Azure CLI (cross-platform), PowerShell (Windows-centric), and REST API, but does not include Linux-specific shell examples (e.g., Bash/cURL) or mention Linux tools. The PowerShell example is given its own section, and there is no parity example for Linux shells. The CLI section does not clarify that it is cross-platform, and PowerShell is presented as a primary method, which may suggest a Windows bias.
Recommendations
  • Add a Bash/cURL example for querying the REST API to demonstrate Linux parity.
  • Clarify that Azure CLI commands work on Windows, Linux, and macOS.
  • If PowerShell is included, consider also including a Bash or shell script example.
  • Reorder examples or explicitly state that all platforms are supported equally.
  • Mention common Linux troubleshooting tools or patterns where relevant.
GitHub Create Pull Request
Container Instances Standby pools for Azure Container Instances ...instances/container-instances-standby-pool-overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates a Windows bias by primarily using Azure PowerShell for provider registration and by listing PowerShell examples before CLI equivalents in the availability zones section. There are no explicit Linux shell (bash) examples for provider registration, and the use of Azure Cloud Shell is not clarified as cross-platform. This may hinder Linux users who prefer Azure CLI or bash scripting.
Recommendations
  • Provide Azure CLI (bash) examples alongside or before PowerShell examples for provider registration and other key operations.
  • Clarify that Azure Cloud Shell supports both Bash and PowerShell, and indicate which shell is being used in each example.
  • Ensure that for every PowerShell example, an equivalent Azure CLI (bash) command is provided.
  • Consider listing CLI (bash) examples before PowerShell to avoid implicit Windows-first bias.
  • Explicitly mention Linux compatibility and provide guidance for Linux/macOS users where relevant.
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
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides both Azure CLI and PowerShell examples for requesting a container group from a standby pool, but PowerShell (a Windows-centric tool) is given its own dedicated section and example. There is no mention of Linux-specific shell patterns (e.g., bash scripting), nor are Linux-native tools or package managers referenced. The ARM template and REST API examples are platform-neutral, but the command-line examples lean towards Windows by including PowerShell and referencing its cmdlets. The ordering of examples places CLI first, but the presence and detail of PowerShell content suggests a Windows bias.
Recommendations
  • Add explicit bash or shell script examples for Linux users, especially for automation scenarios.
  • Clarify that Azure CLI commands work cross-platform and provide sample usage in bash/zsh (e.g., with environment variables, piping, etc.).
  • If PowerShell is included, consider also including Linux shell equivalents or note PowerShell Core compatibility on Linux.
  • Reference Linux package managers or installation instructions for Azure CLI and PowerShell, if relevant.
  • Ensure that documentation language and examples do not assume a Windows environment by default.
GitHub Create Pull Request
Container Instances Update or delete a standby pool for Azure Container Instances ...nces/container-instances-standby-pool-update-delete.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides both Azure CLI and PowerShell examples for updating and deleting standby pools, but PowerShell (a Windows-centric tool) is given equal prominence as CLI, and is mentioned before Linux-native alternatives in some places. There is no explicit mention of Linux shell scripting, nor are there Bash or Linux-specific examples. The ARM template and REST API sections are platform-neutral, but the overall example set leans toward Windows tooling and patterns.
Recommendations
  • Add explicit Bash/Linux shell examples for all CLI commands, demonstrating usage in a Linux terminal.
  • Clarify that Azure CLI is cross-platform and show examples of running CLI commands in Linux environments (e.g., with Bash syntax and environment variables).
  • Consider reordering sections so that CLI (cross-platform) examples appear before PowerShell (Windows-centric) examples.
  • Add notes or links for Linux users, such as installation instructions for Azure CLI on Linux.
  • Avoid assuming PowerShell is the default scripting environment; mention alternatives for Linux and macOS users.
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
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation is heavily focused on PowerShell and Windows-centric tooling. All code examples use PowerShell cmdlets, and the workflow assumes use of Visual Studio Code with the Azure Functions extension, which is most commonly used on Windows. There is no mention of Bash, Azure CLI, or Linux-native scripting alternatives for creating or managing Azure Functions or container groups. The prerequisites and steps reference PowerShell installation and usage exclusively, and do not provide parity for Linux users who may prefer Bash or Azure CLI.
Recommendations
  • Provide equivalent examples using Azure CLI and Bash scripts for all major steps, especially for resource creation, identity assignment, and container group deployment.
  • Explicitly mention and link to Linux setup guides for Azure Functions development, including how to use VS Code and the Azure Functions extension on Linux.
  • Include instructions for installing and using Azure CLI on Linux and macOS, and demonstrate how to perform the same operations without PowerShell.
  • Add notes or sections highlighting cross-platform compatibility, and clarify which steps are OS-agnostic and which may require adaptation for Linux environments.
  • Where PowerShell is used, offer side-by-side Bash/Azure CLI equivalents, especially for commands like New-AzContainerGroup, role assignment, and resource cleanup.
GitHub Create Pull Request
Service Fabric Migrate from Azure Cloud Services to Service Fabric ...ic/cloud-services-to-service-fabric-migration-guide.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation demonstrates a clear Windows bias. PowerShell is the only command-line tool shown for cluster and application deployment, with no Azure CLI or Bash examples. Visual Studio (Windows-only) is the only development environment mentioned for creating Service Fabric applications, and the setup instructions reference preparing the development environment on Windows, with no mention of Linux or cross-platform alternatives. The documentation does not provide Linux-specific guidance or parity for common tasks, and Windows tools and patterns are consistently mentioned first or exclusively.
Recommendations
  • Add Azure CLI and Bash examples for all PowerShell deployment and management commands, including cluster creation, application packaging, and deployment.
  • Include instructions for setting up a development environment on Linux and macOS, such as using VS Code, JetBrains Rider, or the Service Fabric CLI (sfctl).
  • Provide explicit guidance for cross-platform development, including .NET Core/ASP.NET Core usage on Linux.
  • Mention and link to Linux-compatible tools and workflows (e.g., sfctl, Azure CLI, Docker for container scenarios) alongside or before Windows-specific tools.
  • Ensure all code and configuration migration steps include notes or examples relevant to Linux environments (e.g., file paths, environment variables, packaging).
  • Clarify any platform-specific limitations or differences, such as container support or deployment targets, and provide Linux alternatives where possible.
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
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell command examples for key steps (such as obtaining service principal IDs and assigning roles), referencing Azure PowerShell before Azure CLI, and omitting equivalent Linux shell or Azure CLI commands for these operations. There is no mention of Linux-specific tools or cross-platform alternatives, making the instructions less accessible to Linux users.
Recommendations
  • Include Azure CLI examples alongside PowerShell for all command-line steps, especially for service principal and role assignment operations.
  • Present Azure CLI and PowerShell options together, or list Azure CLI first to avoid implicit Windows-first ordering.
  • Add notes clarifying that all steps can be performed on Linux, macOS, or Windows, and provide links to cross-platform tool documentation.
  • Review and update sample scripts and templates to ensure they are platform-agnostic and do not assume a Windows environment.
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
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell-based command-line examples for resource creation, role assignment, and deployment. There are no equivalent examples for Linux users (e.g., Bash/CLI), and the use of PowerShell is assumed throughout. Additionally, administrative access is described in terms of RDP, which is a Windows-centric remote access method, with no mention of SSH for Linux VMs.
Recommendations
  • Add Azure CLI (az) command examples alongside PowerShell for all resource creation, role assignment, and deployment steps.
  • Include instructions and examples for Linux users, such as using SSH for VM access instead of only RDP.
  • Clearly indicate that both Windows and Linux VMs are supported, and provide guidance for both platforms where relevant.
  • Where templates or scripts are referenced, specify any platform requirements or provide cross-platform alternatives.
GitHub Create Pull Request
Service Fabric Deploy app with a user-assigned managed identity ...vice-fabric-application-user-assigned-managed-identity.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation references PowerShell for managing user-assigned managed identities and links to PowerShell-specific guides, without mentioning or providing examples for Linux tools or CLI equivalents. There are no Linux-specific instructions or examples, and the only management tool referenced is PowerShell, which is traditionally associated with Windows environments.
Recommendations
  • Include Azure CLI examples and references alongside or before PowerShell, as Azure CLI is cross-platform and widely used on Linux.
  • Provide links to Linux-friendly documentation for managing user-assigned managed identities.
  • Explicitly mention that the steps can be performed on Linux, and clarify any platform-specific requirements or differences.
  • Add a section or note for Linux users, highlighting equivalent commands and tools.
GitHub Create Pull Request
Service Fabric Configure autoscaling for Service Fabric managed cluster nodes ...les/service-fabric/how-to-managed-cluster-autoscale.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a strong Windows bias. All command-line examples use PowerShell and Azure PowerShell modules, with no mention of equivalent Linux or cross-platform CLI commands (e.g., Azure CLI). Windows-specific scenarios (such as Hyper-V/nested virtualization) are discussed, while Linux equivalents are omitted. The documentation assumes the use of Windows tooling and patterns, and does not provide parity for Linux users.
Recommendations
  • Provide equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Explicitly mention that autoscaling and Service Fabric managed clusters are supported on both Windows and Linux node types, and clarify any OS-specific limitations.
  • Include troubleshooting steps and metric collection examples using Azure CLI and/or Bash scripts, not just PowerShell.
  • Discuss Linux-specific considerations (e.g., memory metrics, VM configuration) alongside Windows-specific notes.
  • Review and update all sample templates and deployment instructions to ensure they are OS-agnostic or provide both Windows and Linux variants.
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
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias by exclusively providing deployment instructions using PowerShell cmdlets and referencing RDP (Remote Desktop Protocol) for VM administration, both of which are Windows-centric. There are no examples or guidance for Linux users, such as using Azure CLI, Bash, or SSH for administration or deployment. The order of presentation also places Windows tools and patterns first, with no mention of Linux alternatives.
Recommendations
  • Add equivalent deployment instructions using Azure CLI (az deployment group create) with Bash examples.
  • Include guidance for Linux users on connecting to VMs via SSH, rather than only mentioning RDP.
  • Present both Windows and Linux administration options side-by-side, or alternate their order to avoid implicit prioritization.
  • Reference cross-platform tools and patterns (e.g., Azure CLI, REST API) before or alongside Windows-specific tools.
  • Explicitly state that the process is platform-agnostic where possible, and provide links to both Windows and Linux documentation for related tasks.
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 ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page exhibits a strong Windows bias. All code examples use Windows containers (mcr.microsoft.com/windows/nanoserver:1809), Windows-specific paths (C:\WorkspaceOnHost), and Windows shell commands (cmd, type, ping). The example explicitly assumes familiarity with creating Windows container applications and references Windows container compatibility. There are no examples or guidance for Linux containers, Linux paths, or Linux shell commands, nor is there mention of Linux equivalents for the demonstrated patterns.
Recommendations
  • Add parallel examples using Linux containers (e.g., mcr.microsoft.com/ubuntu or other Linux images) and Linux shell commands (bash, echo, cat, etc.).
  • Include Linux-specific path examples (e.g., /workspace/log.txt) and volume mounts.
  • Reference documentation for creating Linux container applications in Service Fabric alongside Windows examples.
  • Clarify whether Initializer CodePackages are supported for Linux containers and provide any platform-specific considerations.
  • Present both Windows and Linux examples in each section, or alternate their order to avoid implicit prioritization.
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
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page presents Azure CLI and Azure PowerShell examples for deploying a public IP prefix in a Service Fabric managed cluster. PowerShell, a Windows-centric tool, is given a dedicated section, and references to PowerShell appear before any mention of Linux-specific tools or workflows. There are no explicit Linux shell (bash) examples, nor are Linux-specific deployment patterns (such as using Bash scripts or cloud-init) discussed. The documentation implicitly assumes familiarity with Windows tooling and does not provide parity for Linux users.
Recommendations
  • Add explicit Bash shell examples for each step, especially for ARM template deployment (e.g., using az CLI from Bash).
  • Clarify that Azure CLI is cross-platform and provide Linux-specific instructions or notes where relevant.
  • Include references to Linux-native tools or workflows, such as using cloud-init or bash scripting for deployment.
  • Reorder sections so that cross-platform or Linux-friendly tools (Azure CLI, Bash) are presented before Windows-centric tools (PowerShell).
  • Explicitly state platform compatibility for each tool and example, helping users choose the best workflow for their OS.
GitHub Create Pull Request
Service Fabric Create a Service Fabric cluster using Bicep ...in/articles/service-fabric/quickstart-cluster-bicep.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation is heavily biased toward Windows environments. All examples use PowerShell, including certificate creation and deployment steps. The Service Fabric cluster is specified as a Windows cluster, and certificate creation references Windows Server certificate services for production. There are no Linux-specific instructions, examples, or alternatives for certificate creation, deployment, or cluster configuration. The use of Windows tools and PowerShell is pervasive, and Linux equivalents (such as Bash, OpenSSL, or Azure CLI for all steps) are missing or only mentioned as an afterthought (e.g., CLI for resource deletion).
Recommendations
  • Provide parallel instructions and examples for Linux environments, including Bash and Azure CLI commands for all steps.
  • Include instructions for creating self-signed certificates using OpenSSL, and uploading them to Azure Key Vault from Linux.
  • Clarify how to deploy a Linux-based Service Fabric cluster, or note if only Windows clusters are supported.
  • Ensure all scripts and helper tools (such as New-ServiceFabricClusterCertificate.ps1) have Linux-compatible equivalents.
  • Present CLI and Bash examples before or alongside PowerShell, not only in the clean-up section.
  • Explicitly state platform requirements and alternatives at the start of the documentation.
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 ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation is heavily oriented toward Windows development environments, specifically Visual Studio. All instructions and screenshots reference Visual Studio on Windows, with no mention of Linux or cross-platform alternatives. PowerShell scripts are referenced as the default deployment tooling, and Windows-specific issues (such as path length limits) are discussed without Linux equivalents. There are no examples or guidance for deploying from Linux or using Linux-native tools.
Recommendations
  • Add instructions for deploying a Node.js app to Service Fabric using Linux or macOS, including required SDKs and command-line tools.
  • Provide examples using cross-platform tools such as Azure CLI, Service Fabric CLI (sfctl), or VS Code.
  • Include Linux-specific guidance for project setup, deployment, and troubleshooting (e.g., file permissions, path conventions).
  • Reference Bash scripts or other Linux-native automation options alongside PowerShell.
  • Address Linux-specific considerations, such as service manifest editing and cluster connection, where relevant.
GitHub Create Pull Request
Service Fabric Describing Azure Service Fabric apps and services ...ic/service-fabric-application-and-service-manifests.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits Windows bias primarily through references to Windows-specific tools (Visual Studio, file paths like C:\Program Files\...), and by suggesting Windows workflows (using Visual Studio for XML schema validation) without mentioning Linux alternatives. There are no Linux-specific examples, tools, or instructions provided, and the only command-line reference is to the ServiceFabric PowerShell module, which is Windows-centric.
Recommendations
  • Add instructions for validating XML schema on Linux, such as using xmllint or other open-source editors (e.g., VS Code, Kate, or command-line tools).
  • Include Linux file path equivalents and clarify where Service Fabric SDK files are located on Linux systems.
  • Mention cross-platform editors (e.g., VS Code) and how to enable XML schema validation/intelli-sense on both Windows and Linux.
  • Provide examples or references for managing Service Fabric applications using Linux command-line tools (e.g., Azure CLI, sfctl) alongside PowerShell.
  • Ensure that any references to Windows-specific workflows are paired with Linux alternatives, or clarify platform limitations where applicable.
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 ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a strong Windows bias, primarily by providing only PowerShell-based examples and references to Windows-centric tools and workflows (e.g., Visual Studio, PowerShell cmdlets). There is no mention of Linux equivalents, such as CLI commands, Bash scripts, or cross-platform Service Fabric tools. The ordering and language also prioritize Windows tools and patterns, with no guidance for Linux users.
Recommendations
  • Add equivalent examples using Azure CLI, Bash scripts, or REST API calls for all PowerShell cmdlet usage.
  • Explicitly mention and demonstrate how to perform Service Fabric upgrades on Linux clusters, including any differences in configuration or tooling.
  • Include cross-platform instructions and clarify which steps or tools are Windows-only, providing alternatives for Linux.
  • Reference Linux-compatible editors and deployment workflows (e.g., VS Code, command-line tools) alongside Visual Studio.
  • Ensure that ARM template examples and service manifest configuration steps are shown with cross-platform context, not assuming a Windows environment.
GitHub Create Pull Request
Service Fabric Troubleshooting application upgrades ...https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-application-upgrade-troubleshooting.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a strong Windows bias. All command-line examples use PowerShell cmdlets (e.g., Get-ServiceFabricApplicationUpgrade), with no mention of Linux/Unix equivalents such as the Service Fabric CLI (sfctl) or REST API. The tools and troubleshooting patterns described are specific to Windows environments, and the 'Next steps' section lists Visual Studio and PowerShell tutorials before any mention of cross-platform or Linux tools. There are no Linux-specific instructions or examples, and no guidance for users managing Service Fabric clusters from Linux or macOS.
Recommendations
  • Add equivalent examples using the Service Fabric CLI (sfctl), which is cross-platform, alongside or in place of PowerShell examples.
  • Explicitly mention REST API options for troubleshooting upgrades, which are platform-agnostic.
  • Include troubleshooting steps and command examples that can be run from Linux or macOS environments.
  • In the 'Next steps' section, add links to tutorials for upgrading applications using sfctl or REST API, and ensure these are listed alongside PowerShell/Visual Studio options.
  • Clarify in the introduction that the documented commands are PowerShell-specific and provide guidance for Linux users.
  • Where possible, use neutral language (e.g., 'use your preferred tool such as PowerShell or sfctl') rather than assuming a Windows environment.
GitHub Create Pull Request
Service Fabric Learn about Azure Service Fabric application security ...ric/service-fabric-application-and-service-security.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias in several areas: Windows-specific tools and patterns (Active Directory, gMSA, BitLocker) are mentioned explicitly and often before or instead of Linux equivalents. Examples and instructions for running services under security accounts focus on Windows (domain accounts, gMSA), with Linux alternatives either missing or referenced only briefly. Disk encryption is discussed with a PowerShell/BitLocker focus, while Linux disk encryption is left as a TODO. There are no Linux-specific code samples or detailed instructions for Linux security features.
Recommendations
  • Add explicit Linux examples for running services under local/system accounts and securing resources, including references to Linux user/group management.
  • Provide parity for disk encryption: include instructions and references for encrypting disks on Linux clusters (e.g., using dm-crypt/LUKS), not just BitLocker/PowerShell.
  • When mentioning Windows-specific features (Active Directory, gMSA), also describe Linux equivalents or alternatives (e.g., LDAP, local users/groups, systemd service accounts).
  • Ensure code samples and walkthroughs are available for both Windows and Linux environments, especially for certificate management, service startup scripts, and endpoint security.
  • Review and update the documentation to avoid Windows-first ordering; present cross-platform options side-by-side or in parallel sections.
GitHub Create Pull Request
Service Fabric Capacity planning and scaling for Azure Service Fabric ...bric/service-fabric-best-practices-capacity-scaling.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a Windows bias in several ways: PowerShell commands are used exclusively for manual scaling operations, with no equivalent Linux shell or cross-platform CLI examples provided. Windows-centric tools and patterns (such as PowerShell cmdlets like Disable-ServiceFabricNode and Remove-ServiceFabricNodeState) are referenced without mention of Linux alternatives. The step-by-step instructions for scaling in and out begin with PowerShell commands, and there is no guidance for users managing Service Fabric clusters from Linux environments. While links to Linux cluster creation are present in 'Next steps', the operational guidance throughout the page is Windows-first and omits Linux parity.
Recommendations
  • Provide equivalent Linux shell (bash) or Azure CLI examples for all PowerShell commands, especially for node management and scaling operations.
  • Explicitly mention cross-platform tools and workflows where possible, and clarify which commands are OS-specific.
  • Include guidance or references for managing Service Fabric clusters from Linux environments, such as using Azure CLI, REST API, or Service Fabric SDK for Linux.
  • Balance the order of examples and instructions so that Linux and Windows approaches are presented equally, or clarify when an example is Windows-specific.
  • Add a table or section summarizing available management tools for both Windows and Linux, including PowerShell, Azure CLI, REST API, and Service Fabric Explorer.
GitHub Create Pull Request
Service Fabric Service Fabric cluster capacity planning considerations ...cles/service-fabric/service-fabric-cluster-capacity.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools and configuration files (e.g., 'AzureDeploy.json', 'Remove-ServiceFabricNodeState', and 'service-fabric-cluster-config-upgrade-windows-server.md') without providing equivalent Linux examples or mentioning Linux-specific tools. Instructions for standalone clusters are only given for Windows, and automation of updates is discussed only in the context of Windows. Linux scenarios, tools, or configuration patterns are not mentioned or illustrated.
Recommendations
  • Add explicit examples and instructions for Linux-based Service Fabric clusters, including configuration, scaling, and upgrade procedures.
  • Reference Linux equivalents for configuration files and management tools (e.g., provide guidance for cluster config changes using Linux paths and tools).
  • Include automation and update strategies for Linux clusters, such as using cron jobs or Linux-native patch orchestration tools.
  • When mentioning Windows-specific commands or files, provide parallel Linux commands or configuration file formats.
  • Ensure that documentation for standalone clusters covers both Windows and Linux environments equally, with clear sectioning and parity in depth.
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
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell command examples for managing node tags and service requirements, without any equivalent examples for Linux environments (e.g., Bash, CLI). The use of PowerShell and Windows-centric tools is emphasized, and there is no mention of Linux-specific workflows or cross-platform command-line alternatives. This may hinder Linux users from easily following the documentation or applying the feature in non-Windows environments.
Recommendations
  • Add Azure CLI or Bash examples for all PowerShell commands shown, demonstrating how to manage node tags and service requirements from Linux environments.
  • Explicitly mention cross-platform support and provide guidance for Linux administrators, including any prerequisites or differences in workflow.
  • Reference REST API usage with curl or similar tools to show platform-agnostic approaches.
  • Ensure that examples and instructions are presented in a way that does not assume a Windows environment by default.
GitHub Create Pull Request
Service Fabric On-demand backup in Azure Service Fabric ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-backup-restore-service-ondemand-backup.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell-based examples and instructions, which are native to Windows environments. All command-line operations, REST API calls, and module installation steps are shown using PowerShell syntax and Windows-centric tools (e.g., Microsoft.ServiceFabric.Powershell.Http). There are no equivalent examples or instructions for Linux users (such as Bash, curl, or Azure CLI), nor is there mention of cross-platform alternatives. The documentation implicitly assumes the user is operating in a Windows environment, making it less accessible to Linux or macOS administrators.
Recommendations
  • Add Linux/Bash examples for all PowerShell commands, using curl or wget for REST API calls.
  • Provide Azure CLI equivalents for Service Fabric operations where possible.
  • Include instructions for installing and using Service Fabric tools on Linux and macOS.
  • Explicitly state cross-platform support and limitations for Service Fabric backup operations.
  • Reorganize examples to present both Windows and Linux approaches side-by-side, or clarify platform-specific sections.
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
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides command-line examples exclusively using PowerShell for service creation and update, which is primarily a Windows tool. There are no Linux shell (bash/CLI) equivalents or references to Linux-native tools. The ordering and presence of examples suggest a Windows-first approach, and Linux users are left without guidance for equivalent operations.
Recommendations
  • Add equivalent Linux CLI examples using Azure CLI or Service Fabric CLI (sfctl) for all PowerShell commands.
  • Explicitly mention platform compatibility for each example, clarifying which commands are for Windows and which are for Linux.
  • Include notes or sections for Linux users, detailing how to perform the same tasks on Linux clusters.
  • Ensure that documentation does not assume PowerShell as the default, and present cross-platform options side-by-side where possible.
GitHub Create Pull Request
Service Fabric Roll over an Azure Service Fabric cluster certificate ...vice-fabric/service-fabric-cluster-rollover-cert-cn.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides only a Windows PowerShell script for rolling over an Azure Service Fabric cluster certificate, with no equivalent Bash, CLI, or Linux-based example. The instructions and file paths are Windows-centric, and there is no mention of Linux tooling or cross-platform alternatives.
Recommendations
  • Add equivalent instructions and examples using Azure CLI and Bash scripts suitable for Linux environments.
  • Include notes on how to perform certificate management tasks on Linux-based Service Fabric clusters.
  • Use platform-neutral file paths and commands where possible, or provide both Windows and Linux variants.
  • Explicitly mention cross-platform support and link to relevant documentation for Linux users.
GitHub Create Pull Request
Service Fabric Scale a Service Fabric cluster in or out .../service-fabric/service-fabric-cluster-scale-in-out.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a Windows bias by predominantly featuring PowerShell commands and Windows-centric tools (e.g., Remove-ServiceFabricNodeState cmdlet, Get-ServiceFabricNode), with most examples and instructions given in PowerShell before CLI or sfctl equivalents. There is little to no mention of Linux-specific workflows, and Linux-friendly alternatives are not highlighted or explained. The documentation assumes familiarity with Windows tooling and omits guidance for Linux users, such as bash scripting or Linux-native Service Fabric management patterns.
Recommendations
  • Provide Linux-specific examples and workflows alongside PowerShell, such as bash scripts or equivalent commands using sfctl and Azure CLI.
  • Clearly indicate which commands and tools are platform-specific (Windows vs. Linux) and offer parity in instructions for both environments.
  • Where PowerShell is used, offer the same step-by-step guidance using Azure CLI and sfctl, with explicit notes for Linux users.
  • Add a section or callouts for Linux administrators, including troubleshooting tips and best practices for Service Fabric management on Linux.
  • Review references to Windows-only features (e.g., Hyper-V, dynamic memory driver) and clarify their relevance or alternatives for Linux clusters.
GitHub Create Pull Request
Service Fabric Azure Service Fabric standalone cluster scaling ...ce-fabric/service-fabric-cluster-scaling-standalone.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-specific tools and patterns, such as PowerShell cmdlets (Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade), and linking to guides that focus on Windows Server. There are no examples or instructions for scaling Service Fabric standalone clusters on Linux, nor are Linux tools or commands mentioned. The documentation implicitly assumes a Windows environment for standalone clusters, which may exclude or confuse users deploying Service Fabric on Linux.
Recommendations
  • Provide equivalent Linux instructions and examples, including relevant shell commands and configuration steps.
  • Reference Linux-compatible tools (e.g., Service Fabric CLI, REST API) alongside or before Windows-specific tools.
  • Add links to documentation for scaling Service Fabric clusters on Linux, if available.
  • Clarify which instructions are Windows-specific and offer Linux alternatives where possible.
  • Ensure that terminology and examples do not assume a Windows-only environment for standalone clusters.
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 page exhibits strong Windows bias: all instructions, requirements, and examples are exclusively for Windows Server environments. Only Windows OS versions are mentioned, with no reference to Linux. All tooling (e.g., PowerShell scripts, Windows services, NTFS, SMB, RemoteRegistry, Windows Firewall) is Windows-specific, and there are no Linux equivalents or alternative instructions. The configuration validation uses a PowerShell script with no mention of a cross-platform or Linux-compatible tool.
Recommendations
  • Add equivalent instructions and requirements for deploying Service Fabric clusters on Linux machines, including supported distributions and prerequisites.
  • Provide Linux-specific examples for configuration, environment setup, and validation, such as shell scripts or CLI commands.
  • Mention Linux file system requirements and alternatives to Windows services (e.g., systemd, firewalld, etc.).
  • Include download links and instructions for Service Fabric standalone packages for Linux.
  • Document how to validate cluster configuration and environment on Linux, possibly with Bash scripts or cross-platform tools.
  • Ensure parity in troubleshooting and next steps for Linux deployments.
GitHub Create Pull Request
Service Fabric Upgrade an Azure Service Fabric standalone cluster ...ce-fabric/service-fabric-cluster-upgrade-standalone.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 Windows bias by referencing Windows-specific upgrade guides and tools, such as linking to 'service-fabric-cluster-upgrade-windows-server.md' and 'service-fabric-cluster-config-upgrade-windows-server.md' for upgrade and configuration instructions. The Patch Orchestration Application is described only for Windows, with no mention of Linux equivalents or guidance. There are no Linux-specific examples, instructions, or tool references, and Windows is implicitly treated as the default platform.
Recommendations
  • Add equivalent Linux-specific upgrade and configuration guides, and link to them alongside or before Windows guides.
  • Include examples and instructions for Linux environments (e.g., using bash, Linux-native tools, or configuration files).
  • Mention and document Linux-compatible patch orchestration solutions, or clarify the status of POA on Linux clusters.
  • Ensure that references to platform-specific documentation are balanced and clearly labeled for both Windows and Linux users.
GitHub Create Pull Request
Service Fabric Upgrading Azure Service Fabric clusters ...icles/service-fabric/service-fabric-cluster-upgrade.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits Windows bias by referencing Windows-specific tools and workflows (such as Patch Orchestration Application and NTLM settings) without mentioning Linux equivalents or providing Linux-specific guidance. Examples for cluster management (certificates, ports) mention PowerShell/Azure CLI, but do not clarify Linux compatibility or provide Linux shell examples. The OS patching section links only to Windows patching documentation, omitting Linux node upgrade guidance.
Recommendations
  • Add explicit Linux examples and workflows for cluster management tasks (e.g., certificate management, port changes) using Bash/Azure CLI on Linux.
  • Include references and links to documentation for patching/upgrading Linux-based Service Fabric cluster nodes.
  • Clarify tool compatibility (e.g., Azure CLI usage on Linux vs. PowerShell on Windows) and provide parity in example commands.
  • Mention Linux-specific considerations (such as authentication, file system differences, or service management) where relevant.
  • Ensure that all references to OS-level operations (patching, NTLM settings) include both Windows and Linux contexts, or clearly state if a feature is Windows-only.
GitHub Create Pull Request
Service Fabric Scalability of Service Fabric services .../service-fabric/service-fabric-concepts-scalability.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a Windows bias by providing PowerShell examples and references to Windows-specific tools (e.g., Service Fabric PowerShell cmdlets) without equivalent Linux CLI or scripting examples. Windows tools and patterns are mentioned first and exclusively, with no mention of Linux-native management approaches (such as sfctl or bash scripts). The lack of Linux parity in examples and tooling guidance may hinder Linux users from fully utilizing Service Fabric's scalability features.
Recommendations
  • Add equivalent Linux examples using sfctl, bash, or other Linux-native tools alongside PowerShell examples.
  • Explicitly mention Linux management workflows and tools where Windows tools (e.g., PowerShell cmdlets) are referenced.
  • Ensure that code samples and administrative actions are presented for both platforms, ideally side-by-side.
  • Include a section or callout highlighting platform-specific differences in scaling operations and tooling.
  • Review references to Windows tools and ensure Linux alternatives are provided or linked.
GitHub Create Pull Request
Service Fabric Overview of Service Fabric and containers ...s/service-fabric/service-fabric-containers-overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. Windows container scenarios and tools (IIS, ASP.NET MVC, Mirantis Container Runtime, Windows Server containers) are mentioned in detail, often before or with more emphasis than Linux equivalents. The 'IIS lift and shift' scenario is Windows-specific, and references to Windows container tutorials and resources appear alongside or before Linux ones. Linux container examples are present but less detailed, and some scenarios lack Linux-specific guidance.
Recommendations
  • Add equivalent Linux-focused scenarios, such as Apache/Nginx lift-and-shift, to balance the IIS example.
  • Ensure Linux container tutorials and references are presented with equal prominence and detail as Windows ones.
  • Include Linux-specific tools and patterns (e.g., systemd, SELinux, AppArmor) where relevant.
  • Expand on Linux container runtime options and their configuration, not just Docker.
  • Review ordering so that Linux and Windows examples are interleaved or Linux is presented first in some cases.
  • Clarify any feature parity gaps between Linux and Windows containers in Service Fabric.
GitHub Create Pull Request
Virtual Machines Use Azure Policy to restrict VM extension installation (Windows) ...al-machines/extensions/extensions-rmpolicy-howto-ps.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 environments, with all examples and instructions using Azure PowerShell and referencing Windows VM extensions. There are no Linux-specific examples, nor is there mention of using Azure CLI or Bash. The customer intent, article title, and collection metadata all reinforce a Windows-centric approach, and Linux VM extension management is not addressed.
Recommendations
  • Add equivalent examples for Linux VMs, including how to restrict Linux-specific extensions.
  • Provide Azure CLI and Bash examples alongside PowerShell to support cross-platform usage.
  • Clarify which steps are universal and which are Windows-specific; consider splitting content into Windows and Linux sections.
  • Update metadata and customer intent to reflect support for both Windows and Linux environments.
  • Mention Linux troubleshooting tools and extension types where relevant.
GitHub Create Pull Request
Service Fabric Induce Chaos in Service Fabric clusters ...cles/service-fabric/service-fabric-controlled-chaos.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a clear Windows bias. All code examples provided are in C# and PowerShell, both of which are traditionally Windows-centric. PowerShell is featured heavily, with no mention of Linux shell equivalents or cross-platform command-line usage. References to Service Fabric PowerShell modules and commands are made without any Linux CLI or Bash alternatives. There are no instructions or examples for running Chaos from Linux environments, nor is there guidance for using Service Fabric on Linux clusters. The documentation implicitly assumes a Windows development and operational environment.
Recommendations
  • Add Linux/Bash shell examples for running Chaos and retrieving reports, using Service Fabric CLI (sfctl) or REST API calls with curl.
  • Explicitly mention cross-platform tools (e.g., sfctl) and provide usage instructions for Linux and macOS environments.
  • Reorder examples so that REST API or CLI usage is presented before or alongside PowerShell, to avoid Windows-first bias.
  • Include notes on differences or requirements for running Service Fabric and Chaos on Linux clusters.
  • Reference official documentation for Linux usage and provide links to relevant resources.
GitHub Create Pull Request
Service Fabric Event Aggregation with Microsoft Azure Diagnostics ...ic/service-fabric-diagnostics-event-aggregation-wad.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a Windows bias in several ways. Windows and PowerShell tools and patterns are mentioned and used exclusively or before Linux equivalents. Examples and instructions are centered around Windows tooling (WAD, PowerShell, Visual Studio), with little to no mention of Linux-specific diagnostics (LAD) or command-line examples. The page references Windows-centric logging mechanisms (ETW), and links to Windows-focused templates and guides. Linux alternatives are only referenced in a selector at the top, with no parity in examples or walkthroughs within the main content.
Recommendations
  • Include Linux-specific examples and instructions alongside Windows ones, especially for diagnostics extension deployment, configuration, and log collection.
  • Provide equivalent Linux command-line examples (e.g., Azure CLI, bash scripts) instead of only PowerShell.
  • Reference Linux diagnostics tools (LAD) and logging mechanisms (such as syslog, journald) where ETW and Windows EventSource are discussed.
  • Ensure links to Linux documentation are as prominent and detailed as Windows ones, and avoid referencing only Windows templates or guides.
  • Add troubleshooting and configuration guidance for Linux clusters, including performance counter collection and Application Insights integration.
  • Where Visual Studio is mentioned, provide alternatives for Linux development environments (e.g., VS Code, command-line tools).
GitHub Create Pull Request
Service Fabric Create a cluster using certificate common name ...-fabric/service-fabric-create-cluster-using-cert-cn.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page exhibits a strong Windows bias. All command-line examples use PowerShell, with Windows-style file paths and commands. There are no equivalent instructions or examples for Linux users (e.g., Bash, Azure CLI, or Linux file paths). The template referenced is specifically for Windows nodes, and Windows-centric tools and patterns are used throughout, with no mention of Linux alternatives or cross-platform approaches.
Recommendations
  • Provide equivalent Linux/Bash examples for certificate management, key vault operations, and template deployment using Azure CLI.
  • Reference or include templates for Linux-based Service Fabric clusters, not just Windows node templates.
  • Use cross-platform file paths and avoid hardcoding Windows-specific paths (e.g., C:\users\sfuser\...).
  • Mention and demonstrate use of Azure CLI, which is cross-platform, alongside PowerShell.
  • Clarify which steps are OS-agnostic and which are specific to Windows, and provide guidance for Linux users where necessary.
  • Add notes or sections explicitly addressing Linux deployment scenarios and tools.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Events ...es/service-fabric/service-fabric-diagnostics-events.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias by primarily referencing Windows-centric event logging mechanisms (ETW/Windows Event logs), mentioning the Windows Azure diagnostics agent, and omitting explicit instructions or examples for accessing Service Fabric events on Linux clusters. No Linux-specific tools, logging channels, or parity examples are provided.
Recommendations
  • Include examples and instructions for accessing Service Fabric events on Linux clusters, such as using syslog, journald, or other Linux-native logging mechanisms.
  • Mention Linux-compatible diagnostics agents or alternatives to the Windows Azure diagnostics agent.
  • Provide parity in documentation by listing both Windows and Linux event access methods, and ensure examples are given for both platforms.
  • Clarify whether the described event logging and monitoring approaches apply to Linux clusters, and if not, provide Linux-specific guidance.
GitHub Create Pull Request
Service Fabric Report and check health with Azure Service Fabric ...ric-diagnostics-how-to-report-and-check-service-health.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a strong Windows bias. All examples and instructions assume a Windows development environment, specifically referencing Visual Studio, PowerShell, and Windows-specific tools like Local Cluster Manager. There are no Linux equivalents or cross-platform alternatives provided for cluster creation, application deployment, or health checking. The use of PowerShell is pervasive, and Linux command-line or scripting options are not mentioned.
Recommendations
  • Add instructions and examples for Linux environments, including how to create a secure dev cluster using Bash or Azure CLI.
  • Provide deployment and health check steps using cross-platform tools (e.g., Azure CLI, REST API, or Service Fabric CLI) instead of or alongside PowerShell.
  • Include guidance for using VS Code or other cross-platform IDEs, not just Visual Studio.
  • Mention Linux-compatible Service Fabric Explorer access methods and clarify how to manage clusters on Linux.
  • Ensure all code and tool references are platform-neutral or provide parallel instructions for both Windows and Linux.
GitHub Create Pull Request
Service Fabric Enable disk encryption for Linux clusters ...c/service-fabric-enable-azure-disk-encryption-linux.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, while focused on enabling disk encryption for Linux clusters, exhibits several signs of Windows bias. PowerShell commands are presented first and in greater detail throughout, with Azure CLI equivalents often appearing as secondary or afterthoughts. Paths and examples use Windows-style file paths (e.g., c:\certificates), and certificate management steps are described using PowerShell cmdlets without Linux-native alternatives (such as OpenSSL or Linux file system paths). There is an absence of Linux shell scripting examples, and the documentation assumes familiarity with Windows tooling and conventions.
Recommendations
  • Present Azure CLI and Linux-native commands before or alongside PowerShell examples, especially in Linux-focused documentation.
  • Replace Windows file paths (e.g., c:\certificates) with Linux equivalents (e.g., /home/user/certificates) in examples and variable declarations.
  • Include Linux-native certificate management instructions (e.g., using OpenSSL) for creating and managing certificates.
  • Provide bash shell scripting examples for automation steps, not just PowerShell.
  • Clarify any differences in workflow or tooling between Windows and Linux environments, and ensure Linux users are not required to use Windows-specific tools.
  • Review and update prerequisite steps to include Linux-native methods for tasks such as secure string handling and file management.
GitHub Create Pull Request
Service Fabric Azure Service Fabric disaster recovery ...les/service-fabric/service-fabric-disaster-recovery.md
High 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 Windows bias in several ways: it references Windows-specific tools and APIs (such as PowerShell cmdlets like Repair-ServiceFabricPartition), links to Windows Server setup guides before Linux equivalents, and omits explicit Linux or cross-platform command examples. The troubleshooting and recovery instructions focus on Windows-centric patterns and do not provide parity for Linux environments, nor do they mention Linux-specific Service Fabric management tools or commands.
Recommendations
  • Include Linux-specific examples and instructions for disaster recovery operations, such as using Service Fabric CLI (sfctl) or REST APIs.
  • Reference both Windows and Linux setup guides equally, or provide a cross-platform section for standalone cluster creation.
  • When mentioning PowerShell cmdlets, also provide equivalent sfctl or REST API commands for Linux users.
  • Explicitly state which procedures or tools are platform-specific, and offer alternatives for Linux environments.
  • Add troubleshooting steps and examples relevant to Linux clusters, such as collecting logs or managing processes.
  • Ensure links to documentation for both Windows and Linux Service Fabric management are present and balanced.
GitHub Create Pull Request
Service Fabric Performance monitoring with Azure Diagnostics .../service-fabric/service-fabric-diagnostics-perf-wad.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation page demonstrates a strong Windows bias. It focuses almost exclusively on the Windows Azure Diagnostics (WAD) extension, with detailed configuration and deployment steps for Windows clusters. Linux clusters are mentioned only briefly, with a link to a separate page for setup, and no Linux-specific configuration or example is provided. All code samples and deployment instructions use Windows-centric tools and patterns (ARM templates, PowerShell), and references to performance counters use Windows-specific syntax. There is no parity in example depth or guidance for Linux users.
Recommendations
  • Include equivalent Linux configuration steps and examples for performance counter collection using the Log Analytics agent.
  • Provide sample configuration files or scripts for Linux clusters, such as agent configuration or relevant shell commands.
  • Add deployment instructions for Linux clusters, using CLI tools (e.g., Azure CLI, Bash) rather than only PowerShell.
  • Present both Windows and Linux options side-by-side, or clearly separate them with equal detail and prominence.
  • Reference Linux-specific performance counters and monitoring patterns where applicable.
GitHub Create Pull Request
Service Fabric Reliable Collection object serialization ...c-reliable-services-reliable-collections-serialization.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias primarily through its 'Next steps' section, which lists Windows-centric tools (Visual Studio, PowerShell) for application upgrades and omits Linux equivalents or cross-platform alternatives. There are no examples or instructions for Linux users, and Windows tools are mentioned before any other options. The serialization examples are platform-neutral, but the guidance for upgrades is Windows-focused.
Recommendations
  • Add equivalent instructions and tutorials for upgrading applications using Linux tools (e.g., Azure CLI, Bash scripts) and reference them alongside Windows tools.
  • Include explicit examples or links for Linux environments in the 'Next steps' section, such as 'Upgrading your Application Using Azure CLI' or 'Upgrading your Application Using Bash'.
  • Ensure that cross-platform upgrade paths are documented and presented with parity to Windows options, rather than listing Windows tools first.
  • Clarify which features and APIs are available and supported on Linux clusters, and provide guidance for Linux users where relevant.
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
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by focusing exclusively on C# examples that use Windows-centric certificate stores (e.g., StoreLocation.LocalMachine, StoreName="My") and thumbprint-based certificate selection. While there is a brief note about Linux certificate storage (PEM files in /var/lib/sfcerts), all code samples and configuration snippets assume Windows conventions and APIs. No Linux-specific code samples, configuration details, or troubleshooting guidance are provided for securing service remoting communications in C# on Linux Service Fabric clusters.
Recommendations
  • Provide parallel C# code samples and configuration instructions for Linux clusters, including how to reference PEM-formatted certificates and any differences in API usage or configuration.
  • Explicitly document the differences in certificate handling between Windows and Linux, such as store location, format, and access patterns.
  • Include troubleshooting tips or common issues for Linux deployments, such as permissions or file format errors.
  • Ensure that Linux-specific instructions are given equal prominence and detail as Windows instructions, rather than relegating them to a brief note.
  • Consider adding a selector or section for 'C# on Linux' to match the parity of 'C# on Windows' and 'Java on Linux'.
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 ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates a strong Windows bias. All step-by-step examples use Windows Server SKUs and PowerShell commands, with no equivalent Bash, CLI, or Linux-native instructions. Windows terminology and tooling (e.g., file paths like C:\, certificate store locations, Windows-specific Service Fabric commands) are used throughout. Linux is only briefly mentioned in a single section about changing the OS SKU, but no full Linux workflow or examples are provided.
Recommendations
  • Provide parallel Linux examples for all steps, including cluster deployment, certificate management, and node operations, using Bash, Azure CLI, and Linux file paths.
  • Include instructions for using Linux-based Service Fabric clusters, such as Ubuntu, with relevant ARM template parameters and deployment details.
  • Replace or supplement PowerShell commands with Azure CLI equivalents, and show how to run them on Linux/macOS.
  • Document Linux-specific certificate handling (e.g., using OpenSSL, PEM files, Key Vault integration from Linux).
  • Ensure all references to file paths, certificate stores, and tooling are cross-platform, or clearly indicate OS-specific differences.
  • Add troubleshooting and validation steps for Linux clusters, including connecting to the cluster and checking health status from Linux environments.
GitHub Create Pull Request
Service Fabric Run a script when an Azure Service Fabric service starts ...fabric/service-fabric-run-script-at-service-startup.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a strong Windows bias. All code and script examples use Windows-specific tools and patterns, such as batch files (.bat), PowerShell commands, and Windows environment variable management. The instructions reference Visual Studio and Windows file paths, and debugging steps are tailored to Windows clusters. Linux is mentioned only briefly, with no concrete Linux shell script or example provided. The page assumes a Windows development environment and does not offer parity for Linux users.
Recommendations
  • Provide equivalent Linux examples using shell scripts (e.g., MySetup.sh) and bash commands for environment variable management.
  • Show how to configure and deploy setup entry points for Linux clusters, including file paths and permissions.
  • Include instructions for adding and packaging shell scripts in non-Windows development environments.
  • Demonstrate debugging and log access for Linux clusters, referencing typical Linux file system paths.
  • Balance PowerShell and batch file examples with bash and shell script alternatives, and clarify platform-specific differences throughout the documentation.
GitHub Create Pull Request
Virtual Machines Convert managed disks storage between different disk types .../main/articles/virtual-machines/disks-convert-types.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell (a Windows-centric tool) is consistently presented before Azure CLI in code example tabs, and PowerShell scripts are shown in full detail. The use of PowerShell as a primary automation example can be intimidating or less relevant for Linux users, even though Azure CLI is cross-platform. References to converting unmanaged disks mention both CLI and PowerShell, but the PowerShell link is listed second in one place and first in another. There is no explicit Linux shell scripting (bash) example, and the overall structure and language tend to favor Windows tools and patterns.
Recommendations
  • Alternate the order of PowerShell and CLI examples so that CLI is presented first in some sections, especially those relevant to Linux users.
  • Add explicit bash scripting examples for common disk conversion tasks to improve accessibility for Linux administrators.
  • Clarify that Azure CLI is cross-platform and suitable for both Windows and Linux environments.
  • Where PowerShell is used, note its availability on Linux and macOS, but also provide native bash alternatives.
  • Ensure that references to conversion guides (unmanaged to managed disks) mention Linux/CLI first or equally.
  • Consider adding a short section or callout for Linux-specific considerations or best practices.
GitHub Create Pull Request
Virtual Machines Create a Gallery for Sharing Resources .../blob/main/articles/virtual-machines/create-gallery.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides examples for Azure Portal, Azure CLI, PowerShell, and REST API. However, PowerShell is a Windows-centric tool and is presented as a primary automation option alongside CLI, without any mention of Linux shell scripting or native Linux tools. There are no explicit Linux/Bash examples (e.g., using Bash variables, scripting patterns, or references to Linux environments), and the PowerShell example is more detailed than the CLI example. This may give the impression of Windows preference and insufficient Linux parity.
Recommendations
  • Add explicit Bash/Linux shell examples for each CLI scenario, using Bash variables and scripting patterns.
  • Clarify that Azure CLI commands work cross-platform and provide sample Bash scripts for Linux users.
  • Balance the detail level between PowerShell and CLI examples, ensuring CLI/Bash examples are as comprehensive as PowerShell ones.
  • Mention Linux-native automation tools or scripting environments where relevant.
  • Consider adding a note about cross-platform support for Azure CLI and REST API.
GitHub Create Pull Request
Virtual Machines Create Virtual Machine restore points ...ain/articles/virtual-machines/create-restore-points.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell and Windows-specific consistency features more prominently than Linux equivalents. PowerShell is mentioned as a primary tool for interacting with restore points, while Linux tools or CLI examples are less visible or absent. Application consistency is highlighted for Windows VMs, whereas Linux VMs are only mentioned in the context of file system consistency. There are no explicit Linux or cross-platform command-line examples provided, and Windows tools are referenced before Linux alternatives.
Recommendations
  • Provide equivalent CLI (az CLI) examples alongside PowerShell for all operations, ensuring Linux users have clear guidance.
  • Explicitly mention Linux support and parity in restore point features, including any limitations or differences.
  • Add bash shell and REST API usage examples that can be run on Linux systems.
  • Ensure documentation references Linux tools and workflows as frequently and prominently as Windows/PowerShell ones.
  • Clarify any differences in consistency modes between Windows and Linux VMs, and provide guidance for both.
GitHub Create Pull Request
Virtual Machines Delete a VM and attached resources ...ute-docs/blob/main/articles/virtual-machines/delete.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page provides examples for Azure Portal, Azure CLI, PowerShell, and REST API. However, PowerShell examples are given equal prominence to CLI, despite PowerShell being primarily a Windows tool. REST API examples often use Windows-centric values (e.g., Windows images, Windows admin settings) and do not show Linux-specific configurations. There are no explicit Linux shell (bash) examples, nor are Linux-specific patterns or considerations discussed. The FAQ and main content do not mention Linux-specific behaviors, and Windows terminology (e.g., 'MicrosoftWindowsServer', 'osType': 'Windows') appears in sample payloads before any Linux equivalent. The only reference to Linux is in the 'Next steps' section, which links to a Linux tutorial, but this is not integrated into the main instructional content.
Recommendations
  • Add explicit Linux shell (bash) examples alongside PowerShell, especially for common VM management tasks.
  • In REST API examples, alternate between Windows and Linux image references, or provide both in parallel.
  • Include Linux-specific configuration details (e.g., 'osType': 'Linux', Linux admin settings) in sample payloads.
  • Discuss any differences in delete behavior or resource management for Linux VMs, if applicable.
  • Ensure that CLI examples use Linux-friendly patterns (e.g., bash syntax, environment variables) and clarify cross-platform usage.
  • Balance the order of presentation so that Linux and Windows are treated equally (e.g., alternate which is shown first in examples or explanations).
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
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by listing Azure PowerShell (typically Windows-centric) examples before Azure CLI (cross-platform) in all command sections, referencing PowerShell modules and a 'managed-disks-powershell-getting-started' sample repository in 'Next steps', and mentioning Windows tools and patterns more prominently. While Linux is marked as supported, there are no Linux-specific examples, screenshots, or workflow notes, and the portal instructions do not differentiate between Windows and Linux VM deployment nuances.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or present CLI examples first to emphasize cross-platform parity.
  • Include Linux-specific deployment notes or screenshots, especially where VM configuration may differ.
  • Reference Linux-focused sample repositories or documentation in the 'Next steps' section.
  • Explicitly mention any differences or considerations for Linux VMs in relevant sections.
  • Ensure that all command-line instructions are clearly marked as cross-platform where applicable.
GitHub Create Pull Request
Virtual Machines Migrate Standard HDD OS disks by September 08, 2028 ...n/articles/virtual-machines/disks-hdd-os-retirement.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page mentions both Linux and Windows VMs as affected, but the example commands and tooling references prioritize Windows-centric tools and patterns. The Azure PowerShell module is mentioned before Azure CLI, and the PowerShell example is given in detail, while the CLI example is less prominent. The Disk Storage Center, a GUI tool familiar to Windows users, is referenced first for listing disks, with CLI and PowerShell as alternatives. There are no Linux-specific migration examples or guidance.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and more familiar to Linux users.
  • Include Linux-specific migration steps or considerations, such as scripting with Bash or using Linux-native tools.
  • Explicitly mention that all commands can be run from Linux, macOS, or Windows, and provide sample Bash scripts for disk listing and migration.
  • Balance references to GUI tools (Disk Storage Center) with command-line alternatives, and clarify their cross-platform availability.
  • Add troubleshooting or migration tips relevant to Linux VMs, such as handling fstab updates or GRUB bootloader changes after disk migration.
GitHub Create Pull Request
Virtual Machines Instantly access managed disk snapshots ...les/virtual-machines/disks-instant-access-snapshots.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, Portal, and Resource Manager templates, but does not include explicit Linux shell (bash) or cross-platform scripting examples. Azure PowerShell is featured prominently, which is traditionally associated with Windows environments. There are no references to Linux-specific tools, nor are there instructions or examples tailored for Linux users (e.g., bash scripts, Linux authentication patterns). The ordering of examples often places PowerShell before Portal or Resource Manager, and there is no mention of Linux-specific considerations or troubleshooting.
Recommendations
  • Add explicit bash shell examples for Linux users, including variable declaration and command execution.
  • Clarify that Azure CLI commands are cross-platform and provide sample usage in both Windows (cmd/PowerShell) and Linux (bash) environments.
  • Include troubleshooting notes or tips for common Linux scenarios (e.g., authentication, file permissions, environment variables).
  • Ensure example ordering alternates or starts with cross-platform tools (Azure CLI) before Windows-specific tools (PowerShell).
  • Mention that Azure PowerShell is available on Linux, but provide guidance for native Linux shell users.
  • Add notes about using the Azure CLI in Linux distributions and any differences in output formatting or environment setup.
GitHub Create Pull Request
Virtual Machines Restrict managed disks from being imported or exported ...tual-machines/disks-restrict-import-export-overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell and Windows-specific tools and links before their Linux/CLI equivalents. The custom RBAC role creation links directly to a PowerShell-based guide, and in several sections, PowerShell is mentioned before CLI or Linux alternatives. There is a general tendency to present Windows/PowerShell options first or exclusively, with less emphasis on Linux-native tools and workflows.
Recommendations
  • Provide equal prominence to Linux/CLI examples and documentation links alongside PowerShell/Windows options.
  • When referencing guides or articles, alternate the order (e.g., CLI before PowerShell) or list both together.
  • Include explicit Linux shell examples for key operations, not just CLI references.
  • Ensure that custom role creation and other administrative tasks have clear, step-by-step instructions for both PowerShell and CLI/bash environments.
  • Audit linked articles to verify Linux parity and update them if necessary.
GitHub Create Pull Request
Virtual Machines What's new in Azure Disk Storage ...blob/main/articles/virtual-machines/disks-whats-new.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits mild Windows bias. Several feature explanations and links reference Windows-specific documentation before Linux equivalents, and some links point only to Windows or PowerShell-centric articles (e.g., expand disks, find unattached disks). In some cases, Linux examples or documentation are missing or referenced after Windows, and Windows tools like PowerShell are mentioned without equal mention of Linux alternatives.
Recommendations
  • Ensure all feature explanations provide both Windows and Linux usage examples, with equal prominence.
  • When linking to platform-specific guides (e.g., expanding disks, finding unattached disks), always include both Windows and Linux links side-by-side.
  • Avoid referencing Windows tools (e.g., PowerShell) exclusively; mention Linux CLI equivalents (e.g., Bash, Azure CLI) in parallel.
  • Audit all documentation links to ensure Linux parity, updating or adding Linux-focused articles where missing.
  • Consider alternating the order of Windows and Linux references to avoid implicit prioritization.
GitHub Create Pull Request
Virtual Machines FAQ Ephemeral OS disks ...in/articles/virtual-machines/ephemeral-os-disks-faq.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides a detailed PowerShell script as the sole example for determining VM support for ephemeral OS disks, without offering equivalent examples for Linux users (e.g., Bash/CLI). PowerShell is a Windows-centric tool, and its exclusive use here prioritizes Windows workflows. Additionally, the mention of 'ARM template deployment/PowerShell/CLI' lists PowerShell before CLI, subtly reinforcing Windows-first patterns. There are no Linux/Bash examples or references to Linux-native tooling.
Recommendations
  • Provide equivalent Bash/Azure CLI script examples for Linux users to determine VM support for ephemeral OS disks.
  • When listing automation options, alternate or randomize the order (e.g., CLI, PowerShell, ARM template) to avoid Windows-first bias.
  • Explicitly mention that all operations can be performed using Azure CLI/Bash on Linux, and link to relevant documentation.
  • Add a note or section highlighting cross-platform support and parity for ephemeral OS disk management.
GitHub Create Pull Request
Virtual Machines Share an Azure managed disk across VMs ...cs/blob/main/articles/virtual-machines/disks-shared.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a moderate Windows bias. Windows clustering tools (WSFC) and workloads are described first and in greater detail, with explicit references to Windows-specific features (CSV, Scale-Out File Server, RDS UPD, etc.) and links to Windows-centric guides. Linux support is mentioned, but Linux examples are less detailed, and there are no step-by-step Linux configuration examples or explicit Linux command-line instructions. Windows tools and patterns (WSFC, CSV) are referenced before their Linux equivalents (Pacemaker, Corosync, ocfs2, gfs2), and the examples section provides more concrete Windows scenarios than Linux ones.
Recommendations
  • Provide step-by-step Linux configuration examples, including commands for setting up Pacemaker/Corosync clusters and using SCSI PR utilities (e.g., sg_persist, fence_scsi).
  • Balance the sample workloads section by including more detailed Linux application scenarios (e.g., clustered file servers, SAP on Linux, machine learning clusters) with links to relevant guides.
  • Ensure that Linux tools and patterns (Pacemaker, Corosync, ocfs2, gfs2) are described with equal prominence and detail as Windows equivalents.
  • Add explicit Linux command-line examples for disk reservation and failover flows.
  • Where possible, present Windows and Linux examples in parallel, rather than listing Windows first.
GitHub Create Pull Request
Virtual Machines Ephemeral OS disks ...b/main/articles/virtual-machines/ephemeral-os-disks.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page generally maintains parity between Windows and Linux, but there are subtle signs of Windows bias. Windows-specific details (e.g., page file placement, cache sizing for Windows images) are presented before or in more detail than Linux equivalents. PowerShell is mentioned before CLI in the customer-managed key section, and the example for cache placement only references Windows Server images, while Linux (Ubuntu) is only mentioned for temp/NVMe placement. There are no explicit Linux command examples, and some technical details (like page file placement) are only described for Windows.
Recommendations
  • Provide Linux-specific technical details where Windows details are given (e.g., swap file placement for Linux).
  • Ensure Linux examples are presented alongside Windows examples, especially in sections discussing disk sizing and placement.
  • Mention CLI and Linux tools before or alongside PowerShell, or provide equal prominence.
  • Add explicit Linux command examples (e.g., Azure CLI commands for Linux VM configuration) where PowerShell is referenced.
  • Clarify any differences in ephemeral disk behavior for Linux VMs, not just Windows.
GitHub Create Pull Request
Virtual Machines Azure Linux VM Agent Overview ...in/articles/virtual-machines/extensions/agent-linux.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_reference ⚠ī¸ windows_first
Summary
The documentation is generally Linux-focused, but there is evidence of Windows bias. Windows tools (putty.exe) are mentioned as a consideration for SSH key types, and a Windows tutorial is referenced before any Linux equivalent in the Ubuntu Cloud Images section. The mention of System Center Virtual Machine Manager deployments is also Windows-centric, though contextually relevant. No Linux command-line examples (e.g., installation commands) are provided, and the only external tutorial link is for Windows VM deployment.
Recommendations
  • Add Linux-specific SSH client recommendations (e.g., OpenSSH, MobaXterm) alongside putty.exe, and clarify platform differences.
  • Provide Linux command-line examples for installing, configuring, and managing waagent (e.g., apt, yum, systemctl usage).
  • Replace or supplement the Windows VM deployment tutorial link with a Linux equivalent for automating deployment using the Custom Script extension.
  • Ensure that all references to Windows tools or workflows are balanced with Linux alternatives, and present Linux-first where appropriate.
GitHub Create Pull Request
Virtual Machines Azure Backup for SQL Server running in Azure VM ...extensions/backup-azure-sql-server-running-azure-vm.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a clear Windows bias. It exclusively discusses the AzureBackupWindowsWorkload extension, which is specific to Windows workloads, and provides only PowerShell-based deployment instructions. There are no examples or guidance for Linux-based SQL Server deployments, nor are Linux tools or command-line patterns mentioned. The documentation assumes the SQL Server is running on Windows, with no consideration for Linux VMs or cross-platform scenarios.
Recommendations
  • Explicitly state whether Linux-based SQL Server VMs are supported or not. If not, clarify this early in the documentation.
  • If Linux support exists, add equivalent instructions and examples for Linux VMs, including relevant extensions, deployment methods, and command-line tools (e.g., Bash, Azure CLI).
  • Provide parity in tooling: alongside PowerShell, include Azure CLI or REST API examples for cross-platform compatibility.
  • Mention any differences in backup process or extension names for Linux VMs, if applicable.
  • Review and update the documentation collection metadata (e.g., ms.collection: windows) to reflect cross-platform support if/when Linux is included.
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: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation page is heavily focused on Windows virtual machines, with all examples, configuration snippets, and explanations tailored exclusively to Windows. There are no Linux-specific examples, configuration details, or references to Linux diagnostics extension usage. Windows tools and conventions (such as Windows event logs, performance counters, and Visual Studio) are mentioned exclusively, and the customer intent and sample templates are Windows-centric. While there is a brief mention of the Linux diagnostics extension (LAD) in the deprecation notice, no practical guidance or parity is provided for Linux users.
Recommendations
  • Provide equivalent examples and configuration snippets for Linux VMs, including how to add monitoring and diagnostics using the Linux diagnostics extension (LAD) and/or Azure Monitor Agent.
  • Include sample XML or JSON configuration for Linux diagnostics, such as syslog, performance counters, and log collection.
  • Reference Linux-specific tools and conventions (e.g., system logs, Linux performance metrics) alongside Windows examples.
  • Add links to Linux-focused quickstart templates and documentation.
  • Ensure that deployment instructions cover both Azure PowerShell (Windows) and Azure CLI (cross-platform), with explicit Linux usage examples.
  • Clarify in the introduction and customer intent that the guidance applies to both Windows and Linux, or provide a separate Linux-focused article.
GitHub Create Pull Request
Virtual Machines Export Azure resource groups that contain VM extensions ...ticles/virtual-machines/extensions/export-templates.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell and Windows tools/scripts before mentioning Azure CLI, listing Windows extensions before Linux ones in several places, and lacking explicit Linux shell (bash) examples for template deployment. The 'ms.collection' metadata is set to 'windows', and the screenshot and workflow descriptions are tailored to the Azure portal, which is often used in Windows environments. There are no direct Linux command-line or automation examples, and the sample deployment scripts are described as 'PowerShell and Azure CLI', with PowerShell mentioned first.
Recommendations
  • Add explicit bash/Linux shell examples for template deployment alongside PowerShell.
  • List Linux and Windows extensions in alphabetical order or group them by OS for parity.
  • Mention Azure CLI before or alongside PowerShell when describing sample deployment scripts.
  • Update metadata to include both Windows and Linux collections if the content is cross-platform.
  • Include screenshots or instructions for using the Azure portal from Linux environments (e.g., browser on Ubuntu).
  • Clarify that all steps and exported templates are usable from both Windows and Linux environments.
GitHub Create Pull Request
Virtual Machines Azure VM Extensions and Features for Linux ...articles/virtual-machines/extensions/features-linux.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
Although the documentation is focused on Linux VM extensions, it consistently presents both Azure CLI and Azure PowerShell examples side-by-side, with PowerShell (a Windows-centric tool) given equal prominence. In some sections, references to ARM templates link to Windows documentation first. There is no mention of Linux-native automation tools (such as Bash scripts outside the Custom Script extension), nor are there examples using Linux-native configuration management tools (like Ansible or cloud-init) for extension management. The troubleshooting and operational guidance is generic, but the example commands and links sometimes prioritize Windows or PowerShell patterns, and there are no examples using Linux shell commands for interacting with Azure resources outside the CLI.
Recommendations
  • Prioritize Azure CLI examples before PowerShell, as CLI is cross-platform and more native to Linux users.
  • Add explicit Bash shell script examples for common extension management tasks, such as using curl, jq, or other Linux tools to interact with Azure REST APIs.
  • Reference ARM template documentation for Linux VMs directly, rather than linking to Windows template docs.
  • Include examples or mentions of Linux-native automation/configuration tools (e.g., Ansible, cloud-init) where relevant.
  • Clarify that PowerShell is available on Linux, but most Linux users prefer CLI or Bash, and adjust examples accordingly.
  • Ensure troubleshooting steps include Linux shell commands for log inspection and status checks, not just Azure CLI.
GitHub Create Pull Request
Virtual Machines Use Application Health extension with Azure Virtual Machines ...ticles/virtual-machines/extensions/health-extension.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_examples_first ⚠ī¸ windows_tools
Summary
The documentation demonstrates a Windows bias in several areas: Windows-based examples (REST API and PowerShell) are presented before Linux equivalents (CLI), PowerShell is heavily featured, and Windows-specific extension types and log paths are mentioned first. Linux examples are present but generally follow Windows ones, and Linux-specific tools or commands are not highlighted or explained in parity with Windows/PowerShell. The documentation does not provide Linux-first or Linux-only scenarios, and the narrative often defaults to Windows VM usage.
Recommendations
  • Alternate the order of examples so that Linux (CLI) examples are presented first in some sections, or provide both Windows and Linux examples side-by-side.
  • Include Bash or shell script examples for Linux users where PowerShell is used for Windows.
  • Explicitly mention Linux-specific extension types and log paths before or alongside Windows equivalents.
  • Add troubleshooting and operational guidance for Linux environments, such as using systemd or journalctl for service health.
  • Ensure that all instructions, screenshots, and sample configurations are equally applicable and clearly labeled for both Windows and Linux.
  • Highlight any differences in extension behavior or configuration between Windows and Linux VMs, and provide guidance for both.
GitHub Create Pull Request
Virtual Machines Azure FPGA Attestation Service ...machines/field-programmable-gate-arrays-attestation.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 provides both PowerShell and Bash examples for attestation, but PowerShell is presented first and in more detail (including monitoring scripts), which may signal a Windows-first bias. The monitoring example is only given for PowerShell, with no equivalent Bash or Linux-native example. References to PowerShell and its installation are prominent, and the documentation mentions using the Azure portal (a GUI tool more commonly used on Windows) for some steps, but not for attestation submission or monitoring. There is no mention of Linux-native tools (such as curl for HTTP requests or monitoring), and Bash examples are less detailed.
Recommendations
  • Provide Bash or Linux-native examples for all steps, including monitoring attestation status (e.g., using curl or a Bash script to poll the HTTP endpoint).
  • Alternate the order of PowerShell and Bash examples, or present them side-by-side to avoid Windows-first perception.
  • Explicitly mention that all CLI commands and scripts are cross-platform, and clarify any platform-specific limitations.
  • Include references to Linux-native tools (e.g., curl, jq) for HTTP requests and status monitoring.
  • Ensure parity in detail and completeness between PowerShell and Bash examples throughout the documentation.
GitHub Create Pull Request
Virtual Machines Azure virtual machine extensions and features .../main/articles/virtual-machines/extensions/overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation demonstrates a mild Windows bias. Windows tools (PowerShell) are mentioned before Linux equivalents when discussing extension management. Troubleshooting guidance for Windows VM extensions is called out first, and PowerShell is listed as a primary management tool alongside Azure CLI, without highlighting Linux-native alternatives. Windows extension examples and links are often presented before Linux ones, and some extension namespaces (e.g., Desired State Configuration) are Windows-specific.
Recommendations
  • Present Linux and Windows management tools (e.g., Azure CLI, Bash, PowerShell) in parallel, or highlight Azure CLI/Bash first for cross-platform parity.
  • Ensure troubleshooting guidance for Linux VM extensions is equally prominent and not secondary to Windows.
  • When listing extension examples or links, alternate the order or group by OS to avoid implicit prioritization.
  • Include Linux-native automation patterns (e.g., cloud-init, shell scripts) alongside PowerShell examples.
  • Clarify when extensions or features are Windows-only or Linux-only to avoid confusion.
  • Add explicit Linux command-line examples (e.g., Bash, Azure CLI) where PowerShell is mentioned.
GitHub Create Pull Request
Virtual Machines Azure support for Generation 2 VMs ...cs/blob/main/articles/virtual-machines/generation-2.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. Windows examples, tools, and references (such as PowerShell and Hyper-V) are presented before or more extensively than Linux equivalents. PowerShell commands are given for key tasks (e.g., creating managed disks from .vhd files), while Linux CLI or shell examples are missing for similar operations. Windows-centric terminology and links (e.g., Hyper-V documentation) are referenced more frequently and earlier than Linux alternatives. Although Linux support is mentioned and some Linux images are listed, actionable Linux examples and parity in tooling are lacking.
Recommendations
  • Provide equivalent Linux CLI or shell commands for all PowerShell examples, especially for tasks like creating managed disks from .vhd files.
  • Include Linux-focused documentation links (e.g., KVM, QEMU, or other common Linux virtualization platforms) alongside or before Windows/Hyper-V references.
  • Ensure that Linux examples (e.g., using Azure CLI or ARM templates for Linux VMs) are presented with equal prominence and detail as Windows examples.
  • Add explicit instructions or code snippets for Linux users in all procedural sections (not just referencing that Linux is supported).
  • Review and balance the order of presentation so that Linux and Windows are treated equally in examples, references, and guidance.
GitHub Create Pull Request
Virtual Machines Hibernation overview ...lob/main/articles/virtual-machines/hibernate-resume.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates mild Windows bias. Windows and PowerShell are mentioned explicitly and repeatedly as supported methods for triggering hibernation, while Linux equivalents (such as Bash or shell commands) are not mentioned. The phrase 'PowerShell' appears before 'CLI' in several lists, and there are no concrete examples or references to Linux-specific tools or commands. The troubleshooting and setup sections reference both Windows and Linux documentation, but the main page lacks parity in examples and tool mentions.
Recommendations
  • Explicitly mention Linux command-line tools (e.g., Bash, shell scripts) alongside PowerShell when listing supported methods for triggering hibernation.
  • Provide example commands for both Windows (PowerShell) and Linux (Bash/Azure CLI) directly on the overview page, not just in linked documentation.
  • When listing supported interfaces (portal, CLI, PowerShell, SDKs, APIs), alternate or randomize the order so Windows tools are not always listed first.
  • Add a brief summary of Linux-specific hibernation steps or considerations on the overview page to match the Windows coverage.
  • Ensure troubleshooting and FAQ sections include Linux-specific examples and not just links.
GitHub Create Pull Request
Virtual Machines Azure Write Accelerator ...es/virtual-machines/how-to-enable-write-accelerator.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits several Windows biases. PowerShell is presented as the primary scripting method with detailed examples, while Linux-native CLI or scripting examples are minimal or absent. Windows disk management tools (Storage Spaces, SOFS) are mentioned before Linux equivalents (LVM, MDADM) in planning sections. The REST API section assumes use of Chocolatey (a Windows package manager) and PowerShell/cmd.exe for installation, with no mention of Linux installation methods. There are no bash or Linux shell script examples for enabling Write Accelerator, and the CLI section is brief and lacks parity with the PowerShell walkthrough.
Recommendations
  • Provide bash/Linux shell script examples for enabling Write Accelerator, matching the detail of PowerShell examples.
  • Mention Linux package managers (e.g., apt, yum, snap) for installing armclient, or provide cross-platform installation instructions.
  • Present Linux disk management tools (LVM, MDADM) before or alongside Windows tools in planning and configuration sections.
  • Expand Azure CLI examples to cover all scenarios shown in PowerShell, with explicit Linux usage notes.
  • Add troubleshooting and operational notes specific to Linux environments.
  • Clarify that all steps are cross-platform where applicable, and highlight any OS-specific differences.
GitHub Create Pull Request
Virtual Machines Install VM Watch ...lob/main/articles/virtual-machines/install-vm-watch.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation provides both Windows and Linux parity in terms of instructions and code samples, but there is a subtle Windows bias. Windows is mentioned first in quickstart links, screenshots, and examples. PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, but no Linux-native shell examples (e.g., Bash) are provided. Screenshots and validation steps consistently show Windows first, and PowerShell is presented as a main automation method, which may not be as familiar to Linux users.
Recommendations
  • Alternate the order of Windows and Linux references, so Linux is sometimes mentioned first.
  • Add Bash shell examples alongside PowerShell for Linux users, especially for automation tasks.
  • Ensure screenshots and walkthroughs alternate or equally represent Linux and Windows environments.
  • Explicitly state that PowerShell is cross-platform, or provide links to Linux-native equivalents where appropriate.
  • Highlight Linux-specific considerations or troubleshooting steps, if any, to ensure parity.
GitHub Create Pull Request
Virtual Machines Use infrastructure automation tools ...articles/virtual-machines/infrastructure-automation.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 generally covers both Linux and Windows automation tools, but there are several areas where Windows examples, tools, or instructions are presented before or instead of Linux equivalents. Some sections (Chef, Puppet) provide only or primarily Windows-focused links, and in others (Azure Resource Manager template, Azure Automation) Windows examples are listed before Linux ones. There is also a tendency to mention Windows-specific tools (PowerShell DSC) more prominently, with Linux support as a secondary note.
Recommendations
  • Ensure that examples and instructions for Linux are provided alongside Windows, especially for tools like Chef and Puppet.
  • Present Linux and Windows examples in parallel or alternate order to avoid implicit prioritization.
  • Where Windows-specific tools are discussed (e.g., PowerShell DSC), highlight Linux equivalents (e.g., cloud-init) with equal prominence.
  • Add links to Linux-focused documentation for Chef and Puppet, not just Windows install guides.
  • Review the ordering of examples and links to avoid listing Windows first by default, especially in sections like Azure Resource Manager template and Azure Automation.
  • Explicitly state Linux support and provide Linux-specific instructions for all tools where applicable.
GitHub Create Pull Request
Virtual Machines Create and upload an Oracle Linux VHD ...les/virtual-machines/linux/oracle-create-upload-vhd.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a Windows bias by consistently referencing Hyper-V (a Windows virtualization tool) as the primary example for creating VHDs, providing links to Windows-centric instructions, and using Hyper-V Manager for VM management steps. There are no examples or instructions for equivalent Linux-based tools (such as KVM, qemu-img, or VirtualBox) for creating or managing VHDs, nor are Linux workflows mentioned for converting or uploading VHDs. The steps for preparing the Oracle Linux VM are presented in the context of Hyper-V, with no Linux-native alternatives provided.
Recommendations
  • Add examples and instructions for creating and managing VHDs using Linux-native tools such as KVM, qemu-img, or VirtualBox.
  • Include Linux command-line workflows for converting disk formats (e.g., using qemu-img to convert raw disks to fixed VHD).
  • Provide guidance for managing and shutting down VMs using Linux virtualization platforms (e.g., virsh, virt-manager) alongside Hyper-V instructions.
  • Reference documentation or tutorials for installing and configuring Oracle Linux VMs on Linux hosts, not just Windows/Hyper-V.
  • Ensure parity in tool recommendations and example order, presenting Linux options before or alongside Windows tools.
GitHub Create Pull Request
Virtual Machines Manage Virtual Machine restore points ...ain/articles/virtual-machines/manage-restore-points.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page exclusively provides Azure PowerShell examples for managing VM restore points, without any equivalent examples for Linux users (e.g., Azure CLI, Bash, or REST API usage). Windows-centric tools and patterns are presented first and solely, which may disadvantage users on Linux or macOS platforms.
Recommendations
  • Add Azure CLI examples for all PowerShell commands, demonstrating equivalent operations for Linux/macOS users.
  • Include REST API sample requests and responses where relevant, to provide platform-neutral guidance.
  • Explicitly mention cross-platform options (PowerShell, CLI, REST) at the start of each procedural section.
  • Where scripts are shown, provide both PowerShell and Bash/CLI versions side-by-side.
  • Clarify that the steps can be performed on any OS using appropriate tools, not just Windows.
GitHub Create Pull Request
Virtual Machines Export an image version to a managed disk ...es/virtual-machines/managed-disk-from-image-version.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for exporting an image version to a managed disk. However, the PowerShell section is extensive and uses Windows-centric tooling (PowerShell cmdlets), which are primarily used on Windows. There is no mention of Bash or Linux shell scripting, nor are Linux-specific tools or patterns discussed. The PowerShell section is detailed and appears after the CLI section, but the CLI examples use syntax compatible with both Windows and Linux, while the PowerShell examples are exclusively Windows-oriented.
Recommendations
  • Add explicit Bash examples for Linux users, showing variable assignment and command usage in a Linux shell.
  • Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and provide notes or examples for common Linux shell environments.
  • Consider including Linux-specific troubleshooting tips or notes about environment differences (e.g., quoting, environment variables).
  • Balance the depth of PowerShell and CLI sections, ensuring Linux users have equally detailed guidance.
  • If possible, mention cross-platform alternatives to PowerShell for scripting these operations.
GitHub Create Pull Request
Virtual Machines Specify Marketplace purchase plan information using Azure PowerShell ...b/main/articles/virtual-machines/marketplace-images.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation is heavily focused on Azure PowerShell, with all command-line examples using PowerShell cmdlets and no equivalent Azure CLI or Bash examples provided. The referenced links and examples (such as network security rules for RDP port 3389) are Windows-centric, and Linux-specific scenarios are not demonstrated, despite the documentation claiming applicability to Linux VMs. There is no mention of Linux tools, shell commands, or patterns, and the ARM template example uses a Windows VM name and RDP port, further reinforcing a Windows-first bias.
Recommendations
  • Add equivalent Azure CLI and Bash examples for all PowerShell commands, especially for Linux users.
  • Include Linux-specific scenarios, such as SSH port configuration and Linux VM naming conventions, in both code and ARM template examples.
  • Reference documentation and examples that are platform-neutral or provide both Windows and Linux paths (e.g., links to Linux-focused image finding guides).
  • Explicitly show how to retrieve and use purchase plan information for Linux VMs, including relevant differences.
  • Avoid using Windows-specific ports (like 3389 for RDP) in generic examples; use SSH (port 22) for Linux or provide both.
GitHub Create Pull Request
Virtual Machines Advanced Configuration for MSP ...s/metadata-security-protocol/advanced-configuration.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 provides a detailed example for a Windows process (WinPA) with explicit Windows paths and process names, while the Linux example is less prominent and not as detailed. Windows-specific tools and patterns (e.g., C:\Windows\OEM\Unattend.wsf.exe, SYSTEM user) are mentioned, but there is no equivalent Linux example for common Linux provisioning agents or system users. The Windows example appears before any Linux-specific example, and there is a lack of parity in showcasing Linux tools or patterns.
Recommendations
  • Add a Linux-focused example for a common provisioning agent (e.g., cloud-init) with typical Linux paths, process names, and users/groups.
  • Ensure that examples for both Windows and Linux are presented with equal prominence and detail.
  • Mention Linux system users (e.g., root) and common Linux agent processes in the same context as Windows examples.
  • Where Windows-specific tools or patterns are referenced, provide the Linux equivalents alongside.
  • Consider alternating the order of Windows and Linux examples to avoid implicit prioritization.
GitHub Create Pull Request
Virtual Machines Azure Dedicated Host SKU Retirement Migration Guide ...l-machines/migration/dedicated-host-migration-guide.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides migration instructions for Azure Dedicated Host SKUs, but consistently lists PowerShell (a Windows-centric tool) before CLI options and does not mention Linux-specific tools or workflows. There are no examples for Bash, Linux shell scripts, or references to Linux admin patterns. The CLI instructions are present, but PowerShell is always listed first, and there is no explicit guidance for Linux users.
Recommendations
  • Alternate the order of PowerShell and CLI instructions, or list CLI first to avoid Windows-first bias.
  • Include Bash or Linux shell script examples for common operations (e.g., stopping/starting VMs, managing scale sets).
  • Explicitly mention that the Azure CLI is cross-platform and provide Linux-specific usage notes or troubleshooting tips.
  • Add references to Linux admin documentation or best practices for migration.
  • Clarify that PowerShell examples are primarily for Windows users, and provide parity for Linux users where possible.
GitHub Create Pull Request
Virtual Machines Migrate Managed image to Compute gallery ...igration/migration-managed-image-to-compute-gallery.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page provides both Azure CLI and PowerShell examples for migrating managed images to Azure Compute Gallery, but the PowerShell example is given equal prominence despite PowerShell being a Windows-centric tool. The CLI example uses Azure CLI, which is cross-platform, but there is no explicit mention or example of Linux shell usage (e.g., bash), nor guidance for Linux-specific environments. The presence of PowerShell and lack of Linux shell examples or notes may indicate a subtle Windows bias.
Recommendations
  • Add explicit bash shell examples for Azure CLI commands, showing usage in Linux environments.
  • Clarify that Azure CLI commands can be run on Linux, macOS, and Windows, and provide any Linux-specific notes (e.g., environment variables, authentication differences).
  • If PowerShell is shown, consider also showing bash/zsh equivalents for parity.
  • Mention cross-platform compatibility in the prerequisites and tool selection guidance.
  • Ensure screenshots and UI instructions do not assume Windows unless necessary; add notes for Linux users where relevant.
GitHub Create Pull Request
Virtual Machines NV series migration guide ...-machines/migration/sizes/nv-series-migration-guide.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates Windows bias by exclusively referencing Windows guest OS support for NVv4 VMs, linking only to Windows-specific driver setup guides and extensions, and omitting Linux migration steps, driver installation instructions, or Linux-specific considerations. Linux tools, patterns, or examples are not mentioned, and Windows is presented as the default or only supported platform for key VM series and migration actions.
Recommendations
  • Add explicit Linux migration instructions, including driver installation and removal steps for supported VM series.
  • Provide links to Linux-specific GPU driver setup guides and extension documentation where available.
  • Clarify OS support for each VM series, including any limitations or future plans for Linux support.
  • Include Linux command-line examples (e.g., Bash, Azure CLI) alongside or before Windows/Powershell examples.
  • Mention Linux tools and patterns for GPU workload management and migration, ensuring parity with Windows guidance.
GitHub Create Pull Request
Virtual Machines Move a maintenance configuration to another Azure region ...tual-machines/move-region-maintenance-configuration.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias by repeatedly referencing PowerShell as a primary tool for creating, assigning, and deleting maintenance configurations, alongside Azure CLI. No Linux-specific shell examples (e.g., Bash) are provided, and PowerShell is mentioned before CLI in each step, suggesting a Windows-first approach. There are no explicit Linux command-line examples or guidance tailored to Linux users.
Recommendations
  • Provide Bash shell examples for each step, especially for creating, assigning, and deleting maintenance configurations using Azure CLI.
  • Mention CLI before PowerShell, or present both options equally, to avoid implying PowerShell is the preferred or default method.
  • Clarify that all CLI commands work natively on Linux and macOS, and provide any necessary notes for Linux users (e.g., environment variable syntax differences).
  • Include explicit instructions or links for Linux users on installing and using Azure CLI.
  • Review linked articles to ensure Linux parity in examples and instructions.
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 page exclusively provides PowerShell-based instructions and examples for Windows environments. There are no references to Linux tools, Bash, or CLI equivalents, and the content is explicitly targeted at Windows users. All sample scripts, next steps, and additional resources focus solely on Windows and PowerShell, omitting Linux parity.
Recommendations
  • Add equivalent Bash or Azure CLI examples for Linux users.
  • Include references to Linux VM documentation and script samples.
  • Provide guidance for performing the same tasks on Linux, including any differences in workflow or tooling.
  • Clearly indicate cross-platform support and limitations, if any.
  • Reorganize content to present both Windows and Linux options in parallel, rather than focusing exclusively on Windows.
GitHub Create Pull Request
Virtual Machines Secure and use policies ...blob/main/articles/virtual-machines/security-policy.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 generally covers both Windows and Linux VMs, but there are several instances of Windows bias. Windows tools (PowerShell) are mentioned before Linux equivalents (CLI), especially in the Key Vault section. Some features, such as Microsoft Antimalware, are described with a Windows focus and lack Linux alternatives or examples. In several places, Windows terminology and tools are introduced first, and Linux examples are sometimes missing or referenced secondarily.
Recommendations
  • Ensure that Linux tools (e.g., Azure CLI) are mentioned alongside or before Windows tools (PowerShell) when describing procedures.
  • Provide explicit Linux examples and command snippets wherever Windows examples are given.
  • Where features are Windows-only (e.g., Microsoft Antimalware), suggest Linux alternatives or clarify Linux security recommendations.
  • Balance references to documentation links so that Linux and Windows guides are equally visible and accessible.
  • Use neutral language when introducing cross-platform features, avoiding Windows-first ordering.
GitHub Create Pull Request
Virtual Machines Set up Azure HPC or AI VMs .../blob/main/articles/virtual-machines/set-up-hpc-vms.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates mild Windows bias. While it references both Linux and Windows quickstarts and driver installation guides, Windows examples and links are often listed before Linux equivalents (e.g., in the driver installation section). There is a lack of Linux-specific examples for AMD GPU drivers, and some instructions (such as SSH key generation and download) use patterns more common in Windows-centric workflows. Additionally, the page references connecting via SSH from Windows, but does not mention Linux-native tools or workflows in detail.
Recommendations
  • Ensure Linux and Windows examples are presented in parallel, with equal detail and prominence.
  • Add Linux-specific instructions for AMD GPU driver installation, matching the detail provided for Windows.
  • When listing links or instructions, alternate the order (Linux first in some sections, Windows first in others) or present both together.
  • Include Linux-native tooling and workflows (e.g., mention using ssh-keygen on Linux, or connecting via terminal) where relevant.
  • Review all examples and ensure that Linux users have clear, step-by-step guidance matching Windows parity.
GitHub Create Pull Request
Virtual Machines Faldsv7 size series ...ual-machines/sizes/compute-optimized/faldsv7-series.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits mild Windows bias. In the 'Feature support' section, nested virtualization is linked only to the Windows/Hyper-V documentation, with no mention of Linux/KVM equivalents. In the 'Network' section, bandwidth/throughput testing references NTTTCP, a Microsoft/Windows-centric tool, without mentioning Linux alternatives. There are no command-line examples, but where tooling or guides are referenced, Windows is prioritized or Linux is omitted.
Recommendations
  • Add references to Linux/KVM nested virtualization documentation alongside the Windows/Hyper-V link.
  • Mention Linux network testing tools (e.g., iperf, netperf) in addition to NTTTCP for bandwidth/throughput testing.
  • Where features/tools are OS-specific, clarify applicability for both Windows and Linux, and provide parity in documentation links.
  • Consider including example commands or usage patterns for both Windows (PowerShell/NTTTCP) and Linux (bash/iperf) where relevant.
GitHub Create Pull Request
Virtual Machines Ddsv6 size series ...virtual-machines/sizes/general-purpose/ddsv6-series.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits mild Windows bias. Windows-specific features and tools (such as Hyper-V nested virtualization and NTTTCP for bandwidth testing) are mentioned or linked before or exclusively, with Linux equivalents either omitted or referenced only as 'Linux or Windows' without detail. There are no Linux-specific examples, tools, or optimization guidance, and the only Linux mention is in the context of unsupported disk encryption.
Recommendations
  • Include Linux-specific examples and tools for performance testing (e.g., mention 'iperf' or 'fio' alongside NTTTCP).
  • Provide links to Linux nested virtualization documentation (e.g., KVM or QEMU) in addition to Hyper-V.
  • Add guidance or optimization tips for Linux VMs, similar to those provided for Windows.
  • Ensure parity in feature support tables by listing both Linux and Windows features, and clarify any differences.
  • Where features/tools are Windows-specific, explicitly state Linux alternatives or note their absence.
GitHub Create Pull Request
Virtual Machines Eadsv7 size series ...rtual-machines/sizes/memory-optimized/eadsv7-series.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page shows mild Windows bias. References to Windows technologies (e.g., Hyper-V nested virtualization, NTTTCP for bandwidth testing) are present, and Windows is mentioned before Linux in some feature lists and optimization notes. There are no explicit Linux command examples or Linux-specific tools highlighted, and some features/tools (like NTTTCP) are Windows-centric without Linux alternatives or parity guidance.
Recommendations
  • Add Linux-specific examples and tools where Windows tools are mentioned (e.g., include Linux equivalents for NTTTCP, such as iperf or netperf).
  • When listing features or optimization guidance, alternate or balance the order of Windows and Linux mentions, or group them together to avoid Windows-first impression.
  • Provide links to Linux documentation and troubleshooting guides alongside Windows ones, especially for features like nested virtualization or disk encryption.
  • Explicitly note Linux support and best practices for performance optimization, not just Windows.
  • Ensure that any referenced tools or patterns (such as NVMe support, disk encryption, network testing) include Linux usage instructions or alternatives.
GitHub Create Pull Request
Virtual Machines Eadsv6 size series ...rtual-machines/sizes/memory-optimized/eadsv6-series.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates mild Windows bias. It references Windows-specific technologies (such as Hyper-V nested virtualization and NTTTCP for bandwidth testing) and links to Windows documentation before or instead of Linux equivalents. There are no Linux-specific examples or tools mentioned for virtualization or network testing, and some features are described with a Windows-first perspective (e.g., nested virtualization). Linux support is mentioned only in the context of restrictions or lack of support (e.g., Azure Disk Encryption for Linux VMs: Not Supported), rather than providing positive Linux guidance or parity.
Recommendations
  • Include Linux-specific examples and tools for network testing (e.g., iperf, netperf) alongside NTTTCP.
  • Reference Linux virtualization documentation (e.g., KVM nested virtualization) in addition to or before Windows Hyper-V.
  • Provide positive Linux guidance and feature parity notes, not just restrictions.
  • Ensure that feature support tables and resource links mention both Windows and Linux options equally.
  • Add links to Linux-focused documentation for VM optimization and performance testing.
GitHub Create Pull Request
Virtual Machines Epdsv6 size series ...rtual-machines/sizes/memory-optimized/epdsv6-series.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates mild Windows bias. References to Windows-specific features (e.g., nested virtualization linking to Hyper-V on Windows) and tools (NTTTCP for bandwidth testing, which is a Windows tool) are present. Windows features are mentioned before Linux equivalents in some cases, and there are no explicit Linux command examples or Linux-specific tooling mentioned. While the page states applicability to both Linux and Windows VMs, practical guidance and links favor Windows environments.
Recommendations
  • Include Linux-specific examples and links where Windows tools are referenced (e.g., mention Linux alternatives to NTTTCP such as iperf or netperf for bandwidth testing).
  • When referencing virtualization features, provide parity by linking to Linux nested virtualization documentation or clarifying Linux support status.
  • Ensure that feature support tables and notes mention both Linux and Windows equivalently, and avoid listing Windows features or tools first unless there is a technical reason.
  • Add Linux command-line examples (e.g., using Azure CLI or Linux disk/network benchmarking tools) alongside any Windows/PowerShell examples.
  • Review linked resources to ensure Linux documentation is referenced where available, not just Windows-centric guides.
GitHub Create Pull Request
Virtual Machines Ev5 size series .../virtual-machines/sizes/memory-optimized/ev5-series.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates mild Windows bias. It references Windows-specific technologies (e.g., nested virtualization links to Hyper-V on Windows), and in the networking section, bandwidth/throughput testing is described using NTTTCP, a tool primarily associated with Windows. There are no explicit Linux or cross-platform command examples, and Windows tools/patterns are mentioned before or instead of Linux equivalents. No Linux-specific guidance or parity is provided for features like nested virtualization or performance testing.
Recommendations
  • Include Linux equivalents or cross-platform alternatives for referenced tools (e.g., mention 'iperf' or 'netperf' for bandwidth testing alongside NTTTCP).
  • Provide links to Linux documentation for nested virtualization (e.g., KVM or other supported hypervisors on Azure).
  • Add explicit Linux command-line examples or references where applicable, especially in sections discussing optimization, performance testing, or feature support.
  • Ensure that documentation for features (such as network optimization or disk performance) includes both Windows and Linux guidance, or clarifies platform-specific differences.
  • Review all external links to ensure Linux parity and add Linux-focused resources where missing.
GitHub Create Pull Request
Virtual Machines Use Azure Spot Virtual Machines ...e-docs/blob/main/articles/virtual-machines/spot-vms.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation generally maintains cross-platform language, but there is evidence of Windows bias. PowerShell is mentioned explicitly in the 'Next steps' section, with a direct link to Windows/PowerShell instructions, while Linux CLI and ARM template links are grouped separately. The order of presentation in 'Next steps' places CLI (Linux), portal, ARM template (Linux), and then PowerShell (Windows), which is more balanced, but the explicit mention of PowerShell and the existence of a dedicated Windows/PowerShell page, without a similar dedicated Bash or Linux shell page, suggests a slight bias. There are no explicit Linux shell command examples or screenshots, and some references (such as scheduled events) link to Linux documentation but do not provide in-page Linux-specific examples. No Windows-only tools are promoted, but Linux parity in examples and tooling is not fully achieved.
Recommendations
  • Add explicit Linux shell (Bash) command examples for common Spot VM operations, similar to the PowerShell examples.
  • Provide dedicated Linux/Bash documentation pages, analogous to the Windows/PowerShell page.
  • Include screenshots or walkthroughs for Linux users in the portal and CLI sections.
  • Ensure that all references to tooling (CLI, ARM, PowerShell) are presented with equal prominence and detail.
  • Where possible, provide side-by-side examples for both Windows (PowerShell) and Linux (Bash/CLI) in relevant sections.
GitHub Create Pull Request
Virtual Machines Create SSH keys in the Azure portal ...blob/main/articles/virtual-machines/ssh-keys-portal.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits Windows bias by providing only a PowerShell example for connecting to the VM, without any Linux or macOS terminal equivalents. The instructions for using SSH keys locally assume a Windows environment, and the only explicit command-line example is shown in a PowerShell context. There are no Linux shell (bash) or macOS Terminal instructions, nor is there mention of Linux-specific SSH client usage or file permissions (e.g., chmod). References to further documentation also point to 'ssh-from-windows.md', reinforcing a Windows-first perspective.
Recommendations
  • Add Linux and macOS terminal examples for connecting to the VM using SSH, such as using bash/zsh.
  • Include notes on setting appropriate file permissions for the private key (e.g., 'chmod 600 mySSHKey.pem') on Linux/macOS.
  • Provide parity in instructions for moving and storing the SSH key on Linux/macOS systems.
  • Reference documentation that covers both Windows and Linux workflows, or split links to OS-specific guides.
  • Avoid presenting Windows/Powershell examples exclusively or before Linux equivalents; instead, show both side-by-side or in parallel sections.
GitHub Create Pull Request
Virtual Machines Enable Trusted launch on existing Uniform scale set ...icles/virtual-machines/trusted-launch-existing-vmss.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 Windows bias in several areas: Windows OS images are used as the primary example in ARM templates, CLI, and PowerShell sections; Linux-specific examples and instructions are missing or only referenced in passing (e.g., extension publisher names); PowerShell is given equal or greater prominence compared to CLI, and Windows tooling and patterns (such as WindowsServer images and PowerShell commands) are presented before or instead of Linux equivalents.
Recommendations
  • Provide explicit Linux examples alongside Windows examples in all code blocks (ARM template, CLI, PowerShell), including Linux image references and SKU values.
  • Add instructions and sample commands for enabling Trusted launch on Linux-based scale sets, including any Linux-specific considerations (e.g., custom kernels, unsigned drivers).
  • In ARM template and CLI sections, alternate or parallelize Windows and Linux examples, rather than defaulting to Windows first.
  • Clarify extension publisher usage by showing full Linux extension configuration, not just a table.
  • Ensure parity in troubleshooting, validation, and rollback steps for Linux scale sets.
  • Review screenshots and portal instructions to confirm they are applicable to both Windows and Linux, or provide Linux-specific visuals where needed.
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
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a bias towards Windows by prioritizing PowerShell in both the management options list and the 'Next steps' section. PowerShell, a Windows-centric tool, is mentioned first, and the only direct example link provided is for PowerShell. There are no explicit Linux-specific examples or references to Bash or Linux-native tools, and Azure CLI (which is cross-platform and commonly used on Linux) is listed after PowerShell and not highlighted in the 'Next steps'.
Recommendations
  • Provide equal prominence to Azure CLI examples, especially in the 'Next steps' section, as CLI is widely used on Linux.
  • Include explicit Bash/Linux shell examples or links to Linux-specific documentation where relevant.
  • Alternate the order of management options or clarify that both PowerShell and CLI are supported equally across platforms.
  • Add a note or section highlighting cross-platform compatibility and usage scenarios for Linux administrators.
GitHub Create Pull Request
Azure Impact Reporting Azure Impact Reporting: Connectors Troubleshooting Guide ...e-impact-reporting/connectors-troubleshooting-guide.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides troubleshooting steps for both Bash and PowerShell users, but PowerShell examples and instructions are consistently presented alongside or immediately after Bash, sometimes with additional detail for PowerShell (e.g., file locking). There is a notable emphasis on Azure PowerShell module management and error handling, which are Windows-centric patterns. No Linux-specific troubleshooting (e.g., shell environment issues, file permissions beyond chmod) or tool alternatives are mentioned. The documentation assumes parity between Bash and PowerShell but leans toward Windows/PowerShell usage patterns.
Recommendations
  • Ensure Linux/Bash examples are presented first or given equal prominence.
  • Add Linux-specific troubleshooting steps, such as handling file permissions, environment variables, and common shell errors.
  • Include guidance for updating Azure CLI on Linux (e.g., apt, yum, zypper commands).
  • Mention cross-platform considerations, such as differences in file path formats and script execution environments.
  • Clarify when instructions are platform-specific and provide alternatives for macOS and Linux users.
  • Avoid assuming PowerShell is available on all platforms; note installation steps for PowerShell Core on Linux/macOS if relevant.
GitHub Create Pull Request
Container Instances Quickstart - Create a container instance - Azure Resource Manager template ...r-instances/container-instances-quickstart-template.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation primarily describes deployment using the Azure Portal and only briefly mentions alternative methods (Azure PowerShell, Azure CLI, REST API) after the main instructions. There are no explicit command-line examples for either Windows (PowerShell) or Linux (Bash), but the mention of PowerShell before CLI and REST API, as well as the lack of Linux-specific guidance or screenshots, suggests a subtle Windows-first bias. There are no examples or instructions tailored for Linux users, such as Bash commands or terminal screenshots.
Recommendations
  • Provide explicit Azure CLI (Bash) examples for deploying the ARM template, alongside or before PowerShell examples.
  • Include instructions and screenshots for using the Azure CLI on Linux/macOS, not just the Azure Portal.
  • When mentioning alternative deployment methods, list Azure CLI before PowerShell to avoid Windows-first ordering.
  • Add a section or callout specifically for Linux users, highlighting cross-platform tools and commands.
  • Ensure that all steps (including log viewing and resource cleanup) have CLI/Bash equivalents documented.
GitHub Create Pull Request
Service Fabric Common FabricClient exceptions thrown ...service-fabric/service-fabric-errors-and-exceptions.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 .NET and Windows-centric exception types and error codes, referencing Windows-specific concepts such as X509 certificate stores and .NET exception classes. There are no examples, notes, or guidance for Linux environments, nor any mention of Linux-specific error handling, certificate management, or cross-platform considerations.
Recommendations
  • Include examples or notes on how exceptions and error codes manifest when using FabricClient APIs on Linux environments.
  • Document Linux-specific certificate store locations and management patterns, such as differences in X509 store handling.
  • Add guidance for troubleshooting and handling exceptions in cross-platform scenarios, including any differences in error codes or behaviors.
  • Reference equivalent Linux tools or commands where applicable, and clarify any platform-specific limitations or differences.
GitHub Create Pull Request
Virtual Machines Ev3-series and Esv3-series ...blob/main/articles/virtual-machines/ev3-esv3-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 exhibits mild Windows bias. While it states applicability to both Linux and Windows VMs, the only external tool or feature referenced by OS is 'Nested Virtualization', which links to a Windows/Hyper-V specific guide. No Linux equivalents or examples are provided for nested virtualization or other features. Windows tools and patterns are mentioned exclusively or first where OS-specific features are discussed.
Recommendations
  • Provide Linux-specific guidance or examples for features like Nested Virtualization (e.g., KVM/QEMU).
  • Where OS-specific documentation is referenced, include links to both Windows and Linux guides.
  • Add explicit Linux usage notes or examples for features that differ between OSes.
  • Review all feature links to ensure Linux parity and avoid Windows-first presentation.
GitHub Create Pull Request
Virtual Machines Azure Disk Encryption for Linux ...es/virtual-machines/extensions/azure-disk-enc-linux.md
Medium 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 about checking encryption progress, the PowerShell cmdlet (Get-AzVMDiskEncryptionStatus) is mentioned first, with the Azure CLI command referenced second. This ordering and inclusion of PowerShell (a Windows-centric tool) in a Linux-focused guide introduces a subtle Windows-first and Windows-tools bias.
Recommendations
  • List the Azure CLI command before the PowerShell cmdlet when describing how to check encryption status, as CLI is more commonly used on Linux.
  • Provide explicit Linux shell command examples (e.g., az vm encryption show) with sample output to improve clarity for Linux users.
  • Consider omitting PowerShell references or moving them to a separate section for cross-platform users, focusing the main instructions on Linux-native tools.
  • Ensure all troubleshooting and operational examples use Linux-native commands and patterns unless the context specifically requires cross-platform coverage.
GitHub Create Pull Request
Container Instances Azure Resource Manager template samples .../container-instances/container-instances-samples-rm.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation shows mild Windows bias by listing Windows-specific templates (such as MS NAV with SQL Server and IIS) before Linux equivalents in the 'Applications' section, and by referencing Azure PowerShell as a primary deployment option alongside Azure CLI, without clarifying cross-platform parity or providing Linux-specific command examples. There is also a focus on Windows-based workloads (e.g., IIS, SQL Server) in the sample templates, while Linux application examples are less prominent in the 'Applications' section.
Recommendations
  • Add more Linux-focused application templates to the 'Applications' section, such as popular open-source stacks (e.g., LAMP, MEAN).
  • Ensure Linux and Windows examples are presented with equal prominence, alternating their order or grouping by OS.
  • Clarify in the 'Deployment' section that Azure CLI is cross-platform and provide explicit Bash or shell command examples for Linux users.
  • Include references to Linux-native tools (e.g., Bash scripts) where relevant, and ensure that PowerShell is not presented as the default or primary option for all users.
  • Consider adding a table or section that clearly distinguishes which templates are for Windows, Linux, or both, to help users quickly find relevant examples.
GitHub Create Pull Request
Container Instances Configure role permissions for standby pools in Azure Container Instances ...container-instances-standby-pool-configure-permissions.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation consistently presents Azure Portal (GUI) instructions for role assignment and troubleshooting, with no mention of Linux-specific tools or CLI commands. Where SDKs are referenced, PowerShell is mentioned before CLI, and there are no explicit Bash, Azure CLI, or cross-platform command-line examples. This may disadvantage Linux users or those preferring command-line automation.
Recommendations
  • Add Azure CLI (az role assignment) examples for assigning roles, alongside or before PowerShell references.
  • Include Bash/Azure CLI commands for troubleshooting steps, such as querying Log Analytics (e.g., using az monitor log-analytics query).
  • When referencing SDKs, list Azure CLI and REST API before or alongside PowerShell to avoid Windows-first bias.
  • Explicitly state that all steps can be performed on Linux, macOS, or Windows, and provide links to cross-platform tooling.
  • Provide sample scripts or command snippets for common Linux shells (Bash, zsh) where appropriate.
GitHub Create Pull Request
Container Instances Azure Container Instances support and help options ...ontainer-instances/container-instances-support-help.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page lists Azure PowerShell as the first library in the GitHub issues table, which may suggest a Windows-centric approach. PowerShell is traditionally associated with Windows environments, and its prominent placement could indicate a subtle bias. However, the page also lists cross-platform tools such as Azure CLI, Terraform, Ansible, and SDKs for multiple languages, providing some balance. There are no explicit examples or troubleshooting steps that favor Windows or PowerShell, but the ordering and inclusion of PowerShell as the primary library may reflect a Windows-first mindset.
Recommendations
  • Rotate or randomize the order of libraries/tools listed to avoid implying priority, or list cross-platform tools (e.g., Azure CLI) before Windows-centric ones (e.g., PowerShell).
  • Explicitly mention that Azure CLI and other tools are cross-platform and suitable for Linux, macOS, and Windows.
  • Add troubleshooting and support examples for both Windows (PowerShell) and Linux (CLI, Bash) environments to ensure parity.
  • Include links to Linux-specific documentation or community forums where Linux users can get help.
  • Clarify that PowerShell is available cross-platform, but also highlight native Linux workflows.
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 as the operating system, with no mention of Linux-based deployment options. All instructions, screenshots, and examples assume a Windows environment, and there are no Linux-specific notes, alternatives, or parity guidance. This presents a strong Windows bias and may exclude or confuse users seeking to deploy Service Fabric clusters on Linux.
Recommendations
  • Include instructions and screenshots for deploying Service Fabric clusters using Linux-based virtual machines (e.g., Ubuntu or CentOS).
  • Add a section or notes highlighting differences between Windows and Linux deployments, including certificate handling and cluster management.
  • Provide parity in examples, such as how to import certificates on Linux systems and access Service Fabric Explorer from Linux clients.
  • Explicitly mention Linux support in the prerequisites and operating system selection steps, and offer guidance for users who prefer or require Linux environments.
GitHub Create Pull Request
Service Fabric Service Fabric cluster security: client roles ...ervice-fabric/service-fabric-cluster-security-roles.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation describes Service Fabric client roles and access control but does not provide any platform-specific examples or tooling references. However, the only mention of cluster creation refers to the Azure portal and cluster manifest file, which are typically associated with Windows-centric workflows. There are no Linux-specific instructions, examples, or references to Linux tools or patterns, and no mention of cross-platform command-line usage (e.g., Bash, CLI, etc.).
Recommendations
  • Include explicit examples for both Windows (PowerShell) and Linux (Bash/CLI) when describing how to configure client roles and permissions.
  • Reference cross-platform tools such as Azure CLI and provide sample commands for both Windows and Linux environments.
  • Clarify whether the cluster manifest file and related configuration steps are identical on Linux clusters, and provide guidance for Linux users if there are differences.
  • Add links or sections that address Linux-specific workflows, such as using Service Fabric on Linux, and how access control is managed in those scenarios.
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 discusses Service Fabric clusters on both Windows Server and Linux, but it highlights that standalone clusters are not available on Linux and does not provide Linux-specific examples or operational guidance. Windows is implicitly prioritized by mentioning standalone clusters in the context of Windows only, and there is a lack of parity in examples or tooling for Linux users.
Recommendations
  • Explicitly state the limitations and alternatives for Linux users regarding standalone clusters.
  • Provide Linux-specific operational guidance, examples, and tooling references where possible.
  • Ensure that any feature comparison or instructions are presented in a balanced manner, with Linux and Windows options given equal prominence.
  • Link to Linux-focused documentation or migration guides for users interested in Service Fabric on Linux.
  • Clarify any differences in management, scaling, and diagnostics for Linux clusters, and offer best practices for Linux environments.
GitHub Create Pull Request
Service Fabric Query for cluster events using the EventStore APIs ...-fabric/service-fabric-diagnostics-eventstore-query.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 a Windows bias by explicitly stating that the EventStore APIs are GA only for Windows clusters running on Azure, with no mention of Linux support or examples. All code and usage examples assume Windows clusters, and there are no Linux-specific instructions, caveats, or parity notes. There are no references to Linux tools, shell commands, or patterns, and the documentation does not clarify the status or usage for Service Fabric clusters running on Linux.
Recommendations
  • Clearly state the current support status for Linux clusters, including any limitations or roadmap for EventStore APIs on Linux.
  • If Linux support exists or is planned, provide equivalent Linux usage examples, including REST queries and client library usage.
  • Include notes or guidance for Linux users, such as differences in endpoint URLs, authentication, or setup steps.
  • Add troubleshooting or caveats for Linux clusters, if there are known issues or differences.
  • Ensure that future updates to the documentation maintain parity between Windows and Linux, with examples and instructions for both platforms.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Event Store ...ervice-fabric/service-fabric-diagnostics-eventstore.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 a Windows bias by repeatedly stating that EventStore APIs and UX are only available for Windows clusters running on Azure, with no Linux support yet. All instructions, examples, and enablement steps are written with the assumption of a Windows cluster, and there are no Linux-specific examples, guidance, or parity notes beyond a brief mention that Linux support is planned for the future.
Recommendations
  • Explicitly state the current lack of Linux support at the top of the documentation and provide a timeline or roadmap for Linux parity if possible.
  • Add a dedicated section outlining the differences between Windows and Linux cluster support for EventStore, including any workarounds or alternative monitoring options for Linux users.
  • Once Linux support is available, update all examples and instructions to include both Windows and Linux workflows, configuration snippets, and troubleshooting steps.
  • Provide links to Linux-compatible monitoring and diagnostics tools as alternatives until EventStore is available for Linux clusters.
  • Regularly update the documentation to reflect progress on Linux support and communicate changes clearly to users.
GitHub Create Pull Request
Virtual Machines Best practices for virtual machine cost optimization ...s/virtual-machines/cost-optimization-best-practices.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page shows mild Windows bias. In the best practices section, recommendations for B-Series VM sizing specify 'at least B2 for Windows machines' but do not mention Linux equivalents or considerations. The cost-saving licensing benefit (Azure Hybrid Benefit) is discussed only for Windows Server, with no mention of Linux licensing or cost-saving features. Examples and recommendations are generally Windows-centric, with Linux mentioned only in pricing links and a next-steps link to Linux VM creation, but not in the main body of cost optimization advice.
Recommendations
  • Include equivalent recommendations for Linux VMs, such as optimal B-Series sizing for Linux workloads.
  • Discuss any Linux-specific cost optimization features, such as reserved instance savings, open-source licensing advantages, or relevant Azure Hybrid Benefit for Linux (if applicable).
  • When mentioning licensing benefits, clarify differences for Linux and Windows, and link to Linux cost-saving documentation where appropriate.
  • Ensure examples and advice are balanced between Windows and Linux, especially in sections on automation, disk selection, and policy enforcement.
GitHub Create Pull Request
Virtual Machines Increase performance of Premium SSDs and Standard SSD/HDDs .../articles/virtual-machines/disks-enable-performance.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, but the PowerShell section is given equal prominence and detail, which can be interpreted as Windows bias. There are no explicit Linux shell (bash) or platform-specific examples, but the CLI examples use bash syntax, which is cross-platform. However, the documentation does not mention Linux-specific considerations, nor does it provide parity for Linux-native scripting or tools. The PowerShell examples may be less relevant for Linux users, and the documentation does not clarify platform differences or recommend best practices for Linux environments.
Recommendations
  • Add explicit bash examples and clarify that Azure CLI commands work natively on Linux, macOS, and Windows.
  • Include notes on platform compatibility, such as differences in environment variable syntax (e.g., export vs. $env:), file paths, and shell behaviors.
  • If PowerShell is mentioned, clarify that PowerShell Core is available on Linux and macOS, and provide guidance for Linux users who may prefer bash.
  • Add troubleshooting or tips specific to Linux environments (e.g., permissions, common errors, package installation).
  • Ensure that Linux users are not required to use Windows-centric tools or patterns, and highlight cross-platform approaches where possible.
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 page describes using Azure Storage Explorer, a cross-platform GUI tool, to manage Azure managed disks. While the main instructions are platform-neutral, the 'Next steps' section exclusively links to Windows VM scenarios, such as creating a VM from a VHD and attaching a managed disk to a Windows VM, with no equivalent Linux VM guidance. There are no Linux-specific examples or follow-up links, which may lead Linux users to feel underserved.
Recommendations
  • Add 'Next steps' links for Linux VM scenarios, such as creating a VM from a VHD for Linux and attaching a managed disk to a Linux VM.
  • Ensure parity in example coverage by including Linux-specific instructions or references where relevant.
  • Review other related documentation to ensure both Windows and Linux users have clear, direct guidance for common disk management tasks.
GitHub Create Pull Request
Virtual Machines Chef extension for Azure VMs ...blob/main/articles/virtual-machines/extensions/chef.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation generally maintains parity between Linux and Windows, but there is subtle Windows bias. The extension publisher is named 'Chef.Bootstrap.WindowsAzure', which is Windows-centric. In the extension schema, the Windows type ('ChefClient') is listed before the Linux type ('LinuxChefClient'). The logging paths and troubleshooting sections mention both platforms, but the Windows path is given in Powershell syntax and the Linux path in bash, with no further Linux troubleshooting commands or examples. The Azure CLI deployment example only shows Linux ('LinuxChefClient') and omits a Windows example. The documentation references Windows tools and patterns (e.g., publisher naming, resource types) before Linux equivalents.
Recommendations
  • Provide explicit Windows deployment examples alongside Linux examples in CLI sections.
  • Clarify that the publisher name is historical and applies to both platforms.
  • List Linux and Windows extension types in parallel, or alternate the order to avoid Windows-first bias.
  • Include Linux-specific troubleshooting commands (e.g., 'cat' or 'tail' for log files) as well as Windows equivalents (e.g., 'Get-Content').
  • Ensure that documentation sections do not default to Windows terminology or patterns unless necessary.
GitHub Create Pull Request
Virtual Machines Qualys Cloud Agent Extension for Azure VMs ...ob/main/articles/virtual-machines/extensions/qualys.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page generally presents Windows examples and tools before Linux equivalents, especially in the 'Golden Machine Image' and 'Azure Deployment Policy' sections, where Windows links are listed before Linux links. The 'Deploy Cloud Agent via PowerShell' section emphasizes PowerShell as a cross-platform tool, but PowerShell is natively a Windows-centric technology, and Linux users may prefer bash or shell script examples. There are no explicit Linux tool examples (e.g., bash, cloud-init) provided, and the documentation does not offer Linux-first or Linux-native patterns.
Recommendations
  • Alternate the order of Windows and Linux examples/links to avoid consistently listing Windows first.
  • Provide Linux-native command-line examples (e.g., bash, cloud-init) alongside or instead of PowerShell for Linux deployments.
  • Explicitly mention Linux-specific tools and patterns where relevant, such as using shell scripts or cloud-init for automation.
  • Ensure parity in detail and clarity between Windows and Linux sections, including troubleshooting and advanced configuration guidance.
  • Review and update headings and content to avoid implicit prioritization of Windows tools and workflows.
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 exhibits subtle Windows bias, primarily through the use of Windows-centric links and examples. For instance, the reference to scheduled events points to a Windows-specific documentation page ('../virtual-machines/windows/scheduled-event-service.md'), and activity log instructions default to PowerShell tabs. There are no explicit Linux examples, nor are Linux-specific tools or patterns mentioned, which may leave Linux users without clear guidance.
Recommendations
  • Include parallel Linux documentation links (e.g., '../virtual-machines/linux/scheduled-event-service.md') wherever Windows links are referenced.
  • Provide Linux CLI examples (such as Azure CLI or Bash) alongside PowerShell examples in all code samples and instructions.
  • Mention Linux-specific monitoring considerations or tools if they differ from Windows, ensuring parity in troubleshooting and observability guidance.
  • Review referenced tabs and ensure that Linux/Bash/CLI options are presented before or alongside PowerShell, not exclusively or first.
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
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides a balanced technical overview of HBv3-series VMs, but there is evidence of Windows bias in the 'Recommended OS for Performance' row, which lists Windows Server 2019+ before any Linux recommendation. Additionally, while Linux is referenced (e.g., lstopo output, supported OSes), there are no explicit Linux performance recommendations or examples for Linux-specific tuning, and the only OS recommendation for performance is Windows. The page also includes a note about unsupported Windows versions, but does not provide equivalent Linux caveats or guidance.
Recommendations
  • Add explicit Linux performance recommendations alongside Windows Server 2019+, e.g., 'Recommended OS for Performance: Windows Server 2019+, RHEL 8+, Ubuntu 20.04+'.
  • Provide Linux-specific tuning guidance or references, such as kernel parameters or NUMA optimization tips.
  • Include Linux caveats or notes similar to the Windows Server 2012 R2 support note, e.g., minimum kernel versions for high core counts.
  • Ensure that examples and recommendations are presented in parallel for both Windows and Linux, rather than listing Windows first.
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
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation introduces Windows tooling (DISKSPD) first, with detailed command examples and parameter explanations, before mentioning the Linux equivalent (FIO). The Windows tool is described in greater detail and appears to be the default or primary recommendation, while the Linux tool is introduced later and with less context. There is a clear ordering preference for Windows tools and patterns, and the Windows example is more prominent.
Recommendations
  • Present Linux and Windows benchmarking tools in parallel, giving equal prominence to both.
  • Provide equivalent parameter explanations and example commands for FIO as are given for DISKSPD.
  • Consider starting with a cross-platform introduction, then split into Windows and Linux sections.
  • Include notes on tool availability and installation for both platforms at the start.
  • Ensure images and sample outputs are balanced between Windows and Linux examples.
GitHub Create Pull Request
Virtual Machines What's New in Azure VM Image Builder ...ual-machines/image-builder-api-update-release-notes.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 HTTP, Azure CLI, and Azure PowerShell, with PowerShell (Windows) examples given equal prominence to CLI and HTTP. There is a slight Windows-first bias in the ordering and explicit mention of PowerShell, while Linux-specific tools (such as Bash scripts or shell commands) are not shown in the main example tabs. Additionally, some features and improvements are described with Windows-specific terminology (e.g., PowerShell, Windows Update, Windows restart) before or alongside Linux equivalents, but Linux features are generally present. There are no outright missing Linux examples, but the documentation could do more to highlight Linux parity and provide Linux-first or Linux-specific usage patterns.
Recommendations
  • Add explicit Bash or shell script examples alongside PowerShell in code tabs, especially for Linux users.
  • When listing features or improvements, alternate or balance the order between Windows and Linux terminology, or group them by OS for clarity.
  • Provide Linux-specific troubleshooting examples and error messages where relevant.
  • Ensure that Linux tools and patterns (e.g., cloud-init, shell scripting) are mentioned with equal prominence as Windows tools.
  • Consider adding a section or callout for Linux users summarizing best practices and common patterns for VM Image Builder on Linux.
GitHub Create Pull Request
Virtual Machines Customer intent: As a cloud administrator, I want to understand the limitations and requirements of using customer-managed keys for disk encryption, so that I can ensure compliance and optimize the management of storage solutions in my Azure environment. ...hines-managed-disks-customer-managed-keys-restrictions.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation mentions both Azure CLI and Azure PowerShell as tools for copying managed disks, but it lists the Azure CLI (typically used on Linux/macOS) after referencing the Azure PowerShell module (primarily used on Windows). The example links provided are platform-specific, with the PowerShell (Windows) link appearing to be more prominent. There are no explicit Linux shell or bash examples, and the documentation does not mention Linux-specific tools or workflows beyond the Azure CLI.
Recommendations
  • Present Azure CLI (cross-platform) examples before or alongside PowerShell examples to avoid implying Windows is the primary platform.
  • Include explicit bash or Linux shell command examples where relevant.
  • Ensure documentation links for both Linux and Windows are equally prominent and accessible.
  • Add a note clarifying that Azure CLI is available on all major platforms, and provide guidance for Linux/macOS users.
  • Review other sections for similar patterns and ensure Linux parity throughout.
GitHub Create Pull Request
Virtual Machines DNS Name resolution options for Linux VMs ...blob/main/articles/virtual-machines/linux/azure-dns.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation is focused on Linux VM DNS configuration, but there are subtle signs of Windows bias. Windows retry logic is described first and in more detail than Linux, and Windows-specific tools (PowerShell) are mentioned for determining DNS suffixes, while Linux alternatives are not provided. There are no PowerShell-heavy examples or missing Linux examples, but Windows patterns/tools are referenced before Linux equivalents.
Recommendations
  • When describing DNS client retry logic, present Linux and Windows behaviors with equal detail and consider listing Linux first, given the page's Linux focus.
  • When mentioning tools for querying Azure resources (such as DNS suffixes), provide Linux-native alternatives (e.g., Azure CLI, REST API examples with curl/jq) alongside or before PowerShell.
  • Ensure that any references to Windows tools or patterns are balanced with Linux equivalents, especially in sections targeting Linux administrators.
  • Consider adding explicit Linux command examples for tasks currently only described with PowerShell or Windows-centric tools.
GitHub Create Pull Request
Virtual Machines Azure VM Image Builder networking options ...les/virtual-machines/linux/image-builder-networking.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page presents both Windows and Linux options, but there is a subtle Windows bias. Windows examples and tools (PowerShell) are mentioned before Linux equivalents in several places, and PowerShell is given equal prominence to Azure CLI, even though CLI is more cross-platform. Windows-specific configuration notes (WinRM) are highlighted, while Linux-specific notes are less emphasized.
Recommendations
  • Present Linux and Windows examples in parallel, or alternate which is listed first to avoid implicit prioritization.
  • Where possible, use Azure CLI as the primary example, since it is cross-platform, and mention PowerShell as an alternative for Windows users.
  • Add Linux-specific configuration notes where relevant, to match the detail given for Windows (e.g., SSH configuration).
  • Ensure that all tooling and command examples are available for Linux users, and clearly mark any Windows-only steps.
  • Review the order of example links and checklist items to avoid always listing Windows/PowerShell first.
GitHub Create Pull Request
Virtual Machines Use Azure VM Image Builder for Linux VMs to access an existing Azure virtual network .../articles/virtual-machines/linux/image-builder-vnet.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_reference
Summary
The documentation is focused on Linux VM scenarios and uses Azure CLI and Bash throughout, which are cross-platform and Linux-friendly. However, there are minor references to Windows-specific ports and a link to a Windows-specific managed identity guide. There is also mention of PowerShell in a 'For more information' section, but no PowerShell examples are given, nor is PowerShell prioritized over CLI. No Linux examples are missing, and the workflow is Linux-first.
Recommendations
  • Replace the link to the Windows-specific managed identity guide with a Linux/Azure CLI equivalent, or provide both links for parity.
  • Clarify port usage for Windows and Linux in a way that doesn't prioritize Windows (e.g., list Linux port first, or explain both equally).
  • If mentioning PowerShell as an alternative, provide a Linux equivalent (e.g., Bash or CLI) in parallel, or clarify that CLI is recommended for Linux users.
  • Ensure that all references to Windows tools or patterns are balanced with Linux equivalents, even in 'For more information' sections.
GitHub Create Pull Request
Virtual Machines Deploy a VM or Virtual Machine Scale Set with MSP ...tual-machines/metadata-security-protocol/greenfield.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias by describing the Windows deployment process first and in more detail, while Linux deployment is mentioned only in a warning and not elaborated with examples or step-by-step instructions. There are no Linux-specific configuration examples, and the provided REST API example uses a Windows VM name ('GPAWinVM'), further reinforcing the Windows focus.
Recommendations
  • Add explicit Linux deployment examples, including ARM template and REST API payloads tailored for Linux VMs.
  • Provide step-by-step instructions for the two-step Linux process mentioned in the warning, ensuring parity with the Windows guidance.
  • Use neutral VM naming conventions in examples (e.g., 'GPA-VM') instead of Windows-specific names.
  • Include validation steps specific to Linux environments, if they differ from Windows.
  • Mention Linux tools or commands where relevant, and ensure that any Windows-specific tools or patterns are matched with Linux equivalents.
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 page exhibits Windows bias by listing Windows operating systems before Linux equivalents in the compatibility section and providing a warning that describes a simpler, single-step process for enabling GuestProxyAgent (GPA) on Windows, while Linux requires a more complex, two-step process. No Linux-specific examples or guidance are provided to help Linux users navigate the additional steps.
Recommendations
  • Provide step-by-step instructions or examples for enabling GPA on Linux, including any required commands or configuration files.
  • List supported operating systems in a neutral or alphabetical order to avoid prioritizing Windows.
  • Include troubleshooting tips or automation guidance for Linux users to streamline the GPA setup process.
  • Explicitly mention any Linux tools or patterns (e.g., systemd, shell scripts) that can be used to configure GPA, similar to ARM template usage on Windows.
GitHub Create Pull Request
Virtual Machines Isolated Image Builds for Azure VM Image Builder ...chines/security-isolated-image-builds-image-builder.md
Medium 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. While the content is generally platform-neutral, the only explicit command-line example for registering the Microsoft.ContainerInstance provider is given in both Azure CLI and PowerShell, with PowerShell (a Windows-centric tool) mentioned second but still present. There are no Linux shell (bash) equivalents provided, and no Linux-specific tools or examples are referenced. The troubleshooting and template references are linked under 'linux/', but the main body does not provide parity in command-line examples or mention Linux-first workflows.
Recommendations
  • Add bash/Azure CLI examples alongside PowerShell for all command-line instructions, especially for provider registration.
  • Explicitly mention Linux shell usage where appropriate, and provide examples for both Windows and Linux environments.
  • Ensure that references to troubleshooting and template guides clarify platform applicability (e.g., if a guide is Linux-specific, note Windows equivalents or parity).
  • Review all command-line and tooling references to ensure Linux users are not required to use Windows-centric tools like PowerShell.
GitHub Create Pull Request
Virtual Machines Set up InfiniBand on HPC VMs - Azure Virtual Machines | Microsoft Docs ...lob/main/articles/virtual-machines/setup-infiniband.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation generally maintains OS parity, mentioning both Linux and Windows support for InfiniBand on Azure HPC VMs. However, there is a subtle Windows bias: Microsoft HPC Pack (a Windows-centric tool) is highlighted as a cluster option, and its usage is described before Linux alternatives. The reference to MS-MPI and HPC Pack, which are traditionally Windows tools, is more prominent than Linux-native cluster management or MPI solutions. There are no explicit Linux command examples, and the documentation does not provide Linux-specific configuration steps or tools, whereas Windows tools are named and linked.
Recommendations
  • Add explicit Linux cluster management options (e.g., Slurm, OpenMPI, Warewulf) alongside or before Microsoft HPC Pack.
  • Provide Linux-specific configuration and deployment examples, including command-line instructions for popular distributions.
  • Balance tool recommendations by mentioning Linux-native MPI stacks and cluster orchestration tools with equal detail and prominence.
  • Include links to Linux documentation and community resources for InfiniBand and HPC setup.
  • Ensure that examples and guidance are presented in a way that does not assume Windows-first workflows.
GitHub Create Pull Request
Virtual Machines Dadsv7 size series ...irtual-machines/sizes/general-purpose/dadsv7-series.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page shows mild Windows bias. In the 'Feature support' section, nested virtualization is linked to a Windows-specific Hyper-V guide, with no mention of Linux alternatives (e.g., KVM). In the networking section, bandwidth/throughput testing references NTTTCP, a Microsoft/Windows-centric tool, without mentioning Linux-native equivalents. In both cases, Windows tools and documentation are referenced exclusively or before Linux equivalents.
Recommendations
  • For nested virtualization, add links or notes about Linux support (e.g., KVM on Ubuntu) and provide relevant documentation.
  • In the networking section, mention Linux-native bandwidth testing tools (e.g., iperf, netperf) alongside NTTTCP, and provide links to their usage in Azure.
  • Review all feature support and tooling references to ensure Linux parity, adding Linux-specific examples and documentation where appropriate.
  • Where possible, avoid referencing only Windows documentation or tools; always include Linux equivalents or clarify OS-specific limitations.
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 page shows mild Windows bias. The only tool mentioned for bandwidth/throughput testing is NTTTCP, which is a Microsoft-developed tool primarily associated with Windows. The link for nested virtualization support points to a Windows-specific guide. In the network section, optimization guidance refers to both Linux and Windows, but the only explicit test tool mentioned is Windows-centric. No Linux-specific tools (e.g., iperf, fio) or Linux documentation links are provided, and Windows tools/guides are referenced before any Linux equivalents.
Recommendations
  • Include Linux-specific tools and examples for bandwidth/throughput testing, such as iperf or fio.
  • Provide links to Linux documentation for nested virtualization and other features where Windows guides are referenced.
  • When listing tools or guides, mention both Windows and Linux options, or present them in parallel rather than Windows-first.
  • Add explicit Linux usage notes or examples where relevant, especially in performance optimization and feature support sections.
GitHub Create Pull Request
Virtual Machines NC_RTXPRO6000BSE_v6 size series ...s/sizes/gpu-accelerated/nc-rtxpro6000-bse-v6-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 exhibits mild Windows bias. It references Windows-specific technologies (e.g., Hyper-V nested virtualization) and Windows tools (NTTTCP for bandwidth testing) without mentioning Linux equivalents or alternatives. In the feature support section, the link for nested virtualization points only to the Windows/Hyper-V guide, and in networking, NTTTCP is referenced for both Linux and Windows but is a Windows-origin tool. There are no command-line examples, but where tooling is mentioned, Windows is prioritized or Linux is omitted.
Recommendations
  • For nested virtualization, add or link to Linux/KVM documentation or explicitly state Linux support status.
  • When referencing bandwidth testing tools, mention Linux-native options (e.g., iperf3) alongside NTTTCP, and provide links to usage guides for both platforms.
  • Where features differ between Windows and Linux (e.g., disk encryption), clarify parity and link to both sets of restrictions.
  • Review all referenced guides and ensure Linux-specific instructions and examples are included or linked, especially for performance optimization and troubleshooting.
GitHub Create Pull Request
Virtual Machines M size series ...es/virtual-machines/sizes/memory-optimized/m-series.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page demonstrates mild Windows bias. In the 'VM Basics resources' section, Windows Server is listed first among supported guest OS versions for large vCPU counts, ahead of Linux distributions. In the 'Feature support' section, the link for Nested Virtualization points specifically to Hyper-V on Windows, with no mention of KVM or other Linux virtualization technologies. In the networking section, the bandwidth/throughput testing tool referenced (NTTTCP) is a Windows-centric tool, with no mention of Linux alternatives like iperf or netperf.
Recommendations
  • List supported Linux distributions before or alongside Windows Server in guest OS requirements to avoid Windows-first ordering.
  • When referencing virtualization features, include Linux equivalents (e.g., KVM nested virtualization) and link to relevant documentation.
  • In networking sections, mention and link to Linux-native bandwidth testing tools (such as iperf or netperf) alongside NTTTCP.
  • Review all feature support and tooling references to ensure Linux parity and avoid exclusive focus on Windows technologies.
GitHub Create Pull Request
Virtual Machines Mdsv3 Very High Memory size series ...al-machines/sizes/memory-optimized/mdsv3-vhm-series.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page exhibits a mild Windows bias. In the list of supported OS images, Windows Server is mentioned first, ahead of Linux distributions. The only external tool referenced for bandwidth/throughput testing is NTTTCP, which is a Microsoft-developed tool primarily for Windows. No Linux-specific tools or examples are provided, and there are no command-line examples (PowerShell, Bash, etc.) for either platform. However, Linux compatibility is clearly stated for several distributions.
Recommendations
  • List supported Linux images before or alongside Windows images, or alphabetically, to avoid implicit prioritization.
  • Mention Linux equivalents for network testing tools, such as iperf or netperf, alongside NTTTCP.
  • Provide example commands or usage patterns for both Windows (PowerShell) and Linux (Bash/CLI) where relevant, such as for checking quotas, optimizing performance, or testing network throughput.
  • Ensure that any references to external documentation or guides include both Windows and Linux procedures.
GitHub Create Pull Request
Virtual Machines Understand VM reboots ...ain/articles/virtual-machines/understand-vm-reboots.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 addresses both Linux and Windows VMs, but there is subtle bias in the ordering and example parity. In the 'Reduce downtime' section, scheduled events for Linux are mentioned after Windows, and there are no concrete examples or commands for either OS. The page does not provide OS-specific troubleshooting steps or tools, and does not mention Linux-specific patterns or utilities (e.g., systemd, journalctl) that administrators might use to investigate reboots, nor does it reference Windows tools (e.g., Event Viewer, PowerShell), but the ordering and lack of Linux-specific guidance suggests a slight Windows-first bias.
Recommendations
  • Ensure Linux and Windows examples are presented with equal prominence and detail.
  • Provide concrete troubleshooting steps or commands for both Linux (e.g., checking /var/log/syslog, using journalctl) and Windows (e.g., Event Viewer, PowerShell commands) when discussing VM reboots.
  • Alternate the order of Linux and Windows references, or present them side-by-side, to avoid implicit prioritization.
  • Include links to OS-specific documentation for investigating and responding to reboots.
GitHub Create Pull Request
Virtual Machines List, update, and delete resources ...in/articles/virtual-machines/update-image-resources.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for managing Azure Compute Gallery resources. However, PowerShell examples are given equal prominence to CLI, and PowerShell is a Windows-centric tool. There are no Linux shell-specific examples (e.g., bash scripting, use of Linux tools), nor is there mention of Linux-specific patterns or considerations. The CLI examples are cross-platform, but the presence and parity of PowerShell examples may signal a Windows bias, especially since PowerShell is traditionally associated with Windows environments.
Recommendations
  • Clarify that Azure CLI commands are cross-platform and can be run on Linux, macOS, and Windows.
  • Add explicit bash shell examples where scripting or environment variables are used, to demonstrate Linux usage (e.g., export, variable substitution).
  • Mention installation and usage of Azure CLI on Linux systems, including package manager instructions.
  • If PowerShell examples are provided, consider also providing bash equivalents for common scripting tasks.
  • Avoid implying PowerShell is required for resource management; highlight CLI as the default for cross-platform scenarios.
  • Include troubleshooting or usage notes relevant to Linux users (e.g., file permissions, shell differences).
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: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits Windows bias by providing JSON examples that specify Windows OS types, Windows disk images, and Windows-specific configuration fields (e.g., 'windowsConfiguration', 'timeZone', 'MicrosoftWindowsServer'). There are no equivalent Linux-focused examples, nor are Linux-specific configuration fields or images shown. The ordering and content of examples prioritize Windows, despite the page being for 'virtual-machines-linux'.
Recommendations
  • Add parallel examples using Linux OS types (e.g., 'osType': 'Linux'), Linux disk images, and Linux-specific configuration fields (such as 'linuxConfiguration').
  • Include sample ARM templates and REST API payloads for provisioning Linux VMs and VMSS, with appropriate image references (e.g., Ubuntu, CentOS).
  • Ensure that both Windows and Linux examples are presented side-by-side or in alternating order, or prioritize Linux examples when the documentation is for Linux services.
  • Explicitly mention Linux-specific considerations or differences in user data handling, if any.
  • Review all code samples and configuration blocks to ensure Linux parity and visibility.
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 templates and Windows-specific image references in all code examples. The referenced templates and examples exclusively use 'MicrosoftWindowsServer' as the image publisher and 'WindowsServer' as the offer, with parameters for 'windowsOSVersion'. There are no Linux VM template examples, nor is there any mention of Linux image references or parameters. The only mention of Linux is in the 'Next steps' section, which links to a Linux template, but no Linux-specific example is shown or discussed in the main content.
Recommendations
  • Include parallel Linux VM template examples alongside Windows examples, using 'Canonical' or other Linux publishers and appropriate offers/skus.
  • Show how to specify Linux OS images in the 'imageReference' section of the template.
  • Add Linux-specific configuration notes where relevant (e.g., differences in OS disk settings, diagnostics, or data disk attachment).
  • Ensure that both Windows and Linux examples are presented with equal prominence throughout the documentation, not just in external links.
  • Clarify any differences in disk provisioning or template structure that may apply to Linux VMs.
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 exhibits a subtle Windows bias by listing the Windows Server cluster creation guide before the Linux equivalent in the 'Next steps' section. No PowerShell-heavy examples, Windows-exclusive tools, or missing Linux examples are present in the main content, which is platform-neutral and focused on ARM templates.
Recommendations
  • List Linux and Windows cluster creation guides in parallel or alternate their order to avoid implying priority.
  • Explicitly state that all ARM template examples and guidance apply equally to both Windows and Linux clusters.
  • Where platform-specific instructions are given, ensure both Windows and Linux are covered with equal prominence.
GitHub Create Pull Request