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 826-850 of 2475 flagged pages
Service Fabric Service Fabric Explorer blocking operations ...ged-cluster-service-fabric-explorer-blocking-operation.md
Medium Priority View Details →
Scanned: 2026-02-26 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides management guidance for Service Fabric Explorer and ARM-managed clusters. It consistently recommends Az PowerShell cmdlets for resource operations, with only brief mention of the Azure CLI (az resource) for deleting applications. Most examples and links are PowerShell-focused, and PowerShell tools are mentioned before Azure CLI equivalents, which are more cross-platform and commonly used on Linux/macOS.
Recommendations
  • Add Azure CLI equivalents for all PowerShell cmdlet examples, especially for creating and deleting applications, services, and application type versions.
  • Present Azure CLI and PowerShell examples side-by-side or indicate both options equally, rather than defaulting to PowerShell.
  • Clarify that Azure CLI commands are fully supported on Linux/macOS and provide links to relevant CLI documentation.
  • Review links to ensure both PowerShell and CLI documentation are referenced.
GitHub Create Pull Request
Service Fabric Monitor Azure Service Fabric ...main/articles/service-fabric/monitor-service-fabric.md
Medium Priority View Details →
Scanned: 2026-02-26 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation generally covers both Windows and Linux Service Fabric clusters, but there are several instances where Windows tools, terminology, or examples are presented first or exclusively. Windows-specific tools (Event Log, EventStore APIs, Diagnostics Agent) are mentioned with more detail, while Linux equivalents are referenced but not explained or linked as thoroughly. Some sections provide Windows configuration steps or references before Linux, and Linux-specific guidance is sometimes relegated to a single sentence or external link. There are also missing Linux-specific examples for certain monitoring scenarios.
Recommendations
  • Ensure Linux monitoring tools and configuration steps are described with equal detail and clarity as Windows equivalents.
  • Provide Linux-specific examples (e.g., using LTTng, Syslog, or other Linux-native tools) alongside Windows/PowerShell examples.
  • When referencing tools or APIs (e.g., EventStore, Diagnostics Agent), clarify their availability and alternatives for Linux clusters.
  • Avoid presenting Windows tools or terminology first unless the feature is Windows-only; use neutral or parallel structure.
  • Add links to Linux-focused tutorials and documentation where available, matching the depth of Windows guidance.
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-26 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page for restoring backup in Azure Service Fabric is heavily biased towards Windows/PowerShell usage. All code examples and instructions rely exclusively on PowerShell commands and modules (e.g., Microsoft.ServiceFabric.Powershell.Http), with no mention of Linux/macOS-compatible tools or CLI equivalents. There are no Bash, Azure CLI, or cross-platform REST API examples outside of PowerShell scripting. This creates friction for Linux/macOS users, who may not have access to PowerShell or the required modules.
Recommendations
  • Add Azure CLI examples for backup and restore operations, where possible.
  • Provide generic REST API examples using curl or HTTPie for Linux/macOS users.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is available cross-platform, and if not, suggest alternatives.
  • Include Bash shell scripts or instructions for Linux/macOS environments.
  • Mention any prerequisites or limitations for Linux/macOS users explicitly.
GitHub Create Pull Request
Service Fabric Describing Azure Service Fabric apps and services ...ic/service-fabric-application-and-service-manifests.md
Medium Priority View Details →
Scanned: 2026-02-26 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation contains evidence of Windows bias. It references Windows file paths (e.g., 'C:\Program Files\Microsoft SDKs\Service Fabric\schemas\ServiceFabricServiceModel.xsd') and recommends using Visual Studio, a Windows-centric tool, for authoring manifests. Additionally, it mentions the ServiceFabric PowerShell module for service creation, without providing Linux/bash equivalents or clarifying cross-platform alternatives. Windows-specific terminology and tools are presented first or exclusively, while Linux/macOS options are not discussed.
Recommendations
  • Provide equivalent instructions for Linux/macOS users, such as referencing the location of Service Fabric schema files on non-Windows systems.
  • Suggest cross-platform editors (e.g., VS Code) and explain how to enable XML schema validation and IntelliSense for manifest files.
  • Mention and provide examples for using Service Fabric CLI (sfctl) or REST APIs for service creation and management, alongside PowerShell.
  • Clarify any differences in file paths, tooling, or workflows for Linux/macOS clusters and developers.
  • Explicitly state if certain steps are Windows-only, and provide Linux alternatives where possible.
