← Back to Dashboard
277
Pages Scanned
115
Pages Flagged
277
Changed Pages
41.5%
% Pages Flagged

Live Progress

🔴 Connecting...
100%
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:08 Scan started

Scan Information

Started At: 2026-03-02 00:00:08

Finished At: In Progress

Status: in_progress

Target Repo: Azure Compute

Current Phase: discovery

Files Queued: 277

Files Completed: 277

Problematic Pages

115 issues found
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 for Initializer CodePackages in Service Fabric is heavily Windows-focused. All examples use Windows containers (nanoserver), Windows paths, and Windows command-line syntax (cmd, C:\ paths, etc.). There are no Linux container examples, nor any mention of how to use Initializer CodePackages with Linux containers or on Linux-based Service Fabric clusters. Windows tools and patterns are referenced exclusively.
Recommendations
  • Add equivalent examples using Linux containers (e.g., Ubuntu or Alpine images) with Linux shell commands and paths.
  • Clarify whether Initializer CodePackages are supported for Linux containers and, if so, provide guidance and examples.
  • If there are limitations or differences for Linux, explicitly document them.
  • When showing examples, provide both Windows and Linux variants side-by-side where applicable.
GitHub Create Pull Request
Service Fabric Azure Service Fabric reverse proxy ...articles/service-fabric/service-fabric-reverseproxy.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page explicitly states that the Service Fabric reverse proxy is not available for Linux clusters, and all examples and guidance are implicitly Windows-centric. There are no Linux-specific instructions, examples, or parity guidance. The page assumes a Windows environment throughout, and Linux users are left without actionable steps or alternatives.
Recommendations
  • Clearly indicate at the top that the reverse proxy is Windows-only, and link to Linux alternatives or roadmap if available.
  • Provide guidance or links for Linux users on how to achieve similar functionality (e.g., using other proxies or patterns).
  • If/when Linux support is planned, include a section on expected parity and migration steps.
  • Add a prominent note in the 'Next steps' section clarifying the Windows-only status and redirecting Linux users to relevant resources.
GitHub Create Pull Request
Service Fabric Standalone Service Fabric clusters overview ...-fabric/service-fabric-standalone-clusters-overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
Although the introduction claims Service Fabric clusters can run on both Windows Server and Linux, the documentation page focuses exclusively on Windows Server. All examples, security options, and supported operating systems are Windows-only, with no Linux-specific guidance or examples. The 'Supported operating systems' section explicitly states that Linux isn't yet supported for standalone clusters, contradicting the opening statement.
Recommendations
  • Clarify in the introduction that standalone Service Fabric clusters are currently Windows-only, and Linux support is not available.
  • Remove or revise statements implying Linux parity unless Linux support is actually available.
  • Add a section about Linux support status, expected timelines, or alternative approaches for Linux users (e.g., using Service Fabric on Azure or other supported environments).
  • If Linux support is planned, provide links or references to Linux-specific documentation or guidance.
GitHub Create Pull Request
Service Fabric Service Fabric Explorer blocking operations ...ged-cluster-service-fabric-explorer-blocking-operation.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page primarily references Az PowerShell cmdlets for managing Service Fabric resources, with explicit links to PowerShell modules and commands. While the az CLI is mentioned for deleting applications, PowerShell is consistently presented first and in more detail. There are no explicit Linux/macOS examples or references to Bash or cross-platform CLI usage, which may create friction for non-Windows users.
Recommendations
  • Provide equivalent az CLI examples for all operations (e.g., unprovisioning application type versions, creating applications/services).
  • Mention that az CLI is cross-platform and suitable for Linux/macOS users.
  • Add Bash shell examples alongside PowerShell where relevant.
  • Clarify that ARM templates and az CLI can be used from any OS.
GitHub Create Pull Request
Service Fabric RunToCompletion semantics and specifications ...blob/main/articles/service-fabric/run-to-completion.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page presents RunToCompletion semantics in Service Fabric with a strong Windows bias. All code examples use Windows containers (nanoserver:1809), Windows-specific commands (cmd, echo, ping, set, exit), and reference Windows container compatibility. Querying deployment status is shown only via PowerShell and C# APIs, with no mention of Linux equivalents or cross-platform CLI tools. There are no examples or guidance for Linux containers or Linux-based workflows.
Recommendations
  • Add equivalent examples using Linux containers (e.g., Ubuntu or Alpine images) and Linux shell commands.
  • Clarify whether RunToCompletion semantics are supported for Linux containers and provide guidance if so.
  • Include cross-platform CLI examples (e.g., Azure CLI, sfctl) for querying deployment status, not just PowerShell.
  • Mention any limitations or differences for Linux users explicitly.
  • If RunToCompletion is Windows-only, state this clearly at the top to avoid confusion.
GitHub Create Pull Request
Service Fabric Deploy and upgrade with Azure Resource Manager ...vice-fabric/service-fabric-application-arm-resource.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page provides PowerShell examples for removing Service Fabric application resources, but does not offer equivalent CLI or Linux/macOS-friendly examples. PowerShell is mentioned as the primary tool for post-deployment management, and the CLI is referenced only as an alternative in the 'Next steps' section. This creates friction for Linux/macOS users who may prefer or require cross-platform tools.
Recommendations
  • Add Azure CLI examples alongside PowerShell for resource removal and management tasks.
  • Explicitly mention that both PowerShell and CLI are supported for these operations, and provide links to relevant CLI documentation.
  • Ensure that cross-platform tools (e.g., Service Fabric CLI, Azure CLI) are referenced equally and not only as secondary options.
  • Consider including REST API examples where appropriate, as these are platform-agnostic.
GitHub Create Pull Request
Service Fabric Architecture of Azure Service Fabric ...articles/service-fabric/service-fabric-architecture.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation mentions PowerShell cmdlets as a primary management interface for Service Fabric, without referencing equivalent Linux/macOS tooling (such as Azure CLI or REST APIs). Additionally, Windows security is mentioned alongside X509 certificates in the transport subsystem, with no discussion of Linux authentication mechanisms. These patterns suggest a Windows-first bias, though the architectural content is largely platform-neutral.
Recommendations
  • Add examples or references to Linux/macOS management tools, such as Azure CLI or REST APIs, alongside PowerShell cmdlets.
  • Clarify whether management operations can be performed from non-Windows environments and provide guidance for Linux/macOS users.
  • Mention authentication mechanisms commonly used on Linux (e.g., SSH, certificate-based auth) if relevant, or clarify platform support.
  • Ensure that platform-neutral language is used where possible, and avoid implying PowerShell is the only supported management interface.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager: Movement cost ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-movement-cost.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides PowerShell examples for configuring move cost in Service Fabric, but does not offer equivalent Linux CLI or Bash examples. PowerShell is presented first in each example section, followed by C#. There is no mention of Linux tools or cross-platform CLI alternatives, which may create friction for Linux/macOS users managing Service Fabric clusters.
Recommendations
  • Add Azure CLI or Bash examples for configuring and updating move cost, where possible.
  • Mention whether PowerShell commands are supported on Linux/macOS, or provide guidance for Linux users.
  • Consider presenting cross-platform CLI examples before or alongside PowerShell examples.
  • Clarify if certain operations are Windows-only, or provide links to Linux-specific documentation if available.
GitHub Create Pull Request
Service Fabric Service sensitivity ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-sensitivity.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides PowerShell examples for configuring service sensitivity and maximum load, but does not offer equivalent Linux/macOS CLI examples (such as Bash, Azure CLI, or REST API). PowerShell is presented as the primary scripting interface, which may create friction for Linux/macOS users. The C# API examples are cross-platform, but operational scripting is Windows-centric.
Recommendations
  • Add Azure CLI or REST API examples for configuring service sensitivity and maximum load, if supported.
  • Explicitly note whether PowerShell commands can be run cross-platform (PowerShell Core), or provide Bash equivalents.
  • Clarify if Service Fabric management tasks can be accomplished via Linux-native tools or scripts.
  • If PowerShell is the only supported scripting interface, state this clearly and link to any Linux/macOS installation guidance for PowerShell Core.
GitHub Create Pull Request
Service Fabric Upgrade an Azure Service Fabric standalone cluster ...ce-fabric/service-fabric-cluster-upgrade-standalone.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page primarily references Windows-specific upgrade and configuration guides (e.g., links ending with '-windows-server.md'), and the patch orchestration application is described only for Windows. There is no mention of Linux-specific upgrade procedures, configuration files, or patch orchestration, nor are Linux examples or links provided. This creates friction for Linux users managing Service Fabric standalone clusters.
Recommendations
  • Add explicit references and links to Linux-specific upgrade and configuration documentation, if available.
  • Provide examples and procedures for Linux clusters alongside Windows examples.
  • Clarify which features or tools are Windows-only and offer Linux alternatives or workarounds where possible.
  • Include information about patch orchestration for Linux nodes, or state if it is not supported.
GitHub Create Pull Request
Service Fabric Specifying Service Fabric service endpoints ...ce-fabric/service-fabric-service-manifest-resources.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page primarily uses Windows/PowerShell tooling and paths in its examples and instructions. PowerShell is the only command-line example shown for deploying applications, and file paths reference Windows locations. Linux equivalents are only briefly mentioned (e.g., the certificate store path), and no Linux-native deployment commands or examples are provided.
Recommendations
  • Provide equivalent Linux CLI examples (e.g., using Azure CLI or Service Fabric CLI) alongside PowerShell commands for deploying applications.
  • When referencing file paths (such as the schema definition or certificate store), include both Windows and Linux locations in parallel.
  • Add notes or sections clarifying any differences in workflow or configuration for Linux clusters, especially for deployment and endpoint/certificate management.
  • Where possible, link to Linux-specific documentation or tutorials for common tasks.
GitHub Create Pull Request
Service Fabric Define Service Configuration in StartupServices.xml for a Service Fabric Application ...service-fabric/service-fabric-startupservices-model.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation is heavily focused on Visual Studio workflows and references PowerShell for service creation, with no mention of Linux/macOS equivalents or cross-platform tooling. All examples and instructions are centered around Windows tools and patterns, and there are no instructions or guidance for Linux/macOS users deploying Service Fabric applications.
Recommendations
  • Add explicit guidance for Linux/macOS users, including CLI-based workflows (e.g., Azure CLI, Service Fabric CLI) for managing service configurations.
  • Provide examples of how to deploy and manage Service Fabric applications using cross-platform tools, not just Visual Studio and PowerShell.
  • Clarify which features are Windows-only and which are available cross-platform, and link to Linux/macOS documentation where relevant.
  • Mention alternative editors or IDEs for non-Windows users, if applicable.
GitHub Create Pull Request
Service Fabric Fault Analysis Service overview .../service-fabric/service-fabric-testability-overview.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page for the Fault Analysis Service overview provides usage instructions primarily for C# and PowerShell, with explicit mention of the Service Fabric SDK and PowerShell module. There are no examples or guidance for Linux/macOS users (e.g., Bash, CLI, or cross-platform tools), and PowerShell is presented as the only scripting interface. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other tools.
Recommendations
  • Add examples for using the Fault Analysis Service via Azure CLI or REST API, which are cross-platform.
  • Provide Bash or shell script equivalents for common tasks, or clarify if PowerShell Core (cross-platform) is supported.
  • Explicitly mention any Linux/macOS limitations or supported workflows for the Fault Analysis Service.
  • Include links or references to Linux/macOS documentation for Service Fabric where relevant.
GitHub Create Pull Request
Virtual Machines Share an Azure Managed Disk across VMs ...cs/blob/main/articles/virtual-machines/disks-shared.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation provides both Windows and Linux coverage, but Windows examples and tools (WSFC, CSV, Windows clustering, Windows-specific templates) are presented first and in greater detail. Windows clustering patterns and terminology (WSFC, CSV) are referenced before Linux equivalents, and Windows sample workloads are listed before Linux. Linux tools and cluster managers (Pacemaker, Corosync, sg_persist, fence_scsi) are mentioned, but with less depth and fewer practical examples. Performance throttling examples are Windows-first, with Linux scenarios appearing later.
Recommendations
  • Present Linux and Windows examples in parallel or alternate order, rather than Windows-first.
  • Expand Linux sample workloads with practical, step-by-step examples (e.g., Pacemaker configuration, clustered filesystem setup).
  • Provide Linux-specific templates and links, similar to Windows (e.g., for clustered file servers or SAP workloads).
  • Include Linux command-line examples for disk reservation and cluster setup, not just tool mentions.
  • Ensure performance throttling examples include Linux scenarios with equal detail.
GitHub Create Pull Request
Service Fabric X.509 Certificate-based Authentication in a Service Fabric Cluster ...ticles/service-fabric/cluster-security-certificates.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation provides detailed information on X.509 certificate-based authentication in Service Fabric clusters, but exhibits Windows bias in several areas. Windows certificate store paths (e.g., LocalMachine\My), Windows-specific troubleshooting tools (event logs, CAPI2 logging), and Win32 CryptoAPI references are mentioned first or exclusively. Linux equivalents are referenced only briefly or parenthetically, and no Linux-specific troubleshooting guidance or examples are provided.
Recommendations
  • Provide explicit Linux certificate store paths and management instructions alongside Windows examples (e.g., detail usage of /var/lib/sfcerts).
  • Include Linux-specific troubleshooting steps, such as relevant log locations, commands (e.g., journalctl, openssl), and error codes.
  • Reference cross-platform certificate management tools and APIs, not just Win32 CryptoAPI.
  • Ensure that configuration examples and explanations are equally applicable to Linux, and clarify any platform-specific differences.
  • Add a section or callouts for Linux/macOS users, highlighting any nuances or limitations.
GitHub Create Pull Request
Service Fabric Custom Image .../articles/service-fabric/how-to-deploy-custom-image.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page primarily discusses deploying custom Windows images in Azure Service Fabric Managed Clusters. Windows terminology and examples are presented first and most prominently. The only CLI example given is in PowerShell, and there are no equivalent Linux shell or Azure CLI examples for role assignment. While the page references Linux custom image creation and Azure CLI for browsing Marketplace images, the main workflow and examples are Windows-centric.
Recommendations
  • Add equivalent Azure CLI or Bash examples for role assignment and other operations, not just PowerShell.
  • Clarify whether Linux custom images are supported for Service Fabric Managed Clusters and provide explicit guidance/examples if so.
  • Present Windows and Linux options equally, or note if only Windows images are supported for node types.
  • Include links to Linux-specific documentation where relevant.
