← Back to Dashboard
268
Pages Scanned
88
Pages Flagged
268
Changed Pages
32.8%
% Pages Flagged

Scan Information

Started At: 2026-02-09 00:00:07

Finished At: 2026-02-10 18:44:36

Status: completed

Target Repo: Azure Compute

Current Phase: discovery

Files Queued: 268

Files Completed: 268

Problematic Pages

88 issues found
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
The documentation page initially states that Service Fabric clusters can run on Windows Server and Linux, but later clarifies that Linux isn't yet supported for standalone clusters. Most examples and security options focus on Windows-specific features, and the supported OS list is exclusively Windows. There are no Linux-specific instructions, examples, or parity notes.
Recommendations
  • Clarify at the top that standalone clusters are currently Windows-only, despite initial mention of Linux.
  • Remove or update the description to avoid implying Linux support where it does not exist.
  • Add a section or note about Linux support roadmap or alternatives for Linux users.
  • If Linux support is planned, provide guidance or links for Linux users to relevant documentation or preview features.
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 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 workarounds provided, and the feature is unavailable on Linux, creating a significant platform disparity.
Recommendations
  • Clearly state at the top that the reverse proxy feature is Windows-only, and link to any Linux alternatives or roadmap if available.
  • Provide guidance or links for Linux users on how to achieve similar functionality, or clarify that Linux clusters must use different patterns.
  • If the feature becomes available for Linux in the future, add Linux-specific examples, configuration steps, and troubleshooting guidance.
GitHub Create Pull Request
Service Fabric Configure the upgrade of a Service Fabric application ...abric/service-fabric-visualstudio-configure-upgrade.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example ⚠️ windows_first
Summary
The documentation page focuses exclusively on upgrading Service Fabric applications using Visual Studio and PowerShell, both Windows-centric tools. All examples and instructions reference Visual Studio dialogs and PowerShell cmdlets, with no mention of Linux/macOS alternatives or cross-platform CLI tools. There are no examples or guidance for Linux users, and Windows tools are presented first and exclusively.
Recommendations
  • Add instructions for upgrading Service Fabric applications using Azure CLI or REST API, which are cross-platform.
  • Include examples for Linux/macOS environments, such as using Bash or cross-platform tools instead of PowerShell.
  • Clarify whether Visual Studio and PowerShell are required, or if there are alternative workflows for non-Windows users.
  • Provide links to documentation for Linux-compatible Service Fabric management tools.
GitHub Create Pull Request
Service Fabric Initializer CodePackages in Service Fabric ...in/articles/service-fabric/initializer-codepackages.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation page provides examples and guidance exclusively for Windows containers in Service Fabric, including Windows-specific container images, file paths, and commands. No Linux container examples, Linux file paths, or Linux command syntax are provided, and the page assumes familiarity with Windows container workflows. This creates friction for Linux users wishing to use Initializer CodePackages with Linux containers.
Recommendations
  • Add parallel examples for Linux containers, including Linux-based container images (e.g., Ubuntu, Alpine) and Linux command syntax (e.g., bash, sh).
  • Show Linux file paths and volume mounts (e.g., /workspace/log.txt) alongside Windows paths.
  • Clarify whether Initializer CodePackages are supported for Linux containers and, if so, provide guidance and examples.
  • If Initializer CodePackages are Windows-only, explicitly state this early in the documentation.
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: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation page provides several PowerShell-based instructions (e.g., using Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState) for cluster scaling operations, but does not offer equivalent Linux/CLI/bash examples or guidance. This creates friction for Linux users, who may not have access to PowerShell or may prefer bash/CLI tools. The documentation also references Windows-centric tools and patterns without mentioning Linux alternatives.
Recommendations
  • For every PowerShell command or workflow, provide equivalent Azure CLI, bash, or REST API examples suitable for Linux/macOS users.
  • Explicitly mention if certain commands are only available on Windows, and provide alternative approaches for Linux clusters (e.g., using Service Fabric CLI (sfctl), Azure CLI, or REST API).
  • Add a section or callout for Linux users, summarizing the recommended tools and commands for common scaling operations.
  • Ensure that code snippets and step-by-step instructions are platform-agnostic or include both Windows and Linux variants where possible.
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 page for Azure Service Fabric architecture mentions PowerShell cmdlets as a primary management interface and references Windows security as a transport option. PowerShell is a Windows-centric tool, and its mention as the first or only example for management tasks suggests a Windows-first bias. There are no explicit Linux management examples or references to Linux-native tools (e.g., Bash, CLI), which may create friction for Linux/macOS users.
Recommendations
  • Add examples or references to Azure CLI or Bash scripts for management tasks alongside PowerShell.
  • Clarify whether management APIs and tools are cross-platform, and provide guidance for Linux/macOS users.
  • Mention Linux security mechanisms (e.g., certificate-based authentication) in the transport subsystem section, not just Windows security.
  • Consider providing links to Linux-specific documentation or guides for Service Fabric management.
