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 2351-2375 of 2475 flagged pages
Service Fabric Application upgrade: data serialization ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-application-upgrade-data-serialization.md
Low Priority View Details →
Scanned: 2026-02-20 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates mild Windows bias. It references Visual Studio and PowerShell as primary upgrade tools, both of which are Windows-centric. The 'Next steps' section lists Visual Studio (Windows-only) and PowerShell (Windows-first) tutorials for application upgrades, without mentioning Linux/macOS alternatives or CLI-based approaches. The serialization discussion is focused on C# and .NET, but this is appropriate for Service Fabric workloads and not inherently Windows-biased.
Recommendations
  • Add guidance or links for upgrading Service Fabric applications using cross-platform tools such as Azure CLI or REST APIs.
  • Include examples or tutorials for Linux/macOS users, highlighting how to perform upgrades without Visual Studio or PowerShell.
  • Clarify which steps are Windows-only and provide parity for Linux/macOS where possible.
  • Mention any limitations or differences for Linux/macOS users in the upgrade process.
GitHub Create Pull Request
Service Fabric Reliable Collection object serialization ...c-reliable-services-reliable-collections-serialization.md
Low Priority View Details →
Scanned: 2026-02-20 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides code examples exclusively in C#, which is cross-platform, but references to upgrade tutorials prioritize Visual Studio (a Windows-centric tool) before PowerShell. There are no explicit Linux/macOS examples or mentions of Linux-specific tools, but the content is generally applicable to all platforms where Service Fabric and .NET Core/.NET 5+ are supported.
Recommendations
  • Add explicit notes clarifying that the serialization APIs and patterns work on both Windows and Linux Service Fabric clusters.
  • Provide links or references to Linux/macOS-compatible tools for application upgrades (e.g., Azure CLI or bash scripts), if available.
  • Balance the order of 'Next steps' links by mentioning cross-platform options (such as Azure CLI) before or alongside Windows-specific tools like Visual Studio and PowerShell.
  • Include a brief section or note on any platform-specific considerations for serialization if they exist.
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-20 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page provides a comprehensive reference for Service Fabric cluster settings, but exhibits mild Windows bias. Windows terminology (e.g., certificate store names like 'MY', 'LocalMachine', NTLM authentication, Windows Defender Firewall) is used throughout, and Windows-specific defaults are often mentioned before Linux equivalents. Some settings reference Windows-only behaviors or tools, and links to standalone cluster configuration upgrades point to Windows Server documentation without Linux parity. Linux-specific settings are present (e.g., 'LinuxExternalExecutablePath', 'EnforceLinuxMinTlsVersion'), but Linux guidance is less prominent and sometimes missing.
Recommendations
  • Add explicit Linux equivalents for certificate store names and authentication mechanisms, clarifying differences in guidance tables.
  • Provide links and examples for Linux standalone cluster configuration upgrades, not just Windows Server.
  • Where Windows tools or terminology are used (e.g., NTLM, Windows Defender Firewall), add notes or alternatives for Linux users.
  • Ensure Linux-specific settings are documented with equal detail and visibility as Windows settings.
  • Consider reordering sections or tables to avoid always listing Windows defaults first.
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-20 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 in the ordering and emphasis: Windows container runtimes and tools (Mirantis Container Runtime, DockerEE) are listed in detail, while Linux only mentions Docker. Windows scenarios (IIS lift and shift) and links to Windows container tutorials are presented before or alongside Linux equivalents, sometimes with more detail. However, Linux support and examples are present and referenced throughout.
Recommendations
  • Expand the Linux container runtime section to mention alternative runtimes if applicable (e.g., containerd, Podman), not just Docker.
  • Ensure Linux examples and tutorials are given equal prominence and detail as Windows examples.
  • When listing container runtimes, present Linux and Windows options in parallel rather than Windows-first.
  • Add more Linux-specific scenarios or highlight cross-platform scenarios equally.
  • Review the ordering of links and sections to avoid Windows-first presentation.
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-20 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 examples are presented first and in greater detail, which may suggest a Windows-first bias. PowerShell is primarily a Windows tool (though available cross-platform, it's most common on Windows), and its prominence may create friction for Linux/macOS users. The CLI (sfctl) examples are provided and are cross-platform, mitigating the bias somewhat.
Recommendations
  • Present the cross-platform Service Fabric CLI (sfctl) examples before the PowerShell examples to avoid a Windows-first impression.
  • Explicitly mention that sfctl is supported on Linux/macOS and is the recommended tool for non-Windows users.
  • Clarify that PowerShell Core is available cross-platform if PowerShell examples are retained, or provide Bash equivalents where possible.
  • Add a short section or note for Linux/macOS users, confirming that all deployment steps are supported via sfctl.
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-20 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation acknowledges both Windows and Linux support for Azure Service Fabric, and provides references to Linux-specific development resources. However, Windows development is mentioned first, and the quickstart link points to a .NET/Windows-focused guide, which may create a perception of Windows preference. No critical Linux examples or tools are missing, but Windows is presented before Linux in several sections.
Recommendations
  • Alternate the order of Windows and Linux mentions to avoid Windows-first bias.
  • Provide quickstart links for both Windows (.NET) and Linux (Java/.NET Core) side by side.
  • Explicitly highlight parity in tooling and development experience for Linux users.
  • Ensure that Linux-specific quickstart and development guides are as prominent as Windows ones.
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-20 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 (e.g., 'auto-start Windows service', 'EXE/DLL files', 'Windows Server containers') is mentioned first or exclusively in several sections, and Windows tools/processes (such as FabricHost.exe) are referenced without clear Linux equivalents or explanations. However, Linux support is acknowledged in some places, and the page does mention Docker containers on Linux and guest executables running on both platforms.
Recommendations
  • Clarify when references to Windows-specific processes (e.g., FabricHost.exe, EXE/DLL files) are also applicable to Linux, or provide Linux equivalents (such as referencing .so files or Linux service management).
  • When describing node startup and service hosting, explicitly mention Linux service/process equivalents if they exist.
  • Ensure that container support is described equally for Windows and Linux, and avoid listing Windows containers first unless contextually appropriate.
  • Where possible, provide examples or terminology relevant to Linux (e.g., referencing Linux file types, service management, or process orchestration).
  • Review sections for implicit Windows-first ordering and adjust to be platform-neutral or alternate ordering.
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-19 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page for Azure Service Fabric container image management exhibits minor Windows bias. Windows container base images (microsoft/windowsservercore, microsoft/nanoserver) are mentioned explicitly and prioritized as default exclusions from cleanup. No Linux container base images (such as Ubuntu, Alpine, etc.) are referenced in the default settings or examples. Additionally, there are no explicit examples or guidance for Linux container image management, nor are Linux-specific considerations discussed. The JSON configuration examples and descriptions are generic, but the focus on Windows images and lack of Linux parity creates friction for Linux users.
Recommendations
  • Add examples and explanations for Linux container base images (e.g., Ubuntu, Alpine, CentOS) in the ContainerImagesToSkip setting.
  • Clarify whether the cleanup and management features apply equally to Linux containers and Windows containers.
  • Provide Linux-specific guidance or considerations if there are differences in behavior or requirements.
  • Include sample configurations for skipping common Linux images, similar to the Windows examples.
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-19 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page exhibits mild Windows bias. It references Windows file paths (e.g., 'C:\Program Files\Microsoft SDKs\Service Fabric\schemas\ServiceFabricServiceModel.xsd') and recommends using Visual Studio for schema validation, which is a Windows-centric tool. Additionally, it mentions the ServiceFabric PowerShell module for service creation, but does not provide equivalent Linux CLI examples or mention cross-platform tools. Windows terminology and tools are referenced before any Linux alternatives, and no Linux/macOS-specific guidance is given.
Recommendations
  • Provide Linux/macOS file path equivalents for schema files and instructions on how to validate manifests using cross-platform editors (e.g., VS Code, JetBrains Rider).
  • Mention and provide examples for using Azure CLI or Service Fabric CLI (sfctl) for service creation and management, alongside PowerShell.
  • Clarify that Service Fabric development and deployment can be performed on Linux clusters, and link to relevant Linux-specific documentation.
  • Ensure that all tooling recommendations (e.g., manifest validation, deployment) include cross-platform options.
  • Add notes or examples for Linux/macOS users where Windows-specific instructions are given.
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-19 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 references to Linux-specific development workflows. However, Windows development (Visual Studio, PowerShell, .NET SDK) is described first, with Linux development (Eclipse, Yeoman, Java SDK) mentioned second. No explicit Linux example is missing, but the ordering and emphasis slightly favor Windows.
Recommendations
  • Present Windows and Linux development options in parallel, rather than listing Windows first.
  • Ensure that quickstart and getting started links are available for both Windows and Linux (the quickstart link currently points to a .NET/Windows page).
  • Where possible, provide equal visibility to Linux tooling and workflows (e.g., highlight Yeoman, Eclipse, Java SDK alongside Visual Studio and PowerShell).
  • Consider linking to Linux quickstart or sample projects directly from the overview.
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-19 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 toward Windows: Windows container runtimes and tools are described in more detail, and Windows scenarios (such as IIS lift-and-shift) are mentioned 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 highlighted, while Linux only mentions Docker.
Recommendations
  • Present Linux and Windows scenarios/examples in parallel or alternate order to avoid Windows-first bias.
  • Expand Linux scenario examples (e.g., highlight common Linux workloads or migration paths, such as Apache or NGINX lift-and-shift).
  • Provide equal detail for Linux container runtimes and tools, mentioning alternatives to Docker if relevant.
  • Ensure Linux tutorials and references are listed alongside Windows ones, not after.
  • Add explicit statements clarifying parity and limitations for Linux and Windows container support.
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-19 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 approach. The CLI examples (sfctl) are cross-platform, but the initial emphasis on PowerShell may create friction for Linux/macOS users.
Recommendations
  • Present Service Fabric CLI (sfctl) examples before PowerShell, as sfctl is cross-platform and more accessible to Linux/macOS users.
  • Explicitly state that sfctl works on all platforms and is recommended for non-Windows environments.
  • Consider providing Bash or shell script examples where relevant.
  • Clarify in the introduction that both Windows and Linux users are supported, and direct users to the appropriate section for their OS.
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-19 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 a few areas where Windows-specific terminology and tools are mentioned first or exclusively. For example, the description of nodes references an 'auto-start Windows service, FabricHost.exe' and executable files are described as 'EXE/DLL files.' While Linux is mentioned in the context of containers and guest executables, Windows concepts and tools are often presented first or in more detail. However, Linux support is acknowledged, and no critical tasks are Windows-only.
Recommendations
  • Clarify that FabricHost.exe and related executables have Linux equivalents or note differences in Linux deployments.
  • When describing executable files, mention Linux formats (e.g., ELF binaries) alongside EXE/DLL.
  • Ensure examples and terminology are balanced, mentioning Linux and Windows equally where applicable.
  • Add explicit notes or links to Linux-specific documentation or guidance where relevant.
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-18 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 as default exclusions in cleanup settings, and Windows examples are referenced before Linux equivalents. However, the documentation does not provide Windows-only instructions or examples, and the configuration applies to both Windows and Linux containers.
Recommendations
  • Explicitly mention Linux container base images (such as Ubuntu, Alpine, etc.) in the 'ContainerImagesToSkip' setting example, or clarify that Linux images can be managed similarly.
  • Provide examples or notes for Linux container image management, including any differences in cleanup behavior or recommended settings.
  • Add a statement clarifying that the described settings and behaviors apply to both Windows and Linux container images, unless otherwise noted.
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-18 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 overall. However, in the Management subsystem section, it specifically mentions 'PowerShell cmdlets' as a primary means of provisioning, deploying, patching, upgrading, and de-provisioning applications, without referencing equivalent Linux/macOS tooling (such as Azure CLI or REST APIs). This creates a mild Windows bias by implying PowerShell is the main or only administrative interface, and by mentioning Windows tooling first.
Recommendations
  • Mention Azure CLI and REST APIs alongside PowerShell cmdlets as supported management tools for Service Fabric clusters, especially for provisioning and lifecycle operations.
  • Clarify that administrative APIs are cross-platform and provide links or examples for Linux/macOS users.
  • Consider including example commands or references for both PowerShell and Azure CLI where relevant.
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-18 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation mentions both Windows and Linux support, and provides parity in describing development environments for each. 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-focused) guide, with no immediate Linux-specific quickstart linked.
Recommendations
  • Alternate the order in which Windows and Linux development environments are described, or present them together to emphasize parity.
  • Provide quickstart links for both Windows (.NET) and Linux (Java/.NET Core) development paths.
  • Ensure that introductory examples and links are balanced between Windows and Linux, or explicitly state that both are available.
  • Consider mentioning cross-platform tools (e.g., VS Code) alongside Visual Studio and Eclipse.
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-18 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 comprehensive reference for Service Fabric cluster settings, but exhibits mild Windows bias in several areas. Windows terminology and tools (e.g., certificate store names like 'My', references to Windows Defender Firewall, NTLM authentication, and Windows-specific log directories) are prevalent. Windows concepts (such as 'LocalMachine', 'MY', and Windows account types) are used as defaults or examples, and Windows-specific settings are sometimes described before Linux equivalents. Some settings and guidance reference Windows APIs or documentation (e.g., CertGetCertificateChain), and Windows-only features (like automatic updates via Windows Update) are mentioned without clear Linux alternatives. However, Linux settings and paths are also present, and most configuration options are applicable to both platforms.
Recommendations
  • Where Windows-specific terminology is used (e.g., certificate store names, account types), clarify Linux equivalents and provide Linux-specific examples.
  • Ensure that Linux paths, tools, and concepts are described alongside Windows ones, not just as secondary notes.
  • For settings referencing Windows APIs or documentation, add links or notes for Linux equivalents (e.g., OpenSSL, Linux certificate management).
  • Explicitly state when a setting is Windows-only, and provide Linux alternatives or guidance where possible.
  • Review default values and examples to ensure Linux parity (e.g., certificate store names, log directories, account types).
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-18 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, DockerEE) are listed in detail, and Windows scenarios (IIS lift and shift) are described before Linux equivalents. Windows tutorials and references are often shown alongside Linux, but Windows-specific tools and patterns (IIS, Windows Server containers) are highlighted more prominently.
Recommendations
  • Ensure Linux container runtimes and tools are described with equal detail as Windows (e.g., mention containerd or other Linux runtimes if relevant).
  • Present Linux and Windows scenarios in parallel, rather than listing Windows scenarios first.
  • Add more Linux-specific examples or use cases (e.g., Apache, NGINX, Python apps) to balance the IIS/Windows scenario.
  • Where possible, provide Linux and Windows tutorials/examples side by side, rather than Windows first.
  • Clarify that Service Fabric supports both Linux and Windows containers equally, unless a feature is Windows-only.
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-18 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation shows a mild Windows bias by referencing the Service Fabric SDK schema file path using a Windows directory (C:\Program Files\...), and by mentioning Visual Studio as a primary tool for packaging and deploying guest executables. There are no explicit Linux/macOS command-line examples, and the documentation does not clarify cross-platform alternatives or paths.
Recommendations
  • Add Linux/macOS equivalents for the Service Fabric SDK schema file path, or clarify if the SDK is only available on Windows.
  • Mention cross-platform tools (such as Azure CLI or Service Fabric CLI) for packaging and deploying guest executables, if available.
  • Include examples or references for using non-Windows development environments.
  • Clarify whether Visual Studio is required or if other IDEs/editors can be used.
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-18 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both PowerShell and Service Fabric CLI (sfctl) examples for deploying Docker Compose files to Azure Service Fabric. PowerShell commands are presented first and in greater detail, which may suggest a Windows-first bias. However, the CLI examples are also included and are cross-platform. There is no evidence of missing Linux examples or exclusive mention of Windows tools, but the ordering and emphasis favor Windows users.
Recommendations
  • Present CLI (sfctl) examples before or alongside PowerShell examples to emphasize cross-platform support.
  • Explicitly state that sfctl is supported on Linux/macOS and provide installation instructions or links for those platforms.
  • Clarify any limitations or differences for Linux/macOS users, if applicable.
  • Consider balancing the depth of examples between PowerShell and CLI sections.
