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 176-200 of 2475 flagged pages
Service Fabric Introduction to the Service Fabric Infrastructure Service .../articles/service-fabric/infrastructure-service-faq.md
Medium Priority View Details →
Scanned: 2026-03-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides a PowerShell-only example for bypassing Infrastructure Service, and references Service Fabric Explorer (a Windows-centric tool) without mentioning Linux alternatives. No Linux/macOS command-line examples or equivalent tooling are provided, and Windows tools are mentioned first and exclusively.
Recommendations
  • Add equivalent CLI examples for Linux/macOS users, such as using Azure CLI or REST API where possible.
  • Clarify whether Service Fabric Explorer is cross-platform or suggest alternatives for Linux users.
  • Provide guidance on how Linux/macOS administrators can perform the same operations, or explicitly state if certain actions are Windows-only.
  • Ensure that command examples are shown for both Windows and Linux environments, or note platform limitations.
Service Fabric Initializer CodePackages in Service Fabric ...in/articles/service-fabric/initializer-codepackages.md
Medium Priority View Details →
Scanned: 2026-03-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page for Initializer CodePackages in Service Fabric presents only Windows container examples, uses Windows-specific container images (nanoserver), Windows filesystem paths, and Windows command syntax (cmd.exe). There are no Linux container examples, nor is there guidance for Linux-based Service Fabric clusters or containers. The page assumes Windows familiarity and does not mention Linux alternatives or parity.
Recommendations
  • Add examples using Linux containers (e.g., Ubuntu or Alpine images) with Linux shell commands.
  • Show how to specify Initializer CodePackages for Linux-based Service Fabric clusters, including Linux path conventions and command syntax.
  • Clarify whether Initializer CodePackages are supported for Linux containers and, if not, explicitly state this limitation.
  • If Linux support exists, provide ApplicationManifest and ServiceManifest examples using Linux volume mounts and container images.
  • If Windows-only, add a clear note at the top indicating this feature is not supported on Linux clusters.
Service Fabric Service Fabric Explorer blocking operations ...ged-cluster-service-fabric-explorer-blocking-operation.md
Medium Priority View Details →
Scanned: 2026-03-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page primarily references Az PowerShell cmdlets (e.g., Remove-AzResource, AzSF PowerShell cmdlet) for managing Service Fabric resources, with no explicit mention of Linux/macOS equivalents or Azure CLI usage. While 'az resource' is mentioned once for deleting applications, PowerShell examples and terminology dominate, and PowerShell cmdlets are listed before Azure CLI commands. This creates friction for Linux/macOS users who typically rely on Azure CLI.
Recommendations
  • Add Azure CLI examples for all operations (e.g., deleting, creating, scaling resources) alongside PowerShell cmdlets.
  • Clarify which commands are cross-platform and which are Windows-only.
  • Where possible, provide ARM template examples for resource management.
  • Ensure Azure CLI commands are listed before or alongside PowerShell cmdlets to improve parity.
Service Fabric Learn about Azure Service Fabric application security ...ric/service-fabric-application-and-service-security.md
Medium Priority View Details →
Scanned: 2026-03-09 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 (e.g., Active Directory, gMSA, BitLocker) are mentioned before Linux equivalents, and some examples/tools (like disk encryption) reference only Windows/PowerShell. Linux-specific guidance is missing or relegated to TODOs, and Windows terminology (e.g., NetworkService, Fabric.exe) is used without Linux alternatives.
Recommendations
  • Add Linux-specific examples and guidance, especially for disk encryption and user account management.
  • Ensure parity in describing how to secure Service Fabric applications on Linux clusters (e.g., mention Linux user/group management, SELinux/AppArmor, Linux disk encryption options).
  • Where Windows tools (e.g., BitLocker, PowerShell) are referenced, provide equivalent Linux tools (e.g., dm-crypt/LUKS, bash scripts) and examples.
  • Avoid presenting Windows-specific features first unless they are more widely used; consider parallel structure for Windows and Linux.
  • Clarify when a feature is Windows-only and provide alternative approaches for Linux where possible.
