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 1126-1150 of 2475 flagged pages
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-02-20 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides detailed PowerShell-based migration steps for Service Fabric clusters, especially in the 'Basic SKU load balancer and IP resources' migration scenario. All imperative command-line examples use PowerShell cmdlets, with no equivalent Azure CLI or bash examples. This may create friction for Linux/macOS users who do not have access to PowerShell or prefer cross-platform tooling.
Recommendations
  • Provide equivalent Azure CLI (az) commands for all PowerShell examples, especially for resource deployment, node disabling, and resource cleanup.
  • Explicitly mention that the migration can be performed from any platform using Azure CLI or ARM templates, not just PowerShell.
  • Where possible, link to ARM/Bicep template documentation and show how to use them from bash or cross-platform environments.
  • Add a note clarifying that PowerShell is not required and that all operations can be performed using cross-platform tools.
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-20 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation covers monitoring for both Windows and Linux Service Fabric clusters, but there are several areas where Windows tools and patterns are mentioned first or exclusively, and Linux equivalents are referenced later or less prominently. Some examples and tutorials are Windows/.NET-centric, and certain features (like EventStore APIs) are Windows-only, but this is clearly stated. Linux monitoring is supported, but configuration details and examples are less visible or are referenced via links rather than inline explanations.
Recommendations
  • Ensure Linux monitoring configuration steps and examples are as prominent and detailed as Windows ones, especially for cluster and infrastructure monitoring.
  • Provide Linux-specific tutorials and code samples (e.g., for application logging, cluster diagnostics, and performance counters) alongside Windows/.NET examples.
  • Mention Linux tools and patterns (such as LTTng, Syslog, and relevant logging frameworks) before or alongside Windows tools like ETW and Event Viewer.
  • Clarify which features are Windows-only and provide alternative approaches for Linux users where possible.
  • Add links to Linux-focused monitoring partner integrations and open source tools.
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-20 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page for describing Azure Service Fabric apps and services exhibits mild Windows bias. It references Windows file paths (e.g., 'C:\Program Files\Microsoft SDKs\Service Fabric\schemas\ServiceFabricServiceModel.xsd'), suggests using Visual Studio (a Windows-centric tool) for schema validation, and mentions the ServiceFabric PowerShell module for service creation. No equivalent Linux tooling or examples are provided, and Windows-specific patterns are mentioned first or exclusively. However, the core content (manifest XML) is platform-neutral, and Linux users can complete the tasks with workarounds.
Recommendations
  • Add instructions for validating manifest XML schema on Linux/macOS, such as using 'xmllint' or VS Code with XML extensions.
  • Mention cross-platform alternatives to Visual Studio, like Visual Studio Code or JetBrains Rider.
  • Provide examples of using Service Fabric CLI (sfctl) or REST API for service creation, alongside PowerShell.
  • Clarify that Service Fabric development and deployment can be done on Linux, and link to relevant Linux documentation.
