← Back to Dashboard
282
Pages Scanned
95
Pages Flagged
282
Changed Pages
33.7%
% Pages Flagged

Live Progress

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

Scan Information

Started At: 2026-02-23 00:00:32

Finished At: In Progress

Status: in_progress

Target Repo: Azure Compute

Current Phase: discovery

Files Queued: 282

Files Completed: 282

Problematic Pages

95 issues found
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 Windows-centric. There are no Linux equivalents or workarounds provided, and the feature is described as Windows-only. This creates a clear platform bias, but it is transparently acknowledged.
Recommendations
  • Add a prominent note at the top clarifying that reverse proxy is Windows-only and not available for Linux clusters.
  • Provide links or references to alternative approaches for service discovery and communication in Linux Service Fabric clusters, if any exist.
  • If Linux support is planned, mention roadmap or alternatives for Linux users.
  • Ensure that related documentation (e.g., setup, diagnostics) also clearly states platform limitations.
GitHub Create Pull Request
Service Fabric Standalone Service Fabric clusters overview ...-fabric/service-fabric-standalone-clusters-overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ missing_linux_example ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page initially describes Service Fabric clusters as supporting both Windows Server and Linux, but all subsequent sections, especially 'Supported operating systems', clarify that Linux is not yet supported for standalone clusters. Security and management instructions reference Windows-specific tools and patterns (e.g., Kerberos, group Managed Service Accounts, Windows accounts), with no Linux equivalents or guidance. The examples and recommendations are Windows-centric, and Linux users are left without actionable steps or parity.
Recommendations
  • Clarify at the top that standalone Service Fabric clusters are currently Windows-only, despite initial claims of Linux support.
  • Remove or revise statements suggesting Linux support unless it is imminent or available.
  • If Linux support is planned, provide a roadmap or link to relevant Linux documentation.
  • Add explicit guidance for Linux users, or direct them to alternative Service Fabric deployment models (e.g., Azure Service Fabric clusters with Linux nodes).
  • Ensure that security and management sections either mention Linux equivalents or state their Windows-specific nature.
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 is heavily focused on Windows-centric tools and workflows, specifically Visual Studio and PowerShell. All upgrade instructions and examples reference Visual Studio (a Windows-only IDE) and PowerShell (primarily used on Windows for Service Fabric management), 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 and examples for upgrading Service Fabric applications using Azure CLI or Service Fabric CLI (sfctl), which are cross-platform.
  • Include guidance for configuring upgrade parameters and health policies via command-line tools available on Linux/macOS.
  • Clearly indicate which steps are Windows-only and provide equivalent steps for Linux/macOS users where possible.
  • Reference documentation for Linux/macOS development environments if Visual Studio is not available.
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 comprehensive overview of certificate management in Azure Service Fabric clusters, but there is a notable Windows bias. PowerShell is the only scripting example given for programmatic certificate enrollment, and the Key Vault VM extension is discussed primarily in its Windows context. The 'linkOnRenewal' feature is explicitly described as Windows-only, and there is no mention of Linux equivalents or cross-platform command-line tools (e.g., Azure CLI, Bash scripts, or Linux VM extensions) for certificate management. Additionally, Windows/PowerShell tools and patterns are presented first and in detail, with no Linux-specific guidance or parity.
Recommendations
  • Include Azure CLI and/or Bash script examples for certificate enrollment and management, alongside or instead of PowerShell.
  • Document the use of the Key Vault VM extension for Linux VMs (if supported), or clearly state if it is Windows-only and provide Linux alternatives (e.g., cloud-init, custom script extensions).
  • When referencing features like 'linkOnRenewal' that are Windows-specific, provide guidance or callouts for Linux users.
  • Add explicit Linux/macOS instructions or parity notes where only Windows/PowerShell guidance is given.
  • Ensure that cross-platform tools and workflows are mentioned at least as prominently as Windows-specific ones.
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 page provides several examples and links for Azure PowerShell modules and references PowerShell-based workflows prominently in the 'Best practices' section. PowerShell is traditionally associated with Windows, and its usage is highlighted before mentioning cross-platform tools like Azure CLI or sfctl. While Azure PowerShell is technically cross-platform, its prominence may create friction for Linux/macOS users who prefer CLI or native tools. The page does mention Azure CLI and ARM templates, but PowerShell examples are given first and in more detail.
Recommendations
  • Provide Azure CLI examples alongside PowerShell examples, especially in the 'Best practices' section.
  • Explicitly note that Azure PowerShell and Azure CLI are both cross-platform, and link to installation guides for Linux/macOS.
  • Where possible, show CLI commands before or alongside PowerShell commands to improve parity.
  • Add examples for sfctl usage where relevant, since it is a native Service Fabric CLI tool.
  • Clarify that PowerShell is not required and that all tasks can be performed with CLI or ARM templates.
GitHub Create Pull Request
Service Fabric Service Fabric Explorer blocking operations ...ged-cluster-service-fabric-explorer-blocking-operation.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page provides management guidance for Service Fabric Explorer, referencing Az PowerShell cmdlets (e.g., Remove-AzResource) and AzSF PowerShell cmdlets for key operations. While it briefly mentions the 'az resource' CLI for deleting applications, PowerShell examples and terminology are predominant, and Linux/macOS equivalents (such as Azure CLI commands) are not consistently provided for all tasks. The ordering and emphasis on PowerShell tools may create friction for Linux/macOS users.
Recommendations
  • For every PowerShell cmdlet mentioned, provide the equivalent Azure CLI command (where available) and link to its documentation.
  • Clarify which tools are cross-platform and which are Windows-only.
  • Present Azure CLI examples before or alongside PowerShell examples to improve parity.
  • Explicitly state if certain operations can only be performed with PowerShell, and suggest alternatives for Linux/macOS users if possible.
GitHub Create Pull Request
Service Fabric RunToCompletion semantics and specifications ...blob/main/articles/service-fabric/run-to-completion.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page presents RunToCompletion semantics in Service Fabric with a strong Windows bias. All code examples use Windows containers (nanoserver), Windows-specific commands (cmd, echo, ping, set, exit), and the application manifests are named and described as Windows-only. Querying deployment status is demonstrated only via PowerShell and C# APIs, with no mention of Linux equivalents or CLI tools. There are no examples or guidance for Linux containers or Linux-based workflows, despite Service Fabric supporting Linux containers.
Recommendations
  • Add examples using Linux containers (e.g., Ubuntu or Alpine images) with equivalent shell commands.
  • Provide guidance or code snippets for querying deployment status using Azure CLI or Service Fabric CLI on Linux/macOS.
  • Clarify whether RunToCompletion semantics are supported for Linux containers and, if so, provide parity in documentation.
  • Rename examples and descriptions to be platform-neutral where possible, or explicitly state platform limitations.
  • Include notes or links for Linux/macOS users about relevant tools and commands.
GitHub Create Pull Request
Service Fabric Application upgrade: data serialization ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-application-upgrade-data-serialization.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page provides upgrade walkthroughs using Visual Studio and PowerShell, both of which are primarily Windows tools. There are no Linux/macOS equivalents or examples for upgrading Service Fabric applications, nor are cross-platform CLI options mentioned. The serialization guidance is C#-centric, but this is appropriate given Service Fabric's .NET focus.
Recommendations
  • Add examples and walkthroughs for upgrading applications using cross-platform tools such as Azure CLI or Service Fabric CLI (sfctl), which are available on Linux/macOS.
  • Mention and link to Linux/macOS-compatible upgrade documentation where possible.
  • Clarify that Visual Studio and PowerShell are Windows-centric, and provide alternative instructions for non-Windows users.
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 Service Fabric's periodic backup configuration in a platform-neutral way, but the only on-premises backup storage example given is a Windows file share (with Windows authentication and UNC paths). There are no examples or mentions of Linux-compatible storage options (such as NFS or SMB mounts on Linux), nor guidance for Linux clusters. This creates friction for Linux users seeking to configure on-premises backups.
Recommendations
  • Add examples and guidance for configuring backup storage using Linux-compatible file shares (e.g., NFS, SMB mounts) for standalone clusters.
  • Clarify whether the file share backup storage option is supported on Linux Service Fabric clusters, and if so, provide sample paths and authentication methods relevant to Linux.
  • Mention any limitations or alternative approaches for Linux clusters if Windows file shares are not supported.
  • Consider including a note or section on cross-platform compatibility for backup storage options.
GitHub Create Pull Request
Service Fabric Application upgrade: upgrade parameters ...abric/service-fabric-application-upgrade-parameters.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page presents PowerShell and Visual Studio parameters and examples before SFCTL (Service Fabric CLI), which is the cross-platform tool for Linux and macOS. The parameter tables and explanations are heavily focused on PowerShell and Visual Studio, with SFCTL covered in a separate section. There are no explicit Linux/macOS-specific examples or parity notes, and Windows tools are mentioned first throughout.
Recommendations
  • Reorganize the documentation so that SFCTL (cross-platform CLI) is presented before or alongside PowerShell and Visual Studio, emphasizing its use for Linux/macOS users.
  • Add explicit Linux/macOS examples using SFCTL, including sample commands and parameter usage.
  • Clarify which tools are platform-specific and which are cross-platform, ideally in an introductory section.
  • Ensure parameter tables include SFCTL equivalents where applicable, or provide a unified comparison table.
  • Consider adding a section or callout for Linux/macOS users to highlight relevant tools and workflows.
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 presented as a separate section and is Windows-centric. In the cluster upgrade section, only PowerShell commands are given for manual upgrades, with no Linux shell (bash) or cross-platform alternatives. Windows registry keys and Windows-specific VM template properties are discussed without Linux equivalents or guidance. Windows configuration details are presented before Linux, and Linux-specific upgrade instructions are missing.
Recommendations
  • Add Linux/bash examples for manual cluster upgrades, especially for operations currently shown only in PowerShell.
  • Include Linux-specific guidance for disabling automatic updates and patch management, mirroring the Windows registry and VM template instructions.
  • Where possible, present cross-platform tools and commands (e.g., Azure CLI, REST API) before Windows-specific tools.
  • Clarify when instructions are Windows-only and provide links or references to Linux equivalents.
  • Ensure parity in upgrade and patching guidance for Linux clusters.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager - Application Groups ...ice-fabric-cluster-resource-manager-application-groups.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation provides only PowerShell and C# examples for managing Service Fabric Application Groups, with no mention of Linux-compatible CLI tools (such as Azure CLI or REST API) or Bash scripting. All command-line examples use PowerShell cmdlets, which are Windows-centric and may not be available or convenient for Linux/macOS users. There is no guidance or parity for Linux users on how to perform equivalent operations.
