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 1951-1975 of 2475 flagged pages
Service Fabric Architecture of Azure Service Fabric ...articles/service-fabric/service-fabric-architecture.md
Medium Priority View Details →
Scanned: 2026-02-03 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page on Azure Service Fabric architecture references PowerShell cmdlets as the primary example of management tooling, and mentions Windows security as a transport option before X509 certificates. No Linux-specific management tools or examples are provided, and PowerShell is referenced without mention of cross-platform alternatives, creating a subtle Windows-first bias.
Recommendations
  • Explicitly mention cross-platform management options, such as Azure CLI or REST APIs, alongside PowerShell cmdlets.
  • Clarify that PowerShell is available on Linux/macOS, or provide equivalent Linux/macOS command examples where appropriate.
  • When discussing security, list X509 certificates before or alongside Windows security, and note Linux compatibility.
  • Add a brief note or section highlighting how Linux users can interact with Service Fabric clusters, including supported tools and workflows.
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-03 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides several PowerShell-based examples and instructions (e.g., using Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState) without mentioning or providing Linux/macOS equivalents. There is an implicit assumption that users are operating in a Windows environment, and no CLI or bash alternatives are given. This creates friction for Linux/macOS users, especially when performing manual scaling operations.
Recommendations
  • For every PowerShell command (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState), provide equivalent instructions using the Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • Explicitly mention that the PowerShell commands are for Windows and link to Linux/macOS alternatives where available.
  • Add bash or CLI examples for common scaling operations, or reference official documentation for Linux/macOS users.
  • Clarify in the relevant sections that both Windows and Linux clusters are supported, and provide parity in operational guidance.
GitHub Create Pull Request
Service Fabric Learn about Azure Service Fabric application security ...ric/service-fabric-application-and-service-security.md
Medium Priority View Details →
Scanned: 2026-02-03 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation generally covers Service Fabric security concepts in a cross-platform manner, but several sections show a Windows-first bias. Examples and references to Windows-specific features (Active Directory, gMSA, BitLocker) are given before or in more detail than Linux equivalents. Some features (like disk encryption) only link to Windows/PowerShell guides, with Linux instructions missing or marked as TODO. There are few explicit Linux examples or parity notes for key scenarios.
Recommendations
  • Add explicit Linux examples for disk encryption and securing application data at rest, including links to relevant Azure documentation for Linux VMSS disk encryption.
  • Where Windows-specific features (e.g., gMSA, AD accounts) are mentioned, clarify their platform scope and provide Linux alternatives or state if not applicable.
  • Ensure that API gateway and container security sections include Linux-specific guidance and examples, especially for certificate management.
  • Review all example code and configuration snippets to ensure they are platform-neutral or provide both Windows and Linux variants where appropriate.
  • Update TODOs (e.g., 'Encrypt disks on Linux clusters?') with actual guidance or links to Linux documentation.
GitHub Create Pull Request
Service Fabric Application upgrade: upgrade parameters ...abric/service-fabric-application-upgrade-parameters.md
Medium Priority View Details →
Scanned: 2026-02-03 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page presents PowerShell and Visual Studio (Windows-centric tools) parameters and workflows first, with more detailed tables and examples, before covering the cross-platform Service Fabric CLI (sfctl) approach. PowerShell-specific parameters and patterns are described in detail, while Linux/macOS users (who would use sfctl) receive less prominent placement and fewer usage examples. There are no explicit Linux/macOS command-line examples in the main body, and the CLI section is less detailed. The 'Next steps' section does link to Linux/sfctl and Eclipse plugin guides, but the primary focus remains on Windows tools.
Recommendations
  • Reorder sections so that cross-platform tools (sfctl) are presented before or alongside Windows-specific tools (PowerShell, Visual Studio).
  • Provide equally detailed parameter tables and usage examples for sfctl, including example commands for common upgrade scenarios.
  • Explicitly mention that sfctl is the recommended approach for Linux/macOS users, and clarify tool parity.
  • Where PowerShell-specific syntax is shown (e.g., hashtable examples), provide equivalent JSON or CLI examples for sfctl.
  • Add a short summary table at the top comparing the three main upgrade methods (PowerShell, Visual Studio, sfctl) and their platform compatibility.
