Service Fabric

407
Total Pages
335
Linux-Friendly Pages
72
Pages with Bias
17.7%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

2475 issues found
Showing 2026-2050 of 2475 flagged pages
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-02-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides PowerShell examples for creating and updating Service Fabric services with move cost, but does not offer equivalent examples for Linux environments (such as Azure CLI, Bash, or REST API). PowerShell is primarily a Windows tool, and its exclusive use in examples creates friction for Linux/macOS users. There is no mention of Linux-native tools or cross-platform command-line alternatives, and PowerShell is presented before C# code samples.
Recommendations
  • Add Azure CLI or REST API examples for creating and updating Service Fabric services with move cost, as these are cross-platform and commonly used on Linux/macOS.
  • Explicitly mention whether PowerShell examples are applicable on Linux (e.g., via PowerShell Core), or provide Bash equivalents if possible.
  • Clarify any platform-specific requirements for Service Fabric management commands, and link to cross-platform tooling documentation.
  • Consider presenting cross-platform examples (CLI, REST) before or alongside PowerShell to improve parity.
GitHub Create Pull Request
Service Fabric Service sensitivity ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-sensitivity.md
Medium Priority View Details →
Scanned: 2026-02-02 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 configuration examples using Application Manifest (XML/JSON), PowerShell, and C# API. PowerShell is featured as the primary CLI example, with no mention of Linux/macOS CLI alternatives (e.g., Azure CLI, REST API, or cross-platform Service Fabric CLI). This creates friction for Linux/macOS users who cannot use PowerShell natively. The C# API is also Windows-centric due to Service Fabric SDK support patterns.
Recommendations
  • Add examples using Azure CLI or Service Fabric CLI (sfctl), which are cross-platform and supported on Linux/macOS.
  • Mention REST API options for programmatic configuration where possible.
  • Clarify if PowerShell examples require Windows or if cross-platform PowerShell Core is supported.
  • Explicitly state platform requirements for each method (e.g., 'PowerShell examples require Windows or PowerShell Core').
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-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page for upgrading an Azure Service Fabric standalone cluster shows notable Windows bias. References and links are primarily or exclusively to Windows Server-specific guides (e.g., 'service-fabric-cluster-upgrade-windows-server.md', 'service-fabric-cluster-config-upgrade-windows-server.md'). The Patch Orchestration Application is described only for Windows. There are no Linux-specific instructions, examples, or links, despite Service Fabric standalone clusters supporting both Windows and Linux. This creates friction for Linux users seeking upgrade guidance.
Recommendations
  • Add explicit instructions and links for upgrading Service Fabric standalone clusters running on Linux.
  • Provide Linux-specific examples for configuration changes and cluster upgrades.
  • Clarify which steps or tools are Windows-only and offer Linux alternatives where available.
  • Include references to Linux patch orchestration or manual patching guidance if POA is not available for Linux.
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-02-02 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides examples and instructions using PowerShell and Azure CLI for cluster management tasks, such as managing certificates and opening application ports. While Azure CLI is cross-platform, PowerShell is traditionally Windows-centric, and the documentation mentions PowerShell before Azure CLI in multiple places. Additionally, the section on OS image upgrades references patching Windows operating systems specifically, with no mention of Linux node patching or parity.
Recommendations
  • Provide explicit Linux/macOS examples where PowerShell is mentioned, such as using Bash or Azure CLI commands on Linux.
  • Clarify when Azure CLI instructions are cross-platform and provide sample commands for Linux/macOS terminals.
  • If Service Fabric supports Linux clusters, include guidance or links for patching/upgrading Linux node OS images.
  • Where possible, avoid listing PowerShell before Azure CLI, or present both options equally.
  • Add notes or links for Linux-specific documentation if available, especially in sections referencing OS patching.
GitHub Create Pull Request
Service Fabric Scalability of Service Fabric services .../service-fabric/service-fabric-concepts-scalability.md
Medium Priority View Details →
Scanned: 2026-02-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides code examples for scaling Service Fabric services using C# and PowerShell, but omits equivalent Linux CLI or Bash examples. PowerShell is a Windows-centric tool, and its exclusive use in administrative examples creates friction for Linux users. The documentation also references Windows-specific behaviors (e.g., kernel driver logging) before Linux equivalents, but does acknowledge platform differences.
Recommendations
  • Add equivalent Linux CLI (sfctl) or Bash examples alongside PowerShell commands for service creation and updates.
  • Explicitly mention Linux administrative workflows and tools where PowerShell is referenced.
  • Where platform-specific differences exist, provide clear guidance or links to Linux documentation.
  • Consider reordering examples so that platform-neutral or Linux examples are presented alongside or before Windows-specific ones.
