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 601-625 of 2475 flagged pages
Service Fabric Azure Service Fabric security best practices ...rvice-fabric/service-fabric-best-practices-security.md
Medium Priority View Details →
Scanned: 2026-03-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Windows and Linux guidance for most security best practices, but Windows examples (such as PowerShell commands and Windows Defender configuration) are often presented first or exclusively. Windows-specific tools like PowerShell and Windows Defender are discussed in detail, while Linux equivalents are less prominent or omitted. Some sections (e.g., Windows Defender) are Windows-only, but this is acknowledged. Overall, Linux users can complete the tasks, but may experience friction due to Windows-centric ordering and tool focus.
Recommendations
  • Present Linux and Windows examples side-by-side or alternate their ordering to avoid Windows-first bias.
  • Where Windows-specific tools are discussed (e.g., Windows Defender), provide equivalent Linux guidance (such as recommended Linux antivirus solutions or security baselines) or explicitly state Linux alternatives.
  • Expand Linux-specific instructions and examples, especially for certificate management and encryption, to match the detail provided for Windows.
  • Clarify when a section is Windows-only and provide links or references to Linux documentation where appropriate.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager - Placement Policies ...ce-manager-advanced-placement-rules-placement-policies.md
Medium Priority View Details →
Scanned: 2026-03-02 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 in C# and PowerShell for configuring Service Fabric placement policies, but does not include equivalent Linux/macOS CLI examples (such as Azure CLI or Bash). PowerShell is featured as the only command-line tool, and Windows-centric tools are presented first and exclusively, creating friction for Linux/macOS users who may not have access to PowerShell or prefer other tools.
Recommendations
  • Add Azure CLI or Bash examples for configuring placement policies, especially for service creation and management.
  • Explicitly mention cross-platform alternatives to PowerShell for cluster and service management.
  • Clarify whether the PowerShell commands are usable on Linux/macOS (e.g., via PowerShell Core), or provide guidance for Linux users.
  • Consider reordering examples so that cross-platform tools are presented alongside or before Windows-specific tools.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager - Application Groups ...ice-fabric-cluster-resource-manager-application-groups.md
Medium Priority View Details →
Scanned: 2026-03-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides only PowerShell and C# examples for managing Application Groups in Service Fabric. PowerShell is a Windows-centric tool, and no Linux/macOS CLI or scripting examples (such as Bash, Azure CLI, or REST API) are provided. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other tools.
Recommendations
  • Add equivalent examples using Azure CLI (az servicefabric) or REST API for all tasks currently demonstrated with PowerShell.
  • Mention cross-platform options for managing Service Fabric applications, such as Bash scripts or Azure CLI, especially for Linux/macOS users.
  • Clarify if PowerShell Core (pwsh) is supported and provide guidance for Linux/macOS users if so.
  • Consider including sample YAML or JSON for ARM templates if relevant, to show declarative configuration options.
GitHub Create Pull Request
Service Fabric Azure Service Fabric dynamic node tags ...tps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-node-tagging.md
Medium Priority View Details →
Scanned: 2026-03-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page provides PowerShell examples for managing node tags and services in Azure Service Fabric, but does not include equivalent CLI or scripting examples for Linux/macOS environments. PowerShell is a Windows-centric tool, and its exclusive use here creates friction for users on other platforms. No mention is made of Azure CLI, Bash, or REST API usage for these tasks, despite REST APIs being referenced earlier.
Recommendations
  • Add examples using Azure CLI or Bash scripts for managing node tags and services.
  • Include REST API sample calls for adding/removing node tags and updating service tag requirements.
  • Clarify whether PowerShell commands are cross-platform (e.g., PowerShell Core), or provide guidance for Linux/macOS users.
  • Mention any limitations or platform-specific requirements for node tag management.
