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 2226-2250 of 2475 flagged pages
Service Fabric Configure the upgrade of a Service Fabric application ...abric/service-fabric-visualstudio-configure-upgrade.md
Medium Priority View Details →
Scanned: 2026-01-30 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 is heavily focused on Windows tooling, specifically Visual Studio and PowerShell, for configuring and upgrading Service Fabric applications. All examples and instructions reference Windows-specific tools and workflows, with no mention of Linux/macOS alternatives or cross-platform CLI options. This creates friction for users on non-Windows platforms who wish to perform similar upgrade tasks.
Recommendations
  • Add instructions and examples for upgrading Service Fabric applications using cross-platform tools such as Azure CLI or Service Fabric CLI (sfctl), where possible.
  • Clarify which steps are Windows-only and provide alternative workflows for Linux/macOS users, especially for manual upgrades.
  • Include Linux/macOS-specific notes or links to relevant documentation for non-Windows environments.
  • Reorder sections or provide parity so that non-Windows approaches are presented alongside Windows ones, not only after them.
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-01-30 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 examples for reporting health in Service Fabric using C#/.NET APIs and PowerShell, both of which are primarily Windows-centric. PowerShell examples are given for connecting to clusters and sending health reports, but there are no equivalent examples for Linux/macOS users (e.g., Bash, Azure CLI, or cross-platform scripting). The REST API is mentioned as a cross-platform option, but no concrete example is provided, and the PowerShell workflow is described before REST. There is no discussion of Linux-specific tooling or patterns for Service Fabric health reporting.
Recommendations
  • Add explicit examples for reporting health using Bash scripts or Azure CLI, which are cross-platform and commonly used on Linux/macOS.
  • Provide REST API usage examples with sample curl commands, including authentication and payload details.
  • Clarify which PowerShell commands (if any) are supported on PowerShell Core on Linux/macOS, or note any limitations.
  • Reorder examples so that REST and cross-platform methods are presented before or alongside Windows/PowerShell examples.
  • Mention any Linux/macOS-specific considerations for Service Fabric health reporting, if applicable.
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-01-30 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides several examples and deployment instructions using Windows-centric tools and patterns, notably PowerShell cmdlets (e.g., New-ServiceFabricApplication) and Windows file paths (e.g., C:\Program Files\...). Linux equivalents are mentioned only briefly, such as the certificate store location, and there are no Linux CLI examples or deployment instructions. Windows tooling and patterns are presented first and exclusively in critical deployment sections.
Recommendations
  • Add equivalent Linux CLI examples (e.g., using Azure CLI, Bash scripts, or Service Fabric CLI) for application deployment and parameter overrides.
  • Include Linux file paths and configuration details alongside Windows paths wherever relevant.
  • Clarify which steps or commands are platform-agnostic and which require platform-specific tools.
  • Provide links or references to Linux/macOS-specific Service Fabric deployment documentation.
  • Ensure parity in example coverage, showing both Windows and Linux workflows for common tasks.
GitHub Create Pull Request
Service Fabric Fault Analysis Service overview .../service-fabric/service-fabric-testability-overview.md
Medium Priority View Details →
Scanned: 2026-01-30 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides explicit instructions for using the Fault Analysis Service via PowerShell, which is a Windows-centric tool, and references the Service Fabric SDK and PowerShell module without mentioning equivalent Linux/macOS CLI or scripting options. There are no examples or guidance for Linux/macOS users, such as using Azure CLI, Bash, or cross-platform Service Fabric tools.
Recommendations
  • Add instructions and examples for using the Fault Analysis Service from Linux/macOS environments, such as via Azure CLI, Bash scripts, or REST APIs.
  • Clarify whether the PowerShell and SDK instructions are Windows-only, and provide alternative steps for non-Windows platforms if available.
  • Include cross-platform code samples and tool references where possible, or explicitly state platform limitations if features are Windows-only.
