407
Total Pages
336
Linux-Friendly Pages
71
Pages with Bias
17.4%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

1235 issues found
Showing 51-75 of 1235 flagged pages
Service Fabric Azure Service Fabric reverse proxy ...articles/service-fabric/service-fabric-reverseproxy.md
High Priority View Details →
Scanned: 2026-01-30 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page for Azure Service Fabric reverse proxy clearly states that the reverse proxy feature is not available for Linux clusters. All examples, configuration notes, and usage scenarios are written with Windows clusters in mind, and there are no Linux equivalents or workarounds provided. The page does not offer guidance for Linux users, nor does it clarify alternative approaches for Linux clusters.
Recommendations
  • Add a prominent note at the top of the page clarifying that reverse proxy is Windows-only and suggest alternative communication patterns for Linux clusters.
  • Provide links or references to Linux-compatible Service Fabric features or third-party solutions for service discovery and HTTP routing.
  • If possible, update the documentation when Linux support for reverse proxy becomes available, or maintain a comparison table of feature parity between Windows and Linux clusters.
Service Fabric Standalone Service Fabric clusters overview ...-fabric/service-fabric-standalone-clusters-overview.md
High Priority View Details →
Scanned: 2026-01-30 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools Windows First
Summary
Although the introduction claims Service Fabric clusters can run on both Windows Server and Linux, the documentation and supported OS list indicate that standalone clusters are currently Windows-only. The security section references Windows-specific tools and patterns (Kerberos, Active Directory, group Managed Service Accounts) without Linux equivalents or guidance. No Linux examples, instructions, or supported OS are provided, and Windows terminology is used throughout.
Recommendations
  • Clarify in the introduction that standalone clusters are currently Windows-only, and Linux support is not available yet.
  • Remove or update statements suggesting Linux parity unless Linux support is imminent.
  • If/when Linux support is added, provide equivalent Linux security guidance (e.g., certificate management, authentication patterns) and Linux-specific examples.
  • Explicitly state the lack of Linux support in the 'Supported operating systems' section to avoid confusion.
Scanned: 2026-02-19 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page primarily discusses deploying custom Windows images in Service Fabric Managed Clusters, with Windows terminology and PowerShell examples shown. While Linux custom image creation is referenced, the main focus and examples are Windows-centric, and the PowerShell command is given without a Linux CLI equivalent.
Recommendations
  • Clarify at the top whether Linux node types are supported for custom images in Service Fabric Managed Clusters.
  • Provide equivalent Azure CLI examples for role assignment (e.g., az role assignment create) alongside PowerShell.
  • Include explicit guidance or examples for deploying Linux custom images if supported, such as ARM template snippets for Linux VM images.
  • Balance terminology to refer to both Windows and Linux images where applicable, rather than only 'custom windows images'.
Service Fabric RunToCompletion semantics and specifications ...blob/main/articles/service-fabric/run-to-completion.md
Medium Priority View Details →
Scanned: 2026-02-19 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page for RunToCompletion semantics in Service Fabric presents Windows container examples exclusively, references Windows-specific container images, and uses Windows command syntax (cmd, echo, set, ping). PowerShell is the only CLI example given for querying deployment status, with no mention of Linux or cross-platform alternatives. There is no guidance or example for Linux containers or querying status from Linux/macOS environments.
Recommendations
  • Add Linux container examples (e.g., using Ubuntu or Alpine images) alongside Windows container examples.
  • Provide equivalent shell command examples (bash/sh) for Linux containers, replacing Windows cmd syntax.
  • Include instructions for querying deployment status using Service Fabric CLI (sfctl) or REST API, which are cross-platform.
  • Clarify whether RunToCompletion semantics are supported for Linux containers, and if so, provide relevant guidance.
  • Mention any platform-specific limitations explicitly, so Linux/macOS users know what is and isn't supported.