Recommendations
  • Add Azure CLI examples for all PowerShell cmdlets shown, as Azure CLI is cross-platform and works on Linux/macOS.
  • Mention REST API endpoints for relevant operations, with example requests.
  • Clarify whether PowerShell cmdlets are available on Linux (via PowerShell Core), and if so, provide installation guidance; if not, offer alternatives.
  • Consider including Bash scripting examples or references for Linux users.
  • Explicitly state any limitations or differences for Linux/macOS users when using Service Fabric management tools.
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 exclusively referencing PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) and linking to Windows Server-specific guides. There are no Linux command examples or references to Linux tools for cluster scaling, and the process is described only in Windows-centric terms.
Recommendations
  • Add equivalent Linux command-line examples (e.g., using sfctl or REST APIs) for cluster scaling operations.
  • Clarify whether standalone Service Fabric clusters can be managed/scaled on Linux, and provide guidance if so.
  • Link to Linux-specific documentation or note limitations if Linux management is not supported.
  • Present both Windows and Linux procedures side-by-side where applicable.
GitHub Create Pull Request
Service Fabric Upgrade an Azure Service Fabric standalone cluster ...ce-fabric/service-fabric-cluster-upgrade-standalone.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page references Windows-specific upgrade and configuration guides (e.g., links ending with '-windows-server.md') and the Patch Orchestration Application for Windows, without mentioning Linux equivalents or providing Linux-specific instructions. There are no explicit Linux examples or guidance, and Windows is implicitly prioritized.
Recommendations
  • Add links and instructions for Linux-based Service Fabric standalone clusters, if supported.
  • Clarify in each section whether the guidance applies to both Windows and Linux, or only Windows.
  • Provide Linux-specific examples for cluster upgrades, configuration, and patch orchestration if available.
  • If Linux is not supported for standalone clusters, state this explicitly to avoid confusion.
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 platform-neutral, but there are a few areas where Windows-specific terminology and tools are mentioned first or exclusively. For example, the 'Node' definition references an auto-start Windows service and Windows executables (FabricHost.exe, Fabric.exe, FabricGateway.exe) without mentioning Linux equivalents or clarifying Linux behavior. The 'Code package' section references EXE/DLL files, which are Windows formats, and does not mention Linux binaries. However, the page does acknowledge Linux support in several places, such as container support and development clusters.
Recommendations
  • Clarify Linux node behavior: In the 'Node' section, add information about how Service Fabric nodes operate on Linux, including relevant processes or services.
  • Mention Linux binary formats: In the 'Code package' section, note that Linux services may use ELF binaries or other executable formats.
  • Balance Windows/Linux references: When referencing Windows-specific tools or services, add equivalent Linux information or explicitly state differences.
  • Add Linux examples: Where possible, provide examples or notes for Linux users alongside Windows references.
GitHub Create Pull Request
Service Fabric Fault Analysis Service overview .../service-fabric/service-fabric-testability-overview.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page for the Fault Analysis Service overview provides usage instructions primarily for C# and PowerShell, with explicit mention of the Service Fabric SDK and PowerShell module installation. There are no examples or guidance for Linux/macOS users, such as using CLI tools or REST APIs, nor is there mention of cross-platform alternatives. The PowerShell focus and lack of Linux-specific instructions create friction for non-Windows users.
Recommendations
  • Add examples for using the Fault Analysis Service via Azure CLI or REST API, which are cross-platform.
  • Clarify whether the Fault Analysis Service APIs can be accessed from Linux/macOS environments, and provide relevant instructions.
  • Mention any limitations or requirements for Linux users, such as SDK availability or cluster configuration.
  • Provide links or references to Linux/macOS-compatible tools for managing Service Fabric clusters and invoking Fault Analysis Service actions.
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 modifying Service Fabric managed cluster node types using the Azure Portal, ARM templates, and PowerShell. PowerShell is the only CLI example provided, with no mention of Azure CLI or Bash equivalents. PowerShell is a Windows-centric tool, and its exclusive use creates friction for Linux/macOS users. Additionally, PowerShell examples are given for every operation (add, remove, scale, configure placement properties), and are presented alongside or after portal and ARM template methods, but never with Linux-friendly CLI options.
Recommendations
  • Add Azure CLI examples for all operations (add, remove, scale, configure placement properties, etc.) to ensure Linux/macOS users have parity.
  • Explicitly mention that PowerShell examples are Windows-centric and provide links or guidance for Linux/macOS users.
  • Where possible, clarify if ARM template operations can be performed equally from Linux/macOS environments (e.g., using Azure CLI or REST API).
  • Consider including Bash scripts or references to cross-platform tools for cluster management.
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 ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page for Initializer CodePackages in Service Fabric presents only Windows container examples, referencing Windows-specific images (mcr.microsoft.com/windows/nanoserver:1809), Windows paths (C:\...), and Windows shell commands (cmd, echo, type, ping). There are no Linux container examples, nor any mention of Linux-compatible patterns, tools, or file paths. The page assumes familiarity with creating Windows container applications and does not provide parity for Linux users.
Recommendations
  • Add a complete example using Linux containers (e.g., mcr.microsoft.com/ubuntu or other Linux images), with Linux shell commands (bash, echo, cat, etc.) and Linux file paths (/workspace/log.txt).
  • Clarify whether Initializer CodePackages are supported for Linux containers and, if so, provide guidance and examples for Linux users.
  • If Initializer CodePackages are Windows-only, explicitly state this at the top of the article to avoid confusion for Linux users.
  • Ensure that references to container creation and Service Fabric usage include links and guidance for both Windows and Linux environments.
GitHub Create Pull Request
Service Fabric Migrate an Azure Service Fabric cluster to availability zone support ...ce-fabric/migrate-service-fabric-availability-zones.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides extensive PowerShell examples for migration steps, especially in the 'Basic SKU load balancer and IP resources' scenario. PowerShell commands and Windows-specific paths (e.g., 'D:\\SvcFab') are used throughout, and Windows-based sample templates are referenced before Linux equivalents. There is minimal guidance or examples for Linux/macOS users, and the only Linux sample template is mentioned in passing without corresponding CLI or Bash instructions.
Recommendations
  • Add Azure CLI or Bash script equivalents for all PowerShell migration steps, especially for resource deployment, node disabling, and DNS updates.
  • Reference Linux/Ubuntu sample templates alongside Windows ones, and provide clear instructions for Linux-based clusters.
  • Avoid using Windows paths (e.g., 'D:\\SvcFab') in generic examples; use platform-neutral or Linux paths where appropriate.
  • Ensure that all critical operations (e.g., node management, resource cleanup) are documented with cross-platform tooling.
  • Explicitly state when a step is Windows-only and provide alternatives for Linux/macOS users.
GitHub Create Pull Request
Service Fabric X.509 Certificate-based Authentication in a Service Fabric Cluster ...ticles/service-fabric/cluster-security-certificates.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation provides a generally cross-platform overview of X.509 certificate-based authentication in Service Fabric clusters, but there are several areas where Windows bias is evident. Windows certificate store paths (e.g., LocalMachine\My) and Windows-specific troubleshooting tools (e.g., CAPI2 logging, Win32 CryptoAPI references) are mentioned first or exclusively, with Linux equivalents only briefly referenced or omitted. Troubleshooting and configuration examples focus on Windows-centric patterns, and some error codes and provider types are Windows-specific.
Recommendations
  • Wherever Windows certificate store paths are mentioned (e.g., LocalMachine\My), provide the Linux equivalent (e.g., /var/lib/sfcerts) with equal prominence and detail.
  • In troubleshooting sections, add Linux-specific guidance, such as relevant log file locations, commands (e.g., using OpenSSL or Linux system logs), and error messages.
  • When referencing Windows-specific tools (e.g., CAPI2 logging, Win32 CryptoAPI), also mention Linux alternatives or clarify which steps are Windows-only.
  • For error codes and cryptographic provider types, note any Linux-specific equivalents or differences, or explicitly state if a concept is Windows-only.
  • Ensure all configuration examples and explanations are clearly applicable to both Windows and Linux clusters, or provide parallel examples where necessary.
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 includes a PowerShell-only example for bypassing Infrastructure Service, and references Service Fabric Explorer (a GUI tool typically used on Windows). No Linux/macOS equivalent commands or tools are mentioned, and the PowerShell command is presented as the sole method for manual intervention.
Recommendations
  • Provide equivalent CLI examples for Linux/macOS users, such as using Azure CLI or REST API if available.
  • Mention whether the PowerShell command can be run via PowerShell Core on Linux/macOS, or clarify if it is Windows-only.
  • Include instructions for accessing Service Fabric Explorer from non-Windows platforms, or alternative troubleshooting methods.
  • Add notes about cross-platform support for Service Fabric management 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 is a notable tendency to mention Windows tools and patterns first, such as EventStore APIs being Windows-only, Event Log/Event Viewer, and Diagnostics Agent. Linux equivalents are sometimes referenced later or in passing, and some examples/tutorials focus on .NET/Windows scenarios. There are also sections where Linux-specific guidance is less detailed or deferred to linked pages, and some Windows-specific features (like EventStore APIs) lack Linux alternatives.
Recommendations
  • Ensure Linux monitoring tools and patterns are described with equal prominence and detail as Windows equivalents.
  • Provide Linux-specific examples and walkthroughs alongside Windows/PowerShell examples, especially for cluster and infrastructure monitoring.
  • Clarify when features are Windows-only and offer alternative Linux guidance or links where possible.
  • Add explicit Linux-focused tutorials for application monitoring and diagnostics, not just .NET/Windows.
  • Where EventStore APIs are Windows-only, highlight Linux alternatives (such as querying Syslog or using LTTng) with practical examples.
GitHub Create Pull Request
Service Fabric Learn about Azure Service Fabric application security ...ric/service-fabric-application-and-service-security.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation provides several examples and references that are Windows-centric, such as running services under Active Directory domain accounts, gMSA, BitLocker, and PowerShell disk encryption. Linux equivalents are either missing, mentioned only in passing, or flagged as 'TO DO' items. Windows-specific tools and patterns (e.g., BitLocker, PowerShell) are referenced without Linux alternatives or parity.
Recommendations
  • Add explicit Linux examples for running services under local user accounts, securing resources, and disk encryption.
  • Provide guidance or links for Linux disk encryption (e.g., using dm-crypt/LUKS) in the 'Encrypt application data at rest' section.
  • Ensure that Linux container security features are described with equal detail as Windows/gMSA.
  • Where Windows tools (e.g., PowerShell, BitLocker) are referenced, include Linux equivalents or note platform differences.
  • Review and update 'TO DO' sections to provide actionable Linux guidance.
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 throughout critical lifecycle phases (deploy, upgrade, remove, maintenance). While REST API and .NET methods are also mentioned, PowerShell examples and terminology are prominent and often listed first. There is little explicit mention of Linux-native CLI tools (such as sfctl or Azure CLI) or Linux/macOS workflows, despite Service Fabric supporting cross-platform clusters and management.
Recommendations
  • Add examples and references for Linux/macOS users, such as using sfctl and Azure CLI commands for each lifecycle phase.
  • Where PowerShell cmdlets are mentioned, also provide equivalent sfctl or Azure CLI commands, ideally side-by-side.
  • Clarify which management operations are cross-platform and which are Windows-only, to help users choose the right tools.
  • Update 'Preserving disk space' and 'Cleaning up files' sections to include Linux-native approaches and commands.
  • Consider linking to or embedding Linux/macOS-specific guides for Service Fabric application lifecycle management.
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: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page for on-demand backup in Azure Service Fabric is heavily focused on PowerShell and Windows tooling. All command-line examples use PowerShell, including REST API calls, and require installation of a PowerShell module (Microsoft.ServiceFabric.Powershell.Http). There are no examples or guidance for Linux/macOS users, such as using Bash, curl, or cross-platform Service Fabric CLI tools. The documentation assumes the use of Windows-centric tools and patterns throughout, creating friction for Linux/macOS users.
Recommendations
  • Add equivalent Bash/curl examples for REST API calls, showing how to trigger backups and track progress from Linux/macOS.
  • Document any cross-platform Service Fabric CLI tools (e.g., sfctl) and provide usage examples.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is required for all scenarios, or if REST API calls can be made directly from any platform.
  • Explicitly state platform requirements and provide guidance for Linux/macOS users where possible.
  • Reorder examples to show cross-platform approaches first, or at least in parallel with PowerShell.
