Service Fabric

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 576-600 of 718 flagged pages
Service Fabric Set up Microsoft Entra ID for client authentication in the Azure portal ...vice-fabric-cluster-creation-setup-azure-ad-via-portal.md
Medium Priority View Details →
Scanned: 2026-01-12 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 detailed instructions and examples for configuring Microsoft Entra ID authentication for Service Fabric clusters, but all command-line connection examples use PowerShell, with no Linux/macOS equivalents (such as Azure CLI or REST API). Troubleshooting and connection sections reference PowerShell exclusively. While there are some notes about Linux-specific limitations, the overall guidance and examples are Windows-centric, making it harder for Linux/macOS users to follow or replicate the steps.
Recommendations
  • Add equivalent Linux/macOS connection instructions using Azure CLI or REST API, especially for cluster authentication and management tasks.
  • Provide explicit examples for connecting to Service Fabric clusters from Linux/macOS environments, including required tools and setup steps.
  • Include troubleshooting steps and solutions for common issues encountered on Linux/macOS, not just PowerShell/Windows.
  • Clarify any platform-specific limitations and offer workarounds or alternatives for Linux/macOS users.
  • Where possible, present cross-platform commands (e.g., Azure CLI) before or alongside PowerShell 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 →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. While it mentions both Windows and Linux node types in the Service Fabric extension, several examples and references (such as dataPath using Windows-style paths and certificate store naming) are Windows-centric. The 'Next steps' section prioritizes Windows-specific tasks like RDP port changes and admin credential management, with links to PowerShell scripts and RDP usage, but does not provide equivalent Linux SSH instructions or examples. There are no explicit Linux/macOS walkthroughs or parity in remote connection guidance.
Recommendations
  • Add Linux/macOS-specific examples for connecting to cluster nodes (e.g., SSH instructions alongside RDP/PowerShell).
  • Include Linux-style paths (e.g., /var/svcfab) in the Service Fabric extension example and clarify cross-platform usage.
  • Provide parity in 'Next steps' by linking to Linux/macOS remote connection and credential management guides.
  • Explicitly mention and demonstrate Linux tools and workflows where Windows tools (RDP, PowerShell) are referenced.
GitHub Create Pull Request
Service Fabric Remote connect to an Azure Service Fabric cluster node ...ce-fabric-cluster-remote-connect-to-azure-cluster-node.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows-first bias: Windows (RDP) connection steps and screenshots are presented before Linux (SSH) equivalents, and the examples and visuals focus primarily on Windows tools (Remote Desktop Connection). Additionally, the 'Next steps' section links to PowerShell scripts for Windows-specific tasks, with no Linux alternatives provided.
Recommendations
  • Provide Linux/SSH connection screenshots and examples alongside or before Windows/RDP examples.
  • Include links to Linux-specific scripts or CLI instructions for tasks like changing SSH port ranges and updating admin credentials.
  • Balance the presentation order so that Linux and Windows instructions are equally prominent.
  • Reference cross-platform tools (e.g., Azure CLI, Bash) where possible, not just PowerShell.
  • Clarify any OS-specific differences in steps and provide parity in troubleshooting guidance.
