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 901-925 of 2475 flagged pages
Service Fabric Service Fabric Cluster Resource Manager - Placement Policies ...ce-manager-advanced-placement-rules-placement-policies.md
Medium Priority View Details →
Scanned: 2026-02-25 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides code examples primarily in C# and PowerShell for configuring Service Fabric placement policies. PowerShell is a Windows-centric tool, and there are no equivalent examples for Linux/macOS users (e.g., Bash CLI, REST API, or Azure CLI). All command-line examples are PowerShell, and no Linux-native tools or patterns are mentioned. This creates friction for Linux users who may not have access to PowerShell or prefer other scripting environments.
Recommendations
  • Add Azure CLI examples for each placement policy configuration, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include REST API or ARM template snippets for configuring placement policies, which are platform-agnostic.
  • Explicitly mention whether these policies can be configured using Service Fabric CLI (sfctl) or other Linux-compatible tools, and provide examples if possible.
  • Clarify any limitations or differences for Linux-based Service Fabric clusters, if applicable.
Scanned: 2026-02-25 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides code examples for configuring auto scaling policies in Azure Service Fabric using application manifests, C# APIs, and PowerShell. All PowerShell examples are Windows-specific, and no Linux shell (e.g., Bash, CLI) equivalents are provided. The PowerShell examples are presented alongside C# and manifest examples, but there is no mention of Linux-native tooling or cross-platform CLI usage. Additionally, the documentation does not clarify which steps or tools are available on Linux, nor does it provide guidance for Linux users on how to perform equivalent operations.
Recommendations
  • Add Azure CLI examples for configuring auto scaling policies, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly state which PowerShell commands are Windows-only and provide alternative instructions for Linux users.
  • Include Bash or shell script examples where possible, or reference Service Fabric REST APIs for cross-platform automation.
  • Clarify in each section whether the described approach is supported on Linux, macOS, or only Windows.
  • Mention any limitations or differences for Linux clusters (e.g., resource monitor service support, containerized vs non-containerized workloads).
Service Fabric Describe a cluster by using Cluster Resource Manager ...ce-fabric-cluster-resource-manager-cluster-description.md
Medium Priority View Details →
Scanned: 2026-02-25 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Windows (ClusterManifest.xml, PowerShell) and cross-platform (ClusterConfig.json, Template.json) configuration examples. However, Windows-specific configuration (ClusterManifest.xml with <WindowsServer>) is presented first and in more detail, and PowerShell commands are used for service creation and updates, with no equivalent Linux CLI or REST API examples. There is no explicit mention of Linux tools or patterns, and the documentation does not clarify Linux/macOS parity for standalone Service Fabric clusters.
Recommendations
  • Add explicit Linux/macOS configuration examples, such as using ClusterManifest.xml for Linux clusters (<Linux> element) or referencing Linux node setup.
  • Provide CLI or REST API examples for service creation and updates, not just PowerShell and C#.
  • Clarify which configuration files and approaches are supported on Linux/macOS and how they differ from Windows.
  • Mention any Linux-specific constraints or considerations for Service Fabric standalone clusters.
  • Ensure that cross-platform configuration examples (ClusterConfig.json, Template.json) are given equal prominence and detail as Windows examples.
Service Fabric Manage Azure Service Fabric app load using metrics ...ric/service-fabric-cluster-resource-manager-metrics.md
Medium Priority View Details →
Scanned: 2026-02-25 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides both C# and PowerShell examples for managing Service Fabric metrics, but does not include equivalent Linux/macOS CLI examples (such as Azure CLI or Bash). PowerShell commands are shown prominently, and no Linux-native tooling or cross-platform instructions are provided. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other tools.
Recommendations
  • Add Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used.
  • Explicitly mention if PowerShell commands are available on Linux/macOS (via PowerShell Core), or provide Bash script equivalents.
  • Clarify which management operations can be performed via REST API, Azure CLI, or SDKs on Linux/macOS.
  • Consider including a table comparing management options across platforms (Windows, Linux, macOS) for Service Fabric clusters.