GitHub Create Pull Request
Service Fabric Deny assignment policy for Service Fabric managed clusters ...cles/service-fabric/managed-cluster-deny-assignment.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides examples and links primarily for Azure PowerShell modules, with PowerShell-based tools mentioned before Azure CLI and sfctl. While Azure PowerShell is cross-platform, its usage and prominence may create friction for Linux/macOS users who typically prefer CLI or native tools. The 'Best practices' section highlights PowerShell commands first and provides links to PowerShell modules before CLI equivalents.
Recommendations
  • Provide Azure CLI examples alongside PowerShell examples, especially for key operations like deleting NodeTypes or restarting/reimaging scale sets.
  • List Azure CLI and sfctl tools before or equally with PowerShell in tool tables and best practices.
  • Clarify that Azure PowerShell is cross-platform, but offer parity in examples for CLI and sfctl.
  • Add explicit Linux/macOS guidance or callouts where workflows differ.
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 examples for key security tasks, but Windows-specific tools (PowerShell, Windows Defender, DSC) are mentioned first or exclusively in several sections. Windows-centric terminology and recommendations (e.g., Windows Defender, DSC, security baselines) are prominent, and PowerShell commands are presented before Linux equivalents. Some sections (Windows Defender, DSC, Windows security baselines) are Windows-only by nature, but Linux alternatives or clarifications are not always provided.
Recommendations
  • Ensure Linux examples are presented alongside Windows examples, not after them, and consider alternating order.
  • Where Windows-specific tools are discussed (e.g., Windows Defender, DSC), explicitly mention Linux alternatives or clarify their absence.
  • Add references to Linux security baselines (e.g., CIS benchmarks) and tools (e.g., SELinux, AppArmor) where relevant.
  • For sections with PowerShell-heavy examples, provide equivalent Bash/CLI commands for Linux clusters.
  • Clarify when a feature or recommendation is Windows-only, and provide guidance for Linux users where possible.
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 for the Service Fabric application lifecycle consistently references PowerShell cmdlets and Windows-centric tooling (e.g., PowerShell commands, .NET APIs) as primary examples for operational tasks such as deployment, upgrade, removal, and cleanup. REST API alternatives are mentioned, but PowerShell is often listed first and is the only shell scripting example provided. There is minimal mention of Linux-specific tools or workflows, and no CLI (sfctl or Azure CLI) command examples are shown directly in the main lifecycle sections, despite a link to CLI documentation.
Recommendations
  • Add explicit examples using Service Fabric CLI (sfctl) and Azure CLI for each lifecycle operation, alongside PowerShell and .NET examples.
  • Ensure CLI and REST API options are presented before or equally with PowerShell cmdlets, especially in introductory or summary lists.
  • Include Linux/macOS-friendly shell scripting examples where PowerShell is used, or reference equivalent bash commands.
  • Clarify which tools are cross-platform and which are Windows-only, to help users choose the right approach for their environment.
  • Consider adding a section or table comparing available tooling for Windows and Linux/macOS users.
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 for configuring Service Fabric placement policies primarily using C# and PowerShell. All CLI examples are PowerShell-based, with no equivalent Bash, Linux CLI, or cross-platform Azure CLI examples. PowerShell is a Windows-centric tool, and its exclusive use creates friction for Linux/macOS users. Additionally, PowerShell examples are consistently shown alongside C# code, with no mention of Linux-native tools or patterns.
Recommendations
  • Add equivalent examples using Azure CLI or Bash scripts for configuring placement policies, where possible.
  • Clarify whether the PowerShell commands can be run on Linux/macOS (e.g., via PowerShell Core), or provide guidance for non-Windows users.
  • Mention any cross-platform tools or APIs available for managing Service Fabric clusters.
  • If certain operations are only possible via PowerShell, explicitly state this limitation.
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 extensive PowerShell examples for configuring service sensitivity and maximum load, but does not mention or provide equivalent CLI or scripting examples for Linux/macOS users. PowerShell is presented as the primary scripting interface, and there is no guidance for Linux-native tools or cross-platform alternatives. This creates friction for non-Windows users, especially those managing Service Fabric clusters on Linux.
Recommendations
  • Add equivalent examples using Azure CLI or REST API, which are cross-platform and usable on Linux/macOS.
  • Clarify whether PowerShell examples are supported on Linux (via PowerShell Core), and provide instructions if so.
  • Include bash or shell script examples where possible, or reference cross-platform management tools.
  • Explicitly state any limitations or differences for Linux-based Service Fabric clusters, if applicable.
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 provides examples for managing application parameters in Azure Service Fabric, with a notable emphasis on PowerShell and Visual Studio workflows. PowerShell is mentioned first for application creation, and Visual Studio parameter files are discussed in detail, both of which are Windows-centric tools. Linux equivalents (sfctl and install.sh) are mentioned, but not as prominently or with detailed examples.
Recommendations
  • Provide explicit Linux/macOS examples for parameter management, such as using sfctl and install.sh, including sample commands and workflows.
  • Balance the order of examples so that Linux tools (sfctl) are not secondary to PowerShell.
  • Expand on Jenkins usage for parameter substitution, including sample scripts for Linux environments.
  • Clarify which tools are cross-platform and which are Windows-only, to help users choose the right workflow.
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: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides a PowerShell-based deployment example (New-ServiceFabricApplication) without equivalent Linux/macOS CLI examples, and references Windows file paths and tools first (e.g., schema location in C:\Program Files\...). Linux is mentioned only briefly, and Linux/macOS users are left to infer or seek out their own equivalents.
Recommendations
  • Provide equivalent Azure CLI or sfctl (Service Fabric CLI) examples for application deployment, especially for overriding endpoints, alongside or before PowerShell examples.
  • When referencing file paths (e.g., schema files), include both Windows and Linux locations, or clarify the Linux equivalent.
  • Add explicit notes or sections for Linux/macOS users where behavior or commands differ, such as certificate store locations, deployment commands, or file system paths.
  • Where PowerShell is used, link to documentation for Linux/macOS deployment or provide a cross-platform table of commands.
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 examples and references Windows tools (e.g., RDP, Windows command prompt ping). There are no equivalent examples for Linux/macOS users (such as Azure CLI or Bash), and Windows-specific patterns (like PowerShell and RDP) are mentioned before any cross-platform alternatives. This creates friction for Linux/macOS users wishing to deploy or manage Service Fabric clusters using Azure networking features.
Recommendations
  • Add Azure CLI (az) command examples alongside PowerShell for all deployment steps.
  • Include Bash shell examples for common tasks (e.g., ping, SSH) instead of only Windows command prompt and RDP.
  • Mention SSH access as an alternative to RDP for connecting to VMs, especially for Linux/macOS users.
  • Clearly indicate which steps are cross-platform and which are Windows-specific, and provide guidance for Linux/macOS users where appropriate.
  • Consider reordering examples so that cross-platform tools (Azure CLI, Bash) are presented before or alongside Windows tools.
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 provides a mix of conceptual and hands-on guidance for managing certificates in Azure Service Fabric clusters. While the overall guidance is platform-agnostic, there is a notable bias toward Windows in several areas: PowerShell is the only scripting example given for certificate enrollment, and the Key Vault VM extension is discussed exclusively in its Windows variant. The extension's schema and behaviors are described as 'Only Windows,' and Windows-specific concepts (such as S-channel and certificate linking) are explained in detail. Linux equivalents (e.g., Key Vault VM extension for Linux, Bash/Az CLI examples) are not mentioned or provided, and Windows terminology and tools are presented first or exclusively in critical automation sections.
Recommendations
  • Add Linux-specific examples for certificate provisioning and management, such as using the Key Vault VM extension for Linux or alternative mechanisms.
  • Provide Bash/Az CLI scripting examples alongside PowerShell for certificate enrollment and management.
  • Clarify which steps or mechanisms are Windows-only and offer Linux alternatives or links to relevant documentation.
  • Mention cross-platform considerations explicitly in sections discussing VM extensions, certificate stores, and automation.
  • Ensure that JSON template examples are annotated to indicate any OS-specific settings or requirements.
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 the Azure Portal, ARM templates, and PowerShell. PowerShell is the only CLI tool referenced for scripting, 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 are no Linux/macOS-specific command-line examples or guidance, and PowerShell is presented as the default scripting tool, which may create friction for Linux/macOS users.
Recommendations
  • Add Azure CLI examples for all operations currently demonstrated with PowerShell, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that PowerShell can be used on Linux/macOS, or provide Bash script equivalents where appropriate.
  • Where PowerShell is referenced, clarify if the cmdlets require Windows or if they are available cross-platform.
  • Consider presenting Azure CLI examples before PowerShell, or at least in parallel, to avoid Windows-first bias.
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 ⚠️ missing_linux_example
Summary
The documentation is generally platform-neutral in its conceptual explanations, but exhibits a mild Windows bias in several areas: Windows-specific certificate store paths and tools are mentioned first or exclusively, troubleshooting steps reference Windows event logs and CAPI2 logging without Linux equivalents, and some configuration examples refer to Windows-centric APIs or behaviors. Linux paths are mentioned in passing, but Linux/macOS troubleshooting and operational guidance is largely absent.
Recommendations
  • Provide Linux/macOS equivalents for certificate storage locations, e.g., expand on the mention of /var/lib/sfcerts and describe how to manage certificates there.
  • Include troubleshooting steps for Linux clusters, such as relevant log file locations, commands (e.g., journalctl, systemd logs), and how to diagnose certificate issues on Linux nodes.
  • When referencing Windows tools (e.g., CAPI2 logging, Windows Event Viewer), add parallel instructions for Linux (e.g., OpenSSL commands, syslog, or Service Fabric logs on Linux).
  • Ensure that configuration examples and explanations explicitly state when behavior differs between Windows and Linux, and provide both sets of instructions where applicable.
  • Consider reordering explanations so that Linux and Windows are presented with equal prominence, or group platform-specific instructions under clear headings.
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-only example for bypassing the Infrastructure Service, and references Service Fabric Explorer (a GUI tool primarily used on Windows). No Linux CLI or cross-platform alternatives are mentioned for these tasks, and Windows/PowerShell patterns are presented first and exclusively.
Recommendations
  • Add equivalent Linux/bash CLI examples for cluster operations, such as using Azure CLI or REST API.
  • Clarify whether Service Fabric Explorer is available cross-platform or provide alternatives for Linux/macOS users.
  • Mention any prerequisites or limitations for non-Windows environments when performing cluster management tasks.
  • Where possible, provide links to cross-platform tooling or documentation.