Service Fabric Capacity planning and scaling for Azure Service Fabric ...bric/service-fabric-best-practices-capacity-scaling.md
Medium Priority View Details →
Scanned: 2026-02-19 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides several PowerShell-based manual scaling instructions and references Windows-centric tooling (e.g., PowerShell cmdlets like Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState) without offering equivalent Linux CLI or script examples. Windows/PowerShell instructions are presented first and exclusively in critical scaling workflows, creating friction for Linux users. While Service Fabric supports Linux clusters, the manual scaling guidance is not platform-neutral.
Recommendations
  • Add equivalent Linux CLI instructions (e.g., using sfctl or Service Fabric REST API) alongside PowerShell examples for node management.
  • Clearly indicate which steps are platform-specific and provide links or references to Linux documentation where appropriate.
  • Where possible, use platform-neutral language and tooling (e.g., ARM templates, REST API) for examples.
  • Include a section or callout for Linux users detailing how to perform scaling operations using Linux-compatible tools.
Service Fabric Application upgrade: upgrade parameters ...abric/service-fabric-application-upgrade-parameters.md
Medium Priority View Details →
Scanned: 2026-02-19 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page presents upgrade parameters for Service Fabric applications, but it exhibits Windows bias by prioritizing PowerShell and Visual Studio (Windows tools) in both structure and examples. The PowerShell and Visual Studio sections are detailed and appear first, while Linux-friendly tools (SFCTL CLI) are covered later and with less emphasis. There are no explicit Linux command examples or walkthroughs in the main content, and the parameter tables focus on PowerShell/Visual Studio, with SFCTL parameters separated. Although the 'Next steps' section links to Linux CLI guides, the main article lacks parity in examples and guidance for Linux/macOS users.
Recommendations
  • Add Linux/SFCTL CLI examples alongside PowerShell examples in parameter tables and explanations.
  • Reorganize the page so that SFCTL CLI (cross-platform) is presented equally or before Windows-specific tools.
  • Include explicit notes or guidance for Linux/macOS users in relevant sections.
  • Ensure parameter descriptions reference both Windows and Linux tools where applicable.
  • Consider adding a comparison table showing how to perform upgrades using PowerShell, Visual Studio, SFCTL CLI, and REST, with OS applicability.
Scanned: 2026-02-19 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides example code for configuring auto scaling policies in Service Fabric using application manifests, C# APIs, and PowerShell. However, all CLI examples are PowerShell-based, with no equivalent Bash or Linux CLI examples. The PowerShell examples are shown alongside C# and manifest examples, but there is no mention of Linux-specific tools or commands. Additionally, the documentation does not clarify whether the PowerShell commands are usable on Linux (via PowerShell Core), nor does it provide guidance for Linux users who may prefer Bash or other scripting environments.
Recommendations
  • Add Bash or Azure CLI examples for configuring scaling policies, especially for Linux users.
  • Clarify whether PowerShell examples are compatible with PowerShell Core on Linux, or provide alternative instructions for Linux environments.
  • Mention any Linux-specific considerations or limitations when configuring auto scaling policies.
  • If certain features are Windows-only, explicitly state so to avoid confusion.
Service Fabric Cluster Resource Manager - Management Integration ...fabric-cluster-resource-manager-management-integration.md
Medium Priority View Details →
Scanned: 2026-02-19 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides a PowerShell example (Get-ServiceFabricPartitionHealth) for querying health reports but does not offer equivalent examples or commands for Linux/macOS environments. There is no mention of cross-platform CLI tools (such as sfctl) or REST API alternatives, which may create friction for non-Windows users.
Recommendations
  • Include equivalent examples using sfctl (Service Fabric CLI), which is cross-platform and works on Linux/macOS.
  • Mention REST API options for querying health reports, with example requests.
  • Clarify that PowerShell examples are for Windows and provide links or code snippets for Linux/macOS users.
  • Consider a table or section summarizing management tool parity across platforms.
Service Fabric Manage apps for multiple environments ...e-fabric-manage-multiple-environment-app-configuration.md
Medium Priority View Details →
Scanned: 2026-02-19 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides examples for specifying parameters during application creation, with PowerShell and Visual Studio mentioned first and in detail. Linux-friendly tools like sfctl are referenced, but not explained as thoroughly, and there is no explicit Linux/macOS workflow example. The use of PowerShell and Visual Studio (Windows-centric tools) is emphasized, while Linux equivalents or cross-platform alternatives are less prominent.
Recommendations
  • Add explicit Linux/macOS workflow examples, such as using sfctl from Bash or install.sh scripts.
  • Provide sample shell commands for parameter passing on Linux/macOS.
  • Clarify which tools are cross-platform and which are Windows-only.
  • Ensure that Linux/macOS users are guided on how to perform equivalent tasks without PowerShell or Visual Studio.