Service Fabric Migrate an Azure Service Fabric cluster to availability zone support ...ce-fabric/migrate-service-fabric-availability-zones.md
Medium Priority View Details →
Scanned: 2026-03-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides migration guidance for Azure Service Fabric clusters to availability zone support. While most of the guidance is platform-agnostic (focused on ARM templates and Azure resources), the step-by-step migration for clusters with Basic SKU load balancer and IP resources relies heavily on PowerShell commands and Windows-centric tooling. PowerShell examples are given exclusively, and Windows paths (e.g., 'D:\\SvcFab') appear in configuration snippets. Linux equivalents (such as Azure CLI or Bash) are missing, and the PowerShell approach is presented as the default, creating friction for Linux/macOS users.
Recommendations
  • Add Azure CLI or Bash script equivalents for all PowerShell migration steps, especially for resource deployment, node disabling/removal, and DNS updates.
  • Clarify that PowerShell commands are Windows-specific and provide links or instructions for Linux/macOS users.
  • Where file paths are shown (e.g., 'D:\\SvcFab'), mention Linux alternatives or note how to configure for Linux VMSS.
  • Ensure sample templates and references include both Windows and Linux cluster scenarios.
  • Consider reordering examples so platform-agnostic approaches (ARM templates, Azure CLI) are shown first, with PowerShell as an alternative.
Service Fabric Describing Azure Service Fabric apps and services ...ic/service-fabric-application-and-service-manifests.md
Medium Priority View Details →
Scanned: 2026-03-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation contains a notable Windows bias in its guidance for validating manifest XML schemas. It exclusively references opening the Service Fabric XSD schema file in Visual Studio using a Windows file path (C:\Program Files\...), with no mention of Linux/macOS equivalents or cross-platform tooling. Additionally, the only command-line tooling mentioned for service creation is the ServiceFabric PowerShell module, with no reference to Azure CLI or other cross-platform tools.
Recommendations
  • Provide instructions or alternatives for validating manifest XML on Linux/macOS, such as using cross-platform editors (e.g., VS Code) or command-line XML validation tools.
  • Include Linux/macOS file paths for the Service Fabric XSD schema, or clarify where to find these files on non-Windows systems.
  • Mention and provide examples for using Azure CLI or other cross-platform tools for service creation and management, not just PowerShell.
  • When referencing tools like Visual Studio, note cross-platform alternatives or clarify if a step is only required/supported on Windows.
Service Fabric Deploy and upgrade with Azure Resource Manager ...vice-fabric/service-fabric-application-arm-resource.md
Medium Priority View Details →
Scanned: 2026-03-09 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-only examples for removing Service Fabric application resources and references PowerShell before CLI in the 'Next steps' section. There are no CLI (az or sfctl) or bash examples for Linux/macOS users, and the PowerShell-centric approach may create friction for non-Windows users.
Recommendations
  • Add equivalent Azure CLI (az) and/or Service Fabric CLI (sfctl) examples for managing and removing application resources, especially for the 'Remove Service Fabric Resource Provider Application resource' section.
  • In the 'Next steps' section, mention CLI and PowerShell equally, or provide parallel links/examples for both.
  • Explicitly note that all operations shown with PowerShell can also be performed with CLI/REST, and link to relevant Linux/macOS-friendly instructions.
  • Consider providing bash shell script examples where appropriate.
Service Fabric Application upgrade: upgrade parameters ...abric/service-fabric-application-upgrade-parameters.md
Medium Priority View Details →
Scanned: 2026-03-09 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 tools) upgrade parameters first and in greater detail, with Linux/macOS (SFCTL/CLI) parameters covered only after. Most parameter tables and explanations are focused on PowerShell and Visual Studio, with SFCTL (cross-platform CLI) relegated to a later section. Examples and parameter descriptions are more extensive for Windows tools, and the only explicit example syntax is PowerShell. Linux CLI (SFCTL) is covered, but not with equal prominence or detail.
Recommendations
  • Present SFCTL (Service Fabric CLI) parameters and usage examples alongside PowerShell and Visual Studio, not after them.
  • Provide example commands for SFCTL in the same way as for PowerShell, including parameter usage.
  • Clarify at the start that all features are available cross-platform via SFCTL, and that PowerShell/Visual Studio are Windows-specific.
  • Reorganize parameter tables to show all tools (PowerShell, Visual Studio, SFCTL) in parallel, or provide a comparison table.
  • Add explicit Linux/macOS usage notes or callouts where relevant.