GitHub Create Pull Request
Service Fabric Advanced Application Upgrade Topics ...-fabric/service-fabric-application-upgrade-advanced.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides extensive PowerShell examples and references, with no mention of Linux/macOS CLI equivalents (such as Azure CLI or REST API). Windows/PowerShell tools and cmdlets are used exclusively for all upgrade operations, and PowerShell examples are shown first or only. There is no guidance for Linux/macOS users on how to perform these tasks, creating friction for non-Windows users.
Recommendations
  • Add Azure CLI examples for all upgrade operations, including creating, updating, and rolling back Service Fabric applications.
  • Include REST API references and sample payloads for relevant operations.
  • Clarify which operations are only possible via PowerShell, if any, and provide alternatives or workarounds for Linux/macOS users.
  • Add notes or sections indicating cross-platform support and parity, and link to relevant Linux/macOS documentation.
  • Ensure that ARM template examples are accompanied by CLI/REST instructions for deployment.
GitHub Create Pull Request
Service Fabric Service Fabric application upgrade ...s/service-fabric/service-fabric-application-upgrade.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page for Service Fabric application upgrade exhibits a notable Windows bias. PowerShell is used exclusively in code examples, and Windows-specific tools (such as http.sys and PowerShell cmdlets) are referenced without Linux equivalents or alternatives. There are no examples or guidance for Linux/macOS users, and Windows terminology and tools are mentioned first and exclusively throughout the article.
Recommendations
  • Add CLI (sfctl) examples alongside PowerShell for application upgrade operations, as sfctl is cross-platform and supported on Linux/macOS.
  • Explicitly mention any differences or limitations for Linux clusters, especially regarding certificate management and port usage.
  • Provide guidance or links for Linux/macOS users on how to perform upgrades, including relevant commands and tools.
  • Clarify which features or steps are Windows-only, and offer alternatives or workarounds for Linux environments 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 mentions PowerShell cmdlets as a primary management interface for Service Fabric, without referencing Linux or cross-platform equivalents (such as Azure CLI or REST APIs). Additionally, Windows security is mentioned alongside X509 certificates in the transport subsystem, with no explicit mention of Linux authentication mechanisms. These choices suggest a Windows-first bias in management and security examples.
Recommendations
  • Add references to cross-platform management tools such as Azure CLI and REST APIs, highlighting their parity with PowerShell cmdlets.
  • Clarify authentication options for Linux-based clusters, including how X509 certificates are used and whether Linux equivalents to Windows security exist.
  • Ensure examples and tooling references are balanced, mentioning Linux-compatible approaches where applicable.
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 is heavily biased toward Windows/PowerShell usage. All command-line examples use PowerShell, including REST API calls, and require installation of a Microsoft.ServiceFabric.Powershell.Http module. There are no examples for Linux/macOS users (e.g., Bash, curl, or Azure CLI), nor is there guidance for using cross-platform tools. The documentation assumes the reader is using Windows and PowerShell, which creates friction for Linux/macOS users.
Recommendations
  • Add equivalent Bash/curl examples for REST API calls, showing how to authenticate and trigger restores from Linux/macOS.
  • Document how to use Azure CLI or other cross-platform tools for backup/restore operations, if supported.
  • Clarify if the Microsoft.ServiceFabric.Powershell.Http module is required only on Windows, and provide alternatives for Linux/macOS users.
  • Provide guidance for connecting to Service Fabric clusters from Linux/macOS, including certificate handling.
  • Consider reordering sections so that REST API usage is shown in a generic, cross-platform way first, then PowerShell as a specific example.
GitHub Create Pull Request
Service Fabric Capacity planning and scaling for Azure Service Fabric ...bric/service-fabric-best-practices-capacity-scaling.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides several manual scaling steps and examples using PowerShell cmdlets (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState) without mentioning Linux equivalents or cross-platform alternatives. Additionally, PowerShell-based instructions are presented first and most prominently in scaling sections, while Linux-specific guidance is not provided. However, the page does reference Linux cluster creation in the 'Next steps' section, indicating Service Fabric supports Linux, but the operational guidance is Windows-centric.
Recommendations
  • Add equivalent Linux command-line instructions (e.g., using sfctl or REST API) alongside PowerShell examples for scaling operations.
  • Explicitly state which steps are Windows-only and provide Linux alternatives where possible.
  • Include cross-platform guidance for cluster management tasks, such as node deactivation and removal.
  • Consider providing sample scripts or walkthroughs for Linux users using Service Fabric CLI (sfctl) or REST API.
  • Ensure parity in example ordering, so Linux instructions are not always secondary.
GitHub Create Pull Request
Service Fabric Azure Service Fabric networking best practices ...ice-fabric/service-fabric-best-practices-networking.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation presents some Windows bias, notably in the order and prominence of Windows-specific examples and tools. PowerShell and Windows-centric patterns are mentioned first or exclusively in several sections, such as API endpoints, DevOps integration, and application networking. Linux equivalents are sometimes referenced but often lack parity in example detail or are mentioned after Windows. Some tooling and operational guidance (e.g., PowerShell APIs, Windows container networking) are Windows-focused, and Linux-specific instructions or examples are sparse or missing.
Recommendations
  • Provide Linux CLI (az CLI, bash) examples alongside PowerShell for cluster management and networking tasks.
  • Ensure Linux-specific guidance is given equal prominence and detail, especially for API access, DevOps integration, and application networking.
  • Include references to Linux-native tools and patterns (e.g., systemd, iptables, Linux firewall configuration) where relevant.
  • Add explicit examples for Linux container networking and operational scenarios, not just Windows containers.
  • Review order of presentation so Linux and Windows are treated equally (e.g., mention both in parallel, not always Windows first).
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 ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation provides both Windows and Linux guidance for key security tasks, but Windows-specific tools (PowerShell, Windows Defender, DSC) are mentioned first or exclusively in several sections. Windows examples and terminology are often presented before Linux equivalents, and some sections (e.g., Windows Defender, DSC) are Windows-only without Linux alternatives or clarifications.
Recommendations
  • Ensure Linux examples are presented alongside Windows examples, not after them, especially in sections about certificate generation and secret encryption.
  • Where Windows-specific tools (e.g., PowerShell, Windows Defender, DSC) are discussed, add explicit notes or links to Linux alternatives or clarify their absence.
  • For security baseline recommendations, mention Linux security best practices (e.g., CIS benchmarks, SELinux/AppArmor) in addition to Windows baselines.
  • In sections about firewall rules and outbound traffic, clarify any Linux-specific considerations or tools for managing network security.
  • Consider alternating the order of Windows and Linux examples to avoid implicit prioritization.
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 consistently provides PowerShell examples for configuring Service Fabric placement policies, but does not offer equivalent CLI or scripting examples for Linux/macOS users. All command-line examples are PowerShell-centric, and no mention is made of cross-platform tools such as Azure CLI or REST API methods. The PowerShell examples are presented immediately after the C# code snippets, reinforcing a Windows-first approach.
Recommendations
  • Add Azure CLI examples for each placement policy configuration, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include REST API or ARM template examples where applicable, to provide platform-neutral alternatives.
  • Explicitly note any limitations or differences for Linux-based Service Fabric clusters, if present.
  • Consider reorganizing examples so that cross-platform methods (e.g., Azure CLI, REST API) are shown before or alongside PowerShell, rather than after.
  • Mention the availability of Service Fabric tools for Linux, such as sfctl, and provide usage examples.
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: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page discusses Azure Service Fabric node types and their relationship to virtual machine scale sets. While it mentions both Windows and Linux node types in the extension properties, the JSON example and property descriptions show Windows-centric defaults (e.g., 'dataPath': 'D:\\SvcFab', certificate store values), and the 'Next steps' section links primarily to Windows/PowerShell-specific tasks (RDP port range, admin username/password changes) without Linux equivalents or guidance for SSH access. Linux-specific examples and parity in operational guidance are missing.
Recommendations
  • Provide Linux-specific examples for configuration, such as using Linux file paths (e.g., '/var/svcfab') in the 'dataPath' property.
  • Add guidance or links for Linux users on how to remotely connect to cluster nodes (e.g., SSH instructions) alongside RDP/PowerShell examples.
  • Include Linux admin credential management instructions, or clarify if the linked scripts are Windows-only.
  • Ensure property descriptions and extension examples alternate or equally represent Linux and Windows scenarios.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Auto Scaling Services and Containers ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-autoscaling.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides detailed examples for configuring auto scaling in Azure Service Fabric using application manifests, C# APIs, and PowerShell. However, PowerShell is a Windows-centric tool, and no equivalent Linux/macOS CLI or scripting examples (such as Bash, Azure CLI, or REST API) are provided. Additionally, PowerShell examples are presented alongside C# and manifest examples, but Linux-native options are missing, creating friction for Linux users. The documentation also mentions that resource monitoring is supported for containerized applications on Linux, but does not provide Linux-specific guidance or examples.
Recommendations
  • Add Azure CLI or Bash script examples for configuring scaling policies, especially for Linux/macOS users.
  • Explicitly mention any limitations or differences for Linux clusters and provide guidance for Linux users.
  • Include REST API usage examples for cross-platform parity.
  • Clarify which PowerShell commands (e.g., Update-ServiceFabricService, New-ServiceFabricService) are available or supported on Linux, or provide alternatives.