GitHub Create Pull Request
Service Fabric Learn more about Azure Service Fabric ...icles/service-fabric/service-fabric-content-roadmap.md
Medium Priority View Details →
Scanned: 2026-02-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides a broad overview of Azure Service Fabric, covering both Windows and Linux support. However, there are several instances of Windows bias: Windows-specific tools and processes (e.g., PowerShell, Visual Studio, Windows services) are mentioned first or exclusively in some sections, and examples or instructions for Linux users are often missing or less prominent. The documentation references Windows services and executables (FabricHost.exe, Fabric.exe, FabricGateway.exe) without clarifying Linux equivalents or processes. Standalone cluster creation is described only for Windows, with Linux standalone clusters explicitly noted as unsupported. In lifecycle management and health monitoring, PowerShell and Windows-centric tools are listed before CLI or cross-platform options.
Recommendations
  • Where possible, provide Linux-specific instructions, examples, and tool references alongside Windows ones.
  • Clarify Linux equivalents for Windows services and executables, or note differences in architecture/processes.
  • Ensure CLI and cross-platform tools are presented equally or before Windows-only tools like PowerShell.
  • Add explicit guidance or links for Linux cluster creation and management, even if only to clarify current limitations.
  • Highlight differences and parity between Windows and Linux throughout, referencing the differences documentation as needed.
GitHub Create Pull Request
Service Fabric Overview of Azure Service Fabric ...ain/articles/service-fabric/service-fabric-overview.md
Medium Priority View Details →
Scanned: 2026-02-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation mentions both Windows and Linux support for Azure Service Fabric, but Windows development tools (Visual Studio, PowerShell) are described first and in more detail, while Linux equivalents (Eclipse, Yeoman) are mentioned briefly. There are no concrete Linux-specific examples or walkthroughs, and the primary quickstart link points to a .NET/Windows-centric guide. This creates friction for Linux/macOS users seeking parity in development experience.
Recommendations
  • Provide parallel Linux/macOS examples and walkthroughs, especially in quickstart and getting started sections.
  • Include links to Linux/macOS-specific quickstart guides and documentation (e.g., service-fabric-quickstart-java.md or service-fabric-get-started-linux.md).
  • Describe Linux development tools and workflows (Eclipse, Yeoman, CLI) with equal detail as Windows tools (Visual Studio, PowerShell).
  • Ensure that example commands and screenshots are shown for both platforms where relevant.
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-02 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation discusses security for Azure Service Fabric clusters and standalone clusters, but consistently references Windows Server clusters for standalone scenarios. Links and examples for standalone clusters are exclusively for Windows, with no mention of Linux equivalents or guidance for securing standalone Linux clusters. Windows-specific tools (e.g., MakeCert.exe, Windows Server certificate service) are mentioned, and Windows authentication is described, but there is no coverage of Linux authentication or certificate management tools. The concept of Linux clusters is acknowledged, but practical instructions are missing.
Recommendations
  • Add explicit guidance and links for securing standalone Service Fabric clusters on Linux, including certificate management and authentication options.
  • Provide Linux-specific examples for certificate creation and installation (e.g., using OpenSSL or Linux certificate authorities).
  • Mention Linux authentication mechanisms or clarify if only certificate-based security is supported for Linux clusters.
  • Ensure parity in step-by-step instructions and references for both Windows and Linux standalone clusters.
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-02-02 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 for the Azure Service Fabric application resource model demonstrates a notable Windows bias. All command-line deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) without mention of Azure CLI equivalents. The application packaging workflow is described using Visual Studio, a Windows-centric tool, and screenshots reinforce this. No Linux/macOS alternatives or instructions are provided for key steps such as packaging, uploading, or deploying applications.
Recommendations
  • Add Azure CLI examples for deployment and resource management alongside PowerShell examples.
  • Include instructions for packaging Service Fabric applications using cross-platform tools (e.g., dotnet CLI, SF SDK on Linux/macOS).
  • Provide guidance for uploading application packages to Azure Storage using Azure CLI or azcopy, which are available on Linux/macOS.
  • Clarify which steps are platform-agnostic and which require Windows, and offer alternatives where possible.
  • Reorder examples so that cross-platform options are presented first or in parallel with Windows-specific instructions.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Docker Compose Deployment Preview ...ticles/service-fabric/service-fabric-docker-compose.md
