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 951-975 of 2475 flagged pages
Service Fabric Service Fabric application upgrade ...s/service-fabric/service-fabric-application-upgrade.md
Medium Priority View Details →
Scanned: 2026-02-23 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 for Service Fabric application upgrade exhibits a notable Windows bias. PowerShell is used exclusively in code examples, and Windows-specific tools (such as http.sys and PowerShell cmdlets) are referenced without Linux equivalents or alternatives. There are no examples or guidance for Linux/macOS users, and Windows terminology and tools are mentioned first and exclusively throughout the article.
Recommendations
  • Add CLI (sfctl) examples alongside PowerShell for application upgrade operations, as sfctl is cross-platform and supported on Linux/macOS.
  • Explicitly mention any differences or limitations for Linux clusters, especially regarding certificate management and port usage.
  • Provide guidance or links for Linux/macOS users on how to perform upgrades, including relevant commands and tools.
  • Clarify which features or steps are Windows-only, and offer alternatives or workarounds for Linux environments where possible.
GitHub Create Pull Request
Service Fabric Architecture of Azure Service Fabric ...articles/service-fabric/service-fabric-architecture.md
Medium Priority View Details →
Scanned: 2026-02-23 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation mentions PowerShell cmdlets as a primary management interface for Service Fabric, without referencing Linux or cross-platform equivalents (such as Azure CLI or REST APIs). Additionally, Windows security is mentioned alongside X509 certificates in the transport subsystem, with no explicit mention of Linux authentication mechanisms. These choices suggest a Windows-first bias in management and security examples.
Recommendations
  • Add references to cross-platform management tools such as Azure CLI and REST APIs, highlighting their parity with PowerShell cmdlets.
  • Clarify authentication options for Linux-based clusters, including how X509 certificates are used and whether Linux equivalents to Windows security exist.
  • Ensure examples and tooling references are balanced, mentioning Linux-compatible approaches where applicable.
GitHub Create Pull Request
Service Fabric Restoring backup in Azure Service Fabric ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-backup-restore-service-trigger-restore.md
Medium Priority View Details →
Scanned: 2026-02-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily biased toward Windows/PowerShell usage. All command-line examples use PowerShell, including REST API calls, and require installation of a Microsoft.ServiceFabric.Powershell.Http module. There are no examples for Linux/macOS users (e.g., Bash, curl, or Azure CLI), nor is there guidance for using cross-platform tools. The documentation assumes the reader is using Windows and PowerShell, which creates friction for Linux/macOS users.
Recommendations
  • Add equivalent Bash/curl examples for REST API calls, showing how to authenticate and trigger restores from Linux/macOS.
  • Document how to use Azure CLI or other cross-platform tools for backup/restore operations, if supported.
  • Clarify if the Microsoft.ServiceFabric.Powershell.Http module is required only on Windows, and provide alternatives for Linux/macOS users.
  • Provide guidance for connecting to Service Fabric clusters from Linux/macOS, including certificate handling.
  • Consider reordering sections so that REST API usage is shown in a generic, cross-platform way first, then PowerShell as a specific example.
GitHub Create Pull Request
Service Fabric Capacity planning and scaling for Azure Service Fabric ...bric/service-fabric-best-practices-capacity-scaling.md
Medium Priority View Details →
Scanned: 2026-02-23 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides several manual scaling steps and examples using PowerShell cmdlets (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState) without mentioning Linux equivalents or cross-platform alternatives. Additionally, PowerShell-based instructions are presented first and most prominently in scaling sections, while Linux-specific guidance is not provided. However, the page does reference Linux cluster creation in the 'Next steps' section, indicating Service Fabric supports Linux, but the operational guidance is Windows-centric.
Recommendations
  • Add equivalent Linux command-line instructions (e.g., using sfctl or REST API) alongside PowerShell examples for scaling operations.
  • Explicitly state which steps are Windows-only and provide Linux alternatives where possible.
  • Include cross-platform guidance for cluster management tasks, such as node deactivation and removal.
  • Consider providing sample scripts or walkthroughs for Linux users using Service Fabric CLI (sfctl) or REST API.
  • Ensure parity in example ordering, so Linux instructions are not always secondary.
