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 2301-2325 of 2475 flagged pages
Service Fabric Learn Azure Service Fabric terminology ...es/service-fabric/service-fabric-technical-overview.md
Low Priority View Details →
Scanned: 2026-03-01 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page is largely platform-neutral, but there are subtle indications of Windows bias. Windows terminology and tools (such as references to 'auto-start Windows service', 'FabricHost.exe', and EXE/DLL files) are mentioned first or exclusively in some sections, even though Service Fabric supports Linux. Linux equivalents are not always described with equal clarity or prominence. However, the page does acknowledge Linux support and containers, and does not prevent Linux/macOS users from understanding the concepts.
Recommendations
  • Where Windows-specific tools or terminology are mentioned (e.g., 'auto-start Windows service', 'EXE/DLL'), add clarifying notes about Linux equivalents (e.g., systemd services, ELF binaries).
  • When describing node startup and service processes, explicitly mention Linux process management and file types alongside Windows examples.
  • Ensure that references to executables and packaging (e.g., code packages) include Linux file formats and conventions.
  • Consider alternating the order of Windows and Linux mentions, or grouping them together to reinforce parity.
  • Add links or references to Linux-specific documentation or guides where appropriate.
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-02-28 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page provides a thorough overview of X.509 certificate-based authentication in Service Fabric clusters, but exhibits mild Windows bias. Windows-specific terminology (e.g., certificate store paths like 'LocalMachine\My'), references to Windows APIs (Win32 CryptoAPI, CertGetCertificateChain), and troubleshooting guidance (event logs, CAPI2 logging) are presented first and in greater detail. Linux equivalents are mentioned briefly (e.g., '*var/lib/sfcerts*'), but lack parity in examples, troubleshooting, and tool references.
Recommendations
  • Expand Linux-specific guidance, including certificate store locations, relevant commands (such as openssl, systemd journal, or Linux certificate management tools), and troubleshooting steps.
  • Provide Linux/macOS examples alongside Windows examples, including cluster manifest excerpts and certificate management workflows.
  • Clarify cross-platform differences in certificate handling, validation, and error codes.
  • Reference Linux/macOS documentation or tools where Windows-specific APIs or logs are mentioned.
  • Ensure troubleshooting sections include Linux/macOS log locations and diagnostic commands.
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-02-28 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, but PowerShell commands are presented first and in greater detail. This ordering and emphasis may create friction for Linux/macOS users, as PowerShell is primarily a Windows tool, while sfctl is cross-platform. However, Linux-compatible instructions are present and functional.
Recommendations
  • Present sfctl (CLI) examples before PowerShell, or at least in parallel, to emphasize cross-platform support.
  • Explicitly state that sfctl is recommended for Linux/macOS users.
  • Clarify any OS-specific requirements for PowerShell and sfctl usage.
  • Ensure equal detail and explanation for CLI and PowerShell sections.
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-02-28 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 is described first, and the quickstart link points to a .NET (Windows-oriented) guide, potentially creating a perception of Windows as the default or primary platform. Linux examples and tooling are mentioned, but not as prominently or as the first option.
Recommendations
  • Alternate the order in which Windows and Linux development environments are described, or present them side-by-side.
  • Provide quickstart links for both Windows (.NET) and Linux (Java/.NET Core) users in the 'Next steps' section.
  • Ensure that Linux-specific tooling and examples are as visible and accessible as Windows equivalents.
  • Clarify that Service Fabric supports both platforms equally, and highlight cross-platform parity.
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-02-28 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 Container Runtime, DockerEE) are listed in detail, while Linux only mentions Docker. Windows scenarios (IIS lift and shift) are described first and in more depth, with links to Windows container resources. Linux examples and tutorials are present and referenced, but Windows-specific tools and scenarios are more prominent.
Recommendations
  • Expand the Linux container runtime section to mention alternatives or clarify Docker's role and compatibility.
  • Provide more Linux-specific scenarios, such as using NGINX, Apache, or other Linux-native workloads, to balance the IIS lift-and-shift example.
  • Ensure Linux and Windows tutorials are referenced equally and with similar prominence throughout the article.
  • Add links to Linux container resources (e.g., Docker documentation, Linux container best practices) alongside Windows container links.
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-02-28 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page presents Service Fabric guest executable packaging in a generally platform-neutral way, but it exhibits mild Windows bias. The directory structure example uses a Windows-style .exe file, and the Service Fabric SDK schema path is given only as a Windows filesystem location. There are no explicit Linux/macOS examples or references, and Visual Studio (a Windows-centric tool) is mentioned before command-line utilities. However, the content does not prevent Linux/macOS users from understanding or completing the task.
Recommendations
  • Include examples using Linux/macOS file paths and executable formats (e.g., .sh, no extension).
  • Mention cross-platform tools (e.g., Visual Studio Code, CLI utilities) alongside Visual Studio.
  • Provide the location of Service Fabric SDK schema files for Linux/macOS installations, if available.
  • Add explicit notes or examples for packaging non-Windows executables.
