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 1826-1850 of 2475 flagged pages
Service Fabric Application lifecycle in Service Fabric ...service-fabric/service-fabric-application-lifecycle.md
Medium Priority View Details →
Scanned: 2026-02-05 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation consistently references PowerShell cmdlets and Windows-centric tooling (e.g., Copy-ServiceFabricApplicationPackage, Register-ServiceFabricApplicationType) as primary command-line interfaces for managing the Service Fabric application lifecycle. While REST APIs and .NET methods are also mentioned, there is a notable absence of Linux-native CLI examples (such as Azure CLI or sfctl) in the main lifecycle steps. This creates friction for Linux/macOS users, who may not have access to PowerShell or Windows-specific tools.
Recommendations
  • Include equivalent Azure CLI (az sf) or Service Fabric CLI (sfctl) commands alongside PowerShell cmdlets for all lifecycle operations (deploy, upgrade, remove, etc.).
  • Add explicit notes or examples for Linux/macOS users, clarifying which tools are cross-platform and how to perform tasks without PowerShell.
  • Where possible, show Linux/macOS shell commands (bash) in parallel with PowerShell, especially for automation scenarios.
  • Link to cross-platform tool documentation (sfctl, Azure CLI) in each relevant section.
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-05 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, with some sections and examples that are Windows-centric or reference Windows tools and patterns first. There are references to running services under Windows-specific accounts (Active Directory, gMSA), and disk encryption is only linked to a Windows PowerShell example, with a TODO for Linux. Linux equivalents are mentioned but not detailed, and examples or step-by-step instructions for Linux are missing in several sections.
Recommendations
  • Add explicit Linux examples for disk encryption and securing data at rest, including links to relevant Azure documentation for Linux VMSS disk encryption.
  • Provide parallel instructions or references for running services under Linux user accounts, including any differences in manifest configuration or security principal setup.
  • Ensure that examples and walkthroughs for certificate management, endpoint configuration, and container security include both Windows and Linux scenarios, with clear distinctions.
  • Where Windows-specific features (e.g., gMSA, AD integration) are mentioned, clarify Linux alternatives or state if no equivalent exists.
  • Reorder examples or provide side-by-side Windows and Linux instructions to avoid Windows-first bias.
GitHub Create Pull Request
Service Fabric Advanced Application Upgrade Topics ...-fabric/service-fabric-application-upgrade-advanced.md
Medium Priority View Details →
Scanned: 2026-02-05 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 Service Fabric application upgrades is heavily focused on PowerShell-based workflows, with all command-line examples using PowerShell cmdlets and no mention of Linux/macOS equivalents (such as Service Fabric CLI or REST API usage). Windows/PowerShell tools are referenced first and exclusively, creating friction for users managing Service Fabric clusters on Linux or from non-Windows environments.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and supported on Linux/macOS.
  • Where PowerShell cmdlets are referenced, include a note or link to CLI/REST API documentation for non-Windows users.
  • Clarify which features or commands are available across platforms, and indicate any Windows-only limitations.
  • Provide ARM template and manifest examples alongside CLI commands for parity.
  • Update 'Next steps' to include links to Linux/macOS upgrade tutorials or CLI-based guides.
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-05 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 upgrades demonstrates a notable Windows bias. PowerShell is the only command-line example provided, and all upgrade tooling references (e.g., Get-ServiceFabricApplication, Start-ServiceFabricApplicationUpgrade, Update-ServiceFabricService) are PowerShell cmdlets. There are no examples or guidance for Linux/macOS users, such as using the Service Fabric CLI (sfctl) or REST APIs. The documentation also references Windows-specific components (e.g., http.sys) without clarifying platform differences or alternatives.
Recommendations
  • Add equivalent examples using the Service Fabric CLI (sfctl), which is cross-platform, alongside or instead of PowerShell examples.
  • Mention REST API options for application upgrades, which are platform-agnostic.
  • Clarify when features or errors (such as http.sys certificate handling) are specific to Windows, and provide Linux/macOS alternatives or caveats where applicable.
  • In the 'Next steps' section, include links to tutorials or guides for Linux/macOS users, such as 'Upgrading your Application Using sfctl'.
  • Where PowerShell cmdlets are referenced, add a note or table mapping to equivalent sfctl commands.