Scanned: 2026-02-25 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides PowerShell examples for configuring service sensitivity and maximum load, but does not include equivalent Linux/macOS CLI examples (such as Bash or Azure CLI). PowerShell is presented as the primary scripting interface, and no mention is made of cross-platform alternatives or how Linux users can perform these tasks. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other tools.
Recommendations
  • Add Azure CLI or Bash script examples for all PowerShell commands shown, highlighting cross-platform compatibility.
  • Explicitly mention whether PowerShell Core (pwsh) is supported on Linux/macOS and provide instructions if so.
  • Document any REST API endpoints or SDK methods that can be used from Linux/macOS environments.
  • Clarify if certain operations are Windows-only, or provide guidance for Linux/macOS users where parity exists.
Service Fabric Secure an Azure Service Fabric cluster ...cles/service-fabric/service-fabric-cluster-security.md
Medium Priority View Details →
Scanned: 2026-02-25 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page provides security guidance for Azure Service Fabric clusters, mentioning both Azure-hosted and standalone Windows clusters. However, it consistently references Windows Server clusters for standalone scenarios, with no mention of standalone Linux clusters or Linux-specific security setup. Windows security (Kerberos) is discussed, but there is no equivalent section for Linux authentication or Linux-specific certificate management. Examples and links for standalone clusters are exclusively for Windows, and Windows tools (e.g., Windows Server certificate service) are referenced for certificate creation, with no Linux alternatives provided.
Recommendations
  • Add explicit guidance for securing standalone Linux Service Fabric clusters, including certificate setup and authentication options.
  • Provide links or references to Linux-compatible certificate management tools (e.g., OpenSSL) and instructions for generating certificates on Linux.
  • Clarify whether standalone Linux clusters are supported, and if not, state this explicitly to avoid confusion.
  • Ensure parity in example scenarios, showing both Windows and Linux approaches where applicable.
Service Fabric Azure Service Fabric application resource model ...ervice-fabric/service-fabric-concept-resource-model.md
Medium Priority View Details →
Scanned: 2026-02-25 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates notable Windows bias. All deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) without any mention of Azure CLI equivalents or Bash scripting. Application packaging is described via Visual Studio, a Windows-centric tool, with no alternative for Linux/macOS users. No Linux-specific instructions or cross-platform tooling are referenced, and Windows tools are presented first and exclusively.
Recommendations
  • Add Azure CLI examples for deployment, upgrade, and deletion tasks alongside PowerShell.
  • Provide instructions for packaging Service Fabric applications using cross-platform tools (e.g., dotnet CLI, sfctl, or manual zip commands) instead of only Visual Studio.
  • Mention that the Resource Manager template workflow is platform-agnostic and can be executed from any OS.
  • Include Bash or shell script examples for relevant steps.
  • Clarify which steps are Windows-only and provide Linux/macOS alternatives where possible.
Service Fabric Azure Service Fabric standalone cluster scaling ...ce-fabric/service-fabric-cluster-scaling-standalone.md
Medium Priority View Details →
Scanned: 2026-02-25 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page on scaling Azure Service Fabric standalone clusters demonstrates Windows bias by referencing PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) and linking to Windows Server-specific guides. There are no Linux-specific examples, tools, or guidance, even though Service Fabric standalone clusters can be deployed on both Windows and Linux. The documentation assumes Windows tooling and does not mention Linux equivalents or cross-platform approaches.
Recommendations
  • Add Linux-specific examples and guidance for scaling standalone clusters, including references to relevant CLI tools or scripts.
  • Mention cross-platform tools (e.g., Service Fabric CLI, REST APIs) where possible, and provide both Windows and Linux workflows.
  • Clarify when instructions are Windows-only and provide links or notes for Linux users.
  • Include sample commands for Linux environments, such as using sfctl or bash scripts, alongside PowerShell examples.
Service Fabric Upgrading Azure Service Fabric clusters ...icles/service-fabric/service-fabric-cluster-upgrade.md
Medium Priority View Details →
Scanned: 2026-02-25 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides upgrade guidance for Azure Service Fabric clusters, but several sections reference Windows-specific tools and patterns (e.g., Patch Orchestration Application for Windows, NTLM settings, and a link to patching Windows OS images) without mentioning Linux equivalents or clarifying Linux support. Examples for certificate management and port opening mention PowerShell/Azure CLI, but do not provide explicit Linux guidance or parity. The documentation tends to mention Windows-related actions and tools first, and omits Linux-specific upgrade scenarios or tools.
Recommendations
  • Clarify which upgrade and maintenance procedures apply to Linux-based Service Fabric clusters, and which are Windows-only.
  • Provide explicit examples for Linux users (e.g., using Bash/Azure CLI, Linux certificate management, port opening on Linux clusters).
  • Add links or sections for patching Linux OS images in Service Fabric clusters, if supported.
  • Clearly distinguish Windows-only features (such as NTLM/FileStoreService and Patch Orchestration Application) from cross-platform features.
  • Where PowerShell is mentioned, ensure Azure CLI/Bash examples are also provided and labeled for Linux/macOS users.