GitHub Create Pull Request
Service Fabric Describe a cluster by using Cluster Resource Manager ...ce-fabric-cluster-resource-manager-cluster-description.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides configuration examples for both Windows (ClusterManifest.xml) and cross-platform/standalone (ClusterConfig.json) deployments. However, Windows-specific configuration (ClusterManifest.xml under <WindowsServer>) is presented first and more prominently, and PowerShell examples are included for service management. There is no explicit mention of Linux-specific node configuration or tools, nor are Linux/macOS command-line examples provided. The documentation assumes familiarity with Windows Server concepts and tools, which may create friction for Linux users.
Recommendations
  • Add explicit examples and guidance for Linux-based Service Fabric clusters, including configuration of ClusterManifest.xml for Linux nodes (using <Linux> or <LinuxServer> tags if supported).
  • Provide Linux/macOS command-line equivalents for PowerShell commands (e.g., using sfctl or REST API).
  • Clarify which configuration files and approaches are cross-platform, and highlight Linux-specific differences or requirements.
  • Ensure that Linux node configuration is not only mentioned but also demonstrated alongside Windows examples.
  • Where possible, avoid presenting Windows examples first unless the feature is 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 page provides code examples for managing Service Fabric app load using metrics primarily in C# and PowerShell. PowerShell is a Windows-centric tool, and no equivalent Linux/macOS CLI examples (such as Azure CLI or bash scripts) are provided. The PowerShell examples are presented alongside C# code, but there is no mention of cross-platform alternatives or how Linux users can accomplish the same tasks. This creates friction for Linux/macOS users, as Service Fabric supports Linux clusters and cross-platform management.
Recommendations
  • Add Azure CLI examples for service creation and metric configuration, which are cross-platform and supported on Linux/macOS.
  • Mention and link to documentation about managing Service Fabric clusters from Linux, including REST API usage or SDKs.
  • Clarify which PowerShell commands are available via Azure CLI or REST API, and provide those alternatives where possible.
  • Explicitly state if certain operations are only possible via PowerShell, and provide guidance for Linux users.
  • Consider including bash script examples or references to the Service Fabric CLI (sfctl), which is available on Linux.
GitHub Create Pull Request
Service Fabric Azure Service Fabric dynamic node tags ...tps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-node-tagging.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page provides PowerShell examples for managing node tags and service tag requirements, but does not offer equivalent examples for Linux/macOS users (e.g., Bash, CLI, or REST API usage). PowerShell is primarily a Windows tool, and its exclusive use creates friction for users on other platforms. The C# API examples are cross-platform, but many administrators expect command-line examples for operational tasks.
Recommendations
  • Add Azure CLI or Bash examples for managing node tags and service tag requirements, if supported.
  • Include REST API usage examples for tag operations, as REST APIs are platform-agnostic.
  • Clarify whether PowerShell commands are available cross-platform (PowerShell Core), and if so, provide guidance for Linux/macOS users.
  • Mention any limitations or alternatives for Linux/macOS users if PowerShell is required.
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 discusses securing Azure Service Fabric clusters, covering both Azure-hosted and standalone Windows clusters. However, it repeatedly references Windows Server clusters and Windows-specific security mechanisms (e.g., Windows security, Kerberos, group Managed Service Accounts) without mentioning or providing equivalent guidance for standalone Linux clusters. Examples and links for standalone clusters are exclusively for Windows, and Linux is only mentioned in passing, with no actionable instructions or references for Linux users.
Recommendations
  • Add explicit guidance and links for securing standalone Linux Service Fabric clusters, including certificate setup and any Linux-specific security mechanisms.
  • Provide parity in examples and walkthroughs for Linux clusters, such as how to generate and install certificates on Linux nodes, and how to configure client-to-node and node-to-node security.
  • Clarify which security scenarios and recommendations apply equally to Linux and Windows, and highlight any differences.
  • If standalone Linux clusters are not supported, state this clearly to avoid confusion.
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 supports cross-platform management, the exclusive use of PowerShell creates friction for Linux/macOS users.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl) for Linux/macOS users.
  • Include REST API examples for health reporting and querying, which are platform-agnostic.
  • Clarify in the example section that PowerShell is Windows-specific and provide links or instructions for Linux/macOS alternatives.
GitHub Create Pull Request
Service Fabric Cluster Resource Manager - Management Integration ...fabric-cluster-resource-manager-management-integration.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides a PowerShell example for querying Service Fabric partition health, using a Windows-style prompt and command. No equivalent Linux or cross-platform CLI example is given. The example is presented early in the page, and the use of PowerShell and Windows paths may create friction for Linux/macOS users. However, the rest of the documentation is largely conceptual and platform-neutral.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl) or REST API for Linux/macOS users.
  • Include notes clarifying cross-platform management options and tools.
  • Present examples for both Windows and Linux environments, or use platform-neutral commands 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 provides PowerShell and C# examples for configuring movement cost in Service Fabric, but does not include equivalent Linux/bash/CLI examples. PowerShell is Windows-centric, and its exclusive use creates friction for Linux/macOS users. The order of examples also places Windows tools first, reinforcing Windows bias.
Recommendations
  • Add Azure CLI or bash examples for configuring move cost, where possible.
  • Explicitly mention whether PowerShell commands are supported on Linux/macOS (via PowerShell Core), or provide alternatives.
  • Clarify if certain operations are only possible via PowerShell or C# SDK, and note Linux/macOS limitations if any.
  • Consider including REST API or cross-platform SDK examples for dynamic configuration tasks.
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 in Azure Service Fabric, but does not offer equivalent CLI or scripting examples for Linux/macOS users. PowerShell is presented as the primary scripting interface, and no mention is made of cross-platform alternatives such as Azure CLI or REST API. This creates friction for Linux/macOS administrators, who may not have access to PowerShell or prefer other tools.
Recommendations
  • Add Azure CLI examples for all operations currently shown with PowerShell.
  • Mention REST API endpoints or provide relevant REST payloads for cross-platform automation.
  • Clarify whether PowerShell examples are usable on Linux/macOS (e.g., via PowerShell Core), or provide guidance for Linux users.
  • Ensure that scripting examples are balanced, showing both Windows and Linux/macOS approaches where possible.
GitHub Create Pull Request
Service Fabric Azure Service Fabric application resource model ...ervice-fabric/service-fabric-concept-resource-model.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a notable Windows bias. All deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) without any Azure CLI or Bash equivalents. The application packaging step is described using Visual Studio, a Windows-centric tool, with no mention of cross-platform alternatives. There are no Linux/macOS-specific instructions or examples, and Windows tools and patterns are presented first and exclusively.
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, SF tooling, or manual zip commands).
  • Mention and link to Linux/macOS-compatible workflows for staging and uploading application packages (e.g., using az storage blob upload).
  • Present Windows and Linux/macOS examples in parallel, or clarify when steps are Windows-only.
  • Include guidance for users working on non-Windows platforms, such as using VS Code or command-line tools instead of Visual Studio.
GitHub Create Pull Request
Service Fabric Azure Service Fabric hosting model ...rticles/service-fabric/service-fabric-hosting-model.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides PowerShell examples and references PowerShell cmdlets for managing Service Fabric services, but does not include equivalent Linux CLI (sfctl) or bash examples. Windows tooling (PowerShell) is mentioned first and exclusively in code samples and links, creating friction for Linux/macOS users who must translate instructions to their platform.
Recommendations
  • Add equivalent examples using sfctl (Service Fabric CLI) for Linux/macOS users alongside PowerShell examples.
  • Mention both PowerShell and sfctl tools in relevant sections, clarifying platform applicability.
  • Provide links to Linux/macOS documentation and tools where PowerShell is referenced.
  • Consider showing Linux/macOS examples before or alongside Windows examples to improve parity.
GitHub Create Pull Request
Service Fabric Upgrading Azure Service Fabric clusters ...icles/service-fabric/service-fabric-cluster-upgrade.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page on upgrading Azure Service Fabric clusters exhibits mild Windows bias. While most upgrade concepts are platform-neutral, several sections reference Windows-specific tools (PowerShell) and link to Windows-only procedures (e.g., patching cluster nodes). Linux equivalents are not mentioned or are referenced after Windows tools. The 'Upgrading OS images for cluster nodes' section links only to Windows patching guidance, omitting Linux guidance. Examples for managing certificates, ports, and other cluster properties mention PowerShell/Azure CLI, but do not clarify Linux support or provide Linux-specific examples.
Recommendations
  • Add explicit references and links to Linux patching/upgrading guidance for Service Fabric clusters, if available.
  • Provide examples for managing certificates, ports, and cluster settings using Azure CLI or other cross-platform tools, and clarify their applicability to Linux clusters.
  • When mentioning PowerShell, also mention Bash/CLI usage for Linux/macOS users, or provide equivalent commands.
  • Ensure that upgrade procedures and automation guidance are clearly marked as Windows-only when applicable, and provide Linux alternatives where possible.
GitHub Create Pull Request
Service Fabric Scalability of Service Fabric services .../service-fabric/service-fabric-concepts-scalability.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides code examples and administrative instructions primarily using PowerShell, which is a Windows-centric tool. There are no equivalent Linux CLI or scripting examples (e.g., Bash, Azure CLI) for scaling operations. Windows/PowerShell tools are mentioned first and exclusively, creating friction for Linux users who may not have access to PowerShell or prefer native Linux tooling. The only explicit mention of Linux is in the 'Choosing a platform' section, which discusses implementation differences but does not provide Linux-specific operational guidance.
Recommendations
  • Add equivalent Linux examples using Bash, Azure CLI, or REST API calls for scaling operations.
  • Document Linux-native workflows for managing Service Fabric clusters and services.
  • Where PowerShell is referenced, clarify if cross-platform PowerShell Core is supported, or provide alternative instructions for Linux users.
  • Ensure administrative actions (e.g., creating/removing services) are demonstrated with both Windows and Linux tools.
  • Consider listing Linux examples before or alongside Windows examples to improve parity.
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 and executables (e.g., FabricHost.exe, PowerShell cmdlets) are mentioned first or exclusively in several sections. Examples and instructions often reference Windows concepts and tools before Linux equivalents, and some features (like standalone clusters) are only supported on Windows, with Linux support explicitly missing. Linux tools, CLI usage, and Linux-specific guidance are less prominent or missing in some sections.
Recommendations
  • Ensure that Linux equivalents (e.g., CLI commands, Linux service management) are mentioned alongside Windows tools, not just as secondary options.
  • Provide Linux-specific examples and workflows where possible, especially for cluster management, health monitoring, and application lifecycle.
  • Clarify which features are Windows-only and which are cross-platform, and link to Linux-specific documentation when available.
  • Include Linux-first or Linux-parity sections for critical tasks, such as cluster creation, scaling, upgrades, and monitoring.
  • Avoid referencing Windows executables (e.g., FabricHost.exe) without also describing Linux equivalents or noting differences.
GitHub Create Pull Request
Service Fabric Package an existing executable to Azure Service Fabric ...abric/service-fabric-guest-executables-introduction.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page shows evidence of Windows bias. It references the Service Fabric SDK schema location using a Windows file path, mentions Visual Studio as a primary packaging tool, and does not provide Linux/macOS equivalents or examples for packaging or deploying guest executables. There are no explicit Linux command-line instructions or references to cross-platform tools, and the directory structure example uses a Windows executable (.exe) without mentioning Linux binaries.
Recommendations
  • Add instructions and examples for packaging and deploying guest executables using Linux/macOS command-line tools.
  • Mention cross-platform alternatives to Visual Studio, such as Azure CLI or Service Fabric CLI (sfctl), and provide sample commands.
  • Reference the schema location for ApplicationManifest.xml and ServiceManifest.xml in a platform-agnostic way, or note the Linux/macOS equivalent if available.
  • Include examples using Linux binaries (e.g., .sh or ELF files) alongside Windows executables (.exe) in the directory structure.
  • Clarify if the packaging process is supported on Linux/macOS, and link to relevant documentation or tools.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Events ...es/service-fabric/service-fabric-diagnostics-events.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page for Azure Service Fabric Events primarily references Windows-specific tools and patterns, such as ETW/Windows Event logs and the Windows Azure diagnostics agent, without mentioning Linux equivalents or providing Linux-specific guidance. Windows tools are mentioned first and exclusively, and there are no examples or instructions for accessing Service Fabric events on Linux clusters.