Service Fabric Architecture of Azure Service Fabric ...articles/service-fabric/service-fabric-architecture.md
Medium Priority View Details →
Scanned: 2026-03-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation mentions PowerShell cmdlets as the primary example for management operations, without referencing Linux/macOS equivalents (such as Azure CLI or REST APIs). Windows security is mentioned alongside X509 certificates in the transport subsystem, with Windows listed first. These patterns suggest a Windows-first bias, especially in management and security contexts.
Recommendations
  • Add examples or references to Azure CLI and REST API usage for management operations, highlighting cross-platform options.
  • Clarify that PowerShell cmdlets are available on Linux/macOS via PowerShell Core, or provide alternative commands where applicable.
  • When mentioning security mechanisms, list X509 certificates before Windows security, and clarify Linux/macOS support.
  • Review the documentation for other Windows-centric language and ensure Linux/macOS parity is explicitly addressed.
Service Fabric Application lifecycle in Service Fabric ...service-fabric/service-fabric-application-lifecycle.md
Medium Priority View Details →
Scanned: 2026-03-09 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 frequently references PowerShell cmdlets and Windows-specific tools (e.g., Register-ServiceFabricApplicationType, Remove-ServiceFabricApplicationPackage) as primary examples for managing the Service Fabric application lifecycle. While REST API and .NET methods are also mentioned, there is a notable absence of Linux-focused command-line examples (such as Azure CLI or sfctl usage), and PowerShell is consistently presented before other options. This creates friction for Linux/macOS users, as they must infer or seek out equivalent commands.
Recommendations
  • Add explicit Linux/macOS command-line examples using Azure CLI and sfctl for each lifecycle operation (deploy, upgrade, remove, etc.).
  • Where PowerShell cmdlets are referenced, provide parallel examples using sfctl or Azure CLI, and clarify their cross-platform applicability.
  • Reorder examples so that cross-platform tools (REST API, Azure CLI, sfctl) are presented before or alongside Windows-specific tools.
  • Include a section or note clarifying which tools are supported on Linux/macOS and linking to relevant documentation.
Scanned: 2026-03-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page focuses on C# and .NET serialization, which are cross-platform, but the 'Next steps' section highlights Windows-centric tools (Visual Studio and PowerShell) for application upgrades, with no mention of Linux/macOS equivalents or CLI options. This creates friction for non-Windows users seeking guidance on upgrading applications in Service Fabric.
Recommendations
  • Add examples or links for upgrading applications using cross-platform tools, such as Azure CLI or Service Fabric CLI (sfctl), especially for Linux/macOS users.
  • Mention or link to documentation for Linux/macOS development environments and workflows, if supported.
  • Ensure that upgrade tutorials are available for non-Windows platforms, or clarify platform limitations if certain features are Windows-only.
Service Fabric Service Fabric application upgrade ...s/service-fabric/service-fabric-application-upgrade.md
Medium Priority View Details →
Scanned: 2026-03-09 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. PowerShell is used exclusively in code examples, and Windows-specific tools (e.g., PowerShell cmdlets, http.sys) are referenced without Linux equivalents or guidance. There are no examples or instructions for Linux/macOS users, and Windows terminology and tools are presented first and exclusively throughout the page.
Recommendations
  • Add equivalent CLI examples using Azure CLI or Service Fabric CLI (sfctl) for Linux/macOS users.
  • Provide guidance on performing application upgrades on Linux-based Service Fabric clusters, including relevant commands and tools.
  • Clarify which features or steps are Windows-only and which are cross-platform.
  • Include troubleshooting and upgrade instructions for Linux environments.
  • Mention any limitations or differences for Linux clusters, especially regarding HTTPS endpoints and certificate management.
