810
Total Pages
600
Linux-Friendly Pages
210
Pages with Bias
25.9%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

718 issues found
Showing 126-150 of 718 flagged pages
Service Fabric Service Fabric project creation next steps ...ric/service-fabric-project-creation-next-step-tasks.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page exhibits a notable Windows bias. Tutorials and walkthroughs are exclusively for Windows, with no mention of Linux/macOS equivalents. Deployment instructions reference PowerShell and Windows-specific tools, and the 'Next steps' section highlights creating a Windows cluster without alternatives for Linux. There is no guidance or parity for users on Linux or macOS platforms.
Recommendations
  • Add equivalent tutorials and walkthroughs for Linux (and macOS) environments, including examples for creating clusters, deploying applications, and managing services.
  • Include deployment instructions using cross-platform tools (e.g., Azure CLI, Bash scripts) alongside PowerShell.
  • Clearly indicate which features or steps are Windows-only, and provide alternatives or workarounds for Linux/macOS users.
  • Reorder examples or provide parallel instructions so Windows and Linux users are equally supported.
  • Mention Service Fabric Explorer and other tools' availability or alternatives for non-Windows platforms.
Service Fabric Create an actor-based service on Azure Service Fabric ...e-fabric/service-fabric-reliable-actors-get-started.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily Windows-centric, focusing exclusively on Visual Studio and Windows tooling for C# development. All examples, screenshots, and instructions assume a Windows environment, with no Linux/macOS equivalents provided. PowerShell is used for package management, and there are no instructions for using Linux-compatible tools or IDEs. Although a Java/Linux link is mentioned at the top, the main content does not address Linux users or provide parity for C# development on non-Windows platforms.
Recommendations
  • Add equivalent instructions for developing Reliable Actors in C# on Linux/macOS, such as using VS Code, JetBrains Rider, or the .NET CLI.
  • Include Linux/macOS-specific commands for package management (e.g., dotnet CLI instead of PowerShell).
  • Provide screenshots and steps for Linux/macOS environments.
  • Clarify which steps are Windows-only and offer alternatives for other platforms.
  • Ensure that prerequisites and setup instructions cover cross-platform development environments.
Service Fabric Create your first Service Fabric application in C# ...fabric/service-fabric-reliable-services-quick-start.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily oriented toward Windows development, specifically using Visual Studio and PowerShell scripts. All examples and instructions are for C# on Windows, with no Linux/macOS equivalents provided for project creation, deployment, or diagnostics. Windows-specific tools and patterns (Visual Studio, ETW, PowerShell) are mentioned exclusively, and Linux alternatives are absent.
Recommendations
  • Provide equivalent instructions and examples for Linux/macOS users, such as using the Service Fabric CLI (sfctl), dotnet CLI, or VS Code.
  • Include Linux/macOS deployment steps, such as building and running Service Fabric applications using terminal commands.
  • Mention Linux-compatible diagnostic and logging tools (e.g., using sfctl or log files) instead of only referencing ETW and Visual Studio windows.
  • Add links to Linux/macOS quickstarts and ensure parity in the 'Next steps' section.
  • Clarify which steps are Windows-only and offer alternatives or links for other platforms.
Service Fabric Run an Azure Service Fabric service as an AD user or group ...bric/service-fabric-run-service-as-ad-user-or-group.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on Windows environments, specifically Windows Server standalone clusters and Active Directory. All examples and instructions reference Windows-only technologies (Active Directory, PowerShell, gMSA), with no mention of Linux or cross-platform equivalents. The use of PowerShell commands and Windows-centric security models excludes Linux/macOS users, making it unclear if or how these steps could be performed on non-Windows platforms.
Recommendations
  • Clarify whether running Service Fabric services as AD users/groups is supported or possible on Linux clusters. If not, explicitly state this limitation.
  • If Linux support exists, provide equivalent instructions and examples for Linux clusters, including relevant tools and authentication mechanisms.
  • Mention cross-platform alternatives to PowerShell commands, or provide CLI/bash equivalents where possible.
  • Consider referencing Microsoft Entra ID or other identity providers that may be more cross-platform friendly, if applicable.