Recommendations
  • Add documentation on how Service Fabric events are logged and accessed on Linux clusters, including any differences in logging mechanisms (e.g., use of stdout/stderr, syslog, or other Linux-native logging solutions).
  • Provide examples or references for monitoring tools and log aggregation solutions commonly used on Linux, such as Azure Monitor integration for Linux, or instructions for configuring diagnostics on Linux nodes.
  • Clarify whether the EventStore service's REST APIs and Service Fabric Client Library are fully cross-platform, and provide usage examples for Linux environments.
  • If certain features (like ETW/Windows Event logs) are Windows-only, explicitly state this and offer Linux alternatives or workarounds.
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 tools and patterns (PowerShell, ApplicationManifest.xml, Visual Studio) are mentioned before Linux alternatives, and Linux-specific limitations are discussed but not accompanied by Linux-centric guidance or examples. The documentation assumes Windows-centric workflows, creating friction for Linux users.
Recommendations
  • Add Azure CLI or Bash examples for setting DNS names and managing Service Fabric services, especially for Linux clusters.
  • Include guidance for Linux users on how to perform equivalent tasks (e.g., using ARM templates, Docker Compose, or REST APIs) instead of PowerShell.
  • Clarify Linux limitations and provide workarounds or links to Linux-specific documentation.
  • Present Windows and Linux options side-by-side or clearly indicate which steps are Windows-only and which are cross-platform.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Docker Compose Deployment Preview ...ticles/service-fabric/service-fabric-docker-compose.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both PowerShell and Service Fabric CLI (sfctl) examples for deploying Docker Compose files, but PowerShell commands are presented first and in greater detail. This may create friction for Linux/macOS users, as PowerShell is primarily a Windows tool, and its usage is emphasized before cross-platform alternatives. However, the inclusion of sfctl CLI commands mitigates the bias, allowing Linux/macOS users to complete the tasks.
Recommendations
  • Present sfctl CLI examples before or alongside PowerShell examples to avoid implying Windows-first workflows.
  • Clarify that sfctl is the recommended cross-platform tool for Linux/macOS users.
  • Explicitly mention platform compatibility for each tool (e.g., 'PowerShell (Windows only)', 'sfctl CLI (cross-platform)').
  • Ensure parity in detail and explanation between PowerShell and sfctl sections.
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: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page references PowerShell as the primary example for interacting with Service Fabric clusters (e.g., retrieving the cluster manifest), and links to PowerShell-based deployment guides in the 'Next steps' section. While .NET and REST are mentioned, PowerShell is presented first and most prominently. There are no explicit Linux or cross-platform CLI examples (such as Azure CLI or Bash), nor is it clarified whether PowerShell Core is supported on Linux/macOS. The overall guidance assumes familiarity with Windows-centric tools and workflows.
Recommendations
  • Add Azure CLI or Bash examples for retrieving cluster manifests and deploying/removing applications, where possible.
  • Clarify whether PowerShell Core on Linux/macOS is supported for Service Fabric operations.
  • Include links to cross-platform deployment documentation or note any limitations for non-Windows users.
  • Balance example ordering so that cross-platform approaches are presented alongside or before Windows-specific tools.
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 Service Fabric application parameters across environments, but it shows a notable Windows bias. PowerShell and Visual Studio (Windows-centric tools) are mentioned first and in detail, while Linux/macOS equivalents (sfctl, install.sh) are referenced later and with less explanation. There are no explicit Linux/macOS-specific examples or guidance, and the workflow is oriented toward Windows tools.
Recommendations
  • Add explicit Linux/macOS examples for parameter passing, such as using sfctl and install.sh, with step-by-step instructions.
  • Provide parity in example scripts for both PowerShell (Windows) and Bash (Linux/macOS).
  • Mention cross-platform tools and workflows before or alongside Windows-specific ones.
  • Clarify which tools are cross-platform and which are Windows-only, to help users choose appropriately.
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 container application manifest examples for Azure Service Fabric, but it is notably Windows-centric. The examples are based on the Windows Server 2016 Container Sample, and references to Windows-specific concepts (such as 'winver' for OS build detection and Windows file paths) appear before or instead of Linux equivalents. There are no explicit Linux container manifest examples or references to Linux-specific patterns, even though Service Fabric supports Linux containers. The certificate handling section does mention Linux (PEM files), but overall, Linux users are left to infer their own adaptations.
Recommendations
  • Add explicit Linux container manifest examples, or clarify which elements are cross-platform.
  • Provide Linux-specific guidance for OS build detection (e.g., using 'uname -r' or '/etc/os-release') alongside 'winver'.
  • Include Linux file path examples (e.g., '/mnt/data') in volume bindings, not just Windows paths (e.g., 'c:\VolumeTest\Data').
  • Reference Linux container samples or link to relevant documentation.
  • Ensure that cross-platform features (such as certificate handling, resource governance, environment variables) are demonstrated for both Windows and Linux containers.
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-centric tools (e.g., RDP, PowerShell) without offering equivalent Linux/macOS instructions or CLI examples. Windows tools and patterns are mentioned first and exclusively, creating friction for Linux/macOS users who may prefer Azure CLI or Bash. No Linux-specific guidance is given for template deployment, VM access, or cluster management.
Recommendations
  • Add Azure CLI (az) command examples for deploying ARM templates, alongside PowerShell.
  • Include instructions for accessing VMs via SSH, not just RDP, and clarify jump box usage for Linux/macOS users.
  • Mention cross-platform tools and patterns (e.g., Bash, Azure CLI, SSH) wherever PowerShell or Windows tools are referenced.
  • Provide sample template deployment steps for Linux/macOS environments.
  • Ensure that examples and guidance are not Windows-first; present cross-platform options equally.
GitHub Create Pull Request
Service Fabric Replica soft delete for enhanced data protection in Service Fabric ...s/service-fabric/service-fabric-replica-soft-delete.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page heavily references PowerShell cmdlets (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica, Get-ServiceFabricReplica) for administrative operations, with no mention of Linux/macOS equivalents or CLI usage. All example commands and API references are Windows-centric, and there is no guidance for users managing Service Fabric clusters from Linux or macOS. This creates friction for non-Windows users, though workarounds may exist via FabricClient APIs or REST endpoints.
Recommendations
  • Add examples using Service Fabric CLI (sfctl), which is cross-platform and supported on Linux/macOS.
  • Document how to perform replica soft delete and restore operations using FabricClient APIs in .NET Core or other cross-platform SDKs.
  • Clarify whether the PowerShell cmdlets are available only on Windows, and provide alternative instructions for Linux/macOS users.
  • Include sample commands and screenshots for Linux/macOS environments where possible.
  • Explicitly state platform limitations if certain features are Windows-only.
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 both Windows-specific (HTTP.sys) and cross-platform (Kestrel) guidance for ASP.NET Core service hosting in Azure Service Fabric. However, Windows tools and patterns (HTTP.sys, Windows HTTP Server API, netsh) are discussed in detail, often before or alongside Linux-compatible options. HTTP.sys is clearly marked as Windows-only, but Windows-centric configuration steps (e.g., netsh, Endpoint configuration for HTTP.sys) are described without Linux equivalents. Visual Studio debugging is referenced as a next step, which is Windows-centric. Kestrel, the cross-platform option, is recommended for Linux, but Windows tools and patterns are prominent throughout.
Recommendations
  • Ensure that Linux/macOS users are guided toward Kestrel as the default/cross-platform option, and make this recommendation more prominent at the start of the article.
  • Where Windows-specific tools (e.g., netsh, HTTP.sys) are discussed, explicitly state that these steps are not applicable to Linux/macOS and provide alternative guidance or clarify that Kestrel should be used.
  • Add a section or callout summarizing Linux/macOS development workflow, including debugging, deployment, and configuration differences.
  • When referencing Visual Studio, mention cross-platform alternatives (e.g., VS Code, CLI tools) for Linux/macOS users.
  • Consider reordering sections so that Kestrel (cross-platform) guidance appears before HTTP.sys (Windows-only) guidance.
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 page provides detailed examples for reporting health in Service Fabric using PowerShell, with explicit PowerShell command snippets and references to Windows paths (e.g., PS C:\>). While API and REST methods are mentioned, only PowerShell is demonstrated in depth, and there are no equivalent Linux/bash CLI examples or references to cross-platform tools. The PowerShell examples are presented before REST, and no mention is made of Azure CLI or bash scripting, which would be relevant for Linux/macOS users.
Recommendations
  • Add equivalent examples using Azure CLI or bash scripts for health reporting, if supported.
  • Clarify whether PowerShell examples are usable on Linux/macOS (via PowerShell Core), and provide guidance if so.
  • Mention REST as a cross-platform method earlier and provide more detailed REST examples, including sample curl commands.
  • Explicitly note any limitations or parity gaps for Linux/macOS users, and link to relevant cross-platform tooling.
  • Consider reordering sections so REST and API examples are presented before or alongside PowerShell.
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 example for deploying Service Fabric applications, which is Windows-centric. Windows file paths and certificate store names are mentioned first, with Linux equivalents referenced only briefly. There are no Linux CLI (e.g., Bash, sfctl) examples for deployment, and Windows terminology/tools appear before Linux alternatives.
Recommendations
  • Add Linux deployment examples using sfctl or Bash scripts alongside the PowerShell example.
  • Mention Linux file paths and certificate store locations earlier and more prominently, not just as a note.
  • Clarify any differences in endpoint configuration or deployment steps for Linux clusters.
  • Where possible, provide cross-platform guidance or links to Linux-specific documentation.
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, with repeated references to Visual Studio-specific actions (Build/Rebuild/F5/Ctrl+F5/Publish) and UI screenshots. There are no examples or guidance for Linux/macOS users or CLI-based workflows. The only mention of non-Visual Studio deployment is a brief reference to ARM and PowerShell cmdlets, but no Linux-native tools or cross-platform CLI instructions are provided.
Recommendations
  • Add explicit guidance for Linux/macOS users, including how to manage StartupServices.xml and ApplicationManifest.xml outside Visual Studio.
  • Provide CLI-based examples (e.g., Azure CLI, Service Fabric CLI) for deploying and configuring applications, not just PowerShell.
  • Clarify which features are Visual Studio-only and offer alternatives for non-Windows environments.
  • Include screenshots or workflow descriptions for cross-platform development environments (e.g., VS Code, JetBrains Rider).