GitHub Create Pull Request
Service Fabric Azure Service Fabric networking best practices ...ice-fabric/service-fabric-best-practices-networking.md
Medium Priority View Details →
Scanned: 2026-02-23 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation presents some Windows bias, notably in the order and prominence of Windows-specific examples and tools. PowerShell and Windows-centric patterns are mentioned first or exclusively in several sections, such as API endpoints, DevOps integration, and application networking. Linux equivalents are sometimes referenced but often lack parity in example detail or are mentioned after Windows. Some tooling and operational guidance (e.g., PowerShell APIs, Windows container networking) are Windows-focused, and Linux-specific instructions or examples are sparse or missing.
Recommendations
  • Provide Linux CLI (az CLI, bash) examples alongside PowerShell for cluster management and networking tasks.
  • Ensure Linux-specific guidance is given equal prominence and detail, especially for API access, DevOps integration, and application networking.
  • Include references to Linux-native tools and patterns (e.g., systemd, iptables, Linux firewall configuration) where relevant.
  • Add explicit examples for Linux container networking and operational scenarios, not just Windows containers.
  • Review order of presentation so Linux and Windows are treated equally (e.g., mention both in parallel, not always Windows first).
GitHub Create Pull Request
Service Fabric Azure Service Fabric security best practices ...rvice-fabric/service-fabric-best-practices-security.md
Medium Priority View Details →
Scanned: 2026-02-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation provides both Windows and Linux guidance for key security tasks, but Windows-specific tools (PowerShell, Windows Defender, DSC) are mentioned first or exclusively in several sections. Windows examples and terminology are often presented before Linux equivalents, and some sections (e.g., Windows Defender, DSC) are Windows-only without Linux alternatives or clarifications.
Recommendations
  • Ensure Linux examples are presented alongside Windows examples, not after them, especially in sections about certificate generation and secret encryption.
  • Where Windows-specific tools (e.g., PowerShell, Windows Defender, DSC) are discussed, add explicit notes or links to Linux alternatives or clarify their absence.
  • For security baseline recommendations, mention Linux security best practices (e.g., CIS benchmarks, SELinux/AppArmor) in addition to Windows baselines.
  • In sections about firewall rules and outbound traffic, clarify any Linux-specific considerations or tools for managing network security.
  • Consider alternating the order of Windows and Linux examples to avoid implicit prioritization.
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-02-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation consistently provides PowerShell examples for configuring Service Fabric placement policies, but does not offer equivalent CLI or scripting examples for Linux/macOS users. All command-line examples are PowerShell-centric, and no mention is made of cross-platform tools such as Azure CLI or REST API methods. The PowerShell examples are presented immediately after the C# code snippets, reinforcing a Windows-first approach.
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 examples where applicable, to provide platform-neutral alternatives.
  • Explicitly note any limitations or differences for Linux-based Service Fabric clusters, if present.
  • Consider reorganizing examples so that cross-platform methods (e.g., Azure CLI, REST API) are shown before or alongside PowerShell, rather than after.
  • Mention the availability of Service Fabric tools for Linux, such as sfctl, and provide usage examples.
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-02-23 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page discusses Azure Service Fabric node types and their relationship to virtual machine scale sets. While it mentions both Windows and Linux node types in the extension properties, the JSON example and property descriptions show Windows-centric defaults (e.g., 'dataPath': 'D:\\SvcFab', certificate store values), and the 'Next steps' section links primarily to Windows/PowerShell-specific tasks (RDP port range, admin username/password changes) without Linux equivalents or guidance for SSH access. Linux-specific examples and parity in operational guidance are missing.
Recommendations
  • Provide Linux-specific examples for configuration, such as using Linux file paths (e.g., '/var/svcfab') in the 'dataPath' property.
  • Add guidance or links for Linux users on how to remotely connect to cluster nodes (e.g., SSH instructions) alongside RDP/PowerShell examples.
  • Include Linux admin credential management instructions, or clarify if the linked scripts are Windows-only.
  • Ensure property descriptions and extension examples alternate or equally represent Linux and Windows scenarios.
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-02-23 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, PowerShell is a Windows-centric tool, and no equivalent Linux/macOS CLI or scripting examples (such as Bash, Azure CLI, or REST API) are provided. Additionally, PowerShell examples are presented alongside C# and manifest examples, but Linux-native options are missing, creating friction for Linux users. The documentation also mentions that resource monitoring is supported for containerized applications on Linux, but does not provide Linux-specific guidance or examples.
Recommendations
  • Add Azure CLI or Bash script examples for configuring scaling policies, especially for Linux/macOS users.
  • Explicitly mention any limitations or differences for Linux clusters and provide guidance for Linux users.
  • Include REST API usage examples for cross-platform parity.
  • Clarify which PowerShell commands (e.g., Update-ServiceFabricService, New-ServiceFabricService) are available or supported on Linux, or provide alternatives.
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-02-23 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation provides configuration examples for both Windows (ClusterManifest.xml) and cross-platform/standalone (ClusterConfig.json) deployments. However, Windows-specific configuration (ClusterManifest.xml under <WindowsServer>) is presented first and more prominently, and PowerShell examples are included for service management. There is no explicit mention of Linux-specific node configuration or tools, nor are Linux/macOS command-line examples provided. The documentation assumes familiarity with Windows Server concepts and tools, which may create friction for Linux users.
Recommendations
  • Add explicit examples and guidance for Linux-based Service Fabric clusters, including configuration of ClusterManifest.xml for Linux nodes (using <Linux> or <LinuxServer> tags if supported).
  • Provide Linux/macOS command-line equivalents for PowerShell commands (e.g., using sfctl or REST API).
  • Clarify which configuration files and approaches are cross-platform, and highlight Linux-specific differences or requirements.
  • Ensure that Linux node configuration is not only mentioned but also demonstrated alongside Windows examples.
  • Where possible, avoid presenting Windows examples first unless the feature is Windows-only.
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-02-23 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 for managing Service Fabric app load using metrics primarily in C# and PowerShell. PowerShell is a Windows-centric tool, and no equivalent Linux/macOS CLI examples (such as Azure CLI or bash scripts) are provided. The PowerShell examples are presented alongside C# code, but there is no mention of cross-platform alternatives or how Linux users can accomplish the same tasks. This creates friction for Linux/macOS users, as Service Fabric supports Linux clusters and cross-platform management.
Recommendations
  • Add Azure CLI examples for service creation and metric configuration, which are cross-platform and supported on Linux/macOS.
  • Mention and link to documentation about managing Service Fabric clusters from Linux, including REST API usage or SDKs.
  • Clarify which PowerShell commands are available via Azure CLI or REST API, and provide those alternatives where possible.
  • Explicitly state if certain operations are only possible via PowerShell, and provide guidance for Linux users.
  • Consider including bash script examples or references to the Service Fabric CLI (sfctl), which is available on Linux.
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-02-23 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 service tag requirements, but does not offer equivalent examples for Linux/macOS users (e.g., Bash, CLI, or REST API usage). PowerShell is primarily a Windows tool, and its exclusive use creates friction for users on other platforms. The C# API examples are cross-platform, but many administrators expect command-line examples for operational tasks.
Recommendations
  • Add Azure CLI or Bash examples for managing node tags and service tag requirements, if supported.
  • Include REST API usage examples for tag operations, as REST APIs are platform-agnostic.
  • Clarify whether PowerShell commands are available cross-platform (PowerShell Core), and if so, provide guidance for Linux/macOS users.
  • Mention any limitations or alternatives for Linux/macOS users if PowerShell is required.
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-02-23 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page discusses securing Azure Service Fabric clusters, covering both Azure-hosted and standalone Windows clusters. However, it repeatedly references Windows Server clusters and Windows-specific security mechanisms (e.g., Windows security, Kerberos, group Managed Service Accounts) without mentioning or providing equivalent guidance for standalone Linux clusters. Examples and links for standalone clusters are exclusively for Windows, and Linux is only mentioned in passing, with no actionable instructions or references for Linux users.
Recommendations
  • Add explicit guidance and links for securing standalone Linux Service Fabric clusters, including certificate setup and any Linux-specific security mechanisms.
  • Provide parity in examples and walkthroughs for Linux clusters, such as how to generate and install certificates on Linux nodes, and how to configure client-to-node and node-to-node security.
  • Clarify which security scenarios and recommendations apply equally to Linux and Windows, and highlight any differences.
  • If standalone Linux clusters are not supported, state this clearly to avoid confusion.
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-02-23 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 supports cross-platform management, the exclusive use of PowerShell creates friction for Linux/macOS users.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl) for Linux/macOS users.
  • Include REST API examples for health reporting and querying, which are platform-agnostic.
  • Clarify in the example section that PowerShell is Windows-specific and provide links or instructions for Linux/macOS alternatives.
