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 2326-2350 of 2475 flagged pages
Service Fabric Azure Service Fabric container image management .../articles/service-fabric/container-image-management.md
Low Priority View Details →
Scanned: 2026-02-25 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page for Azure Service Fabric container image management shows minor Windows bias. Windows container base images (microsoft/windowsservercore, microsoft/nanoserver) are referenced as default exclusions in cleanup settings, and Windows image examples are given before Linux equivalents. However, the configuration and cleanup logic appear to be platform-agnostic, and Linux container images are referenced in example regular expressions (e.g., docker.io/library/alpine:latest). No PowerShell or Windows-only tooling is mentioned.
Recommendations
  • Include explicit Linux container image examples (e.g., Ubuntu, Alpine, etc.) in the 'ContainerImagesToSkip' documentation.
  • Clarify that the cleanup settings apply to both Windows and Linux containers, if applicable.
  • Add a note or section about managing Linux container images, including any platform-specific considerations.
  • Ensure parity in examples and descriptions for both Windows and Linux container scenarios.
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-25 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's container support for both Linux and Windows. However, there is a slight bias toward Windows: Windows container runtimes are listed in more detail, Windows-specific tools (Mirantis Container Runtime, DockerEE) are mentioned, and Windows scenarios (IIS lift and shift) are described first in the 'Scenarios for using containers' section. Linux examples and tutorials are present, but Windows tools and scenarios are often mentioned before their Linux equivalents.
Recommendations
  • Ensure Linux scenarios are described with equal prominence and detail as Windows scenarios.
  • List Linux container runtimes and tools with the same specificity as Windows (e.g., mention Docker CE, Podman, or other relevant Linux container runtimes if supported).
  • Alternate the order of Linux and Windows examples/tutorials to avoid always listing Windows first.
  • Expand Linux-specific use cases in the 'Scenarios for using containers' section, such as using Apache, NGINX, or other Linux-native workloads.
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-25 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, and provides parity in describing development environments and cluster deployment. However, in the 'Any OS, any cloud' section, Windows development (with Visual Studio and PowerShell) is described before Linux development (with Eclipse and Yeoman), and the quickstart link points to a .NET/Windows-focused guide. No Linux-specific examples or quickstart links are provided, and Windows tools are mentioned first.
Recommendations
  • Provide Linux quickstart links alongside Windows/.NET quickstart.
  • Alternate the order of Windows and Linux development environment descriptions, or present them in parallel.
  • Include examples or references for Linux development and deployment in the 'Next steps' section.
  • Ensure that Linux tools (Eclipse, Yeoman, Java SDK) are given equal prominence to Windows tools (Visual Studio, PowerShell).
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-25 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page is mostly 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 mentions Docker containers on Linux.
Recommendations
  • Where Windows-specific tools or executables are mentioned (e.g., 'FabricHost.exe', EXE/DLL), clarify Linux equivalents or note if they are not applicable.
  • Add explicit references to Linux service/process management where Windows services are discussed.
  • When describing code packages, mention typical Linux executable formats (e.g., ELF binaries) alongside EXE/DLL.
  • Ensure that examples and descriptions consistently mention both Windows and Linux environments, especially in sections discussing node setup and service hosting.
  • Consider reordering or balancing platform mentions so Linux is not always secondary to Windows.
GitHub Create Pull Request
Service Fabric Custom Image .../articles/service-fabric/how-to-deploy-custom-image.md
Low Priority View Details →
Scanned: 2026-02-23 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 introduction and main examples focus on custom Windows images, and the PowerShell command for role assignment is provided without a Linux CLI equivalent. However, references to Linux custom images and Azure CLI are present, and the ARM template examples are platform-neutral.
Recommendations
  • Add Azure CLI examples for role assignment alongside the PowerShell command.
  • Clarify that custom images can be Linux-based as well, and provide explicit Linux image deployment examples.
  • Ensure that Linux-specific links and instructions are as prominent as Windows ones.
  • Consider including a section or examples for deploying Linux custom images to Service Fabric Managed Clusters.
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-23 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 is a slight bias toward Windows in some sections. Windows container runtimes and IIS scenarios are described in more detail, and Windows-specific tools (Mirantis Container Runtime, DockerEE) are listed explicitly. Windows examples and tutorials are sometimes presented before Linux equivalents, and IIS lift-and-shift scenarios are highlighted, which are Windows-centric.
Recommendations
  • Ensure Linux and Windows tutorials/examples are presented with equal prominence and in parallel, rather than Windows first.
  • Expand Linux-specific scenarios (e.g., Apache, NGINX, or other Linux workloads) to match the detail given to IIS/Windows scenarios.
  • List Linux container runtimes and tools with the same specificity as Windows (e.g., mention containerd, Podman, etc., if supported).
  • Clarify when features or scenarios are Windows-only to avoid confusion.
  • Add more Linux-focused use cases and references to Linux container images and repositories.
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-23 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, in the 'Any OS, any cloud' section, Windows development is described first, and the quickstart link points to a .NET (Windows-oriented) tutorial, which may create a minor impression of Windows preference.
Recommendations
  • Add a quickstart link for Linux development alongside the Windows/.NET quickstart.
  • Alternate the order of Windows and Linux mentions in sections to avoid implicit prioritization.
  • Ensure that introductory examples and links are available for both Windows and Linux users.