GitHub Create Pull Request
Service Fabric Node types and virtual machine scale sets ...les/service-fabric/service-fabric-cluster-nodetypes.md
Medium Priority View Details →
Scanned: 2026-03-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides some Linux awareness (e.g., mentions 'ServiceFabricLinuxNode'), but overall, there is a Windows-first bias. Examples use Windows-style paths (e.g., 'D:\\SvcFab'), and the 'Next steps' section links to PowerShell scripts for RDP port and admin credential changes, which are Windows-specific tasks and tools. There are no explicit Linux/macOS command examples or guidance for SSH access, and Linux equivalents are not mentioned alongside Windows instructions.
Recommendations
  • Include Linux/macOS examples for common tasks, such as connecting to cluster nodes (e.g., SSH instructions) and managing credentials.
  • When showing configuration snippets, provide both Windows and Linux path examples for the 'dataPath' property.
  • In the 'Next steps' section, add links or guidance for Linux/macOS users (e.g., how to connect via SSH, change SSH keys, or manage Linux user accounts).
  • Clearly indicate when a step or script is Windows-only, and provide Linux alternatives where possible.
GitHub Create Pull Request
Service Fabric Manage Azure Service Fabric app load using metrics ...ric/service-fabric-cluster-resource-manager-metrics.md
Medium Priority View Details →
Scanned: 2026-03-02 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 C# and PowerShell, but omits equivalent Linux/macOS CLI examples (e.g., Azure CLI or REST API). PowerShell is featured prominently for service creation and metric management, and is presented before any mention of cross-platform alternatives. There is no discussion of Linux-native tools or workflows, which creates friction for non-Windows users managing Service Fabric clusters.
Recommendations
  • Add Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Mention REST API options for metric management, with example requests.
  • Clarify which management operations can be performed from Linux/macOS and provide guidance for those environments.
  • Consider including bash shell scripts or references to Service Fabric SDK tools available for Linux.
  • Explicitly state PowerShell is required only if using Windows, and provide parity for Linux users wherever possible.
GitHub Create Pull Request
Service Fabric Scalability of Service Fabric services .../service-fabric/service-fabric-concepts-scalability.md
Medium Priority View Details →
Scanned: 2026-03-02 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 primarily in C# and PowerShell, with no equivalent Linux shell or CLI examples. PowerShell commands are referenced as the main administrative tooling, and Windows-specific patterns (e.g., PowerShell cmdlets) are mentioned before any Linux alternatives. There is a lack of guidance for Linux users on how to perform equivalent tasks, creating friction for those deploying Service Fabric clusters on Linux.
Recommendations
  • Add Linux CLI (e.g., Bash, Azure CLI) examples alongside PowerShell for administrative tasks such as updating instance counts and creating services.
  • Mention Linux-specific tools or commands (such as sfctl or Azure CLI) where PowerShell cmdlets are referenced.
  • Clarify which commands are Windows-only and provide Linux alternatives where possible.
  • Ensure parity in example ordering, showing Linux and Windows approaches side-by-side.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Auto Scaling Services and Containers ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-autoscaling.md
Medium Priority View Details →
Scanned: 2026-03-02 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 examples for configuring auto scaling in Azure Service Fabric using application manifests, C# APIs, and PowerShell. However, all CLI/script examples are PowerShell-based, which is primarily a Windows tool. There are no equivalent Bash, Linux CLI, or cross-platform scripting examples. The PowerShell examples are presented alongside C# and manifest examples, but Linux users may lack guidance for command-line operations. Additionally, there is no mention of Linux-specific tools or patterns for managing Service Fabric auto scaling, and PowerShell is used without clarifying its cross-platform support.
Recommendations
  • Add Bash or Azure CLI examples for configuring scaling policies, especially for Linux-based Service Fabric clusters.
  • Clarify whether PowerShell examples are compatible with PowerShell Core on Linux/macOS, or provide alternatives.
  • Mention any Linux-specific considerations or limitations when using auto scaling features.
  • Include references to Linux management tools (e.g., Azure CLI, REST API) where appropriate.
GitHub Create Pull Request
Service Fabric Describe a cluster by using Cluster Resource Manager ...ce-fabric-cluster-resource-manager-cluster-description.md
Medium Priority View Details →
Scanned: 2026-03-02 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Windows and cross-platform (JSON) configuration examples for Service Fabric clusters, but Windows-specific XML (ClusterManifest.xml) and PowerShell examples are consistently shown first or exclusively. PowerShell is used for service creation and update examples, with no Linux/bash CLI equivalents. The XML configuration is wrapped in <WindowsServer> tags, which may imply Windows-centric deployment, though JSON examples are also given for standalone and Azure deployments. There is no explicit mention of Linux tooling or parity in command-line examples.
Recommendations
  • Add Azure CLI or bash examples for service creation and update, alongside PowerShell.
  • Clarify if ClusterManifest.xml examples are applicable to Linux clusters, or provide Linux-specific configuration examples if available.
  • Mention Linux support and any differences in cluster setup, especially for standalone deployments.
  • Ensure that JSON examples are given equal prominence to XML/Windows examples.
  • Where PowerShell is used, also provide Azure CLI or REST API equivalents for cross-platform users.