GitHub Create Pull Request
Service Fabric Azure Service Fabric DNS service ...n/articles/service-fabric/service-fabric-dnsservice.md
Medium Priority View Details →
Scanned: 2026-02-20 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides PowerShell examples for setting DNS names, references ApplicationManifest.xml (a Windows-centric deployment pattern), and does not offer equivalent Linux CLI or scripting examples. Enabling DNS service via Azure portal is only possible for Windows clusters, and Linux support is limited and discussed secondarily. There are no Linux-specific deployment or configuration examples, and Windows tools/patterns are mentioned first or exclusively.
Recommendations
  • Add Linux CLI examples (e.g., Bash, Azure CLI) for setting DNS names and managing Service Fabric services.
  • Clarify Linux deployment workflows, including how to set DNS names for containerized services on Linux clusters.
  • Provide guidance for enabling DNS service on Linux clusters using ARM templates or other methods, since portal support is unavailable.
  • Include notes or links to Linux-specific documentation or troubleshooting.
  • Balance the order of Windows and Linux information, mentioning Linux options alongside Windows where applicable.
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-20 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation covers Azure Service Fabric application security in a cross-platform manner but exhibits some Windows bias. Windows-specific tools and patterns (e.g., Active Directory, gMSA, BitLocker, NetworkService account) are mentioned before or more prominently than Linux equivalents. Some sections (e.g., disk encryption, user accounts) provide Windows-focused examples or references, while Linux guidance is missing or relegated to TODO comments.
Recommendations
  • Add Linux-specific examples for disk encryption (e.g., using Azure Disk Encryption with Linux VMSS, or referencing LUKS).
  • Provide guidance on configuring user accounts and security principals for Linux clusters, including how to run services under different Linux users/groups.
  • Ensure parity in certificate management and container security examples for Linux clusters.
  • When mentioning Windows tools or patterns (e.g., BitLocker, gMSA, NetworkService), immediately follow with Linux equivalents or clarify platform applicability.
  • Remove or resolve TODO comments regarding Linux disk encryption and provide actionable documentation.
  • Include sample manifests or scripts for Linux scenarios where possible.
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-20 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 notable Windows bias. PowerShell is used exclusively in the main example for upgrading applications and handling application parameters, with no equivalent CLI or Linux-native example. Windows-specific tools (PowerShell, http.sys) are referenced without mention of cross-platform alternatives. The 'Next steps' section prioritizes Visual Studio and PowerShell tutorials, both Windows-centric, with no Linux or cross-platform guidance. This creates friction for Linux/macOS users, who may not have access to PowerShell or Visual Studio.
Recommendations
  • Add equivalent examples using Azure CLI or Service Fabric CLI (sfctl), which are cross-platform and supported on Linux/macOS.
  • Mention Linux/macOS-compatible tools and workflows for application upgrades.
  • Provide links to Linux/macOS-specific documentation or tutorials, if available.
  • Clarify which features are Windows-only and which are cross-platform, especially when referencing http.sys or PowerShell.
  • Ensure that examples and guidance are balanced, showing both Windows and Linux approaches where 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-20 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation frequently uses PowerShell cmdlets (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState) for manual scaling operations without providing equivalent Linux/CLI commands. All step-by-step manual procedures reference PowerShell, and there are no Bash, Azure CLI, or REST API alternatives shown. The documentation also refers to 'PowerShell' generically for cluster management tasks, which may not be directly applicable to Linux/macOS users. Additionally, in several sections, Windows tools and patterns are mentioned first or exclusively, with Linux alternatives only referenced in the 'Next steps' section.
Recommendations
  • For every PowerShell-based example (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState), provide equivalent Azure CLI, Bash, or REST API commands where possible.
  • Explicitly state when a command or tool is Windows-only, and link to Linux/macOS alternatives.
  • In step-by-step guides, offer parallel instructions for Linux users, or clarify if the operation must be performed from a Windows environment.
  • When referencing Service Fabric Explorer or other tools, note any cross-platform considerations.
  • Balance the order of 'Next steps' so Linux and Windows cluster creation links are presented equally.
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-20 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Minor Windows Example
Summary
The documentation provides both Windows and Linux guidance for Service Fabric networking, but there are several areas where Windows concepts, tools, and examples are emphasized or presented first. PowerShell and Windows-specific terminology appear more frequently, and some example links and references (such as ARM templates and DevOps tasks) are Windows-centric. Linux equivalents are mentioned but often after Windows, and some explanations assume familiarity with Windows networking tools.
Recommendations
  • Ensure Linux examples and references are given equal prominence and are presented alongside Windows examples, not after.
  • Where PowerShell is mentioned, include corresponding Bash/CLI commands for Linux users.
  • Add links to Linux-focused ARM templates and sample clusters, not just Windows ones.
  • Clarify which features or steps are platform-agnostic and which are Windows-specific.
  • Expand explanations for Linux networking (e.g., dynamic port ranges, firewall configuration) to match Windows detail.
  • Avoid referencing Windows tools (e.g., netsh) without Linux equivalents (e.g., ss, iptables, etc.).
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-20 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page frequently references PowerShell cmdlets and Windows-centric tooling for Service Fabric application lifecycle operations, often listing them before or alongside REST API and .NET methods. There is minimal mention of Linux-specific tools or CLI equivalents, and PowerShell is presented as the primary scripting interface. While REST API and .NET methods are included, Linux users may experience friction due to the lack of explicit Linux/CLI examples and guidance.
Recommendations
  • Add explicit examples using Service Fabric CLI (sfctl) and Azure CLI for each lifecycle operation, especially for deployment, upgrade, removal, and cleanup tasks.
  • Where PowerShell cmdlets are mentioned, also provide equivalent sfctl or Azure CLI commands, and clarify their applicability to Linux/macOS environments.
  • Reorder examples so that cross-platform tools (REST API, sfctl, Azure CLI) are listed before or alongside PowerShell cmdlets.
  • Include a section or note clarifying which tools are available and supported on Linux/macOS, and link to relevant Linux documentation.
  • Provide sample shell scripts or command-line workflows for Linux users, especially for automation and cleanup scenarios.