GitHub Create Pull Request
Service Fabric Reliable Collection object serialization ...c-reliable-services-reliable-collections-serialization.md
Low Priority View Details →
Scanned: 2026-02-23 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation is generally platform-neutral, focusing on .NET serialization concepts relevant to Azure Service Fabric Reliable Collections. However, in the 'Next steps' section, Windows-centric tools (Visual Studio and PowerShell) are mentioned before any Linux/macOS alternatives, and no Linux/macOS upgrade tooling is referenced.
Recommendations
  • Add links or references to Linux/macOS-compatible upgrade workflows, such as using Azure CLI or Service Fabric CLI (sfctl) for application upgrades.
  • Explicitly mention cross-platform development options for Service Fabric, including .NET Core/.NET 5+ and relevant tooling.
  • Consider reordering 'Next steps' to avoid Windows-first ordering, or group upgrade tutorials by platform.
GitHub Create Pull Request
Service Fabric Describing Azure Service Fabric apps and services ...ic/service-fabric-application-and-service-manifests.md
Low Priority View Details →
Scanned: 2026-02-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page for Azure Service Fabric application and service manifests exhibits mild Windows bias. The only explicit tooling guidance is for Windows users (Visual Studio and a Windows file path for the XSD schema), and PowerShell is mentioned as the example method for creating service instances. There are no Linux/macOS-specific examples or equivalent tooling recommendations. Windows tools and patterns are referenced first and exclusively.
Recommendations
  • Add instructions for validating manifest XML schema on Linux/macOS, such as using xmllint or VS Code with XML plugins.
  • Mention cross-platform alternatives to Visual Studio for schema validation (e.g., VS Code, JetBrains Rider, or command-line tools).
  • Provide examples for creating service instances using Azure CLI or REST API, not just PowerShell.
  • Clarify which steps and tools are cross-platform, and highlight any Windows-only requirements.
  • Include Linux/macOS file paths or instructions where relevant.
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-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page provides a comprehensive reference for Service Fabric cluster settings, but exhibits mild Windows bias. Several parameters and descriptions reference Windows-specific concepts (such as certificate store names like 'MY', store locations like 'LocalMachine', NTLM authentication, and Windows Defender Firewall), and some settings default to Windows values or mention Windows-only behaviors. In a few cases, Windows terminology or tools are mentioned before Linux equivalents, and Linux-specific guidance is less prominent or missing. There are no explicit Linux examples or parity notes for settings that differ between platforms.
Recommendations
  • For parameters referencing Windows certificate stores (e.g., 'MY', 'LocalMachine'), add Linux equivalents or clarify Linux usage (e.g., file paths, openssl stores).
  • For NTLM authentication and Windows Defender Firewall settings, explicitly note Linux alternatives or limitations.
  • Where settings default differently on Windows and Linux (e.g., ContainerNetworkSetup), highlight both defaults and provide guidance for each OS.
  • Add explicit Linux/macOS examples or notes for settings that behave differently or require different configuration on non-Windows platforms.
  • Where Windows terminology is used (e.g., 'Windows Fabric Replicator'), clarify if/how it applies to Linux clusters.
  • Consider adding a section or table summarizing platform-specific behaviors for key settings.