GitHub Create Pull Request
Virtual Machines Associate a virtual machine to a capacity reservation group .../virtual-machines/capacity-reservation-associate-vm.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ powershell_heavy
Summary
The documentation covers both Windows and Linux VMs, but several sections show Windows bias. PowerShell examples are provided alongside CLI, but there are no Bash or Linux shell script equivalents. The ARM template example is Windows-only, with no Linux image option. In some cases, Windows terminology (e.g., password complexity, OSVersion) is emphasized or appears first. While Azure CLI is cross-platform and Linux is mentioned, Linux-specific examples and parity in templates are lacking.
Recommendations
  • Add Linux-specific ARM template examples, including Ubuntu or other popular Linux distributions in the 'imageReference' section.
  • Provide Bash or Linux shell script examples where PowerShell is used, or clarify that PowerShell is available cross-platform.
  • Ensure password/account creation instructions are inclusive of Linux (e.g., SSH key setup for Linux VMs, not just username/password).
  • Balance the order of examples so Linux and Windows are equally represented, or alternate which appears first.
  • Clarify in each section that the instructions apply to both Windows and Linux VMs, and highlight any OS-specific differences.
GitHub Create Pull Request
Virtual Machines Restrict managed disks from being imported or exported ...tual-machines/disks-restrict-import-export-overview.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both Azure CLI and PowerShell options for configuring the NetworkAccessPolicy, but references to PowerShell and Windows-centric links appear before Linux equivalents. The custom RBAC role section links to a PowerShell-based guide, and PowerShell is mentioned alongside CLI, potentially creating friction for Linux/macOS users. However, CLI options are present, and the topic is not inherently Windows-specific.
Recommendations
  • Ensure that Linux/CLI examples and links are given equal prominence and placement as PowerShell/Windows examples.
  • Add explicit Linux/macOS instructions or links for custom RBAC role creation, not just PowerShell.
  • Where possible, provide cross-platform guidance (e.g., Bash, CLI, PowerShell) side-by-side.
  • Review linked articles to ensure Linux parity and update main page to reference them equally.
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, frequently references Windows-centric tools and workflows (notably Hyper-V and PowerShell's Convert-VHD) for creating and managing VHDs. Windows/Hyper-V instructions are given first and in detail, with no Linux-native alternatives for key steps such as VHD creation/conversion and VM management. This creates friction for Linux/macOS users who may not have access to Windows tools or environments.
Recommendations
  • Provide Linux-native instructions and examples for creating and converting VHDs (e.g., using qemu-img, VBoxManage, or other open-source tools).
  • Include guidance for managing and shutting down VMs using Linux-based virtualization platforms (such as KVM/QEMU, VirtualBox, or VMware Workstation).
  • Offer parity in example commands for extracting and preparing images, ensuring Linux/macOS users can follow all steps without relying on Windows/Hyper-V.
  • Clarify which steps are Windows-specific and provide equivalent Linux/macOS workflows where possible.
  • Move Linux-native instructions to the forefront, or at least present them alongside Windows instructions.
GitHub Create Pull Request
Virtual Machines Upload a VHD to Azure or copy a disk across regions - Azure CLI ...machines/linux/disks-upload-vhd-to-managed-disk-cli.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides a Windows-style AzCopy example (using 'AzCopy.exe' and Windows file paths) but does not show a Linux/macOS equivalent. The AzCopy upload command is only demonstrated with Windows syntax and paths, and there is no explicit Linux/macOS example or mention of how to run AzCopy on those platforms. The rest of the CLI commands are cross-platform, but the upload step is Windows-centric.
Recommendations
  • Add a Linux/macOS AzCopy example, e.g., 'azcopy copy /home/user/mydisk.vhd "sas-URI" --blob-type PageBlob'.
  • Clarify that AzCopy is available for Linux/macOS and provide download/install instructions for those platforms.
  • Mention that file paths and command syntax differ between Windows and Linux/macOS.
  • Consider showing both Windows and Linux/macOS examples side by side for critical steps.
GitHub Create Pull Request
Virtual Machines Verify encryption status for Linux - Azure Disk Encryption ...tual-machines/linux/how-to-verify-encryption-status.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for verifying disk encryption status on Linux VMs, but consistently presents PowerShell examples before CLI examples. The PowerShell section is notably more detailed, with more granular examples and explanations, while the CLI section, although comprehensive, appears after PowerShell. There are no missing Linux-specific examples, and OS-level Linux commands are included. However, the ordering and depth of PowerShell content may create friction for Linux users, as PowerShell is less commonly used on Linux than Azure CLI or Bash.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is the default and most common tool for Linux users.
  • Ensure parity in detail and explanation between PowerShell and Azure CLI sections.
  • Explicitly note that PowerShell is optional and that Azure CLI is recommended for Linux environments.
  • Consider grouping CLI and PowerShell examples together, or providing a clear navigation for Linux users to skip PowerShell sections.
  • Add a brief rationale for tool selection, highlighting CLI as the preferred cross-platform solution.
GitHub Create Pull Request
Virtual Machines Run scripts in a Linux VM in Azure using managed Run Commands ...articles/virtual-machines/linux/run-command-managed.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation is focused on Linux VMs, but exhibits several Windows biases: PowerShell examples and tooling are heavily featured, some command references and tooling (e.g., Get-AzVMRunCommandDocument, New-AzStorageBlobSASToken) are Windows-centric or PowerShell-only, and REST/ARM template examples use Windows-style scripts (e.g., Write-Host, .ps1 files) without Linux shell script equivalents. In several places, Windows terminology and patterns are mentioned before Linux, and Linux-specific examples (e.g., bash script, .sh files) are missing or less prominent.
Recommendations
  • Provide Linux shell (.sh) script examples alongside PowerShell (.ps1) examples in REST and ARM template sections.
  • Clarify which tools and commands are cross-platform, and offer Linux-native alternatives where possible (e.g., az CLI for listing command IDs, SAS token generation).
  • Ensure that Linux-specific usage patterns (environment variables, script arguments, file types) are explained and demonstrated equally to Windows patterns.
  • Reorder sections or examples to show Linux CLI usage first, or at least equally, especially in documentation for Linux VMs.
  • Add explicit notes when a command/tool is Windows-only or PowerShell-only, and provide Linux alternatives.
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 introduction and main examples focus on custom Windows images, and the PowerShell command for role assignment is provided without a Linux CLI equivalent. However, references to Linux custom images and Azure CLI are present, and the ARM template examples are platform-neutral.
Recommendations
  • Add Azure CLI examples for role assignment alongside the PowerShell command.
  • Clarify that custom images can be Linux-based as well, and provide explicit Linux image deployment examples.
  • Ensure that Linux-specific links and instructions are as prominent as Windows ones.
  • Consider including a section or examples for deploying Linux custom images to Service Fabric Managed Clusters.
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 IIS scenarios are described in more detail, and Windows-specific tools (Mirantis Container Runtime, DockerEE) are listed explicitly. Windows examples and tutorials are sometimes presented before Linux equivalents, and IIS lift-and-shift scenarios are highlighted, which are Windows-centric.
Recommendations
  • Ensure Linux and Windows tutorials/examples are presented with equal prominence and in parallel, rather than Windows first.
  • Expand Linux-specific scenarios (e.g., Apache, NGINX, or other Linux workloads) to match the detail given to IIS/Windows scenarios.
  • List Linux container runtimes and tools with the same specificity as Windows (e.g., mention containerd, Podman, etc., if supported).
  • Clarify when features or scenarios are Windows-only to avoid confusion.
  • Add more Linux-focused use cases and references to Linux container images and repositories.
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 Service Fabric, and provides parity in describing development environments for each. However, in the 'Any OS, any cloud' section, Windows development is described first, and the quickstart link points to a .NET (Windows-oriented) tutorial, which may create a minor impression of Windows preference.
Recommendations
  • Add a quickstart link for Linux development alongside the Windows/.NET quickstart.
  • Alternate the order of Windows and Linux mentions in sections to avoid implicit prioritization.
  • Ensure that introductory examples and links are available for both Windows and Linux users.
GitHub Create Pull Request
Service Fabric Reliable Collection object serialization ...c-reliable-services-reliable-collections-serialization.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation is generally platform-neutral, focusing on .NET serialization concepts relevant to Azure Service Fabric Reliable Collections. However, in the 'Next steps' section, Windows-centric tools (Visual Studio and PowerShell) are mentioned before any Linux/macOS alternatives, and no Linux/macOS upgrade tooling is referenced.
Recommendations
  • Add links or references to Linux/macOS-compatible upgrade workflows, such as using Azure CLI or Service Fabric CLI (sfctl) for application upgrades.
  • Explicitly mention cross-platform development options for Service Fabric, including .NET Core/.NET 5+ and relevant tooling.
  • Consider reordering 'Next steps' to avoid Windows-first ordering, or group upgrade tutorials by platform.
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: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation provides both Linux (Bash/Python) and Windows (PowerShell) examples for configuring custom metrics and the application health extension. However, there are signs of Windows bias: PowerShell examples are consistently present and sometimes shown before Bash/Linux examples, and Windows-specific extension types (ApplicationHealthWindows) are used in several code snippets. The PowerShell section is detailed and prominent, and Windows tools (PowerShell cmdlets) are referenced throughout. Linux examples are present but not always as detailed or prominent as their Windows counterparts.
Recommendations
  • Ensure Linux/Bash examples are always shown alongside PowerShell, and consider showing Bash first or equally.
  • Provide more detailed Linux examples, especially for extension installation and querying, matching the depth of PowerShell examples.
  • Clarify when to use ApplicationHealthLinux vs ApplicationHealthWindows in all code snippets and tables.
  • Add troubleshooting steps for Linux environments (e.g., systemd, firewall rules, SELinux/AppArmor considerations).
  • Explicitly state that all features are supported on both Linux and Windows unless otherwise noted.
GitHub Create Pull Request
Virtual Machines What's new in Azure Disk Storage ...blob/main/articles/virtual-machines/disks-whats-new.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation is mostly platform-neutral and focuses on Azure Disk Storage features and regional availability. However, there are minor instances where Windows documentation or tools are referenced first or exclusively, such as linking to Windows-specific expand disk documentation before Linux equivalents, and referencing Azure PowerShell before Azure CLI in one property update. No critical tasks are Windows-only, and Linux parity is generally maintained.
Recommendations
  • Ensure that links to both Windows and Linux documentation are presented together or in a neutral order, rather than Windows first.
  • When referencing Azure CLI and PowerShell, list both tools equally and avoid prioritizing Windows tools.
  • Where possible, provide examples or links for Linux/macOS alongside Windows, especially for disk management operations.
  • Review linked articles to ensure Linux/macOS instructions are as comprehensive as Windows instructions.
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 for both Linux and Windows users, with CLI and REST examples defaulting to Linux, and PowerShell examples defaulting to Windows. However, PowerShell examples are shown for Windows first, and the PowerShell section is more detailed for Windows scenarios. The CLI section defaults to Linux, but the PowerShell section defaults to Windows, which may create minor friction for Linux users who prefer PowerShell. No critical tasks are Windows-only, and Linux guidance is present throughout.
Recommendations
  • In PowerShell examples, show Linux usage first or provide a Linux-specific example alongside the Windows example.
  • Clarify in PowerShell sections that -OsType can be set to Linux, and provide a sample command for Linux.
  • Ensure that all example blocks (CLI, PowerShell, REST) consistently show both Linux and Windows usage, or alternate which OS is shown first.
  • Add a brief note in the PowerShell section that Linux images can be managed equivalently, with a sample command.
GitHub Create Pull Request
Service Fabric Describing Azure Service Fabric apps and services ...ic/service-fabric-application-and-service-manifests.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page for Azure Service Fabric application and service manifests exhibits mild Windows bias. The only explicit tooling guidance is for Windows users (Visual Studio and a Windows file path for the XSD schema), and PowerShell is mentioned as the example method for creating service instances. There are no Linux/macOS-specific examples or equivalent tooling recommendations. Windows tools and patterns are referenced first and exclusively.
Recommendations
  • Add instructions for validating manifest XML schema on Linux/macOS, such as using xmllint or VS Code with XML plugins.
  • Mention cross-platform alternatives to Visual Studio for schema validation (e.g., VS Code, JetBrains Rider, or command-line tools).
  • Provide examples for creating service instances using Azure CLI or REST API, not just PowerShell.
  • Clarify which steps and tools are cross-platform, and highlight any Windows-only requirements.
  • Include Linux/macOS file paths or instructions where relevant.
GitHub Create Pull Request
Service Fabric Change Azure Service Fabric cluster settings ...rvice-fabric/service-fabric-cluster-fabric-settings.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides a comprehensive reference for Service Fabric cluster settings, but exhibits mild Windows bias. Several parameters and descriptions reference Windows-specific concepts (such as certificate store names like 'MY', store locations like 'LocalMachine', NTLM authentication, and Windows Defender Firewall), and some settings default to Windows values or mention Windows-only behaviors. In a few cases, Windows terminology or tools are mentioned before Linux equivalents, and Linux-specific guidance is less prominent or missing. There are no explicit Linux examples or parity notes for settings that differ between platforms.
Recommendations
  • For parameters referencing Windows certificate stores (e.g., 'MY', 'LocalMachine'), add Linux equivalents or clarify Linux usage (e.g., file paths, openssl stores).
  • For NTLM authentication and Windows Defender Firewall settings, explicitly note Linux alternatives or limitations.
  • Where settings default differently on Windows and Linux (e.g., ContainerNetworkSetup), highlight both defaults and provide guidance for each OS.
  • Add explicit Linux/macOS examples or notes for settings that behave differently or require different configuration on non-Windows platforms.
  • Where Windows terminology is used (e.g., 'Windows Fabric Replicator'), clarify if/how it applies to Linux clusters.
  • Consider adding a section or table summarizing platform-specific behaviors for key settings.
GitHub Create Pull Request
Service Fabric Azure Service Fabric hosting activation and deactivation life cycle ...les/service-fabric/service-fabric-hosting-lifecycle.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page on Azure Service Fabric hosting activation and deactivation life cycle is largely platform-neutral in its technical explanations, but it shows mild Windows bias in its 'Next steps' section, which links only to PowerShell-based deployment/removal instructions. Additionally, the only explicit tooling example for downloading a ServicePackage references a PowerShell cmdlet. There are no Linux-specific examples, nor are cross-platform CLI alternatives mentioned.
Recommendations
  • Add links or examples for deploying and removing applications using Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • Mention Linux/macOS-compatible tools or commands alongside PowerShell references, especially in 'Next steps' and any operational examples.
  • Clarify where PowerShell is used that equivalent functionality exists via CLI or REST APIs for non-Windows users.
  • Provide sample configuration or operational flows for Linux-based Service Fabric clusters, if applicable.
GitHub Create Pull Request
Service Fabric Reliable services app manifest examples ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-manifest-example-reliable-services-app.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page for Service Fabric reliable services app manifest examples shows mild Windows bias. It references Windows-specific concepts (such as 'NetworkService', 'Administrators', and '.bat' files) and mentions the ServiceFabric PowerShell module as a way to create service instances, without mentioning Linux equivalents or cross-platform CLI options. Examples and explanations often use Windows terminology and tools first, with no explicit Linux guidance or parity.
Recommendations
  • Add examples and explanations for Linux deployments, including references to Linux user/group concepts and how Service Fabric handles principals on Linux nodes.
  • Mention cross-platform tools such as Azure CLI or Service Fabric CLI (sfctl) for creating and managing services, alongside or instead of PowerShell.
  • Clarify which features and manifest elements are supported on Linux clusters, and note any differences in behavior or limitations.
  • Provide sample scripts or entry points using shell scripts (.sh) in addition to .bat files, to illustrate Linux compatibility.
  • Explicitly state when a feature or example is Windows-only, and provide Linux alternatives where possible.
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
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for most operations, but PowerShell examples are often presented before CLI examples, and some sections (such as querying public IPs) show PowerShell commands first or in greater detail. While Linux parity is generally good, the ordering and prominence of PowerShell may create friction for Linux/macOS users.
Recommendations
  • Present Azure CLI and PowerShell examples side-by-side or in parallel tabs, ensuring CLI (cross-platform) is not secondary.
  • Where both CLI and PowerShell are available, alternate which is shown first or default to CLI for cross-platform parity.
  • Ensure all PowerShell examples have equivalent CLI examples, and vice versa.
  • Explicitly note that Azure CLI works on Windows, Linux, and macOS to reinforce cross-platform support.
GitHub Create Pull Request
Virtual Machine Scale Sets Enable Automatic Zone Balance on Virtual Machine Scale Sets (Preview) ...virtual-machine-scale-sets/auto-zone-balance-enable.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for all major operations, but PowerShell (a Windows-centric tool) is consistently presented as a first-class citizen alongside CLI, and in some sections, PowerShell examples are shown before or at parity with CLI. There are no explicit Linux shell script examples, but the CLI examples are cross-platform. The PowerShell examples use Windows-specific extension types (e.g., ApplicationHealthWindows), which may confuse Linux users. However, Linux users can complete all tasks using the Azure CLI or REST API, and the documentation does not block Linux/macOS users.
Recommendations
  • Clarify that Azure CLI examples are fully cross-platform and recommended for Linux/macOS users.
  • In PowerShell examples, clarify when an extension type (e.g., ApplicationHealthWindows) is for Windows VMs and provide the Linux equivalent (e.g., ApplicationHealthLinux) if applicable.
  • Consider presenting Azure CLI examples before PowerShell, as CLI is cross-platform.
  • Explicitly state that all features are available to both Windows and Linux VMSS, unless otherwise noted.
  • Add a note in the prerequisites or intro about tool parity for Linux/macOS users.
GitHub Create Pull Request
Virtual Machine Scale Sets Migrate deployments and resources to Virtual Machine Scale Sets in Flexible orchestration ...lexible-virtual-machine-scale-sets-migration-resources.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ minor_windows_tools
Summary
The documentation provides migration guidance for Azure Virtual Machine Scale Sets in Flexible orchestration. While the topic is cross-platform, there are subtle signs of Windows bias: Windows/PowerShell is mentioned alongside Azure CLI, and Windows-specific scenarios (activation, updates) are listed before Linux equivalents. However, Linux is referenced (e.g., package managers), and most examples use Azure CLI, which is cross-platform. No critical migration steps are Windows-only, but minor friction exists for Linux/macOS users.
Recommendations
  • Ensure Linux-specific migration scenarios (e.g., package manager access, SSH configuration) are given equal prominence alongside Windows scenarios.
  • Provide explicit Linux/macOS command examples (e.g., Bash, Azure CLI) before or alongside PowerShell examples.
  • Mention Linux tools and patterns (such as cloud-init, SSH, package managers) in relevant sections.
  • Clarify that Azure CLI is cross-platform and recommend it as the default for scripting unless Windows-specific features are required.
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 consistently presents PowerShell examples immediately after CLI and before ARM template examples. PowerShell is a Windows-centric tool, and its prominence may create friction for Linux/macOS users. However, Azure CLI is cross-platform and all tasks can be completed with it, so Linux/macOS users are not blocked. There are no Windows-only tools or patterns mentioned, and no missing Linux examples.
Recommendations
  • Consider listing Azure CLI examples before PowerShell in each section, as CLI is cross-platform and more inclusive for Linux/macOS users.
  • Explicitly note that Azure CLI works on Linux, macOS, and Windows, while PowerShell is primarily for Windows users.
  • If possible, add Bash shell script snippets for common tasks to further improve Linux parity.
  • Ensure screenshots and portal instructions are not Windows-specific (they are not in this doc).
GitHub Create Pull Request
Virtual Machine Scale Sets Orchestration modes for Virtual Machine Scale Sets in Azure ...sets/virtual-machine-scale-sets-orchestration-modes.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation provides a balanced overview of orchestration modes for Azure Virtual Machine Scale Sets, with clear support for both Linux and Windows VMs. However, there is a minor bias in the order of example links and references: the Managed Identity section links to a Windows VMSS portal example, and some references (such as Azure Site Recovery via PowerShell) mention Windows tools first. No critical sections are Windows-only, and Linux users can complete all tasks described.
Recommendations
  • Add explicit Linux example links alongside Windows ones, especially in sections referencing Managed Identity or Azure Site Recovery.
  • Clarify that Azure CLI and REST API examples work for both Linux and Windows users.
  • Where PowerShell is mentioned, also reference Bash/CLI equivalents for parity.
  • Ensure that all feature tables and comparisons highlight Linux support as clearly as Windows support.
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 updating scale sets), PowerShell is presented before REST API and after CLI, with no explicit Bash or Linux shell examples. The CLI examples are cross-platform, but PowerShell is Windows-centric. There are no 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, but the overall example flow slightly favors Windows tools.
Recommendations
  • Add explicit Bash shell examples for Linux users, especially for update operations.
  • Clarify that Azure CLI commands are cross-platform and suitable for Linux/macOS users.
  • Consider mentioning or linking to Linux-specific quickstart guides or scripts where appropriate.
  • Ensure that PowerShell examples are not shown before CLI or REST API examples unless the feature is Windows-only.
  • Add notes or callouts for Linux/macOS users where PowerShell is referenced.