GitHub Create Pull Request
Service Fabric Service Fabric Explorer blocking operations ...ged-cluster-service-fabric-explorer-blocking-operation.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation page predominantly references PowerShell cmdlets (e.g., Remove-AzResource, AzSF PowerShell cmdlets) for managing Service Fabric resources, with no explicit mention of Linux/macOS alternatives or Azure CLI equivalents for key operations. This creates friction for users on non-Windows platforms, as PowerShell is traditionally Windows-centric and may not be installed or preferred on Linux/macOS systems.
Recommendations
  • Include Azure CLI examples for all operations (e.g., az resource delete, az servicefabric managed-cluster application create) alongside PowerShell cmdlets.
  • Clarify that PowerShell Core is cross-platform, but provide explicit instructions for Linux/macOS users on installation and usage.
  • Add notes or examples for ARM template deployment using Azure CLI or portal for Linux/macOS users.
  • Where possible, link to documentation for equivalent operations using Azure CLI or REST API.
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 ⚠️ missing_linux_example ⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation page presents RunToCompletion semantics for Service Fabric containers and guest executables, but all code examples and walkthroughs are Windows-centric. The container examples use Windows Server container images and Windows-specific commands (cmd, echo, ping, set, exit). Querying deployment status is described only via PowerShell and C# APIs, with no mention of Linux or cross-platform CLI tools. There is no guidance or example for Linux containers or Linux-based workflows, despite Service Fabric supporting Linux containers.
Recommendations
  • Add equivalent examples using Linux container images (e.g., Ubuntu or Alpine) and Linux shell commands.
  • Include instructions for querying deployment status using Azure CLI or Service Fabric CLI (sfctl), which are cross-platform.
  • Clarify whether RunToCompletion semantics are supported for Linux containers and, if so, provide Linux-specific guidance.
  • Present Windows and Linux examples side-by-side, or at least mention Linux alternatives where applicable.
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 ⚠️ windows_first
Summary
The documentation contains a notable Windows bias in its guidance for validating manifest XML schemas. It exclusively references opening the schema file in Visual Studio using a Windows file path, with no mention of Linux or cross-platform alternatives. Additionally, the PowerShell module is mentioned as a way to create service instances, but no Linux equivalent (such as Azure CLI or cross-platform tools) is referenced.
Recommendations
  • Provide guidance for validating XML schema on Linux/macOS, such as using cross-platform editors (e.g., VS Code) or command-line tools (e.g., xmllint, xmlstarlet).
  • When referencing file paths, include Linux/macOS equivalents or clarify if the schema file is available on those platforms.
  • Mention cross-platform alternatives to the ServiceFabric PowerShell module, such as Azure CLI, where applicable.
  • Ensure that examples and tooling recommendations are not Windows-exclusive unless the feature is truly Windows-only.
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 for 'Advanced Application Upgrade Topics' in Azure Service Fabric heavily features PowerShell cmdlets for upgrade operations, with all command-line examples given in PowerShell syntax and explicit references to PowerShell module documentation. There are no examples or guidance for Linux/macOS users, such as using the Service Fabric CLI (sfctl) or REST APIs, nor is there mention of cross-platform tooling. The structure and examples assume Windows/PowerShell as the default environment, creating friction for non-Windows users.
Recommendations
  • Add equivalent examples using sfctl (Service Fabric CLI), which is cross-platform and supported on Linux/macOS.
  • Include REST API usage examples for upgrade operations, as these are platform-agnostic.
  • Mention and link to Linux/macOS-specific documentation or guides for Service Fabric application upgrades.
  • Clarify which features or commands are Windows-only, and provide alternatives for Linux/macOS where possible.
  • Reorder sections or examples so that cross-platform tools are presented alongside PowerShell, not only after or instead of.
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: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation page presents upgrade parameters for Service Fabric applications, but it shows a notable Windows bias. Windows tools (PowerShell, Visual Studio) are discussed first and in greater detail, including parameter tables and usage patterns. SFCTL (the cross-platform CLI) is covered later and less extensively. There are no explicit Linux/macOS command examples or walkthroughs in the main content; Linux users must refer to external links for guidance. The PowerShell-centric parameter descriptions and lack of Linux-first or parity examples create friction for non-Windows users.
Recommendations
  • Reorder sections so that SFCTL (the cross-platform CLI) is presented before or alongside PowerShell/Visual Studio.
  • Provide explicit command-line examples for SFCTL usage on Linux/macOS within the main documentation, not just in linked pages.
  • Clarify which parameters are available or behave differently in SFCTL versus PowerShell/Visual Studio.
  • Add a comparison table showing parameter mapping between PowerShell, Visual Studio, and SFCTL.
  • Ensure that Linux/macOS users are not required to consult external pages for basic upgrade operations.
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 upgrades demonstrates a notable Windows bias. The only code example provided uses PowerShell cmdlets, which are native to Windows environments. References to Windows-specific tools (e.g., http.sys) and error messages from the Windows HTTP Server API are present. There are no equivalent examples or instructions for Linux/macOS users, nor are cross-platform CLI alternatives (such as Azure CLI or Service Fabric CLI) mentioned. The 'Next steps' section also prioritizes Visual Studio and PowerShell tutorials, both Windows-centric tools.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl) or Azure CLI for Linux/macOS users.
  • Clarify which upgrade steps and APIs are cross-platform and which are Windows-only.
  • Provide guidance or links for performing upgrades from Linux/macOS environments.
  • Mention any platform-specific limitations or differences explicitly.
  • Reorder or balance 'Next steps' to include Linux/macOS-friendly tooling before or alongside Windows tools.
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 there are several areas where Windows tools and patterns are mentioned first or exclusively. Windows-specific tools (e.g., Event Log, Event Viewer, Diagnostics Agent) are referenced before Linux equivalents, and some examples/tutorials focus on .NET/Windows scenarios. Linux-specific guidance is present but less prominent, and some sections lack Linux-specific examples or configuration details.
Recommendations
  • Ensure Linux monitoring tools and patterns are mentioned alongside Windows equivalents, not after.
  • Provide Linux-specific examples and tutorials (e.g., instrumenting applications, configuring monitoring agents, reading logs via Syslog/LTTng).
  • Clarify which features are Windows-only and which are cross-platform, and provide parity guidance where possible.
  • Add links to Linux-focused tutorials and documentation in the 'Recommended setup' and 'Related content' sections.
  • Balance references to Windows tools (Event Viewer, Diagnostics Agent) with Linux equivalents (Syslog, LTTng, Linux agent configuration).
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 covers Service Fabric application security in a cross-platform context but exhibits mild Windows bias. Windows-specific tools and patterns (e.g., Active Directory domain accounts, group managed service accounts, BitLocker) are mentioned before or more prominently than Linux equivalents. Several examples and links focus on Windows scenarios, and Linux-specific guidance (e.g., disk encryption, user accounts) is either missing or noted as a TODO. Some sections (e.g., container certificate access, HTTPS endpoints) do mention Linux, but overall, Linux parity is incomplete.
Recommendations
  • Add explicit Linux examples for securing user accounts, running services under different principals, and disk encryption.
  • Ensure Linux tools and patterns (e.g., Linux disk encryption methods, Linux user/group management) are mentioned alongside Windows equivalents.
  • Provide links to Linux-specific documentation where available.
  • Clarify which features are cross-platform and which are Windows-only, to help users understand applicability.
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 primarily discusses data serialization in the context of Azure Service Fabric, focusing on C# and .NET serialization. In the 'Next steps' section, upgrade tutorials are offered for Visual Studio and PowerShell, both of which are Windows-centric tools. There are no explicit Linux/macOS alternatives or examples provided, nor is there mention of cross-platform tooling for application upgrades.
Recommendations
  • Add guidance or links for upgrading Service Fabric applications using cross-platform tools such as Azure CLI or REST APIs, which are available on Linux/macOS.
  • Include examples or references for performing application upgrades from Linux/macOS environments.
  • Clarify whether PowerShell Core (cross-platform) is supported, and provide relevant instructions if so.
  • Mention any limitations or considerations for Linux/macOS users, especially if certain features are Windows-only.
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 ⚠️ missing_linux_example
Summary
The documentation page primarily describes Azure Service Fabric's periodic backup configuration, which is cross-platform. However, in the section about file share backup storage, only Windows-specific patterns (e.g., Integrated Windows Authentication and UNC paths) are described, with no mention of Linux-compatible file share approaches (such as SMB mounting on Linux or NFS). There are no Linux-specific examples or guidance for configuring file share backups from Linux-based Service Fabric clusters.
Recommendations
  • Add examples and guidance for configuring file share backup storage from Linux-based Service Fabric clusters, such as using SMB mounts with Linux credentials or NFS shares.
  • Clarify whether file share backup storage is supported on Linux clusters, and if so, provide Linux-specific authentication and path examples.
  • If file share backup is Windows-only, explicitly state this limitation to avoid confusion for Linux users.
  • Ensure parity in documentation by mentioning any Linux-compatible backup storage options (e.g., Azure Blob, NFS) and providing relevant configuration examples.
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 featured prominently and exclusively for certain operations (e.g., cluster upgrades). Windows-specific tools and registry keys are mentioned without Linux equivalents. Windows configuration examples and guidance appear before Linux references, and some upgrade instructions are Windows-only.
Recommendations
  • Add Linux-specific upgrade instructions and examples, such as using shell scripts or relevant Linux tools for cluster upgrades.
  • Provide equivalent Linux configuration guidance for disabling automatic updates, such as using cloud-init or other Linux-native mechanisms.
  • When mentioning PowerShell commands, also include Bash or Azure CLI alternatives where possible, especially for cluster upgrade operations.
  • Ensure Linux examples and references are presented alongside Windows ones, not only in 'Next steps' but throughout the documentation.
  • Clarify when a step is Windows-only, and provide Linux alternatives or explicitly state if Linux users should skip that step.
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 ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation is heavily focused on PowerShell-based workflows, with all command-line examples using PowerShell cmdlets or PowerShell-based REST calls. There are no examples for Linux/macOS users (e.g., using Bash, curl, or Azure CLI), and the required tooling (Microsoft.ServiceFabric.Powershell.Http) is Windows/PowerShell-specific. This creates friction for non-Windows users, even though the REST API is platform-agnostic.
Recommendations
  • Add equivalent Bash/curl examples for REST API calls to demonstrate on-demand backup from Linux/macOS.
  • Clarify whether the PowerShell module is required or if REST API calls can be made directly from any platform.
  • If possible, provide Azure CLI or cross-platform .NET Core examples for common tasks.
  • Explicitly mention platform support and any limitations for Linux/macOS users.
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 for restoring backups in Azure Service Fabric is heavily biased toward Windows/PowerShell usage. All code examples use PowerShell, including REST API calls, and require the Microsoft.ServiceFabric.Powershell.Http module. There are no examples or guidance for Linux/macOS users (e.g., using Bash, curl, or cross-platform tools). The documentation assumes the reader is using Windows and PowerShell, creating friction for non-Windows users.
Recommendations
  • Add equivalent examples using Bash and curl for REST API calls.
  • Document how to authenticate and connect to Service Fabric clusters from Linux/macOS.
  • Mention any cross-platform CLI tools (e.g., Azure CLI) that can be used for these operations.
  • Clarify if the Microsoft.ServiceFabric.Powershell.Http module functionality is available via REST API or other cross-platform means.
  • Provide guidance for Linux/macOS users on prerequisites and setup.
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 Windows bias: PowerShell is referenced as the primary API client, Windows-specific tools and terminology (e.g., RDP, netsh) are used without Linux equivalents, and Windows examples or references often appear before Linux ones. Some sections (e.g., Azure DevOps, API Management) focus on PowerShell and Windows-centric workflows, while Linux alternatives are not always mentioned or are referenced second.
Recommendations
  • Include Linux CLI (az CLI, bash) examples alongside PowerShell where relevant, especially for cluster management and networking tasks.
  • Mention Linux tools and commands (e.g., iptables, ss, netstat) when discussing port ranges, dynamic ports, and firewall configuration.
  • Provide Linux-specific guidance for DevOps and API Management scenarios, including references to cross-platform tools.
  • Ensure parity in documentation structure by presenting Windows and Linux options equally, rather than Windows-first.
  • Clarify when a feature or recommendation is Windows-only, and offer Linux alternatives or workarounds where possible.