Service Fabric Run an Azure Service Fabric service under a gMSA account ...s/service-fabric/service-fabric-run-service-as-gmsa.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily focused on Windows environments, specifically Windows Server standalone clusters. All examples and instructions use Windows-specific tools (PowerShell cmdlets, Windows Features), and there is no mention of Linux or cross-platform equivalents. The prerequisites and steps assume a Windows infrastructure and Active Directory, with no guidance for Linux clusters or non-Windows authentication mechanisms.
Recommendations
  • Clearly state at the beginning that the instructions are Windows-only and provide links or notes about Linux/macOS support (or lack thereof).
  • If Service Fabric on Linux supports similar functionality, add equivalent instructions for Linux clusters, including relevant tools and configuration steps.
  • If gMSA is not supported on Linux, mention alternative secure credential management approaches for Linux clusters.
  • Provide a comparison table or section outlining differences between Windows and Linux Service Fabric cluster authentication options.
Service Fabric Azure Service Fabric reverse proxy ...articles/service-fabric/service-fabric-reverseproxy.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a strong Windows bias. The reverse proxy feature is explicitly stated as unavailable for Linux clusters, with all examples, configuration guidance, and referenced tools (such as http.sys-based servers and Windows-specific environment setup) tailored to Windows environments. There are no Linux equivalents or workarounds provided, and critical functionality is not supported on Linux.
Recommendations
  • Clearly state the lack of Linux support at the top of the article and in the prerequisites.
  • Provide guidance or alternatives for Linux users, such as recommended patterns for service discovery and communication in Linux clusters.
  • If possible, include a roadmap or link to updates regarding Linux support for reverse proxy.
  • Offer Linux-specific examples or documentation for similar scenarios (e.g., using nginx or Envoy as a reverse proxy in Service Fabric Linux clusters).
  • Reference Linux-compatible tools and patterns where applicable, or clarify Windows-only sections.
Service Fabric Run a script when an Azure Service Fabric service starts ...fabric/service-fabric-run-script-at-service-startup.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page is heavily biased towards Windows environments. All code and script examples use Windows batch files (.bat), Windows-specific tools (setx, REG, PowerShell.exe), and Windows filesystem paths. Visual Studio instructions and screenshots are Windows-centric. Linux is only briefly mentioned in a single note about AccountType, with no Linux shell script or deployment examples provided.
Recommendations
  • Provide equivalent Linux examples using shell scripts (e.g., MySetup.sh) and Linux commands for setting environment variables.
  • Include instructions for packaging and deploying startup scripts in Linux Service Fabric clusters, including file permissions and location.
  • Show how to debug startup scripts on Linux, including log file locations and redirection.
  • Add parity for PowerShell examples by providing bash or sh equivalents.
  • Clarify differences in user/account configuration between Windows and Linux clusters, with explicit Linux manifest samples.
Service Fabric Scale up an Azure Service Fabric non-primary node type ...abric/service-fabric-scale-up-non-primary-node-type.md
High Priority View Details →
Scanned: 2026-01-12 00:00
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 biased towards Windows environments, with all command-line examples provided in PowerShell, explicit references to Windows file paths (e.g., C:\), and instructions for certificate management and deployment that assume Windows tooling. There are no Linux/macOS CLI equivalents, and the VM upgrade scenario focuses exclusively on Windows Server SKUs. This creates significant friction for Linux/macOS users attempting to follow the guide.
Recommendations
  • Provide equivalent Azure CLI (az) commands for all PowerShell examples, ensuring cross-platform compatibility.
  • Include Linux/macOS file path examples and instructions for certificate generation and management (e.g., using OpenSSL).
  • Add guidance for upgrading clusters with Linux-based VM SKUs, not just Windows Server.
  • Explicitly state platform requirements and offer links to platform-specific guides where appropriate.
  • Reorder examples so that cross-platform solutions (Azure CLI, ARM templates) are presented before or alongside Windows/PowerShell-specific instructions.