GitHub Create Pull Request
Service Fabric Service Fabric application upgrade ...s/service-fabric/service-fabric-application-upgrade.md
Medium Priority View Details →
Scanned: 2026-02-03 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 demonstrates a notable Windows bias. The only code example provided uses PowerShell cmdlets, which are traditionally Windows-centric and may not work natively on Linux/macOS clusters. References to Windows-specific tools (e.g., http.sys, PowerShell, Visual Studio) are present throughout the page, with no equivalent Linux or cross-platform instructions. The 'Next steps' section prioritizes Windows tooling (Visual Studio, PowerShell) and omits guidance for Linux users or Service Fabric CLI usage.
Recommendations
  • Provide equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • Include notes or sections clarifying how Linux/macOS users can perform application upgrades, including any differences in workflow or tooling.
  • Add references to Linux-compatible tools and patterns (e.g., bash scripts, sfctl commands) alongside or before Windows/PowerShell examples.
  • Ensure that upgrade scenarios involving http.sys or other Windows-only APIs are clearly marked as Windows-specific, and offer Linux alternatives or caveats where appropriate.
  • Expand 'Next steps' to include tutorials for upgrading applications using cross-platform tools.
GitHub Create Pull Request
Service Fabric Understanding periodic backup configuration ...-fabric-backuprestoreservice-configure-periodic-backup.md
Medium Priority View Details →
Scanned: 2026-02-03 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page for configuring periodic backups in Azure Service Fabric is generally platform-neutral, but the only on-premises backup storage example provided is for Windows file shares (with Integrated Windows Authentication and UNC paths). There are no examples or mentions of Linux-compatible storage options (such as NFS or SMB with Linux authentication), nor guidance for Linux clusters. This may create friction for Linux users deploying standalone Service Fabric clusters.
Recommendations
  • Add examples for configuring backup storage using Linux-compatible file shares, such as NFS mounts or SMB shares accessed from Linux nodes.
  • Clarify whether the FileShare storage option supports Linux clusters and, if so, provide authentication and path examples relevant to Linux environments.
  • Explicitly state any platform limitations for backup storage types (e.g., if FileShare is Windows-only, mention alternatives for Linux).
  • Consider including a note or section on best practices for backup storage configuration on Linux-based Service Fabric clusters.
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-03 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 for restoring backups in Azure Service Fabric is heavily focused on PowerShell-based workflows, with all CLI/API examples provided exclusively in PowerShell syntax. The prerequisite section requires installation of a PowerShell module, and all command-line instructions use PowerShell cmdlets or scripts. There are no examples or guidance for Linux/macOS users, such as using Bash, curl, or cross-platform tools. The documentation implicitly assumes a Windows environment and does not mention alternatives for non-Windows platforms.
Recommendations
  • Add equivalent examples using Bash and curl for REST API calls, demonstrating how Linux/macOS users can perform the same operations.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is required for all platforms, and if not, provide platform-specific instructions.
  • Explicitly mention cross-platform support and provide guidance for Linux/macOS users, including any required authentication steps (e.g., certificate handling) in Bash.
  • If Service Fabric supports REST API calls directly, provide generic HTTP request examples that do not depend on PowerShell.
  • Reorder examples so that REST API usage is shown first, followed by platform-specific tooling.