GitHub Create Pull Request
Service Fabric Application lifecycle in Service Fabric ...service-fabric/service-fabric-application-lifecycle.md
Medium Priority View Details →
Scanned: 2026-02-26 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page for the Service Fabric application lifecycle consistently references PowerShell cmdlets and Windows-centric tooling (e.g., PowerShell commands, .NET APIs) as primary examples for operational tasks such as deployment, upgrade, and removal. REST API alternatives are mentioned, but PowerShell is often listed first and no Linux-specific CLI examples (such as Azure CLI or sfctl) are provided for these workflows. This creates friction for Linux/macOS users, as they must infer how to perform these actions using cross-platform tools.
Recommendations
  • Add explicit examples using Azure CLI and sfctl for all operational tasks (deploy, upgrade, remove, etc.), especially where PowerShell cmdlets are currently used.
  • Where multiple tooling options exist, list cross-platform tools (Azure CLI, sfctl, REST API) before Windows-specific tools (PowerShell).
  • Clarify which tools are cross-platform and which are Windows-only, to help users choose appropriate options.
  • Include sample command lines for Linux/macOS environments alongside PowerShell examples.
GitHub Create Pull Request
Service Fabric Application upgrade: upgrade parameters ...abric/service-fabric-application-upgrade-parameters.md
Medium Priority View Details →
Scanned: 2026-02-26 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page presents Windows/PowerShell and Visual Studio parameters and examples before Linux equivalents (SFCTL), and provides more detailed parameter tables and explanations for PowerShell and Visual Studio. SFCTL (the cross-platform CLI) is covered in a separate section with less detail and fewer examples. The page structure and example order favor Windows tools, which may create friction for Linux/macOS users.
Recommendations
  • Present SFCTL (Service Fabric CLI) parameters and examples alongside PowerShell/Visual Studio, not after them, to avoid Windows-first ordering.
  • Provide equally detailed parameter tables and usage examples for SFCTL as are given for PowerShell.
  • Add explicit Linux/macOS usage examples for SFCTL, including sample commands and parameter formats.
  • Clarify that SFCTL is the recommended cross-platform tool for Linux/macOS users.
  • Consider a summary table comparing all upgrade methods (PowerShell, Visual Studio, SFCTL, REST) with OS/platform applicability.
GitHub Create Pull Request
Service Fabric Understanding periodic backup configuration ...-fabric-backuprestoreservice-configure-periodic-backup.md
Medium Priority View Details →
Scanned: 2026-02-26 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page is generally platform-neutral, focusing on Azure Service Fabric's backup configuration. However, in the section describing file share backup storage, only Windows-style UNC paths (\\StorageServer\BackupStore) and Windows authentication methods are mentioned, with no examples or guidance for Linux-based file shares (e.g., Samba/CIFS or NFS). There are no PowerShell or Windows command-line examples, but the file share section implicitly assumes Windows environments.
Recommendations
  • Add examples and guidance for configuring file share backup storage using Linux-based file shares (e.g., Samba/CIFS or NFS), including path formats and authentication options.
  • Clarify whether Linux clusters can use file share backup storage and, if so, provide relevant instructions.
  • Mention any limitations or requirements for Linux/macOS clusters regarding file share backup storage.
  • If file share backup is Windows-only, explicitly state this to avoid confusion for Linux users.
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-26 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides several manual scaling steps exclusively using PowerShell commands (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState) without Linux CLI or cross-platform alternatives. Windows/PowerShell tooling is referenced first and exclusively in procedural sections, creating friction for Linux users. No Linux-specific commands or guidance are given for equivalent operations, despite Service Fabric supporting Linux clusters.
Recommendations
  • Add equivalent Linux CLI commands (e.g., Azure CLI, Bash scripts, or Service Fabric CLI) for node management and scaling operations.
  • Explicitly note which commands are Windows-only and provide cross-platform alternatives where possible.
  • Reorder procedural sections to present cross-platform or Linux options alongside Windows/PowerShell examples.
  • Clarify whether PowerShell commands can be run on Linux (via PowerShell Core), and if so, provide guidance; otherwise, offer native Linux instructions.
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-26 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides a general overview of Service Fabric application security, but several sections show Windows bias. Windows-specific features (such as Active Directory domain accounts, gMSA, BitLocker, and PowerShell disk encryption) are mentioned or linked, while Linux equivalents are either missing or referenced only as TODOs. Examples and instructions often default to Windows terminology and tools, with Linux guidance less prominent or absent.
Recommendations
  • Add explicit Linux examples and instructions for disk encryption (currently only PowerShell/BitLocker/Windows are mentioned, Linux is a TODO).
  • Ensure parity in describing how to run services under different accounts on Linux clusters, not just Windows (e.g., clarify Linux user/group management in manifests).
  • Include Linux-specific guidance for certificate management and container security (expand on how certificates are handled in Linux clusters).
  • Where Windows tools (e.g., PowerShell) are referenced, provide equivalent Linux commands (e.g., Bash, CLI) and link to relevant documentation.
  • Review all sections for Windows-first language and ensure Linux options are presented equally, not as afterthoughts or TODOs.