GitHub Create Pull Request
Service Fabric Manage certificates in a Service Fabric cluster ...vice-fabric/cluster-security-certificate-management.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page provides a comprehensive overview of certificate management in Azure Service Fabric clusters, but exhibits Windows bias in several areas. PowerShell is the only scripting example shown for certificate enrollment, and references to Windows-specific tools and patterns (such as the Key Vault VM extension for Windows, S-channel, and Windows certificate store concepts) are prevalent. The Key Vault VM extension is described primarily in its Windows context, and Windows-specific behaviors (like certificate linking and renewal properties) are discussed in detail. Linux equivalents, such as the Key Vault VM extension for Linux or Linux certificate store handling, are not mentioned or are relegated to secondary status. Windows terminology and tools are presented first and exclusively in critical sections, creating friction for Linux/macOS users.
Recommendations
  • Add Linux-specific examples for certificate enrollment and provisioning, such as using Azure CLI or Bash scripts instead of only PowerShell.
  • Include guidance for using the Key Vault VM extension for Linux, referencing its documentation and any differences in behavior compared to Windows.
  • Discuss certificate store handling and ACLing on Linux nodes, including relevant commands and security considerations.
  • Where Windows-specific behaviors (like S-channel and certificate linking) are described, clarify their applicability and provide Linux alternatives or note their absence.
  • Ensure troubleshooting and FAQ sections include Linux/macOS scenarios and commands.
GitHub Create Pull Request
Service Fabric Configure or modify a Service Fabric managed cluster node type ...vice-fabric/how-to-managed-cluster-modify-node-type.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides examples for configuring Service Fabric managed cluster node types using Azure Portal, ARM templates, and PowerShell. PowerShell is the only CLI tool shown, with no mention of Azure CLI or Bash equivalents. PowerShell examples are given for all major operations (add, remove, scale, configure placement properties), and are presented alongside Portal and ARM template methods. There is no explicit indication that these operations require Windows, but the exclusive use of PowerShell and lack of Azure CLI/Bash examples may create friction for Linux/macOS users.
Recommendations
  • Add Azure CLI examples for all operations where PowerShell is used, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention if PowerShell is required for certain operations, or clarify if Azure CLI can be used instead.
  • Consider listing Azure CLI or Bash examples before or alongside PowerShell to improve parity.
  • Add notes or links for Linux/macOS users about how to perform equivalent tasks.
GitHub Create Pull Request
Service Fabric Introduction to the Service Fabric Infrastructure Service .../articles/service-fabric/infrastructure-service-faq.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides a PowerShell command example for bypassing Infrastructure Service, with no equivalent Linux/macOS CLI or REST API example. The use of PowerShell and the Invoke-ServiceFabricInfrastructureCommand cmdlet suggests a Windows-centric approach, and the example is given without mention of cross-platform alternatives. Service Fabric Explorer is referenced, but no Linux-friendly tooling is discussed.
Recommendations
  • Add equivalent examples using Azure CLI, REST API, or other cross-platform tools for managing Infrastructure Service.
  • Clarify whether the PowerShell command is required, or if Linux/macOS users can perform the same operation via other means.
  • Mention any limitations or prerequisites for non-Windows users, and provide guidance for Linux/macOS environments.
  • If Service Fabric Explorer is Windows-only, suggest alternative monitoring tools or interfaces for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Migrate an Azure Service Fabric cluster to availability zone support ...ce-fabric/migrate-service-fabric-availability-zones.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides extensive PowerShell-based migration steps and scripts for Service Fabric clusters, especially in the section for migrating clusters with Basic SKU load balancer and IP resources. PowerShell is a Windows-centric tool, and the examples and commands are exclusively shown using PowerShell, with no equivalent Bash, Azure CLI, or cross-platform scripting alternatives. Additionally, references to Windows paths (e.g., 'D:\\SvcFab') and Windows-centric sample templates are present, and Windows tools are mentioned before any Linux alternatives. While there is a mention of an Ubuntu sample template, the actual migration steps and scripts are Windows/PowerShell-only.
Recommendations
  • Provide Azure CLI or Bash equivalents for all PowerShell scripts and migration steps to ensure Linux/macOS users can follow the guide without friction.
  • Explicitly note which steps require Windows/PowerShell and offer alternatives or workarounds for Linux/macOS environments.
  • Where sample templates reference Windows paths or configurations, include Linux/Ubuntu equivalents and clarify any OS-specific requirements.
  • Add links to cross-platform tooling documentation (e.g., Azure CLI, Bash) for relevant tasks.
GitHub Create Pull Request
Service Fabric Monitor Azure Service Fabric ...main/articles/service-fabric/monitor-service-fabric.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation covers monitoring Azure Service Fabric clusters on both Windows and Linux, but several sections show a Windows-first bias. Windows tools and patterns (e.g., Event Log, Event Viewer, Diagnostics Agent) are mentioned before Linux equivalents, and some examples or tutorials are Windows-centric (.NET, Visual Studio templates). Linux-specific guidance is present but less prominent, sometimes only referenced via links. Some features (like EventStore APIs) are Windows-only, but this is clearly stated. Overall, Linux users can complete the tasks, but may experience friction due to less detailed or less prominent Linux guidance.
Recommendations
  • Ensure Linux-specific monitoring tools and patterns are described with equal prominence and detail as Windows equivalents.
  • Provide Linux-first or parallel examples in sections that currently show Windows tools or workflows first (e.g., mention Syslog, LTTng, and Linux agent configuration alongside Windows Event Log/Diagnostics Agent).
  • Include explicit Linux sample code/tutorial links wherever Windows/.NET examples are given.
  • Clarify when features are Windows-only and provide alternative Linux approaches or links.
  • Add more Linux-focused screenshots and walkthroughs, especially for cluster and infrastructure monitoring.
GitHub Create Pull Request
Service Fabric Describing Azure Service Fabric apps and services ...ic/service-fabric-application-and-service-manifests.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation contains some Windows bias, primarily in the form of referencing Windows tools (e.g., Visual Studio, C:\Program Files paths) and mentioning PowerShell for service creation. There are no explicit Linux/macOS equivalents or cross-platform tooling suggestions, and the only tool-based guidance is Windows-specific.
Recommendations
  • Where Visual Studio is recommended for schema validation, suggest cross-platform alternatives such as VS Code with XML plugins, or xmllint for schema validation on Linux/macOS.
  • When referencing file paths (e.g., C:\Program Files\...), mention the equivalent location or approach for Linux clusters (e.g., /opt/microsoft/servicefabric/schemas/ or a note about schema availability).
  • When mentioning PowerShell for service creation, also mention the Service Fabric CLI (sfctl), which is cross-platform, and provide example commands.
  • Add explicit notes or examples for Linux-based Service Fabric clusters, especially for common developer tasks.
  • Review and update any tool or workflow recommendations to ensure Linux/macOS parity where possible.
GitHub Create Pull Request
Service Fabric Learn about Azure Service Fabric application security ...ric/service-fabric-application-and-service-security.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation provides a general overview of Service Fabric application security, but several sections show Windows bias. Windows-specific tools and patterns (e.g., Active Directory, gMSA, BitLocker, NetworkService account) are mentioned, often before or instead of Linux equivalents. Some examples and links focus on Windows scenarios, and Linux-specific guidance is either missing or relegated to brief mentions. Disk encryption is discussed primarily with Windows/PowerShell, and Linux disk encryption is left as a TODO. The use of Windows accounts and features is described in detail, while Linux approaches are less explicit.
Recommendations
  • Add explicit Linux examples and guidance for disk encryption, including supported tools and patterns (e.g., dm-crypt, Azure Disk Encryption for Linux).
  • Provide parity in user account and security principal configuration for Linux clusters, including how to run services under Linux user accounts and groups.
  • Include Linux-specific instructions for certificate management and container security, not just Windows/gMSA.
  • Ensure that all code snippets and walkthroughs are available for both Windows and Linux environments.
  • Clarify which features are cross-platform and which are Windows-only, and provide alternative approaches for Linux where possible.
GitHub Create Pull Request
Service Fabric Application upgrade: data serialization ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-application-upgrade-data-serialization.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page provides links to upgrade tutorials using Visual Studio and PowerShell, both of which are Windows-centric tools. There are no equivalent Linux/macOS upgrade examples or CLI alternatives mentioned. The serialization guidance is focused on C# and .NET, but Service Fabric supports .NET Core, which is cross-platform. The page does not mention Linux tooling or workflows for application upgrades.
Recommendations
  • Add examples or links for upgrading Service Fabric applications using cross-platform tools such as Azure CLI or Service Fabric CLI (sfctl).
  • Include guidance for Linux/macOS users, such as how to perform upgrades from non-Windows environments.
  • Mention .NET Core/.NET 5+ compatibility and serialization options for cross-platform scenarios.
  • Ensure parity in documentation by providing Linux/macOS-specific instructions alongside Windows/PowerShell/Visual Studio examples.
GitHub Create Pull Request
Service Fabric Service Fabric application upgrade ...s/service-fabric/service-fabric-application-upgrade.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page for Service Fabric application upgrade demonstrates a notable Windows bias. PowerShell is the only CLI example provided, and references to Windows-specific tools (e.g., http.sys, PowerShell cmdlets) are present. There are no Linux or cross-platform CLI examples (such as Azure CLI, REST API, or Service Fabric CLI), and Windows tools and patterns are mentioned exclusively or before any Linux equivalents. This creates friction for Linux/macOS users, who may not have access to PowerShell or Windows-specific APIs.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl), Azure CLI, or REST API for application upgrades.
  • Mention cross-platform upgrade workflows and tools where possible.
  • Clarify which features or commands are Windows-only, and provide guidance for Linux/macOS users.
  • Include links or references to Linux/macOS documentation for Service Fabric application upgrades.
GitHub Create Pull Request
Service Fabric Application lifecycle in Service Fabric ...service-fabric/service-fabric-application-lifecycle.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page frequently references PowerShell cmdlets and Windows-centric tooling (e.g., Copy-ServiceFabricApplicationPackage, Register-ServiceFabricApplicationType) alongside .NET APIs and REST operations, but does not provide equivalent Linux/CLI examples or highlight cross-platform tools (such as sfctl or Azure CLI) in the main procedural sections. PowerShell examples are shown first and most prominently, and Windows tools are mentioned before REST or cross-platform alternatives, creating friction for Linux/macOS users.
Recommendations
  • Add explicit examples and procedural steps using sfctl (Service Fabric CLI) and Azure CLI for all major lifecycle operations (deploy, upgrade, remove, etc.), ensuring parity with PowerShell examples.
  • Where PowerShell cmdlets are referenced, also mention or link to the equivalent sfctl/Azure CLI commands, and clarify which tools are cross-platform.
  • Consider reordering tool mentions so that cross-platform options (sfctl, Azure CLI, REST API) appear before or alongside Windows-specific tools.
  • Add a short section or note clarifying which management tools are available on Linux/macOS and how to use them for common tasks.
  • Ensure that all code snippets and automation examples include Linux-compatible options where possible.
GitHub Create Pull Request
Service Fabric Advanced Application Upgrade Topics ...-fabric/service-fabric-application-upgrade-advanced.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides numerous PowerShell-based examples and references, with no equivalent CLI or Linux-native examples. The Service Fabric PowerShell cmdlets are used throughout for application upgrade operations, and there is no mention of cross-platform tools (such as Azure CLI or REST API) for Linux/macOS users. Additionally, PowerShell examples are presented first and exclusively, creating friction for users on non-Windows platforms.
Recommendations
  • Add Azure CLI examples for all upgrade operations (e.g., creating/updating services, starting upgrades, rolling back upgrades, updating parameters).
  • Mention REST API options for Service Fabric management where applicable.
  • Clarify which PowerShell cmdlets are available cross-platform (via PowerShell Core) and which are Windows-only.
  • Provide guidance for Linux/macOS users on how to perform equivalent operations, including links to relevant documentation.
  • Where possible, present cross-platform examples (Azure CLI, REST API) alongside PowerShell examples, not just after or instead of them.
GitHub Create Pull Request
Service Fabric Application upgrade: upgrade parameters ...abric/service-fabric-application-upgrade-parameters.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page presents Windows/PowerShell and Visual Studio parameters and examples before Linux equivalents (SFCTL), and provides more detailed parameter tables and explanations for PowerShell and Visual Studio. SFCTL (the cross-platform CLI) is covered later and with less depth. The 'Next steps' section also lists Windows-centric tutorials first, with Linux CLI guidance appearing later.
Recommendations
  • Reorganize the documentation so that SFCTL (cross-platform CLI) parameters and examples are presented alongside or before PowerShell/Visual Studio sections.
  • Provide equally detailed parameter tables and explanations for SFCTL as are given for PowerShell and Visual Studio.
  • Add explicit Linux/macOS usage examples for SFCTL, including sample commands and parameter usage.
  • In the 'Next steps' section, list Linux/SFCTL tutorials alongside or before Windows/PowerShell/Visual Studio tutorials to signal parity.
  • Clarify that SFCTL is the recommended cross-platform tool for Linux/macOS users.
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
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page for on-demand backup in Azure Service Fabric exclusively provides PowerShell-based examples and instructions, which are inherently Windows-centric. There are no examples or guidance for Linux/macOS users, such as using Bash, Azure CLI, or cross-platform REST tools (e.g., curl). The prerequisite section requires installation of a PowerShell module, and all REST API calls are demonstrated using PowerShell cmdlets, with no mention of alternatives for non-Windows environments.
Recommendations
  • Add equivalent examples using Azure CLI or Bash scripts for REST API calls (e.g., using curl or wget).
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module can be used on PowerShell Core (pwsh) on Linux/macOS, or provide alternatives.
  • Include instructions for connecting to Service Fabric clusters from Linux/macOS environments.
  • Provide guidance for Linux/macOS users on prerequisites and tool installation.
  • Consider showing REST API payloads and headers separately from PowerShell, so users can use any HTTP client.
