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 176-200 of 718 flagged pages
Service Fabric Upgrade an Azure Service Fabric standalone cluster ...ce-fabric/service-fabric-cluster-upgrade-standalone.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 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 and configuration instructions. The Patch Orchestration Application is described only for Windows, with no mention of Linux equivalents or guidance. There are no Linux-specific examples, instructions, or tool references, and Windows is implicitly treated as the default platform.
Recommendations
  • Add equivalent Linux-specific upgrade and configuration guides, and link to them alongside or before Windows guides.
  • Include examples and instructions for Linux environments (e.g., using bash, Linux-native tools, or configuration files).
  • Mention and document Linux-compatible patch orchestration solutions, or clarify the status of POA on Linux clusters.
  • Ensure that references to platform-specific documentation are balanced and clearly labeled for both Windows and Linux users.
GitHub Create Pull Request
Service Fabric Upgrading Azure Service Fabric clusters ...icles/service-fabric/service-fabric-cluster-upgrade.md
High Priority View Details →
Scanned: 2026-01-09 19:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits Windows bias by referencing Windows-specific tools and workflows (such as Patch Orchestration Application and NTLM settings) without mentioning Linux equivalents or providing Linux-specific guidance. Examples for cluster management (certificates, ports) mention PowerShell/Azure CLI, but do not clarify Linux compatibility or provide Linux shell examples. The OS patching section links only to Windows patching documentation, omitting Linux node upgrade guidance.
Recommendations
  • Add explicit Linux examples and workflows for cluster management tasks (e.g., certificate management, port changes) using Bash/Azure CLI on Linux.
  • Include references and links to documentation for patching/upgrading Linux-based Service Fabric cluster nodes.
  • Clarify tool compatibility (e.g., Azure CLI usage on Linux vs. PowerShell on Windows) and provide parity in example commands.
  • Mention Linux-specific considerations (such as authentication, file system differences, or service management) where relevant.
  • Ensure that all references to OS-level operations (patching, NTLM settings) include both Windows and Linux contexts, or clearly state if a feature is Windows-only.
GitHub Create Pull Request
Service Fabric Scalability of Service Fabric services .../service-fabric/service-fabric-concepts-scalability.md
High Priority View Details →
Scanned: 2026-01-09 19: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 and references to Windows-specific tools (e.g., Service Fabric PowerShell cmdlets) without equivalent Linux CLI or scripting examples. Windows tools and patterns are mentioned first and exclusively, with no mention of Linux-native management approaches (such as sfctl or bash scripts). The lack of Linux parity in examples and tooling guidance may hinder Linux users from fully utilizing Service Fabric's scalability features.
Recommendations
  • Add equivalent Linux examples using sfctl, bash, or other Linux-native tools alongside PowerShell examples.
  • Explicitly mention Linux management workflows and tools where Windows tools (e.g., PowerShell cmdlets) are referenced.
  • Ensure that code samples and administrative actions are presented for both platforms, ideally side-by-side.
  • Include a section or callout highlighting platform-specific differences in scaling operations and tooling.
  • Review references to Windows tools and ensure Linux alternatives are provided or linked.
GitHub Create Pull Request
Service Fabric Overview of Service Fabric and containers ...s/service-fabric/service-fabric-containers-overview.md
High Priority View Details →
Scanned: 2026-01-09 19: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. Windows container scenarios and tools (IIS, ASP.NET MVC, Mirantis Container Runtime, Windows Server containers) are mentioned in detail, often before or with more emphasis than Linux equivalents. The 'IIS lift and shift' scenario is Windows-specific, and references to Windows container tutorials and resources appear alongside or before Linux ones. Linux container examples are present but less detailed, and some scenarios lack Linux-specific guidance.
Recommendations
  • Add equivalent Linux-focused scenarios, such as Apache/Nginx lift-and-shift, to balance the IIS example.
  • Ensure Linux container tutorials and references are presented with equal prominence and detail as Windows ones.
  • Include Linux-specific tools and patterns (e.g., systemd, SELinux, AppArmor) where relevant.
  • Expand on Linux container runtime options and their configuration, not just Docker.
  • Review ordering so that Linux and Windows examples are interleaved or Linux is presented first in some cases.
  • Clarify any feature parity gaps between Linux and Windows containers in Service Fabric.