Service Fabric Scalability of Service Fabric services .../service-fabric/service-fabric-concepts-scalability.md
Medium Priority View Details →
Scanned: 2026-02-25 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides code examples and administrative instructions primarily using PowerShell, which is a Windows-centric tool. There are no equivalent Linux CLI or script examples (e.g., Bash, Azure CLI) for scaling operations. Windows tools and patterns (PowerShell cmdlets) are mentioned exclusively and before any Linux alternatives, and Linux users are not given parity in actionable examples. The only explicit Linux mention is in a platform comparison section, but it does not provide Linux-specific operational guidance.
Recommendations
  • Add Linux-friendly examples for scaling operations, such as using Azure CLI or Bash scripts.
  • Include instructions or references for Linux users to perform equivalent tasks (e.g., scaling services, updating instance counts) via REST API, Azure CLI, or Service Fabric CLI (sfctl).
  • Present examples for both Windows and Linux platforms side-by-side, or clarify which examples are platform-specific.
  • Mention Linux tools (e.g., sfctl, Bash) where PowerShell is referenced, and provide links to relevant documentation.
Service Fabric Learn more about Azure Service Fabric ...icles/service-fabric/service-fabric-content-roadmap.md
Medium Priority View Details →
Scanned: 2026-02-25 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation provides a broad overview of Azure Service Fabric, which supports both Windows and Linux. However, there is a notable Windows bias: Windows-specific tools (e.g., PowerShell, Visual Studio) are mentioned before Linux equivalents, and Windows terminology (e.g., Windows service, .exe files) is used throughout. Standalone cluster creation and upgrade instructions are Windows-only, with Linux standalone clusters explicitly unsupported. Examples and tool references (e.g., PowerShell cmdlets) are often Windows-first or Windows-only, and Linux-specific workflows or tools are rarely detailed.
Recommendations
  • Where possible, provide Linux-specific examples and workflows alongside Windows ones (e.g., CLI commands, shell scripts, Linux service management).
  • Mention cross-platform tools (e.g., sfctl CLI) before or alongside Windows tools like PowerShell.
  • Clarify which features are Windows-only and which are cross-platform, ideally linking to Linux documentation when available.
  • Add guidance for Linux users on cluster management, health monitoring, and application lifecycle, using Linux-native tools.
  • Update 'Next steps' to include Linux cluster creation and management, or clearly state Linux limitations.
Service Fabric Health monitoring in Service Fabric ...s/service-fabric/service-fabric-health-introduction.md
Medium Priority View Details →
Scanned: 2026-02-25 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides a PowerShell-only example for reporting and evaluating application health in Service Fabric, without offering equivalent Linux/macOS CLI or REST API examples. While Service Fabric is cross-platform, the exclusive use of PowerShell in the example creates friction for Linux/macOS users.
Recommendations
  • Add equivalent examples using Azure CLI, Service Fabric CLI (sfctl), or REST API for health reporting and querying.
  • Clearly indicate which tools are available on Linux/macOS and provide links to their documentation.
  • Consider showing Linux/macOS examples alongside Windows/PowerShell examples, or at least referencing them in the 'Example' section.
Service Fabric Azure Service Fabric Events ...es/service-fabric/service-fabric-diagnostics-events.md
Medium Priority View Details →
Scanned: 2026-02-25 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page primarily references Windows-specific logging mechanisms (ETW/Windows Event logs) and the Windows Azure diagnostics agent as default channels for Service Fabric event access. Windows tools and patterns are mentioned first and exclusively in the 'How to access events' section, with no equivalent Linux examples or guidance. There is no mention of Linux-native logging (e.g., journald, syslog) or cross-platform diagnostic agents, which may create friction for Linux cluster administrators.
Recommendations
  • Add explicit guidance for accessing Service Fabric events on Linux clusters, including supported logging channels (e.g., Azure Monitor, journald, syslog) and any differences in default diagnostics configuration.
  • Mention whether the Azure diagnostics agent is available for Linux clusters, or provide alternatives if not.
  • Provide Linux-specific examples or clarify which instructions are cross-platform.
  • Ensure parity in tool recommendations and order of presentation (e.g., mention cross-platform REST APIs before Windows-specific tools).