Service Fabric Containerize your Azure Service Fabric services on Windows ...ce-fabric/service-fabric-services-inside-containers.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is exclusively focused on Windows, with explicit statements that the feature only works for Windows. All examples, instructions, and tooling (Visual Studio, PowerShell scripts, Windows container isolation modes) are Windows-specific. There are no Linux/macOS equivalents, nor any guidance for those platforms.
Recommendations
  • Clearly state Windows-only support at the top and provide a link to Linux containerization guidance if/when available.
  • Add a section describing the status of Linux/macOS support and any workarounds or alternatives.
  • If possible, provide Linux/macOS equivalents for packaging, scripting, and deployment steps (e.g., Bash scripts, Docker commands).
  • Mention cross-platform tools or approaches where relevant, or clarify that certain steps are not applicable outside Windows.
  • Ensure future updates include Linux parity as Service Fabric container support evolves.
Service Fabric Scale up an Azure Service Fabric primary node type ...ce-fabric/service-fabric-scale-up-primary-node-type.md
High Priority View Details →
Scanned: 2026-01-12 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 is heavily biased toward Windows environments, with all command-line examples provided in PowerShell and references to Windows file paths and certificate stores. The upgrade scenario is described only for Windows Server OS, and Linux-specific instructions are minimal and not integrated into the main workflow. There are no Bash, Azure CLI, or Linux-native examples, and Windows tools and conventions are used throughout.
Recommendations
  • Provide equivalent Bash/Azure CLI examples for all PowerShell commands, especially for cluster deployment, certificate management, and resource cleanup.
  • Include Linux file path and certificate store references where relevant.
  • Offer a parallel Linux scenario (e.g., upgrading from Ubuntu 18.04 to Ubuntu 20.04) with step-by-step instructions.
  • Clearly indicate which steps differ for Linux clusters and provide explicit guidance.
  • Avoid assuming Windows as the default; present Windows and Linux options side-by-side or in separate sections.
  • Reference Linux tools (e.g., openssl for certificate generation, Linux file system paths) where appropriate.
Service Fabric Testability: Service communication ...ice-fabric-testability-scenarios-service-communication.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively provides PowerShell cmdlet examples (e.g., Move-ServiceFabricPrimaryReplica, Stop-ServiceFabricNode, Invoke-ServiceFabricPartitionQuorumLoss) for all testability actions, which are Windows-centric tools. There are no equivalent examples or instructions for Linux or macOS users, nor any mention of cross-platform alternatives. This creates friction for non-Windows users attempting to follow the guidance.
Recommendations
  • Add equivalent CLI examples using Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • Explicitly mention that PowerShell cmdlets are Windows-only and provide links or instructions for Linux/macOS users.
  • Reorder examples so that cross-platform tools (sfctl) are presented first or alongside PowerShell examples.
  • Include a table or section summarizing available tools for each platform.
Service Fabric Tutorial: Build a .NET application in Azure Service Fabric ...ce-fabric/service-fabric-tutorial-create-dotnet-app.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The tutorial is heavily oriented toward Windows development, requiring Visual Studio and a Windows developer computer. All instructions, screenshots, and tooling references are for Windows and Visual Studio, with no mention of Linux/macOS alternatives or cross-platform development options. There are no examples or guidance for Linux users, and key steps (local cluster setup, debugging, project creation) are tied to Windows-only tools.
Recommendations
  • Add explicit instructions for Linux/macOS users, including prerequisites and supported tooling (e.g., Visual Studio Code, CLI tools).
  • Describe how to create and manage Service Fabric clusters locally on Linux/macOS, referencing the Service Fabric CLI (sfctl) and Docker-based clusters.
  • Provide equivalent steps for project creation and deployment using dotnet CLI and VS Code, including screenshots or terminal commands.
  • Clarify which steps are Windows-only and offer alternatives or workarounds for other platforms.
  • Include troubleshooting notes for Linux/macOS environments, especially around cluster setup and debugging.