GitHub Create Pull Request
Service Fabric Induce Chaos in Service Fabric clusters ...cles/service-fabric/service-fabric-controlled-chaos.md
High Priority View Details →
Scanned: 2026-01-09 19: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 clear Windows bias. All code examples provided are in C# and PowerShell, both of which are traditionally Windows-centric. PowerShell is featured heavily, with no mention of Linux shell equivalents or cross-platform command-line usage. References to Service Fabric PowerShell modules and commands are made without any Linux CLI or Bash alternatives. There are no instructions or examples for running Chaos from Linux environments, nor is there guidance for using Service Fabric on Linux clusters. The documentation implicitly assumes a Windows development and operational environment.
Recommendations
  • Add Linux/Bash shell examples for running Chaos and retrieving reports, using Service Fabric CLI (sfctl) or REST API calls with curl.
  • Explicitly mention cross-platform tools (e.g., sfctl) and provide usage instructions for Linux and macOS environments.
  • Reorder examples so that REST API or CLI usage is presented before or alongside PowerShell, to avoid Windows-first bias.
  • Include notes on differences or requirements for running Service Fabric and Chaos on Linux clusters.
  • Reference official documentation for Linux usage and provide links to relevant resources.
GitHub Create Pull Request
Service Fabric Event Aggregation with Microsoft Azure Diagnostics ...ic/service-fabric-diagnostics-event-aggregation-wad.md
High Priority View Details →
Scanned: 2026-01-09 19: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 Windows bias in several ways. Windows and PowerShell tools and patterns are mentioned and used exclusively or before Linux equivalents. Examples and instructions are centered around Windows tooling (WAD, PowerShell, Visual Studio), with little to no mention of Linux-specific diagnostics (LAD) or command-line examples. The page references Windows-centric logging mechanisms (ETW), and links to Windows-focused templates and guides. Linux alternatives are only referenced in a selector at the top, with no parity in examples or walkthroughs within the main content.
Recommendations
  • Include Linux-specific examples and instructions alongside Windows ones, especially for diagnostics extension deployment, configuration, and log collection.
  • Provide equivalent Linux command-line examples (e.g., Azure CLI, bash scripts) instead of only PowerShell.
  • Reference Linux diagnostics tools (LAD) and logging mechanisms (such as syslog, journald) where ETW and Windows EventSource are discussed.
  • Ensure links to Linux documentation are as prominent and detailed as Windows ones, and avoid referencing only Windows templates or guides.
  • Add troubleshooting and configuration guidance for Linux clusters, including performance counter collection and Application Insights integration.
  • Where Visual Studio is mentioned, provide alternatives for Linux development environments (e.g., VS Code, command-line tools).
GitHub Create Pull Request
Service Fabric Create a cluster using certificate common name ...-fabric/service-fabric-create-cluster-using-cert-cn.md
High Priority View Details →
Scanned: 2026-01-09 19: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 exhibits a strong Windows bias. All command-line examples use PowerShell, with Windows-style file paths and commands. There are no equivalent instructions or examples for Linux users (e.g., Bash, Azure CLI, or Linux file paths). The template referenced is specifically for Windows nodes, and Windows-centric tools and patterns are used throughout, with no mention of Linux alternatives or cross-platform approaches.
Recommendations
  • Provide equivalent Linux/Bash examples for certificate management, key vault operations, and template deployment using Azure CLI.
  • Reference or include templates for Linux-based Service Fabric clusters, not just Windows node templates.
  • Use cross-platform file paths and avoid hardcoding Windows-specific paths (e.g., C:\users\sfuser\...).
  • Mention and demonstrate use of Azure CLI, which is cross-platform, alongside PowerShell.
  • Clarify which steps are OS-agnostic and which are specific to Windows, and provide guidance for Linux users where necessary.
  • Add notes or sections explicitly addressing Linux deployment scenarios and tools.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Events ...es/service-fabric/service-fabric-diagnostics-events.md