Service Fabric Azure Service Fabric DNS service ...n/articles/service-fabric/service-fabric-dnsservice.md
Medium Priority View Details →
Scanned: 2026-02-25 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides PowerShell examples for setting DNS names but does not offer equivalent Linux CLI or scripting examples. Windows tools and patterns (such as ApplicationManifest.xml and Visual Studio) are mentioned, while Linux alternatives are not. The limitations section notes Linux support is restricted, but the overall documentation assumes Windows as the default, with Linux-specific instructions and caveats appearing later or being omitted.
Recommendations
  • Add Linux CLI examples (e.g., Azure CLI, Bash scripts) for setting DNS names and managing services.
  • Mention Linux-compatible editors and deployment workflows alongside Visual Studio/ApplicationManifest.xml.
  • Clarify Linux-specific steps earlier in the documentation, not only in the limitations section.
  • Provide guidance for enabling DNS service on Linux clusters using ARM templates, including any required settings or workarounds.
  • Include explicit examples for containerized services on Linux, since Linux support is limited to these.
Service Fabric Package an existing executable to Azure Service Fabric ...abric/service-fabric-guest-executables-introduction.md
Medium Priority View Details →
Scanned: 2026-02-25 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias. It references Windows directory paths (e.g., C:\Program Files\Microsoft SDKs\Service Fabric\schemas\ServiceFabricServiceModel.xsd) and does not provide equivalent Linux/macOS paths or instructions. The examples and directory structures use Windows conventions (e.g., .exe file extension, backslashes), and there are no explicit Linux/macOS examples or guidance. Visual Studio is mentioned as a packaging tool, which is primarily a Windows application, without mentioning cross-platform alternatives.
Recommendations
  • Add Linux/macOS equivalent paths for Service Fabric SDK schema files.
  • Provide examples using Linux/macOS directory conventions (forward slashes, .out or no extension for executables).
  • Mention cross-platform tools for packaging and deploying guest executables (such as Azure CLI, Service Fabric CLI, or VS Code).
  • Clarify whether the process is supported on Linux/macOS clusters and, if so, provide relevant instructions.
  • Include sample manifests and directory structures for Linux/macOS users.
Service Fabric Azure Service Fabric container application manifest examples ...abric/service-fabric-manifest-example-container-app.md
Medium Priority View Details →
Scanned: 2026-02-25 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 application manifest examples exhibits a Windows bias. The manifest examples are explicitly based on a Windows Server 2016 container sample, and several instructions and comments reference Windows-specific tools (e.g., 'winver' to get the OS build version). There are no Linux-specific examples, nor is there guidance for Linux container scenarios, even though Service Fabric supports Linux containers. The documentation also references Windows paths (e.g., 'c:\VolumeTest\Data') and does not provide Linux path equivalents.
Recommendations
  • Provide parallel examples or notes for Linux container scenarios, including sample manifests based on Linux container images.
  • When referencing OS build versions, include instructions for obtaining the build/version on Linux (e.g., 'uname -r' or '/etc/os-release').
  • Use platform-agnostic paths in examples, or show both Windows and Linux path formats where relevant.
  • Clarify in the introduction whether the examples are Windows-only, or add a section for Linux users if both are supported.
  • Where features differ between Windows and Linux, explicitly call out the differences and provide guidance for both.
Service Fabric Azure Service Fabric hosting model ...rticles/service-fabric/service-fabric-hosting-model.md
Medium Priority View Details →
Scanned: 2026-02-25 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page for Azure Service Fabric hosting model demonstrates a moderate Windows bias. PowerShell is the only CLI example provided for service creation, and PowerShell-based links are referenced throughout for management tasks. There are no Linux CLI (e.g., Bash, Azure CLI) or cross-platform examples, and Windows tooling (PowerShell) is mentioned first and exclusively. This creates friction for Linux/macOS users, as Service Fabric supports cross-platform development and deployment, but the documentation does not reflect this parity.
Recommendations
  • Add Azure CLI examples for service creation and management tasks, alongside PowerShell.
  • Explicitly mention cross-platform support and provide guidance for Linux/macOS users.
  • Include Bash or shell script examples where relevant.
  • Reference REST API usage with curl or other Linux-friendly tools, not just .NET or PowerShell.
  • Clarify which management tasks can be performed from Linux/macOS and provide links to relevant tools.