GitHub Create Pull Request
Service Fabric Architecture of Azure Service Fabric ...articles/service-fabric/service-fabric-architecture.md
Medium Priority View Details →
Scanned: 2026-02-05 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation references PowerShell cmdlets as the primary means for managing Service Fabric clusters and applications, without mentioning equivalent Linux/macOS management tools or CLI options. Windows security is mentioned as a transport option before X509 certificates, and no Linux-specific management patterns are described. This creates friction for Linux users seeking parity in cluster management and automation.
Recommendations
  • Include references to cross-platform management tools such as Azure CLI, REST APIs, or Service Fabric CLI (sfctl) alongside PowerShell cmdlets.
  • Clarify that PowerShell cmdlets are available on Linux/macOS via PowerShell Core, or provide Linux/macOS-specific instructions/examples.
  • Mention X509 certificates before or alongside Windows security as a transport option, and clarify Linux support.
  • Add explicit notes or links to Linux/macOS management documentation for 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-05 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation for restoring backups in Azure Service Fabric is heavily focused on PowerShell-based workflows, with all command-line examples using PowerShell syntax and Windows-specific modules. There are no equivalent Linux/macOS CLI or REST API examples using cross-platform tools (e.g., curl, Azure CLI, or bash). The prerequisite steps and operational guidance assume a Windows environment and PowerShell, which may create friction for Linux/macOS users.
Recommendations
  • Add equivalent examples using cross-platform tools such as curl, Azure CLI, or bash scripts for REST API calls.
  • Clarify whether the Service Fabric PowerShell module is required for all platforms, and if not, provide installation and usage instructions for Linux/macOS.
  • Include explicit guidance for Linux/macOS users on how to authenticate and interact with the Service Fabric REST APIs (e.g., using certificates with curl or other HTTP clients).
  • Reorganize examples so that REST API usage is shown independently of PowerShell, or provide both PowerShell and cross-platform examples side-by-side.
  • Document any platform limitations (if any) for Service Fabric backup/restore operations, so users know if certain steps are Windows-only.
GitHub Create Pull Request
Service Fabric Understanding periodic backup configuration ...-fabric-backuprestoreservice-configure-periodic-backup.md
Medium Priority View Details →
Scanned: 2026-02-05 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page for configuring periodic backups in Azure Service Fabric shows evidence of Windows bias, primarily in the 'File share' backup storage section. Only Windows-style UNC paths (\\StorageServer\BackupStore) and Integrated Windows Authentication are described, with no mention of Linux-compatible file share options (such as NFS, SMB mounting on Linux, or cross-platform authentication patterns). The examples and instructions for file share access are Windows-centric, and there is no guidance for Linux/macOS users on how to configure or access file shares for backup storage. Additionally, Windows authentication methods are presented first and exclusively, without Linux alternatives.
Recommendations
  • Add documentation for configuring file share backup storage using Linux/macOS nodes, including supported protocols (e.g., NFS, SMB) and authentication methods.
  • Provide examples of mounting and accessing file shares from Linux-based Service Fabric clusters, including sample paths and credential handling.
  • Clarify whether Linux clusters can use the file share backup option, and if so, provide parity in instructions for both platforms.
  • If file share backup is Windows-only, explicitly state this limitation to avoid confusion for Linux users.
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-05 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 some upgrade operations. Windows-specific tools and registry settings are discussed without Linux equivalents or alternatives. Windows VM configuration details are given before Linux, and some upgrade instructions are Windows-centric.
Recommendations
  • Provide equivalent Bash or Linux shell examples for manual upgrade operations currently shown only in PowerShell.
  • Include Linux-specific instructions for disabling automatic updates and managing OS upgrades, such as using cloud-init or systemd settings.
  • Clarify which steps are Windows-only and provide Linux alternatives or links to Linux documentation where appropriate.
  • Balance the order of Windows and Linux references, presenting both options side-by-side when possible.
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-05 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 detailed step-by-step instructions for scaling Service Fabric clusters, but the manual scaling sections exclusively reference PowerShell commands (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState) without mentioning Linux equivalents or cross-platform alternatives. There are no bash/CLI examples or guidance for Linux users, and the use of PowerShell is presented as the default approach for cluster management tasks. This creates friction for Linux/macOS users, who may not have access to PowerShell or may prefer native Linux tools.
Recommendations
  • Add equivalent examples for Linux environments, such as using Azure CLI, Service Fabric CLI (sfctl), or bash scripts for node management tasks.
  • Clearly indicate which commands are Windows-only and provide cross-platform alternatives where possible.
  • Include links or references to Linux/macOS documentation for Service Fabric cluster management.
  • Reorder examples to present cross-platform or Linux-native tools alongside or before Windows/PowerShell examples.