High Priority View Details →
Scanned: 2026-01-09 19:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates Windows bias by primarily referencing Windows-centric event logging mechanisms (ETW/Windows Event logs), mentioning the Windows Azure diagnostics agent, and omitting explicit instructions or examples for accessing Service Fabric events on Linux clusters. No Linux-specific tools, logging channels, or parity examples are provided.
Recommendations
  • Include examples and instructions for accessing Service Fabric events on Linux clusters, such as using syslog, journald, or other Linux-native logging mechanisms.
  • Mention Linux-compatible diagnostics agents or alternatives to the Windows Azure diagnostics agent.
  • Provide parity in documentation by listing both Windows and Linux event access methods, and ensure examples are given for both platforms.
  • Clarify whether the described event logging and monitoring approaches apply to Linux clusters, and if not, provide Linux-specific guidance.
GitHub Create Pull Request
Service Fabric Report and check health with Azure Service Fabric ...ric-diagnostics-how-to-report-and-check-service-health.md
High Priority View Details →
Scanned: 2026-01-09 19: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 strong Windows bias. All examples and instructions assume a Windows development environment, specifically referencing Visual Studio, PowerShell, and Windows-specific tools like Local Cluster Manager. There are no Linux equivalents or cross-platform alternatives provided for cluster creation, application deployment, or health checking. The use of PowerShell is pervasive, and Linux command-line or scripting options are not mentioned.
Recommendations
  • Add instructions and examples for Linux environments, including how to create a secure dev cluster using Bash or Azure CLI.
  • Provide deployment and health check steps using cross-platform tools (e.g., Azure CLI, REST API, or Service Fabric CLI) instead of or alongside PowerShell.
  • Include guidance for using VS Code or other cross-platform IDEs, not just Visual Studio.
  • Mention Linux-compatible Service Fabric Explorer access methods and clarify how to manage clusters on Linux.
  • Ensure all code and tool references are platform-neutral or provide parallel instructions for both Windows and Linux.
GitHub Create Pull Request
Service Fabric Enable disk encryption for Linux clusters ...c/service-fabric-enable-azure-disk-encryption-linux.md
High Priority View Details →
Scanned: 2026-01-09 19:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation, while focused on enabling disk encryption for Linux clusters, exhibits several signs of Windows bias. PowerShell commands are presented first and in greater detail throughout, with Azure CLI equivalents often appearing as secondary or afterthoughts. Paths and examples use Windows-style file paths (e.g., c:\certificates), and certificate management steps are described using PowerShell cmdlets without Linux-native alternatives (such as OpenSSL or Linux file system paths). There is an absence of Linux shell scripting examples, and the documentation assumes familiarity with Windows tooling and conventions.
Recommendations
  • Present Azure CLI and Linux-native commands before or alongside PowerShell examples, especially in Linux-focused documentation.
  • Replace Windows file paths (e.g., c:\certificates) with Linux equivalents (e.g., /home/user/certificates) in examples and variable declarations.
  • Include Linux-native certificate management instructions (e.g., using OpenSSL) for creating and managing certificates.
  • Provide bash shell scripting examples for automation steps, not just PowerShell.
  • Clarify any differences in workflow or tooling between Windows and Linux environments, and ensure Linux users are not required to use Windows-specific tools.
  • Review and update prerequisite steps to include Linux-native methods for tasks such as secure string handling and file management.