Service Fabric Create infrastructure for a cluster on AWS ...rvice-fabric-tutorial-standalone-create-infrastructure.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily biased toward Windows. All examples and instructions assume the use of Windows Server EC2 instances, with PowerShell scripts and Windows-specific tools (RDP, net use, SMB, remote registry). There are no Linux/macOS alternatives or guidance, despite Service Fabric's 'any OS, any cloud' positioning.
Recommendations
  • Provide parallel instructions for creating Linux-based EC2 instances, including recommended distributions and configuration steps.
  • Include Linux shell script equivalents for setting up users, configuring firewalls, and opening ports.
  • Offer guidance for connecting to Linux instances (e.g., SSH) and validating connectivity (e.g., using scp, sftp, or NFS instead of SMB).
  • Clarify which Service Fabric features require Windows and which are available cross-platform.
  • Explicitly state the limitations (if any) of running Service Fabric on Linux, and link to relevant documentation.
Service Fabric Standalone Service Fabric clusters overview ...-fabric/service-fabric-standalone-clusters-overview.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a notable Windows bias. While the introduction claims Service Fabric clusters run on both Windows Server and Linux, the detailed sections focus almost exclusively on Windows features, authentication methods, and supported operating systems. Windows security mechanisms (Kerberos, group Managed Service Accounts, Active Directory) are described in detail, with no equivalent Linux authentication or management patterns mentioned. The 'Supported operating systems' section explicitly states that Linux isn't yet supported for standalone clusters, contradicting the initial claim of Linux support. No Linux-specific examples, tools, or guidance are provided.
Recommendations
  • Clarify the actual Linux support status for standalone clusters at the top of the page to avoid misleading users.
  • If Linux support is planned or partial, provide a roadmap or guidance for Linux users.
  • Add Linux-specific sections or examples for cluster creation, security (e.g., certificate management, Linux authentication patterns), and management.
  • Mention Linux equivalents for Windows tools and patterns (such as using OpenSSL for certificates, Linux service accounts, etc.).
  • Ensure that any future updates maintain parity in examples and instructions for both platforms.
Service Fabric Define Service Configuration in StartupServices.xml for a Service Fabric Application ...service-fabric/service-fabric-startupservices-model.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page is heavily oriented toward Windows development environments, specifically Visual Studio. All workflow descriptions, examples, and screenshots reference Visual Studio features (Build/Rebuild/F5/Ctrl+F5/Publish), which are Windows-only. The only command-line tooling mentioned is PowerShell, with no mention of Linux/macOS equivalents (e.g., Bash, CLI tools). There are no examples or guidance for Linux/macOS users, nor any mention of how to achieve similar workflows outside of Windows/Visual Studio.
Recommendations
  • Add explicit guidance for deploying Service Fabric applications on Linux/macOS, including supported workflows and tooling.
  • Provide command-line examples using cross-platform tools (e.g., Azure CLI, Bash scripts) alongside PowerShell.
  • Clarify which features (such as StartupServices.xml) are Visual Studio/Windows-only and suggest alternatives for Linux/macOS users.
  • Include screenshots or descriptions for non-Windows environments if supported.
  • Add a section summarizing platform limitations and parity for Service Fabric application deployment.