GitHub Create Pull Request
Service Fabric Advanced Application Upgrade Topics ...-fabric/service-fabric-application-upgrade-advanced.md
Medium Priority View Details →
Scanned: 2026-02-20 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 extensive PowerShell-based examples and references, with no mention of Linux/macOS equivalents (such as Azure CLI, REST API, or cross-platform tooling). Windows/PowerShell tools are referenced exclusively and repeatedly, and all command-line examples are PowerShell-centric. There is no guidance for Linux/macOS users on how to perform the same tasks, despite Service Fabric supporting cross-platform clusters and management.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell cmdlets shown, especially for application upgrades, service creation, and parameter updates.
  • Reference REST API endpoints where applicable, and provide sample payloads for ARM template operations.
  • Explicitly mention cross-platform management options (e.g., Azure CLI, REST API, SDKs) and link to relevant documentation.
  • Where PowerShell is referenced, clarify if the cmdlets are available on Linux/macOS (via PowerShell Core), or provide alternatives if not.
  • Ensure that 'Next steps' and tutorial links include Linux/macOS-compatible workflows (e.g., CLI or SDK-based tutorials).
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-20 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 toward Windows and 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 using Windows and PowerShell, creating friction for Linux/macOS users.
Recommendations
  • Add equivalent Bash/curl examples for REST API calls, showing how to authenticate and invoke the Service Fabric APIs from Linux/macOS.
  • Document any cross-platform CLI tools (e.g., Azure CLI, Service Fabric CLI) that can be used for backup/restore operations.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is required for REST API calls, or if standard HTTP tools can be used.
  • Mention prerequisites or limitations for Linux/macOS users, and provide links to relevant cross-platform guidance.
  • Consider providing a table or section comparing Windows and Linux/macOS approaches for backup/restore operations.