GitHub Create Pull Request
Service Fabric Azure Service Fabric hosting activation and deactivation life cycle ...les/service-fabric/service-fabric-hosting-lifecycle.md
Low Priority View Details →
Scanned: 2026-02-23 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page on Azure Service Fabric hosting activation and deactivation life cycle is largely platform-neutral in its technical explanations, but it shows mild Windows bias in its 'Next steps' section, which links only to PowerShell-based deployment/removal instructions. Additionally, the only explicit tooling example for downloading a ServicePackage references a PowerShell cmdlet. There are no Linux-specific examples, nor are cross-platform CLI alternatives mentioned.
Recommendations
  • Add links or examples for deploying and removing applications using Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • Mention Linux/macOS-compatible tools or commands alongside PowerShell references, especially in 'Next steps' and any operational examples.
  • Clarify where PowerShell is used that equivalent functionality exists via CLI or REST APIs for non-Windows users.
  • Provide sample configuration or operational flows for Linux-based Service Fabric clusters, if applicable.
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-23 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page for Service Fabric reliable services app manifest examples shows mild Windows bias. It references Windows-specific concepts (such as 'NetworkService', 'Administrators', and '.bat' files) and mentions the ServiceFabric PowerShell module as a way to create service instances, without mentioning Linux equivalents or cross-platform CLI options. Examples and explanations often use Windows terminology and tools first, with no explicit Linux guidance or parity.
Recommendations
  • Add examples and explanations for Linux deployments, including references to Linux user/group concepts and how Service Fabric handles principals on Linux nodes.
  • Mention cross-platform tools such as Azure CLI or Service Fabric CLI (sfctl) for creating and managing services, alongside or instead of PowerShell.
  • Clarify which features and manifest elements are supported on Linux clusters, and note any differences in behavior or limitations.
  • Provide sample scripts or entry points using shell scripts (.sh) in addition to .bat files, to illustrate Linux compatibility.
  • Explicitly state when a feature or example is Windows-only, and provide Linux alternatives where possible.
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-02-22 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page for Azure Service Fabric container image management shows minor Windows bias. Windows container base images (microsoft/windowsservercore, microsoft/nanoserver) are mentioned explicitly in the configuration examples and descriptions, and the default behavior is to skip deleting these Windows images. Linux container images are referenced only in a generic example, and there are no Linux-specific examples or guidance. However, the documentation does not restrict the feature to Windows and does mention generic container image patterns.
Recommendations
  • Include explicit examples for Linux container images (e.g., Ubuntu, Alpine) in the 'ContainerImagesToSkip' setting.
  • Clarify that the cleanup and deletion features apply equally to Linux containers, and provide guidance for common Linux container scenarios.
  • Mention any differences in behavior between Windows and Linux containers, if applicable.
  • Add sample configuration for skipping Linux base images (e.g., 'docker.io/library/ubuntu:latest').
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-22 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 scenarios (such as IIS lift-and-shift) are described in greater detail, and Windows tools (Mirantis Container Runtime, DockerEE) are listed explicitly. Windows examples and links are sometimes presented before Linux equivalents, and Windows-specific scenarios (IIS, ASP.NET MVC) are highlighted. However, Linux support is clearly mentioned, and Linux tutorials are linked.
Recommendations
  • Ensure Linux and Windows examples/tutorials are presented with equal prominence and in parallel (e.g., always list Linux and Windows quickstarts together).
  • Expand Linux-specific scenarios and examples to match the detail given for Windows (e.g., highlight common Linux workloads or migration scenarios).
  • Mention Linux container runtimes/tools with the same specificity as Windows (e.g., reference containerd or other alternatives if relevant).
  • Avoid listing Windows tools or scenarios first unless there is a technical reason.
  • Add more Linux-focused use cases alongside Windows-specific ones (such as IIS).
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-22 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation presents PowerShell commands first for deploying Docker Compose files on Azure Service Fabric, followed by cross-platform Service Fabric CLI (sfctl) examples. The PowerShell section is more detailed, with multiple commands for deployment, status, upgrade, and rollback. While the CLI section covers equivalent functionality, the ordering and depth of PowerShell examples suggest a Windows-first bias. However, Linux/macOS users can complete all tasks using sfctl, and no critical functionality is missing for non-Windows users.
Recommendations
  • Present Service Fabric CLI (sfctl) examples before PowerShell, or in parallel, to emphasize cross-platform support.
  • Ensure that CLI examples are as detailed as PowerShell examples, covering all operations (deployment, status, upgrade, rollback, etc.).
  • Explicitly state that sfctl is supported on Linux/macOS and provide installation instructions or links for those platforms.
  • Add a note clarifying that all tasks can be performed on Linux/macOS using sfctl, to reassure non-Windows users.
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-22 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page exhibits a mild Windows bias. The only explicit file path for the Service Fabric schema is given as a Windows path (C:\Program Files\Microsoft SDKs\Service Fabric\schemas\...), and there is no mention of Linux or cross-platform equivalents. The structure and terminology (e.g., .exe files) also implicitly assume a Windows environment, and Visual Studio is mentioned as a primary tool, which is most commonly used on Windows. However, the content does not explicitly exclude Linux, and some examples reference Node.js and Java, which are cross-platform.
Recommendations
  • Provide Linux-equivalent file paths or clarify where schema files are located on Linux installations.
  • Include explicit mention or examples of packaging non-Windows executables (e.g., ELF binaries) to reinforce cross-platform support.
  • Mention cross-platform tools (such as Visual Studio Code or CLI alternatives) alongside Visual Studio.
  • Clarify any platform-specific limitations or requirements for Service Fabric guest executables.
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-22 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, and provides parity in describing development environments for each OS. However, in the 'Any OS, any cloud' section, Windows development is described first, with Visual Studio and PowerShell highlighted before Linux development tools (Eclipse, Yeoman). The quickstart link also points to a .NET (likely Windows-oriented) guide, rather than a Linux or cross-platform example.
Recommendations
  • Alternate the order of Windows and Linux mentions to avoid implicit prioritization.
  • Provide quickstart links for both Windows (.NET) and Linux (Java/.NET Core) users.
  • Ensure that examples and tooling references for Linux are as prominent and detailed as those for Windows.
  • Consider linking to cross-platform guides or explicitly noting parity where it exists.
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-22 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page primarily describes Service Fabric concepts and terminology, but there are several instances where Windows-specific tools and patterns are mentioned before their Linux equivalents. For example, the description of nodes references an 'auto-start Windows service, FabricHost.exe' and Windows executables (EXE/DLL) without mentioning Linux equivalents or patterns. Windows Server containers are mentioned before Docker containers on Linux. However, the page does acknowledge Linux support and provides some parity in container and guest executable descriptions.
Recommendations
  • When describing node startup, clarify how Service Fabric operates on Linux nodes (e.g., which processes/services are used, if any).
  • When referencing executable formats, mention Linux equivalents (e.g., ELF binaries) alongside EXE/DLL.
  • Present Windows and Linux container support together, or mention Linux first where appropriate.
  • Add explicit examples or clarifications for Linux environments where Windows-specific terminology is used.
  • Ensure that descriptions of tools and processes are platform-neutral unless the feature is Windows-only.
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-21 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page for 'Architecture of Azure Service Fabric' exhibits mild Windows bias. The management subsystem section explicitly mentions PowerShell cmdlets as a primary means of managing Service Fabric, without referencing Linux/macOS equivalents (such as CLI tools or REST APIs). Additionally, Windows security is mentioned alongside X509 certificates in the transport subsystem, but Linux authentication mechanisms are not discussed. The overall architectural description is platform-neutral, but administrative tooling is presented with a Windows-first perspective.
Recommendations
  • Mention cross-platform management tools (such as Azure CLI, REST APIs, or Service Fabric CLI) alongside PowerShell cmdlets.
  • Clarify if PowerShell cmdlets are available on Linux/macOS via PowerShell Core, or provide alternative instructions for Linux users.
  • Discuss Linux authentication mechanisms (such as certificate-based authentication) in the transport subsystem, or clarify platform support.
  • Add explicit notes or links to Linux/macOS documentation for managing Service Fabric clusters.
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-21 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 in the order and emphasis: Windows container runtimes and tools (Mirantis Container Runtime, DockerEE) are listed in detail, while Linux only mentions Docker. Windows scenarios (such as IIS lift-and-shift) are described first in the 'Scenarios for using containers' section, and Windows-specific links are often shown before Linux equivalents. There are no missing Linux examples, and Linux support is clearly documented.
Recommendations
  • List Linux container runtimes and tools with equal detail as Windows (e.g., mention containerd, Podman if relevant).
  • Present Linux and Windows examples in parallel or alternate order to avoid 'Windows first' bias.
  • Add more Linux-specific scenarios (e.g., Apache, NGINX, Python workloads) alongside Windows/IIS examples.
  • Ensure that Linux tutorials and links are given equal prominence in 'Next steps' and throughout the page.