GitHub Create Pull Request
Service Fabric Change Azure Service Fabric cluster settings ...rvice-fabric/service-fabric-cluster-fabric-settings.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools
Summary
The documentation provides a comprehensive reference for Service Fabric cluster settings, covering both Azure-hosted and standalone clusters. However, there is evidence of Windows bias: certificate store names default to Windows values (e.g., 'My', 'LocalMachine'), references to Windows-specific tools and concepts (e.g., NTLM authentication, Windows Defender Firewall, Windows Fabric Replicator), and some parameters are described with Windows terminology or defaults. Windows-specific settings (e.g., log directories, firewall configuration) are mentioned without always providing Linux equivalents or clarifying cross-platform differences. Linux is referenced in some settings, but Windows concepts/tools are often presented first or exclusively.
Recommendations
  • Where parameters reference Windows concepts (e.g., certificate store names, NTLM authentication, log directories), add explicit notes or examples for Linux equivalents (e.g., Linux certificate paths, Linux authentication mechanisms, Linux log directories).
  • Clarify which settings are platform-specific and which are cross-platform, ideally with a table or section indicating applicability.
  • For settings like firewall configuration, mention Linux firewall equivalents (e.g., iptables, firewalld) or note if the setting is Windows-only.
  • When referencing Windows tools or patterns (e.g., Windows Defender Firewall, NTLM), provide Linux alternatives or clarify if the feature is not available on Linux.
  • Review default values and descriptions to ensure Linux defaults are mentioned where applicable, not just Windows defaults.
  • Consider providing Linux-first or Linux-parity examples where possible, especially for certificate management and authentication.
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 page provides PowerShell and C# examples exclusively for managing Application Groups in Service Fabric. PowerShell is a Windows-centric tool, and no equivalent Linux/macOS command-line examples (such as Azure CLI, Bash, or REST API) are provided. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer cross-platform tools.
Recommendations
  • Add Azure CLI examples for all operations shown (application creation, updating, querying load, removing capacity).
  • Include REST API sample requests for relevant actions, as these are platform-agnostic.
  • Mention that PowerShell examples are Windows-specific and provide guidance for Linux/macOS users.
  • If PowerShell Core is supported cross-platform, clarify its usage and limitations.
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 ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation page provides general information about Azure Service Fabric node types and virtual machine scale sets. However, there are signs of Windows bias: the 'dataPath' example uses a Windows-style path (D:\SvcFab), and the 'Next steps' section links to PowerShell scripts for changing RDP port ranges and admin credentials, which are Windows-centric tasks. There are no explicit Linux/macOS examples or equivalent guidance for Linux users, despite the mention of 'ServiceFabricLinuxNode' in the extension configuration.
Recommendations
  • Provide Linux/macOS equivalents for remote connection and admin credential changes, such as SSH-based instructions or Bash scripts.
  • Include examples of Linux-style paths (e.g., /var/svcfab) alongside Windows paths in configuration snippets.
  • Clarify which tasks are Windows-only and which are cross-platform, and provide parity guidance where possible.
  • Add links or references to Linux-specific documentation for managing Service Fabric clusters.
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_tools ⚠️ missing_linux_example
Summary
The documentation provides code examples for configuring auto scaling in Service Fabric using C#, XML (application manifest), and PowerShell. The PowerShell examples are Windows-specific, and there are no equivalent CLI or scripting examples for Linux/macOS users. The documentation does mention that resource monitoring is supported for containerized applications on Linux, but all operational/scripted examples are Windows-centric.
Recommendations
  • Add Azure CLI or Bash scripting examples for configuring scaling policies, especially for Linux/macOS users.
  • Clarify which steps or tools are cross-platform and which are Windows-only.
  • Provide guidance or links for Linux users on how to perform equivalent operations (e.g., using REST APIs, Service Fabric CLI (sfctl), or ARM templates).
  • Explicitly state if certain management operations (such as PowerShell cmdlets) are only available on Windows, and suggest alternatives where possible.
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: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation shows a moderate Windows bias. While Service Fabric supports both Windows and Linux clusters, the configuration and code examples (e.g., ClusterManifest.xml, PowerShell cmdlets, .NET/C# code) are Windows-centric or shown first. Linux-specific configuration (e.g., Linux-based manifest examples, Bash/CLI commands) is not provided. The XML manifest examples use <WindowsServer> as the only infrastructure type, and PowerShell is the only shell scripting example given. There is no explicit mention of Linux clusters or their configuration differences.
Recommendations
  • Add Linux-specific configuration examples (e.g., using <Linux> infrastructure in ClusterManifest.xml or Linux node configuration in ClusterConfig.json).
  • Include Azure CLI or Bash examples for service creation and updates, alongside or instead of PowerShell.
  • Clarify in the text where configuration or behavior differs between Windows and Linux clusters.
  • Provide .NET Core or cross-platform SDK code examples, or note if only .NET Framework is supported.
  • Explicitly state if any features or configuration are Windows-only, to avoid confusion.
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 ⚠️ missing_linux_example
Summary
The documentation provides a PowerShell example for querying Service Fabric partition health, but does not include equivalent Linux/macOS CLI examples or mention cross-platform tools. This creates friction for non-Windows users, as Service Fabric can be managed from Linux/macOS using the Service Fabric CLI (sfctl), but this is not referenced.
Recommendations
  • Add equivalent Linux/macOS examples using the Service Fabric CLI (sfctl) for health queries.
  • Mention that Service Fabric management can be performed from Linux/macOS and provide links to relevant documentation.
  • Where possible, show both PowerShell and CLI examples side-by-side to improve parity.
  • Clarify any platform-specific limitations if certain commands are Windows-only.
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 managing Service Fabric metrics primarily in C# and PowerShell, with PowerShell commands shown for service creation and metric configuration. There are no Linux CLI (e.g., Bash, Azure CLI) or cross-platform examples, and PowerShell is presented as the main scripting interface for operational tasks. This creates friction for Linux/macOS users, as Service Fabric supports Linux clusters and the Azure CLI is available cross-platform.
Recommendations
  • Add Azure CLI examples for service creation and metric configuration, where possible.
  • Explicitly mention cross-platform alternatives to PowerShell for Linux/macOS users.
  • Clarify which commands and APIs are available on Linux clusters and which are Windows-only.
  • Consider including Bash scripts or references to REST API usage for metric management.
  • Reorder examples so that cross-platform options (Azure CLI, REST API) are shown before or alongside PowerShell.
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 provides PowerShell command examples for managing node tags and service requirements, but does not include equivalent CLI examples for Linux/macOS users (e.g., Bash, Azure CLI, or REST API usage). PowerShell is a Windows-centric tool, and its exclusive use creates friction for non-Windows users. The documentation also references 'standard Service Fabric interface mechanisms' but only demonstrates PowerShell and C# APIs, omitting practical Linux-friendly alternatives.
Recommendations
  • Add examples using Azure CLI or Bash scripts for managing node tags and service requirements.
  • Include REST API usage examples, which are platform-agnostic and accessible from Linux/macOS.
  • Explicitly mention cross-platform tools and clarify which commands are available on Linux clusters.
  • If PowerShell Core is supported on Linux, note this and provide installation guidance.
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 primarily discusses security scenarios for Azure Service Fabric clusters, but consistently references standalone clusters as 'running on Windows' and provides links and guidance only for Windows Server clusters. There are no equivalent examples, instructions, or links for standalone Linux clusters, nor is it clear how Linux users should secure their clusters outside of Azure. Windows-specific terminology and tools (e.g., Windows authentication, Windows certificate services) are mentioned without Linux alternatives, and Windows instructions are presented first or exclusively.
Recommendations
  • Add explicit guidance and links for securing standalone Linux Service Fabric clusters, including certificate setup and client authentication.
  • Clarify whether standalone Linux clusters are supported and, if so, provide parity in documentation for Linux users.
  • Include Linux-specific examples, such as using OpenSSL for certificate generation, and mention Linux authentication patterns where relevant.
  • Avoid presenting Windows instructions first unless the feature is Windows-only; otherwise, structure sections to address both platforms equally.
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: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools
Summary
The documentation provides general guidance on upgrading Azure Service Fabric clusters and mostly avoids platform-specific bias. However, in the section about OS image upgrades, it references 'Patch the Windows operating system in your Service Fabric cluster' and links to a Windows-specific guide, without mentioning Linux equivalents or clarifying if Linux node patching is supported. Additionally, PowerShell is mentioned alongside Azure CLI for cluster management tasks, but Linux tools or Bash examples are not provided.
Recommendations
  • Clarify whether OS image upgrades and patching guidance apply to Linux-based Service Fabric clusters, and provide links or instructions for Linux node patching if supported.
  • When mentioning PowerShell/Azure CLI, add Bash or Linux shell examples where relevant, or explicitly state if the guidance is platform-agnostic.
  • If Service Fabric clusters support Linux nodes, ensure parity in upgrade and management documentation, including examples and links.
  • Add a note if certain features (like Patch Orchestration Application) are Windows-only, to avoid confusion for Linux users.
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 for the Azure Service Fabric application resource model demonstrates notable Windows bias. All deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) without any mention of Azure CLI or Bash equivalents. The application packaging step is described using Visual Studio, a Windows-centric tool, with no alternative for Linux/macOS users. There are no Linux/macOS-specific instructions or examples, and Windows tools and patterns are presented exclusively and first.
Recommendations
  • Add Azure CLI examples for deployment and deletion alongside PowerShell examples.
  • Provide instructions for packaging applications using cross-platform tools (e.g., dotnet CLI, sfctl, or manual zip commands) instead of only Visual Studio.
  • Include guidance for Linux/macOS users on uploading application packages (e.g., using Azure CLI or azcopy).
  • Ensure screenshots and walkthroughs are not exclusively Windows/Visual Studio-centric, or provide alternatives for other platforms.
  • Clearly indicate when steps are Windows-only and offer Linux/macOS alternatives where possible.
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 Service Fabric service move costs, but does not offer equivalent Linux/CLI examples. PowerShell is primarily a Windows tool, and its use here without mentioning cross-platform alternatives (such as Azure CLI or REST API) creates friction for Linux/macOS users. Additionally, PowerShell examples are presented before C# code, reinforcing a Windows-first approach.
Recommendations
  • Add Azure CLI or REST API examples for configuring and updating MoveCost, as these are cross-platform and usable on Linux/macOS.
  • Explicitly mention whether PowerShell commands are supported on Linux/macOS, or provide guidance for non-Windows users.
  • Consider presenting cross-platform examples (CLI, REST) before or alongside PowerShell to avoid Windows-first ordering.
  • Clarify any platform limitations for Service Fabric management tools, and link to relevant Linux/macOS documentation if available.
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 demonstrates Windows bias by referencing PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) and linking to a Windows Server-specific guide for adding/removing nodes. There are no Linux-specific examples, tools, or guidance provided, and the terminology and instructions assume a Windows environment.
Recommendations
  • Provide equivalent Linux commands or scripts for querying and updating cluster configuration (e.g., using sfctl or REST APIs).
  • Clarify whether standalone clusters can be managed on Linux, and if so, add Linux-specific instructions or links.
  • Add examples for scaling operations using Linux-native tools or cross-platform approaches.
  • Explicitly mention any limitations or differences for Linux users if Windows-only tools are required.