GitHub Create Pull Request
Service Fabric Cluster Resource Manager - Management Integration ...fabric-cluster-resource-manager-management-integration.md
Medium Priority View Details →
Scanned: 2026-02-23 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides a PowerShell example for querying Service Fabric partition health, using a Windows-style prompt and command. No equivalent Linux or cross-platform CLI example is given. The example is presented early in the page, and the use of PowerShell and Windows paths may create friction for Linux/macOS users. However, the rest of the documentation is largely conceptual and platform-neutral.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl) or REST API for Linux/macOS users.
  • Include notes clarifying cross-platform management options and tools.
  • Present examples for both Windows and Linux environments, or use platform-neutral commands where possible.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager: Movement cost ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-movement-cost.md
Medium Priority View Details →
Scanned: 2026-02-23 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 and C# examples for configuring movement cost in Service Fabric, but does not include equivalent Linux/bash/CLI examples. PowerShell is Windows-centric, and its exclusive use creates friction for Linux/macOS users. The order of examples also places Windows tools first, reinforcing Windows bias.
Recommendations
  • Add Azure CLI or bash examples for configuring move cost, where possible.
  • Explicitly mention whether PowerShell commands are supported on Linux/macOS (via PowerShell Core), or provide alternatives.
  • Clarify if certain operations are only possible via PowerShell or C# SDK, and note Linux/macOS limitations if any.
  • Consider including REST API or cross-platform SDK examples for dynamic configuration tasks.