GitHub Create Pull Request
Service Fabric Cluster Resource Manager - Management Integration ...fabric-cluster-resource-manager-management-integration.md
Medium Priority View Details →
Scanned: 2026-03-02 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides a PowerShell example for querying partition health, using Windows-style paths and commands (e.g., 'PS C:\Users\User > Get-ServiceFabricPartitionHealth'), without offering equivalent Linux/bash examples or mentioning cross-platform tools. This creates friction for Linux/macOS users managing Service Fabric clusters, as they may not be familiar with PowerShell or its usage on non-Windows systems.
Recommendations
  • Add equivalent Linux/bash examples for querying partition health, such as using Service Fabric CLI (sfctl) or REST API calls.
  • Mention cross-platform management tools and how to perform the same tasks on Linux/macOS clusters.
  • Clarify that PowerShell examples are for Windows environments, and provide guidance for Linux users.
  • Where possible, use generic command syntax or highlight platform-specific differences.
GitHub Create Pull Request
Service Fabric Azure Service Fabric standalone cluster scaling ...ce-fabric/service-fabric-cluster-scaling-standalone.md
Medium Priority View Details →
Scanned: 2026-03-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page for scaling Azure Service Fabric standalone clusters shows evidence of Windows bias. It references PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) without mentioning Linux equivalents or cross-platform tools. The linked 'scale a standalone cluster' page is specifically for Windows Server, and there are no examples or guidance for Linux-based standalone clusters, even though Service Fabric can be deployed on Linux. This creates friction for Linux users seeking parity.
Recommendations
  • Add examples and instructions for scaling standalone clusters on Linux, including relevant CLI commands and configuration steps.
  • Mention cross-platform tools (such as sfctl or REST APIs) where possible, alongside PowerShell.
  • Clarify when instructions are Windows-specific and provide links or references to Linux documentation if available.
  • Ensure that guidance for querying and upgrading cluster configuration is available for Linux environments.
GitHub Create Pull Request
Service Fabric Secure an Azure Service Fabric cluster ...cles/service-fabric/service-fabric-cluster-security.md
Medium Priority View Details →
Scanned: 2026-03-02 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page for securing an Azure Service Fabric cluster exhibits a moderate Windows bias. While it mentions both Azure-hosted and standalone Windows clusters, it consistently provides detailed guidance and links for Windows Server clusters, but omits equivalent instructions or links for standalone Linux clusters. Windows security (Kerberos) is described, but there is no mention of Linux authentication mechanisms or how to secure standalone Linux clusters. Examples and recommendations for certificate creation reference Windows tools and services, with no Linux-specific alternatives or parity.
Recommendations
  • Add explicit guidance and links for securing standalone Linux Service Fabric clusters, including certificate setup and authentication options.
  • Provide Linux-specific examples for certificate creation, such as using OpenSSL, and clarify how to install and manage certificates on Linux nodes.
  • Mention Linux authentication mechanisms (if supported), or clarify if only certificate-based security is available for Linux clusters.
  • Ensure parity in recommendations and next steps by including Linux-focused documentation links where relevant.
GitHub Create Pull Request
Service Fabric Upgrading Azure Service Fabric clusters ...icles/service-fabric/service-fabric-cluster-upgrade.md
Medium Priority View Details →
Scanned: 2026-03-02 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 general guidance for upgrading Azure Service Fabric clusters, but exhibits mild Windows bias. Windows-specific tools (PowerShell) are mentioned alongside Azure CLI, but Linux equivalents are not explicitly referenced. The section on OS image upgrades links only to Windows patching guidance, omitting Linux node patching. Examples and instructions do not prioritize Linux or macOS, and Windows terminology appears first or exclusively in some sections.
Recommendations
  • Explicitly mention Linux node patching options and link to relevant documentation for Linux clusters.
  • Provide examples using Azure CLI and bash scripts, not just PowerShell, especially in sections about certificate management, port opening, and cluster upgrades.
  • Clarify when instructions are applicable to both Windows and Linux clusters, or note any differences.
  • Add links to Linux-specific Service Fabric cluster maintenance documentation where available.