Scanned: 2026-03-09 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, cluster connection, and API invocation. All CLI and scripting guidance is Windows-centric, with no mention of Linux/macOS equivalents (such as Bash, curl, or Azure CLI). The Service Fabric Explorer UI is platform-neutral, but all code samples and automation guidance assume a Windows/PowerShell environment.
Recommendations
  • Add Bash/curl examples for REST API calls, showing how Linux/macOS users can trigger backups and track progress.
  • Mention Azure CLI commands if available for Service Fabric backup operations.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is required only for Windows/PowerShell users, and provide alternatives for Linux/macOS users.
  • Add a section or note explaining how Linux/macOS users can perform the same tasks, and reference any cross-platform tools or SDKs.
  • Ensure REST API documentation links are prominent, and provide sample requests in both PowerShell and Bash/curl formats.
Service Fabric Understanding periodic backup configuration ...-fabric-backuprestoreservice-configure-periodic-backup.md
Medium Priority View Details →
Scanned: 2026-03-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page is mostly platform-neutral, focusing on Service Fabric's backup configuration via REST APIs and JSON policy definitions. However, in the 'File share' backup storage section, only Windows-style file share paths (\\StorageServer\BackupStore) and Windows authentication mechanisms are described. There is no mention of Linux-compatible file share paths (e.g., SMB/CIFS mounts), nor guidance for Linux clusters or users. This creates a gap for Linux/macOS users who may wish to use file shares for backup storage.
Recommendations
  • Add examples and instructions for configuring file share backup storage on Linux clusters, including SMB/CIFS mount paths and authentication methods.
  • Clarify whether file share backup storage is supported on Linux Service Fabric clusters, and if so, provide Linux-specific guidance.
  • If file share backup is Windows-only, explicitly state this limitation to avoid confusion for Linux users.
  • Ensure parity in documentation by mentioning Linux-compatible storage options and authentication patterns where relevant.
Scanned: 2026-03-09 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 backups in Azure Service Fabric is heavily biased toward Windows/PowerShell usage. All code examples use PowerShell, including REST API calls, and require the Microsoft.ServiceFabric.Powershell.Http module. There are no examples or guidance for Linux/macOS users, such as using Bash, curl, or cross-platform tools. The documentation assumes the reader is on Windows and does not mention alternative approaches for non-Windows environments.
Recommendations
  • Add Bash/curl examples for REST API calls to demonstrate how Linux/macOS users can trigger restores and track progress.
  • Mention that the REST API can be used from any platform and provide sample requests using curl or HTTPie.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is required for all scenarios, or if REST API calls can be made directly without it.
  • Include guidance on certificate handling for Linux/macOS (e.g., how to pass client certificates with curl).
  • Consider providing a table or section comparing Windows/PowerShell and Linux/Bash approaches for common tasks.
Service Fabric Capacity planning and scaling for Azure Service Fabric ...bric/service-fabric-best-practices-capacity-scaling.md
Medium Priority View Details →
Scanned: 2026-03-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides only PowerShell-based examples for critical Service Fabric cluster operations (e.g., scaling in/out, disabling nodes), with no mention of Linux/macOS equivalents (such as Service Fabric CLI or REST API). This creates friction for users managing Linux-based clusters or working from non-Windows environments.
Recommendations
  • Add equivalent examples using the Service Fabric CLI (sfctl), which is cross-platform, for all PowerShell commands (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState).
  • Where PowerShell is referenced, clarify if the commands are available on Linux/macOS via PowerShell Core, or provide REST API alternatives.
  • Explicitly mention and link to Linux/macOS management tooling (sfctl, REST API) in sections describing operational tasks.
  • Consider including bash/shell script snippets or command-line instructions for Linux users alongside PowerShell examples.