GitHub Create Pull Request
Service Fabric Azure Service Fabric disaster recovery ...les/service-fabric/service-fabric-disaster-recovery.md
High Priority View Details →
Scanned: 2026-01-09 19:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example Powershell Heavy
Summary
The documentation page demonstrates a Windows bias in several ways: it references Windows-specific tools and APIs (such as PowerShell cmdlets like Repair-ServiceFabricPartition), links to Windows Server setup guides before Linux equivalents, and omits explicit Linux or cross-platform command examples. The troubleshooting and recovery instructions focus on Windows-centric patterns and do not provide parity for Linux environments, nor do they mention Linux-specific Service Fabric management tools or commands.
Recommendations
  • Include Linux-specific examples and instructions for disaster recovery operations, such as using Service Fabric CLI (sfctl) or REST APIs.
  • Reference both Windows and Linux setup guides equally, or provide a cross-platform section for standalone cluster creation.
  • When mentioning PowerShell cmdlets, also provide equivalent sfctl or REST API commands for Linux users.
  • Explicitly state which procedures or tools are platform-specific, and offer alternatives for Linux environments.
  • Add troubleshooting steps and examples relevant to Linux clusters, such as collecting logs or managing processes.
  • Ensure links to documentation for both Windows and Linux Service Fabric management are present and balanced.
GitHub Create Pull Request
Service Fabric Performance monitoring with Azure Diagnostics .../service-fabric/service-fabric-diagnostics-perf-wad.md
High Priority View Details →
Scanned: 2026-01-09 19: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 demonstrates a strong Windows bias. It focuses almost exclusively on the Windows Azure Diagnostics (WAD) extension, with detailed configuration and deployment steps for Windows clusters. Linux clusters are mentioned only briefly, with a link to a separate page for setup, and no Linux-specific configuration or example is provided. All code samples and deployment instructions use Windows-centric tools and patterns (ARM templates, PowerShell), and references to performance counters use Windows-specific syntax. There is no parity in example depth or guidance for Linux users.
Recommendations
  • Include equivalent Linux configuration steps and examples for performance counter collection using the Log Analytics agent.
  • Provide sample configuration files or scripts for Linux clusters, such as agent configuration or relevant shell commands.
  • Add deployment instructions for Linux clusters, using CLI tools (e.g., Azure CLI, Bash) rather than only PowerShell.
  • Present both Windows and Linux options side-by-side, or clearly separate them with equal detail and prominence.
  • Reference Linux-specific performance counters and monitoring patterns where applicable.
GitHub Create Pull Request
Service Fabric Reliable Collection object serialization ...c-reliable-services-reliable-collections-serialization.md
High Priority View Details →
Scanned: 2026-01-09 19: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 Windows bias primarily through its 'Next steps' section, which lists Windows-centric tools (Visual Studio, PowerShell) for application upgrades and omits Linux equivalents or cross-platform alternatives. There are no examples or instructions for Linux users, and Windows tools are mentioned before any other options. The serialization examples are platform-neutral, but the guidance for upgrades is Windows-focused.
Recommendations
  • Add equivalent instructions and tutorials for upgrading applications using Linux tools (e.g., Azure CLI, Bash scripts) and reference them alongside Windows tools.
  • Include explicit examples or links for Linux environments in the 'Next steps' section, such as 'Upgrading your Application Using Azure CLI' or 'Upgrading your Application Using Bash'.
  • Ensure that cross-platform upgrade paths are documented and presented with parity to Windows options, rather than listing Windows tools first.
  • Clarify which features and APIs are available and supported on Linux clusters, and provide guidance for Linux users where relevant.