GitHub Create Pull Request
Service Fabric Restoring backup in Azure Service Fabric ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-backup-restore-service-trigger-restore.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page is heavily biased toward Windows/PowerShell usage. All code examples and instructions rely exclusively on PowerShell cmdlets and scripts, with no mention of Linux/macOS-compatible tools or workflows. The prerequisite explicitly requires the Microsoft.ServiceFabric.Powershell.Http module, and REST API usage is only demonstrated via PowerShell. There are no Bash, curl, or cross-platform CLI examples, nor guidance for Linux users.
Recommendations
  • Add equivalent Bash/curl examples for REST API calls, showing how to trigger restores and track progress from Linux/macOS.
  • Document how to authenticate and manage certificates for REST calls on Linux/macOS (e.g., using OpenSSL, curl --cert, etc.).
  • Mention Azure CLI or Service Fabric CLI (sfctl) alternatives if available, and provide cross-platform instructions.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module functionality is available or required on non-Windows platforms, and provide alternatives if not.
  • Include a section explicitly addressing Linux/macOS users, outlining supported workflows and any limitations.
GitHub Create Pull Request
Service Fabric Capacity planning and scaling for Azure Service Fabric ...bric/service-fabric-best-practices-capacity-scaling.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides PowerShell-based manual scaling instructions and references Windows tooling (e.g., PowerShell commands) without offering equivalent Linux CLI or cross-platform alternatives. Windows/PowerShell examples are given first and exclusively in critical scaling procedures, which creates friction for Linux users. However, the page does mention Linux clusters and links to Linux-specific documentation, indicating Service Fabric is not Windows-only.
Recommendations
  • Add equivalent Bash/CLI instructions for scaling operations, such as using Azure CLI or REST API calls, especially for disabling/removing nodes.
  • Clearly indicate which commands are Windows-specific and provide cross-platform alternatives where possible.
  • Include examples for Linux users in critical sections, such as scaling in/out, to ensure parity.
  • Reference Service Fabric CLI (sfctl) or Azure CLI for cluster management tasks alongside PowerShell.
  • Consider restructuring sections so Linux and Windows instructions are presented in parallel or clearly separated.
GitHub Create Pull Request
Service Fabric Azure Service Fabric infrastructure as Code Best Practices ...tps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-best-practices-infrastructure-as-code.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Resource Manager templates, but PowerShell is given its own section and is more prominent. Windows-specific tools and registry keys are mentioned in the VM upgrade section, with no Linux equivalents or guidance. PowerShell is used for cluster upgrades, with no Linux command-line alternatives (e.g., Bash or CLI) provided. Windows configuration properties are shown before any Linux-specific guidance, and Windows registry keys are referenced without mentioning Linux update management.
Recommendations
  • Add Linux-specific examples for cluster upgrades, such as Bash scripts or Azure CLI commands.
  • Include guidance for disabling automatic updates on Linux VMs (e.g., using apt or yum configuration) alongside Windows registry instructions.
  • Provide parity in upgrade instructions, showing both Windows and Linux approaches for manual upgrades.
  • Ensure PowerShell examples are paired with equivalent Bash or CLI examples where possible.
  • Clarify which steps are Windows-only and which are cross-platform, to help Linux/macOS users navigate the documentation.
GitHub Create Pull Request
Service Fabric Azure Service Fabric networking best practices ...ice-fabric/service-fabric-best-practices-networking.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides networking best practices for Azure Service Fabric clusters and covers both Windows and Linux scenarios. However, there is a noticeable bias towards Windows: PowerShell is referenced as the primary client API example, Windows-specific tools and terminology (e.g., netsh, RDP, Windows container workloads) are mentioned first or exclusively, and some example links and ARM templates are Windows-focused. Linux equivalents are sometimes mentioned, but often after Windows or less prominently.
Recommendations
  • Include Linux CLI (az CLI, bash) examples alongside PowerShell, especially for client API access and cluster management.
  • Mention Linux tools (e.g., ss, ip, netstat) where Windows tools like netsh are referenced.
  • Provide ARM template examples for Linux clusters, not just Windows.
  • Ensure Linux container networking scenarios are described with equal detail as Windows container scenarios.
  • When referencing reverse proxy solutions, highlight Linux-native options and usage patterns.
  • Balance the order of Windows and Linux references in sections and links.
GitHub Create Pull Request
Service Fabric Understanding periodic backup configuration ...-fabric-backuprestoreservice-configure-periodic-backup.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page primarily describes Service Fabric's periodic backup configuration in a platform-neutral way, but the only example for file share backup storage uses Windows-style UNC paths (\\StorageServer\BackupStore) and references 'Integrated Windows Authentication' as the default method for file share access. There are no Linux or SMB-specific examples or guidance for file share configuration, and Windows authentication is mentioned first and exclusively. Azure Blob storage examples are platform-neutral, but file share backup is presented as a Windows-centric scenario.
Recommendations
  • Add examples and guidance for configuring file share backup storage using SMB on Linux, including sample paths and authentication methods (e.g., username/password, mount options).
  • Clarify whether Linux-based Service Fabric clusters can use file share backup, and if so, provide parity instructions.
  • Mention Linux-compatible authentication mechanisms for file shares, such as Kerberos or username/password, and note any limitations.
  • Consider including a note about cross-platform support for file share backup, or explicitly state if Windows-only.
GitHub Create Pull Request
Service Fabric Azure Service Fabric security best practices ...rvice-fabric/service-fabric-best-practices-security.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation provides both Windows and Linux guidance for most security best practices, but Windows examples (such as PowerShell commands and Windows Defender configuration) are often presented first or exclusively. Windows-specific tools like PowerShell and Windows Defender are discussed in detail, while Linux equivalents are less prominent or omitted. Some sections (e.g., Windows Defender) are Windows-only, but this is acknowledged. Overall, Linux users can complete the tasks, but may experience friction due to Windows-centric ordering and tool focus.
Recommendations
  • Present Linux and Windows examples side-by-side or alternate their ordering to avoid Windows-first bias.
  • Where Windows-specific tools are discussed (e.g., Windows Defender), provide equivalent Linux guidance (such as recommended Linux antivirus solutions or security baselines) or explicitly state Linux alternatives.
  • Expand Linux-specific instructions and examples, especially for certificate management and encryption, to match the detail provided for Windows.
  • Clarify when a section is Windows-only and provide links or references to Linux documentation where appropriate.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager - Placement Policies ...ce-manager-advanced-placement-rules-placement-policies.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides code examples in C# and PowerShell for configuring Service Fabric placement policies, but does not include equivalent Linux/macOS CLI examples (such as Azure CLI or Bash). PowerShell is featured as the only command-line tool, and Windows-centric tools are presented first and exclusively, creating friction for Linux/macOS users who may not have access to PowerShell or prefer other tools.
Recommendations
  • Add Azure CLI or Bash examples for configuring placement policies, especially for service creation and management.
  • Explicitly mention cross-platform alternatives to PowerShell for cluster and service management.
  • Clarify whether the PowerShell commands are usable on Linux/macOS (e.g., via PowerShell Core), or provide guidance for Linux users.
  • Consider reordering examples so that cross-platform tools are presented alongside or before Windows-specific tools.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager - Application Groups ...ice-fabric-cluster-resource-manager-application-groups.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation provides only PowerShell and C# examples for managing Application Groups in Service Fabric. PowerShell is a Windows-centric tool, and no Linux/macOS CLI or scripting examples (such as Bash, Azure CLI, or REST API) are provided. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other tools.
Recommendations
  • Add equivalent examples using Azure CLI (az servicefabric) or REST API for all tasks currently demonstrated with PowerShell.
  • Mention cross-platform options for managing Service Fabric applications, such as Bash scripts or Azure CLI, especially for Linux/macOS users.
  • Clarify if PowerShell Core (pwsh) is supported and provide guidance for Linux/macOS users if so.
  • Consider including sample YAML or JSON for ARM templates if relevant, to show declarative configuration options.
GitHub Create Pull Request
Service Fabric Azure Service Fabric dynamic node tags ...tps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-node-tagging.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page provides PowerShell examples for managing node tags and services in Azure Service Fabric, but does not include equivalent CLI or scripting examples for Linux/macOS environments. PowerShell is a Windows-centric tool, and its exclusive use here creates friction for users on other platforms. No mention is made of Azure CLI, Bash, or REST API usage for these tasks, despite REST APIs being referenced earlier.
Recommendations
  • Add examples using Azure CLI or Bash scripts for managing node tags and services.
  • Include REST API sample calls for adding/removing node tags and updating service tag requirements.
  • Clarify whether PowerShell commands are cross-platform (e.g., PowerShell Core), or provide guidance for Linux/macOS users.
  • Mention any limitations or platform-specific requirements for node tag management.
GitHub Create Pull Request
Service Fabric Node types and virtual machine scale sets ...les/service-fabric/service-fabric-cluster-nodetypes.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation provides some Linux awareness (e.g., mentions 'ServiceFabricLinuxNode'), but overall, there is a Windows-first bias. Examples use Windows-style paths (e.g., 'D:\\SvcFab'), and the 'Next steps' section links to PowerShell scripts for RDP port and admin credential changes, which are Windows-specific tasks and tools. There are no explicit Linux/macOS command examples or guidance for SSH access, and Linux equivalents are not mentioned alongside Windows instructions.
Recommendations
  • Include Linux/macOS examples for common tasks, such as connecting to cluster nodes (e.g., SSH instructions) and managing credentials.
  • When showing configuration snippets, provide both Windows and Linux path examples for the 'dataPath' property.
  • In the 'Next steps' section, add links or guidance for Linux/macOS users (e.g., how to connect via SSH, change SSH keys, or manage Linux user accounts).
  • Clearly indicate when a step or script is Windows-only, and provide Linux alternatives where possible.
GitHub Create Pull Request
Service Fabric Manage Azure Service Fabric app load using metrics ...ric/service-fabric-cluster-resource-manager-metrics.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides code examples for C# and PowerShell, but omits equivalent Linux/macOS CLI examples (e.g., Azure CLI or REST API). PowerShell is featured prominently for service creation and metric management, and is presented before any mention of cross-platform alternatives. There is no discussion of Linux-native tools or workflows, which creates friction for non-Windows users managing Service Fabric clusters.
Recommendations
  • Add Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Mention REST API options for metric management, with example requests.
  • Clarify which management operations can be performed from Linux/macOS and provide guidance for those environments.
  • Consider including bash shell scripts or references to Service Fabric SDK tools available for Linux.
  • Explicitly state PowerShell is required only if using Windows, and provide parity for Linux users wherever possible.
GitHub Create Pull Request
Service Fabric Scalability of Service Fabric services .../service-fabric/service-fabric-concepts-scalability.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides code examples primarily in C# and PowerShell, with no equivalent Linux shell or CLI examples. PowerShell commands are referenced as the main administrative tooling, and Windows-specific patterns (e.g., PowerShell cmdlets) are mentioned before any Linux alternatives. There is a lack of guidance for Linux users on how to perform equivalent tasks, creating friction for those deploying Service Fabric clusters on Linux.
Recommendations
  • Add Linux CLI (e.g., Bash, Azure CLI) examples alongside PowerShell for administrative tasks such as updating instance counts and creating services.
  • Mention Linux-specific tools or commands (such as sfctl or Azure CLI) where PowerShell cmdlets are referenced.
  • Clarify which commands are Windows-only and provide Linux alternatives where possible.
  • Ensure parity in example ordering, showing Linux and Windows approaches side-by-side.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Auto Scaling Services and Containers ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-autoscaling.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides detailed examples for configuring auto scaling in Azure Service Fabric using application manifests, C# APIs, and PowerShell. However, all CLI/script examples are PowerShell-based, which is primarily a Windows tool. There are no equivalent Bash, Linux CLI, or cross-platform scripting examples. The PowerShell examples are presented alongside C# and manifest examples, but Linux users may lack guidance for command-line operations. Additionally, there is no mention of Linux-specific tools or patterns for managing Service Fabric auto scaling, and PowerShell is used without clarifying its cross-platform support.
Recommendations
  • Add Bash or Azure CLI examples for configuring scaling policies, especially for Linux-based Service Fabric clusters.
  • Clarify whether PowerShell examples are compatible with PowerShell Core on Linux/macOS, or provide alternatives.
  • Mention any Linux-specific considerations or limitations when using auto scaling features.
  • Include references to Linux management tools (e.g., Azure CLI, REST API) where appropriate.
GitHub Create Pull Request
Service Fabric Describe a cluster by using Cluster Resource Manager ...ce-fabric-cluster-resource-manager-cluster-description.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Windows and cross-platform (JSON) configuration examples for Service Fabric clusters, but Windows-specific XML (ClusterManifest.xml) and PowerShell examples are consistently shown first or exclusively. PowerShell is used for service creation and update examples, with no Linux/bash CLI equivalents. The XML configuration is wrapped in <WindowsServer> tags, which may imply Windows-centric deployment, though JSON examples are also given for standalone and Azure deployments. There is no explicit mention of Linux tooling or parity in command-line examples.
Recommendations
  • Add Azure CLI or bash examples for service creation and update, alongside PowerShell.
  • Clarify if ClusterManifest.xml examples are applicable to Linux clusters, or provide Linux-specific configuration examples if available.
  • Mention Linux support and any differences in cluster setup, especially for standalone deployments.
  • Ensure that JSON examples are given equal prominence to XML/Windows examples.
  • Where PowerShell is used, also provide Azure CLI or REST API equivalents for cross-platform users.
GitHub Create Pull Request
Service Fabric Cluster Resource Manager - Management Integration ...fabric-cluster-resource-manager-management-integration.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides a PowerShell example for querying partition health, using Windows-style paths and commands (e.g., 'PS C:\Users\User > Get-ServiceFabricPartitionHealth'), without offering equivalent Linux/bash examples or mentioning cross-platform tools. This creates friction for Linux/macOS users managing Service Fabric clusters, as they may not be familiar with PowerShell or its usage on non-Windows systems.
Recommendations
  • Add equivalent Linux/bash examples for querying partition health, such as using Service Fabric CLI (sfctl) or REST API calls.
  • Mention cross-platform management tools and how to perform the same tasks on Linux/macOS clusters.
  • Clarify that PowerShell examples are for Windows environments, and provide guidance for Linux users.
  • Where possible, use generic command syntax or highlight platform-specific differences.
GitHub Create Pull Request
Service Fabric Azure Service Fabric standalone cluster scaling ...ce-fabric/service-fabric-cluster-scaling-standalone.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page for scaling Azure Service Fabric standalone clusters shows evidence of Windows bias. It references PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) without mentioning Linux equivalents or cross-platform tools. The linked 'scale a standalone cluster' page is specifically for Windows Server, and there are no examples or guidance for Linux-based standalone clusters, even though Service Fabric can be deployed on Linux. This creates friction for Linux users seeking parity.
Recommendations
  • Add examples and instructions for scaling standalone clusters on Linux, including relevant CLI commands and configuration steps.
  • Mention cross-platform tools (such as sfctl or REST APIs) where possible, alongside PowerShell.
  • Clarify when instructions are Windows-specific and provide links or references to Linux documentation if available.
  • Ensure that guidance for querying and upgrading cluster configuration is available for Linux environments.