GitHub Create Pull Request
Service Fabric Configure or modify a Service Fabric managed cluster node type ...vice-fabric/how-to-managed-cluster-modify-node-type.md
Medium Priority View Details →
Scanned: 2026-01-27 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides step-by-step instructions for configuring and modifying Service Fabric managed cluster node types using the Azure portal, ARM templates, and PowerShell. However, all command-line examples are exclusively in PowerShell, with no mention of Azure CLI, Bash, or Linux/macOS shell equivalents. PowerShell is presented as the only scripting option for automation, which may create friction for Linux/macOS users who do not use PowerShell. The documentation does not clarify whether PowerShell Core (cross-platform) is supported, nor does it offer alternative command-line approaches.
Recommendations
  • Add Azure CLI examples for all operations currently shown only in PowerShell, such as adding, removing, scaling, and modifying node types.
  • Explicitly mention whether PowerShell Core (pwsh) is supported on Linux/macOS, or clarify if only Windows PowerShell is required.
  • Provide guidance or links for Linux/macOS users on how to perform these tasks using their preferred environments.
  • Consider listing Azure CLI or cross-platform options before or alongside PowerShell examples to avoid Windows-first bias.
GitHub Create Pull Request
Service Fabric Overview of Azure Service Fabric ...ain/articles/service-fabric/service-fabric-overview.md
Low Priority View Details →
Scanned: 2026-03-10 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation mentions both Windows and Linux environments for Azure Service Fabric, and provides parity in describing development tools for each. However, Windows development is mentioned first, with references to Visual Studio and PowerShell, while Linux development is described second, with Eclipse and Yeoman. No explicit Linux bias or missing Linux examples are present, but the ordering may subtly prioritize Windows.
Recommendations
  • Alternate the order in which Windows and Linux development environments are presented, or present them together in a neutral way.
  • Ensure quickstart and linked guides provide Linux examples and are equally accessible from the overview.
  • Explicitly mention cross-platform support in introductory sections to reinforce parity.
GitHub Create Pull Request
Service Fabric X.509 Certificate-based Authentication in a Service Fabric Cluster ...ticles/service-fabric/cluster-security-certificates.md
Low Priority View Details →
Scanned: 2026-03-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation provides a thorough overview of X.509 certificate-based authentication in Service Fabric clusters, but exhibits mild Windows bias. Windows-specific terminology, tools, and patterns (e.g., certificate store paths like 'LocalMachine\My', references to Win32 CryptoAPI, and event log locations) are mentioned first or exclusively, with Linux equivalents sometimes referenced parenthetically or not at all. Troubleshooting and configuration examples focus on Windows paths and APIs, and PowerShell/C++ error codes are used without Linux-specific guidance.
Recommendations
  • Ensure Linux certificate store paths (e.g., /var/lib/sfcerts) are mentioned equally and clearly alongside Windows paths in all relevant sections.
  • Add troubleshooting guidance for Linux clusters, including log locations and commands for certificate validation (e.g., using openssl, journalctl, or systemd logs).
  • Where Windows APIs (e.g., CertGetCertificateChain) are referenced, provide Linux equivalents or clarify how Service Fabric handles certificate validation on Linux.
  • Include Linux-specific error codes, symptoms, and remediation steps in troubleshooting sections.
  • Present examples and configuration snippets for both Windows and Linux environments, not just Windows-first.
GitHub Create Pull Request
Service Fabric Azure Service Fabric container image management .../articles/service-fabric/container-image-management.md
Low Priority View Details →
Scanned: 2026-03-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 for Azure Service Fabric container image management shows mild Windows bias. Windows container base images (microsoft/windowsservercore, microsoft/nanoserver) are mentioned as default exclusions, and no Linux container image examples or references are provided. The examples and descriptions focus on Windows images and do not mention Linux container management or provide Linux-specific guidance.
Recommendations
  • Add examples referencing common Linux container images (e.g., 'docker.io/library/ubuntu', 'docker.io/library/alpine') in the 'ContainerImagesToSkip' setting.
  • Clarify whether the cleanup and management features apply equally to Linux containers, and if there are any differences in behavior or configuration.
  • Include notes or examples for Linux-based Service Fabric clusters, if supported.
  • Explicitly state if the feature set is Windows-only, or provide parity guidance for Linux users.