GitHub Create Pull Request
Service Fabric Upgrade an Azure Service Fabric standalone cluster ...ce-fabric/service-fabric-cluster-upgrade-standalone.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation page for upgrading an Azure Service Fabric standalone cluster demonstrates a notable Windows bias. References and links to upgrade instructions and configuration guides are consistently directed to Windows Server-specific documentation (e.g., 'service-fabric-cluster-upgrade-windows-server.md', 'service-fabric-cluster-config-upgrade-windows-server.md'). The patch orchestration application is also described only for Windows. There are no Linux-specific instructions, examples, or references, and no mention of Linux equivalents or support, which may leave Linux users without clear guidance.
Recommendations
  • Add explicit statements clarifying whether standalone clusters are supported on Linux, and if not, state this clearly at the top of the article.
  • If Linux support exists, provide parallel Linux-specific upgrade and configuration instructions, or link to relevant Linux documentation.
  • For features like the Patch Orchestration Application, clarify if there is a Linux equivalent or explicitly state that it is Windows-only.
  • Ensure that examples and references are balanced between Windows and Linux, or explain platform limitations up front.
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_tools ⚠️ missing_linux_example
Summary
The documentation provides code examples for scaling Service Fabric services using C# and PowerShell, but does not include equivalent Linux CLI (e.g., Azure CLI, Bash) examples. PowerShell, a Windows-centric tool, is used exclusively for command-line operations, and there is no mention of Linux-native tools or commands. This creates friction for Linux users who may not use PowerShell or develop on Windows.
Recommendations
  • Add Azure CLI or Bash examples for all PowerShell command snippets (e.g., using 'az sf service update' or 'az sf service create').
  • Explicitly mention Linux support and provide guidance for Linux users where platform differences exist.
  • Where PowerShell is referenced, clarify if cross-platform PowerShell Core is supported, or provide alternatives.
  • Include notes or links to Linux-specific Service Fabric documentation or tools.
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 is a notable Windows bias: Windows-specific tools (e.g., PowerShell, Visual Studio) are mentioned before Linux equivalents, and examples or instructions for Linux are often missing or less prominent. Standalone cluster creation is described only for Windows, with Linux standalone clusters explicitly not supported. References to Windows services and executables (FabricHost.exe, etc.) are frequent, and PowerShell is often listed first among management tools. Linux support is acknowledged, but practical parity in examples and guidance is lacking.
Recommendations
  • Add equivalent Linux examples and instructions wherever Windows-specific steps are described (e.g., cluster creation, management, scaling).
  • Mention Linux CLI tools (e.g., sfctl) and bash scripting alongside PowerShell, and provide sample commands for both platforms.
  • Clarify when features are Windows-only and provide alternative guidance for Linux users where possible.
  • Highlight Linux support earlier in relevant sections, and ensure that Linux users are guided to appropriate resources.
  • Provide links to Linux-specific tutorials and troubleshooting guides.
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 but does not offer equivalent Linux CLI (e.g., Bash, Azure CLI) examples. Windows-centric tools and patterns (PowerShell, ApplicationManifest.xml, Visual Studio) are mentioned first or exclusively, while Linux support is described as limited and lacks practical guidance. There are no Linux-specific instructions or examples for enabling or configuring DNS service, especially for containerized workloads.
Recommendations
  • Add Azure CLI or Bash examples for setting DNS names and managing Service Fabric services, especially for Linux clusters.
  • Include instructions for Linux users on how to enable DNS service (e.g., via ARM templates or CLI), highlighting any differences or limitations.
  • Mention and demonstrate Linux-friendly editors and workflows (e.g., VS Code, nano, vim) for editing manifest files.
  • Clarify any Linux-specific steps or caveats, such as how to verify DNS service status or troubleshoot issues on Linux clusters.
  • Where PowerShell is used, provide equivalent commands for Linux environments if possible.
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 PowerShell-only example for reporting and evaluating application health in Service Fabric, without offering equivalent Linux/macOS CLI or REST API examples. While Service Fabric is cross-platform, the exclusive use of PowerShell in the example creates friction for Linux/macOS users.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl) for Linux/macOS environments.
  • Include REST API examples for health reporting and querying, which are platform-agnostic.
  • Clearly indicate that PowerShell is just one option, and reference cross-platform tools earlier in the section.
  • Provide links or inline examples for Linux/macOS users to accomplish the same tasks.
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 page for Azure Service Fabric hosting model presents PowerShell examples and references Service Fabric PowerShell cmdlets prominently, without providing equivalent Linux CLI (e.g., Bash, sfctl) or cross-platform guidance. Windows/PowerShell tools are mentioned first and exclusively in several sections, creating friction for Linux/macOS users who may need to use sfctl or REST APIs instead.
Recommendations
  • Add equivalent Linux/macOS command-line examples using sfctl (Service Fabric CLI) alongside PowerShell examples.
  • Explicitly mention that PowerShell examples are Windows-centric and provide links or guidance for Linux/macOS users.
  • Where REST API or FabricClient examples are given, clarify their cross-platform applicability.
  • Update 'Next steps' and operational sections to include Linux/macOS management options, not just PowerShell.
  • Consider a table or section summarizing management tool parity (PowerShell vs sfctl vs REST).
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: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page provides manifest examples and explanations for Azure Service Fabric container applications. The examples and narrative are based on the Windows Server 2016 Container Sample, with explicit references to Windows paths (e.g., 'c:\VolumeTest\Data'), Windows-specific commands (e.g., 'winver'), and Windows build versions. There is no mention of Linux container equivalents, Linux paths, or Linux-specific configuration patterns. While some features (like certificate handling) acknowledge Linux (PEM files), the overall examples and guidance are Windows-centric, and Linux users are left to infer how to adapt the manifests for their environment.
Recommendations
  • Provide equivalent manifest examples for Linux containers, including Linux file paths and volume mounts.
  • Include instructions or references for obtaining OS build/version information on Linux (e.g., 'cat /etc/os-release' or 'uname -r').
  • Clarify which manifest settings and patterns are cross-platform and which are Windows-specific.
  • Add links or references to Linux container samples for Service Fabric.
  • Explicitly note any differences in resource governance, certificate handling, or isolation modes between Windows and Linux clusters.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Events ...es/service-fabric/service-fabric-diagnostics-events.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page for Azure Service Fabric Events primarily references Windows-centric 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 mentioned first and exclusively, with no examples or instructions for accessing Service Fabric events on Linux clusters.
Recommendations
  • Add documentation about how Service Fabric events are logged and accessed on Linux clusters, including supported logging mechanisms (e.g., stdout, syslog, Azure Monitor integration).
  • Include examples or references for Linux-based monitoring tools and how to configure diagnostics on Linux nodes.
  • Clarify which features or instructions are Windows-only and provide Linux alternatives where possible.
  • Ensure parity in example commands and tool references for both Windows and Linux environments.
GitHub Create Pull Request
Service Fabric Azure Service Fabric hosting activation and deactivation life cycle ...les/service-fabric/service-fabric-hosting-lifecycle.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation page for Azure Service Fabric hosting activation and deactivation life cycle contains a notable bias toward Windows/PowerShell usage. The only explicit tooling example for deploying or managing Service Fabric applications is via PowerShell, and the 'Next steps' section links to PowerShell-based deployment/removal instructions. There are no Linux/Bash/CLI equivalents or mentions of cross-platform tools, which may hinder Linux/macOS users.
Recommendations
  • Add equivalent examples or references for Linux/macOS users, such as using Azure CLI, Bash scripts, or Service Fabric CLI (sfctl) where applicable.
  • In the 'Next steps' section, provide links to documentation for deploying/removing applications using cross-platform tools (e.g., sfctl, Azure CLI) in addition to PowerShell.
  • Where PowerShell cmdlets are referenced (such as in [p1]), clarify if there are cross-platform alternatives, and link to them.
  • Consider including a note early in the article clarifying which tools are cross-platform and which are Windows-only.
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 frequently references PowerShell and Visual Studio for interacting with the ImageStoreConnectionString, both of which are traditionally Windows-centric tools. Examples and next steps focus on PowerShell, with no mention of Linux/macOS equivalents (such as Azure CLI, Bash, or cross-platform .NET Core tools). This creates friction for users on non-Windows platforms, as they may not know how to retrieve or set the connection string without Windows tools.
Recommendations
  • Add examples for retrieving and setting the ImageStoreConnectionString using Azure CLI, Bash, or REST API, which are cross-platform.
  • Include instructions or links for deploying applications from Linux/macOS environments.
  • Clarify which tools and workflows are available on non-Windows platforms, and provide parity where possible.
  • Mention .NET Core-based approaches if relevant, as these are cross-platform.