GitHub Create Pull Request
Service Fabric Import certificates into a container ...s/service-fabric/service-fabric-securing-containers.md
Medium 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 demonstrates a moderate Windows bias. Windows-specific details (such as PFX export, ACLs, and environment variables) are described first and in greater depth, with Linux equivalents mentioned briefly and lacking code examples. The only code sample provided is C# for importing a PFX file, which is relevant to Windows but not Linux (which uses PEM and unencrypted private keys). There are no Linux shell or code examples for certificate import, nor guidance on handling PEM/private key files inside Linux containers.
Recommendations
  • Provide equivalent Linux-focused code examples (e.g., Bash or Python) for importing PEM and private key files inside containers.
  • Describe Linux-specific certificate handling steps, including file permissions and security considerations.
  • Present Windows and Linux instructions/examples in parallel, or clearly separate them for clarity.
  • Include references to Linux-native tools (e.g., openssl) for certificate import and management.
  • Clarify differences in environment variables and certificate formats between platforms with side-by-side tables or sections.
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 →
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 page provides code samples for configuring Service Fabric placement policies using C# and PowerShell only. PowerShell is a Windows-centric tool, and no equivalent Linux/macOS command-line examples (such as Azure CLI, Bash, or REST API) are provided. The documentation assumes familiarity with Windows tooling and omits guidance for Linux-based Service Fabric clusters, which can create friction for non-Windows users.
Recommendations
  • Add Azure CLI examples for all placement policy configurations, as Azure CLI is cross-platform.
  • Include REST API examples for service creation and placement policy configuration.
  • Explicitly mention how Linux-based Service Fabric clusters can be managed, and link to relevant documentation.
  • If PowerShell is required, clarify whether PowerShell Core (cross-platform) is supported and provide usage instructions for Linux/macOS.
  • Present cross-platform examples (CLI, REST) before or alongside PowerShell to avoid Windows-first bias.
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 →
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 provides detailed examples for configuring auto scaling in Azure Service Fabric using PowerShell and C# APIs, both of which are strongly associated with Windows environments. There are no equivalent Linux/macOS CLI or scripting examples (e.g., Bash, Azure CLI, REST API), and PowerShell is presented as the primary command-line automation tool. Windows-centric tools and patterns are referenced exclusively, and Linux support is mentioned only in passing, with no actionable guidance for Linux users.
Recommendations
  • Add examples using Azure CLI, Bash scripts, or REST API for configuring auto scaling policies, ensuring Linux/macOS users have clear, actionable steps.
  • Explicitly document which features and commands are supported on Linux clusters, and provide guidance for Linux-specific workflows.
  • Where PowerShell is used, offer equivalent commands using cross-platform tools (e.g., Azure CLI) and clarify platform compatibility.
  • Reorder examples so that cross-platform or Linux-compatible methods are presented before or alongside Windows/PowerShell methods.
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 →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page exhibits a moderate Windows bias. Windows terminology and configuration formats (ClusterManifest.xml with <WindowsServer>), Windows-specific examples, and PowerShell commands are presented before or more prominently than Linux equivalents. There is little explicit mention of Linux-specific configuration or tooling, and the examples and instructions assume a Windows-centric environment, especially for standalone clusters and local development. PowerShell is used for service management examples, with no Linux CLI or bash alternatives provided.
Recommendations
  • Provide explicit Linux configuration examples, such as using Linux-based node definitions in ClusterManifest.xml or ClusterConfig.json.
  • Include Linux CLI equivalents (e.g., Service Fabric CLI (sfctl)) alongside PowerShell commands for service creation and updates.
  • Clarify that Service Fabric supports both Windows and Linux nodes, and note any differences in configuration or deployment steps.
  • Where examples use <WindowsServer> in XML, also show <Linux> or cross-platform alternatives.
  • Add notes or sections on Linux-specific considerations for cluster setup, node properties, and resource management.
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 →
Scanned: 2026-01-12 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 command-line examples exclusively in PowerShell, which is a Windows-centric tool, and does not mention or provide equivalent examples for Linux or macOS environments (such as Bash, CLI, or shell scripts). The PowerShell examples are presented first and are the only command-line examples, creating friction for users on non-Windows platforms. There is no discussion of Linux-specific tools or patterns, nor any guidance for Linux/macOS users on how to perform the same operations.
Recommendations
  • Add Azure CLI or Bash examples for service creation and update commands, ensuring Linux/macOS users have clear instructions.
  • Explicitly mention cross-platform tools and provide guidance for running Service Fabric commands on Linux/macOS.
  • Clarify whether PowerShell commands can be run via PowerShell Core on Linux/macOS, or provide alternatives if not.
  • Reorder examples or provide parallel Windows and Linux/macOS sections to avoid implicit prioritization of Windows.