GitHub Create Pull Request
Service Fabric Secure an Azure Service Fabric cluster ...cles/service-fabric/service-fabric-cluster-security.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page for securing an Azure Service Fabric cluster exhibits a moderate Windows bias. While it mentions both Azure-hosted and standalone Windows clusters, it consistently provides detailed guidance and links for Windows Server clusters, but omits equivalent instructions or links for standalone Linux clusters. Windows security (Kerberos) is described, but there is no mention of Linux authentication mechanisms or how to secure standalone Linux clusters. Examples and recommendations for certificate creation reference Windows tools and services, with no Linux-specific alternatives or parity.
Recommendations
  • Add explicit guidance and links for securing standalone Linux Service Fabric clusters, including certificate setup and authentication options.
  • Provide Linux-specific examples for certificate creation, such as using OpenSSL, and clarify how to install and manage certificates on Linux nodes.
  • Mention Linux authentication mechanisms (if supported), or clarify if only certificate-based security is available for Linux clusters.
  • Ensure parity in recommendations and next steps by including Linux-focused documentation links where relevant.
GitHub Create Pull Request
Service Fabric Upgrading Azure Service Fabric clusters ...icles/service-fabric/service-fabric-cluster-upgrade.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page provides general guidance for upgrading Azure Service Fabric clusters, but exhibits mild Windows bias. Windows-specific tools (PowerShell) are mentioned alongside Azure CLI, but Linux equivalents are not explicitly referenced. The section on OS image upgrades links only to Windows patching guidance, omitting Linux node patching. Examples and instructions do not prioritize Linux or macOS, and Windows terminology appears first or exclusively in some sections.
Recommendations
  • Explicitly mention Linux node patching options and link to relevant documentation for Linux clusters.
  • Provide examples using Azure CLI and bash scripts, not just PowerShell, especially in sections about certificate management, port opening, and cluster upgrades.
  • Clarify when instructions are applicable to both Windows and Linux clusters, or note any differences.
  • Add links to Linux-specific Service Fabric cluster maintenance documentation where available.
GitHub Create Pull Request
Service Fabric Azure Service Fabric application resource model ...ervice-fabric/service-fabric-concept-resource-model.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a notable Windows bias. All deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) without mention of Azure CLI or other cross-platform tools. Application packaging instructions reference Visual Studio, a Windows-centric IDE, and do not provide alternatives for Linux/macOS users. No Linux/macOS-specific guidance or examples are given for key steps, such as packaging, uploading, or deploying applications.
Recommendations
  • Add Azure CLI examples for deployment and resource management alongside PowerShell examples.
  • Provide instructions for packaging Service Fabric applications using cross-platform tools (e.g., dotnet CLI, sfctl, or manual zip commands).
  • Mention alternative IDEs or command-line workflows for Linux/macOS users.
  • Ensure screenshots and walkthroughs are not exclusively tied to Windows tools.
  • Explicitly state which steps are Windows-only and offer Linux/macOS equivalents where possible.
GitHub Create Pull Request
Service Fabric Azure Service Fabric hosting model ...rticles/service-fabric/service-fabric-hosting-model.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides PowerShell examples and references to PowerShell cmdlets for managing Service Fabric services, with no equivalent Linux CLI or cross-platform examples. PowerShell is presented as the primary tool for service creation and management, and examples are shown before REST or .NET API alternatives. There is no mention of Linux-specific tools (such as sfctl) or Bash usage, and no guidance for Linux/macOS users.
Recommendations
  • Add equivalent examples using sfctl (Service Fabric CLI), which is cross-platform and supported on Linux/macOS.
  • Include Bash or shell command examples alongside PowerShell, especially for service creation and querying.
  • Mention that PowerShell examples are Windows-centric and provide links or references to Linux/macOS documentation.
  • Clarify that REST API and .NET SDK examples are cross-platform, and highlight their usage for non-Windows environments.
  • Update 'Next steps' to include Linux/macOS management options, not just PowerShell.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Events ...es/service-fabric/service-fabric-diagnostics-events.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page primarily references Windows-specific logging mechanisms (ETW/Windows Event logs, Windows Azure diagnostics agent) and does not mention Linux equivalents or provide Linux-specific guidance. Windows tools and patterns are discussed first and exclusively, creating friction for Linux cluster administrators seeking parity.
Recommendations
  • Add information about how Service Fabric events are accessed and logged on Linux clusters, including supported logging channels (e.g., stdout, syslog, Azure Monitor integration).
  • Provide examples or references for configuring diagnostics and event collection on Linux nodes.
  • Clarify which features or tools are Windows-only and offer Linux alternatives where possible.
  • Ensure that monitoring and event access instructions are platform-agnostic or clearly separated for Windows and Linux.
GitHub Create Pull Request
Service Fabric Azure Service Fabric DNS service ...n/articles/service-fabric/service-fabric-dnsservice.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides PowerShell examples for setting DNS names, references ApplicationManifest.xml (a Windows-centric deployment artifact), and describes enabling DNS service via the Azure portal (which is not supported for Linux clusters). There are no Linux-specific command-line examples (e.g., CLI or Bash), and Linux limitations are mentioned but not accompanied by alternative guidance or parity examples. Windows tools and patterns are presented first and more thoroughly.
Recommendations
  • Add Linux-specific examples for setting DNS names, such as using Azure CLI or Bash scripts.
  • Clarify how Linux users can enable DNS service (e.g., via ARM templates) and provide step-by-step instructions.
  • Include guidance for Linux container deployments outside of ApplicationManifest.xml and PowerShell.
  • Explicitly state limitations for Linux clusters earlier and link to Linux-specific documentation or workarounds.
  • Balance the order of examples so Linux and Windows approaches are presented equally.
GitHub Create Pull Request
Service Fabric Azure Service Fabric image store connection string ...fabric/service-fabric-image-store-connection-string.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page references PowerShell as the primary example for interacting with Service Fabric clusters and retrieving the cluster manifest, and links to a PowerShell-centric deployment guide. There are no explicit Linux or cross-platform CLI examples, nor mention of Linux tools or workflows for managing the ImageStoreConnectionString. The documentation assumes Visual Studio for publishing, which is Windows-centric, and does not provide parity for Linux/macOS users.
Recommendations
  • Add Azure CLI or cross-platform command examples for retrieving and configuring the ImageStoreConnectionString.
  • Include references to Linux/macOS-compatible tools and workflows (e.g., Bash, Azure CLI, REST API usage from curl).
  • Provide guidance for deploying Service Fabric applications from non-Windows environments.
  • Mention Visual Studio Code as an alternative to Visual Studio for cross-platform development.
  • Ensure links to deployment guides include both PowerShell and CLI/REST options.
GitHub Create Pull Request
Service Fabric Learn more about Azure Service Fabric ...icles/service-fabric/service-fabric-content-roadmap.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides a broad overview of Azure Service Fabric, which supports both Windows and Linux. However, there are several areas where Windows is prioritized or referenced first, such as descriptions of cluster nodes, service processes, and standalone clusters. Windows-specific tools (e.g., PowerShell) and executables are mentioned more prominently, and Linux equivalents or examples are often missing or referenced later. Some features (like standalone clusters) are noted as Windows-only, but Linux alternatives or workarounds are not always provided. Overall, the documentation creates friction for Linux users by not offering equal visibility or examples.
Recommendations
  • Ensure Linux examples and tools (e.g., Bash, Linux CLI usage) are provided alongside Windows/PowerShell examples.
  • When referencing Service Fabric executables or processes, clarify differences for Linux (e.g., systemd services, Linux process names) and provide Linux-specific instructions where applicable.
  • Avoid always mentioning Windows tools (PowerShell, Visual Studio) first; alternate order or provide parity.
  • Highlight Linux support and limitations more clearly, and link to Linux-specific guides where features differ.
  • Add explicit Linux walkthroughs for cluster creation, management, and health monitoring, especially where only Windows examples are given.
GitHub Create Pull Request
Service Fabric Package an existing executable to Azure Service Fabric ...abric/service-fabric-guest-executables-introduction.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates mild Windows bias. The schema definition for manifest files is referenced as being installed in a Windows directory (C:\Program Files\Microsoft SDKs\Service Fabric\schemas\ServiceFabricServiceModel.xsd), and the example application package structure uses a Windows-style executable (existingapp.exe). No Linux/macOS-specific paths, tools, or examples are provided, and there is no mention of packaging or deploying non-Windows executables (e.g., ELF binaries or scripts). Visual Studio is mentioned as a packaging tool, which is primarily Windows-focused, and no Linux-native alternatives are referenced.
Recommendations
  • Add examples or references for packaging and deploying Linux/macOS executables (e.g., ELF binaries, shell scripts).
  • Mention the location of schema files on Linux/macOS, if available, or clarify if the SDK is cross-platform.
  • Include command-line instructions and tools that are available on Linux/macOS, such as Azure CLI or cross-platform SDK usage.
  • Provide parity in sample applications, showing both Windows (.exe) and Linux (e.g., .sh, .out) guest executables.
  • Clarify Visual Studio alternatives for Linux/macOS users, such as VS Code or other editors.
GitHub Create Pull Request
Service Fabric Health monitoring in Service Fabric ...s/service-fabric/service-fabric-health-introduction.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides a detailed conceptual overview of Service Fabric health monitoring, but the only concrete example of reporting and evaluating health uses PowerShell cmdlets, with no equivalent Linux/macOS CLI or REST API example. The documentation mentions REST APIs and .NET APIs as options, but does not demonstrate their usage, creating friction for non-Windows users.
Recommendations
  • Add examples for reporting and evaluating health using REST APIs, which are cross-platform.
  • Include equivalent CLI examples using Service Fabric CLI (sfctl), which works on Linux/macOS.
  • Explicitly mention and demonstrate how Linux/macOS users can perform health reporting and querying tasks.
  • Where PowerShell is used, provide alternative commands or links for Linux/macOS environments.
GitHub Create Pull Request
Service Fabric Manage apps for multiple environments ...e-fabric-manage-multiple-environment-app-configuration.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page provides examples for managing Service Fabric application parameters across environments. It mentions PowerShell and Visual Studio (Windows-centric tools) first when describing how to pass parameters, with Linux-friendly tools (sfctl, Jenkins) referenced later or less prominently. There are no explicit Linux/macOS examples or screenshots, and the workflow descriptions are weighted toward Windows tools.
Recommendations
  • Add explicit Linux/macOS examples for parameter passing, such as using sfctl and install.sh, including sample command lines.
  • Provide parity in workflow descriptions for Linux users, e.g., describe how to use Jenkins or shell scripts to substitute parameters.
  • Reorder examples so Linux tools (sfctl, shell scripts) are presented alongside or before Windows tools.
  • Include screenshots or code snippets for Linux/macOS environments where relevant.
GitHub Create Pull Request
Service Fabric Azure Service Fabric container application manifest examples ...abric/service-fabric-manifest-example-container-app.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page provides application and service manifest examples for Azure Service Fabric container applications, but it is notably Windows-centric. The examples are based on a Windows Server 2016 container sample, and Windows-specific tools and patterns (such as 'winver' for OS build detection and Windows file paths) are referenced. There is no explicit Linux example, and Windows terminology and instructions appear before or instead of Linux equivalents.
Recommendations
  • Add equivalent Linux-based manifest examples, referencing a Linux container sample repository.
  • Include instructions for obtaining OS build/version on Linux (e.g., 'cat /etc/os-release' or 'uname -r') alongside the Windows 'winver' command.
  • Use cross-platform file paths in volume examples (e.g., '/mnt/data' for Linux) or clarify Windows-specific paths.
  • Clarify which manifest features are supported on Linux Service Fabric clusters, and note any differences.
  • Provide links to Linux-specific documentation or samples where available.
GitHub Create Pull Request
Service Fabric Networking patterns for Azure Service Fabric ...s/service-fabric/service-fabric-patterns-networking.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides only PowerShell-based deployment commands and examples, with no mention of Azure CLI, Bash, or Linux/macOS workflows. Windows tools (PowerShell, RDP, Windows command prompt) are used exclusively and shown first, creating friction for Linux/macOS users who must adapt instructions or use alternative tooling.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all deployment steps.
  • Mention Bash or shell scripting alternatives where relevant.
  • Clarify that Azure Resource Manager templates can be deployed from any OS, and provide cross-platform guidance.
  • Replace or supplement RDP and Windows command prompt examples (e.g., ping) with SSH and Bash equivalents.
  • Explicitly state OS-agnostic steps and note any Windows-specific requirements.
GitHub Create Pull Request
Service Fabric Service communication with the ASP.NET Core ...vice-fabric-reliable-services-communication-aspnetcore.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation covers both Windows and Linux scenarios for ASP.NET Core in Service Fabric, but there is a notable Windows bias in several areas. Windows-specific tools and APIs (HTTP.sys, Windows HTTP Server API, netsh) are discussed in detail, often before or more extensively than their Linux equivalents. HTTP.sys is described as Windows-only, and its configuration is explained with references to Windows tools. Kestrel, the cross-platform web server, is covered thoroughly and is recommended for Linux, but Windows-specific patterns and terminology (such as endpoint registration and port sharing) are introduced first and in greater depth. Some example code and configuration steps are Windows-centric, and Visual Studio debugging is referenced as a next step, which is primarily a Windows tool.
Recommendations
  • Ensure Linux parity by providing explicit Linux/macOS guidance where relevant, such as how to configure Kestrel endpoints and firewall rules on Linux.
  • Add notes or links for Linux/macOS users on how to debug Service Fabric applications using cross-platform tools (e.g., VS Code, CLI).
  • When discussing endpoint configuration or port assignment, clarify any OS-specific differences and provide Linux/macOS equivalents.
  • Consider reordering sections so that cross-platform solutions (Kestrel) are presented before Windows-only solutions (HTTP.sys).
  • Where Windows tools like netsh are mentioned, offer Linux alternatives or clarify that these steps are not required on Linux.