GitHub Create Pull Request
Service Fabric Azure Service Fabric application resource model ...ervice-fabric/service-fabric-concept-resource-model.md
Medium Priority View Details →
Scanned: 2026-03-02 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 a notable Windows bias. All deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) without mention of Azure CLI or other cross-platform tools. Application packaging instructions reference Visual Studio, a Windows-centric IDE, and do not provide alternatives for Linux/macOS users. No Linux/macOS-specific guidance or examples are given for key steps, such as packaging, uploading, or deploying applications.
Recommendations
  • Add Azure CLI examples for deployment and resource management alongside PowerShell examples.
  • Provide instructions for packaging Service Fabric applications using cross-platform tools (e.g., dotnet CLI, sfctl, or manual zip commands).
  • Mention alternative IDEs or command-line workflows for Linux/macOS users.
  • Ensure screenshots and walkthroughs are not exclusively tied to Windows tools.
  • Explicitly state which steps are Windows-only and offer Linux/macOS equivalents where possible.
GitHub Create Pull Request
Service Fabric Azure Service Fabric hosting model ...rticles/service-fabric/service-fabric-hosting-model.md
Medium Priority View Details →
Scanned: 2026-03-02 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 and references to PowerShell cmdlets for managing Service Fabric services, with no equivalent Linux CLI or cross-platform examples. PowerShell is presented as the primary tool for service creation and management, and examples are shown before REST or .NET API alternatives. There is no mention of Linux-specific tools (such as sfctl) or Bash usage, and no guidance for Linux/macOS users.
Recommendations
  • Add equivalent examples using sfctl (Service Fabric CLI), which is cross-platform and supported on Linux/macOS.
  • Include Bash or shell command examples alongside PowerShell, especially for service creation and querying.
  • Mention that PowerShell examples are Windows-centric and provide links or references to Linux/macOS documentation.
  • Clarify that REST API and .NET SDK examples are cross-platform, and highlight their usage for non-Windows environments.
  • Update 'Next steps' to include Linux/macOS management options, not just PowerShell.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Events ...es/service-fabric/service-fabric-diagnostics-events.md
Medium Priority View Details →
Scanned: 2026-03-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page primarily references Windows-specific logging mechanisms (ETW/Windows Event logs, Windows Azure diagnostics agent) and does not mention Linux equivalents or provide Linux-specific guidance. Windows tools and patterns are discussed first and exclusively, creating friction for Linux cluster administrators seeking parity.
Recommendations
  • Add information about how Service Fabric events are accessed and logged on Linux clusters, including supported logging channels (e.g., stdout, syslog, Azure Monitor integration).
  • Provide examples or references for configuring diagnostics and event collection on Linux nodes.
  • Clarify which features or tools are Windows-only and offer Linux alternatives where possible.
  • Ensure that monitoring and event access instructions are platform-agnostic or clearly separated for Windows and Linux.
GitHub Create Pull Request
Service Fabric Azure Service Fabric DNS service ...n/articles/service-fabric/service-fabric-dnsservice.md
Medium Priority View Details →
Scanned: 2026-03-02 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, references ApplicationManifest.xml (a Windows-centric deployment artifact), and describes enabling DNS service via the Azure portal (which is not supported for Linux clusters). There are no Linux-specific command-line examples (e.g., CLI or Bash), and Linux limitations are mentioned but not accompanied by alternative guidance or parity examples. Windows tools and patterns are presented first and more thoroughly.
Recommendations
  • Add Linux-specific examples for setting DNS names, such as using Azure CLI or Bash scripts.
  • Clarify how Linux users can enable DNS service (e.g., via ARM templates) and provide step-by-step instructions.
  • Include guidance for Linux container deployments outside of ApplicationManifest.xml and PowerShell.
  • Explicitly state limitations for Linux clusters earlier and link to Linux-specific documentation or workarounds.
  • Balance the order of examples so Linux and Windows approaches are presented equally.