Medium Priority View Details →
Scanned: 2026-02-02 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both PowerShell and Service Fabric CLI (sfctl) examples for deploying Docker Compose files to Azure Service Fabric. PowerShell examples are presented first and in greater detail, which may suggest a Windows-first approach. However, the CLI commands (sfctl) are cross-platform and allow Linux/macOS users to perform the same tasks. No Linux-specific tools or shell examples are given, and PowerShell is a Windows-centric tool, though it is available on other platforms.
Recommendations
  • Clarify that sfctl is cross-platform and suitable for Linux/macOS users.
  • Consider presenting sfctl examples before PowerShell, or side-by-side, to emphasize Linux/macOS parity.
  • Explicitly mention that PowerShell commands are primarily for Windows users, while sfctl is recommended for Linux/macOS.
  • Provide example shell commands (bash/zsh) for common Linux workflows, if relevant.
  • Add a note about PowerShell Core availability on Linux/macOS, if PowerShell usage is intended to be cross-platform.
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-02 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-based examples for reporting and evaluating Service Fabric health, with no equivalent Linux/macOS CLI or REST API examples. The example section uses Windows PowerShell cmdlets exclusively, and there is no mention of Service Fabric CLI (sfctl) or REST API usage, which are the primary tools for Linux/macOS users. This creates friction for non-Windows users attempting to follow the documentation.
Recommendations
  • Add equivalent examples using the Service Fabric CLI (sfctl), which is cross-platform and the standard tool for Linux/macOS environments.
  • Include REST API examples for health reporting and querying, as these are platform-agnostic and useful for automation.
  • Explicitly mention that PowerShell examples are for Windows and provide links or inline examples for Linux/macOS users.
  • Update the 'How to report and check service health' and related links to clarify cross-platform tooling and provide parity in examples.
GitHub Create Pull Request
Service Fabric Azure Service Fabric DNS service ...n/articles/service-fabric/service-fabric-dnsservice.md
Medium Priority View Details →
Scanned: 2026-02-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation covers both Windows and Linux clusters, but several sections show Windows bias. PowerShell is the only CLI example given for setting DNS names, with no Linux CLI (e.g., Bash, Azure CLI) alternatives. The ApplicationManifest.xml example assumes Visual Studio, a Windows-centric tool, and does not mention Linux workflows or editors. Enabling DNS service through the Azure portal is only available for Windows clusters, but this limitation is mentioned. Overall, Linux users are left to infer or research their own methods for several key tasks.
Recommendations
  • Provide Linux/Bash/Azure CLI examples for setting DNS names and managing services, especially for common tasks currently shown only with PowerShell.
  • Mention Linux-friendly editors and workflows for editing ApplicationManifest.xml (e.g., VS Code, nano, vim).
  • Clarify Linux-specific steps for enabling DNS service, including ARM template modifications and limitations, with explicit guidance.
  • Where features are Windows-only, make this clear at the start of each section to avoid confusion.
GitHub Create Pull Request
Service Fabric Azure Service Fabric hosting model ...rticles/service-fabric/service-fabric-hosting-model.md
Medium Priority View Details →
Scanned: 2026-02-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides PowerShell examples and references PowerShell cmdlets for managing Service Fabric services, with no equivalent CLI or Linux/macOS instructions. PowerShell is a Windows-centric tool, and the absence of Azure CLI, Bash, or cross-platform examples creates friction for users on Linux or macOS. The C# example is cross-platform, but operational guidance (e.g., service creation, querying, health reporting) is PowerShell-focused.
Recommendations
  • Add Azure CLI examples for service creation and management tasks, as Azure CLI is cross-platform.
  • Include Bash or shell script equivalents where appropriate.
  • Clarify which management operations can be performed using REST APIs, and provide sample REST calls.
  • Explicitly note PowerShell examples are for Windows, and link to Linux/macOS alternatives.
  • Ensure references to management tools are not exclusively PowerShell; mention cross-platform options where available.