GitHub Create Pull Request
Service Fabric Azure Service Fabric infrastructure as Code Best Practices ...tps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-best-practices-infrastructure-as-code.md
Medium Priority View Details →
Scanned: 2026-02-03 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Service Fabric clusters, but PowerShell is featured prominently and exclusively for several critical operations (e.g., cluster upgrade). Windows-specific configuration details, such as registry keys and Windows Update settings, are described without Linux equivalents or guidance. The upgrade instructions rely solely on PowerShell, with no Linux shell or cross-platform alternatives provided. Windows-related tools and patterns (registry, PowerShell, WindowsUpdate) are mentioned before or instead of Linux approaches.
Recommendations
  • Provide equivalent Linux shell (bash) commands for cluster upgrade operations currently shown only in PowerShell.
  • Include Linux-specific configuration guidance for disabling automatic updates or managing patching, analogous to the Windows registry and WindowsUpdate settings.
  • Where Windows-specific instructions are given (e.g., registry keys), clarify if/how Linux users should perform similar steps or state that no action is needed.
  • Balance example order: present Azure CLI and Linux shell examples before or alongside PowerShell/Windows examples.
  • Explicitly call out differences or limitations between Windows and Linux clusters in relevant sections.
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-03 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation generally covers both Windows and Linux scenarios for Service Fabric security, but there is a tendency to present Windows-specific tools and examples first, such as PowerShell commands for certificate management and encryption. Windows Defender and Windows security baselines are discussed in detail, while Linux equivalents are either omitted or referenced only briefly. Some sections (e.g., Windows Defender) are Windows-only by nature, but others could provide more Linux parity.
Recommendations
  • Present Windows and Linux examples side-by-side or alternate which is shown first to avoid implicit prioritization.
  • For sections like security baselines and antivirus, mention recommended Linux equivalents (e.g., CIS benchmarks, ClamAV, or other Linux security tools) and link to relevant documentation.
  • Where PowerShell is used for Windows, provide equivalent Bash/openssl commands for Linux where possible, or link to Linux-specific guides.
  • Clarify when a feature or recommendation is Windows-only, and provide Linux alternatives or explicitly state when no equivalent exists.
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-03 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 samples in C# and PowerShell only, with no mention of Linux command-line equivalents or cross-platform CLI tools. PowerShell is a Windows-centric tool, and its use throughout the examples suggests a Windows-first approach. There is no guidance for Linux/macOS users on how to perform these tasks, nor are alternatives like Azure CLI or REST API referenced.
Recommendations
  • Add equivalent examples using Azure CLI, which is cross-platform and widely used on Linux/macOS.
  • Include REST API or ARM template snippets for placement policy configuration, as these are OS-agnostic.
  • Explicitly mention how Linux/macOS users can perform these operations, or link to relevant cross-platform tooling.
  • Clarify if PowerShell Core (pwsh) is supported for these commands, and provide examples if so.
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-03 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 provides both Windows and Linux references for Service Fabric networking, but there is a notable Windows-first bias in several sections. PowerShell is mentioned as the primary API client, and Windows-specific tools and examples (such as netsh and RDP) are referenced without equivalent Linux commands or alternatives. Some examples and ARM templates are Windows-focused, and Linux-specific guidance is less detailed or omitted.
Recommendations
  • Include Linux CLI (az, bash) examples alongside or before PowerShell examples, especially for common operations.
  • Provide Linux equivalents for Windows-specific tools (e.g., show how to check dynamic port ranges on Linux).
  • Reference Linux-focused ARM templates and sample clusters where appropriate.
  • Clarify when instructions or examples apply only to Windows, and provide parallel Linux guidance where possible.
  • Ensure that application networking and security sections mention Linux container scenarios and tools (e.g., iptables, SSH, Linux firewall configuration).
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-02-03 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides command-line examples exclusively using PowerShell cmdlets for Service Fabric application management tasks, with no mention of Linux shell equivalents or cross-platform CLI tools. This creates friction for Linux/macOS users, as PowerShell is a Windows-centric tool and the Service Fabric CLI (sfctl), which is cross-platform, is not referenced. All automation and scripting examples are either PowerShell or C#, with no Bash or sfctl usage.
Recommendations
  • Add equivalent examples using the Service Fabric CLI (sfctl), which is supported on Linux and macOS.
  • Include Bash shell examples for common tasks where appropriate.
  • Clarify which commands are Windows-only and provide cross-platform alternatives where possible.
  • Add a note about platform support for PowerShell cmdlets and recommend sfctl for Linux/macOS users.
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-03 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, with PowerShell being the only CLI example shown for service creation and metric configuration. There are no equivalent examples for Linux/macOS users (e.g., Azure CLI, Bash, or REST API), and PowerShell is presented as the default scripting interface. This creates friction for users managing Service Fabric clusters from non-Windows platforms.
Recommendations
  • Add Azure CLI or REST API examples for service creation and metric configuration, alongside PowerShell.
  • Explicitly mention cross-platform management options for Service Fabric (e.g., Azure CLI, REST API, or Service Fabric CLI).
  • Clarify when PowerShell is required and provide guidance for Linux/macOS users on alternative workflows.
  • Reorder examples so that platform-neutral options (e.g., REST API, Azure CLI) are presented before or alongside PowerShell.
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-03 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 creating and updating Service Fabric services with move cost, but does not offer equivalent CLI or bash examples for Linux/macOS users. PowerShell is a Windows-centric tool, and its use as the sole shell example creates friction for users managing Service Fabric clusters from Linux or macOS. The C# API examples are cross-platform, but operational/management examples are Windows-first and lack Linux parity.
Recommendations
  • Add Azure CLI or REST API examples for creating and updating Service Fabric services with move cost, as these are cross-platform and commonly used on Linux/macOS.
  • If PowerShell is required, clarify whether PowerShell Core is supported on Linux/macOS and provide usage notes.
  • Explicitly mention management options for Linux/macOS users, such as Service Fabric CLI (sfctl) or REST API, and provide equivalent examples.
  • Reorder examples so that cross-platform options appear before or alongside Windows-specific tools.
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-03 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides configuration and code examples for describing and managing Service Fabric clusters using Cluster Resource Manager. While the concepts are platform-neutral, the examples and tooling references show a notable Windows bias: PowerShell and WindowsServer XML configuration are presented first and more prominently, with no equivalent Linux CLI or Bash examples. The documentation does not mention Linux-specific configuration patterns or Service Fabric management tools, nor does it clarify how Linux users should adapt the PowerShell or WindowsServer examples.
Recommendations
  • Add Linux/Bash CLI examples alongside PowerShell for service creation and updates (e.g., using sfctl or REST API).
  • Include configuration snippets for Linux-based Service Fabric clusters (e.g., referencing 'Linux' infrastructure in ClusterManifest.xml or clarifying differences).
  • Explicitly state which examples are Windows-only and provide guidance or links for Linux users.
  • Where PowerShell is shown, add equivalent Linux command-line or API usage to ensure parity.
  • Clarify any platform-specific limitations or differences in resource manager behavior.
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-03 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides a PowerShell example (Get-ServiceFabricPartitionHealth) for querying health information, but does not include equivalent examples for Linux/macOS environments or Service Fabric CLI (sfctl). The only command-line example is Windows/PowerShell-specific, and there is no mention of cross-platform tools or commands.
Recommendations
  • Add equivalent examples using the Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS as well as Windows.
  • When showing command-line examples, provide both PowerShell and sfctl (or REST API) usage, or at least mention the cross-platform alternatives.
  • Explicitly state which tools/commands are Windows-only and which are available cross-platform.
  • Consider showing Linux/macOS commands first or side-by-side with Windows examples to promote parity.
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-03 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 managing node tags and service requirements, but does not offer equivalent CLI or script examples for Linux/macOS users. PowerShell is featured first and exclusively as the command-line interface, with no mention of Service Fabric CLI (sfctl) or REST API usage from non-Windows platforms. This creates friction for Linux/macOS administrators who may not have access to PowerShell or prefer native tools.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and commonly used on Linux/macOS.
  • Include REST API example commands (e.g., using curl) for adding/removing node tags and updating service requirements.
  • Clarify which tools are available on which platforms, and provide guidance for Linux/macOS users on how to perform these tasks.
  • Consider reordering examples so that cross-platform tools (sfctl, REST API) are presented before or alongside PowerShell.
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-02-03 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 exclusively referencing PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) and linking to Windows Server-specific instructions. There are no examples or guidance for Linux-based standalone clusters, nor are Linux tools or commands mentioned. This creates friction for users deploying Service Fabric on non-Windows environments.
Recommendations
  • Add equivalent Linux instructions and examples for scaling standalone clusters, including relevant shell commands and configuration steps.
  • Reference cross-platform tools or clarify if only Windows is supported for standalone clusters.
  • Explicitly state platform limitations if standalone clusters are Windows-only, or provide parity where Linux is supported.
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-03 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides upgrade guidance for Azure Service Fabric clusters in a generally platform-neutral manner, but several sections and references show a mild Windows bias. PowerShell and Azure CLI are mentioned as command-line options, but PowerShell is listed first. The only OS patching guidance linked is for Windows clusters, and the Patch Orchestration Application (POA) is described as a Windows patching solution, with no mention of Linux equivalents or guidance. References to NTLM settings and FileStoreService are Windows-centric, and there is no explicit Linux example or mention of Linux-specific upgrade considerations.
Recommendations
  • Include explicit Linux upgrade guidance or links for Service Fabric clusters running on Linux nodes, especially for OS patching and cluster management.
  • When mentioning PowerShell/Azure CLI, clarify which commands are cross-platform and provide bash examples where relevant.
  • Add references or links to Linux-specific Service Fabric documentation, such as patching, certificate management, and node configuration.
  • If certain features (like POA) are Windows-only, clarify this and provide Linux alternatives or state the limitations.
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-03 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides configuration examples using XML, JSON, PowerShell, and C# APIs. PowerShell is featured prominently as the only CLI example for dynamic configuration, with no equivalent Linux/macOS CLI (e.g., Azure CLI, REST API, or cross-platform Service Fabric CLI) examples. PowerShell examples are shown before C# API examples, and there is no mention of Linux tools or workflows for managing service sensitivity, which may create friction for Linux/macOS users managing Service Fabric clusters.
Recommendations
  • Add equivalent examples using cross-platform tools such as Azure CLI, Service Fabric CLI (sfctl), or REST API for setting service sensitivity and maximum load.
  • Clarify whether PowerShell examples are required for all environments, or if Linux/macOS users should use alternative tools.
  • Reorder examples so that cross-platform methods (e.g., CLI, REST) are presented before or alongside PowerShell.
  • Explicitly mention Linux/macOS management options if available, or provide guidance for non-Windows users.