GitHub Create Pull Request
Service Fabric Secure service remoting communications with C# ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-reliable-services-secure-communication.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 demonstrates a Windows bias by focusing exclusively on C# examples that use Windows-centric certificate stores (e.g., StoreLocation.LocalMachine, StoreName="My") and thumbprint-based certificate selection. While there is a brief note about Linux certificate storage (PEM files in /var/lib/sfcerts), all code samples and configuration snippets assume Windows conventions and APIs. No Linux-specific code samples, configuration details, or troubleshooting guidance are provided for securing service remoting communications in C# on Linux Service Fabric clusters.
Recommendations
  • Provide parallel C# code samples and configuration instructions for Linux clusters, including how to reference PEM-formatted certificates and any differences in API usage or configuration.
  • Explicitly document the differences in certificate handling between Windows and Linux, such as store location, format, and access patterns.
  • Include troubleshooting tips or common issues for Linux deployments, such as permissions or file format errors.
  • Ensure that Linux-specific instructions are given equal prominence and detail as Windows instructions, rather than relegating them to a brief note.
  • Consider adding a selector or section for 'C# on Linux' to match the parity of 'C# on Windows' and 'Java on Linux'.
GitHub Create Pull Request
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-09 19:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a strong Windows bias. All step-by-step examples use Windows Server SKUs and PowerShell commands, with no equivalent Bash, CLI, or Linux-native instructions. Windows terminology and tooling (e.g., file paths like C:\, certificate store locations, Windows-specific Service Fabric commands) are used throughout. Linux is only briefly mentioned in a single section about changing the OS SKU, but no full Linux workflow or examples are provided.
Recommendations
  • Provide parallel Linux examples for all steps, including cluster deployment, certificate management, and node operations, using Bash, Azure CLI, and Linux file paths.
  • Include instructions for using Linux-based Service Fabric clusters, such as Ubuntu, with relevant ARM template parameters and deployment details.
  • Replace or supplement PowerShell commands with Azure CLI equivalents, and show how to run them on Linux/macOS.
  • Document Linux-specific certificate handling (e.g., using OpenSSL, PEM files, Key Vault integration from Linux).
  • Ensure all references to file paths, certificate stores, and tooling are cross-platform, or clearly indicate OS-specific differences.
  • Add troubleshooting and validation steps for Linux clusters, including connecting to the cluster and checking health status from Linux environments.
GitHub Create Pull Request
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-09 19: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 strong Windows bias. All code and script examples use Windows-specific tools and patterns, such as batch files (.bat), PowerShell commands, and Windows environment variable management. The instructions reference Visual Studio and Windows file paths, and debugging steps are tailored to Windows clusters. Linux is mentioned only briefly, with no concrete Linux shell script or example provided. The page assumes a Windows development environment and does not offer parity for Linux users.
Recommendations
  • Provide equivalent Linux examples using shell scripts (e.g., MySetup.sh) and bash commands for environment variable management.
  • Show how to configure and deploy setup entry points for Linux clusters, including file paths and permissions.
  • Include instructions for adding and packaging shell scripts in non-Windows development environments.
  • Demonstrate debugging and log access for Linux clusters, referencing typical Linux file system paths.
  • Balance PowerShell and batch file examples with bash and shell script alternatives, and clarify platform-specific differences throughout the documentation.
GitHub Create Pull Request
Service Fabric Custom Image .../articles/service-fabric/how-to-deploy-custom-image.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page primarily references Windows custom images and provides a PowerShell example for role assignment, with Windows terminology and patterns appearing before Linux equivalents. While there are links to Linux custom image creation and Azure CLI usage, the main narrative and examples are Windows-centric, and the PowerShell command is given without a Linux/CLI equivalent.
Recommendations
  • Clarify in the introduction that both Windows and Linux custom images are supported, if applicable.
  • Provide equivalent Azure CLI examples for role assignment alongside the PowerShell example.
  • Include explicit ARM template examples for Linux node types, or clarify if the process is identical.
  • Balance references to Windows and Linux throughout the documentation, ensuring Linux terminology and links are not secondary.
  • Add a section or note about any Linux-specific considerations or limitations, if relevant.