GitHub Create Pull Request
Service Fabric Azure Service Fabric networking best practices ...ice-fabric/service-fabric-best-practices-networking.md
Low Priority View Details →
Scanned: 2026-03-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Minor Missing Linux Example
Summary
The documentation provides networking best practices for Azure Service Fabric clusters and covers both Windows and Linux scenarios. However, there is a mild bias toward Windows: PowerShell is referenced as the primary API client, Windows-specific tools and examples (like netsh) are mentioned, and Windows container scenarios are described in more detail. Linux equivalents (such as CLI commands or Linux container networking) are less prominent or missing. Windows examples and terminology often appear first or exclusively, especially in sections about API access and application networking.
Recommendations
  • Add Linux CLI (az CLI) examples alongside PowerShell references, especially for client API access.
  • Include Linux-specific commands for checking dynamic port ranges (e.g., 'ss', 'lsof', or '/proc/net/tcp') instead of only referencing 'netsh'.
  • Expand application networking guidance to cover Linux container workloads and networking modes, not just Windows containers.
  • Balance references to Windows and Linux in tables and explanations, ensuring Linux scenarios are equally described.
  • Where possible, provide links to Linux-focused ARM templates and sample deployments.
GitHub Create Pull Request
Service Fabric Overview of Service Fabric and containers ...s/service-fabric/service-fabric-containers-overview.md
Low Priority View Details →
Scanned: 2026-03-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation provides a balanced overview of Service Fabric container support for both Linux and Windows, but there are minor signs of Windows bias. Windows container runtimes and tools (Mirantis, DockerEE) are listed in more detail than Linux, and Windows scenarios (IIS lift and shift) are described first in the 'Scenarios for using containers' section. However, Linux examples and tutorials are present and referenced throughout.
Recommendations
  • Ensure Linux and Windows examples are presented in parallel, rather than Windows scenarios being listed first.
  • Expand Linux-specific scenarios (e.g., Apache, NGINX, Python workloads) to match the detail given to Windows/IIS examples.
  • Provide more detail on Linux container runtimes and tools, similar to the Windows section.
  • Where possible, alternate the order of Linux and Windows links/examples to avoid 'windows_first' bias.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Docker Compose Deployment Preview ...ticles/service-fabric/service-fabric-docker-compose.md
Low Priority View Details →
Scanned: 2026-03-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both PowerShell and cross-platform CLI (sfctl) examples for deploying Docker Compose files to Azure Service Fabric. However, PowerShell (a Windows-centric tool) is presented first and in greater detail, with more explanation and command coverage. The CLI section is present and functional for Linux/macOS users, but appears secondary.
Recommendations
  • Present the Azure Service Fabric CLI (sfctl) examples before PowerShell, or clarify that sfctl is cross-platform and recommended for Linux/macOS users.
  • Explicitly state which tools are available on which platforms at the start of the 'Deploy a Docker Compose file' section.
  • Ensure that all PowerShell commands have direct sfctl equivalents shown, and vice versa, to reinforce parity.
  • Add a note highlighting that sfctl is the preferred method for non-Windows environments.
GitHub Create Pull Request
Service Fabric Manage apps for multiple environments ...e-fabric-manage-multiple-environment-app-configuration.md
Low Priority View Details →
Scanned: 2026-03-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides examples for managing Service Fabric application parameters across environments. It mentions PowerShell and Visual Studio (both Windows-centric tools) first and in detail, while Linux/macOS equivalents (sfctl, install.sh) are mentioned but with less prominence and detail. There is a slight bias toward Windows tools and workflows, though Linux options are referenced.
Recommendations
  • Provide equally detailed examples for Linux/macOS workflows, such as using sfctl and install.sh.
  • List Linux/macOS tools and commands before or alongside Windows tools to avoid 'windows_first' bias.
  • Expand on how Jenkins (a cross-platform tool) can be used for parameter substitution, including sample scripts.
  • Clarify which tools are cross-platform and which are Windows-only, so users can easily identify their options.
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
Low Priority View Details →
Scanned: 2026-03-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page provides Service Fabric application and service manifest examples, but exhibits mild Windows bias. Windows-specific terminology (e.g., 'NetworkService', 'Administrators', 'Setup.bat', 'VotingWeb.exe') is used throughout, and references to running scripts (e.g., 'Setup.bat') and executables (.exe) are Windows-centric. The only mention of tooling is the 'ServiceFabric PowerShell module', with no Linux CLI or cross-platform alternatives referenced. There are no explicit Linux/macOS examples or notes about cross-platform support.
Recommendations
  • Add examples or notes for Linux deployments, such as using shell scripts (.sh) instead of batch files (.bat) and referencing Linux user/group equivalents.
  • Mention cross-platform tools (e.g., Azure CLI, sfctl) alongside PowerShell, and provide example commands for Linux/macOS.
  • Clarify which features are Windows-only and which are supported on Linux clusters, especially around user accounts and security principals.
  • Include guidance for running .NET Core apps on Linux Service Fabric clusters, if supported.
  • Where possible, use neutral terminology (e.g., 'service executable') and provide both Windows and Linux file formats in examples.