GitHub Create Pull Request
Service Fabric Upgrade an Azure Service Fabric standalone cluster ...ce-fabric/service-fabric-cluster-upgrade-standalone.md
Medium Priority View Details →
Scanned: 2026-02-03 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page for upgrading an Azure Service Fabric standalone cluster exhibits a moderate Windows bias. References and links to upgrade instructions and configuration changes point specifically to Windows Server documentation (e.g., 'service-fabric-cluster-upgrade-windows-server.md', 'service-fabric-cluster-config-upgrade-windows-server.md'). The patch orchestration application is described only for Windows, with no mention of Linux equivalents or instructions. There are no explicit Linux examples or guidance, and Windows terminology/tools are referenced exclusively.
Recommendations
  • Add equivalent documentation and examples for Linux-based Service Fabric standalone clusters, if supported.
  • Clarify in the introduction whether Linux standalone clusters are supported and, if not, explicitly state this to avoid confusion.
  • Where possible, provide links to Linux-specific upgrade/configuration instructions or note any feature gaps.
  • Include examples of configuration files, upgrade steps, and patch orchestration for Linux clusters if applicable.
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-03 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 the Azure Service Fabric application resource model demonstrates several Windows-centric biases. All command-line deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) with no mention of Azure CLI equivalents. The application packaging workflow is described using Visual Studio, a Windows-focused IDE, and screenshots show Windows file paths and UI. 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, upgrade, and deletion steps alongside PowerShell examples.
  • Include instructions for packaging Service Fabric applications using cross-platform tools (e.g., dotnet CLI, SF SDK on Linux/macOS) and mention alternatives to Visual Studio.
  • Provide screenshots or descriptions for Linux/macOS workflows (e.g., file system paths, terminal commands).
  • Clearly indicate which steps are platform-agnostic and which require Windows-specific tooling, and suggest 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-03 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides code examples for scaling Service Fabric services using C# and PowerShell, but omits equivalent Linux CLI (sfctl) or bash examples. PowerShell is a Windows-centric tool, and its exclusive use in examples and references creates friction for Linux users. The documentation also references administrative actions using PowerShell cmdlets before mentioning programmatic APIs, and does not provide Linux-specific guidance or parity in operational instructions.