GitHub Create Pull Request
Service Fabric Replica soft delete for enhanced data protection in Service Fabric ...s/service-fabric/service-fabric-replica-soft-delete.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page for Replica Soft Delete in Service Fabric consistently references PowerShell APIs (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica) and provides examples and screenshots based on Windows tooling. There is no mention of Linux equivalents, CLI usage, or cross-platform SDK/API patterns. The documentation assumes familiarity with PowerShell and does not clarify whether these operations can be performed on Linux/macOS clusters or provide alternative commands for those platforms.
Recommendations
  • Add examples using Service Fabric CLI (sfctl), if available, for Linux/macOS users.
  • Clarify whether the PowerShell APIs are available or supported on Linux clusters, or provide equivalent REST/SDK usage.
  • Include screenshots and command outputs from Linux environments where possible.
  • Explicitly state platform requirements for the administrative APIs (PowerShell vs. CLI vs. SDK) and provide guidance for non-Windows users.
GitHub Create Pull Request
Service Fabric Add custom Service Fabric health reports ...rticles/service-fabric/service-fabric-report-health.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides extensive PowerShell examples and references, with no equivalent Linux/macOS CLI examples (such as Bash or Azure CLI). Windows tools and patterns (PowerShell cmdlets, Windows-style paths) are mentioned exclusively and before REST or API alternatives. This creates friction for Linux/macOS users, who are not shown how to perform health reporting tasks using their native tools.
Recommendations
  • Add equivalent Bash or Azure CLI examples for health reporting tasks, especially where PowerShell is used.
  • Clarify whether Service Fabric health reporting can be performed from Linux/macOS nodes and, if so, provide guidance for those environments.
  • Mention cross-platform REST usage earlier and provide concrete examples for Linux/macOS users (e.g., using curl).
  • Where PowerShell is referenced, note its availability on Linux/macOS, or provide alternatives if not supported.
  • Ensure that all configuration and reporting steps are documented for both Windows and Linux environments, including any differences in tooling or prerequisites.
GitHub Create Pull Request
Service Fabric Configure the upgrade of a Service Fabric application ...abric/service-fabric-visualstudio-configure-upgrade.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation focuses exclusively on upgrading Service Fabric applications using Visual Studio and PowerShell, both of which are Windows-centric tools. There are no examples or guidance for Linux/macOS users, such as using cross-platform CLI tools or alternative workflows. The only upgrade methods described are via Visual Studio (Windows-only) and PowerShell (primarily Windows), with no mention of Azure CLI, REST API, or Linux-compatible tools.
Recommendations
  • Add instructions and examples for upgrading Service Fabric applications using cross-platform tools such as Azure CLI or REST API.
  • Mention and link to any Linux/macOS-compatible workflows for Service Fabric application upgrades.
  • Clarify if PowerShell Core (pwsh) is supported for Service Fabric cmdlets on Linux/macOS, and provide relevant examples if so.
  • If Visual Studio is required, explicitly state its Windows-only nature and suggest alternatives for non-Windows users.
GitHub Create Pull Request
Virtual Machine Scale Sets Automatic OS image upgrades with Azure Virtual Machine Scale Sets ...e-sets/virtual-machine-scale-sets-automatic-upgrade.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation covers automatic OS image upgrades for Azure Virtual Machine Scale Sets and is intended for both Windows and Linux workloads. However, there is evidence of Windows bias: Windows terminology and properties are often mentioned first or exclusively (e.g., 'enableAutomaticUpdates', 'Windows Update'), ARM template examples default to Windows images, and PowerShell examples are prominent. While Azure CLI examples are provided (which are cross-platform), there are no explicit Linux-specific configuration examples or notes about Linux-specific behaviors, and Windows-specific settings are discussed in detail without equivalent Linux guidance.
Recommendations
  • Add explicit Linux-focused examples in ARM templates and Bicep (e.g., default to Ubuntu or Mariner images, not WindowsServer).
  • Provide guidance or notes on Linux-specific configuration nuances (such as handling custom scripts, extension behaviors, or disk mounting differences).
  • Ensure Linux terminology and settings are mentioned alongside Windows settings, not after or omitted.
  • Balance PowerShell and CLI examples, and clarify that CLI is cross-platform.
  • Where Windows-specific properties are discussed (e.g., 'enableAutomaticUpdates'), add a note about their irrelevance or Linux equivalents for Linux images.
GitHub Create Pull Request
Virtual Machines Deploy a ZRS managed disk ...lob/main/articles/virtual-machines/disks-deploy-zrs.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying ZRS managed disks, but there is notable bias towards Windows/PowerShell. PowerShell examples are extensive and use Windows-centric patterns (e.g., Windows VM images, Windows credentials, ConvertTo-SecureString), and PowerShell is presented before Linux-friendly alternatives in some sections. Resource Manager Template examples also use PowerShell commands for deployment, rather than cross-platform CLI or ARM template JSON. The Azure CLI examples use Ubuntu images, but PowerShell and ARM sections default to Windows images and Windows-specific configuration.
Recommendations
  • Provide ARM template deployment examples using pure JSON and Azure CLI, not PowerShell.
  • Add PowerShell examples for Linux VM images and credentials, or clarify how to adapt for Linux.
  • Ensure Azure CLI and PowerShell examples are equally detailed and placed side-by-side, not with PowerShell first.
  • Explicitly mention cross-platform compatibility and how Linux/macOS users can use Azure CLI or ARM templates.
  • Where possible, avoid Windows-specific credential patterns (e.g., ConvertTo-SecureString) in generic deployment examples.
GitHub Create Pull Request
Virtual Machines Deploy a Premium SSD v2 managed disk ...n/articles/virtual-machines/disks-deploy-premium-v2.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Premium SSD v2 disks, but all CLI and PowerShell examples use Windows VM images (e.g., 'Win2016Datacenter') and Windows-style authentication (username/password). There are no explicit Linux VM deployment examples, and the instructions do not mention or illustrate how to deploy or attach Premium SSD v2 disks to Linux VMs. This may cause confusion or friction for Linux users, who must adapt the examples themselves.
Recommendations
  • Add explicit Linux VM deployment examples in both Azure CLI and PowerShell sections, using a Linux image (e.g., 'UbuntuLTS') and SSH authentication.
  • In variable initialization, show both Windows and Linux image options, or provide a note explaining how to select a Linux image.
  • Include a brief section or note clarifying that Premium SSD v2 disks are fully supported on Linux VMs, and link to Linux-specific disk attachment documentation.
  • Ensure that the 'Next steps' section links to both Linux and Windows disk attachment guides equally.
GitHub Create Pull Request
Virtual Machines Ultra Disks for VMs - Azure Managed Disks ...in/articles/virtual-machines/disks-enable-ultra-ssd.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation is intended for both Linux and Windows VMs, but consistently uses Windows VM images (e.g., Win2016Datacenter) in all CLI and PowerShell examples. There are no examples showing how to deploy Ultra Disks with a Linux VM image, nor any Linux-specific considerations or commands. Windows is always the default in code samples, and the only Quickstart link is for Windows VMs. This creates friction for Linux users, who must adapt the examples themselves.
Recommendations
  • Add parallel examples for Linux VM images (e.g., Ubuntu, CentOS) in CLI and PowerShell sections.
  • Include a Quickstart link for creating a Linux VM in the Azure portal.
  • Explicitly mention that the steps are identical for Linux VMs, and provide sample values for Linux images.
  • Where VM image is specified, show both Windows and Linux image options.
  • Add notes or sections for Linux-specific disk partitioning and formatting guidance.
GitHub Create Pull Request
Virtual Machines Azure Write Accelerator ...es/virtual-machines/how-to-enable-write-accelerator.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation provides extensive PowerShell examples and scripts for enabling Write Accelerator, with detailed step-by-step instructions. Windows-specific tools (Chocolatey, cmd.exe, PowerShell) are mentioned for installing the armclient, and Windows disk/volume managers are referenced before Linux equivalents. While Azure CLI and REST API methods are also documented, the PowerShell approach is given much more prominence and detail, and the installation instructions for armclient are Windows-centric.
Recommendations
  • Provide equivalent Bash shell scripts for Linux users alongside PowerShell examples.
  • Include instructions for installing armclient on Linux (e.g., via npm, direct download, or other package managers) instead of only Chocolatey.
  • Mention Linux disk/volume managers (LVM, MDADM) before or equally with Windows tools in relevant sections.
  • Ensure all CLI and REST API examples are shown with both Windows and Linux command syntax where differences exist.
GitHub Create Pull Request
Virtual Machines Create an encrypted image version with customer-managed keys .../articles/virtual-machines/image-version-encryption.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for creating encrypted image versions with customer-managed keys. However, PowerShell examples are presented first and in greater detail, including more complex scripting for regional encryption sets. The CLI section is present and functional, but PowerShell receives more prominence and depth. There are no Linux-specific command-line examples (e.g., Bash scripting), but the CLI commands are cross-platform. References to Windows tools (e.g., PowerShell) are more frequent, and links to Windows-specific articles appear in prerequisites, though the feature itself is not Windows-only.
Recommendations
  • Present Azure CLI examples before PowerShell, or alternate their order to avoid Windows-first bias.
  • Expand CLI examples to match the complexity and detail of PowerShell examples, including scripting for multiple regions and disks.
  • Add Bash scripting examples for CLI usage to demonstrate Linux-native workflows.
  • Clarify that Azure CLI commands are cross-platform and suitable for Linux/macOS users.
  • Review prerequisite links to ensure parity between PowerShell and CLI/portal guidance.