Service Fabric Networking patterns for Azure Service Fabric ...s/service-fabric/service-fabric-patterns-networking.md
Medium Priority View Details →
Scanned: 2026-02-19 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides only PowerShell-based deployment commands and examples, with no mention of Azure CLI or Bash equivalents. Windows-specific tools (PowerShell, RDP) are referenced exclusively or before alternatives, and even basic connectivity checks use Windows command prompt syntax. There are no Linux/macOS-specific instructions or examples, which creates friction for non-Windows users.
Recommendations
  • Add Azure CLI (az) command examples alongside PowerShell for template deployments and resource creation.
  • Include Bash shell examples for connectivity checks (e.g., using ping from Linux/macOS terminals).
  • Mention SSH as an alternative to RDP for accessing VMs, especially for Linux users.
  • Clarify that Service Fabric clusters can be managed from any OS, and provide cross-platform guidance where applicable.
  • Consider reorganizing examples so that cross-platform tools (Azure CLI, SSH) are presented before or alongside Windows-specific tools.
Service Fabric Fault Analysis Service overview .../service-fabric/service-fabric-testability-overview.md
Medium Priority View Details →
Scanned: 2026-02-19 00:00
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 instructions for Linux/macOS users, such as using CLI tools or REST APIs, nor is there mention of cross-platform alternatives. This creates friction for Linux/macOS users who may not have access to PowerShell or Windows-specific SDKs.
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 prerequisites for Linux/macOS users, and provide guidance for equivalent tooling.
  • If PowerShell is required, note the availability of PowerShell Core on Linux/macOS and provide installation instructions.
Service Fabric Manage certificates in a Service Fabric cluster ...vice-fabric/cluster-security-certificate-management.md
Medium Priority View Details →
Scanned: 2026-02-19 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page provides extensive PowerShell examples and references Windows-specific tools and extensions (e.g., Key Vault VM extension for Windows, S-channel, Windows certificate store concepts). While the core certificate management concepts are cross-platform and Azure-centric, the hands-on automation and scripting guidance is heavily Windows-focused, with PowerShell as the primary scripting language and Windows-specific mechanisms discussed in detail. There is minimal mention of Linux or cross-platform equivalents, and Windows patterns/tools are presented first and exclusively in critical automation sections.
Recommendations
  • Add equivalent Bash/CLI examples for certificate enrollment and management, especially for Key Vault operations.
  • Document how certificate provisioning and autorollover can be achieved on Linux-based Service Fabric clusters, including any differences in VM extensions or certificate store handling.
  • Clarify which steps or tools are Windows-only and provide guidance for Linux/macOS users where possible.
  • Reference or link to Linux-specific documentation for Service Fabric certificate management if available.
  • Where PowerShell is used, offer Azure CLI or REST API alternatives for cross-platform automation.
Service Fabric X.509 Certificate-based Authentication in a Service Fabric Cluster ...ticles/service-fabric/cluster-security-certificates.md
Medium Priority View Details →
Scanned: 2026-02-19 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation provides a thorough conceptual overview of X.509 certificate-based authentication in Service Fabric clusters, but exhibits Windows bias in several ways. Windows-specific terminology (e.g., certificate stores like LocalMachine\My), references to Windows APIs (Win32 CryptoAPI, CertGetCertificateChain), and troubleshooting instructions (event logs, CAPI2 logging) are presented first and in detail. Linux equivalents are mentioned briefly or parenthetically, but not explained or exemplified. No Linux-specific troubleshooting guidance or certificate store management examples are provided.
Recommendations
  • Add explicit Linux examples for certificate store paths and management (e.g., using openssl, Linux certificate directories).
  • Provide troubleshooting guidance for Linux nodes, including log locations and relevant tools.
  • When referencing Windows APIs or tools, also mention Linux equivalents (e.g., OpenSSL, systemd journal, /var/log).
  • Include Linux-specific error codes and remediation steps where applicable.
  • Ensure that all configuration examples (manifest XML, JSON) clarify any OS-specific differences.
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 →
Scanned: 2026-02-19 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides examples for configuring Service Fabric managed cluster node types using the Azure Portal, ARM templates, and PowerShell. PowerShell is the only CLI example provided, and it is presented as the exclusive scripting option for command-line operations. There are no examples or mentions of Linux/macOS-compatible CLI tools (such as Azure CLI or Bash scripts), and PowerShell is shown before any Linux alternatives (which are missing). This creates friction for Linux/macOS users who may not have access to PowerShell or prefer Azure CLI.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all command-line operations (adding, removing, scaling node types, etc.).
  • Explicitly mention that PowerShell examples are Windows-centric and provide guidance for Linux/macOS users.
  • Consider including Bash script samples or references to cross-platform tools where possible.
  • Clarify whether all operations can be performed with Azure CLI or if PowerShell is required for certain advanced scenarios.