GitHub Create Pull Request
Service Fabric Roll over an Azure Service Fabric cluster certificate ...vice-fabric/service-fabric-cluster-rollover-cert-cn.md
Medium 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 provides only a Windows PowerShell script for rolling over a Service Fabric cluster certificate, with Windows file paths and no mention of Linux/macOS equivalents. There are no Bash, CLI, or cross-platform examples, and the workflow assumes use of Windows tools and conventions.
Recommendations
  • Add equivalent instructions and scripts using Azure CLI and Bash for Linux/macOS users.
  • Use cross-platform file path examples or clarify platform-specific differences.
  • Explicitly mention how Linux/macOS users can perform certificate upload and VMSS update steps.
  • Provide guidance on running Azure PowerShell in cross-platform environments (e.g., PowerShell Core on Linux/macOS) if applicable.
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 →
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 consistently provides PowerShell examples for all operations, which is a Windows-centric tool. There are no equivalent examples for Linux/macOS users, such as Azure CLI, Bash, or REST API commands. The PowerShell examples are always presented first, reinforcing a Windows-first perspective. This creates friction for users on non-Windows platforms, as they must seek out alternative methods themselves.
Recommendations
  • Add equivalent Azure CLI, Bash, or REST API examples for all PowerShell commands.
  • Clearly indicate which commands are platform-specific and provide guidance for Linux/macOS users.
  • Consider presenting cross-platform examples (e.g., Azure CLI) before or alongside PowerShell to promote parity.
  • Reference official documentation for Linux/macOS management of Service Fabric clusters.
GitHub Create Pull Request
Service Fabric Cluster Resource Manager - Management Integration ...fabric-cluster-resource-manager-management-integration.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides a detailed example of querying Service Fabric health using a PowerShell command (Get-ServiceFabricPartitionHealth), which is specific to Windows environments. There are no equivalent examples or instructions for Linux/macOS users, such as using the Service Fabric CLI (sfctl) or REST API. The only command-line tooling shown is Windows-centric, and no Linux-native tools or patterns are mentioned.
Recommendations
  • Add equivalent Linux/macOS examples using sfctl or REST API for health queries.
  • Explicitly mention cross-platform tooling and provide instructions for both Windows and Linux/macOS users.
  • Where PowerShell is used, include the analogous command for Linux (e.g., sfctl partition health).
  • Clarify any platform-specific limitations or differences in tooling.
GitHub Create Pull Request
Service Fabric Azure Service Fabric standalone cluster scaling ...ce-fabric/service-fabric-cluster-scaling-standalone.md
Medium 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 page exhibits a notable Windows bias. It references PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) as the primary method for managing and scaling standalone Service Fabric clusters, without mentioning equivalent Linux commands, tools, or workflows. The linked 'scale a standalone cluster' guide is explicitly for Windows Server, and there is no guidance or examples for Linux-based clusters. This creates friction for Linux/macOS users and implies that Windows is the default or only supported platform for standalone cluster management.
Recommendations
  • Provide equivalent Linux examples using Service Fabric CLI (sfctl), REST API, or other cross-platform tools for cluster scaling operations.
  • Clarify platform support for standalone clusters (Windows vs. Linux) and explicitly mention any limitations.
  • Add links or sections for Linux-specific cluster scaling documentation, if available.
  • Ensure that references to PowerShell cmdlets are accompanied by Linux alternatives or a note about platform compatibility.
  • Reorganize examples so that Windows and Linux instructions are presented side-by-side or in parallel sections.