GitHub Create Pull Request
Service Fabric Advanced Application Upgrade Topics ...-fabric/service-fabric-application-upgrade-advanced.md
Medium Priority View Details →
Scanned: 2026-02-26 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page for 'Advanced Application Upgrade Topics' in Azure Service Fabric heavily features PowerShell cmdlets for all procedural examples and upgrade operations. There are no CLI, Bash, or Linux-native tool examples provided, nor is it clarified whether these PowerShell commands are cross-platform or Windows-only. The documentation assumes PowerShell usage and does not mention or link to Linux/macOS equivalents or alternatives, creating friction for non-Windows users.
Recommendations
  • Add Azure CLI examples for all upgrade operations alongside PowerShell examples, or clarify if PowerShell cmdlets are cross-platform.
  • Explicitly state which commands/tools are available on Linux/macOS and provide links to relevant documentation.
  • Include Bash or shell script examples where applicable, especially for ARM template deployments.
  • Mention any limitations or prerequisites for Linux/macOS users when using Service Fabric upgrade features.
  • Reorganize examples so that cross-platform tools (e.g., Azure CLI, REST API) are shown before or alongside PowerShell.
GitHub Create Pull Request
Service Fabric Application upgrade: data serialization ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-application-upgrade-data-serialization.md
Medium Priority View Details →
Scanned: 2026-02-26 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page primarily discusses data serialization in the context of Azure Service Fabric, which is cross-platform. However, in the 'Next steps' section, upgrade tutorials are presented first for Visual Studio (a Windows-centric IDE) and PowerShell (primarily a Windows tool, though available on Linux). There is no mention of Linux-native tools or CLI-based upgrade workflows, nor are Linux/macOS-specific examples provided. The serialization discussion is focused on C# and .NET, but Service Fabric supports .NET Core, which is cross-platform.
Recommendations
  • Add explicit references and links to Linux/macOS upgrade workflows using Azure CLI or Service Fabric CLI (sfctl), if available.
  • Include examples or tutorials for upgrading applications on Linux/macOS environments.
  • Clarify that PowerShell is available cross-platform, but also mention native Linux tools where applicable.
  • Consider providing parity in example ordering (e.g., Visual Studio, then CLI, then PowerShell) to avoid Windows-first impression.