GitHub Create Pull Request
Service Fabric Azure Service Fabric container application manifest examples ...abric/service-fabric-manifest-example-container-app.md
Low Priority View Details →
Scanned: 2026-03-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a mild Windows bias. The manifest examples and explanations are based on the 'Windows Server 2016 Container Sample', and Windows-specific tools and patterns (such as referencing 'winver' to get the OS build version) are mentioned before or instead of their Linux equivalents. However, the documentation does acknowledge Linux in places (e.g., certificate handling), and the manifest XML itself is largely cross-platform. There are no PowerShell-heavy sections or critical omissions of Linux examples, but the overall framing and some instructions assume a Windows-first context.
Recommendations
  • Include or reference parallel Linux-based manifest samples, or clarify which elements are cross-platform and which are Windows-specific.
  • When mentioning Windows tools (e.g., 'winver'), also mention the Linux equivalent (e.g., 'cat /etc/os-release' or 'uname -r') for determining OS version.
  • Explicitly state which manifest features or XML elements are supported on Linux clusters, and highlight any differences.
  • If possible, provide links to Linux container samples or documentation alongside the Windows sample reference.
GitHub Create Pull Request
Service Fabric Reliable Collection object serialization ...c-reliable-services-reliable-collections-serialization.md
Low Priority View Details →
Scanned: 2026-03-10 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides code examples and references that are primarily .NET/C#-centric, which is common for Service Fabric, but does not show Linux-specific patterns or alternatives. In the 'Next steps' section, Windows tools (Visual Studio, PowerShell) are mentioned before any Linux-friendly options, and there are no explicit Linux/macOS examples or CLI alternatives provided.
Recommendations
  • Add examples or notes for Linux/macOS users, such as using the Azure CLI or Service Fabric CLI (sfctl) for application upgrades.
  • Mention cross-platform development environments (e.g., Visual Studio Code) alongside Visual Studio.
  • Clarify if the serialization APIs and patterns are equally supported on Linux Service Fabric clusters, and provide any relevant differences.
  • Reorder 'Next steps' to avoid always listing Windows tools first, or group by platform.
GitHub Create Pull Request
Service Fabric Custom Image .../articles/service-fabric/how-to-deploy-custom-image.md
Low Priority View Details →
Scanned: 2026-03-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page exhibits mild Windows bias. The introductory section and terminology focus on 'custom windows images' and Windows-specific concepts, with Windows mentioned before Linux. The only command-line example provided is a PowerShell command for role assignment, with no equivalent Linux/CLI example. However, the page does reference Linux custom image creation and Azure CLI for browsing images, and the ARM template examples are platform-agnostic.
Recommendations
  • Provide Azure CLI or Bash equivalents for the PowerShell role assignment command.
  • Clarify that custom images can be Linux or Windows, and adjust introductory language to be more inclusive.
  • Add explicit examples or links for Linux custom image usage and deployment.
  • Ensure parity in guidance for both Windows and Linux image scenarios.
GitHub Create Pull Request
Service Fabric Overview of Azure Service Fabric ...ain/articles/service-fabric/service-fabric-overview.md
Low Priority View Details →
Scanned: 2026-03-09 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation mentions both Windows and Linux support for Azure Service Fabric, including development environments and SDKs. However, Windows development (Visual Studio and PowerShell) is described before Linux development (Eclipse and Yeoman), and the quickstart link points to a .NET (likely Windows-centric) guide. There are no Linux-specific examples or links provided in the 'Next steps' section, and Windows tools are mentioned first.
Recommendations
  • Provide Linux-specific quickstart links alongside Windows/.NET quickstart.
  • Alternate the order of Windows and Linux development environment descriptions, or present them side-by-side.
  • Include examples or links for Linux development and deployment in the 'Next steps' section.
  • Clarify that .NET Core/.NET 5+ workloads are cross-platform and provide guidance for Linux users.