GitHub Create Pull Request
Service Fabric Deny assignment policy for Service Fabric managed clusters ...cles/service-fabric/managed-cluster-deny-assignment.md
Low Priority View Details →
Scanned: 2026-02-21 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides best practice examples and links primarily using Azure PowerShell modules, with PowerShell mentioned before Azure CLI and sfctl. While Azure PowerShell is cross-platform, its prominence and the lack of explicit Linux/macOS command examples may create friction for non-Windows users. The page does mention Azure CLI and sfctl, but PowerShell is referenced first and most often.
Recommendations
  • Add explicit Azure CLI examples for key operations (e.g., deleting NodeTypes, restarting/reimaging scale sets) alongside PowerShell examples.
  • Ensure that CLI and sfctl commands are shown before or equally with PowerShell in best practice sections.
  • Clarify that Azure PowerShell and Azure CLI are both cross-platform, and provide guidance for Linux/macOS users.
  • Where possible, include sample commands for sfctl (which is Python-based and Linux-friendly) for relevant tasks.
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-21 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 commands are presented first and in greater detail, with explicit command blocks for each operation. The CLI section is presented second, and while it covers the same operations, it is less emphasized. There is no mention of Linux-specific tools or patterns, but the inclusion of sfctl commands does provide Linux/macOS parity. No Linux-specific example or guidance is given, and PowerShell is a Windows-centric tool.
Recommendations
  • Present CLI (sfctl) examples before PowerShell, or at least equally, to avoid Windows-first bias.
  • Explicitly mention that sfctl is cross-platform and suitable for Linux/macOS users.
  • Add a brief note or section for Linux/macOS users, clarifying that PowerShell commands are Windows-specific and that sfctl is the recommended tool for non-Windows environments.
  • Consider including example shell commands for Linux/macOS where relevant (e.g., using Bash).
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-21 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, in the 'Any OS, any cloud' section, Windows development (with Visual Studio and PowerShell) is described first, followed by Linux development (with Eclipse and Yeoman). The quickstart link also points to a .NET-based tutorial, which may be more Windows-centric, though .NET Core is cross-platform.
Recommendations
  • Alternate the order of Windows and Linux mentions to avoid implicit prioritization.
  • Provide quickstart links for both Windows (.NET) and Linux (Java/.NET Core) users.
  • Explicitly state that .NET Core examples are cross-platform when referenced.
  • Ensure that Linux tooling (Eclipse, Yeoman) is given equal prominence and example coverage as Windows tooling (Visual Studio, PowerShell).
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-21 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page is generally cross-platform and describes Service Fabric concepts applicable to both Windows and Linux. However, there is a mild Windows bias in the 'Infrastructure concepts' section, where Windows-specific tools (FabricHost.exe, Fabric.exe, FabricGateway.exe) are mentioned as auto-start Windows services, without clarifying Linux equivalents or behaviors. Additionally, Windows terminology (EXE/DLL) is used in the 'Code package' section before mentioning Linux guest executables. The order of examples and explanations tends to reference Windows first, with Linux support noted later.
Recommendations
  • Clarify that FabricHost.exe, Fabric.exe, and FabricGateway.exe are also present on Linux nodes, and describe their startup mechanisms on Linux (e.g., systemd services) if applicable.
  • When mentioning executable formats (EXE/DLL), add Linux equivalents (e.g., ELF binaries, .so files) to ensure parity.
  • Where Windows services or tools are referenced, add a brief note about Linux equivalents or behaviors.
  • Consider alternating the order of Windows and Linux examples or explicitly stating cross-platform support where relevant.
GitHub Create Pull Request
Service Fabric Reliable Collection object serialization ...c-reliable-services-reliable-collections-serialization.md
Low Priority View Details →
Scanned: 2026-02-21 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation is generally platform-neutral, focusing on .NET serialization concepts relevant to Azure Service Fabric. However, in the 'Next steps' section, Windows-centric tools (Visual Studio and PowerShell) are mentioned for application upgrades, with no Linux/macOS alternatives or parity. PowerShell is referenced as a primary upgrade method, and Visual Studio is listed before any CLI or cross-platform options.
Recommendations
  • Add references to cross-platform upgrade methods, such as Azure CLI or Service Fabric CLI (sfctl), especially for Linux/macOS users.
  • Include links or examples for upgrading applications on Linux/macOS, or clarify if PowerShell/Visual Studio are Windows-only and provide alternatives.
  • Consider listing cross-platform tools before Windows-specific ones, or grouping them by platform for clarity.
GitHub Create Pull Request
← Previous Page 94 of 99 Next →