GitHub Create Pull Request
Service Fabric Understanding periodic backup configuration ...-fabric-backuprestoreservice-configure-periodic-backup.md
Medium Priority View Details →
Scanned: 2026-02-20 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation provides a generally platform-neutral overview of periodic backup configuration in Azure Service Fabric. However, in the 'File share' backup storage section, Windows-specific patterns are emphasized: examples use UNC paths (\\StorageServer\BackupStore), and authentication options focus on Integrated Windows Authentication and username/password, which are Windows-centric. There is no mention of Linux-compatible file share options (e.g., SMB/CIFS mounts on Linux, NFS, or Azure Files usage from Linux nodes). The documentation also presents Windows file share options before any discussion of Linux equivalents, and does not clarify cross-platform support or limitations.
Recommendations
  • Add examples and guidance for configuring file share backup storage from Linux-based Service Fabric clusters, including supported protocols (e.g., SMB/CIFS, NFS, Azure Files) and authentication methods.
  • Clarify whether Integrated Windows Authentication is required, or if Linux clusters can use username/password or other mechanisms.
  • Explicitly state any platform limitations for file share backup storage, and provide parity guidance for Linux/macOS users.
  • Consider including a note or section on cross-platform compatibility for all backup storage types.
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-20 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 Resource Manager templates, but PowerShell is presented as a separate section and is heavily used for cluster upgrade operations. Windows-specific tools and registry keys are mentioned for patch management and update disabling, with no Linux equivalents or guidance. The manual upgrade section only provides PowerShell commands for Windows, omitting Linux (deb) instructions. Windows configuration properties are shown first in VM scale set examples. While Linux is referenced in template samples and cluster creation links, the operational guidance and scripting are notably Windows-centric.
Recommendations
  • Add equivalent Linux shell (bash) examples for cluster upgrade operations, especially for manual upgrades using deb packages.
  • Include guidance on disabling automatic updates for Linux VM scale sets, such as relevant OS profile settings or scripts.
  • Provide Linux-specific instructions or notes where Windows registry keys and PowerShell are referenced.
  • Ensure parity in operational examples by including both Windows and Linux approaches side-by-side.
  • When showing VM scale set configuration, include Linux configuration properties alongside Windows.
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-20 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 examples for key security tasks, such as certificate generation and secret encryption. However, Windows-specific tools (PowerShell, Windows Defender, Azure DSC) are often mentioned first or exclusively, and Windows-centric guidance (e.g., security baselines, Defender exclusions) is more detailed. Linux equivalents are present but sometimes less prominent or detailed.
Recommendations
  • Ensure Linux examples are given equal prominence and detail as Windows examples, especially for certificate management and secret encryption.
  • Where Windows tools (e.g., PowerShell, Windows Defender, DSC) are mentioned, provide clear Linux alternatives or note their absence.
  • Add guidance for Linux security baselines and antimalware solutions, or explicitly state if no equivalent exists.
  • Consider alternating the order of Windows and Linux examples to avoid 'windows_first' bias.
  • Expand Linux-specific troubleshooting and best practices sections to match Windows coverage.
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-20 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Data Path Windows Pattern Powershell Heavy
Summary
The documentation generally covers both Linux and Windows node types for Azure Service Fabric clusters, but there are subtle signs of Windows bias. The 'dataPath' example uses a Windows-style path ('D:\\SvcFab'), and the 'Next steps' section links primarily to PowerShell scripts for Windows-specific tasks (changing RDP port range, admin username/password), without Linux equivalents or Bash/CLI alternatives. Windows patterns and tools are referenced first or exclusively in some places.
Recommendations
  • Provide Linux-style examples for 'dataPath' (e.g., '/var/svcfab') alongside Windows paths.
  • Add links or instructions for performing remote connection, port changes, and admin credential updates on Linux clusters, using Bash or Azure CLI.
  • Ensure parity in 'Next steps' by including Linux-focused guidance and scripts.
  • Clarify when instructions or examples are Windows-only, and offer Linux alternatives where possible.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager: Movement cost ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-movement-cost.md