GitHub Create Pull Request
Service Fabric Service Fabric Explorer blocking operations ...ged-cluster-service-fabric-explorer-blocking-operation.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page frequently references PowerShell cmdlets (Az PowerShell, AzSF PowerShell) for managing Service Fabric resources, with no explicit mention of Linux/macOS equivalents or Azure CLI alternatives in some sections. PowerShell examples are presented first and predominantly, which may create friction for Linux/macOS users who typically use Azure CLI or bash scripting.
Recommendations
  • Add Azure CLI examples alongside PowerShell cmdlets for all management operations, especially for application type version unprovisioning and service creation.
  • Clarify which commands are cross-platform and which are Windows-only, and provide guidance for Linux/macOS users where appropriate.
  • Where possible, link to ARM template documentation and examples that are platform-agnostic.
  • Explicitly mention that Azure CLI can be used on Linux/macOS for resource management tasks.
GitHub Create Pull Request
Service Fabric Understanding periodic backup configuration ...-fabric-backuprestoreservice-configure-periodic-backup.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page is generally platform-neutral, focusing on Azure Service Fabric backup configuration. However, in the 'File share' backup storage section, only Windows-style file share paths (\\StorageServer\BackupStore) and Windows authentication methods are described. Integrated Windows Authentication is mentioned exclusively, and no Linux or SMB/CIFS mounting instructions are provided. This suggests a Windows-first bias in the file share backup example, potentially creating friction for Linux/macOS users who may wish to use SMB/CIFS file shares.
Recommendations
  • Add examples and guidance for configuring file share backup storage using SMB/CIFS on Linux/macOS, including mount instructions and authentication options.
  • Clarify whether Linux-based Service Fabric clusters can use file share backup storage, and if so, provide platform-specific instructions.
  • Mention alternative storage options (such as NFS or Azure Files) if supported, and provide parity in examples for both Windows and Linux environments.
GitHub Create Pull Request
Service Fabric Architecture of Azure Service Fabric ...articles/service-fabric/service-fabric-architecture.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page describes the architecture of Azure Service Fabric in a platform-neutral manner for most subsystems. However, in the Management subsystem section, it explicitly mentions 'PowerShell cmdlets' as a primary means of lifecycle management, without referencing Linux/macOS equivalents (such as Azure CLI or REST APIs). This creates a Windows-first impression and suggests a bias toward Windows tooling for administration.
Recommendations
  • Mention cross-platform management tools such as Azure CLI and REST APIs alongside PowerShell cmdlets.
  • Clarify which management operations can be performed using Azure CLI or other platform-neutral tools.
  • Add examples or references for Linux/macOS users to manage Service Fabric clusters.
  • Consider rephrasing to avoid implying PowerShell is the only or primary management interface.
GitHub Create Pull Request
Service Fabric Azure Service Fabric security best practices ...rvice-fabric/service-fabric-best-practices-security.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Windows and Linux examples for key security tasks, such as certificate generation and secret encryption, but often presents Windows/PowerShell instructions first and in greater detail. Windows-specific tools and features (e.g., Windows Defender, PowerShell commands) are discussed prominently, sometimes without Linux equivalents or with less detail for Linux. Some sections (e.g., Windows security baselines, Windows Defender) are Windows-only, but these are appropriately marked as such.
Recommendations
  • Present Linux and Windows instructions in parallel, or alternate which comes first to avoid implicit prioritization.
  • Expand Linux-specific guidance where Windows-specific tools are discussed (e.g., mention Linux antimalware options or clarify if none are required).
  • Where PowerShell commands are given, ensure equivalent Bash/CLI commands are provided and described with equal detail.
  • Clearly label Windows-only sections and provide links or notes for Linux alternatives where applicable.
  • Review the order of examples and ensure Linux is not consistently secondary.
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-02-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page on securing an Azure Service Fabric cluster presents security scenarios and technologies applicable to both Azure-hosted clusters and standalone Windows clusters. However, it consistently references standalone clusters as 'Windows Server clusters' and provides links and examples only for Windows-specific standalone cluster security (certificate and Windows security). There is no mention of standalone Linux cluster security, nor are Linux-specific instructions, examples, or links provided. Windows terminology and tools (e.g., Windows certificate service, MakeCert.exe) are referenced without Linux equivalents or alternatives.
Recommendations
  • Add explicit guidance for securing standalone Linux Service Fabric clusters, including certificate setup and any Linux-specific authentication mechanisms.
  • Provide links to Linux-focused documentation or instructions for certificate management and cluster configuration on Linux.
  • When referencing certificate creation tools, mention Linux-compatible alternatives (e.g., OpenSSL) alongside Windows tools.
  • Clarify which security scenarios and recommendations apply equally to Linux clusters, and which are Windows-specific.
  • Ensure parity in example commands, templates, and walkthroughs for both Windows and Linux environments.