GitHub Create Pull Request
Service Fabric Secure an Azure Service Fabric cluster ...cles/service-fabric/service-fabric-cluster-security.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. While it mentions that Service Fabric clusters can run on both Azure (which can be Linux or Windows) and standalone Windows Server, the examples and linked guides for standalone clusters are exclusively for Windows. Windows authentication (Kerberos) is discussed in detail, with no mention of Linux equivalents (such as LDAP, PAM, or certificate-based authentication on Linux). Certificate creation and management references Windows Server certificate services and Windows tools, with no guidance for Linux-based certificate management. There are no explicit Linux examples or instructions for standalone clusters, and Windows terminology and tools are referenced first and exclusively in several sections.
Recommendations
  • Add explicit instructions and examples for setting up node-to-node and client-to-node security on standalone Linux clusters.
  • Include Linux-compatible certificate creation and management workflows (e.g., using OpenSSL, Let's Encrypt, or other Linux CA tools).
  • Reference Linux authentication mechanisms or clarify how certificate-based authentication works on Linux clusters.
  • Balance references to Windows tools (e.g., MakeCert.exe, Windows Server certificate service) with Linux alternatives.
  • Where standalone clusters are discussed, clarify support and provide parity for Linux environments.
GitHub Create Pull Request
Service Fabric Scale a Service Fabric cluster in or out .../service-fabric/service-fabric-cluster-scale-in-out.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. PowerShell is used extensively for examples and critical operations (such as node removal), with Windows-specific cmdlets and terminology (e.g., Remove-ServiceFabricNodeState, Get-ServiceFabricNode). While Azure CLI and sfctl commands are provided, PowerShell examples are often presented first and in more detail. There is no explicit mention of Linux shell equivalents for Service Fabric management tasks, nor guidance for Linux/macOS users regarding prerequisites or environment setup. The documentation assumes familiarity with Windows tooling and omits Linux-specific instructions for connecting to clusters or running Service Fabric commands.
Recommendations
  • Provide Linux/macOS shell (bash) equivalents for all PowerShell examples, especially for critical operations like node removal and scaling.
  • Clearly indicate which commands are cross-platform and which are Windows-only.
  • Add guidance for Linux/macOS users on setting up Service Fabric CLI tools and connecting to clusters.
  • Present Azure CLI and sfctl examples before or alongside PowerShell, rather than after.
  • Include troubleshooting notes for common Linux/macOS issues (e.g., permissions, environment variables).
GitHub Create Pull Request
Service Fabric Common questions about Microsoft Azure Service Fabric ...cles/service-fabric/service-fabric-common-questions.md
Medium 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 exhibits several signs of Windows bias. Examples and recommendations often reference Windows-specific tools (e.g., PowerShell, Windows Server upgrade paths), and anti-virus exclusions list only Windows directories and processes. Where authentication to Key Vault is discussed, PowerShell is suggested as the method, with no mention of Linux alternatives. There are no explicit Linux or bash examples, and Windows terminology (e.g., 'Program Files') is used exclusively. Linux/macOS users may find it difficult to map these instructions to their environments.
Recommendations
  • Provide Linux/macOS equivalents for all Windows-specific instructions, such as bash scripts or CLI commands.
  • List anti-virus exclusions for Linux-based clusters, including relevant directories and processes.
  • When discussing OS upgrades, include guidance for Linux distributions (e.g., Ubuntu, CentOS) alongside Windows Server.
  • Offer authentication examples using cross-platform tools (e.g., Azure CLI, REST API) in addition to PowerShell.
  • Avoid using Windows terminology exclusively; clarify when instructions are OS-specific.
GitHub Create Pull Request
Service Fabric Upgrade Linux OS for Azure Service Fabric ...es/service-fabric/service-fabric-cluster-upgrade-os.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page for upgrading Linux OS in Azure Service Fabric is heavily focused on Az PowerShell cmdlets for cluster management tasks, with step-by-step examples provided only in PowerShell. While the scenario is Linux-specific, the management tooling and examples are Windows-centric, and PowerShell is presented as the primary interface for critical operations. Linux-native alternatives (e.g., Azure CLI, Bash scripts) are not mentioned or demonstrated, and PowerShell examples appear before any Linux command-line instructions.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell cmdlets, especially for cluster and node type management.
  • Provide Bash script samples for common tasks, such as updating vmImage, adding/removing node types, and querying cluster state.
  • Explicitly mention that Az PowerShell can be run cross-platform, but highlight native Linux management options.
  • Reorder examples so that Linux-native tools (Azure CLI, Bash) are shown before or alongside PowerShell.
  • Clarify prerequisites for Linux users, such as installing Azure CLI, sfctl, and jq, and provide links to their documentation.
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 →
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 displays a Windows bias by consistently referencing Windows-specific upgrade guides and tools, such as linking to 'service-fabric-cluster-upgrade-windows-server.md' and 'service-fabric-cluster-config-upgrade-windows-server.md' for upgrade instructions. The Patch Orchestration Application is described as 'for Windows,' with no mention of Linux equivalents or guidance. There are no Linux/macOS-specific examples, instructions, or links, and Windows terminology is used exclusively.
Recommendations
  • Include parallel documentation links and instructions for Linux-based Service Fabric clusters, if supported.
  • Explicitly mention whether features like Patch Orchestration Application are available or not for Linux clusters.
  • Provide configuration and upgrade examples for Linux environments, including relevant file paths, commands, and tools.
  • Clarify platform support in each section to help users on non-Windows systems understand applicability.
GitHub Create Pull Request
Service Fabric Upgrading Azure Service Fabric clusters ...icles/service-fabric/service-fabric-cluster-upgrade.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits moderate Windows bias. While most upgrade instructions are platform-neutral, several management actions (certificate management, port opening, etc.) mention PowerShell and Azure CLI, but do not provide explicit Linux/macOS guidance or examples. The OS patching section links only to Windows-specific instructions, with no mention of Linux node patching. The Patch Orchestration Application is described only in the context of Windows. Windows terminology (NTLM, FileStoreService) is referenced without Linux alternatives or caveats.
Recommendations
  • Provide explicit Linux/macOS examples for all CLI operations, including certificate management and port opening.
  • Include links or sections for patching Linux-based Service Fabric clusters, if supported.
  • Clarify whether Patch Orchestration Application and OS image upgrades are available for Linux clusters, and provide instructions if so.
  • When mentioning Windows-specific features (e.g., NTLM, FileStoreService), note Linux equivalents or limitations.
  • Ensure that Azure CLI examples are presented in a cross-platform manner, and avoid PowerShell-only instructions.
GitHub Create Pull Request
Service Fabric Scalability of Service Fabric services .../service-fabric/service-fabric-concepts-scalability.md
Medium 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 page demonstrates a Windows bias by providing PowerShell examples exclusively for service scaling operations, referencing Windows-specific tools and cmdlets (e.g., Update-ServiceFabricService, New-ServiceFabricService), and omitting equivalent Linux CLI or script examples. Windows tooling is mentioned first and most prominently, while Linux alternatives are not presented, creating friction for Linux users.
Recommendations
  • Add equivalent Linux CLI examples (e.g., using Service Fabric CLI (sfctl) or REST API) alongside PowerShell commands.
  • Explicitly mention Linux-compatible tools and workflows for scaling operations.
  • Present examples for both platforms in parallel, or clarify platform-specific differences where relevant.
  • Avoid referencing Windows tools/cmdlets exclusively; provide parity in documentation structure and examples.
GitHub Create Pull Request
Service Fabric Azure Service Fabric application resource model ...ervice-fabric/service-fabric-concept-resource-model.md
Medium 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 demonstrates a notable Windows bias: all command-line deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) with no mention of Azure CLI equivalents, which are cross-platform. The application packaging workflow is described using Visual Studio (Windows-only) and Windows file paths, with no alternatives for Linux/macOS users (e.g., dotnet CLI, Service Fabric SDK for Linux, or cross-platform zip tools). Screenshots and instructions assume Azure Portal usage but do not address Linux/macOS workflows or tools.
Recommendations
  • Add Azure CLI examples for deployment and resource management (e.g., az deployment group create, az resource delete).
  • Include instructions for packaging Service Fabric applications using cross-platform tools (e.g., dotnet CLI, zip command).
  • Provide alternative steps for Linux/macOS users, such as using VS Code or command-line utilities instead of Visual Studio.
  • Present examples for both Windows and Linux/macOS, or use cross-platform commands first.
  • Explicitly state that the workflow is supported on Linux/macOS and link to relevant documentation.