GitHub Create Pull Request
Service Fabric Reliable services app manifest examples ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-manifest-example-reliable-services-app.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation page provides Service Fabric application and service manifest examples, but it exhibits mild Windows bias. Windows concepts (such as local admin accounts, NetworkService, Setup.bat, and references to ServiceFabric PowerShell module) are mentioned without Linux equivalents or alternatives. The manifest examples use Windows-centric terminology and tools (e.g., .bat files, NetworkService), and instructions reference Windows user/group patterns. There are no explicit Linux examples or notes about cross-platform differences.
Recommendations
  • Add explicit notes or examples for Linux deployments, such as using shell scripts (.sh) instead of .bat files for SetupEntryPoint.
  • Clarify how user accounts and groups are handled on Linux clusters, and provide equivalent manifest snippets.
  • Mention Linux-specific service accounts (e.g., 'sfuser') or patterns where relevant.
  • Where PowerShell is referenced, add equivalent CLI or bash commands for Linux users.
  • Document any limitations or differences in resource governance, security, and endpoint configuration between Windows and Linux clusters.
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 ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation page for 'Replica soft delete for enhanced data protection in Service Fabric' demonstrates a notable Windows/PowerShell bias. All command-line/API examples reference PowerShell cmdlets (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica, Get-ServiceFabricReplica), with no mention of equivalent CLI commands, REST APIs, or Linux/macOS tooling. The documentation assumes the use of PowerShell and does not provide guidance or examples for Linux users, despite Service Fabric supporting cross-platform clusters.
Recommendations
  • Include equivalent examples using Service Fabric CLI (sfctl) or REST APIs where available, alongside PowerShell examples.
  • Explicitly mention if certain APIs or features are only available via PowerShell, and provide Linux/macOS alternatives or workarounds if possible.
  • Add a section or callout clarifying cross-platform support and how Linux/macOS users can perform the same operations.
  • Reference documentation for managing Service Fabric clusters from Linux/macOS environments.
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 provides explicit instructions for using the Fault Analysis Service with PowerShell and references the Service Fabric SDK, which is primarily Windows-focused. There are no examples or guidance for Linux/macOS users, such as using the Service Fabric CLI (sfctl) or REST APIs, nor is there mention of cross-platform tooling. This creates friction for non-Windows users.
Recommendations
  • Add examples for using the Fault Analysis Service with sfctl (Service Fabric CLI), which is cross-platform.
  • Include references or examples for using the REST API to interact with the Fault Analysis Service.
  • Clarify which features are available on Linux clusters and provide parity in documentation where possible.
  • Explicitly state any Windows-only limitations, if applicable, to set expectations for Linux/macOS users.
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 provides comprehensive coverage of both Kestrel (cross-platform) and HTTP.sys (Windows-only) web servers for ASP.NET Core integration with Azure Service Fabric Reliable Services. However, there is a notable Windows bias in several areas: HTTP.sys (a Windows-only technology) is discussed in depth, with explicit mention of Windows-specific tools (netsh), kernel drivers, and endpoint configuration. Windows-specific details and examples (such as HTTP.sys usage and endpoint registration) are presented before Linux equivalents, and Windows tools are referenced without Linux alternatives. While Kestrel is recommended for Linux and cross-platform scenarios, the documentation sometimes leads with Windows-centric approaches and does not always clarify Linux-specific setup or troubleshooting. There are no PowerShell scripts or commands, but the use of Windows tools and APIs is prominent.
Recommendations
  • Ensure that Linux/macOS users are explicitly guided on how to configure endpoints and ports for Kestrel, including any OS-specific firewall or networking considerations.
  • When referencing Windows tools (such as netsh), provide a note or alternative for Linux/macOS users, or clarify that these steps are not required for Kestrel.
  • Consider reorganizing sections so that cross-platform solutions (Kestrel) are discussed before Windows-only solutions (HTTP.sys), or clearly mark Windows-only content.
  • Add troubleshooting tips or common issues for Linux/macOS users running Service Fabric Reliable Services with ASP.NET Core.
  • Explicitly state which features or examples are Windows-only, and which are cross-platform, to avoid confusion.
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 detailed PowerShell examples for reporting health in Service Fabric, but does not include equivalent Linux/macOS CLI examples (such as Azure CLI, Bash, or cross-platform tools). PowerShell is presented as the primary scripting interface, and Windows-style paths and prompts are used. REST and API usage are described, but scripting and command-line examples are Windows-centric.
Recommendations
  • Add equivalent examples using Azure CLI or Bash scripts for Linux/macOS users.
  • Clarify whether PowerShell Core (cross-platform) is supported, and provide examples if so.
  • Mention any Linux-specific Service Fabric tools or commands, or note if PowerShell cmdlets are available on Linux.
  • Reorder sections so that REST and API examples are presented before PowerShell, or present them together to avoid Windows-first bias.
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: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation is heavily oriented toward Visual Studio workflows, referencing Windows-specific build/deploy actions (F5/Ctrl+F5/Publish) and GUI interactions. There are no Linux/macOS equivalents or CLI examples for managing StartupServices.xml, and PowerShell is mentioned as a way to create service instances, but no Linux tools or commands are provided. The documentation assumes use of Visual Studio, which is primarily a Windows tool.
Recommendations
  • Add guidance for Linux/macOS users, such as how to manage StartupServices.xml using CLI tools (e.g., Azure CLI, Service Fabric CLI, or PowerShell Core on Linux).
  • Provide examples for deploying and configuring Service Fabric applications without Visual Studio, including relevant commands and scripts.
  • Clarify which features are Visual Studio/Windows-only and offer alternative workflows for cross-platform users.
  • Mention any limitations or differences for Linux/macOS users explicitly, so expectations are clear.