GitHub Create Pull Request
Service Fabric Reliable Collection object serialization ...c-reliable-services-reliable-collections-serialization.md
Low Priority View Details →
Scanned: 2026-02-27 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation primarily focuses on .NET and C# examples, which are cross-platform, but the 'Next steps' section lists Windows-centric tools (Visual Studio and PowerShell) before mentioning any alternatives. There are no Linux-specific examples or references to Linux tooling, but the core serialization content is platform-neutral.
Recommendations
  • Add examples or links for upgrading applications using Linux/macOS tools, such as Azure CLI or Bash scripts.
  • Mention cross-platform development environments (e.g., VS Code, JetBrains Rider) alongside Visual Studio.
  • Clarify that PowerShell is available cross-platform, or provide equivalent Bash/CLI instructions.
  • Ensure that any referenced tutorials or guides include Linux/macOS options where applicable.
GitHub Create Pull Request
Service Fabric Understanding periodic backup configuration ...-fabric-backuprestoreservice-configure-periodic-backup.md
Low Priority View Details →
Scanned: 2026-02-27 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 Service Fabric's backup configuration via REST APIs and JSON payloads. However, the only example for file share backup storage uses Windows-style UNC paths (\\StorageServer\BackupStore) and references 'Integrated Windows Authentication', which are Windows-specific concepts. No Linux or SMB/CIFS examples are provided, and Windows authentication is mentioned first. This creates minor friction for Linux users who may want to use SMB/CIFS file shares or need guidance on configuring file share access from non-Windows nodes.
Recommendations
  • Add examples showing how to configure file share backup storage using SMB/CIFS paths compatible with Linux/macOS (e.g., //StorageServer/BackupStore).
  • Include guidance or links for configuring file share access and authentication from Linux-based Service Fabric clusters, such as using mount options or credential management.
  • Clarify whether Linux clusters can use file share backup storage and, if so, provide parity in authentication and path examples.
  • Mention any limitations or differences for Linux/macOS clusters regarding file share backup storage.
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-02-27 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 are described in more detail, and Windows scenarios (such as IIS lift-and-shift) are highlighted first in the 'Scenarios for using containers' section. Windows tutorials and references are often listed before Linux equivalents, and Windows-specific tools (Mirantis Container Runtime, DockerEE) are mentioned with more granularity than Linux (which only mentions Docker).
Recommendations
  • Ensure Linux examples and tutorials are listed alongside Windows ones, ideally alternating or grouping by platform.
  • Expand Linux-specific scenarios (e.g., NGINX, Apache, Python apps) in the 'Scenarios for using containers' section to balance the Windows IIS example.
  • Provide more detail about Linux container runtimes and tools (e.g., mention containerd, podman, or Docker alternatives if supported).
  • Clarify parity in feature support between Linux and Windows containers, especially for advanced features (networking modes, resource governance, etc.).
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-02-27 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 Docker Compose deployment. However, PowerShell commands are presented first and in greater detail, which may suggest a Windows-first bias. The CLI examples, which are cross-platform, are included but appear after the PowerShell section.
Recommendations
  • Present cross-platform CLI (sfctl) examples before PowerShell to emphasize Linux/macOS parity.
  • Explicitly state that sfctl is supported on Linux/macOS and link to installation instructions for non-Windows users.
  • Ensure that all features described are available via sfctl, and clarify any differences in functionality or limitations between PowerShell and CLI.
  • Consider adding a short note at the start of the examples section highlighting that both Windows (PowerShell) and cross-platform (sfctl) options are available.
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-02-27 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates mild Windows bias. The schema definition for manifest files is referenced as being installed in a Windows file path, and the example application package structure uses a Windows-style executable (.exe). Visual Studio is mentioned as a packaging tool, which is primarily a Windows application. There are no explicit Linux/macOS examples or references to cross-platform tooling, and Windows terminology appears first or exclusively.
Recommendations
  • Add Linux/macOS equivalent instructions for locating schema files, or clarify if the SDK supports those platforms.
  • Provide examples using cross-platform executables (e.g., .sh, .out, or generic binaries) alongside .exe.
  • Mention or link to cross-platform command-line tools for packaging and deploying guest executables, if available.
  • Clarify Visual Studio alternatives for Linux/macOS users, such as Visual Studio Code or CLI tools.
  • Explicitly state platform support for Service Fabric guest executables and SDK, including any limitations.
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-02-27 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 Service Fabric, and provides parity in describing development environments for each. However, Windows development (with .NET SDK, Visual Studio, and PowerShell) is described before Linux development (with Java SDK, Eclipse, and Yeoman), which is a minor 'windows_first' bias. No Windows-only tools or examples are given exclusively, and Linux equivalents are mentioned. No critical sections are Windows-only.
Recommendations
  • Alternate the order in which Windows and Linux development environments are described, or present them side-by-side to emphasize equal support.
  • Consider linking to both Windows and Linux quickstart guides in the 'Next steps' section, rather than only the .NET (Windows) quickstart.
  • Explicitly state Linux/macOS support in introductory sections to reinforce 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-02-27 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, but there are subtle signs of Windows bias. Windows-specific terminology and tools (such as references to 'auto-start Windows service', 'FabricHost.exe', and EXE/DLL files) are mentioned first or exclusively in some sections, even though Service Fabric supports Linux. Linux equivalents or clarifications are not always provided alongside Windows examples. However, the page does acknowledge Linux support and containers, and does not prevent Linux/macOS users from understanding the concepts.
Recommendations
  • When referencing Windows-specific tools or services (e.g., 'FabricHost.exe'), clarify if and how these concepts apply on Linux (e.g., what is the equivalent process/service on Linux nodes?).
  • When mentioning executable formats (EXE/DLL), add Linux equivalents (e.g., ELF binaries, .so files) or note that Linux executables are supported.
  • Where Windows terminology is used (e.g., 'auto-start Windows service'), add a note about Linux startup mechanisms (e.g., systemd services) if relevant.
  • Ensure that examples and terminology are presented in a platform-neutral way, or provide parallel Linux/macOS information when possible.
GitHub Create Pull Request
Service Fabric Architecture of Azure Service Fabric ...articles/service-fabric/service-fabric-architecture.md
Low Priority View Details →
Scanned: 2026-02-26 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 specifically mentions 'PowerShell cmdlets' as the primary tooling for lifecycle management, without referencing equivalent Linux/macOS tools (such as Azure CLI or REST APIs). Additionally, Windows security is mentioned alongside X509 certificates in the Transport subsystem, but Linux equivalents are not discussed. These patterns indicate a mild Windows bias, primarily in tooling references.
Recommendations
  • Mention Azure CLI and REST API options for management tasks alongside PowerShell cmdlets.
  • Clarify that management operations can be performed from Linux/macOS using Azure CLI or SDKs.
  • In the Transport subsystem section, explain how security is handled on non-Windows platforms (e.g., X509 certificates, other mechanisms).
  • Ensure examples and tooling references are platform-neutral or provide parity for Linux/macOS users.
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-02-26 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation presents Windows/PowerShell examples first and in greater detail, such as referencing the New-ServiceFabricApplication PowerShell cmdlet and Visual Studio workflows before mentioning Linux-compatible tools like sfctl. While Linux tools are mentioned, the ordering and emphasis favor Windows environments.
Recommendations
  • Present Linux-compatible tools (e.g., sfctl, install.sh) before or alongside Windows/PowerShell examples.
  • Provide explicit Linux/macOS command-line examples for parameter passing and deployment.
  • Clarify which tools are cross-platform and which are Windows-only.
  • Add guidance for Linux/macOS users on using parameter files and scripts outside Visual Studio.
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-02-26 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. However, PowerShell is presented first and in greater detail, which may suggest a Windows-first bias. The CLI examples (sfctl) are cross-platform, but the initial focus on PowerShell may create friction for Linux/macOS users. No Linux-specific tools or shell examples (e.g., Bash scripts) are provided, but the CLI coverage does allow non-Windows users to complete all tasks.
Recommendations
  • Present Service Fabric CLI (sfctl) examples before PowerShell, or clarify that sfctl is cross-platform and recommended for Linux/macOS users.
  • Explicitly mention that all deployment and management tasks can be performed on Linux/macOS using sfctl.
  • Consider adding a short Bash example or note for Linux/macOS users to reinforce parity.
  • Add a table summarizing which tools are available on which platforms.
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-02-26 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 Service Fabric, and references development tools for each platform. However, Windows development (Visual Studio and PowerShell) is mentioned before Linux development (Eclipse and Yeoman), and the quickstart link points to a .NET (likely Windows-focused) guide. There are no Linux-specific examples or quickstart links provided, and Windows tools are referenced first.
Recommendations
  • Provide Linux/macOS quickstart links alongside the Windows/.NET quickstart.
  • Alternate the order of mentioning Windows and Linux development tools to avoid implicit prioritization.
  • Include explicit examples or walkthroughs for Linux development and deployment.
  • Clarify parity between Windows and Linux features, linking to documentation on differences.
GitHub Create Pull Request
Service Fabric Change Azure Service Fabric cluster settings ...rvice-fabric/service-fabric-cluster-fabric-settings.md
Low Priority View Details →
Scanned: 2026-02-26 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page covers Service Fabric cluster settings for both Azure-hosted and standalone clusters. While the content is largely platform-neutral, there are several subtle signs of Windows bias: Windows terminology (e.g., 'certificate store', 'MY', 'LocalMachine'), Windows-centric defaults (e.g., NTLM authentication, Windows Defender Firewall), and Windows-specific references (e.g., 'Windows Fabric Replicator', 'fabric.exe'). Windows tools and patterns (such as certificate store names and NTLM) are mentioned exclusively or before Linux equivalents. Linux-specific settings are present but less prominent and often appear as exceptions or afterthoughts.
Recommendations
  • Where certificate store names are referenced (e.g., 'MY', 'LocalMachine'), clarify Linux equivalents and provide explicit Linux guidance.
  • For NTLM authentication and Windows Defender Firewall, clearly state Linux alternatives or limitations.
  • When referencing Windows-specific tools (e.g., 'fabric.exe', 'Windows Fabric Replicator'), add Linux context or note if the feature is unavailable on Linux.
  • Ensure Linux-specific settings (such as X509Folder, LinuxExternalExecutablePath) are given equal prominence and explanation.
  • Review default values and descriptions to ensure Linux defaults are equally documented.
  • Consider adding a summary table or section highlighting platform differences for key settings.
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-02-26 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. However, there is a slight bias towards Windows, such as mentioning Windows container runtimes and IIS scenarios before Linux equivalents, and referencing Windows-specific tools and patterns (e.g., Mirantis Container Runtime, IIS lift-and-shift). Linux support is present and linked, but Windows examples and tools are sometimes presented first or in greater detail.
Recommendations
  • Ensure Linux examples and scenarios are presented with equal prominence and detail as Windows.
  • When listing container runtimes, mention Linux (Docker) first or equally alongside Windows options.
  • Add Linux-specific 'lift-and-shift' scenarios (e.g., Apache, NGINX) to balance the IIS example.
  • Where Windows tools are mentioned (e.g., Mirantis, IIS), include Linux equivalents or clarify their scope.
  • Review the order of quickstart/tutorial links to alternate Linux and Windows, or group them together.
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-02-26 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page provides Service Fabric application and service manifest examples, but it exhibits minor Windows bias. The only explicit cross-platform friction is the mention of 'ServiceFabric PowerShell module' for service creation, with no Linux CLI equivalent. Additionally, references to Windows-centric accounts (e.g., NetworkService, Administrators) are present, but these are intrinsic to Service Fabric's security model and not strictly Windows-only. No Linux-specific examples, tools, or patterns are provided, and Windows terminology appears first or exclusively in some sections.
Recommendations
  • Add equivalent Azure CLI or Service Fabric CLI (sfctl) commands for service creation and management, especially for Linux users.
  • Clarify which security principal/account types are supported on Linux clusters (e.g., local user, group, etc.) and note any differences.
  • Where scripts are referenced (e.g., Setup.bat), provide examples or guidance for Linux shell scripts (e.g., Setup.sh) if supported.
  • Explicitly state any limitations or differences for Linux Service Fabric clusters, especially regarding user accounts, endpoints, and resource governance.
  • Consider including manifest snippets or examples that highlight Linux-specific deployment patterns if applicable.
GitHub Create Pull Request
Service Fabric Reliable Collection object serialization ...c-reliable-services-reliable-collections-serialization.md
Low Priority View Details →
Scanned: 2026-02-26 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides code examples and references exclusively in C#/.NET, which is cross-platform but historically associated with Windows. The 'Next steps' section lists Visual Studio and PowerShell upgrade tutorials, with Visual Studio (a Windows-centric IDE) mentioned before PowerShell. No Linux/macOS-specific tools, patterns, or examples are provided, but the content is not strictly Windows-only.
Recommendations
  • Add examples or guidance for using cross-platform .NET development tools (such as VS Code, CLI tools) on Linux/macOS.
  • Include references to Linux/macOS-compatible upgrade workflows (e.g., using Azure CLI or .NET CLI instead of PowerShell/Visual Studio).
  • Clarify that Service Fabric Reliable Collections and custom serialization are supported on Linux node types, if applicable.
  • Consider providing sample code or links for Linux/macOS environments where relevant.
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-02-26 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, but there are some subtle Windows biases. Windows terminology and tools (such as references to Windows services and EXE/DLL files) are mentioned first or exclusively in several sections. For example, the description of nodes references an 'auto-start Windows service, FabricHost.exe', and code packages are described as containing 'EXE/DLL files'. While Linux is mentioned in the context of containers and guest executables, Windows-specific patterns and terminology are more prominent and appear first. However, Linux support is acknowledged and described in relevant places.
Recommendations
  • Clarify that the node startup process differs between Windows and Linux, and describe the Linux equivalent (e.g., systemd services or relevant Linux processes).
  • When describing code packages, mention Linux executable formats (e.g., ELF binaries) alongside EXE/DLL files.
  • Ensure examples and terminology are balanced, mentioning Linux and Windows equally, and avoid defaulting to Windows-first descriptions.
  • Add links or references to Linux-specific documentation or guides where appropriate.
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-02-25 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 examples are presented first and in greater detail, which may suggest a Windows-first bias. There is no explicit mention of Linux/macOS-specific issues or guidance, and the CLI section is less emphasized.
Recommendations
  • Present CLI (sfctl) examples before PowerShell, as sfctl is cross-platform and more accessible to Linux/macOS users.
  • Explicitly state that sfctl works on all major platforms and is recommended for non-Windows environments.
  • Balance the level of detail between PowerShell and CLI sections, ensuring both have equivalent explanations and troubleshooting notes.
  • Add a brief note clarifying that PowerShell commands require Windows, and recommend sfctl for Linux/macOS users.
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-02-25 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 using PowerShell, sfctl, and Visual Studio. PowerShell and Visual Studio (Windows-centric tools) are mentioned first and in more detail, while Linux-friendly tools (sfctl, install.sh) are referenced but not emphasized. There is a mild bias toward Windows tools and workflows, with limited Linux/macOS-specific guidance.
Recommendations
  • Add explicit Linux/macOS examples for parameter passing, such as using sfctl from Bash or install.sh.
  • Clarify which tools are cross-platform and which are Windows-only.
  • Provide sample scripts or workflows for Linux/macOS users, e.g., using Bash or shell scripts for parameter substitution.
  • Ensure parity in detail and order between Windows and Linux/macOS tools/examples.
GitHub Create Pull Request
← Previous Page 93 of 99 Next →