GitHub Create Pull Request
Service Fabric Service sensitivity ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-sensitivity.md
Medium Priority View Details →
Scanned: 2026-02-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides extensive PowerShell examples for configuring service sensitivity and maximum load in Azure Service Fabric, but does not offer equivalent CLI or scripting examples for Linux/macOS users. PowerShell is presented as the primary scripting interface, and no mention is made of cross-platform alternatives such as Azure CLI or REST API. This creates friction for Linux/macOS administrators, who may not have access to PowerShell or prefer other tools.
Recommendations
  • Add Azure CLI examples for all operations currently shown with PowerShell.
  • Mention REST API endpoints or provide relevant REST payloads for cross-platform automation.
  • Clarify whether PowerShell examples are usable on Linux/macOS (e.g., via PowerShell Core), or provide guidance for Linux users.
  • Ensure that scripting examples are balanced, showing both Windows and Linux/macOS approaches where possible.
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-02-23 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 any Azure CLI or Bash equivalents. The application packaging step is described using Visual Studio, a Windows-centric tool, with no mention of cross-platform alternatives. There are no Linux/macOS-specific instructions or examples, and Windows tools and patterns are presented first and exclusively.
Recommendations
  • Add Azure CLI examples for deployment and deletion alongside PowerShell examples.
  • Provide instructions for packaging applications using cross-platform tools (e.g., dotnet CLI, SF tooling, or manual zip commands).
  • Mention and link to Linux/macOS-compatible workflows for staging and uploading application packages (e.g., using az storage blob upload).
  • Present Windows and Linux/macOS examples in parallel, or clarify when steps are Windows-only.
  • Include guidance for users working on non-Windows platforms, such as using VS Code or command-line tools instead of Visual Studio.
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-02-23 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 PowerShell cmdlets for managing Service Fabric services, but does not include equivalent Linux CLI (sfctl) or bash examples. Windows tooling (PowerShell) is mentioned first and exclusively in code samples and links, creating friction for Linux/macOS users who must translate instructions to their platform.
Recommendations
  • Add equivalent examples using sfctl (Service Fabric CLI) for Linux/macOS users alongside PowerShell examples.
  • Mention both PowerShell and sfctl tools in relevant sections, clarifying platform applicability.
  • Provide links to Linux/macOS documentation and tools where PowerShell is referenced.
  • Consider showing Linux/macOS examples before or alongside Windows examples to improve parity.
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-02-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page on upgrading Azure Service Fabric clusters exhibits mild Windows bias. While most upgrade concepts are platform-neutral, several sections reference Windows-specific tools (PowerShell) and link to Windows-only procedures (e.g., patching cluster nodes). Linux equivalents are not mentioned or are referenced after Windows tools. The 'Upgrading OS images for cluster nodes' section links only to Windows patching guidance, omitting Linux guidance. Examples for managing certificates, ports, and other cluster properties mention PowerShell/Azure CLI, but do not clarify Linux support or provide Linux-specific examples.
Recommendations
  • Add explicit references and links to Linux patching/upgrading guidance for Service Fabric clusters, if available.
  • Provide examples for managing certificates, ports, and cluster settings using Azure CLI or other cross-platform tools, and clarify their applicability to Linux clusters.
  • When mentioning PowerShell, also mention Bash/CLI usage for Linux/macOS users, or provide equivalent commands.
  • Ensure that upgrade procedures and automation guidance are clearly marked as Windows-only when applicable, and provide Linux alternatives where 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-02-23 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 scripting examples (e.g., Bash, Azure CLI) for scaling operations. Windows/PowerShell tools are mentioned first and exclusively, creating friction for Linux users who may not have access to PowerShell or prefer native Linux tooling. The only explicit mention of Linux is in the 'Choosing a platform' section, which discusses implementation differences but does not provide Linux-specific operational guidance.