GitHub Create Pull Request
Service Fabric Learn Azure Service Fabric terminology ...es/service-fabric/service-fabric-technical-overview.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools
Summary
The documentation page is generally cross-platform and describes Service Fabric concepts applicable to both Windows and Linux. However, some terminology and examples, such as references to 'auto-start Windows service' and EXE/DLL files, are Windows-centric and appear before Linux equivalents. The mention of Windows-specific executables and services (e.g., FabricHost.exe, Fabric.exe, FabricGateway.exe) is prominent, and Linux equivalents or clarifications are not provided in those sections. The page does acknowledge Linux support for containers and guest executables, but Windows terminology and tools are presented first and more frequently.
Recommendations
  • Where Windows-specific services or executables are mentioned (e.g., FabricHost.exe), clarify if/how these concepts apply on Linux nodes, or explicitly state differences.
  • When describing code packages, supplement EXE/DLL references with Linux equivalents (e.g., ELF binaries, .so files) to improve parity.
  • In sections referencing Windows services, add notes or examples for Linux (e.g., systemd services or relevant Linux process management).
  • Ensure that descriptions of cluster nodes, application packaging, and deployment reference both Windows and Linux environments equally, or provide links to Linux-specific documentation where appropriate.
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 (notably Hyper-V and PowerShell's Convert-VHD), often without providing Linux-native alternatives or mentioning them second. This creates friction for Linux/macOS users, especially in the disk creation and conversion steps.
Recommendations
  • Add instructions for creating and converting VHDs using Linux-native tools (e.g., qemu-img, VBoxManage, or KVM).
  • Mention Linux/macOS alternatives alongside Windows tools, not after or instead of them.
  • Provide example commands for VHD conversion on Linux (e.g., qemu-img convert -O vpc ...).
  • Clarify which steps are Windows-only and offer Linux equivalents where possible.
  • Move Windows-specific instructions (Hyper-V, PowerShell) to a dedicated section or appendix, and prioritize Linux-native workflows in the main guide.
GitHub Create Pull Request
Virtual Machines vCPU quotas ...ute-docs/blob/main/articles/virtual-machines/quotas.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for checking vCPU quotas. However, the PowerShell example is given equal prominence to the CLI example, despite PowerShell being primarily a Windows-centric tool. There is no explicit mention of Linux-specific tools or shell environments (e.g., Bash), and the CLI example is not clearly labeled as suitable for Linux/macOS users. The PowerShell section may create friction for Linux/macOS users, as it is less relevant to their platforms.
Recommendations
  • Clarify that Azure CLI commands are cross-platform and suitable for Linux/macOS users.
  • Label the PowerShell section as primarily for Windows users.
  • Consider providing Bash shell examples or explicitly stating that Azure CLI works in Bash on Linux/macOS.
  • Ensure that CLI examples are shown first, as they are more universally applicable.
GitHub Create Pull Request
Virtual Machines Create a VM from a generalized image in a gallery ...icles/virtual-machines/vm-generalized-image-version.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for creating VMs from generalized images in a gallery. However, PowerShell examples are exclusively shown using Windows VM configuration (Set-AzVMOperatingSystem -Windows), and the full parameter set for PowerShell is Windows-specific. In contrast, CLI examples default to Linux VM creation, with a brief note on how to switch to password authentication for Windows or Linux. The PowerShell tab is always present and detailed, but does not show how to create a Linux VM using PowerShell. Additionally, in the REST examples, both Linux and Windows VM creation are shown, but the PowerShell section is Windows-centric. The ordering of examples sometimes places Windows (PowerShell) before Linux (CLI), and the PowerShell examples do not provide parity for Linux users.
Recommendations
  • Add PowerShell examples for creating Linux VMs, including the use of Set-AzVMOperatingSystem -Linux and SSH key authentication.
  • Clarify in PowerShell sections that both Windows and Linux VMs can be created, and provide explicit instructions for both.
  • Ensure that CLI and PowerShell examples are presented with equal detail for both OS types.
  • Consider alternating or grouping examples by OS type, rather than by tool, to avoid implicit prioritization.
GitHub Create Pull Request
Virtual Machines Resize a virtual machine ...blob/main/articles/virtual-machines/sizes/resize-vm.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation provides detailed PowerShell examples and explanations for resizing Azure VMs, including both general and availability set scenarios, before presenting Azure CLI and Terraform options. The PowerShell sections are more extensive and include local usage and authentication steps, which are Windows-centric. The Terraform example references only a Windows VM quickstart, and there is no explicit Linux-focused example or mention of Linux-specific considerations. While the CLI examples are cross-platform, the overall structure and example selection favor Windows users.
Recommendations
  • Add explicit Linux-focused examples, especially in the Terraform section (e.g., link to or show an azurerm_linux_virtual_machine block and a Linux quickstart).
  • Balance the PowerShell and CLI sections in terms of detail and explanation, ensuring CLI (which is cross-platform) is not treated as secondary.
  • In the Terraform section, provide both Windows and Linux resource block examples or link to both quickstarts.
  • Where possible, clarify that CLI commands work on all platforms and highlight any OS-specific considerations.
  • Consider presenting CLI examples before PowerShell, as CLI is cross-platform and PowerShell is primarily Windows-focused (though available on Linux, it is less common there).
GitHub Create Pull Request
Virtual Machines Deploy a Trusted Launch VM ...ain/articles/virtual-machines/trusted-launch-portal.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation covers both Linux and Windows VM scenarios for Trusted Launch, but PowerShell examples are exclusively Windows-focused and provided in greater detail than Linux equivalents. In several sections, Windows-specific parameters and images are shown first or exclusively in PowerShell, while CLI examples are Linux-centric. Some PowerShell snippets lack Linux parity, and Windows terminology is used in places where Linux alternatives could be clarified.
Recommendations
  • Add PowerShell examples for Linux VM deployment, including specifying Linux images and OS types.
  • Ensure PowerShell snippets demonstrate both Windows and Linux VM creation, mirroring the CLI approach.
  • Where possible, clarify parameters that differ between Windows and Linux (e.g., OS-specific flags, credential handling).
  • In PowerShell sections, provide Linux image references and instructions for Linux VM configuration.
  • Review ordering: avoid always showing Windows examples first in PowerShell, and balance with Linux examples.
GitHub Create Pull Request
Virtual Machines Create a VM from a specialized image version ...icles/virtual-machines/vm-specialized-image-version.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for creating VMs from specialized images. However, PowerShell examples are notably more detailed, including extensive networking and VM configuration steps, while CLI examples are more concise. PowerShell is a Windows-centric tool, and its prominence and depth in the documentation may create friction for Linux/macOS users. Additionally, in several sections, PowerShell examples are presented immediately after CLI, sometimes with more explanation and context, which could be perceived as Windows-first bias.
Recommendations
  • Expand Azure CLI examples to include more detailed steps, such as networking and VM configuration, to match the depth of PowerShell examples.
  • Explicitly mention that Azure CLI is cross-platform and encourage its use for Linux/macOS users.
  • Consider providing Bash shell script examples for common tasks, especially for Linux users.
  • Ensure that CLI and PowerShell examples are equally detailed and placed in parallel, rather than PowerShell being more comprehensive.
  • Add a brief note clarifying that PowerShell examples are primarily for Windows users, while CLI is suitable for all platforms.
GitHub Create Pull Request
Service Fabric Package an existing executable to Azure Service Fabric ...abric/service-fabric-guest-executables-introduction.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first
Summary
The documentation shows a mild Windows bias by referencing the Service Fabric SDK schema path only as a Windows directory (C:\Program Files\...), and by mentioning Visual Studio (a Windows-centric tool) as the primary packaging method before mentioning command-line utilities. There are no explicit Linux/macOS examples or tool references, and the file structure and packaging process are described in a platform-agnostic way otherwise.
Recommendations
  • Add Linux/macOS equivalents for the Service Fabric SDK schema path, or clarify if the SDK is Windows-only.
  • Mention cross-platform tools (such as Azure CLI, Service Fabric CLI, or VS Code) where possible, or clarify if Visual Studio is required and only available on Windows.
  • Include explicit Linux/macOS packaging and deployment examples if supported.
  • Clarify any platform limitations for Service Fabric guest executables in an early note.
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: 1 bias type
Detected Bias Types
⚠️ windows_first
Summary
The documentation provides a balanced overview of migrating to Azure Virtual Machine Scale Sets in Flexible orchestration, but in the 'Create scalable network connectivity' section, Windows scenarios (activation, updates) are listed before Linux scenarios (package managers). There are no PowerShell-heavy examples, Windows tools, or missing Linux examples; Azure CLI is used for code snippets, which is cross-platform.
Recommendations
  • When listing common outbound connectivity scenarios, mention Linux package manager access before or alongside Windows activation and updates.
  • Explicitly state that Azure CLI commands are cross-platform and can be used on Windows, Linux, and macOS.
  • Consider adding a brief example or note for Linux-specific migration considerations if relevant (e.g., SSH key handling, package updates).
GitHub Create Pull Request
Service Fabric Overview of Azure Service Fabric ...ain/articles/service-fabric/service-fabric-overview.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 support for Azure Service Fabric, and provides parity in describing development environments for each. However, Windows development (with Visual Studio and PowerShell) is mentioned before Linux development (with Eclipse and Yeoman), and the quickstart link points to a .NET (Windows-centric) guide. No Linux-specific examples or quickstarts are directly linked or highlighted.
Recommendations
  • Provide quickstart links for both Windows (.NET) and Linux (Java/.NET Core) development paths.
  • Alternate the order of Windows and Linux mentions to avoid 'windows_first' bias.
  • Include explicit examples or links for Linux development, such as a quickstart for Java or .NET Core on Linux.
  • Ensure that references to tools (e.g., PowerShell, Visual Studio) are matched with Linux equivalents (e.g., Bash, Eclipse, Yeoman) in both description and prominence.
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: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example
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, and Windows image patterns are referenced before Linux equivalents. There are no explicit Linux-specific examples or guidance, and the documentation does not clarify whether the described cleanup features apply equally to Linux containers or clusters.
Recommendations
  • Add explicit examples and guidance for Linux container images (e.g., Ubuntu, Alpine) and clarify if cleanup settings apply to Linux clusters.
  • Mention Linux base images (such as 'docker.io/library/alpine', 'ubuntu') alongside Windows images in the 'ContainerImagesToSkip' section.
  • Clarify any platform-specific limitations or behaviors for container image management on Linux vs. Windows nodes.
  • Provide sample configuration for Linux container scenarios if applicable.
GitHub Create Pull Request
Service Fabric Custom Image .../articles/service-fabric/how-to-deploy-custom-image.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation page exhibits mild Windows bias. The introductory section and terminology focus on 'custom windows images' and Windows-specific concepts, even though Linux is referenced in prerequisites. The only CLI example provided is in PowerShell, with no equivalent Linux/bash example. Windows terminology and patterns are mentioned first and more prominently.
Recommendations
  • Provide equivalent bash/Azure CLI examples for role assignment (e.g., using az CLI instead of PowerShell).
  • Clarify that custom images can be Linux-based, not just Windows, and update language to be OS-neutral where applicable.
  • Add explicit examples or links for Linux custom image creation and deployment, ensuring parity in guidance.
  • Reorder sections or examples so Linux and Windows are treated equally, or note when instructions apply to both.
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 container support for both Linux and Windows, but there is a slight bias toward Windows in some sections. Windows container runtimes and tools (Mirantis, DockerEE) are listed in more detail than Linux (just 'Docker'), and Windows scenarios (IIS lift-and-shift) are described first and in more depth. Windows tutorials and resources are sometimes mentioned before Linux equivalents, and Windows-specific tools are referenced without always providing Linux alternatives.
Recommendations
  • Expand Linux container runtime details beyond just 'Docker' (e.g., mention containerd, Podman if supported).
  • Ensure Linux scenarios/examples are given equal prominence and detail as Windows scenarios (e.g., highlight common Linux web servers like Apache or NGINX for lift-and-shift).
  • When listing tutorials or quickstarts, alternate the order or group by OS to avoid 'windows_first' bias.
  • Provide links to Linux container documentation and resources where Windows-specific links are given.
  • Clarify any feature parity or limitations between Linux and Windows containers in Service Fabric.
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 Windows PowerShell and cross-platform CLI (sfctl) examples for deploying Docker Compose files to Azure Service Fabric. However, PowerShell examples are presented first and in greater detail, with explicit command blocks for each operation, which may signal a Windows-first bias. The CLI section is present and covers equivalent functionality, but is less prominent and lacks some explanatory detail compared to the PowerShell section.
Recommendations
  • Present CLI (sfctl) examples before or alongside PowerShell examples to emphasize cross-platform support.
  • Expand the CLI section with more detailed explanations, matching the depth of the PowerShell section.
  • Clearly indicate which tools are cross-platform and which are Windows-only, to help users choose appropriately.
  • Consider adding Linux/macOS-specific notes or troubleshooting tips, if applicable.
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: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation is generally platform-neutral, focusing on .NET serialization concepts relevant to Azure Service Fabric. However, in the 'Next steps' section, Windows-centric upgrade tutorials (Visual Studio and PowerShell) are listed before any Linux/macOS alternatives, and only PowerShell is mentioned as a CLI tool. There are no explicit Linux/macOS examples or references to cross-platform tools like Azure CLI or Bash.
Recommendations
  • Add Linux/macOS-friendly upgrade tutorials, such as using Azure CLI or Bash scripts, and reference them alongside or before Windows-specific tools.
  • Clarify that PowerShell is available cross-platform, or provide equivalent instructions for Bash/Azure CLI.
  • Ensure that examples and links are balanced between Windows and Linux/macOS environments, especially in 'Next steps' and tooling sections.
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
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all major operations (attach, detach, move VMs). However, PowerShell examples are always present and shown alongside CLI, which is cross-platform but often associated with Linux/macOS users. The PowerShell examples are more verbose and detailed, sometimes including Windows-centric parameters (e.g., OpenPorts 3389 for RDP). In most sections, Azure CLI is shown before PowerShell, but both are always included. There are no missing Linux examples, as Azure CLI covers Linux/macOS scenarios. No Windows-only tools or patterns are mentioned, and the documentation is not Windows-specific.
Recommendations
  • Clarify that Azure CLI is fully cross-platform and suitable for Linux/macOS users.
  • Consider adding explicit Bash or shell script examples where relevant, especially for automation scenarios.
  • Review PowerShell examples for Windows-centric parameters (e.g., OpenPorts 3389) and add Linux-relevant ports (e.g., SSH 22) or notes for Linux users.
  • Ensure parity in detail between CLI and PowerShell examples; if PowerShell includes extra networking or security group parameters, add similar CLI examples.
  • Add a short section or note for Linux/macOS users confirming that all operations are supported via Azure CLI and portal.
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 parity between Azure CLI and PowerShell for all command-line examples, but PowerShell examples are consistently shown alongside CLI and portal, and are sometimes more detailed. There is a mild 'windows_first' bias in that PowerShell is presented as a primary scripting option, but Azure CLI is cross-platform and is always included. No Windows-only tools or patterns are mentioned, and Linux users can complete all tasks using the Azure CLI. There are no missing Linux examples, but the PowerShell presence may suggest Windows-centric workflows.
Recommendations
  • Clarify that Azure CLI is fully cross-platform and suitable for Linux/macOS users.
  • Consider explicitly mentioning Bash or shell scripting in CLI examples to reinforce Linux parity.
  • Add a note that PowerShell examples are for Windows users, while Azure CLI is recommended for Linux/macOS.
  • Ensure that CLI examples are as detailed as PowerShell ones, if any discrepancies exist.
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 listed before CLI examples, and some sections (such as querying public IPs) show PowerShell commands first or exclusively. There is a slight preference for Windows/PowerShell tooling in example ordering and coverage, but Linux parity is generally maintained through CLI and ARM template examples.
Recommendations
  • Ensure CLI examples are always provided alongside PowerShell, especially for tasks like querying public IP addresses.
  • Present CLI and PowerShell examples in parallel tabs, or alternate their ordering to avoid Windows-first bias.
  • Explicitly mention that Azure CLI works cross-platform (Linux/macOS/Windows) and highlight this in introductory sections.
  • Where possible, add Bash scripting examples for advanced scenarios to further support Linux users.
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 custom metrics and application health extension responses. However, there are several instances where Windows/PowerShell examples are presented before Linux/Bash equivalents, and PowerShell is given equal or greater prominence. The REST and Azure CLI examples are platform-neutral, but the PowerShell sections are detailed and appear before Bash in some places. The documentation also uses Windows-centric extension names (e.g., ApplicationHealthWindows) in some sample code, though Linux equivalents are mentioned.
Recommendations
  • Present Linux/Bash examples before Windows/PowerShell examples, or alternate their order for parity.
  • Ensure that both ApplicationHealthLinux and ApplicationHealthWindows are equally referenced in sample code and explanations.
  • Clarify in sample code comments which extension type to use for Linux vs. Windows VMSS instances.
  • Expand Bash/Python examples to match the detail level of PowerShell examples.
  • Add explicit notes for macOS users where Bash/Python examples are applicable.
GitHub Create Pull Request
Virtual Machine Scale Sets Create an Azure scale set that uses Availability Zones ...s/virtual-machine-scale-sets-use-availability-zones.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for creating and updating scale sets with Availability Zones. However, PowerShell examples are given equal prominence to CLI, and in some sections (such as 'Update scale set to add availability zones'), PowerShell is listed before REST API and after CLI. The CLI examples are cross-platform, but PowerShell is Windows-centric. There are no explicit Linux-specific command-line examples (e.g., Bash scripts), and the documentation does not mention Linux tools or patterns. The Resource Manager template section references both Linux and Windows getting started articles, but overall, there is a slight bias towards Windows/PowerShell in example prominence and ordering.
Recommendations
  • Ensure Azure CLI examples are always presented before PowerShell, as CLI is cross-platform.
  • Add explicit Bash shell script examples for Linux users where relevant.
  • Clarify that Azure CLI commands are cross-platform and suitable for Linux/macOS users.
  • Consider including a note or section highlighting Linux/macOS parity and recommending CLI for those platforms.
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 (cross-platform) and Azure PowerShell (Windows-centric) examples for creating instant access snapshots, with CLI examples shown first. There are no Linux-specific tools or shell scripts, but the CLI coverage is sufficient for Linux/macOS users. No Windows-only tools or patterns are mentioned, and the PowerShell example is not prioritized over CLI. The presence of PowerShell is expected for Azure, but the lack of explicit Linux shell scripting or troubleshooting is a minor bias.
Recommendations
  • Consider adding explicit Bash shell script examples for common Linux automation scenarios (e.g., using az CLI in bash loops or with jq for JSON parsing).
  • Clarify in the introduction that all CLI examples are cross-platform and suitable for Linux/macOS users.
  • If there are any troubleshooting steps or advanced usage, provide Linux/macOS-specific notes if behavior differs.
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 primarily Linux-focused, as indicated by the title and content. However, there are some minor Windows bias patterns: PowerShell deployment instructions are presented before Azure CLI instructions, and troubleshooting examples use PowerShell first. The CLI and JSON examples are present and correct for Linux, but the ordering and emphasis on PowerShell may create friction for Linux users who typically use Bash or Azure CLI.
Recommendations
  • Present Azure CLI deployment instructions before PowerShell, as CLI is more commonly used on Linux.
  • Ensure troubleshooting sections show Azure CLI commands first or equally alongside PowerShell.
  • Clarify that PowerShell is optional and primarily for Windows users, while Azure CLI is recommended for Linux.
  • Consider adding Bash script examples for common Linux automation 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: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides parity between Linux and Windows in most sections, especially in CLI and REST examples, but there is a subtle Windows bias in the PowerShell examples and ordering. PowerShell examples are Windows-centric by default, and Windows is mentioned first in some places. Linux is well-covered, but Windows examples and terminology sometimes appear before Linux equivalents.
Recommendations
  • Ensure Linux and Windows examples are presented with equal prominence and ordering, especially in PowerShell and CLI sections.
  • In PowerShell examples, provide explicit Linux-focused examples (e.g., using -OsType Linux) alongside Windows ones.
  • Where possible, alternate the order of Linux and Windows examples to avoid implicit prioritization.
  • Add clarifying notes that PowerShell can be used for Linux images as well, and show Linux-specific PowerShell commands.
GitHub Create Pull Request
Virtual Machines Azure Instance Metadata Service for virtual machines ...articles/virtual-machines/instance-metadata-service.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ minor_windows_tools
Summary
The documentation provides both Windows (PowerShell) and Linux (bash/curl) examples for all major usage scenarios, with clear tab separation. However, Windows/PowerShell examples are consistently presented first in each sample, and some troubleshooting and advanced routing instructions are more verbose for Windows (including PowerShell CLI examples even in Linux troubleshooting). Windows-specific tools (PowerShell, route print, ipconfig) are referenced before their Linux equivalents, but Linux coverage is strong and parity is maintained throughout.
Recommendations
  • Alternate the order of Windows and Linux examples, or present Linux first in some sections to avoid implicit prioritization.
  • Ensure troubleshooting steps for Linux are as detailed as those for Windows, and avoid including PowerShell CLI examples in Linux troubleshooting unless a direct Linux CLI equivalent is also provided.
  • Where possible, reference Linux tools (e.g., netstat, ip, ifconfig) alongside Windows tools in general guidance sections.
  • Consider adding a short note at the start stating that both Linux and Windows are equally supported, and that example order does not imply priority.
GitHub Create Pull Request
Virtual Machines Share VM images in a compute gallery ...in/articles/virtual-machines/shared-image-galleries.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 images, but there is a mild Windows bias in several areas. PowerShell examples are provided alongside Azure CLI, but PowerShell is mentioned first or more prominently in some sections. References to Windows tools (e.g., Sysprep) are given equal footing to Linux tools (waagent), but links to Windows-specific pages (e.g., upload VHD for Windows) are sometimes listed before Linux equivalents. In the FAQ, PowerShell is mentioned before CLI for cross-tenant sharing. Overall, Linux users can complete all tasks, but Windows tools and patterns are sometimes prioritized.
Recommendations
  • Ensure that CLI and PowerShell examples are presented in parallel, with equal prominence and ordering.
  • When referencing upload or creation guides, list Linux and Windows links together, or alternate their order to avoid Windows-first bias.
  • Where possible, provide Bash or shell script examples alongside PowerShell for automation.
  • In cross-tenant sharing sections, mention CLI and PowerShell equally, or provide a combined example for both platforms.
GitHub Create Pull Request
Virtual Machines Enable Trusted launch on existing Gen2 VMs ...rticles/virtual-machines/trusted-launch-existing-vm.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides parity for both Linux and Windows VMs, with explicit statements that the feature applies to both. However, PowerShell examples are used for ARM template deployment and rollback, which may create friction for Linux/macOS users. In several sections, PowerShell is presented before CLI, and installation instructions for Azure PowerShell reference Windows. The CLI examples are cross-platform, but PowerShell is emphasized, suggesting a mild Windows bias.
Recommendations
  • Provide Bash or cross-platform shell examples for ARM template deployment and rollback, especially for Linux/macOS users.
  • Clarify that Azure PowerShell can be used on Linux/macOS and provide installation links for those platforms.
  • Where PowerShell is used, offer equivalent Bash/CLI commands or note that CLI is preferred for Linux/macOS.
  • Consider listing CLI examples before PowerShell in tab order, as CLI is more universally available.
GitHub Create Pull Request
Virtual Machines VM vCore Customization ...lob/main/articles/virtual-machines/vm-customization.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 VM vCore customization. While the CLI example uses a Linux image (Ubuntu), the PowerShell section is given equal prominence and is described in detail. The ordering of sections places PowerShell immediately after CLI, and both are referenced as valid tools. There is a slight 'windows_first' bias in the ordering and prominence of PowerShell, but Linux users are not blocked from completing the task, as CLI and ARM template examples are provided. No Windows-only tools or patterns are mentioned exclusively, and Linux parity is generally maintained.
Recommendations
  • Explicitly state that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Consider providing Bash shell script examples or referencing Bash usage for Linux users.
  • Clarify that PowerShell is available cross-platform, but highlight CLI as the default for Linux/macOS.
  • Ensure that CLI examples are shown first, or that the ordering does not imply Windows preference.
  • Add a note that all features are available regardless of OS, and that the CLI is the recommended tool for Linux/macOS.
GitHub Create Pull Request