GitHub Create Pull Request
Service Fabric Azure Service Fabric image store connection string ...fabric/service-fabric-image-store-connection-string.md
Medium Priority View Details →
Scanned: 2026-03-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page references PowerShell as the primary example for interacting with Service Fabric clusters and retrieving the cluster manifest, and links to a PowerShell-centric deployment guide. There are no explicit Linux or cross-platform CLI examples, nor mention of Linux tools or workflows for managing the ImageStoreConnectionString. The documentation assumes Visual Studio for publishing, which is Windows-centric, and does not provide parity for Linux/macOS users.
Recommendations
  • Add Azure CLI or cross-platform command examples for retrieving and configuring the ImageStoreConnectionString.
  • Include references to Linux/macOS-compatible tools and workflows (e.g., Bash, Azure CLI, REST API usage from curl).
  • Provide guidance for deploying Service Fabric applications from non-Windows environments.
  • Mention Visual Studio Code as an alternative to Visual Studio for cross-platform development.
  • Ensure links to deployment guides include both PowerShell and CLI/REST options.
GitHub Create Pull Request
Service Fabric Learn more about Azure Service Fabric ...icles/service-fabric/service-fabric-content-roadmap.md
Medium Priority View Details →
Scanned: 2026-03-02 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 are several areas where Windows is prioritized or referenced first, such as descriptions of cluster nodes, service processes, and standalone clusters. Windows-specific tools (e.g., PowerShell) and executables are mentioned more prominently, and Linux equivalents or examples are often missing or referenced later. Some features (like standalone clusters) are noted as Windows-only, but Linux alternatives or workarounds are not always provided. Overall, the documentation creates friction for Linux users by not offering equal visibility or examples.
Recommendations
  • Ensure Linux examples and tools (e.g., Bash, Linux CLI usage) are provided alongside Windows/PowerShell examples.
  • When referencing Service Fabric executables or processes, clarify differences for Linux (e.g., systemd services, Linux process names) and provide Linux-specific instructions where applicable.
  • Avoid always mentioning Windows tools (PowerShell, Visual Studio) first; alternate order or provide parity.
  • Highlight Linux support and limitations more clearly, and link to Linux-specific guides where features differ.
  • Add explicit Linux walkthroughs for cluster creation, management, and health monitoring, especially where only Windows examples are given.
GitHub Create Pull Request
Service Fabric Package an existing executable to Azure Service Fabric ...abric/service-fabric-guest-executables-introduction.md
Medium Priority View Details →
Scanned: 2026-03-02 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. The schema definition for manifest files is referenced as being installed in a Windows directory (C:\Program Files\Microsoft SDKs\Service Fabric\schemas\ServiceFabricServiceModel.xsd), and the example application package structure uses a Windows-style executable (existingapp.exe). No Linux/macOS-specific paths, tools, or examples are provided, and there is no mention of packaging or deploying non-Windows executables (e.g., ELF binaries or scripts). Visual Studio is mentioned as a packaging tool, which is primarily Windows-focused, and no Linux-native alternatives are referenced.
Recommendations
  • Add examples or references for packaging and deploying Linux/macOS executables (e.g., ELF binaries, shell scripts).
  • Mention the location of schema files on Linux/macOS, if available, or clarify if the SDK is cross-platform.
  • Include command-line instructions and tools that are available on Linux/macOS, such as Azure CLI or cross-platform SDK usage.
  • Provide parity in sample applications, showing both Windows (.exe) and Linux (e.g., .sh, .out) guest executables.
  • Clarify Visual Studio alternatives for Linux/macOS users, such as VS Code or other editors.
GitHub Create Pull Request
Service Fabric Health monitoring in Service Fabric ...s/service-fabric/service-fabric-health-introduction.md
Medium Priority View Details →
Scanned: 2026-03-02 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides a detailed conceptual overview of Service Fabric health monitoring, but the only concrete example of reporting and evaluating health uses PowerShell cmdlets, with no equivalent Linux/macOS CLI or REST API example. The documentation mentions REST APIs and .NET APIs as options, but does not demonstrate their usage, creating friction for non-Windows users.
Recommendations
  • Add examples for reporting and evaluating health using REST APIs, which are cross-platform.
  • Include equivalent CLI examples using Service Fabric CLI (sfctl), which works on Linux/macOS.
  • Explicitly mention and demonstrate how Linux/macOS users can perform health reporting and querying tasks.
  • Where PowerShell is used, provide alternative commands or links for Linux/macOS environments.