GitHub Create Pull Request
Service Fabric Manage apps for multiple environments ...e-fabric-manage-multiple-environment-app-configuration.md
Medium Priority View Details →
Scanned: 2026-02-02 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 examples and tooling references that prioritize Windows-centric workflows, such as PowerShell cmdlets and Visual Studio integration, with limited or less prominent coverage of Linux/macOS equivalents. While sfctl and Jenkins are mentioned, the examples and explanations are weighted toward Windows tools and patterns, and Linux/macOS users may need to infer or research their own workflows.
Recommendations
  • Provide explicit Linux/macOS command-line examples for common tasks, such as using sfctl and shell scripts for application deployment.
  • Include a section or table comparing Windows and Linux/macOS workflows for managing Service Fabric applications across environments.
  • Highlight cross-platform tools (like sfctl) earlier and more prominently, ensuring parity in example depth and clarity.
  • Add links or references to Linux/macOS-specific documentation or community resources.
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-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page for Azure Service Fabric container application manifest examples exhibits a moderate Windows bias. The examples and explanations are based on the Windows Server 2016 Container Sample, and Windows-specific tools and patterns (such as 'winver' for OS build detection and Windows file paths) are mentioned first or exclusively. There is little to no explicit mention of Linux equivalents, and no Linux-specific manifest samples or guidance are provided, even though Service Fabric supports Linux containers.
Recommendations
  • Include parallel Linux-based manifest examples, or clarify which elements differ for Linux clusters.
  • Add notes or sections explaining how to obtain OS build/version information on Linux (e.g., using 'cat /etc/os-release' or 'uname -r').
  • Provide Linux file path examples (e.g., '/mnt/VolumeTest/Data') alongside Windows paths.
  • Clarify any differences in certificate handling, volume drivers, or container isolation modes between Windows and Linux clusters.
  • Reference Linux container samples in addition to the Windows Server 2016 Container Sample.
GitHub Create Pull Request
Service Fabric Azure Service Fabric image store connection string ...fabric/service-fabric-image-store-connection-string.md
Medium Priority View Details →
Scanned: 2026-02-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page for Azure Service Fabric image store connection string frequently references PowerShell and Windows-centric workflows, such as retrieving the cluster manifest via PowerShell and publishing through Visual Studio. There are no examples or explicit instructions for Linux/macOS users, nor are cross-platform CLI alternatives (e.g., Azure CLI, Bash) mentioned. The 'Next steps' section links only to PowerShell-based deployment guidance, further reinforcing a Windows-first perspective.
Recommendations
  • Add examples for retrieving the cluster manifest using Azure CLI, Bash, or REST API, and clarify which methods work cross-platform.
  • Include deployment instructions for Linux/macOS users, such as using Azure CLI or Service Fabric CLI (sfctl), alongside PowerShell and Visual Studio workflows.
  • Mention and link to documentation for cross-platform tools where available, ensuring parity in guidance for non-Windows environments.
  • Explicitly state platform requirements for any Windows-only steps, and provide alternatives for other operating systems where possible.
GitHub Create Pull Request
Service Fabric Reliable services app manifest examples ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-manifest-example-reliable-services-app.md
Medium Priority View Details →
Scanned: 2026-02-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page for Service Fabric reliable services app manifest examples shows moderate Windows bias. It references Windows-specific concepts (such as running services as local admin, NETWORKSERVICE, and .bat scripts), and mentions using the ServiceFabric PowerShell module for service creation. Examples and explanations use Windows-centric tools and patterns (e.g., .exe and .bat files), with no Linux-specific equivalents or guidance. Linux support for Service Fabric is not acknowledged, and Linux/macOS users may need to infer how to adapt these instructions.
Recommendations
  • Add explicit notes or examples for Linux Service Fabric clusters, such as using shell scripts (.sh) instead of .bat files, and referencing Linux service accounts.
  • Mention Linux-compatible tools for deploying and managing Service Fabric applications (e.g., Service Fabric CLI, sfctl) alongside PowerShell.
  • Clarify which manifest elements and patterns are cross-platform, and which are Windows-only.
  • Provide guidance on running services under Linux user accounts, and how to configure RunAsPolicy for Linux environments.
  • Where .exe or .bat files are referenced, include Linux equivalents (.sh, ELF binaries) in examples.