GitHub Create Pull Request
Service Fabric Azure Service Fabric container image management .../articles/service-fabric/container-image-management.md
Low Priority View Details →
Scanned: 2026-03-09 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 image management exhibits mild Windows bias. Windows container base images (microsoft/windowsservercore, microsoft/nanoserver) are referenced as default exclusions, and no Linux container image examples or references are provided. The configuration examples and descriptions do not mention Linux-specific images or patterns, nor do they clarify parity for Linux-based Service Fabric clusters.
Recommendations
  • Add examples or references to Linux container images (e.g., Ubuntu, Alpine) in the 'ContainerImagesToSkip' setting.
  • Clarify whether the described cleanup features and settings apply equally to Linux-based Service Fabric clusters.
  • Provide sample configurations or notes for Linux container scenarios, including any differences in behavior or recommended practices.
  • Mention common Linux container base images alongside Windows ones to ensure parity.
GitHub Create Pull Request
Service Fabric Azure Service Fabric networking best practices ...ice-fabric/service-fabric-best-practices-networking.md
Low Priority View Details →
Scanned: 2026-03-09 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Minor Windows Example
Summary
The documentation provides networking best practices for Azure Service Fabric clusters and covers both Windows and Linux scenarios. However, there is a mild bias toward Windows: PowerShell is referenced as the primary client API example, Windows-specific tools and scenarios (e.g., RDP, Windows Update, Windows containers) are mentioned before or more prominently than Linux equivalents, and some sample links and templates are Windows-focused. Linux is referenced, but examples and explanations are often Windows-first or Windows-heavy.
Recommendations
  • Add explicit Linux CLI (az, bash) examples alongside PowerShell for client API access and cluster management.
  • Provide links to Linux-focused ARM templates and sample clusters, not just Windows ones.
  • Clarify when a feature or example applies to both Windows and Linux, and provide parity in explanations.
  • Where Windows tools (e.g., netsh) are mentioned, add Linux equivalents (e.g., ss, netstat, iptables) or note differences.
  • Ensure reverse proxy and container networking guidance includes Linux container scenarios, not just Windows containers.
GitHub Create Pull Request
Service Fabric Overview of Service Fabric and containers ...s/service-fabric/service-fabric-containers-overview.md
Low Priority View Details →
Scanned: 2026-03-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation provides a balanced overview of Service Fabric container support for both Linux and Windows, but Windows-specific tools and scenarios (such as IIS lift-and-shift and Mirantis Container Runtime) are mentioned in detail, and Windows examples and links are sometimes presented before Linux equivalents. However, Linux support and examples are also clearly included.
Recommendations
  • Ensure Linux and Windows examples are presented in parallel, with equal prominence.
  • Add more Linux-specific scenarios (e.g., Apache/Nginx lift-and-shift) to match the Windows IIS example.
  • Clarify Linux container runtime options beyond Docker, if relevant.
  • Where Windows tools are mentioned (e.g., Mirantis Container Runtime), provide equivalent Linux context or alternatives.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Docker Compose Deployment Preview ...ticles/service-fabric/service-fabric-docker-compose.md
Low Priority View Details →
Scanned: 2026-03-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both PowerShell and cross-platform CLI (sfctl) instructions for deploying Docker Compose files to Azure Service Fabric. However, PowerShell examples are presented first and in more detail, which may suggest a Windows-first approach. The CLI section is present and sufficient for Linux/macOS users, but the initial emphasis on PowerShell may create minor friction.
Recommendations
  • Present CLI (sfctl) instructions before or alongside PowerShell examples to emphasize cross-platform support.
  • Explicitly state that sfctl is cross-platform and suitable for Linux/macOS users.
  • Consider balancing the detail and prominence of PowerShell and CLI examples.
  • Add a short note clarifying that all deployment operations can be performed using sfctl on any OS.