GitHub Create Pull Request
Service Fabric Manage apps for multiple environments ...e-fabric-manage-multiple-environment-app-configuration.md
Medium Priority View Details →
Scanned: 2026-03-02 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides examples for managing Service Fabric application parameters across environments. It mentions PowerShell and Visual Studio (Windows-centric tools) first when describing how to pass parameters, with Linux-friendly tools (sfctl, Jenkins) referenced later or less prominently. There are no explicit Linux/macOS examples or screenshots, and the workflow descriptions are weighted toward Windows tools.
Recommendations
  • Add explicit Linux/macOS examples for parameter passing, such as using sfctl and install.sh, including sample command lines.
  • Provide parity in workflow descriptions for Linux users, e.g., describe how to use Jenkins or shell scripts to substitute parameters.
  • Reorder examples so Linux tools (sfctl, shell scripts) are presented alongside or before Windows tools.
  • Include screenshots or code snippets for Linux/macOS environments where relevant.
GitHub Create Pull Request
Service Fabric Azure Service Fabric container application manifest examples ...abric/service-fabric-manifest-example-container-app.md
Medium Priority View Details →
Scanned: 2026-03-02 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 application and service manifest examples for Azure Service Fabric container applications, but it is notably Windows-centric. The examples are based on a Windows Server 2016 container sample, and Windows-specific tools and patterns (such as 'winver' for OS build detection and Windows file paths) are referenced. There is no explicit Linux example, and Windows terminology and instructions appear before or instead of Linux equivalents.
Recommendations
  • Add equivalent Linux-based manifest examples, referencing a Linux container sample repository.
  • Include instructions for obtaining OS build/version on Linux (e.g., 'cat /etc/os-release' or 'uname -r') alongside the Windows 'winver' command.
  • Use cross-platform file paths in volume examples (e.g., '/mnt/data' for Linux) or clarify Windows-specific paths.
  • Clarify which manifest features are supported on Linux Service Fabric clusters, and note any differences.
  • Provide links to Linux-specific documentation or samples where available.
GitHub Create Pull Request
Service Fabric Networking patterns for Azure Service Fabric ...s/service-fabric/service-fabric-patterns-networking.md
Medium Priority View Details →
Scanned: 2026-03-02 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 only PowerShell-based deployment commands and examples, with no mention of Azure CLI, Bash, or Linux/macOS workflows. Windows tools (PowerShell, RDP, Windows command prompt) are used exclusively and shown first, creating friction for Linux/macOS users who must adapt instructions or use alternative tooling.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all deployment steps.
  • Mention Bash or shell scripting alternatives where relevant.
  • Clarify that Azure Resource Manager templates can be deployed from any OS, and provide cross-platform guidance.
  • Replace or supplement RDP and Windows command prompt examples (e.g., ping) with SSH and Bash equivalents.
  • Explicitly state OS-agnostic steps and note any Windows-specific requirements.
GitHub Create Pull Request
Service Fabric Service communication with the ASP.NET Core ...vice-fabric-reliable-services-communication-aspnetcore.md
Medium Priority View Details →
Scanned: 2026-03-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation covers both Windows and Linux scenarios for ASP.NET Core in Service Fabric, but there is a notable Windows bias in several areas. Windows-specific tools and APIs (HTTP.sys, Windows HTTP Server API, netsh) are discussed in detail, often before or more extensively than their Linux equivalents. HTTP.sys is described as Windows-only, and its configuration is explained with references to Windows tools. Kestrel, the cross-platform web server, is covered thoroughly and is recommended for Linux, but Windows-specific patterns and terminology (such as endpoint registration and port sharing) are introduced first and in greater depth. Some example code and configuration steps are Windows-centric, and Visual Studio debugging is referenced as a next step, which is primarily a Windows tool.
Recommendations
  • Ensure Linux parity by providing explicit Linux/macOS guidance where relevant, such as how to configure Kestrel endpoints and firewall rules on Linux.
  • Add notes or links for Linux/macOS users on how to debug Service Fabric applications using cross-platform tools (e.g., VS Code, CLI).
  • When discussing endpoint configuration or port assignment, clarify any OS-specific differences and provide Linux/macOS equivalents.
  • Consider reordering sections so that cross-platform solutions (Kestrel) are presented before Windows-only solutions (HTTP.sys).
  • Where Windows tools like netsh are mentioned, offer Linux alternatives or clarify that these steps are not required on Linux.
GitHub Create Pull Request
← Previous Page 25 of 99 Next →