Service Fabric Introduction to the Service Fabric Infrastructure Service .../articles/service-fabric/infrastructure-service-faq.md
Medium Priority View Details →
Scanned: 2026-02-19 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides a PowerShell-only example for bypassing Infrastructure Service, and references Service Fabric Explorer (a GUI tool typically used on Windows). No Linux/bash equivalents or cross-platform CLI alternatives are mentioned. Most instructions and tooling references implicitly assume Windows environments, creating friction for Linux/macOS users.
Recommendations
  • Add equivalent bash or Azure CLI examples for cluster operations, especially for bypassing Infrastructure Service.
  • Clarify whether Service Fabric Explorer is available cross-platform or provide alternatives for Linux/macOS users.
  • Mention any prerequisites or limitations for Linux/macOS users explicitly.
  • Where possible, provide links to cross-platform tools or documentation.
Service Fabric Deny assignment policy for Service Fabric managed clusters ...cles/service-fabric/managed-cluster-deny-assignment.md
Medium Priority View Details →
Scanned: 2026-02-19 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides examples and links for Azure PowerShell prominently, with PowerShell-based actions mentioned first in the 'Best practices' section. While Azure CLI is listed as an ARM-backed tool, PowerShell is emphasized for operational tasks, and no Linux-specific command examples or shell scripts are provided. The page does not exclusively reference Windows tools, but the focus on PowerShell may create friction for Linux/macOS users.
Recommendations
  • Add explicit Azure CLI examples for key operations (e.g., deleting NodeTypes, restarting/reimaging scale sets) alongside PowerShell examples.
  • Mention cross-platform tools (like Azure CLI and sfctl) earlier and equally in the 'Best practices' section.
  • Clarify that Azure PowerShell is available cross-platform, but provide CLI alternatives for Linux/macOS users.
  • Where possible, provide sample commands for both PowerShell and CLI for parity.
Service Fabric Service Fabric Explorer blocking operations ...ged-cluster-service-fabric-explorer-blocking-operation.md
Medium Priority View Details →
Scanned: 2026-02-19 00:00
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 blocking operations. It consistently references Az PowerShell cmdlets (e.g., Remove-AzResource, AzSF PowerShell cmdlets) for resource operations, and only briefly mentions the Azure CLI ('az resource') for deleting applications. There are no explicit Linux/macOS examples or references to cross-platform tools, and PowerShell-based instructions are presented first and most often.
Recommendations
  • Add explicit Azure CLI examples for all operations (e.g., unprovisioning application type versions, creating applications/services, scaling, and deletions), since Azure CLI is cross-platform and works on Linux/macOS.
  • Where PowerShell cmdlets are referenced, provide equivalent Azure CLI commands alongside, and clarify which tools are available on which platforms.
  • Consider reorganizing sections so that cross-platform tools (Azure CLI) are presented before or alongside PowerShell examples.
  • Add notes or guidance for Linux/macOS users, indicating how they can perform the same operations without PowerShell.