Service Fabric Monitor a Service Fabric cluster in Azure ...vice-fabric/service-fabric-tutorial-monitor-cluster.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation is heavily biased toward Windows environments. It repeatedly references Windows clusters, Windows-specific tools (such as Windows Performance Counters), and PowerShell cmdlets for monitoring and health queries. There are no Linux cluster creation or monitoring examples, nor any mention of Linux equivalents for performance counters or command-line tools. All example commands and walkthroughs are Windows-centric, with no guidance for Linux/macOS users.
Recommendations
  • Add explicit instructions and examples for creating and monitoring Linux Service Fabric clusters, including links to Linux cluster templates.
  • Include Linux/macOS equivalents for all PowerShell cmdlets, such as REST API, Azure CLI, or Service Fabric CLI (sfctl) commands.
  • Document how to collect and monitor Linux performance counters, referencing Linux tools (e.g., collectd, sysstat, or Azure Monitor's Linux agent).
  • Ensure parity in screenshots and walkthroughs for Linux clusters in the Azure portal.
  • Where Windows-specific references are made (e.g., Windows Performance Counters), provide a Linux alternative or clarify platform limitations.
Service Fabric Configure the upgrade of a Service Fabric application ...abric/service-fabric-visualstudio-configure-upgrade.md
High Priority View Details →
Scanned: 2026-01-12 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 focuses exclusively on Windows-centric tools and workflows, specifically Visual Studio and PowerShell, for configuring and upgrading Service Fabric applications. There are no examples or guidance for Linux/macOS users, nor are cross-platform CLI alternatives mentioned. The upgrade process is described only in terms of Visual Studio dialogs and PowerShell commands, both of which are primarily available on Windows.
Recommendations
  • Add instructions and examples for upgrading Service Fabric applications using cross-platform tools such as Azure CLI or Service Fabric CLI (sfctl).
  • Include Linux/macOS-specific workflows and screenshots where applicable.
  • Mention platform requirements and alternatives up front, clarifying which steps are Windows-only and providing parity for other operating systems.
  • Provide sample commands for Linux shells (bash/zsh) alongside PowerShell examples.
  • Reference documentation for Service Fabric development on Linux/macOS clusters.
Service Fabric Service Fabric app upgrade tutorial ...-fabric/service-fabric-application-upgrade-tutorial.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The tutorial is heavily focused on Visual Studio, a Windows-centric tool, with all steps and screenshots assuming a Windows environment. There are no Linux/macOS equivalents or alternative instructions for non-Windows users. The only alternative mentioned is a separate PowerShell tutorial, which is also Windows-focused. No cross-platform CLI or Linux-native tooling is referenced.
Recommendations
  • Provide equivalent instructions using cross-platform tools such as Azure CLI or Service Fabric CLI (sfctl).
  • Include examples and screenshots for Linux/macOS environments, such as using VS Code or command-line workflows.
  • Explicitly mention platform requirements and offer guidance for non-Windows users at the start of the tutorial.
  • Link to or create tutorials for Linux/macOS users covering the same upgrade workflow.
Service Fabric Update the RDP username and password in PowerShell ...ts/service-fabric-powershell-change-rdp-user-and-pw.md
High Priority View Details →
Scanned: 2026-01-10 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 is heavily biased towards Windows and PowerShell. All examples and instructions use Azure PowerShell, with no mention of Bash, Azure CLI, or Linux/macOS-compatible workflows. The script and command explanations are PowerShell-only, and installation instructions reference only the Azure PowerShell guide. There are no Linux or cross-platform alternatives provided.
Recommendations
  • Add equivalent Azure CLI or Bash examples for updating RDP credentials on VMSS nodes.
  • Include installation instructions for Azure CLI and note its cross-platform compatibility.
  • Explicitly state platform requirements and provide guidance for Linux/macOS users.
  • Reorder sections to present cross-platform solutions before or alongside Windows/PowerShell ones.
Service Fabric How to migrate to TLS (Transport Layer Security) 1.3 for Service Fabric ...vice-fabric/how-to-migrate-transport-layer-security.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows Only Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation is explicitly Windows-centric, stating that Linux is not supported for TLS 1.3 migration in Service Fabric clusters. All prerequisites, upgrade instructions, and compatibility notes reference Windows Server, PowerShell, and Windows application manifests. There are no Linux equivalents, examples, or instructions, and Linux users are told outright that the steps do not apply to them.
Recommendations
  • Add a clear roadmap or timeline for Linux support for TLS 1.3 in Service Fabric clusters.
  • Provide alternative instructions or workarounds for Linux users, or explicitly link to relevant Linux documentation.
  • Include a prominent callout at the top of the article clarifying the lack of Linux support and suggesting next steps for Linux users.
  • When Linux support is available, ensure examples, prerequisites, and upgrade steps are provided for both Windows and Linux, with parity in detail and order.
Service Fabric RunToCompletion semantics and specifications ...blob/main/articles/service-fabric/run-to-completion.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias: all code examples use Windows containers and Windows-specific commands (cmd, set, exit, etc.), and the example explicitly references Windows container images. Querying deployment status is described only via PowerShell and C# APIs, with no mention of Linux CLI or cross-platform alternatives. There are no Linux container or macOS examples, nor any guidance for non-Windows environments.
Recommendations
  • Add parallel examples using Linux containers (e.g., Ubuntu or Alpine images) with equivalent shell commands.
  • Include instructions for querying deployment status using Service Fabric CLI (sfctl), which is cross-platform.
  • Clarify which features and patterns are supported on Linux clusters, and note any differences.
  • Present examples for both Windows and Linux side-by-side, or indicate platform-specific sections.
  • Reference Linux container compatibility and provide links to relevant documentation.
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exclusively uses PowerShell commands and outputs for troubleshooting Service Fabric application upgrades, with no mention of Linux or macOS equivalents (such as Azure CLI, REST API, or Service Fabric CLI). All example commands and troubleshooting steps are Windows-centric, and the 'Next steps' section prioritizes Visual Studio and PowerShell, both Windows-focused tools. There is no guidance for users on Linux or macOS platforms, nor any cross-platform instructions.
Recommendations
  • Add equivalent examples using Azure CLI, Service Fabric CLI (sfctl), or REST API for all PowerShell commands.
  • Explicitly mention cross-platform tools and workflows for troubleshooting upgrades on Linux/macOS clusters.
  • Include sample outputs and troubleshooting steps for Linux environments.
  • In the 'Next steps' section, link to upgrade tutorials using CLI or REST API, not just Visual Studio and PowerShell.
  • Where possible, provide a table or side-by-side comparison of commands for Windows (PowerShell) and Linux/macOS (CLI).
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page is heavily biased towards Windows and PowerShell. All command-line examples use PowerShell and require the Microsoft.ServiceFabric.Powershell.Http module, which is Windows-centric. There are no CLI or script examples for Linux/macOS users (e.g., Bash, Azure CLI, curl). The prerequisites and workflow assume a Windows environment, and Windows tools are mentioned exclusively and first. This creates friction for Linux/macOS users and may prevent them from completing the task without significant adaptation.
Recommendations
  • Provide equivalent examples using Bash, Azure CLI, or curl for Linux/macOS users.
  • Clarify whether the PowerShell module is cross-platform (PowerShell Core) or Windows-only, and offer alternatives if needed.
  • Add instructions for connecting to clusters and triggering backups using REST APIs with non-PowerShell tools.
  • Mention Linux/macOS compatibility and requirements explicitly in the prerequisites.
  • Reorder examples to present cross-platform or REST API methods before Windows/PowerShell-specific ones.
Service Fabric Upgrading Azure Service Fabric managed clusters ...cles/service-fabric/how-to-managed-cluster-upgrades.md
High Priority View Details →
Scanned: 2026-01-09 19:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias by exclusively showing examples and references for Windows environments. The REST API output only lists Windows cluster versions, with no mention or examples of Linux equivalents. There are no Linux-specific instructions, examples, or references to Linux tools or operating systems throughout the page.
Recommendations
  • Include examples and instructions for Linux-based Service Fabric clusters, such as showing REST API output for Linux cluster versions.
  • Explicitly mention Linux support where relevant, including in the 'Query for supported cluster versions' section.
  • Add guidance for managing upgrades on Linux clusters, including any differences in configuration or supported features.
  • Ensure parity in documentation by providing both Windows and Linux examples side-by-side where applicable.
Service Fabric Manage Azure Service Fabric application secrets ...fabric/service-fabric-application-secret-management.md
High Priority View Details →
Scanned: 2026-01-09 19:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a Windows-first bias by referencing Windows and PowerShell tooling before Linux equivalents, and providing only PowerShell and C# examples for application deployment and parameter overrides. There are no Linux-specific command-line examples (e.g., Bash, CLI), and the use of PowerShell is presented as the default scripting option. The section on setting up encryption certificates does link to both Windows and Linux guides, but all in-page examples and automation references are Windows-centric.
Recommendations
  • Provide equivalent Linux command-line examples (e.g., Bash scripts using Azure CLI or Service Fabric CLI) for creating application instances and overriding parameters.
  • Mention Linux tooling (such as sfctl or Azure CLI) alongside PowerShell, and present both options in parallel.
  • Avoid language that implies PowerShell is the default or only automation method; clarify cross-platform alternatives.
  • Ensure that all steps and code samples have Linux equivalents, or explicitly note platform differences where parity is not possible.
  • Consider alternating the order of Windows and Linux references, or present them side-by-side to reinforce platform neutrality.