Recommendations
  • Add equivalent Linux examples using Bash, Azure CLI, or REST API calls for scaling operations.
  • Document Linux-native workflows for managing Service Fabric clusters and services.
  • Where PowerShell is referenced, clarify if cross-platform PowerShell Core is supported, or provide alternative instructions for Linux users.
  • Ensure administrative actions (e.g., creating/removing services) are demonstrated with both Windows and Linux tools.
  • Consider listing Linux examples before or alongside Windows examples to improve parity.
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-02-23 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 and executables (e.g., FabricHost.exe, PowerShell cmdlets) are mentioned first or exclusively in several sections. Examples and instructions often reference Windows concepts and tools before Linux equivalents, and some features (like standalone clusters) are only supported on Windows, with Linux support explicitly missing. Linux tools, CLI usage, and Linux-specific guidance are less prominent or missing in some sections.
Recommendations
  • Ensure that Linux equivalents (e.g., CLI commands, Linux service management) are mentioned alongside Windows tools, not just as secondary options.
  • Provide Linux-specific examples and workflows where possible, especially for cluster management, health monitoring, and application lifecycle.
  • Clarify which features are Windows-only and which are cross-platform, and link to Linux-specific documentation when available.
  • Include Linux-first or Linux-parity sections for critical tasks, such as cluster creation, scaling, upgrades, and monitoring.
  • Avoid referencing Windows executables (e.g., FabricHost.exe) without also describing Linux equivalents or noting differences.
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-02-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page shows evidence of Windows bias. It references the Service Fabric SDK schema location using a Windows file path, mentions Visual Studio as a primary packaging tool, and does not provide Linux/macOS equivalents or examples for packaging or deploying guest executables. There are no explicit Linux command-line instructions or references to cross-platform tools, and the directory structure example uses a Windows executable (.exe) without mentioning Linux binaries.
Recommendations
  • Add instructions and examples for packaging and deploying guest executables using Linux/macOS command-line tools.
  • Mention cross-platform alternatives to Visual Studio, such as Azure CLI or Service Fabric CLI (sfctl), and provide sample commands.
  • Reference the schema location for ApplicationManifest.xml and ServiceManifest.xml in a platform-agnostic way, or note the Linux/macOS equivalent if available.
  • Include examples using Linux binaries (e.g., .sh or ELF files) alongside Windows executables (.exe) in the directory structure.
  • Clarify if the packaging process is supported on Linux/macOS, and link to relevant documentation or tools.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Events ...es/service-fabric/service-fabric-diagnostics-events.md
Medium Priority View Details →
Scanned: 2026-02-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page for Azure Service Fabric Events primarily references Windows-specific tools and patterns, such as ETW/Windows Event logs and the Windows Azure diagnostics agent, without mentioning Linux equivalents or providing Linux-specific guidance. Windows tools are mentioned first and exclusively, and there are no examples or instructions for accessing Service Fabric events on Linux clusters.
Recommendations
  • Add documentation on how Service Fabric events are logged and accessed on Linux clusters, including any differences in logging mechanisms (e.g., use of stdout/stderr, syslog, or other Linux-native logging solutions).
  • Provide examples or references for monitoring tools and log aggregation solutions commonly used on Linux, such as Azure Monitor integration for Linux, or instructions for configuring diagnostics on Linux nodes.
  • Clarify whether the EventStore service's REST APIs and Service Fabric Client Library are fully cross-platform, and provide usage examples for Linux environments.
  • If certain features (like ETW/Windows Event logs) are Windows-only, explicitly state this and offer Linux alternatives or workarounds.
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-02-23 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 (e.g., Bash, Azure CLI) examples. Windows tools and patterns (PowerShell, ApplicationManifest.xml, Visual Studio) are mentioned before Linux alternatives, and Linux-specific limitations are discussed but not accompanied by Linux-centric guidance or examples. The documentation assumes Windows-centric workflows, creating friction for Linux users.
Recommendations
  • Add Azure CLI or Bash examples for setting DNS names and managing Service Fabric services, especially for Linux clusters.
  • Include guidance for Linux users on how to perform equivalent tasks (e.g., using ARM templates, Docker Compose, or REST APIs) instead of PowerShell.
  • Clarify Linux limitations and provide workarounds or links to Linux-specific documentation.
  • Present Windows and Linux options side-by-side or clearly indicate which steps are Windows-only and which are cross-platform.
GitHub Create Pull Request
← Previous Page 39 of 99 Next →