GitHub Create Pull Request
Service Fabric Node types and virtual machine scale sets ...les/service-fabric/service-fabric-cluster-nodetypes.md
Medium Priority View Details →
Scanned: 2026-02-05 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides a general overview of Service Fabric node types and VM scale sets, with some references to both Windows and Linux nodes. However, there are signs of Windows bias: the example configuration uses a Windows-style file path (D:\SvcFab) and certificate store naming conventions, and the 'Next steps' section links to PowerShell scripts for RDP port and credential management, which are Windows-specific tasks. There are no explicit Linux/macOS examples or equivalent SSH instructions for remote connectivity or admin management.
Recommendations
  • Include Linux/macOS-specific examples, such as using SSH for remote connection and managing credentials.
  • Provide sample configuration snippets with Linux-style paths (e.g., /var/svcfab) when 'type' is ServiceFabricLinuxNode.
  • Add links to documentation or scripts for managing Linux nodes, such as changing SSH keys or port ranges.
  • Clarify which instructions apply to Windows nodes and which to Linux nodes, especially in 'Next steps'.
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-05 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 presents several examples and references that prioritize Windows and PowerShell usage, with Linux equivalents mentioned less prominently or omitted. Windows tools and patterns (e.g., PowerShell, Windows containers, Windows-specific ARM templates) are referenced before or instead of Linux alternatives. Some sections, such as API access and DevOps, focus on PowerShell and Windows-specific workflows, while Linux guidance is less detailed or missing. Example ARM templates and networking scenarios are Windows-centric, and Linux-specific instructions are often relegated to links or brief mentions.
Recommendations
  • Provide Linux CLI (az, bash) examples alongside PowerShell commands, especially for API access and cluster management.
  • Include Linux-focused ARM template samples and reference them equally with Windows examples.
  • Clarify when instructions or features apply to both Windows and Linux clusters, and explicitly note any differences.
  • Add more Linux-specific networking scenarios and troubleshooting steps.
  • Ensure that DevOps and automation examples include Linux agent workflows, not just classic PowerShell tasks.
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-05 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 noticeable Windows-first bias in several sections. Windows-specific tools (PowerShell, Windows Defender, DSC) are described in detail, often before or with more emphasis than Linux equivalents. Some examples and recommendations are Windows-centric, with Linux alternatives provided later or in less detail. Windows Defender configuration is covered extensively, while Linux antimalware is only briefly mentioned as unsupported.
Recommendations
  • Ensure Linux examples and instructions are presented with equal prominence and detail as Windows ones, especially in sections like certificate management and encryption.
  • Where Windows tools (e.g., PowerShell, Windows Defender, DSC) are mentioned, provide clear Linux alternatives or explicitly state when no equivalent exists.
  • Avoid presenting Windows examples first by default; alternate or parallelize example order for cross-platform parity.
  • Expand on Linux antimalware and security baseline options, or link to relevant resources if available.
  • Clarify which features or recommendations are Windows-only and which are cross-platform, to reduce confusion.