GitHub Create Pull Request
Virtual Machines Create and upload an Ubuntu Linux VHD in Azure ...rticles/virtual-machines/linux/create-upload-ubuntu.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation, while focused on Ubuntu Linux VHDs, repeatedly references Windows-centric tools and workflows (Hyper-V, PowerShell's Convert-VHD) as primary methods for creating and converting VHDs. Windows/Hyper-V instructions and links are provided first and in detail, while Linux-native alternatives (such as qemu-img or KVM) are not mentioned. This creates friction for Linux/macOS users, who may not have access to Windows tools or environments.
Recommendations
  • Add instructions and examples for creating and converting VHDs using Linux-native tools such as qemu-img, KVM, or VirtualBox.
  • Provide links to Linux-specific guides for disk conversion and VM creation.
  • Ensure that Linux workflows are presented before or alongside Windows/Hyper-V methods, not after.
  • Clarify which steps are platform-agnostic and which are Windows-specific, to help users choose the right path.
GitHub Create Pull Request
Virtual Machines Customer intent: As a cloud architect, I want to understand the limitations of shared disks across different disk types, so that I can effectively design and implement scalable virtual machine solutions in the cloud environment. .../includes/virtual-machines-disks-shared-limitations.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation repeatedly references Windows Server Failover Cluster and links exclusively to Windows Server documentation for clustering requirements. There are no mentions of Linux clustering solutions (e.g., Pacemaker, Corosync), nor are Linux-specific limitations or guidance provided. The proximity placement group link is Windows-focused, and Windows clustering is discussed before any Linux alternatives.
Recommendations
  • Add information about Linux-based clustering solutions (such as Pacemaker/Corosync) and their compatibility or limitations with Azure shared disks.
  • Include links to relevant Linux documentation or Azure guidance for Linux clusters.
  • Clarify if the 'basic disks' limitation applies to Linux clusters, or if it is Windows-specific.
  • Provide parity in examples and guidance for both Windows and Linux users.
GitHub Create Pull Request
Virtual Machines Upload a VHD to Azure or copy a disk across regions - Azure CLI ...machines/linux/disks-upload-vhd-to-managed-disk-cli.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides a Windows-centric example for uploading a VHD using AzCopy, specifically referencing 'AzCopy.exe' and a Windows file path ('c:\somewhere\mydisk.vhd'), without offering a Linux/macOS equivalent. While the rest of the CLI commands are cross-platform, the AzCopy upload step is presented only for Windows, which may confuse or hinder Linux/macOS users. Additionally, the Windows example appears before any mention of Linux usage, and there is no explicit guidance for Linux/macOS users regarding AzCopy usage or file paths.
Recommendations
  • Add a Linux/macOS AzCopy example, using the typical command-line syntax (e.g., './azcopy' or 'azcopy') and a Linux-style file path (e.g., '/home/user/mydisk.vhd').
  • Clarify that AzCopy is cross-platform and provide download/install instructions for Linux/macOS.
  • Mention any OS-specific considerations for AzCopy usage, such as executable naming or permissions.
  • Present both Windows and Linux/macOS examples side-by-side, or note that the command is identical except for path syntax.
GitHub Create Pull Request
Virtual Machines Create an Azure Image Builder Bicep file or ARM template JSON template .../articles/virtual-machines/linux/image-builder-json.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation covers both Linux and Windows VM image creation with Azure Image Builder, providing parity in most areas. However, there are several sections where Windows/PowerShell tools and examples are emphasized or shown first, such as checksum generation (PowerShell cmdlets), restart customizer (Windows only), and validation examples (PowerShell shown before Shell). Windows-specific tools and commands (e.g., PowerShell, Sysprep, shutdown.exe) are referenced more frequently and sometimes before Linux equivalents. Linux instructions are present but occasionally secondary.
Recommendations
  • Where PowerShell is referenced for tasks like checksum generation, add Linux/macOS equivalents (e.g., sha256sum) alongside or before the Windows instructions.
  • For customizer and validator examples, alternate the order so Linux/Shell examples are shown first or equally prominent.
  • Explicitly note Linux limitations (e.g., no Linux restart customizer) and suggest workarounds or alternatives if possible.
  • Ensure all CLI instructions are clearly cross-platform and avoid referencing Windows tools exclusively unless necessary.
  • Where possible, provide links to Linux/macOS documentation for relevant tasks (e.g., file hash generation, script execution).
GitHub Create Pull Request
Virtual Machines Run scripts in a Linux VM in Azure using managed Run Commands ...articles/virtual-machines/linux/run-command-managed.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
While the documentation is focused on Linux VMs and provides extensive Azure CLI examples (which are cross-platform), it exhibits Windows bias in several areas: PowerShell examples are given equal or greater prominence than Azure CLI, and PowerShell-specific tools (e.g., New-AzStorageBlobSASToken) are referenced for generating SAS tokens, with no Linux-native alternatives mentioned. REST API script examples use Windows PowerShell syntax (Write-Host, .ps1), and some example scripts reference Windows conventions (e.g., myscript.ps1) before Linux equivalents (.sh). Additionally, the PowerShell section is more detailed and appears before REST API, and some notes reference Windows-specific behaviors without Linux parity explanations.
Recommendations
  • Provide Bash or Linux-native alternatives for generating SAS tokens (e.g., using Azure CLI or azcopy), not just PowerShell.
  • In REST API and deployment template examples, use .sh scripts and Linux shell commands (e.g., echo) as the primary example, or at least alternate between Windows and Linux script types.
  • Clarify when PowerShell tools are required and offer equivalent Azure CLI or Bash commands for Linux users.
  • Ensure that Linux-specific behaviors (such as parameter passing to .sh scripts) are explained with equal detail as Windows behaviors.
  • Consider placing Azure CLI examples before PowerShell, as CLI is more universally available on Linux/macOS.
GitHub Create Pull Request
Service Fabric Azure Service Fabric container image management .../articles/service-fabric/container-image-management.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page for Azure Service Fabric container image management shows minor Windows bias. Windows container base images (microsoft/windowsservercore, microsoft/nanoserver) are mentioned as default exclusions in cleanup settings, and Windows examples are given first in the 'ContainerImagesToSkip' section. However, Linux images (e.g., docker.io/library/alpine:latest) are also referenced, and the documentation does not restrict the guidance to Windows-only scenarios.
Recommendations
  • Provide explicit examples for Linux container base images (such as Ubuntu, Alpine, or other common Linux distributions) in the 'ContainerImagesToSkip' section.
  • Clarify that the cleanup settings and image management apply equally to both Windows and Linux containers, unless there are platform-specific limitations.
  • Consider mentioning Linux container image patterns alongside Windows examples, or list Linux examples first to balance presentation.
  • Add a note about any differences in image cleanup behavior between Windows and Linux containers, if applicable.
GitHub Create Pull Request
Service Fabric Deny assignment policy for Service Fabric managed clusters ...cles/service-fabric/managed-cluster-deny-assignment.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page provides examples and links for Azure PowerShell before mentioning Azure CLI or sfctl, and the 'Best practices' section highlights PowerShell-based workflows. While Azure CLI and ARM/Bicep tools are listed, PowerShell is emphasized, and no explicit Linux/macOS usage examples are given. This creates mild friction for Linux/macOS users, though all recommended tools (except Service Fabric PowerShell) are cross-platform.
Recommendations
  • Add explicit Azure CLI examples for key operations (e.g., deleting NodeTypes, restarting/reimaging scale sets) alongside PowerShell examples.
  • Clarify that Azure PowerShell and Azure CLI are both cross-platform and provide links to installation/use guides for Linux/macOS.
  • Consider showing Azure CLI examples before or alongside PowerShell examples to avoid Windows-first ordering.
  • Mention sfctl usage for relevant tasks, or clarify its limitations compared to ARM-backed tools.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Docker Compose Deployment Preview ...ticles/service-fabric/service-fabric-docker-compose.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both PowerShell and cross-platform CLI (sfctl) examples for deploying Docker Compose files to Azure Service Fabric. However, PowerShell examples are presented first and in more detail, which may signal a Windows-first bias. The CLI examples (sfctl) are included and are cross-platform, but are listed after PowerShell and with slightly less introductory context.
Recommendations
  • Present CLI (sfctl) examples before PowerShell, or clarify that sfctl is cross-platform and recommended for Linux/macOS users.
  • Explicitly state that sfctl works on all platforms and is the preferred method for non-Windows environments.
  • Ensure that all PowerShell examples have equivalent sfctl commands and vice versa.
  • Consider adding a short section or callout for Linux/macOS users to highlight the cross-platform workflow.
GitHub Create Pull Request
Virtual Machine Scale Sets Configure rolling upgrades on Virtual Machine Scale Sets ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-configure-rolling-upgrades.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring rolling upgrades on Virtual Machine Scale Sets. However, PowerShell examples are consistently presented alongside CLI, and in some sections, PowerShell is shown immediately after CLI. There are no Linux-specific examples (e.g., Bash scripting), but since Azure CLI is cross-platform and the documentation does not reference Windows-only tools or patterns, the bias is minor. The documentation does not mention Linux or macOS users explicitly, nor does it provide parity guidance for those environments.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows.
  • Add Bash shell scripting examples or clarify that CLI commands can be run in Bash on Linux/macOS.
  • Consider including a note for Linux/macOS users about installing Azure CLI and using it in their preferred shell.
  • Ensure PowerShell examples are not presented before CLI, as CLI is more cross-platform.
GitHub Create Pull Request
Virtual Machines Associate a virtual machine to a capacity reservation group .../virtual-machines/capacity-reservation-associate-vm.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation provides both Windows (PowerShell) and cross-platform (Azure CLI, API, Portal) instructions for associating a VM to a capacity reservation group. However, there is a minor bias in the ARM template section, where only Windows VM images are shown by default, and the OSVersion parameter only lists Windows options. In all other sections, Linux is clearly supported and examples (e.g., CLI with Ubuntu image) are present. PowerShell is included as a tab equal to CLI, not prioritized above it.
Recommendations
  • In the ARM template example, add a comment or alternative showing how to deploy a Linux VM (e.g., Ubuntu) by adjusting the imageReference and OSVersion parameters.
  • In the OSVersion parameter, clarify that the template is for Windows VMs, or provide a Linux equivalent parameter and allowedValues.
  • Consider adding a note in the ARM template section that Linux VMs are supported, with a link or snippet for a Linux image example.
GitHub Create Pull Request
Virtual Machines Azure VM Extensions and Features for Linux ...articles/virtual-machines/extensions/features-linux.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples throughout, but consistently presents Azure CLI (Linux-friendly) examples before PowerShell. However, PowerShell examples are always included, even though PowerShell is less commonly used on Linux. There are no Windows-only tools or patterns mentioned, and all examples and screenshots are Linux-specific. The only minor bias is the inclusion of PowerShell examples, which may not be as relevant for Linux users, but this is mitigated by the clear focus on Linux tools and content.
Recommendations
  • Consider clarifying that PowerShell examples are optional for Linux users, or note that Azure CLI is the primary cross-platform tool.
  • Add brief guidance about PowerShell availability on Linux (if relevant), or link to Azure CLI installation instructions for Linux.
  • Ensure that all troubleshooting and reference sections prioritize Linux-native commands and paths.
GitHub Create Pull Request
Virtual Machines Customer intent: As a cloud administrator, I want to expand virtual machine disks efficiently, so that I can manage storage capacity without downtime and ensure optimal performance in my infrastructure. ...al-machines-disks-expand-without-downtime-restrictions.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation mentions both Windows and Linux VM disk rescan procedures, but the Windows rescan function is referenced before the Linux equivalent. All major tools (Azure CLI, PowerShell, Portal) are presented neutrally, but the order of Windows/Linux instructions shows minor Windows-first bias.
Recommendations
  • Present Linux and Windows rescan instructions in parallel or list Linux first to balance visibility.
  • Ensure that links to Linux documentation are as prominent and descriptive as Windows links.
  • Consider adding explicit examples for both Linux and Windows disk expansion/rescan commands.
GitHub Create Pull Request
Virtual Machines Enable Azure Disk Encryption for Linux VMs ...les/virtual-machines/linux/disk-encryption-overview.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation is focused on Linux VMs and provides Linux-centric instructions and examples. However, in several places, Azure PowerShell is mentioned alongside Azure CLI, and PowerShell examples/scripts are referenced equally or before Linux CLI equivalents. The 'Next steps' section lists both CLI and PowerShell quickstarts, with CLI first, but also includes PowerShell scripts. The terminology table includes 'PowerShell cmdlets' as a term, even though the feature is Linux-specific.
Recommendations
  • Ensure that Linux CLI (bash) examples and scripts are always presented before PowerShell equivalents.
  • Clarify that Azure PowerShell can be used cross-platform, but emphasize Linux-native tools (Azure CLI, bash) for Linux VM management.
  • Consider removing or de-emphasizing PowerShell terminology unless it is critical for Linux users.
  • If PowerShell is mentioned, explicitly note its cross-platform nature and relevance for Linux users.
GitHub Create Pull Request
Virtual Machines Expand Virtual Hard Disks on a Linux VM ...b/main/articles/virtual-machines/linux/expand-disks.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ powershell_heavy
Summary
The documentation is overwhelmingly Linux-focused, with detailed instructions and examples for Ubuntu, SUSE, and Red Hat distributions. However, in the section about classic VM SKU support for expanding disks without downtime, only a PowerShell script is provided to check SKU compatibility, with no equivalent Bash/Azure CLI example for Linux users.
Recommendations
  • Add a Bash or Azure CLI example for checking classic VM SKU support, so Linux users can perform the same check without relying on PowerShell.
  • Clarify that the PowerShell script is optional and provide guidance for Linux users on how to access this information via the Azure CLI or portal.
GitHub Create Pull Request
Virtual Machines Time sync for Linux VMs in Azure ...blob/main/articles/virtual-machines/linux/time-sync.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation is focused on Linux VM time synchronization in Azure and provides comprehensive Linux-specific guidance, commands, and configuration examples. However, the introductory section discusses Windows Server 2016 and its time sync improvements before describing Linux mechanisms. References to Windows time service documentation are also given before Linux-specific details. No PowerShell or Windows tool examples are used for Linux configuration, except for a single PowerShell command to base64 encode a cloud-init file for use in an ARM template, which is relevant for cross-platform Azure users. All configuration and troubleshooting examples are Linux-centric.
Recommendations
  • Move the Windows Server 2016 discussion to a background section or as a note, clarifying its relevance to Azure host time only.
  • Prioritize Linux-specific information in the introduction and overview, mentioning Windows host context only as needed.
  • Replace the PowerShell base64 example with a Linux equivalent (e.g., 'base64 cloud-config.txt') or provide both Windows and Linux commands for cross-platform parity.
  • Ensure that all links and references to Windows documentation are clearly marked as background/context and not configuration guidance for Linux users.
GitHub Create Pull Request
Service Fabric Change Azure Service Fabric cluster settings ...rvice-fabric/service-fabric-cluster-fabric-settings.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page provides a comprehensive reference for Service Fabric cluster settings, but exhibits mild Windows bias. Windows-specific terminology, defaults, and tools (such as certificate store names like 'MY', store locations like 'LocalMachine', and references to Windows Defender Firewall) are used throughout. Windows is often mentioned first in settings (e.g., 'ContainerNetworkSetup' defaults to TRUE for Windows, FALSE for Linux), and some parameters (like log file settings for containers) are marked 'Windows only' without Linux equivalents or guidance. There are references to Windows-specific APIs (e.g., CertGetCertificateChain) and settings (e.g., NTLM authentication, Windows Fabric Replicator endpoints), but Linux settings are sometimes present (e.g., 'LinuxExternalExecutablePath', 'X509Folder'). However, Linux-specific guidance and parity are often missing or less detailed.
Recommendations
  • Provide explicit Linux/macOS examples or guidance for settings where Windows defaults or terminology are used (e.g., certificate store names, log file locations, firewall configuration).
  • Where parameters are 'Windows only', clarify Linux equivalents or explicitly state if no equivalent exists.
  • Ensure Linux-specific settings (such as 'LinuxExternalExecutablePath', 'X509Folder') are documented as thoroughly as Windows settings.
  • Add notes or tables summarizing differences in behavior, defaults, or required actions between Windows and Linux clusters.
  • Where Windows APIs or tools are referenced (e.g., CertGetCertificateChain), provide Linux alternatives or clarify applicability.
GitHub Create Pull Request
Virtual Machines Support matrix for VM restore points ...n/articles/virtual-machines/concepts-restore-points.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation presents Windows operating system support before Linux in the 'Operating system support for application consistency' section. However, both Windows and Linux are covered with comparable detail, and no Windows-specific tools, examples, or patterns are prioritized elsewhere. The 'Next steps' section lists CLI, Portal, and PowerShell options, with CLI (cross-platform) listed first.
Recommendations
  • Consider listing Linux and Windows support together or in alphabetical order to avoid implicit prioritization.
  • Ensure future examples and walkthroughs (linked pages) provide parity for Linux and Windows users, especially for CLI and PowerShell usage.
  • Explicitly state that both Windows and Linux are equally supported where applicable.
GitHub Create Pull Request
Service Fabric Overview of Service Fabric and containers ...s/service-fabric/service-fabric-containers-overview.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides a balanced overview of Service Fabric's container support for both Linux and Windows, but there is a slight bias toward Windows. Windows container runtimes and tools are discussed in more detail, and Windows scenarios (such as IIS lift-and-shift) are mentioned first in the 'Scenarios for using containers' section. Windows tutorials and references are often listed before Linux equivalents, and Windows-specific tools (Mirantis Container Runtime, DockerEE) are highlighted.
Recommendations
  • Ensure Linux scenarios are presented with equal prominence to Windows scenarios, such as mentioning NGINX or Apache lift-and-shift alongside IIS.
  • List Linux and Windows tutorials/examples in parallel or alternate their order to avoid Windows-first bias.
  • Provide more detail about Linux container runtimes and tools, such as mentioning containerd or Podman if relevant.
  • Expand Linux-specific use cases and highlight Linux container orchestration patterns where applicable.
GitHub Create Pull Request
Service Fabric Reliable services app manifest examples ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-manifest-example-reliable-services-app.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page for Service Fabric application and service manifest examples shows a mild Windows bias. Batch scripts (.bat), EXE files, and references to Windows user accounts (Administrators, NetworkService) are used in examples, and Windows-specific terminology appears throughout. The only mention of command-line tooling is a reference to the ServiceFabric PowerShell module, with no Linux CLI equivalent. However, the page focuses on XML manifest structure and does not explicitly exclude Linux, nor does it use Windows-only features.
Recommendations
  • Provide Linux-specific examples alongside Windows ones, such as using shell scripts (.sh) instead of only .bat files.
  • Mention cross-platform deployment tools (e.g., Azure CLI, sfctl) in addition to PowerShell.
  • Clarify which user account concepts apply to Linux (e.g., mapping NetworkService to Linux equivalents, or noting limitations).
  • Add notes or examples for running services on Linux Service Fabric clusters, including any differences in manifest usage.
GitHub Create Pull Request
Service Fabric Reliable Collection object serialization ...c-reliable-services-reliable-collections-serialization.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation is generally platform-neutral, focusing on .NET serialization concepts relevant to Azure Service Fabric Reliable Collections. However, in the 'Next steps' section, Windows-centric tools (Visual Studio and PowerShell) are mentioned for application upgrades, with no equivalent Linux/macOS tooling or examples provided. The main content does not reference Windows-specific patterns or tools, but the ordering and selection of upgrade tutorials could create minor friction for non-Windows users.
Recommendations
  • Add links or references to Linux/macOS-compatible upgrade workflows, such as using Azure CLI or REST APIs.
  • Clarify whether PowerShell examples are cross-platform (PowerShell Core) or Windows-only.
  • Consider mentioning cross-platform development environments (e.g., VS Code, CLI) alongside Visual Studio.
  • Explicitly state if certain tools are Windows-only, and provide alternatives for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Learn Azure Service Fabric terminology ...es/service-fabric/service-fabric-technical-overview.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation page contains several instances of Windows-centric terminology and examples, such as referencing Windows services (FabricHost.exe), EXE/DLL files, and Windows-specific containers. Windows tools and patterns are mentioned first or exclusively in some sections, with Linux equivalents referenced later or less prominently. However, Linux support is acknowledged, and most concepts are described in a cross-platform manner.
Recommendations
  • Clarify when features or terminology are Windows-specific versus cross-platform.
  • Provide Linux-specific examples and terminology alongside Windows examples (e.g., mention Linux service management, file types, and container support equally).
  • Avoid referencing Windows executables (EXE/DLL) exclusively; mention Linux binaries or scripts where relevant.
  • Ensure that descriptions of cluster nodes and services do not imply Windows-only operation unless the feature is truly Windows-specific.
  • Add explicit Linux/macOS parity notes for development clusters and guest executables.
GitHub Create Pull Request
Virtual Machine Scale Sets Migrate deployments and resources to Virtual Machine Scale Sets in Flexible orchestration ...lexible-virtual-machine-scale-sets-migration-resources.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides some Windows-specific scenarios (e.g., Windows VM activation, Windows updates) before mentioning Linux equivalents (e.g., Linux package manager access). There are no explicit Linux-focused migration examples, commands, or troubleshooting links. Azure CLI is referenced, but no Linux-specific shell or command examples are given. The overall guidance is generic, but Windows scenarios are mentioned first and more prominently.
Recommendations
  • Add explicit Linux migration scenarios and troubleshooting links (e.g., guidance for Linux VM updates, package manager outbound connectivity).
  • Provide Linux-specific command examples or references (e.g., Bash shell, Linux CLI usage).
  • Ensure Linux scenarios (such as package manager access) are mentioned alongside or before Windows scenarios where relevant.
  • Include links to Linux documentation for Azure VM activation, updates, and outbound connectivity.
  • Balance the order and prominence of Windows and Linux scenarios in outbound connectivity and migration sections.
GitHub Create Pull Request
Virtual Machine Scale Sets Enable Automatic Zone Balance on Virtual Machine Scale Sets (Preview) ...virtual-machine-scale-sets/auto-zone-balance-enable.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation provides both Azure CLI (cross-platform) and PowerShell (Windows-centric) examples for all major operations. However, PowerShell examples are consistently presented after CLI, and both are given equal prominence. There are no Linux-specific shell (bash) or scripting examples, but the CLI examples use Linux images and Application Health extensions for Linux, which helps parity. The PowerShell examples use the ApplicationHealthWindows extension, which could confuse Linux users. There are no references to Windows-only tools, but PowerShell is a Windows-first automation tool. No critical steps are Windows-only, and all tasks can be completed with CLI or REST API.
Recommendations
  • Clarify in PowerShell examples when the ApplicationHealthWindows extension is used, and provide a Linux equivalent (ApplicationHealthLinux) if the VMSS is Linux-based.
  • Add a short note at the start of each section explaining that Azure CLI is cross-platform and recommended for Linux/macOS users.
  • Consider including bash script snippets for common tasks to further improve Linux parity.
  • In PowerShell examples, explicitly mention that PowerShell Core is available cross-platform, or clarify if examples are only for Windows.
  • Ensure that the documentation does not default to Windows-centric extension types (like ApplicationHealthWindows) in generic examples.
GitHub Create Pull Request
Virtual Machine Scale Sets Attach or detach a virtual machine to or from a Virtual Machine Scale Set ...le-sets/virtual-machine-scale-sets-attach-detach-vm.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides examples for Azure Portal, Azure CLI, and Azure PowerShell in all major sections. However, in each case, the Azure PowerShell (a Windows-centric tool) example is always presented, and sometimes appears before or at parity with Azure CLI. While Azure CLI is cross-platform and shown in all cases, PowerShell is not as commonly used on Linux/macOS. There are no explicit Linux/macOS-specific instructions or notes, but the CLI examples use Ubuntu images, indicating some Linux awareness. The order of examples (Portal, CLI, then PowerShell) is generally neutral, but the presence of PowerShell in all cases may create a slight perception of Windows bias.
Recommendations
  • Clearly indicate that Azure CLI is cross-platform and preferred for Linux/macOS users, perhaps with a short note at the start of CLI sections.
  • Optionally, add a brief note in PowerShell sections that PowerShell Core is available cross-platform, but is less common on Linux/macOS.
  • Consider providing Bash shell script examples for common operations, or clarifying that Azure CLI commands are intended for Bash/Unix shells as well as Windows.
  • If possible, add a small section or callout for Linux/macOS users, confirming that all operations are supported equally on those platforms via Azure CLI.
GitHub Create Pull Request
Virtual Machine Scale Sets Networking for Azure Virtual Machine Scale Sets ...ne-scale-sets/virtual-machine-scale-sets-networking.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for most tasks, but PowerShell examples are often presented before CLI examples, and some sections (e.g., querying public IPs) show PowerShell commands before CLI. Portal instructions are also included, but there is a slight tendency to present Windows/PowerShell patterns first. All features are cross-platform and Linux parity is generally maintained, but minor ordering bias exists.
Recommendations
  • Present Azure CLI examples before PowerShell examples, or side-by-side, to emphasize cross-platform support.
  • Ensure that CLI and PowerShell examples are equally detailed and prominent.
  • Where possible, clarify that PowerShell examples work on both Windows and Linux (via PowerShell Core), but CLI is native to Linux/macOS.
  • Add explicit statements that all features and examples are applicable to both Linux and Windows VMSS unless otherwise noted.
GitHub Create Pull Request
Virtual Machine Scale Sets Custom metrics for rolling upgrades on Virtual Machine Scale Sets ...tual-machine-scale-sets-rolling-upgrade-custom-metrics.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Linux (Bash/Python) and Windows (PowerShell) examples for configuring the application health extension response and for managing VMSS extensions. However, in several places, Windows/PowerShell examples are presented before or alongside Linux equivalents, and the PowerShell section is notably detailed. The REST and Azure CLI examples are platform-neutral, but the PowerShell examples are prominent and sometimes shown before Bash/Linux. The extension installation section uses 'ApplicationHealthLinux' and 'ApplicationHealthWindows' types, but the PowerShell example defaults to 'ApplicationHealthWindows'.
Recommendations
  • Ensure Linux/Bash examples are presented before or equally with Windows/PowerShell examples in each section.
  • In PowerShell examples, clarify how to use 'ApplicationHealthLinux' for Linux VMSS instances.
  • Add explicit notes or guidance for macOS users where relevant (e.g., Bash examples).
  • Where possible, provide parity in troubleshooting steps for both Windows and Linux environments.
  • Consider adding a table or summary showing which commands/tools are available for each OS.
GitHub Create Pull Request
Virtual Machine Scale Sets Rolling upgrades with MaxSurge for Virtual Machine Scale Sets ...hine-scale-sets/virtual-machine-scale-sets-maxsurge.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides configuration examples for rolling upgrades with MaxSurge using Azure Portal, Azure CLI, PowerShell, and ARM Template. While the CLI and ARM Template examples are cross-platform, the PowerShell example is Windows-specific and is presented equally alongside CLI. The CLI example is shown before PowerShell, but both are given equal prominence. There are no exclusive Windows tools or patterns mentioned, and Linux users can complete all tasks using the CLI or ARM Template. However, the inclusion of PowerShell as a primary example may create minor friction for Linux/macOS users.
Recommendations
  • Clarify that Azure CLI is cross-platform and recommended for Linux/macOS users.
  • Add explicit notes indicating PowerShell is Windows-centric and suggest CLI for non-Windows environments.
  • Consider including Bash shell scripting examples for Linux users, if relevant.
  • Ensure parity in example coverage and ordering, with CLI examples shown first and PowerShell as an alternative.
GitHub Create Pull Request
Virtual Machine Scale Sets Orchestration modes for Virtual Machine Scale Sets in Azure ...sets/virtual-machine-scale-sets-orchestration-modes.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation provides a conceptual overview of orchestration modes for Azure Virtual Machine Scale Sets and is largely platform-neutral. However, there is a minor instance of Windows bias: in the 'Managed Identity' row of the comparison table, the link for configuring user-assigned managed identity points to a Windows VMSS-specific guide, even though Flexible orchestration supports both Linux and Windows VMs. Additionally, the Azure Site Recovery feature is noted as 'Yes (via PowerShell)' for Flexible orchestration, which may imply Windows-centric tooling, though PowerShell is cross-platform. All CLI/API examples use Azure CLI, which is cross-platform, and Linux is explicitly mentioned as supported throughout.
Recommendations
  • Update managed identity documentation links to reference both Linux and Windows guides, or a platform-neutral guide.
  • Clarify that Azure Site Recovery via PowerShell is available on Linux/macOS as well, or provide Bash/Azure CLI alternatives if possible.
  • Ensure that any referenced extension or tooling is described as available for both Linux and Windows, or provide links to Linux-specific documentation where relevant.
GitHub Create Pull Request
Virtual Machines Customer intent: "As a cloud architect, I want to develop a robust backup and disaster recovery strategy for my Azure VMs and their managed disks, so that my organization can ensure data availability and minimize downtime during outages or data loss incidents." ...s/backup-and-disaster-recovery-for-azure-iaas-disks.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides a balanced overview of backup and disaster recovery strategies for Azure Managed Disks, explicitly stating applicability to both Linux and Windows VMs. However, in several sections, Windows-specific tools and patterns (such as Volume Shadow Service for application-consistent backups and SQL Server Always On) are mentioned first or exclusively, with Linux equivalents (like fsfreeze) referenced later and with less detail. Some backup consistency options are described in more depth for Windows, and Windows examples (e.g., SQL Server) are more prominent than Linux database solutions.
Recommendations
  • Provide equal detail for Linux tools and patterns (e.g., expand on fsfreeze and other Linux application-consistent backup options).
  • Include Linux-first or Linux-specific examples alongside Windows examples, such as PostgreSQL or MySQL backup strategies.
  • When mentioning Windows tools (e.g., Volume Shadow Service), immediately follow with Linux equivalents and clarify their limitations or strengths.
  • Ensure comparison tables and scenario descriptions highlight Linux and Windows parity, including file system and application consistency for both platforms.
GitHub Create Pull Request
Virtual Machines Best practices for virtual machine cost optimization ...s/virtual-machines/cost-optimization-best-practices.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation provides general best practices for virtual machine cost optimization and references both Windows and Linux VM pricing. However, there is a minor bias where Windows examples and recommendations (such as 'Use at least B2 for Windows machines' and Windows pricing links) are mentioned before Linux equivalents. There are no PowerShell-heavy examples, Windows-only tools, or missing Linux examples for general VM operations. The page is not Windows-specific and covers both OS types.
Recommendations
  • When mentioning VM sizing recommendations, provide equivalent guidance for Linux VMs (e.g., 'Use at least B2 for Windows machines; for Linux, review minimum recommended sizes').
  • Ensure that links to pricing and VM sizes for both Windows and Linux are presented together or in parallel, rather than Windows first.
  • Where automation or shutdown examples are given, clarify that these apply to both Windows and Linux VMs, and provide links to relevant Linux automation documentation if available.
GitHub Create Pull Request
Virtual Machines Server-side encryption of Azure Managed Disks ...blob/main/articles/virtual-machines/disk-encryption.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation covers both Linux and Windows VM scenarios and explicitly states applicability to both. However, throughout the page, Windows/PowerShell examples and links are consistently listed before Linux/CLI equivalents. References to PowerShell are frequent, sometimes with CLI mentioned second. There are no missing Linux examples or exclusive Windows tools; parity is maintained, but Windows is prioritized in ordering.
Recommendations
  • Alternate the order of Windows and Linux examples/links, or list Linux/CLI first in some sections.
  • Ensure that references to PowerShell and CLI are equally prominent, and avoid always listing PowerShell first.
  • Consider adding explicit Linux/macOS command-line snippets or screenshots where relevant.
  • Review for any subtle language that implies Windows is the default or primary platform.
GitHub Create Pull Request
Virtual Machines Migrate Standard HDD OS disks by September 08, 2028 ...n/articles/virtual-machines/disks-hdd-os-retirement.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation covers both Linux and Windows VMs, and provides Azure CLI and PowerShell examples for listing affected disks. However, the PowerShell example is presented before the Azure CLI example, which is a minor 'windows_first' bias. Both tools are mentioned, and the Disk Storage Center is a web portal, not Windows-specific. No critical Windows-only tools or missing Linux examples are found.
Recommendations
  • Present Azure CLI and PowerShell examples in parallel or list Azure CLI first, as it is cross-platform.
  • Explicitly note that Azure CLI works on Linux/macOS/Windows, while PowerShell is primarily Windows-focused.
  • Consider adding Bash script examples for Linux users, if relevant.
GitHub Create Pull Request
Virtual Machines Secure Azure Managed Disk Downloads and Uploads ...icles/virtual-machines/disks-secure-upload-download.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for most operations, but PowerShell examples are often presented before CLI (which is more cross-platform). References to the portal and PowerShell are frequent, and PowerShell is sometimes highlighted more prominently. However, Linux parity is generally maintained, especially in the 'Next steps' section, which includes both Linux and Windows links.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and more accessible to Linux/macOS users.
  • Explicitly mention that Azure CLI commands work on Linux/macOS, and provide Bash shell examples where relevant.
  • Where PowerShell is referenced, clarify if it is available cross-platform (PowerShell Core), or provide alternatives for Linux users.
  • Ensure screenshots and portal instructions are not Windows-centric (e.g., avoid showing Windows UI elements unless necessary).
GitHub Create Pull Request
Virtual Machines Instantly access managed disk snapshots ...les/virtual-machines/disks-instant-access-snapshots.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for creating instant access snapshots, but PowerShell (a Windows-centric tool) is given equal prominence. Azure CLI is cross-platform, but there are no explicit Linux/macOS-specific instructions or notes. The ordering of examples sometimes puts PowerShell before CLI, and there are no references to Linux-native scripting or shell environments. However, the CLI examples are sufficient for Linux users, and no critical tasks are Windows-only.
Recommendations
  • Always present Azure CLI examples before PowerShell to emphasize cross-platform parity.
  • Explicitly state that Azure CLI commands work on Linux/macOS and Windows, and provide any relevant shell-specific notes (e.g., quoting, environment variables).
  • Consider adding a note for Linux/macOS users about installing Azure CLI and running the commands in bash/zsh.
  • If possible, provide bash script examples or highlight any OS-specific considerations for disk snapshot operations.
GitHub Create Pull Request
Virtual Machines Restrict managed disks from being imported or exported ...tual-machines/disks-restrict-import-export-overview.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page provides both Azure CLI and PowerShell options for configuring disk restrictions, but PowerShell is mentioned first and linked more prominently. The custom RBAC role section links only to a PowerShell-based guide, and PowerShell is referenced before CLI in the NetworkAccessPolicy section. Linux-specific examples and parity are present but less emphasized.
Recommendations
  • Add links to Azure CLI guides for creating custom RBAC roles, not just PowerShell.
  • Present CLI and PowerShell options equally, or list CLI first to better support Linux/macOS users.
  • Ensure all sections referencing PowerShell also reference CLI equivalents.
  • Include explicit Linux/macOS instructions or examples where possible.
GitHub Create Pull Request
Virtual Machines What's new in Azure Disk Storage ...blob/main/articles/virtual-machines/disks-whats-new.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation is generally neutral and focused on Azure Disk Storage features, but there are a few subtle signs of Windows bias. Some links and references point to Windows-specific documentation first or exclusively (e.g., expand disks links, unattached disks documentation), and Windows tools (Azure PowerShell) are mentioned alongside Azure CLI, but Linux equivalents are not always given equal prominence. In a few cases, Linux documentation is referenced, but often after Windows or not at all.
Recommendations
  • Ensure that all feature links referencing disk operations (such as expanding disks, finding unattached disks) include both Windows and Linux documentation, ideally side-by-side or with equal prominence.
  • When mentioning Azure PowerShell, also mention Azure CLI and Bash where appropriate, and clarify cross-platform support.
  • Review linked articles to ensure Linux/macOS parity in examples and instructions.
  • Avoid referencing Windows documentation first when the feature is cross-platform; alternate or combine links for Windows and Linux.
  • Add explicit statements about Linux/macOS support for features where relevant.
GitHub Create Pull Request
Virtual Machines Ephemeral OS disks ...b/main/articles/virtual-machines/ephemeral-os-disks.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ minor_powershell_reference
Summary
The documentation covers ephemeral OS disks for both Linux and Windows VMs, with clear applicability to both platforms. Examples and guidance are provided for both OS types, and VM size recommendations are given for Ubuntu (Linux) and Windows Server images. However, there are minor instances of Windows bias: Windows Server image sizing is mentioned first in the 'Size requirements' section, and PowerShell is referenced before CLI in the 'Customer Managed key' section. These are minor ordering biases and do not impact the ability of Linux/macOS users to follow the documentation.
Recommendations
  • Alternate the order of Linux and Windows examples in sections where both are relevant, or present them side-by-side.
  • When referencing tooling, mention Azure CLI and PowerShell together, or list CLI first for Linux parity.
  • Ensure that all critical steps and examples are available for both Linux and Windows users, especially in linked deployment guides.
GitHub Create Pull Request
Virtual Machines Azure Key Vault VM Extension for Linux ...rticles/virtual-machines/extensions/key-vault-linux.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation is focused on the Azure Key Vault VM Extension for Linux and provides Linux-specific guidance throughout. However, in several sections, Windows-oriented tools (Azure PowerShell) are presented first or in greater detail than their Linux equivalents (Azure CLI). PowerShell deployment instructions and troubleshooting commands are shown before CLI, and PowerShell-specific warnings are included. There are no missing Linux examples, but the ordering and emphasis may create friction for Linux users.
Recommendations
  • Present Azure CLI examples before Azure PowerShell examples, as CLI is cross-platform and native to Linux/macOS.
  • Add explicit notes clarifying that PowerShell is not required for Linux users and that Azure CLI is the preferred tool for Linux/macOS.
  • Ensure troubleshooting commands are shown with Azure CLI first, and PowerShell only as an alternative.
  • Remove or minimize PowerShell-specific warnings unless they are relevant to Linux users.
  • Consider adding a brief section on using Bash scripts or other Linux-native automation tools for deployment, if applicable.
GitHub Create Pull Request
Virtual Machines NVIDIA GPU Driver Extension - Azure Linux VMs ...es/virtual-machines/extensions/hpccompute-gpu-linux.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation is focused on Linux VM GPU driver installation, but includes PowerShell examples alongside Azure CLI and ARM template examples. The PowerShell example is presented before the Azure CLI example, which is more relevant for Linux users. There are references to Windows extensions, but these are clearly separated and not the main focus. No Linux example is missing, and Linux-specific tools and commands are well represented.
Recommendations
  • Move the Azure CLI example before the PowerShell example to prioritize Linux-relevant tooling.
  • Clarify that PowerShell is primarily for users on Windows or those using Azure Cloud Shell, and recommend Azure CLI for Linux users.
  • Consider adding Bash shell script examples for common deployment scenarios, as Bash is native to Linux.
  • Explicitly note that PowerShell examples are optional for Linux users and not required.
GitHub Create Pull Request
Virtual Machines Deprovision or generalize a VM before creating an image ...docs/blob/main/articles/virtual-machines/generalize.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation covers both Linux and Windows VM generalization, but Windows examples and prerequisites are more detailed and are presented after Linux, with Windows-specific tools (Sysprep, PowerShell) used. The Windows section includes registry edits, role checks, and encryption steps, while the Linux section is simpler and relies on waagent. The Azure CLI is used for Linux, but PowerShell is used for Windows, with no Azure CLI equivalent shown for Windows. Overall, both platforms are covered, but Windows examples are more tool-specific and detailed.
Recommendations
  • Provide Azure CLI examples for generalizing Windows VMs, not just PowerShell.
  • Ensure parity in detail: add more troubleshooting and validation steps for Linux, similar to Windows.
  • Consider showing Linux and Windows sections in parallel or with equal prominence.
  • Add a note clarifying that both Azure CLI and PowerShell can be used for either OS where applicable.
GitHub Create Pull Request
Virtual Machines Customer intent: As a cloud administrator, I want to benchmark disk performance using custom I/O workloads, so that I can optimize storage configurations for maximum read and write IOPS in my virtual machines. ...ncludes/virtual-machines-managed-disks-benchmarking.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation presents benchmarking instructions for both Windows (DISKSPD) and Linux (FIO), but the Windows section appears first and is more detailed in its parameter explanations. Both platforms are covered with clear examples and screenshots, but Windows tools and examples are prioritized in order of presentation.
Recommendations
  • Consider presenting Linux (FIO) and Windows (DISKSPD) sections in parallel or alternating order, or explicitly state that both tools are equally supported.
  • Add a brief introductory note clarifying that both Windows and Linux are fully supported for disk benchmarking, and that the order of examples does not imply preference.
  • Ensure parameter explanations and example depth are consistent across both Windows and Linux sections.
  • If possible, provide a summary table comparing DISKSPD and FIO usage for common scenarios.
GitHub Create Pull Request
Virtual Machines Create an image definition and image version ...s/blob/main/articles/virtual-machines/image-version.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides both Linux and Windows guidance, but there is a notable Windows bias in several areas. PowerShell examples are prominent and often shown before or alongside CLI examples. Windows-specific tools (Sysprep, PowerShell) are referenced, sometimes before Linux equivalents. In the PowerShell section, Windows is the default in the example, with Linux only mentioned as an alternative. However, Linux parity is generally maintained, and CLI and REST examples are provided for both OS types.
Recommendations
  • Ensure Linux and Windows examples are equally represented and alternated in order of appearance.
  • In PowerShell sections, provide explicit Linux examples (e.g., -OsType Linux) rather than only mentioning it as an alternative.
  • Where Windows tools are referenced (e.g., Sysprep), ensure Linux equivalents (e.g., waagent -deprovision) are mentioned with equal prominence.
  • Consider starting with a neutral or Linux example in code blocks, or alternate the default OS type in examples.
  • Add explicit notes clarifying that all steps are applicable to both Linux and Windows unless otherwise stated.
GitHub Create Pull Request
Virtual Machines Azure Disk Encryption scenarios on Linux VMs ...ticles/virtual-machines/linux/disk-encryption-linux.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all major operations, but PowerShell (a Windows-centric tool) is given equal prominence throughout, including detailed scripts and explanations. PowerShell cmdlets are referenced frequently and sometimes before CLI equivalents. The documentation also refers to using PowerShell sessions on local machines, which is a Windows-native pattern, though PowerShell Core is cross-platform. There are no missing Linux examples, but the heavy use of PowerShell and its prominence may create friction for Linux users who prefer native Bash or CLI workflows.
Recommendations
  • Make clear that Azure PowerShell is cross-platform, but highlight Azure CLI as the default for Linux users.
  • Consider showing Azure CLI examples first in each section, as CLI is more native to Linux environments.
  • Add brief Bash scripting examples for common tasks (e.g., mounting disks, preparing VHDs) where relevant.
  • Clarify that PowerShell scripts can be run on Linux/macOS with PowerShell Core, but CLI is often simpler.
  • Reduce references to 'PowerShell session' and instead use 'terminal session' or 'shell session' for Linux contexts.
GitHub Create Pull Request
Virtual Machines Verify encryption status for Linux - Azure Disk Encryption ...tual-machines/linux/how-to-verify-encryption-status.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for verifying disk encryption status on Linux VMs, but the PowerShell section is presented before the Azure CLI section and contains more detailed, step-by-step examples. This may create friction for Linux users, as PowerShell is not the default scripting environment on most Linux distributions. However, Azure CLI examples are present and comprehensive, and OS-level Linux commands are included.
Recommendations
  • Move the Azure CLI section before the PowerShell section to prioritize Linux-native tooling.
  • Ensure all PowerShell examples have equivalent Azure CLI examples, matching detail and coverage.
  • Explicitly note that PowerShell commands are optional and primarily for users who prefer PowerShell or are working cross-platform.
  • Expand OS-level Linux command examples (e.g., using 'lsblk', 'cryptsetup') to cover more scenarios, such as checking encryption status for multiple disks or partitions.
  • Add a short introductory note clarifying that Azure CLI and Bash are the recommended tools for Linux users.
GitHub Create Pull Request
Virtual Machines Create and upload a Red Hat Enterprise Linux VHD for use in Azure ...les/virtual-machines/linux/redhat-create-upload-vhd.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides detailed instructions for preparing and uploading a Red Hat Enterprise Linux VHD for Azure, covering multiple hypervisors (Hyper-V, KVM, VMware, Kickstart). However, throughout the document, Windows tools and patterns (such as Hyper-V Manager and PowerShell cmdlets) are often mentioned first or exclusively in key steps, especially for disk conversion and VM creation. Linux alternatives are present, but Windows-centric approaches (e.g., Hyper-V Manager, convert-vhd cmdlet) are prioritized or referenced before Linux-native tools (e.g., qemu-img, KVM).
Recommendations
  • Present Linux-native tools and procedures (such as qemu-img, KVM, VMware) before or alongside Windows/Hyper-V tools, especially in sections about disk conversion and VM creation.
  • Where Windows tools (e.g., Hyper-V Manager, convert-vhd) are mentioned, immediately provide equivalent Linux commands and workflows, not just as secondary options.
  • Clarify that Linux users can complete all steps without access to Windows or Hyper-V, and highlight Linux-only workflows in the introduction and summary.
  • Consider adding a summary table or flowchart that shows parity between Windows and Linux approaches for each major step.
  • Avoid referencing Windows/PowerShell tools as the default or primary method unless the majority of users are expected to use them.
GitHub Create Pull Request
Virtual Machines Overview of Azure Disk Storage ...in/articles/virtual-machines/managed-disks-overview.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ minor_windows_reference
Summary
The documentation is generally cross-platform and explicitly states applicability to both Linux and Windows VMs. However, there are minor instances of Windows bias: Windows terminology and links are sometimes presented first, Windows-specific tools (PowerShell) are referenced alongside Linux tools (CLI), and Windows partitioning concepts (MBR/GPT) are discussed in detail with Windows-centric links. The temporary disk section references Windows drive letters before Linux device paths. These biases are minor and do not prevent Linux/macOS users from completing tasks or understanding features.
Recommendations
  • Ensure Linux and Windows examples/tools are presented together or alternate their order.
  • Where partitioning concepts are discussed, include links to Linux equivalents (e.g., Linux partitioning guides, GPT/MBR on Linux).
  • When referencing disk paths, mention Linux device paths before or alongside Windows drive letters.
  • Add links to Linux-specific documentation where only Windows links are provided, such as for disk conversion or partitioning.
GitHub Create Pull Request
Virtual Machines Migrate from Amazon Elastic Compute Cloud (Amazon EC2) to Azure Virtual Machines ...ion/migrate-from-elastic-compute-cloud-architecture.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides general migration guidance from Amazon EC2 to Azure Virtual Machines, covering compute, storage, networking, and images. While it mentions both Windows and Linux operating systems, there are subtle signs of Windows bias: Windows-specific tools (Sysprep) are mentioned before Linux equivalents, and some example patterns (such as image generalization) are described in a Windows-first manner. There are no explicit Linux command-line examples (e.g., Bash, Linux CLI), and PowerShell or Windows-centric terminology appears slightly more frequently. However, the overall guidance is mostly platform-neutral and does not prevent Linux users from completing the migration.
Recommendations
  • Provide Linux-specific examples and CLI commands alongside Windows/PowerShell examples, especially in sections about image capture, agent installation, and storage migration.
  • Mention Linux tools (such as waagent, cloud-init, and relevant configuration management tools) with equal prominence to Windows tools like Sysprep.
  • Ensure that migration steps and validation guidance include Linux-specific considerations, such as SELinux/AppArmor, systemd, and Linux networking nuances.
  • Add explicit Bash or Linux CLI snippets for tasks like copying files, installing agents, or benchmarking performance.
  • Review the order of presentation to avoid Windows-first bias in listing tools or procedures.
GitHub Create Pull Request