GitHub Create Pull Request
Virtual Machine Scale Sets Rolling upgrades with MaxSurge for Virtual Machine Scale Sets ...hine-scale-sets/virtual-machine-scale-sets-maxsurge.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides configuration instructions for rolling upgrades with MaxSurge on Azure Virtual Machine Scale Sets. It includes examples for the Azure Portal, Azure CLI, PowerShell, and ARM templates. The PowerShell example is presented after the CLI example, but both are given equal prominence. There is no evidence of Windows-only tools or patterns being mentioned exclusively, and the CLI example is cross-platform. However, PowerShell is a Windows-centric tool, and its inclusion may suggest a slight Windows bias, especially since no explicit mention is made of Bash or Linux-specific scripting. The ordering of examples (CLI before PowerShell) minimizes this bias, but the presence of PowerShell as a primary example is notable.
Recommendations
  • Clarify that Azure CLI commands are cross-platform and can be used on Linux, macOS, and Windows.
  • Consider adding Bash shell scripting examples or explicitly noting that Azure CLI works on Linux/macOS.
  • If relevant, mention any Linux-specific considerations for VMSS upgrades (e.g., health extensions or probes).
  • Ensure parity in troubleshooting or advanced configuration sections, if present, for both Windows and Linux environments.
GitHub Create Pull Request
Virtual Machines Secure Azure Managed Disk Downloads and Uploads ...icles/virtual-machines/disks-secure-upload-download.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both PowerShell and Azure CLI examples for securing managed disk uploads/downloads, but PowerShell (a Windows-centric tool) is presented before Azure CLI in several sections. The 'Assign RBAC role' and 'Restrict access to an individual disk' sections list PowerShell before CLI, and the tab order is PowerShell first. However, Linux/macOS users are not blocked, as CLI examples are present and relevant links for Linux tasks are included in 'Next steps'.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI first to avoid implicit Windows prioritization.
  • Explicitly note that Azure CLI works cross-platform and is recommended for Linux/macOS users.
  • Add Bash or shell script examples where relevant, especially for disk operations.
  • Ensure parity in screenshots and UI descriptions for portal steps (if differences exist).