GitHub Create Pull Request
Service Fabric Service communication with the ASP.NET Core ...vice-fabric-reliable-services-communication-aspnetcore.md
Medium Priority View Details →
Scanned: 2026-02-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation provides detailed coverage of both Kestrel (cross-platform) and HTTP.sys (Windows-only) web servers for ASP.NET Core integration with Azure Service Fabric Reliable Services. However, HTTP.sys (Windows-only) is described first and in greater detail, with explicit code samples and endpoint configuration steps. The documentation notes HTTP.sys is Windows-only, but does not provide equivalent Linux/macOS-specific troubleshooting, deployment, or configuration guidance. Kestrel (cross-platform) is covered well, but Windows-specific tools (e.g., netsh) and patterns are mentioned without Linux alternatives. There are no explicit Linux/macOS code samples or platform-specific notes for non-Windows users.
Recommendations
  • Reorder sections so that Kestrel (cross-platform) is described before HTTP.sys (Windows-only), emphasizing its suitability for Linux/macOS.
  • Add explicit Linux/macOS deployment notes, including any Service Fabric configuration steps or troubleshooting tips unique to those platforms.
  • Where Windows tools (e.g., netsh) are mentioned, clarify that these are not required for Kestrel and provide Linux/macOS equivalents or state when they are not applicable.
  • Include example code snippets or configuration files for Linux/macOS environments, especially for ServiceManifest.xml and endpoint configuration.
  • Add a summary table or decision tree at the top to help users quickly identify which web server and configuration to use based on their OS.
GitHub Create Pull Request
Service Fabric Specifying Service Fabric service endpoints ...ce-fabric/service-fabric-service-manifest-resources.md
Medium Priority View Details →
Scanned: 2026-02-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page provides several examples and deployment instructions using PowerShell commands and Windows file paths, such as 'PS C:\>' and references to 'C:\Program Files\Microsoft SDKs\Service Fabric\schemas\ServiceFabricServiceModel.xsd'. Linux equivalents are mentioned only briefly (e.g., the certificate store path), and there are no Linux/macOS CLI examples or deployment instructions. The documentation assumes familiarity with Windows tooling and patterns, which may create friction for Linux/macOS users.
Recommendations
  • Include Linux/macOS equivalents for PowerShell deployment commands, such as Azure CLI or Service Fabric CLI (sfctl) examples.
  • Document Linux/macOS file paths and installation locations for Service Fabric SDK and schema files.
  • Provide explicit instructions or examples for deploying Service Fabric applications on Linux clusters, including endpoint configuration and certificate management.
  • Ensure that references to tools and commands are cross-platform or clearly indicate platform-specific sections.
GitHub Create Pull Request
Service Fabric Learn Azure Service Fabric terminology ...es/service-fabric/service-fabric-technical-overview.md
Medium Priority View Details →
Scanned: 2026-02-02 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page generally describes Service Fabric concepts in a cross-platform manner, but some terminology and examples are Windows-centric. Specifically, the 'Node' definition references an auto-start Windows service (FabricHost.exe) and Windows executables before mentioning Linux support. The code package section also emphasizes EXE/DLL files, which are Windows formats, and only later clarifies that guest executables can run on Windows or Linux. Windows-specific tools and patterns (Windows service, EXE/DLL) are mentioned first, with Linux equivalents implied but not detailed.
Recommendations
  • When describing nodes, clarify how Service Fabric runs on Linux (e.g., mention the equivalent Linux processes/services alongside Windows services).
  • In the code package section, explicitly state Linux executable formats (e.g., ELF binaries) and how Service Fabric handles them.
  • Provide examples or explanations for both Windows and Linux wherever platform-specific terminology (services, executables) is used.
  • Ensure that cross-platform parity is clear in all sections, especially where Windows-specific terms are introduced.
GitHub Create Pull Request
Service Fabric Replica soft delete for enhanced data protection in Service Fabric ...s/service-fabric/service-fabric-replica-soft-delete.md
Medium Priority View Details →
Scanned: 2026-02-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page for Replica soft delete in Service Fabric exclusively references PowerShell cmdlets (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica, Get-ServiceFabricReplica) for administrative operations, with no mention of equivalent CLI commands, REST APIs, or Linux/macOS-compatible tooling. All operational examples and API references are Windows/PowerShell-centric, and there are no Linux-specific instructions or parity examples.
Recommendations
  • Include examples using cross-platform tools such as Azure CLI or REST API equivalents for managing replicas (removal, restoration, querying).
  • Document how to perform these operations on Linux-based Service Fabric clusters, if supported.
  • Clarify if certain APIs or administrative tasks are only available via PowerShell, and provide alternative guidance for non-Windows users.
  • Add explicit notes or tables indicating platform/tool compatibility for each administrative operation.