Medium Priority View Details →
Scanned: 2026-02-20 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 configuring move cost, 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# examples are cross-platform, but administrative/configuration examples are Windows-centric. There is no mention of Azure CLI, Bash, or Linux-native tools for managing Service Fabric services.
Recommendations
  • Add Azure CLI or Bash examples for creating and updating Service Fabric services with move cost.
  • Explicitly mention whether PowerShell commands are supported on Linux/macOS (via PowerShell Core), and provide guidance for those platforms.
  • If PowerShell is the only supported scripting interface, clarify this in the documentation and link to any Linux/macOS installation instructions.
  • Consider including REST API examples for service management tasks, which are platform-neutral.
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-20 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 code examples for configuring Service Fabric placement policies using C# and PowerShell only. PowerShell is a Windows-centric tool, and there are no examples or guidance for Linux-based Service Fabric clusters, such as using Azure CLI, REST API, or cross-platform tools. This creates friction for Linux/macOS users who cannot use PowerShell natively.
Recommendations
  • Add equivalent examples using Azure CLI (az sf) for all placement policy configurations.
  • Document how to configure placement policies via ARM templates or REST API for cross-platform automation.
  • Explicitly note any differences or limitations for Linux-based Service Fabric clusters, if applicable.
  • If PowerShell is required, mention how to use PowerShell Core on Linux/macOS, or provide alternatives.
  • Consider including YAML or JSON snippets for ARM/Bicep deployments where relevant.
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-20 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides 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 Linux shell (bash/CLI) equivalents. PowerShell is presented as the only scripting option, and there is no mention of Linux tools or commands for managing scaling policies. The documentation does note that resource monitoring is supported for containerized applications on Linux, but practical Linux usage examples are missing.
Recommendations
  • Add equivalent bash/CLI examples for managing scaling policies on Linux clusters, using Service Fabric CLI (sfctl) or REST APIs.
  • Explicitly mention cross-platform management tools and provide links or references to Linux/macOS documentation.
  • Clarify which PowerShell commands are available on Linux (via PowerShell Core), or provide alternative commands if they are Windows-only.
  • Include a section or note on how Linux users can perform the same operations, especially for containerized workloads.
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-20 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation provides both Windows-specific (ClusterManifest.xml with <WindowsServer>) and cross-platform (ClusterConfig.json) configuration examples. However, Windows terminology and XML examples are presented first and more prominently, and PowerShell is used for CLI examples, with no Linux shell or cross-platform CLI equivalents. The use of WindowsServer in the XML and PowerShell commands suggests a Windows-first bias, though Linux/standalone parity is addressed via JSON examples.
Recommendations
  • Include Linux-specific or cross-platform CLI examples (e.g., Azure CLI, Bash) alongside PowerShell.
  • Present Linux/standalone configuration examples (ClusterConfig.json) before or equally with Windows XML examples.
  • Clarify which features and configuration patterns are supported on Linux clusters, and note any Windows-only limitations.
  • Add explicit guidance or links for Linux users, such as how to run Service Fabric clusters on Linux and configure fault/upgrade domains.
  • Where PowerShell is used, provide equivalent Azure CLI or Bash script examples.
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-20 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 managing Service Fabric metrics using C# and PowerShell. PowerShell is a Windows-centric tool, and no equivalent Linux/macOS CLI examples (such as Azure CLI or Bash) are provided. The PowerShell examples are prominent and appear before any mention of alternative tooling. There is no discussion of how Linux users can accomplish these tasks, nor is there mention of cross-platform tools or patterns.
Recommendations
  • Add Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention whether the PowerShell commands are supported on Linux (via PowerShell Core), or provide Bash scripts if possible.
  • Clarify any platform-specific limitations for Service Fabric management, and provide guidance for Linux/macOS users.
  • Consider including REST API or SDK usage examples that are platform-agnostic.
  • Reorder examples so that cross-platform options (Azure CLI, REST API) are shown before or alongside PowerShell.
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-20 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 mention or provide equivalent CLI or scripting examples for Linux/macOS users. PowerShell is presented as the primary scripting interface, and there is no reference to Service Fabric CLI (sfctl) or REST API usage, which are cross-platform. This creates friction for Linux/macOS administrators who may not have access to PowerShell or prefer native tools.
Recommendations
  • Add examples using Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • Mention REST API options for configuring service sensitivity and maximum load, with example requests.
  • Clarify which PowerShell commands are available on Linux (via PowerShell Core) and which are Windows-only.
  • Present CLI or REST API examples before or alongside PowerShell examples to avoid Windows-first bias.
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-20 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides code examples and administrative patterns primarily using PowerShell and C#, with no equivalent Linux CLI or scripting examples. Windows/PowerShell tools are referenced exclusively and first, creating friction for Linux users who may need to perform similar operations using Service Fabric CLI or REST APIs. The section 'Choosing a platform' does acknowledge Linux-specific implementation differences, but the practical guidance and examples remain Windows-centric.
Recommendations
  • Add equivalent Linux command-line examples using Service Fabric CLI (sfctl) or REST API for operations such as updating instance counts, creating services, and managing applications.
  • Mention Linux tools and administrative patterns alongside PowerShell, not just in the 'Choosing a platform' section.
  • Where PowerShell is referenced, provide a note or link to Linux documentation or examples.
  • Ensure that guidance for scaling, service creation, and management is platform-neutral or clearly indicates platform-specific steps.
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-20 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page provides PowerShell examples for managing node tags and service requirements, but does not offer equivalent examples for Linux/macOS users (e.g., Bash, CLI, or REST API usage). PowerShell is a Windows-centric tool, and its exclusive use creates friction for users on other platforms. The page also references PowerShell before C# APIs, and does not mention or demonstrate Azure CLI or REST API commands, which are cross-platform.
Recommendations
  • Add Azure CLI examples for all node tag and service tag operations, as Azure CLI is cross-platform and widely used.
  • Include REST API usage examples for managing node tags and service requirements, since REST APIs are platform-agnostic.
  • Explicitly mention that PowerShell commands can be run on Linux/macOS if supported, or clarify any limitations.
  • Consider providing Bash script examples or guidance for Linux users where applicable.
  • Reorder examples so that cross-platform tools (CLI/REST) are presented before Windows-specific tools like PowerShell.