Service Fabric Azure Service Fabric image store connection string ...fabric/service-fabric-image-store-connection-string.md
Medium Priority View Details →
Scanned: 2026-02-25 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page references PowerShell as the primary example for interacting with Service Fabric clusters and retrieving the cluster manifest. It also links to a PowerShell-focused deployment guide as the main 'Next steps'. While Service Fabric is cross-platform, the documentation does not provide equivalent Linux/macOS CLI or scripting examples (e.g., Azure CLI, Bash), nor does it mention Linux tooling or patterns for these operations. Windows tools and workflows are mentioned first and most prominently.
Recommendations
  • Add Azure CLI or Bash examples for retrieving the cluster manifest and deploying/removing applications, alongside PowerShell.
  • Include links to Linux/macOS-specific documentation or workflows where relevant.
  • Mention cross-platform tools and clarify which steps are applicable to Linux/macOS users.
  • Balance the order of examples so Windows and Linux approaches are presented equally.
Scanned: 2026-02-25 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page provides manifest examples for Service Fabric applications, but the examples and descriptions are implicitly Windows-centric. Batch scripts (.bat), EXE files, and references to Windows user/group concepts (Administrators, NetworkService) are used throughout, with no mention of Linux equivalents (e.g., shell scripts, Linux user/group patterns). There are no examples or guidance for Linux deployments, even though Service Fabric supports Linux nodes.
Recommendations
  • Add parallel examples for Linux deployments, such as using shell scripts (.sh) instead of .bat files in SetupEntryPoint.
  • Clarify which user/group concepts map to Linux equivalents, or provide guidance for configuring principals and RunAsPolicy on Linux clusters.
  • Include notes or sections indicating which manifest settings are cross-platform and which are Windows-specific.
  • Show how to configure service manifests for Linux containers or processes, including file permissions and user/group management.
  • Where EXE files are referenced, mention that on Linux, these would be ELF binaries or scripts, and provide Linux-specific examples.
Service Fabric Networking patterns for Azure Service Fabric ...s/service-fabric/service-fabric-patterns-networking.md
Medium Priority View Details →
Scanned: 2026-02-25 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation consistently uses PowerShell for deployment examples and command-line instructions, with no mention of Azure CLI or Bash equivalents. Windows-centric tools and patterns (e.g., RDP, PowerShell, Windows file paths) are referenced throughout, and Windows examples are presented first or exclusively. There are no Linux/macOS-specific instructions or parity for deployment or cluster management.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all deployment steps.
  • Include Bash shell command examples for Linux/macOS users.
  • Mention SSH as an alternative to RDP for accessing VMs in the cluster.
  • Use platform-neutral file paths or clarify when Windows paths are used.
  • Explicitly state if templates and instructions are cross-platform, or provide guidance for Linux/macOS users where differences exist.
Service Fabric Service communication with the ASP.NET Core ...vice-fabric-reliable-services-communication-aspnetcore.md
Medium Priority View Details →
Scanned: 2026-02-25 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation provides comprehensive coverage of both Kestrel (cross-platform) and HTTP.sys (Windows-only) web servers for ASP.NET Core in Azure Service Fabric. However, there is a notable Windows bias: HTTP.sys (Windows-only) is discussed in detail, including endpoint configuration and port sharing, with explicit mention of Windows tools (netsh) and Windows kernel drivers. Windows-specific features are described before their Linux equivalents, and Linux/macOS-specific guidance is largely absent. While Kestrel is recommended for cross-platform scenarios, Linux/macOS users may find the documentation less clear regarding platform-specific setup, troubleshooting, and limitations. There are no explicit Linux/macOS examples, and some sections (such as endpoint configuration and port assignment) reference Windows patterns/tools without Linux alternatives.
Recommendations
  • Add explicit Linux/macOS examples for Service Fabric Reliable Services using Kestrel, including platform-specific configuration and troubleshooting.
  • Clarify which sections and features are Windows-only and which are cross-platform, especially when discussing endpoint configuration and port assignment.
  • Provide Linux/macOS-specific guidance for firewall configuration, port assignment, and service debugging, avoiding exclusive reference to Windows tools (e.g., netsh).
  • Include a summary table or section highlighting platform support for each web server and feature.
  • Ensure parity in example ordering: present cross-platform (Kestrel) examples first, or side-by-side with Windows-only (HTTP.sys) examples.