GitHub Create Pull Request
Service Fabric Change Azure Service Fabric cluster settings ...rvice-fabric/service-fabric-cluster-fabric-settings.md
Medium Priority View Details →
Scanned: 2026-02-05 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation lists Service Fabric cluster settings in a platform-neutral way, but there are several signs of Windows bias. Windows terminology and tools (e.g., certificate store names like 'My', NTLM authentication, references to Windows-specific features like Windows Update, and default paths like d:\svcfab) are prevalent throughout. Some settings and defaults are described primarily in Windows terms, with Linux equivalents either omitted or mentioned secondarily. There are parameters whose guidance is Windows-centric (e.g., references to Windows Defender Firewall, Windows node management, and PowerShell-style paths), and Linux-specific configuration is rarely highlighted or explained in parity. The documentation does not provide Linux/macOS-specific examples or guidance for certificate management, file paths, or service management, even though Service Fabric supports Linux clusters.
Recommendations
  • For each setting that references Windows-specific concepts (e.g., certificate store names, NTLM, Windows Update), add Linux equivalents or clarify platform applicability.
  • Where file paths or store names are mentioned, provide both Windows and Linux examples (e.g., 'My' vs. '/var/lib/waagent').
  • Explicitly document Linux/macOS configuration steps, especially for certificate management, service activation, and file system paths.
  • Add notes or tables indicating which settings are Windows-only, Linux-only, or cross-platform.
  • Include Linux/macOS-focused examples for common configuration scenarios.
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-05 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 provides code examples for configuring Service Fabric placement policies using C# and PowerShell. All command-line examples use PowerShell, which is a Windows-centric tool, and there are no equivalent examples for Linux/macOS users (e.g., Azure CLI, Bash, or REST API). The documentation implicitly assumes a Windows environment for operational tasks, which may create friction for users managing Service Fabric clusters from Linux/macOS.
Recommendations
  • Add Azure CLI or REST API examples for configuring placement policies, as these are cross-platform and commonly used on Linux/macOS.
  • Explicitly mention whether PowerShell commands can be run on Linux/macOS (e.g., via PowerShell Core), or provide alternative instructions if not.
  • Clarify any platform-specific requirements for Service Fabric management, and link to cross-platform tooling where available.
  • Consider reordering examples so that cross-platform options (if available) are presented first or alongside Windows-specific tools.
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-05 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides example code for configuring auto scaling policies in Service Fabric using application manifests, C# APIs, and PowerShell. However, all command-line examples use PowerShell, which is Windows-centric, and there are no equivalent Linux shell (e.g., Bash/CLI) examples. The documentation does mention that resource monitoring is supported for containerized applications on Linux, but practical configuration steps and code samples are only shown for Windows tools and patterns. This creates friction for Linux users who may need to adapt or research how to perform these tasks on their platform.
Recommendations
  • Add equivalent examples using Azure CLI or Bash scripts for configuring scaling policies, especially for Linux clusters.
  • Clearly indicate which steps or commands are platform-specific and provide guidance or links for Linux users.
  • If PowerShell is required for some operations, explain how Linux users can install and use PowerShell Core, or provide alternative approaches.
  • Include notes or sections explicitly addressing Linux configuration workflows for Service Fabric auto scaling.
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-05 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides both C# and PowerShell examples for managing Service Fabric metrics, but omits equivalent Linux/macOS command-line examples (such as Azure CLI or REST API). PowerShell is featured as the only scripting/command-line interface, which is Windows-centric. There is no mention of Linux-native tools or workflows, nor are Linux/macOS users guided on how to perform these tasks without PowerShell.
Recommendations
  • Add Azure CLI examples for service creation and metric management, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include REST API examples for metric configuration and load reporting, which are platform-agnostic.
  • Explicitly mention how Linux/macOS users can perform these operations, and clarify any differences or limitations.
  • Consider reordering examples so that platform-neutral options (C#, CLI, REST) appear before or alongside PowerShell.
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-05 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 Cluster Resource Manager - Application Groups predominantly provides PowerShell examples and references, which are Windows-centric. There are no CLI/bash examples or explicit instructions for Linux/macOS users. PowerShell commands are presented before C# code samples, and no cross-platform alternatives (such as Azure CLI or REST API) are mentioned. This creates friction for users managing Service Fabric clusters from Linux/macOS environments.
Recommendations
  • Add Azure CLI examples for all operations shown with PowerShell (e.g., creating/updating applications, querying load information).
  • Explicitly mention REST API endpoints or SDKs that can be used from any platform.
  • Clarify whether PowerShell commands can be run from Linux/macOS (using PowerShell Core), and provide guidance if so.
  • Reorder examples or provide parallel examples for Windows (PowerShell) and Linux/macOS (CLI/bash) where possible.
  • Include a note about cross-platform management options for Service Fabric clusters.
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-05 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 examples for both ClusterManifest.xml (Windows Server clusters) and ClusterConfig.json (standalone deployments, which can be Linux or Windows). However, code samples for service creation and updates are given only in C# and PowerShell, with no Linux CLI or cross-platform examples. The XML configuration is shown under a <WindowsServer> element, and PowerShell is used for operational tasks, suggesting a Windows-first approach. There is no explicit mention of Linux-specific operational workflows, nor are Linux CLI equivalents (such as sfctl) demonstrated.
Recommendations
  • Add Linux-specific operational examples using sfctl (Service Fabric CLI) for service creation, updates, and placement constraints.
  • Clarify that ClusterConfig.json applies to both Linux and Windows standalone clusters, and provide explicit Linux deployment context where relevant.
  • Where PowerShell is used, provide equivalent commands for Linux/macOS users (e.g., sfctl or REST API).
  • Include notes or sections highlighting any differences or considerations for Linux clusters, especially in configuration and management tasks.
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-05 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 querying Service Fabric health, with no equivalent Linux/macOS CLI or REST API examples. This may create friction for users managing Service Fabric clusters from non-Windows environments.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • Include REST API examples for health queries, as these are platform-agnostic.
  • Explicitly mention that the PowerShell example is for Windows and provide guidance for Linux/macOS users.
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-05 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides PowerShell examples for creating and updating Service Fabric services with move cost, but does not include equivalent CLI or script examples for Linux/macOS users. PowerShell is primarily a Windows tool, and its use here creates friction for users managing Service Fabric clusters from Linux environments. All command-line examples are PowerShell-only, with no mention of Azure CLI, Bash, or other cross-platform tools.
Recommendations
  • Add equivalent Azure CLI or REST API examples for creating and updating Service Fabric services with move cost, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Clarify whether PowerShell examples are supported on Linux (via PowerShell Core), and provide guidance for Linux users if so.
  • Include Bash or script examples where possible, or reference documentation for Linux/macOS management of Service Fabric clusters.
  • Explicitly mention cross-platform management options for Service Fabric clusters, if available.
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-05 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 for service creation and updates, but there are no equivalent CLI (e.g., Bash, Azure CLI, or REST API) examples for Linux/macOS users. PowerShell is a Windows-centric tool, and its use without alternatives creates friction for non-Windows users. The C# API is cross-platform, but operational examples (service creation/update) are Windows-first and PowerShell-heavy.
Recommendations
  • Add Azure CLI or REST API examples for service sensitivity and maximum load configuration, if supported.
  • Clarify whether PowerShell commands can be run cross-platform (e.g., via PowerShell Core on Linux/macOS) or provide Bash/CLI alternatives.
  • Explicitly mention platform requirements for each example (e.g., 'Windows only', 'cross-platform', etc.).
  • Provide guidance for Linux/macOS users on how to perform equivalent operations.
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-05 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 a notable Windows bias. All deployment and management examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) without mention of Azure CLI equivalents or cross-platform scripting options. The application packaging workflow is described using Visual Studio, a Windows-centric tool, with no alternative guidance for Linux/macOS users. There are no Linux/macOS-specific instructions or examples, and Windows tools and patterns are presented first and exclusively.
Recommendations
  • Provide Azure CLI examples for deployment, upgrade, and deletion tasks alongside PowerShell examples.
  • Include instructions for packaging Service Fabric applications using cross-platform tools (e.g., dotnet CLI, SF SDK on Linux/macOS).
  • Mention alternative editors or build tools for non-Windows environments (e.g., VS Code, command-line packaging).
  • Clarify which steps are platform-agnostic and which require Windows, and offer Linux/macOS workarounds where possible.
  • Add notes or links to official cross-platform Service Fabric documentation.
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-05 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides a broad overview of Azure Service Fabric, which supports both Windows and Linux. However, there is a noticeable Windows bias in several areas: Windows services and executables (e.g., FabricHost.exe) are described in detail, often before Linux equivalents are mentioned or without Linux-specific details; PowerShell is frequently referenced as a primary management tool, with CLI and REST APIs listed as alternatives; and some examples and links (e.g., standalone cluster creation) are Windows-only, with Linux support explicitly called out as unavailable. Linux is acknowledged, but examples, tooling, and instructions are often Windows-centric or presented first.
Recommendations
  • Provide Linux-specific examples and instructions alongside Windows ones, especially for cluster management, service deployment, and health monitoring.
  • Reference Linux-native tools (e.g., Bash, Linux CLI) and workflows equally with PowerShell and Windows tools.
  • Where features are Windows-only, clearly label them as such and provide alternative guidance or links for Linux users.
  • Ensure that links to getting started, tutorials, and samples include Linux options where available.
  • Consider reordering sections so that Linux and Windows are presented with equal prominence, or explicitly state platform applicability at the start of each section.
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-05 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 include equivalent Linux/macOS CLI examples (such as Bash, Azure CLI, or REST API usage). PowerShell is presented first and exclusively for command-line operations, which may create friction for users managing Service Fabric clusters from non-Windows environments.
Recommendations
  • Add examples using Azure CLI or REST API for managing node tags and service requirements, which are cross-platform.
  • Include Bash or shell script examples for Linux/macOS users where applicable.
  • Clarify whether PowerShell Core (cross-platform) is supported, and if so, provide guidance for installation and usage on Linux/macOS.
  • Present cross-platform examples before or alongside Windows/PowerShell examples to improve parity.
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-05 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 referencing only PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) for cluster management tasks, without mentioning or providing equivalent Linux commands or tools. The linked 'scale a standalone cluster' documentation is Windows Server-specific, and there are no examples or guidance for Linux-based standalone clusters, despite Service Fabric supporting Linux nodes in some scenarios.
Recommendations
  • Provide equivalent Linux commands or scripts (e.g., using Service Fabric CLI or REST API) for cluster scaling operations.
  • Clarify whether standalone clusters can be managed on Linux, and if so, include Linux-specific instructions and examples.
  • If certain operations are Windows-only, explicitly state this in the documentation to set user expectations.
  • Reference cross-platform tools (such as sfctl) alongside PowerShell, and provide parity in example usage.
GitHub Create Pull Request
← Previous Page 74 of 99 Next →