GitHub Create Pull Request
Service Fabric On-demand backup in Azure Service Fabric ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-backup-restore-service-ondemand-backup.md
Medium Priority View Details →
Scanned: 2026-02-26 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page for on-demand backup in Azure Service Fabric exclusively provides PowerShell-based examples and instructions, including module installation and REST API usage via PowerShell. There are no examples or guidance for Linux/macOS users (e.g., Bash, Azure CLI, curl), and the prerequisite steps assume a Windows environment. This creates friction for non-Windows users, as Service Fabric clusters can be managed from Linux/macOS as well.
Recommendations
  • Add equivalent Bash or Azure CLI examples for REST API calls (e.g., using curl or az rest).
  • Clarify if the Microsoft.ServiceFabric.Powershell.Http module is required only for Windows, and provide alternatives for Linux/macOS users.
  • Include instructions for connecting to Service Fabric clusters from Linux/macOS (e.g., using certificate files and curl).
  • Present cross-platform examples side-by-side, or indicate which steps are Windows-specific.
  • Mention any limitations or differences for Linux/macOS users explicitly.
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-26 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides PowerShell examples for configuring move cost, but does not offer equivalent Linux/Unix shell or CLI examples. PowerShell is primarily a Windows tool, and its usage is presented before any mention of cross-platform alternatives. There are no Linux-specific instructions or examples for users managing Service Fabric clusters on Linux nodes.
Recommendations
  • Add Azure CLI or Bash examples for configuring move cost, especially for cluster operations that can be performed from Linux/macOS.
  • Clarify whether PowerShell commands are available cross-platform (e.g., via PowerShell Core), or provide guidance for Linux users.
  • Include notes or links to Linux-specific documentation for Service Fabric cluster management.
  • Ensure that configuration file examples (ClusterManifest.xml, ClusterConfig.json) are accompanied by instructions relevant to Linux deployments.
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-26 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page provides networking best practices for Azure Service Fabric clusters and covers both Windows and Linux scenarios. However, there is a notable bias toward Windows: PowerShell and Windows-specific tools are referenced more frequently and often before Linux equivalents. Some examples and links are Windows-focused, and Linux-specific guidance is less detailed or referenced later. Several sections (e.g., API access, DevOps, port usage) mention Windows tools or patterns first, and Linux examples are sometimes missing or less emphasized.
Recommendations
  • Ensure Linux CLI examples are provided alongside PowerShell examples, especially for cluster management and networking configuration.
  • When referencing tools (e.g., PowerShell), mention Linux equivalents (e.g., Azure CLI, Bash scripts) and provide links or examples.
  • Balance the order of Windows and Linux guidance so Linux is not always secondary.
  • Add Linux-specific ARM template samples or links where only Windows samples are given.
  • Clarify which features or steps are platform-agnostic and which are Windows-only, to help Linux users navigate the guidance.
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-26 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 (PowerShell, Windows Defender, Windows security baselines) are often presented first or in greater detail. Windows-specific tools and extensions (e.g., Windows Defender, Azure DSC) are discussed without Linux equivalents or with notes stating Linux is not supported. PowerShell commands are used for Windows encryption, while Linux uses bash/openssl, but the Windows section is more prominent and detailed.
Recommendations
  • Ensure Linux examples are presented alongside Windows examples, not after or as an afterthought.
  • Where Windows-specific tools are discussed (e.g., Windows Defender, DSC), briefly mention Linux alternatives or clarify if no equivalent exists.
  • Balance the detail and prominence of Windows and Linux instructions, especially in critical sections like certificate management and secret encryption.
  • Consider adding a summary table or section highlighting parity and differences between Windows and Linux security practices for Service Fabric.
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-26 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page provides only PowerShell and C# examples for managing Service Fabric Application Groups. PowerShell is a Windows-centric tool, and there are no examples or guidance for Linux/macOS users (e.g., Bash, Azure CLI, REST API). This creates friction for users managing Service Fabric clusters from non-Windows environments.
Recommendations
  • Add Azure CLI examples for all operations shown (creation, update, querying, removal).
  • Include REST API sample requests for relevant actions.
  • Clarify whether PowerShell cmdlets are available cross-platform or provide alternatives for Linux/macOS users.
  • Mention any limitations or differences in managing Service Fabric clusters from Linux/macOS, if applicable.
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-26 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides code examples for scaling Service Fabric services 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 implementation details (such as kernel driver logging) are discussed before Linux equivalents. While Linux is mentioned in the platform section, Linux users may find friction due to the lack of parity in examples and tooling guidance.
Recommendations
  • Add Azure CLI or Bash examples alongside PowerShell for administrative actions such as creating/updating services.
  • Explicitly mention Linux-compatible tools and workflows for managing Service Fabric clusters.
  • Clarify which PowerShell commands are available cross-platform (if any), or provide links to Linux-specific documentation.
  • Consider providing sample scripts or references for Linux users to perform equivalent tasks.
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-26 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 given its own section and used for cluster upgrades, which are shown only with Windows-specific PowerShell commands. Windows registry keys and Windows Update settings are discussed without Linux equivalents. The upgrade section only provides Windows (MSI) instructions, omitting Linux (DEB) examples. Windows configuration is described in detail, while Linux-specific instructions are minimal or missing.
Recommendations
  • Add Linux-specific examples for cluster upgrades, including DEB package instructions and relevant shell commands.
  • Include Linux configuration details for VM scale sets, such as disabling automatic updates on Linux VMs.
  • Provide Bash or shell script equivalents for PowerShell commands where applicable.
  • Ensure that Linux and Windows examples are presented with equal prominence, ideally side-by-side.
  • Mention Linux registry/file configuration (if applicable) when discussing Windows registry keys.
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-26 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 presented as the primary scripting interface, which may create friction for Linux/macOS users who typically use Bash or Azure CLI. There is no mention of Linux-specific tools or patterns, nor guidance for non-Windows environments.
Recommendations
  • Add Azure CLI or Bash examples for each placement policy configuration, where possible.
  • Clarify whether PowerShell commands can be run cross-platform (e.g., with PowerShell Core) or if they are Windows-only.
  • Mention any Linux/macOS limitations or differences in Service Fabric management, if applicable.
  • Provide links or references to Linux/macOS documentation for Service Fabric management.
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-26 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides code examples for configuring auto scaling policies in Azure Service Fabric using application manifests, C# APIs, and PowerShell. All CLI examples are PowerShell-based, with no equivalent Bash or Linux CLI examples. The PowerShell examples are shown after C# but before any mention of Linux tooling. There is no guidance for Linux users on how to perform these operations via Bash, Azure CLI, or REST API. The documentation mentions that resource monitoring is supported for containerized applications on Linux, but does not provide Linux-specific instructions or examples.
Recommendations
  • Add Linux/Bash examples for configuring scaling policies, such as using Azure CLI or REST API.
  • Explicitly mention any limitations or differences for Linux clusters and provide guidance for Linux users.
  • Include instructions or references for Linux users to achieve the same tasks, especially for cluster management and service updates.
  • Consider providing sample scripts or commands for Linux environments alongside PowerShell examples.
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-26 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 practical example for reporting and querying health uses PowerShell cmdlets. There are no Linux/macOS CLI or REST API examples, even though Service Fabric supports cross-platform management. This creates friction for non-Windows users, as they must infer how to perform equivalent actions.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl) for Linux/macOS users.
  • Include REST API usage examples for health reporting and querying, which are platform-agnostic.
  • Mention cross-platform tooling and clarify which tools are available on each OS.
  • Ensure that PowerShell examples are accompanied by CLI or REST examples where possible.
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-26 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides configuration examples for both Windows (ClusterManifest.xml) and cross-platform/standalone (ClusterConfig.json), but code samples for service creation and updates are given only in C# and PowerShell, with PowerShell being a Windows-centric tool. The XML configuration section is labeled <WindowsServer>, and PowerShell examples are shown before any Linux CLI or cross-platform alternatives (which are missing). There is no explicit mention of Linux-specific tools or patterns, and Linux/macOS users may need to adapt instructions for their environments.
Recommendations
  • Add Azure CLI or Service Fabric CLI (sfctl) examples for service creation and placement constraints, which are cross-platform.
  • Clarify that ClusterConfig.json is used for standalone deployments, including Linux clusters, and provide explicit Linux cluster configuration guidance.
  • Include references or links to Linux/macOS setup guides for Service Fabric clusters.
  • Where PowerShell is used, note Linux/macOS equivalents or alternatives.
  • Consider providing bash or shell script examples for relevant operations.
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-26 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 PowerShell commands used for service creation and metric configuration. There are no equivalent examples for Linux/macOS users (e.g., Azure CLI, Bash, or REST API). PowerShell is a Windows-centric tool, and its exclusive use creates friction for non-Windows users. Additionally, PowerShell examples are presented before any mention of alternative tools, and there is no guidance for Linux/macOS users on how to perform these tasks.
Recommendations
  • Add equivalent Azure CLI or REST API examples for service creation and metric configuration.
  • Explicitly mention cross-platform tools and provide guidance for Linux/macOS users.
  • Where possible, include Bash scripting examples or reference documentation for non-Windows environments.
  • Clarify which tools are supported on which platforms, and link to relevant installation guides for PowerShell Core (if applicable) or Azure CLI.
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-26 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 PowerShell examples for managing node tags and service requirements, but does not include equivalent Linux/bash/CLI examples. PowerShell is primarily a Windows tool, and its exclusive use creates friction for Linux/macOS users. The C# API examples are cross-platform, but scripting and command-line guidance is Windows-centric.
Recommendations
  • Add Azure CLI or bash examples for managing node tags and service requirements, if supported.
  • Explicitly mention whether PowerShell commands are available on Linux/macOS (via PowerShell Core), and provide installation guidance if relevant.
  • If REST API endpoints exist for these operations, include sample curl or HTTP requests.
  • Clarify any limitations or differences for Linux-based Service Fabric clusters.
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-26 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides PowerShell examples for configuring service sensitivity and maximum load, but does not offer equivalent Linux/macOS CLI examples (such as Bash or Azure CLI). PowerShell is presented as the primary scripting interface, and there is no mention of cross-platform tools or instructions for Linux users. The C# API is platform-neutral, but operational scripting is Windows-centric.
Recommendations
  • Add Azure CLI or Bash examples for configuring service sensitivity and maximum load, where possible.
  • Clarify whether PowerShell examples are usable on Linux/macOS (e.g., via PowerShell Core), or provide guidance for Linux users.
  • Explicitly mention any cross-platform alternatives or limitations for Linux/macOS users.
  • Consider including REST API examples if available, as these are platform-independent.
GitHub Create Pull Request
← Previous Page 34 of 99 Next →