GitHub Create Pull Request
Service Fabric Add custom Service Fabric health reports ...rticles/service-fabric/service-fabric-report-health.md
Medium Priority View Details →
Scanned: 2026-02-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed PowerShell examples for health reporting in Service Fabric, with explicit Windows command-line syntax and references to PowerShell cmdlets. There are no equivalent examples or guidance for Linux/macOS users, such as Bash, CLI, or cross-platform scripting. PowerShell is presented before REST, and REST is only briefly mentioned, with no concrete Linux-friendly walkthroughs. This creates friction for non-Windows users, who must infer how to perform these tasks without direct examples.
Recommendations
  • Add equivalent Bash or Azure CLI examples for health reporting tasks, especially for sending reports and querying health status.
  • Clarify which PowerShell commands (if any) are available on Linux/macOS, or provide alternatives if not.
  • Expand REST API usage sections with step-by-step Linux/macOS-friendly instructions, including sample curl commands.
  • Explicitly mention cross-platform options and limitations for Service Fabric management and health reporting.
  • Consider reordering examples so REST or CLI options are shown before or alongside PowerShell.
GitHub Create Pull Request
Service Fabric Fault Analysis Service overview .../service-fabric/service-fabric-testability-overview.md
Medium Priority View Details →
Scanned: 2026-02-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page for the Fault Analysis Service overview in Azure Service Fabric demonstrates a moderate Windows bias. PowerShell is the only command-line example provided, and there is no mention of Linux or cross-platform command-line alternatives (such as Bash, CLI, or REST API usage). The documentation refers to installing the Service Fabric SDK and using PowerShell modules, but does not clarify whether equivalent tooling or instructions exist for Linux/macOS users. The C# example is platform-neutral, but the operational guidance is Windows/PowerShell-centric.
Recommendations
  • Add explicit instructions or examples for Linux/macOS users, such as using Bash, Azure CLI, or REST API to interact with the Fault Analysis Service.
  • Clarify whether the Service Fabric SDK and PowerShell modules are available or supported on Linux/macOS, and provide alternative steps if not.
  • Reorder or balance examples so that Windows and Linux/macOS approaches are presented equally, or at least mention cross-platform options before Windows-specific ones.
  • Include a note about platform support and limitations for the Fault Analysis Service, so users are aware of any OS-specific constraints.
GitHub Create Pull Request
Service Fabric Configure the upgrade of a Service Fabric application ...abric/service-fabric-visualstudio-configure-upgrade.md
Medium Priority View Details →
Scanned: 2026-02-02 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 configuring Service Fabric application upgrades using Visual Studio and PowerShell, both of which are primarily Windows tools. All examples and instructions reference Visual Studio dialogs and PowerShell cmdlets, with no mention of Linux/macOS alternatives, CLI usage, or cross-platform tooling. This creates friction for users on non-Windows platforms, as the upgrade workflow is presented as Windows-centric.
Recommendations
  • Add instructions for upgrading Service Fabric applications using cross-platform tools such as Azure CLI or Service Fabric CLI (sfctl), where applicable.
  • Include examples for configuring upgrade parameters and health policies via command-line or configuration files, not just through Visual Studio dialogs.
  • Clarify which steps are Windows-only and provide alternative guidance for Linux/macOS users, such as using VS Code or other editors for manifest editing.
  • Reference official documentation for Service Fabric management on Linux clusters, if available.
GitHub Create Pull Request
Service Fabric Introduction to the Service Fabric Infrastructure Service .../articles/service-fabric/infrastructure-service-faq.md
Medium Priority View Details →
Scanned: 2026-02-01 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides a PowerShell-only example for bypassing the Infrastructure Service, without mentioning equivalent Linux/macOS command-line options or tools. The use of PowerShell cmdlets and lack of cross-platform instructions creates friction for non-Windows users managing Service Fabric clusters.
Recommendations
  • Include equivalent instructions for Linux/macOS users, such as using Azure CLI, REST API, or Service Fabric CLI (sfctl) if available.
  • Clarify whether the PowerShell command is required or if cross-platform alternatives exist.
  • Add notes or links to cross-platform tooling for cluster management tasks.
GitHub Create Pull Request
← Previous Page 82 of 99 Next →