Service Fabric Azure Service Fabric security best practices ...rvice-fabric/service-fabric-best-practices-security.md
Medium Priority View Details →
Scanned: 2026-03-09 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 key security tasks, but Windows examples (PowerShell, Windows Defender, Windows security baselines) are often presented first or in greater detail. Windows-specific tools and concepts (PowerShell, Windows Defender, DSC) are mentioned without Linux equivalents, and some sections (Windows Defender, security baselines) are Windows-only, though they do note Linux limitations. Linux examples are present for certificate and secret encryption, but overall, Windows is prioritized in ordering and tool references.
Recommendations
  • Reorder sections to present Windows and Linux examples side-by-side or alternate which comes first.
  • Add Linux equivalents for Windows-specific tools where possible (e.g., mention Linux security baselines or antivirus options).
  • Clarify when a feature or tool is Windows-only and provide Linux alternatives or workarounds.
  • Ensure Linux guidance is as detailed and prominent as Windows guidance, especially for critical security tasks.
  • Where PowerShell is used, provide Bash or CLI equivalents for Linux clusters.
Service Fabric Node types and virtual machine scale sets ...les/service-fabric/service-fabric-cluster-nodetypes.md
Medium Priority View Details →
Scanned: 2026-03-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides some cross-platform information (e.g., mentions both 'ServiceFabricLinuxNode' and 'ServiceFabricNode'), but there are notable Windows biases. Examples and property tables use Windows-style paths (e.g., 'D:\\SvcFab'), and 'Next steps' links focus on RDP and PowerShell scripts, which are Windows-centric, with no Linux/SSH equivalents provided. There are no explicit Linux/macOS remote connection or management examples.
Recommendations
  • Include Linux/SSH-based remote connection instructions and examples alongside or before Windows/RDP examples.
  • Provide Linux-style file path examples (e.g., '/var/lib/servicefabric') in property tables and code snippets.
  • Add links to Linux management scripts or documentation in the 'Next steps' section.
  • Clarify when a step or tool is Windows-only, and offer Linux/macOS alternatives where possible.
Service Fabric Change Azure Service Fabric cluster settings ...rvice-fabric/service-fabric-cluster-fabric-settings.md
Medium Priority View Details →
Scanned: 2026-03-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation provides a comprehensive reference for Service Fabric cluster settings, covering both Azure-hosted and standalone clusters. However, there is evidence of Windows bias: Windows terminology (e.g., 'MY' certificate store, 'LocalMachine', NTLM authentication, Windows Defender Firewall) is used throughout, and Windows-specific settings are often mentioned before Linux equivalents. Some settings default to Windows values or are described as 'Windows only', while Linux-specific guidance is minimal or absent. Linux is referenced in a few places (e.g., LinuxExternalExecutablePath, ContainerNetworkSetup), but parity is not consistent.
Recommendations
  • Add explicit Linux/macOS equivalents for settings where Windows tools or terminology are used (e.g., certificate store names, authentication methods).
  • Where settings are Windows-only, clarify Linux alternatives or note if the setting is not applicable.
  • Ensure Linux-specific guidance is provided for configuration upgrade, certificate management, and firewall settings.
  • Review default values and descriptions to ensure they are not Windows-centric unless the feature is truly Windows-only.
  • Consider providing examples or references for Linux cluster configuration and management, not just standalone Windows clusters.
Service Fabric Service Fabric Cluster Resource Manager - Placement Policies ...ce-manager-advanced-placement-rules-placement-policies.md
Medium Priority View Details →
Scanned: 2026-03-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides code examples primarily in C# and PowerShell. PowerShell is a Windows-centric tool, and no equivalent Linux/macOS command-line examples (such as Azure CLI, Bash, or REST API) are provided. All PowerShell examples appear before any mention of alternative tooling, and there is no guidance for Linux users on how to perform these tasks. This creates friction for users managing Service Fabric clusters from non-Windows environments.
Recommendations
  • Add Azure CLI examples for each placement policy configuration, as Azure CLI is cross-platform.
  • Include REST API examples for configuring placement policies, which are usable from any OS.
  • Explicitly mention whether PowerShell commands can be run on PowerShell Core (cross-platform), or if they require Windows PowerShell.
  • Provide Bash script snippets or references for Linux/macOS users where applicable.
  • Clarify any OS-specific limitations for Service Fabric management tools.