GitHub Create Pull Request
Service Fabric Connect securely to an Azure Service Fabric cluster ...ice-fabric/service-fabric-connect-to-secure-cluster.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. PowerShell is the only scripting example for connecting to clusters, with no Linux shell or bash equivalents for key operations. Certificate installation instructions are detailed for Windows (including PowerShell commands), but for Mac and Linux, only minimal or generic guidance is provided. Windows-specific tools and terminology (e.g., certificate stores, PowerShell cmdlets) are used throughout, and Windows instructions are consistently presented before alternatives. There are no Linux-specific examples for connecting via CLI or managing certificates.
Recommendations
  • Add Linux-specific examples for connecting to clusters, including bash commands and instructions for common Linux distributions.
  • Provide certificate installation steps for Linux (e.g., using openssl, certutil, or browser settings for Firefox/Chrome).
  • Include parity for PowerShell commands with bash or shell equivalents, especially for certificate management.
  • Clearly separate platform-specific instructions and ensure Linux/macOS guidance is as detailed as Windows.
  • Mention cross-platform tools (e.g., sfctl, openssl) first, or in parallel, rather than defaulting to Windows tools.
GitHub Create Pull Request
Service Fabric Azure Files volume driver for Service Fabric ...ic/service-fabric-containers-volume-logging-drivers.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 5 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Minor Windows Paths Manifest Windows Examples
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific details, examples, and tools (PowerShell, Windows paths, Windows Server versioning) are frequently presented first or exclusively, especially in deployment and configuration sections. While Linux equivalents are present in most command-line examples, Windows-centric tools and patterns (PowerShell, Windows paths, Windows Server versioning) are emphasized, and manifest examples use Windows-style paths. The recommended deployment script is PowerShell-only, requiring Linux users to run PowerShell scripts, which may not be native to their environment.
Recommendations
  • Provide Bash or shell script equivalents for the recommended PowerShell deployment, or document how to run the PowerShell script on Linux/macOS (e.g., via pwsh).
  • Ensure manifest examples include both Windows and Linux path conventions (e.g., c:\... and /mnt/...).
  • When listing prerequisites, mention Linux requirements and tools (e.g., Bash, SFCTL) before or alongside Windows ones.
  • Clarify how Linux/macOS users can perform all steps without relying on Windows-only tooling.
  • Add explicit Linux/macOS sample manifests and deployment walkthroughs.
  • Where possible, avoid using Windows-specific terminology or paths as defaults in cross-platform documentation.