Recommendations
  • Add equivalent Linux CLI (sfctl) or bash examples alongside PowerShell examples for all administrative tasks.
  • Explicitly mention Linux tooling (sfctl, REST API) in sections discussing service creation, updates, and management.
  • Clarify which tools are cross-platform and which are Windows-only, and provide links or guidance for Linux users.
  • Consider reordering examples so that platform-neutral or Linux examples are presented alongside or before Windows/PowerShell examples.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Docker Compose Deployment Preview ...ticles/service-fabric/service-fabric-docker-compose.md
Medium Priority View Details →
Scanned: 2026-02-03 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both PowerShell and Service Fabric CLI (sfctl) examples for deploying Docker Compose files on Azure Service Fabric. However, PowerShell examples are presented first, with more detailed command breakdowns, and PowerShell is a Windows-centric tool. There are no explicit Linux shell (e.g., Bash) or macOS Terminal examples, nor is there mention of Linux-specific patterns or tools. The CLI (sfctl) is cross-platform, but its usage is described after PowerShell and with less detail.
Recommendations
  • Present CLI (sfctl) examples before or alongside PowerShell examples to emphasize cross-platform support.
  • Explicitly mention that sfctl works on Linux/macOS and provide example commands in a Linux shell context (e.g., Bash).
  • Clarify any platform requirements for PowerShell commands and recommend CLI usage for non-Windows users.
  • Add a brief section or note for Linux/macOS users, highlighting installation and usage of sfctl.
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-03 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 page provides a broad overview of Azure Service Fabric, covering both Windows and Linux support. However, there is a noticeable Windows bias in several areas: Windows terminology and executables (e.g., FabricHost.exe) are described first and in detail, with Linux equivalents only mentioned later or not at all. PowerShell is frequently referenced as a primary management tool, with CLI and REST APIs listed after. Standalone cluster creation is described only for Windows, with Linux standalone clusters explicitly noted as unsupported. Examples and instructions tend to use Windows-centric tools and patterns, and Linux-specific workflows or examples are generally missing or referenced second.
Recommendations
  • Provide equal prominence to Linux workflows and tools, especially in sections describing cluster nodes, management, and health monitoring.
  • Include Linux-specific examples and instructions where possible, such as using Linux CLI tools, shell commands, and Linux service management patterns.
  • Clarify when features or instructions are Windows-only, and offer Linux alternatives or workarounds if available.
  • In lists of management tools (PowerShell, CLI, REST), present CLI and REST APIs before or alongside PowerShell to avoid implying PowerShell is the primary or preferred method.
  • Add links or references to Linux-focused documentation or quickstarts where available.
GitHub Create Pull Request
← Previous Page 79 of 99 Next →