Service Fabric Migrate an Azure Service Fabric cluster to availability zone support ...ce-fabric/migrate-service-fabric-availability-zones.md
Medium Priority View Details →
Scanned: 2026-02-19 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides migration guidance for Azure Service Fabric clusters to availability zone support. While most of the guidance is platform-neutral and focuses on Azure Resource Manager templates, the only explicit command-line examples are PowerShell-based and reference Windows tools (e.g., Service Fabric PowerShell cmdlets, AzureRm modules). The PowerShell examples are given exclusively, with no equivalent Bash, Azure CLI, or Linux-native instructions. Additionally, sample templates referenced are often for Windows (e.g., '15-VM-Windows-Multiple-AZ-Secure'), and Windows paths (e.g., 'D:\\SvcFab') are used in configuration snippets. Linux equivalents are not provided or are mentioned only in passing.
Recommendations
  • Add Azure CLI or Bash examples for all migration steps currently shown only in PowerShell.
  • Reference and link to Linux/Ubuntu sample templates equally alongside Windows templates.
  • When showing configuration snippets, use platform-neutral paths or provide both Windows and Linux examples (e.g., 'D:\\SvcFab' and '/var/svcfab').
  • Explicitly mention that Service Fabric clusters can run on Linux and provide guidance for Linux users where appropriate.
  • Include notes or sections for Linux-specific considerations, such as certificate management or node disabling/removal using cross-platform tools.
Service Fabric Learn about Azure Service Fabric application security ...ric/service-fabric-application-and-service-security.md
Medium Priority View Details →
Scanned: 2026-02-19 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation covers Azure Service Fabric application security in a cross-platform manner, but several sections show Windows bias. Windows-specific features (e.g., AD accounts, gMSA, BitLocker) are mentioned before Linux equivalents or without Linux parity. Some examples and links are Windows-centric (e.g., disk encryption via PowerShell, running services as AD users/groups), and Linux-specific guidance is missing or only briefly referenced. The section on encrypting disks has a TODO for Linux, indicating incomplete Linux coverage.
Recommendations
  • Add explicit Linux examples and guidance for disk encryption, including links to Azure documentation for encrypting disks on Linux VMSS clusters.
  • When mentioning Windows-specific features (e.g., AD accounts, gMSA, BitLocker), clarify Linux alternatives or limitations, and provide links to relevant Linux documentation.
  • Ensure parity in examples for running services under different accounts, showing both Windows and Linux approaches.
  • Review the order of presentation so Linux options are not consistently secondary to Windows options.
  • Complete the TODO for Linux disk encryption and BitLocker alternatives.
Service Fabric Monitor Azure Service Fabric ...main/articles/service-fabric/monitor-service-fabric.md
Medium Priority View Details →
Scanned: 2026-02-19 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides monitoring guidance for Azure Service Fabric clusters on both Windows and Linux, but there are several areas where Windows tools and patterns are mentioned first or exclusively. Windows-specific tools (Event Log, Event Viewer, Diagnostics Agent) are referenced before Linux equivalents, and some example/tutorial links focus on .NET/Windows scenarios. Linux alternatives are sometimes mentioned, but often as secondary or with less detail. There are few explicit Linux-focused examples or walkthroughs, and some features (like EventStore APIs) are noted as Windows-only without Linux alternatives or workarounds.
Recommendations
  • Ensure Linux monitoring tools and patterns are described with equal prominence and detail as Windows equivalents.
  • Add Linux-focused example walkthroughs and tutorials, especially for application monitoring and cluster diagnostics.
  • Where Windows-only features are mentioned (e.g., EventStore APIs), provide clear guidance or links for Linux users to achieve similar outcomes.
  • When referencing tools (e.g., Service Fabric Explorer, logging frameworks), clarify cross-platform compatibility and provide Linux/macOS setup instructions.
  • Avoid listing Windows tools or patterns first unless they are truly more relevant; alternate order or group by OS where appropriate.
Service Fabric Application lifecycle in Service Fabric ...service-fabric/service-fabric-application-lifecycle.md
Medium Priority View Details →
Scanned: 2026-02-19 00:00
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 all lifecycle phases (deploy, test, upgrade, remove, maintenance). While REST API and .NET methods are also mentioned, PowerShell examples are prominent and often listed before cross-platform alternatives. There is minimal mention of Linux-specific tools or CLI usage (such as sfctl or Azure CLI), and no explicit Linux/macOS examples are provided. The inclusion of PowerShell as the primary automation method and lack of Linux parity creates friction for non-Windows users.
Recommendations
  • Add explicit examples using sfctl (Service Fabric CLI) and Azure CLI for each lifecycle phase, especially for deployment, upgrade, and removal.
  • Ensure that cross-platform tools are mentioned alongside PowerShell cmdlets, not after or instead of them.
  • Provide sample commands and workflows for Linux/macOS environments, including file management and automation.
  • Clarify which methods and tools are available on Linux clusters and which are Windows-only.
  • Consider reordering examples so that REST API, sfctl, and Azure CLI are presented before or alongside PowerShell.