GitHub Create Pull Request
Service Fabric Induce Chaos in Service Fabric clusters ...cles/service-fabric/service-fabric-controlled-chaos.md
Medium 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 provides detailed examples for running Chaos in Service Fabric using C# and PowerShell, both of which are Windows-centric. PowerShell is a Windows-native tool, and no equivalent Linux/macOS CLI or shell examples are given. References to Service Fabric PowerShell modules and cmdlets are present, but there is no mention of Linux-compatible tools (e.g., Bash, Azure CLI, or REST usage from curl). This creates friction for Linux/macOS users, who must infer how to perform these tasks without direct guidance.
Recommendations
  • Add Linux/macOS-friendly examples, such as using Bash with curl to invoke the REST API for Chaos operations.
  • Include instructions for using Azure CLI (if supported) to manage Chaos runs.
  • Explicitly mention cross-platform alternatives to PowerShell, or clarify if PowerShell Core is supported on Linux/macOS.
  • Reorder examples so that platform-neutral (REST API) or cross-platform methods are presented first, followed by platform-specific ones.
  • Document any prerequisites or limitations for Linux/macOS users, such as Service Fabric SDK support or required tools.
GitHub Create Pull Request
Service Fabric Create a cluster using certificate common name ...-fabric/service-fabric-create-cluster-using-cert-cn.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exclusively provides PowerShell examples for certificate upload and cluster deployment, with file paths and commands tailored to Windows environments. There are no CLI, Bash, or Linux/macOS-specific instructions, nor any mention of cross-platform alternatives. This creates friction for Linux/macOS users who may not have access to PowerShell or Windows-style file paths.
Recommendations
  • Add equivalent Azure CLI (az) commands for certificate upload and cluster deployment, which are cross-platform.
  • Include Bash examples for Linux/macOS users, especially for file paths and scripting.
  • Explicitly mention that the process can be completed on Linux/macOS and provide guidance or links to relevant documentation.
  • Avoid using Windows-specific file paths (e.g., C:\users\sfuser\...) in generic instructions; use environment-neutral paths or provide alternatives.
  • Clarify tool requirements and suggest installation steps for non-Windows platforms if PowerShell is required.
GitHub Create Pull Request
Service Fabric Azure Service Fabric deployment with FabricClient ...service-fabric-deploy-remove-applications-fabricclient.md
Medium 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 exhibits a notable Windows bias. It references Visual Studio and PowerShell as primary tools for packaging and deploying Service Fabric applications, with file paths and workflows that are Windows-centric. All example paths use Windows conventions (e.g., C:\Users\...), and troubleshooting steps rely on PowerShell cmdlets and Windows SDK modules. There are no Linux/macOS equivalents or examples, nor is there guidance for performing these tasks on non-Windows platforms.
Recommendations
  • Add explicit instructions and examples for Linux/macOS users, including file path conventions and alternative tools.
  • Provide CLI-based workflows (e.g., using Service Fabric CLI 'sfctl') alongside PowerShell examples, and reference them equally.
  • Clarify which steps are platform-agnostic and which require Windows-specific tools, offering alternatives where possible.
  • Include troubleshooting steps for Linux environments, such as using Bash scripts or sfctl commands.
  • Document how to package and upload applications from Linux/macOS, including any required SDKs or dependencies.
GitHub Create Pull Request
← Previous Page 24 of 29 Next →