Service Fabric Reliable Collection object serialization ...c-reliable-services-reliable-collections-serialization.md
Medium 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 provides .NET/C# examples exclusively, which is expected for Azure Service Fabric Reliable Collections, as they are primarily used with .NET. However, in the 'Next steps' section, Windows-centric tools (Visual Studio and PowerShell) are mentioned before any Linux-agnostic alternatives, and there is no mention of Linux/macOS tooling or CLI options for application upgrades. There are no explicit Linux examples or references to Linux development environments.
Recommendations
  • Add references to cross-platform tools such as Azure CLI or Service Fabric CLI (sfctl) for application upgrades.
  • Include guidance or links for Linux/macOS users on how to develop, deploy, and upgrade Service Fabric applications.
  • Ensure that PowerShell and Visual Studio are not presented as the only upgrade options; mention alternatives for non-Windows environments.
  • Clarify that Service Fabric Reliable Collections can be used in Linux node pools (if applicable) and provide relevant links.
Service Fabric Replica soft delete for enhanced data protection in Service Fabric ...s/service-fabric/service-fabric-replica-soft-delete.md
Medium Priority View Details →
Scanned: 2026-02-25 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page for 'Replica soft delete for enhanced data protection in Service Fabric' demonstrates a notable Windows bias. All command-line/API examples reference PowerShell cmdlets (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica), and no Linux or cross-platform equivalents (such as CLI, REST, or SDK usage from Linux/macOS) are provided. The documentation repeatedly mentions administrative PowerShell APIs as the primary interface, and Windows-centric tooling is referenced first and exclusively. There is no guidance for Linux users on how to perform equivalent operations, nor any mention of Linux-compatible tools or workflows.
Recommendations
  • Add examples using Service Fabric CLI (sfctl) or REST APIs for replica management, where available.
  • Clarify whether the PowerShell cmdlets have cross-platform equivalents or if the FabricClient API can be used from Linux/macOS.
  • Provide sample commands or code snippets for Linux/macOS users, including relevant SDK usage (e.g., Python, Java, .NET Core).
  • Explicitly state any limitations or parity gaps for Linux clusters, if applicable.
  • Mention Service Fabric Explorer (SFX) as a cross-platform tool and provide usage instructions for Linux/macOS users.
Service Fabric Add custom Service Fabric health reports ...rticles/service-fabric/service-fabric-report-health.md
Medium Priority View Details →
Scanned: 2026-02-25 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed PowerShell examples for health reporting in Service Fabric, with no equivalent Linux/macOS CLI examples (such as Bash or Azure CLI). Windows/PowerShell commands are shown first and exclusively, which may create friction for Linux/macOS users who do not have access to PowerShell or prefer other tools.
Recommendations
  • Add equivalent examples using Azure CLI or Bash scripts for health reporting tasks.
  • Clarify which PowerShell commands are cross-platform (PowerShell Core) and which are Windows-only.
  • Mention any Linux/macOS-compatible tools or APIs for interacting with Service Fabric health reports.
  • Provide guidance for Linux users on how to install and use PowerShell Core if it is required, or offer alternative approaches.
Service Fabric Standalone Service Fabric clusters overview ...-fabric/service-fabric-standalone-clusters-overview.md
Medium Priority View Details →
Scanned: 2026-02-25 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation initially describes Service Fabric clusters as supporting both Windows Server and Linux, but later clarifies that Linux isn't yet supported for standalone clusters. Most examples and security guidance focus on Windows-specific features (Kerberos, Windows authentication, Windows Server versions), with no Linux-specific instructions or examples. This creates confusion and friction for Linux users seeking parity.
Recommendations
  • Clarify at the top of the page that standalone clusters are currently Windows-only, despite initial mention of Linux.
  • Remove or rephrase statements implying Linux support where it does not exist.
  • If/when Linux support is added, provide Linux-specific examples, instructions, and security guidance.
  • Consider linking to documentation for Service Fabric on Linux (if available) or clearly state where Linux is supported (e.g., Azure clusters, not standalone).