Service Fabric Manage Azure Service Fabric app load using metrics ...ric/service-fabric-cluster-resource-manager-metrics.md
Medium Priority View Details →
Scanned: 2026-03-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides code examples for C# and PowerShell, but omits equivalent Linux/macOS CLI examples (such as Azure CLI or REST API). PowerShell is featured prominently and appears before any mention of cross-platform alternatives. There is no guidance for Linux users on how to perform the same operations, creating friction for non-Windows users.
Recommendations
  • Add Azure CLI examples for service creation and metric management, as Azure CLI is cross-platform.
  • Include REST API sample calls for relevant operations (service creation, metric updates, load reporting).
  • Clarify which PowerShell commands are available cross-platform (PowerShell Core) and which are Windows-only.
  • Add a section or notes for Linux/macOS users, outlining supported tools and workflows.
  • Consider referencing or linking to Service Fabric SDK documentation for Linux/macOS, if available.
Scanned: 2026-03-09 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 CLI or scripting examples for Linux/macOS users (e.g., Bash, Azure CLI). PowerShell is presented first and exclusively as the shell-based method, which may create friction for non-Windows users. The C# API examples are cross-platform, but shell/command-line guidance is Windows-centric.
Recommendations
  • Add Azure CLI or Bash examples for managing node tags and service requirements, if supported.
  • Clarify whether PowerShell commands are available cross-platform (e.g., via PowerShell Core) or if they are Windows-only.
  • If PowerShell is the only supported CLI, explicitly state this and provide guidance for Linux/macOS users (e.g., using REST APIs or C#).
  • Consider including REST API examples for node tag management, as these are platform-agnostic.
Service Fabric Azure Service Fabric standalone cluster scaling ...ce-fabric/service-fabric-cluster-scaling-standalone.md
Medium Priority View Details →
Scanned: 2026-03-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page for scaling Azure Service Fabric standalone clusters demonstrates Windows bias by exclusively referencing PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) and linking to a Windows Server-specific scaling guide. There are no examples or guidance for Linux-based standalone clusters, nor are Linux-native tools or commands mentioned.
Recommendations
  • Add examples and instructions for scaling standalone clusters deployed on Linux machines, including relevant Linux-native tools and commands.
  • Reference any cross-platform or Linux-specific Service Fabric management tools (such as sfctl or REST APIs) alongside PowerShell.
  • Provide parity in guidance for both Windows and Linux environments, including links to Linux documentation if available.
  • Clarify if standalone clusters are Windows-only, or explicitly state Linux support status.
Service Fabric Service Fabric Cluster Resource Manager - Application Groups ...ice-fabric-cluster-resource-manager-application-groups.md
Medium Priority View Details →
Scanned: 2026-03-09 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 only PowerShell and C# examples for managing Service Fabric Application Groups, with no Linux/macOS CLI or scripting equivalents. All command-line instructions use PowerShell cmdlets, which are native to Windows, and there is no mention of cross-platform tools or Azure CLI commands. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other tools.
Recommendations
  • Add Azure CLI examples for all PowerShell cmdlets shown, as Azure CLI is cross-platform.
  • Mention if PowerShell Core (pwsh) can be used on Linux/macOS, and provide guidance if so.
  • Include REST API examples for relevant operations, as these are platform-agnostic.
  • Clarify any limitations or requirements for Linux/macOS users in the introductory section.
  • Consider linking to documentation about Service Fabric management on Linux clusters.
Scanned: 2026-03-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed examples for configuring auto scaling in Azure Service Fabric using application manifests, C# APIs, and PowerShell. However, all CLI/script examples are PowerShell-based, with no equivalent Bash or Linux CLI examples. The PowerShell examples are presented alongside C# and XML, but there is no mention of Linux-native tooling or cross-platform CLI usage. While Service Fabric supports Linux containers, the documentation does not demonstrate how Linux users can configure auto scaling via CLI or scripting, creating friction for non-Windows users.
Recommendations
  • Add equivalent Bash or Azure CLI examples for configuring scaling policies, especially for Linux-based Service Fabric clusters.
  • Explicitly mention cross-platform tools (e.g., Azure CLI, REST API) and provide usage examples.
  • Clarify which PowerShell commands are available on Linux (via PowerShell Core) and which are Windows-only.
  • Add a section summarizing Linux-specific considerations for auto scaling, including any limitations or differences.