GitHub Create Pull Request
Service Fabric Azure Service Fabric container application manifest examples ...abric/service-fabric-manifest-example-container-app.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation is notably Windows-focused: all manifest examples are based on the 'Windows Server 2016 Container Sample', and several instructions reference Windows-specific tools and concepts (e.g., 'winver' for OS build, Windows path formats, and PFX certificates). There is no mention of Linux equivalents, nor are there Linux-specific manifest examples or guidance for Linux containers. This creates friction for Linux users deploying Service Fabric containers.
Recommendations
  • Add parallel manifest examples based on Linux container samples, or clarify which elements differ for Linux clusters.
  • Where Windows-specific tools are referenced (e.g., 'winver'), provide Linux equivalents (e.g., 'cat /etc/os-release' or 'uname -r').
  • When discussing certificate handling, explicitly describe the Linux PEM scenario and how to access/use these files.
  • Use platform-neutral path formats in examples, or provide both Windows and Linux path variants.
  • Explicitly state at the top if the examples are only valid for Windows clusters, and link to Linux-specific documentation if available.
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-02-10 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 Windows bias by primarily referencing Windows-specific upgrade guides and tools, such as linking to Windows Server-specific instructions and the Patch Orchestration Application for Windows. There are no explicit Linux examples or references to Linux-based Service Fabric clusters, and all upgrade/configuration links point to Windows-focused documentation.
Recommendations
  • Clarify early in the article whether standalone Service Fabric clusters are supported on Linux, and if so, provide equivalent Linux upgrade/configuration instructions or links.
  • If Linux standalone clusters are supported, add Linux-specific examples and references alongside or before Windows ones.
  • If only Windows is supported for standalone clusters, explicitly state this at the top to avoid confusion for Linux/macOS users.
  • Where possible, generalize instructions or provide cross-platform guidance (e.g., editing ClusterConfig.json, using REST APIs) rather than referencing only Windows tools.
GitHub Create Pull Request
Service Fabric Health monitoring in Service Fabric ...s/service-fabric/service-fabric-health-introduction.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides only PowerShell examples for reporting and querying Service Fabric health, with no equivalent examples for Linux/macOS users (e.g., using Azure CLI, REST API, or Service Fabric CLI). The only concrete example uses PowerShell cmdlets, and there is no mention of cross-platform tools or commands. This creates friction for Linux/macOS users who cannot use PowerShell natively.
Recommendations
  • Add equivalent examples using the Service Fabric CLI (sfctl), which is cross-platform and supported on Linux/macOS.
  • Include REST API examples for reporting and querying health, as these are platform-agnostic.
  • Mention and link to documentation for cross-platform tools (sfctl, REST API) alongside PowerShell, not just in passing.
  • Clearly indicate which tools are Windows-only and provide alternatives for other platforms.
  • Consider providing code snippets in Bash or with curl for REST API usage.
GitHub Create Pull Request
← Previous Page 8 of 29 Next →