Service Fabric Advanced Application Upgrade Topics ...-fabric/service-fabric-application-upgrade-advanced.md
Medium Priority View Details →
Scanned: 2026-02-19 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page for 'Advanced Application Upgrade Topics' in Azure Service Fabric is heavily focused on PowerShell cmdlets and Windows-centric tooling. All command-line examples use PowerShell, and references to Service Fabric management are exclusively via PowerShell commands. There is no mention of Linux/macOS equivalents, such as the Service Fabric CLI (sfctl), nor are cross-platform examples provided. The documentation assumes the reader is using Windows and PowerShell, creating friction for Linux/macOS users who must translate instructions to their environment.
Recommendations
  • Add equivalent examples using the Service Fabric CLI (sfctl), which is cross-platform and supported on Linux/macOS.
  • Mention that PowerShell examples are for Windows and provide links or instructions for Linux/macOS users.
  • Where possible, provide ARM template or REST API examples alongside PowerShell to ensure platform neutrality.
  • Update 'Next steps' to include tutorials for Linux/macOS users, such as upgrading applications using sfctl.
Scanned: 2026-02-19 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides links to application upgrade tutorials using Visual Studio and PowerShell, both of which are primarily Windows tools. The PowerShell example is explicitly mentioned, while there is no reference to Linux-native tools or CLI equivalents for application upgrades. The serialization discussion is focused on C# and .NET, but this is appropriate for Service Fabric workloads and does not constitute bias. However, the upgrade guidance leans towards Windows-centric tooling.
Recommendations
  • Add references or links to application upgrade tutorials using Azure CLI or Service Fabric CLI (sfctl), which are cross-platform and commonly used on Linux/macOS.
  • Clarify whether PowerShell Core (pwsh) is supported for Linux/macOS users, or provide alternative instructions for those environments.
  • Consider including examples or guidance for upgrading applications from Linux/macOS environments, if supported by Service Fabric.
  • If Visual Studio is Windows-only, mention cross-platform alternatives such as Visual Studio Code or command-line tools.
Service Fabric Architecture of Azure Service Fabric ...articles/service-fabric/service-fabric-architecture.md
Medium Priority View Details →
Scanned: 2026-02-19 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation mentions PowerShell cmdlets as a primary management interface for Service Fabric, without referencing equivalent Linux/macOS tooling (such as Azure CLI or REST APIs). Additionally, Windows security is mentioned alongside X509 certificates in the transport subsystem, with no discussion of Linux authentication patterns. These choices suggest a Windows-first bias, though most architectural concepts are platform-neutral.
Recommendations
  • Add references to Linux/macOS-compatible management tools, such as Azure CLI and REST APIs, alongside PowerShell.
  • Clarify that PowerShell cmdlets are available cross-platform, or provide Linux/macOS-specific examples where relevant.
  • Mention Linux authentication mechanisms (e.g., certificate-based, SSH) in the transport subsystem discussion.
  • Ensure that all platform-neutral concepts are illustrated with examples or notes for both Windows and Linux environments.
Scanned: 2026-02-19 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page for restoring backups in Azure Service Fabric is heavily biased towards Windows and PowerShell usage. All code examples and instructions rely on PowerShell modules and cmdlets, with no mention of Linux/macOS-compatible tooling or CLI alternatives. The prerequisite section explicitly requires installation of a PowerShell module, and all REST API usage is demonstrated via PowerShell scripts. There are no Bash, Azure CLI, or curl examples, nor any guidance for non-Windows environments.
Recommendations
  • Add equivalent Bash or shell script examples using curl or HTTPie for REST API calls.
  • Document how to use Azure CLI or other cross-platform tools to trigger backup and restore operations.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is supported on PowerShell Core (pwsh) for Linux/macOS, and provide installation instructions if so.
  • Explicitly state any limitations or requirements for Windows-only tooling, and provide workarounds or alternatives for Linux/macOS users.
  • Consider including a section or callout for Linux/macOS users, outlining supported approaches and any differences.