GitHub Create Pull Request
Service Fabric Azure Service Fabric standalone cluster scaling ...ce-fabric/service-fabric-cluster-scaling-standalone.md
Medium Priority View Details →
Scanned: 2026-02-20 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page on scaling Azure Service Fabric standalone clusters demonstrates Windows bias by exclusively referencing Windows PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) and linking to a Windows Server-specific scaling guide. There are no Linux-specific examples, tools, or guidance, despite standalone clusters being deployable on both Windows and Linux. This creates friction for Linux users seeking parity.
Recommendations
  • Add equivalent Linux command-line examples (e.g., using sfctl or REST API) for cluster manifest queries and configuration upgrades.
  • Clarify which steps or tools are Windows-only and provide Linux alternatives where possible.
  • Link to Linux-specific scaling documentation or create a dedicated guide for scaling standalone clusters on Linux.
  • Mention cross-platform management options (such as sfctl, REST API, or Azure CLI) alongside PowerShell.
  • Ensure references to Windows Server guides are balanced with Linux guidance.
GitHub Create Pull Request
Service Fabric Upgrade an Azure Service Fabric standalone cluster ...ce-fabric/service-fabric-cluster-upgrade-standalone.md
Medium Priority View Details →
Scanned: 2026-02-20 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page references Windows-specific upgrade and configuration guides (e.g., 'service-fabric-cluster-upgrade-windows-server.md', 'service-fabric-cluster-config-upgrade-windows-server.md') and the Patch Orchestration Application for Windows. There are no explicit Linux or cross-platform examples, and Linux equivalents are not mentioned or linked. The page does not clarify whether Linux clusters are supported or provide guidance for Linux users.
Recommendations
  • Add links and instructions for upgrading and configuring Service Fabric standalone clusters running on Linux, if supported.
  • Mention Linux-specific patch orchestration options or clarify if POA is Windows-only.
  • Ensure that references to upgrade/configuration guides are not Windows-exclusive, or clearly state platform limitations.
  • Provide parity in examples and guidance for Linux/macOS users where applicable.
GitHub Create Pull Request
← Previous Page 46 of 99 Next →