GitHub Create Pull Request
Service Fabric Package an existing executable to Azure Service Fabric ...abric/service-fabric-guest-executables-introduction.md
Low Priority View Details →
Scanned: 2026-03-09 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 mild Windows bias. The schema definition for manifest files is referenced with a Windows file path, and there is no mention of Linux/macOS equivalents or installation locations. The examples and directory structure use Windows conventions (e.g., .exe files, Windows-style paths). There are no explicit Linux/macOS examples or guidance, and Visual Studio (a Windows-centric tool) is mentioned as a packaging option without alternatives for Linux/macOS users.
Recommendations
  • Include Linux/macOS file path examples for schema definitions and manifest locations.
  • Provide guidance or links for packaging and deploying guest executables using cross-platform tools (e.g., Azure CLI, Service Fabric CLI, or VS Code).
  • Clarify whether the Service Fabric SDK and packaging tools are available and supported on Linux/macOS, and provide installation instructions if so.
  • Add examples using Linux/macOS executables (e.g., ELF binaries, shell scripts) and directory structures.
  • Mention alternative editors or IDEs for Linux/macOS users if Visual Studio is not available.
GitHub Create Pull Request
Service Fabric Reliable Collection object serialization ...c-reliable-services-reliable-collections-serialization.md
Low Priority View Details →
Scanned: 2026-03-09 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides conceptual and code examples for Reliable Collection object serialization in Azure Service Fabric, focusing on .NET/C# usage. While the main content is platform-neutral, the 'Next steps' section lists 'Upgrading your Application Using Visual Studio' and 'Upgrading your Application Using PowerShell' before any mention of Linux/macOS tools or equivalents. There are no Linux-specific examples or references to cross-platform tooling, which may create a minor perception of Windows bias.
Recommendations
  • Add links or references to Linux/macOS-compatible upgrade tools (e.g., Azure CLI, Service Fabric CLI) in the 'Next steps' section.
  • Include examples or guidance for developers using Service Fabric on Linux, such as how to register custom serializers in .NET Core/.NET 5+ environments.
  • Clarify that Service Fabric supports both Windows and Linux clusters, and note any platform-specific differences in serialization or upgrade processes.
  • Consider alternating the order of Windows and Linux/macOS tooling references, or grouping them together for parity.
GitHub Create Pull Request
Service Fabric Learn Azure Service Fabric terminology ...es/service-fabric/service-fabric-technical-overview.md
Low Priority View Details →
Scanned: 2026-03-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page is generally platform-neutral and describes Service Fabric concepts applicable to both Windows and Linux. However, there are subtle signs of Windows bias: Windows-specific terminology (e.g., 'Windows service', 'EXE/DLL files') and Windows tools (e.g., 'FabricHost.exe') are mentioned first or exclusively in some sections, even though Linux is supported. Linux equivalents or clarifications are not always provided alongside Windows references.
Recommendations
  • Where Windows-specific tools or executables are mentioned (e.g., 'FabricHost.exe', 'EXE/DLL files'), clarify if/how these concepts apply on Linux clusters, or explicitly state differences.
  • When describing node startup processes, include Linux-specific details or note if the process differs.
  • When referencing file types (e.g., EXE/DLL), add Linux equivalents (e.g., ELF binaries, .so files) or clarify that Linux binaries are supported.
  • Ensure that examples and terminology are equally representative of both Windows and Linux environments.
  • Add links or references to Linux-specific documentation where relevant.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Docker Compose Deployment Preview ...ticles/service-fabric/service-fabric-docker-compose.md
Low Priority View Details →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both PowerShell and cross-platform CLI (sfctl) examples for deploying Docker Compose applications to Azure Service Fabric. However, the PowerShell section is presented first and in greater detail, with the CLI section labeled as 'alternative.' This ordering and emphasis may suggest a preference for Windows/PowerShell usage, even though the CLI is cross-platform. No Linux/macOS-specific tools or patterns are missing, and the CLI examples are sufficient for non-Windows users.
Recommendations
  • Present the Service Fabric CLI (sfctl) examples before or alongside the PowerShell examples to emphasize cross-platform support.
  • Explicitly mention that sfctl is cross-platform and suitable for Linux/macOS users.
  • Consider adding a short introductory note clarifying that both PowerShell and sfctl are supported, and users should choose based on their OS.
  • Ensure that any advanced usage or troubleshooting sections include CLI examples, not just PowerShell.
GitHub Create Pull Request
← Previous Page 90 of 99 Next →