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 2401-2425 of 2475 flagged pages
Service Fabric
Reliable Collection object serialization
...c-reliable-services-reliable-collections-serialization.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation is generally platform-neutral, focusing on .NET and Azure Service Fabric concepts. However, in the 'Next steps' section, Windows-centric upgrade tutorials (Visual Studio and PowerShell) are listed before any mention of Linux or cross-platform alternatives. No Linux/macOS-specific examples or tools are referenced, and there are no explicit Linux instructions or parity notes.
Recommendations
- Add links or references to Linux/macOS-compatible upgrade workflows, such as using Azure CLI or REST APIs.
- Include examples or notes for developers using .NET Core/.NET 5+ on Linux/macOS, clarifying any platform-specific considerations.
- If PowerShell is mentioned, also mention Bash or other scripting alternatives for Linux/macOS users.
- Consider reordering 'Next steps' to avoid Windows-first ordering, or explicitly state cross-platform options.
Create Pull Request
Service Fabric
Learn Azure Service Fabric terminology
...es/service-fabric/service-fabric-technical-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page is generally platform-neutral, describing Service Fabric concepts applicable to both Windows and Linux. However, there are subtle signs of Windows bias: Windows-specific tools and executables (e.g., FabricHost.exe, Fabric.exe, FabricGateway.exe) are mentioned first and in detail, with less explicit coverage of Linux equivalents. The description of node startup references an 'auto-start Windows service' without clarifying Linux behavior. Executable file types are described as EXE/DLL, which are Windows-centric, and Windows containers are mentioned before Linux containers in some sections.
Recommendations
- Clarify Linux node startup behavior alongside Windows (e.g., what processes/services are used on Linux nodes).
- When describing executable file types, mention Linux equivalents (e.g., ELF binaries, .so files) in addition to EXE/DLL.
- Where Windows-specific tools or services are referenced, add notes or links about Linux equivalents or differences.
- Ensure container support is described with Linux and Windows parity, mentioning Docker containers on Linux before or alongside Windows containers.
- Review ordering of examples and terminology to avoid always listing Windows first.
Service Fabric
Overview of Service Fabric and containers
...s/service-fabric/service-fabric-containers-overview.md
Low Priority
View Details →
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 tendency to mention Windows-specific tools (like Mirantis Container Runtime and DockerEE) and Windows scenarios (such as IIS lift-and-shift) before or more prominently than Linux equivalents. Windows examples and tutorials are listed alongside Linux ones, but Windows scenarios (like IIS) are described in more detail.
Recommendations
- Ensure Linux scenarios (such as Apache/Nginx lift-and-shift or Linux-specific app migrations) are described with equal detail as Windows scenarios.
- Mention Linux container runtimes and tools (such as containerd or Podman) if relevant, not just Docker.
- Provide Linux-first examples in some sections, or alternate the order between Linux and Windows.
- Expand on Linux-specific use cases and container orchestration patterns within Service Fabric.
Service Fabric
Overview of Azure Service Fabric
...ain/articles/service-fabric/service-fabric-overview.md
Low Priority
View Details →
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 options. However, in the 'Any OS, any cloud' section, Windows development (with .NET SDK, Visual Studio, PowerShell) is described before Linux development (with Java SDK, Eclipse, Yeoman), and the quickstart link points to a .NET (Windows-centric) guide. No Linux-specific quickstart or example is linked, and Windows tools are mentioned first.
Recommendations
- Add a quickstart link for Linux development (e.g., a Java or .NET Core example on Linux).
- Present Windows and Linux development options in parallel, rather than Windows first.
- Ensure that both Windows and Linux tooling (e.g., PowerShell vs. Bash, Visual Studio vs. Eclipse) are described with equal prominence.
- Link to Linux-specific documentation (such as service-fabric-quickstart-java.md or service-fabric-quickstart-linux.md) alongside Windows quickstarts.
Service Fabric
Azure Service Fabric Docker Compose Deployment Preview
...ticles/service-fabric/service-fabric-docker-compose.md
Low Priority
View Details →
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, the PowerShell (Windows-centric) instructions are presented first and in greater detail, with more explanation and command breakdowns. The CLI (sfctl) section is present and functional for Linux/macOS users, but is introduced as an 'alternative' rather than a co-equal path. There are no Linux/macOS-specific caveats or examples, but the ordering and emphasis slightly favor Windows users.
Recommendations
- Present PowerShell and sfctl (CLI) instructions in parallel or with equal prominence, possibly using tabs or side-by-side sections labeled 'Windows (PowerShell)' and 'Cross-platform (sfctl)'.
- Explicitly state that sfctl works on Linux/macOS and provide installation links or prerequisites for non-Windows users.
- Ensure that all command examples and explanations are equally detailed for both PowerShell and sfctl.
- Consider including a short section or note confirming that Service Fabric Compose deployment is supported on both Windows and Linux clusters (if true), or clarify any platform limitations.
Service Fabric
Azure Service Fabric hosting activation and deactivation life cycle
...les/service-fabric/service-fabric-hosting-lifecycle.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page is generally platform-neutral in its explanations of Service Fabric activation and deactivation lifecycle. However, the 'Next steps' section and one example reference PowerShell and a PowerShell module for downloading ServicePackages, suggesting Windows-centric tooling and workflows. There are no explicit Linux/bash examples or references to Linux-native tools, and PowerShell is mentioned as the deployment/removal method without alternatives.
Recommendations
- Add Linux/bash examples or references alongside PowerShell for deployment/removal tasks.
- Mention cross-platform tools (such as Azure CLI or REST API) where applicable, and provide links or examples.
- Clarify if PowerShell examples are cross-platform (PowerShell Core) or Windows-only, and provide Linux/macOS equivalents if available.
- Reference Linux-specific documentation or workflows for Service Fabric where possible.
Service Fabric
Service communication with the ASP.NET Core
...vice-fabric-reliable-services-communication-aspnetcore.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation provides comprehensive guidance for integrating ASP.NET Core with Azure Service Fabric Reliable Services, covering both Kestrel (cross-platform) and HTTP.sys (Windows-only) web servers. While Kestrel is recommended and well-documented for cross-platform (Windows and Linux) scenarios, HTTP.sys is discussed in detail with explicit notes about its Windows-only nature. In some sections, Windows-specific tools and patterns (e.g., HTTP.sys, netsh, Windows HTTP Server API) are mentioned before or in more detail than their Linux equivalents, but Linux parity is generally maintained through Kestrel guidance.
Recommendations
- Continue to clearly indicate when features are Windows-only (as is done with HTTP.sys).
- Where Windows-specific tools like netsh are referenced, briefly note that they are not applicable on Linux and that Kestrel is the cross-platform alternative.
- Consider adding a short section or callout early in the article explicitly stating that Kestrel is the recommended and supported option for Linux deployments, and that HTTP.sys is only for Windows.
- In code and configuration examples, ensure that Kestrel (cross-platform) examples are shown first or given equal prominence to avoid the perception of Windows-first bias.
- If possible, add a troubleshooting or FAQ section addressing common Linux deployment questions.
Service Fabric
Learn Azure Service Fabric terminology
...es/service-fabric/service-fabric-technical-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation is generally cross-platform and describes Service Fabric concepts in an OS-agnostic way. However, there are minor instances of Windows bias: Windows terminology and tools (such as 'Windows service', 'FabricHost.exe', and references to EXE/DLL files) are mentioned first or exclusively in some definitions, even though Linux is supported. The description of nodes focuses on Windows services and executables, and the code package section refers to EXE/DLL files, which are Windows-centric. Linux is mentioned in the context of containers and guest executables, but not always with equal prominence.
Recommendations
- When describing node startup, clarify the equivalent Linux processes or daemons, or note that on Linux, Service Fabric uses systemd or other init systems.
- In the 'Code package' section, mention that on Linux, code packages may include ELF binaries or scripts, not just EXE/DLL files.
- Where Windows executables or services are referenced, add a note or parallel description for Linux (e.g., 'On Linux, Service Fabric runs as systemd services and uses equivalent binaries').
- Ensure that examples and terminology are balanced, mentioning both Windows and Linux where relevant, especially in introductory or conceptual sections.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page for Service Fabric Reliable Services app manifest examples demonstrates a mild Windows bias. Windows-specific concepts (such as running scripts via .bat files, references to NETWORKSERVICE, and mentions of ServiceFabric PowerShell module) are present. Examples and explanations often use Windows terminology and tools (e.g., Setup.bat, VotingWeb.exe), and the PowerShell module is referenced as the default for service creation. There is no explicit mention of Linux equivalents (such as shell scripts or Linux user accounts), nor are Linux-specific patterns or examples provided.
Recommendations
- Add examples using Linux-compatible scripts (e.g., .sh files) alongside .bat examples.
- Clarify that Service Fabric supports Linux and provide guidance for Linux user account configuration and script execution.
- Mention Linux tools or CLI alternatives to the ServiceFabric PowerShell module for service creation.
- Where user accounts or system groups are referenced, note Linux equivalents (e.g., systemd users, sudo group).
- Ensure terminology is cross-platform or clarify Windows-specific terms when used.
Service Fabric
Reliable Collection object serialization
...c-reliable-services-reliable-collections-serialization.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides .NET/C# code examples and references Visual Studio and PowerShell in the 'Next steps' section. While the main content is platform-neutral (focused on .NET Core/Service Fabric Reliable Collections), the order of 'Next steps' links places Windows-centric tools (Visual Studio, PowerShell) before any mention of cross-platform or Linux alternatives. No Linux/macOS-specific examples or guidance are provided.
Recommendations
- Add explicit mention of cross-platform development with .NET Core/.NET 5+ and Service Fabric, clarifying Linux/macOS support.
- Include examples or links for upgrading applications using CLI tools (e.g., Azure CLI, Service Fabric CLI) that work on Linux/macOS.
- Balance the order of 'Next steps' so Linux/macOS-friendly options (CLI, VS Code) are not always listed after Windows tools.
- If relevant, provide sample code or instructions for serialization in environments other than Windows (e.g., running Service Fabric on Linux).
Service Fabric
Overview of Azure Service Fabric
...ain/articles/service-fabric/service-fabric-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions both Windows and Linux support for Service Fabric, but Windows development tools (Visual Studio, PowerShell) are listed before Linux equivalents (Eclipse, Yeoman). There are no exclusive Windows examples or tools, and Linux parity is generally acknowledged.
Recommendations
- Present Windows and Linux development options in parallel, rather than listing Windows first.
- Add links to Linux quickstarts and documentation alongside Windows quickstarts.
- Ensure that example workflows and tool references are balanced between Windows and Linux.
- Consider linking to the Linux development guide in the 'Next steps' section.
Service Fabric
Overview of Service Fabric and containers
...s/service-fabric/service-fabric-containers-overview.md
Low Priority
View Details →
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 some sections where Windows-specific tools (IIS, Mirantis Container Runtime) and Windows scenarios (IIS lift and shift) are mentioned before or more prominently than Linux equivalents. Windows container runtimes are listed in detail, while Linux only mentions Docker. Windows scenarios (IIS lift and shift) are described in depth, while Linux scenarios are less emphasized.
Recommendations
- Add more Linux-specific scenarios (e.g., Apache/Nginx lift and shift, common Linux workloads) alongside Windows scenarios.
- Provide parity in listing container runtimes for Linux (e.g., mention containerd, Podman if supported) as is done for Windows.
- Ensure Linux examples and tutorials are referenced equally and not only after Windows examples.
- Clarify when features or scenarios are Windows-only to avoid confusion.
- Consider alternating the order of Linux and Windows examples to avoid 'windows_first' bias.
Service Fabric
Azure Service Fabric Docker Compose Deployment Preview
...ticles/service-fabric/service-fabric-docker-compose.md
Low Priority
View Details →
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 give the impression of a Windows-first bias. The CLI examples are present and sufficient for Linux/macOS users, but the ordering and emphasis favor Windows/PowerShell.
Recommendations
- Present cross-platform CLI (sfctl) examples before PowerShell examples to emphasize Linux/macOS parity.
- Explicitly note that sfctl works on all platforms and is recommended for non-Windows users.
- Balance the level of detail and explanation between PowerShell and CLI sections.
- Consider adding a short note at the top of the deployment section clarifying that both Windows (PowerShell) and cross-platform (sfctl) options are available.
Service Fabric
Azure Service Fabric container image management
.../articles/service-fabric/container-image-management.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
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 as default exclusions, and no Linux container image examples or references are provided. The configuration examples and descriptions focus on Windows images and do not demonstrate parity for Linux-based containers, nor do they clarify whether the cleanup features apply equally to Linux containers.
Recommendations
- Add examples and references to Linux container images (e.g., 'docker.io/library/alpine', 'ubuntu') in configuration and explanations.
- Clarify whether the image cleanup features apply to both Windows and Linux containers, and note any differences.
- Include sample settings or scenarios for Linux container images in the 'ContainerImagesToSkip' parameter.
- Explicitly mention Linux support in the introductory and settings sections if applicable.
Service Fabric
Architecture of Azure Service Fabric
...articles/service-fabric/service-fabric-architecture.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page describes the architecture of Azure Service Fabric in a platform-neutral manner, but the Management subsystem section specifically mentions PowerShell cmdlets as a primary management interface, without referencing Linux/macOS equivalents (such as Azure CLI or REST APIs). Windows security is also mentioned alongside X509 certificates in the Transport subsystem, but not Linux authentication mechanisms. These examples and tool references are presented before any cross-platform alternatives, creating a mild Windows bias.
Recommendations
- Mention Azure CLI and REST API as cross-platform management options alongside PowerShell cmdlets.
- Clarify that Service Fabric management can be performed from Linux/macOS using CLI or API tools.
- When discussing security, explicitly note that X509 certificates are supported on all platforms, and clarify Windows security is an additional option for Windows environments.
- Provide links or references to Linux/macOS management documentation or examples.
Service Fabric
Change Azure Service Fabric cluster settings
...rvice-fabric/service-fabric-cluster-fabric-settings.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page presents Service Fabric cluster settings in a platform-neutral way, but there are subtle signs of Windows bias. Windows terminology (e.g., 'MY' certificate store, 'LocalMachine' store location, NTLM authentication) is used throughout, and Windows-specific defaults are sometimes mentioned before Linux equivalents. Some parameters reference Windows tools or concepts (e.g., certificate store names, NTLM, Windows Defender Firewall) without always clarifying Linux alternatives or differences. However, Linux-specific settings are present, and the page is not exclusively Windows-focused.
Recommendations
- Where Windows-specific terms (e.g., 'MY', 'LocalMachine', NTLM') are used, clarify Linux equivalents or note differences.
- Add explicit Linux/macOS guidance for certificate management, authentication, and firewall configuration where Windows tools are referenced.
- When listing parameters with platform-specific defaults, present Linux and Windows values equally (e.g., 'default is FALSE (Linux) and TRUE (Windows)').
- Link to Linux-specific documentation or examples for relevant settings.
- Review guidance for any implicit Windows assumptions and ensure Linux parity in explanations.
Service Fabric
Reliable Collection object serialization
...c-reliable-services-reliable-collections-serialization.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
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 upgrade tutorials (Visual Studio and PowerShell) are mentioned before any Linux or cross-platform alternatives. PowerShell is a Windows-first tool, and no Linux CLI or cross-platform upgrade guidance is referenced.
Recommendations
- Add links or references to Linux/macOS upgrade workflows, such as using Azure CLI or Service Fabric CLI (sfctl).
- Explicitly mention cross-platform tools and approaches for application upgrades, ensuring parity with Windows examples.
- Reorder 'Next steps' to avoid listing Windows tools first, or group platform-specific guidance together.
- Clarify that PowerShell and Visual Studio are Windows-centric, and provide alternatives for Linux/macOS users.
Service Fabric
Learn Azure Service Fabric terminology
...es/service-fabric/service-fabric-technical-overview.md
Low Priority
View Details →
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 are subtle signs of Windows bias: Windows-specific tools and patterns (such as references to Windows services and EXE/DLL files) are mentioned first or exclusively in some sections, and Windows terminology is used before Linux equivalents. Linux support is acknowledged, but Windows is often the default or primary context.
Recommendations
- When describing node infrastructure, clarify that Linux nodes use different service management mechanisms (e.g., systemd) instead of Windows services, and mention relevant Linux processes/tools.
- When referencing executable files, note that Linux uses ELF binaries and not EXE/DLL files, and provide examples or terminology for Linux equivalents.
- In sections referencing auto-start Windows services (e.g., FabricHost.exe), add a note about how this works on Linux (e.g., systemd units, service scripts).
- Ensure that examples and descriptions are equally balanced between Windows and Linux, or explicitly state differences where relevant.
- Consider providing Linux-first or Linux-parallel examples where possible, especially in technical sections.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page is generally cross-platform, referencing both Windows and Linux custom images and linking to Linux image creation tutorials. However, the narrative and examples are Windows-centric: 'Custom windows images' are discussed first and most prominently, and the only CLI example provided is in PowerShell, with no equivalent Linux/bash example. Windows terminology and tools are mentioned before Linux equivalents, creating a subtle Windows-first bias.
Recommendations
- Add explicit Linux/bash CLI examples alongside PowerShell for role assignment and image management.
- Clarify that custom images can be Linux-based and provide examples or links for Linux-specific workflows.
- Balance the narrative to mention Linux and Windows images equally, avoiding Windows-first phrasing.
- Include references to Linux tools and commands (e.g., Azure CLI bash usage) where relevant.
Service Fabric
Overview of Service Fabric and containers
...s/service-fabric/service-fabric-containers-overview.md
Low Priority
View Details →
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 listed in detail, and Windows scenarios (such as IIS lift-and-shift) are described before Linux equivalents. Windows tutorials and references are often placed before Linux ones, and Windows-specific tools (Mirantis Container Runtime, DockerEE) are mentioned, while Linux only lists Docker. However, Linux support is clearly acknowledged, and Linux tutorials are linked.
Recommendations
- Ensure Linux and Windows examples/tutorials are presented in parallel or alternate order to avoid 'windows_first' bias.
- Expand Linux-specific scenarios (e.g., NGINX, Apache) to match the detail given to Windows/IIS scenarios.
- List Linux container runtimes and tools with equal detail as Windows (e.g., mention containerd, Podman if supported).
- Provide explicit Linux command-line examples or references where Windows tools are mentioned.
- Clarify parity and limitations for Linux vs Windows containers in Service Fabric, if any.
Service Fabric
Azure Service Fabric container image management
.../articles/service-fabric/container-image-management.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
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 exclusively in the 'ContainerImagesToSkip' setting, and the default behavior is to not delete these Windows images. No Linux container base images (such as Ubuntu, Alpine, or other common Linux distributions) are mentioned, nor are Linux-specific examples provided. The examples and descriptions focus on Windows images first, and there is no guidance for Linux container image management or parity.
Recommendations
- Add examples and references for common Linux container base images (e.g., 'docker.io/library/alpine', 'ubuntu', etc.) in the 'ContainerImagesToSkip' setting.
- Clarify whether the cleanup and deletion features apply equally to Linux containers and images, and provide explicit guidance for Linux-based Service Fabric clusters.
- Include a note or section on Linux container image management, including any differences or considerations for Linux VMs in Service Fabric clusters.
- Ensure that examples and descriptions are balanced between Windows and Linux container scenarios.
Service Fabric
Architecture of Azure Service Fabric
...articles/service-fabric/service-fabric-architecture.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation references PowerShell cmdlets as a primary management interface in the Management subsystem section, suggesting a Windows-centric approach. No Linux or cross-platform CLI tools (such as Azure CLI or Bash) are mentioned, and Windows security is referenced before X509 certificates in the Transport subsystem. These patterns indicate a mild Windows bias, though the overall architectural description is platform-neutral.
Recommendations
- Mention and provide examples of cross-platform management tools, such as Azure CLI or REST APIs, alongside PowerShell cmdlets.
- Clarify that Service Fabric management can be performed from Linux/macOS using Azure CLI or other APIs.
- Reference Linux-compatible security mechanisms (e.g., X509 certificates) before or alongside Windows security in the Transport subsystem.
- Add links or notes about Linux/macOS support for Service Fabric where relevant.
Service Fabric
Azure Service Fabric Docker Compose Deployment Preview
...ticles/service-fabric/service-fabric-docker-compose.md
Low Priority
View Details →
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 examples are presented first and in greater detail, which may imply a Windows-centric workflow. The CLI examples are present and suitable for Linux/macOS users, but the prominence and depth of PowerShell instructions suggest a Windows-first bias.
Recommendations
- Present CLI (sfctl) examples before or alongside PowerShell examples to signal equal support for Linux/macOS users.
- Expand CLI example explanations to match the detail given to PowerShell commands.
- Explicitly state that sfctl is cross-platform and suitable for Linux/macOS environments.
- Add a short section clarifying that all deployment tasks can be completed on Linux/macOS using sfctl, and PowerShell is optional for Windows users.
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 →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page provides Service Fabric application and service manifest examples, but exhibits mild Windows bias. It references Windows concepts (e.g., 'NetworkService', 'Administrators' group, 'Setup.bat', '.exe' files) and mentions using the ServiceFabric PowerShell module to create service instances. There are no explicit Linux or cross-platform examples (e.g., shell scripts, Linux user/group patterns), and Windows-specific tools and terminology are used throughout. However, the manifest XML itself is platform-neutral, and Service Fabric supports Linux, so Linux users can adapt the examples with some effort.
Recommendations
- Add Linux-specific examples, such as using shell scripts (.sh) for SetupEntryPoint and EntryPoint, and referencing Linux user/group equivalents.
- Mention Linux-compatible tools for managing Service Fabric applications (e.g., Azure CLI, sfctl) alongside or before PowerShell.
- Clarify which concepts (e.g., user accounts, system groups) map to Linux equivalents, and provide guidance for Linux deployments.
- Ensure examples and explanations are platform-neutral where possible, or provide parallel examples for both Windows and Linux.
Service Fabric
Overview of Azure Service Fabric
...ain/articles/service-fabric/service-fabric-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions both Windows and Linux support for Service Fabric, and provides parity in describing development environments and cluster deployment. However, in the 'Any OS, any cloud' section, Windows development is described first, with Visual Studio and PowerShell highlighted, while Linux development is described second. The quickstart link also points to a .NET (likely Windows-focused) guide, rather than a Linux or cross-platform example.
Recommendations
- Present Windows and Linux development environments in parallel or alternate the order to avoid Windows-first bias.
- Include quickstart links for both Windows (.NET) and Linux (Java/.NET Core) development, or a cross-platform quickstart.
- Explicitly mention cross-platform tooling and provide links to Linux/macOS guides alongside Windows guides.
- Highlight that Service Fabric supports containerized workloads in any language, and provide example links for Linux scenarios.