GitHub Create Pull Request
Virtual Machines Azure VM Extensions and Features for Linux ...articles/virtual-machines/extensions/features-linux.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all major tasks (discovering, running, managing, and troubleshooting VM extensions). However, PowerShell examples are always given alongside CLI, and in some sections, PowerShell is presented immediately after CLI, which may suggest parity but still reinforces PowerShell as a primary tool. There are no Linux-specific shell or scripting examples outside Azure CLI, and no Linux-native tooling is discussed. The documentation does not omit Linux examples, but the presence and prominence of PowerShell throughout may create friction for Linux users who do not use PowerShell.
Recommendations
  • Consider providing Bash shell script examples for common extension management tasks, especially for users who prefer native Linux tools.
  • Clarify that PowerShell is optional for Linux users and highlight Azure CLI as the primary cross-platform tool.
  • Where possible, reorder examples to show Azure CLI first, and PowerShell second, or explicitly state that Azure CLI is recommended for Linux.
  • Add a brief section explaining the typical Linux admin workflow (using Bash, SSH, etc.) and how Azure CLI fits into that.
  • Remove unnecessary references to PowerShell in Linux-focused documentation unless it is required for a specific scenario.
GitHub Create Pull Request
Virtual Machines NVIDIA GPU Driver Extension - Azure Linux VMs ...es/virtual-machines/extensions/hpccompute-gpu-linux.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation is primarily focused on Linux, as indicated by the title and content. However, PowerShell examples are provided alongside Azure CLI and ARM template examples for deploying the extension, even though PowerShell is a Windows-centric tool. Additionally, PowerShell is presented before Azure CLI in several sections, which may subtly prioritize Windows tooling. There are no missing Linux examples, and Linux tools and patterns are well represented throughout the document.
Recommendations
  • Move Azure CLI examples before PowerShell examples, as Azure CLI is cross-platform and more relevant for Linux users.
  • Clarify that PowerShell examples are optional and primarily for users on Windows or those using PowerShell Core on Linux.
  • Consider adding Bash script examples for common deployment scenarios, as Bash is native to Linux.
  • Explicitly note that Azure CLI is recommended for Linux users.
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 generally Linux-focused and provides extensive Linux-specific details, but there are minor signs of Windows bias. Azure PowerShell examples are presented before Azure CLI examples in deployment sections, and troubleshooting commands reference PowerShell first. There is also a link to a Windows VM access policy guide in the template deployment section, though the context is relevant for managed identities. All technical content, examples, and paths are Linux-centric, and Linux tools (Azure CLI, Fluentd, symlinks, Linux file paths) are well covered.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as CLI is more cross-platform and native to Linux.
  • In troubleshooting sections, show Azure CLI commands first or alongside PowerShell.
  • Clarify that PowerShell examples are optional for Linux users, and highlight CLI as the primary method.
  • Where links reference Windows VM guides, add a Linux-specific link or clarify applicability.
GitHub Create Pull Request
Virtual Machines Create and upload a Red Hat Enterprise Linux VHD for use in Azure ...les/virtual-machines/linux/redhat-create-upload-vhd.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation covers multiple hypervisors (Hyper-V, KVM, VMware, Kickstart) for preparing and uploading a Red Hat Enterprise Linux VHD for Azure. However, throughout the article, instructions for Hyper-V (a Windows-based hypervisor) are consistently presented first in each major section and tab group. This ordering may subtly suggest Windows/Hyper-V as the primary or preferred platform, even though full Linux-native (KVM, VMware, Kickstart) instructions are provided. There are no missing Linux examples, and Linux tools and patterns are well represented.
Recommendations
  • Consider reordering sections so that Linux-native hypervisors (KVM, VMware, Kickstart) are presented before Hyper-V, or at least alternate the order to avoid implicit prioritization.
  • Explicitly state in the introduction that all major hypervisors are equally supported, and that the order of presentation does not imply preference.
  • Where possible, highlight that Linux-native workflows (KVM, VMware, Kickstart) are fully supported and may be preferable for Linux users.
  • Add a summary table at the top showing parity across hypervisors, so users can quickly identify their preferred workflow.
GitHub Create Pull Request
Virtual Machines Create an Azure Image Builder Bicep file or ARM template JSON template .../articles/virtual-machines/linux/image-builder-json.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation provides both Windows and Linux guidance for Azure Image Builder, but there are several areas where Windows tools and patterns are emphasized or presented first. PowerShell is frequently referenced for checksum generation and template operations, sometimes before Linux equivalents. Windows-specific customizers (PowerShell, WindowsRestart, WindowsUpdate) are described in detail, while Linux customizers are less prominent. Some examples and notes use Windows terminology or tools (e.g., Get-FileHash, shutdown commands) before mentioning Linux alternatives.
Recommendations
  • Ensure Linux and macOS command-line examples (e.g., for checksum generation) are presented alongside or before Windows/PowerShell equivalents.
  • Where PowerShell is referenced, also provide bash or shell alternatives for Linux/macOS users, especially for operations like file hash generation and template actions.
  • Balance the order of examples so that Linux and Windows are equally represented, or alternate which OS is shown first.
  • Clarify when a feature or customizer is Windows-only, and provide Linux equivalents or explicitly state when no equivalent exists.
  • Expand Linux-specific customizer and validator examples to match the detail given for Windows (e.g., more shell script examples, troubleshooting tips).
GitHub Create Pull Request
Virtual Machines Time sync for Linux VMs in Azure ...blob/main/articles/virtual-machines/linux/time-sync.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation is focused on Linux VM time synchronization in Azure and provides Linux-specific guidance, examples, and tools. However, the 'Overview' section and introduction spend several paragraphs describing Windows Server 2016 time sync improvements and Windows host infrastructure before discussing Linux-specific mechanisms. Windows references and links appear before Linux configuration details, which may create confusion or friction for Linux users seeking direct guidance.
Recommendations
  • Move Windows Server 2016 background information to a separate 'Background' or 'Azure host infrastructure' section, or summarize briefly before focusing on Linux-specific mechanisms.
  • Begin the page with Linux VM time sync options and configuration steps, referencing Windows host infrastructure only as needed for context.
  • Ensure Linux-specific examples and tools are presented first and clearly, minimizing Windows-centric framing unless directly relevant.
  • Consider adding a short summary at the top clarifying that the Windows host information is background and that the page is Linux-focused.
GitHub Create Pull Request
Virtual Machines vCPU quotas ...ute-docs/blob/main/articles/virtual-machines/quotas.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for checking vCPU quotas. However, the PowerShell section is given equal prominence to the CLI, despite PowerShell being primarily a Windows tool. Additionally, the PowerShell example is presented immediately after the CLI example, which may subtly reinforce Windows-centric workflows. No Linux-specific tools or shell examples (e.g., Bash scripting) are provided, but the CLI example is cross-platform.
Recommendations
  • Clearly indicate that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Consider adding a brief Bash shell example (e.g., piping Azure CLI output to grep or awk) to demonstrate Linux-native workflows.
  • Explicitly mention that PowerShell is primarily for Windows users, and that Azure CLI works on all platforms.
  • If possible, provide links to Azure CLI installation instructions for Linux/macOS users.
GitHub Create Pull Request
Virtual Machines Customer intent: "As an IT administrator managing Azure IaaS virtual machines, I want to implement a backup and disaster recovery plan for unmanaged disks, so that I can ensure data durability and high availability in the event of localized or regional failures." ...al-machines/page-blobs-backup-and-disaster-recovery.md
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 covers both Linux and Windows VMs and generally maintains parity in describing backup and disaster recovery approaches. However, there are several instances where Windows-specific tools (such as PowerShell and Volume Shadow Service) are mentioned first or in more detail, and PowerShell is often referenced as the primary scripting/automation method. Linux equivalents (such as Azure CLI or fsfreeze) are mentioned, but sometimes after Windows tools or with less detail. There are also references to Windows-specific backup consistency mechanisms (VSS) before Linux alternatives, and links to Windows-focused pages (e.g., incremental snapshots under 'windows'). However, Linux options are present and described, and critical tasks can be completed on Linux.
Recommendations
  • Ensure that scripting/automation examples are provided for both PowerShell and Azure CLI, with equal prominence.
  • When mentioning backup consistency mechanisms, describe Linux options (such as fsfreeze and application-consistent backup for Linux VMs) before or alongside Windows VSS.
  • Provide links to both Linux and Windows incremental snapshot guides in relevant sections, not just Windows.
  • Where PowerShell is referenced, add Azure CLI equivalents and note their parity.
  • Review and balance the order of tool mentions so Linux tools are not consistently secondary.
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: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ minor_windows_tools
Summary
The documentation covers both Windows and Linux VM images, but there are several signs of Windows bias. PowerShell examples are consistently provided alongside Azure CLI, sometimes referenced first. Windows-specific tools (Sysprep) are mentioned before Linux equivalents (waagent) in the generalization section. Some links and examples reference Windows paths or documentation before Linux equivalents. However, Linux parity is generally maintained, and most tasks can be completed by Linux users.
Recommendations
  • Ensure that CLI and PowerShell examples are presented with equal prominence, or alternate which comes first.
  • Where both Windows and Linux tools are mentioned, list Linux tools first or together, rather than defaulting to Windows-first ordering.
  • Add explicit Linux examples or links wherever Windows examples are given, especially in sections referencing upload or specialized image creation.
  • Review FAQ and troubleshooting sections for balanced coverage of Linux and Windows scenarios.
  • Where possible, use generic language (e.g., 'generalize your VM') and then specify both Windows and Linux methods equally.
GitHub Create Pull Request