GitHub Create Pull Request
Service Fabric Reliable Collection object serialization ...c-reliable-services-reliable-collections-serialization.md
Low Priority View Details →
Scanned: 2026-02-18 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 there is no reference to Linux-native tools or CLI usage for application upgrades.
Recommendations
  • Add examples or links for upgrading applications using Azure CLI or Service Fabric CLI (sfctl), which are cross-platform and commonly used on Linux/macOS.
  • Mention cross-platform development environments (such as VS Code or JetBrains Rider) alongside Visual Studio.
  • Ensure that PowerShell references are accompanied by Bash or shell script alternatives where applicable.
  • Clarify that the serialization concepts apply equally to Linux-based Service Fabric clusters, and provide any Linux-specific considerations if relevant.
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-17 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page for Service Fabric application and service manifest examples shows minor Windows bias. There are references to Windows-specific tools (e.g., 'ServiceFabric PowerShell module'), Windows account types (e.g., 'NetworkService', 'Administrators'), and scripts (e.g., 'Setup.bat'), with no equivalent Linux examples or explicit mention of Linux-compatible approaches. Windows terminology and tools are referenced first and exclusively, even though Service Fabric supports Linux clusters and .NET Core workloads.
Recommendations
  • Add Linux-specific examples, such as using shell scripts (.sh) instead of batch files (.bat) for SetupEntryPoint.
  • Mention Linux account types and how RunAsPolicy works on Linux clusters.
  • Reference Linux deployment tools (e.g., Azure CLI, Bash) alongside PowerShell.
  • Clarify which manifest features are cross-platform and which are Windows-only.
  • Provide guidance or links for Linux users on adapting the manifest for Linux clusters.
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-17 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, but Windows development tools (Visual Studio and PowerShell) are listed before Linux equivalents (Eclipse, Yeoman). No explicit PowerShell-heavy examples or Windows-only tools are present, and Linux is acknowledged as a supported platform. However, the ordering and phrasing subtly prioritize Windows development.
Recommendations
  • Present Windows and Linux development options in parallel, rather than listing Windows first.
  • Explicitly mention .NET Core support for Linux alongside .NET SDK for Windows.
  • Provide links to both Windows and Linux quickstart guides in the 'Next steps' section.
  • Ensure examples and tooling references are balanced between Windows and Linux.
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-17 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page is generally cross-platform, but there are subtle signs of Windows bias. Windows-specific terminology and tools (such as references to Windows services and EXE/DLL files) are mentioned first or exclusively in some sections, particularly in the 'Node' and 'Code package' definitions. The description of node startup references only Windows services and executables, and the code package section assumes EXE/DLL files as typical, which are Windows-centric. However, Linux support is acknowledged in container and guest executable sections, and the overall content is mostly platform-neutral.
Recommendations
  • Clarify that node startup processes and equivalents exist for Linux, not just Windows services.
  • When describing code packages, mention typical Linux binaries (e.g., ELF files, .so libraries) alongside EXE/DLL files.
  • Provide explicit examples or references for Linux-specific deployment and operational patterns where relevant.
  • Ensure that descriptions of Service Fabric internals (such as FabricHost.exe) note Linux equivalents or clarify if Windows-only.
  • Review ordering of examples and terminology to avoid always mentioning Windows first.
GitHub Create Pull Request
Service Fabric Azure Service Fabric container image management .../articles/service-fabric/container-image-management.md
Low Priority View Details →
Scanned: 2026-02-17 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation mentions Windows container base images (microsoft/windowsservercore, microsoft/nanoserver) as defaults in the 'ContainerImagesToSkip' setting, but does not mention Linux base images or provide Linux-specific examples. There are no explicit Linux container image examples or guidance, and the examples focus on Windows images first.
Recommendations
  • Add examples showing how to skip common Linux base images (e.g., 'docker.io/library/ubuntu', 'docker.io/library/alpine').
  • Clarify that the container image management applies to both Windows and Linux containers, if applicable.
  • Provide sample settings or scenarios for Linux container deployments.
  • Mention any differences in cleanup behavior between Windows and Linux containers, if relevant.
GitHub Create Pull Request
← Previous Page 95 of 99 Next →