Service Fabric

810
Total Pages
600
Linux-Friendly Pages
210
Pages with Bias
25.9%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

718 issues found
Showing 351-375 of 718 flagged pages
Service Fabric Deploy a Service Fabric managed cluster across Availability Zones ...ce-fabric/how-to-managed-cluster-availability-zones.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides command-line examples and instructions using PowerShell and the Az PowerShell module, with no mention of Linux/macOS equivalents (such as Azure CLI or Bash). Steps for cluster migration and node management reference PowerShell commands and tools exclusively, creating friction for users on non-Windows platforms.
Recommendations
  • Include Azure CLI (az) command examples alongside PowerShell, as Azure CLI is cross-platform and works on Linux/macOS.
  • Explicitly mention that all API calls can be performed using curl or other HTTP clients on any OS, and provide sample curl commands.
  • Clarify which steps require PowerShell and offer alternatives for Linux/macOS users.
  • Add notes or links to documentation for performing equivalent operations on Linux/macOS.
GitHub Create Pull Request
Service Fabric Service Fabric Explorer blocking operations ...ged-cluster-service-fabric-explorer-blocking-operation.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page primarily references PowerShell cmdlets (e.g., Remove-AzResource, AzSF PowerShell cmdlet) for managing Service Fabric resources, which are traditionally Windows-centric tools. There is no mention of Linux/macOS equivalents, nor are CLI examples (such as Azure CLI) provided alongside PowerShell. This creates friction for users on non-Windows platforms, as PowerShell is less commonly used or installed by default.
Recommendations
  • Include Azure CLI examples (e.g., az resource delete, az servicefabric managed-cluster application create) alongside PowerShell cmdlets for all operations.
  • Explicitly note platform compatibility for each tool and provide installation guidance for Linux/macOS users if PowerShell is required.
  • Where possible, recommend ARM template usage, which is platform-agnostic, and provide sample templates.
  • Add a section clarifying cross-platform management options and best practices.
GitHub Create Pull Request
Service Fabric Manage Azure Service Fabric application secrets ...fabric/service-fabric-application-secret-management.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides both Windows and Linux links for certificate setup, but scripting and automation examples (PowerShell and C#) are Windows-centric. There are no Linux CLI (e.g., Bash, sfctl) examples for creating application instances or overriding parameters, and PowerShell is presented as the default scripting method. Windows tools and patterns are mentioned first and exclusively in critical automation sections.
Recommendations
  • Add equivalent Linux command-line examples using sfctl or Bash scripts for creating application instances and overriding parameters.
  • Explicitly mention cross-platform tools and workflows where possible, not just PowerShell and C#.
  • Present Windows and Linux options side-by-side in automation sections, or clarify platform applicability for each example.
  • Reference Linux documentation links before or alongside Windows links to avoid 'windows_first' ordering.
GitHub Create Pull Request
Service Fabric Monitoring data reference for Azure Service Fabric ...les/service-fabric/monitor-service-fabric-reference.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. Performance counter examples and recommendations are exclusively based on Windows-specific counters and tools (e.g., Performance Monitor, Windows performance counters). There is no mention of Linux equivalents, nor are Linux monitoring tools or patterns referenced. The instructions and references assume a Windows environment, leaving Linux users without guidance for collecting similar metrics.
Recommendations
  • Add equivalent Linux performance metrics and counters (e.g., using /proc, sysstat, or collectd).
  • Include examples of how to collect metrics on Linux nodes, such as using common Linux monitoring tools (top, sar, vmstat, etc.).
  • Reference Linux-compatible agents and their configuration for Service Fabric monitoring.
  • Clarify which counters are Windows-only and provide Linux alternatives where possible.
  • Ensure documentation sections explicitly address both Windows and Linux environments.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Central Secret Service ...vice-fabric/service-fabric-application-secret-store.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a notable Windows bias. All REST API usage examples are provided exclusively in PowerShell, with no equivalent Linux/macOS shell (e.g., curl, bash) examples. Windows-specific tools and patterns (such as PowerShell and Windows file paths) are mentioned first and/or exclusively, while Linux equivalents are either absent or relegated to comments. This creates friction for Linux/macOS users attempting to follow the guidance.
Recommendations
  • Add Linux/macOS shell examples (e.g., curl commands) alongside PowerShell for all REST API operations.
  • Present both Windows and Linux file path mount examples equally, not as commented-out alternatives.
  • Explicitly mention cross-platform certificate installation and management steps, including Linux-specific guidance.
  • Ensure all configuration and usage instructions are platform-neutral or provide parallel instructions for both Windows and Linux/macOS.
  • Avoid using Windows tools (e.g., PowerShell) exclusively; offer alternatives or note platform requirements.
GitHub Create Pull Request
Service Fabric Monitor Azure Service Fabric ...main/articles/service-fabric/monitor-service-fabric.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example Powershell Heavy
Summary
The documentation page exhibits a moderate Windows bias. Windows-specific tools (EventStore APIs, Diagnostics Agent, Event Viewer, ETW providers) are mentioned before or in more detail than their Linux equivalents. Several tutorials and examples focus on .NET/Windows, with Linux alternatives referenced but not equally explained or linked. Linux monitoring approaches (e.g., Syslog, LTTng) are mentioned but lack step-by-step guidance or parity in example depth. PowerShell and Visual Studio are referenced without cross-platform alternatives.
Recommendations
  • Provide equivalent Linux-focused tutorials and examples, especially for cluster monitoring and application instrumentation.
  • Ensure all tool references (e.g., EventStore, Diagnostics Agent) include Linux-specific setup and usage instructions, not just links.
  • Add explicit Linux command-line examples (e.g., Bash, CLI) alongside PowerShell where automation is discussed.
  • Balance .NET/Windows application monitoring examples with those for Java, Node.js, or other Linux-friendly stacks.
  • Clarify which features/tools are Windows-only and suggest Linux alternatives or workarounds.
  • Include links to Linux documentation pages at parity with Windows references.
GitHub Create Pull Request
Service Fabric Architecture of Azure Service Fabric ...articles/service-fabric/service-fabric-architecture.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily in the Management subsystem section, where PowerShell cmdlets are mentioned as the main tooling for lifecycle management, with no mention of Linux/macOS equivalents (such as Azure CLI or REST APIs). Additionally, Windows security is referenced as an option for securing transport, but Linux alternatives are not discussed. No Linux-specific examples or tools are provided throughout the page.
Recommendations
  • Explicitly mention and provide examples for Linux/macOS management tools, such as Azure CLI and REST APIs, alongside PowerShell.
  • Clarify how transport security is handled on Linux clusters (e.g., X509 certificates) and provide guidance for non-Windows environments.
  • Ensure that any tooling or command-line references are cross-platform, or provide platform-specific instructions where necessary.
  • Add a section or note on Linux/macOS support and parity for Service Fabric management and security operations.
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-01-14 01:31
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 samples for configuring Service Fabric placement policies using C# and PowerShell only. PowerShell is a Windows-centric tool, and there are no equivalent examples for Linux/macOS users (e.g., Azure CLI, REST API, or bash). The configuration steps and automation patterns are presented exclusively with Windows tooling, which may create friction for users operating Service Fabric clusters on Linux or in cross-platform environments.
Recommendations
  • Add equivalent examples using Azure CLI and/or REST API for each placement policy configuration.
  • Explicitly mention cross-platform management options and link to relevant documentation for Linux/macOS users.
  • Reorder examples so that cross-platform tools (Azure CLI, REST API) are shown before or alongside PowerShell.
  • Clarify any platform-specific limitations or differences in Service Fabric management between Windows and Linux.
GitHub Create Pull Request
Service Fabric Update a cluster to use certificate common name ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-change-cert-thumbprint-to-cn.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides only PowerShell-based deployment instructions and examples, which are specific to Windows environments. There are no equivalent examples or guidance for Linux/macOS users, such as using Azure CLI or Bash. The use of Windows file paths in examples further reinforces the Windows-first approach.
Recommendations
  • Add Azure CLI examples for template deployment, suitable for Linux/macOS users.
  • Include Bash shell commands alongside PowerShell, especially for file operations and deployments.
  • Use platform-neutral file paths or clarify path conventions for different operating systems.
  • Explicitly mention cross-platform tooling and provide links to relevant documentation for Linux/macOS users.
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-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation shows a moderate Windows bias. Windows-specific tools (PowerShell, Windows Defender, DSC) are mentioned and demonstrated before or instead of Linux equivalents. Windows examples (PowerShell commands) are presented first in encryption sections, and Windows-specific security baselines and antivirus are covered in detail, while Linux alternatives are not discussed or are referenced only briefly. Some sections (e.g., Windows Defender, DSC) are Windows-only, with Linux users left to seek their own solutions.
Recommendations
  • Present Linux and Windows examples side-by-side, or alternate which platform is shown first.
  • Include Linux equivalents for Windows-specific tools (e.g., mention Linux security baselines, antivirus solutions, and configuration management tools like Ansible or Chef).
  • Add explicit guidance for Linux users where only Windows instructions are given, especially for security baselines and antivirus.
  • Clarify when a feature or tool is Windows-only and provide recommended Linux alternatives.
  • Ensure all code samples are available for both platforms where possible.
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-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Many configuration parameters and descriptions reference Windows-specific concepts, tools, or defaults (e.g., certificate store names like "MY", store locations like "LocalMachine", NTLM authentication, and references to Windows Defender Firewall). Some settings explicitly mention Windows-only applicability, and links or references to further documentation often point to Windows Server guides before Linux equivalents. Linux-specific details are present but less prominent, and Linux alternatives or differences are not always explained in parallel with Windows options.
Recommendations
  • For every Windows-specific parameter (e.g., certificate store names, NTLM authentication, firewall settings), add explicit Linux/macOS equivalents or clarify their applicability.
  • Where defaults differ between Windows and Linux (e.g., ContainerNetworkSetup), highlight both defaults and explain the rationale.
  • Provide links to Linux/macOS documentation alongside or before Windows Server documentation, especially in 'Next steps' and reference sections.
  • Add examples or guidance for Linux/macOS users where only Windows tools or patterns are mentioned (e.g., certificate management, firewall configuration).
  • Review terminology to ensure cross-platform neutrality (e.g., avoid 'Windows Fabric Replicator' when describing platform-agnostic features).
GitHub Create Pull Request
Service Fabric Scale a Service Fabric cluster in or out .../service-fabric/service-fabric-cluster-scale-in-out.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page exhibits a moderate Windows bias. Most code examples and operational instructions are given using PowerShell cmdlets, which are primarily Windows-centric. Windows-specific tools (e.g., ServiceFabric PowerShell module) are referenced and used extensively, with Linux/macOS equivalents (such as sfctl and Azure CLI) provided but often after the PowerShell examples. Some advanced operations (like node removal) are described in detail for PowerShell, with sfctl commands present but less emphasized. There are no explicit Linux/macOS-only examples or instructions, and the documentation assumes familiarity with Windows tooling.
Recommendations
  • Present Azure CLI and sfctl examples before or alongside PowerShell examples, not after.
  • Expand and clarify instructions for Linux/macOS users, including environment setup and prerequisites.
  • Ensure all operations described with PowerShell have equivalent, fully-detailed sfctl or Azure CLI workflows.
  • Explicitly mention platform compatibility for each tool and example.
  • Add troubleshooting or notes for common Linux/macOS issues (e.g., permissions, path differences).
GitHub Create Pull Request
Service Fabric Create a Service Fabric cluster in the Azure portal ...e-fabric/service-fabric-cluster-creation-via-portal.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation describes creating a Service Fabric cluster via the Azure portal, which supports both Linux and Windows clusters. However, the examples and instructions are written in a way that assumes Windows usage, such as requiring a username and password for Remote Desktop (RDP) access to VMs, which is a Windows-centric pattern. There are no explicit Linux-specific instructions, nor is SSH mentioned as a remote access method. Additionally, PowerShell is referenced for management operations, but there is no mention of Bash, Azure CLI, or Linux-native tools. This creates friction for Linux users, who may need to adapt Windows-centric steps to their environment.
Recommendations
  • Include explicit instructions for Linux clusters, such as SSH key setup for VM access instead of RDP credentials.
  • Provide examples for both Windows and Linux management operations, referencing Azure CLI and Bash where appropriate.
  • Clarify which steps differ for Linux clusters, especially around remote access and certificate handling.
  • Add notes or sections highlighting Linux-specific considerations and parity with Windows features.
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-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page consistently provides PowerShell examples for all command-line operations, with no mention of Linux/macOS equivalents (such as Bash, Azure CLI, or REST API). PowerShell is a Windows-centric tool, and its use is presented first and exclusively for scripting and management tasks. There is no guidance for users on Linux or macOS platforms, nor are alternative tools or commands referenced.
Recommendations
  • Add equivalent examples using Azure CLI, which is cross-platform, for all PowerShell commands.
  • Include REST API sample calls for management operations where applicable.
  • Explicitly mention Linux/macOS support and provide instructions for those platforms.
  • Reorder examples so that cross-platform tools (Azure CLI, REST API) are presented before or alongside PowerShell.
  • Clarify any platform-specific limitations or requirements for Service Fabric management.
GitHub Create Pull Request
Service Fabric Scalability of Service Fabric services .../service-fabric/service-fabric-concepts-scalability.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias in its examples and tooling references. PowerShell commands are provided for scaling operations, but there are no equivalent Linux CLI or bash examples. Windows-specific tools (PowerShell cmdlets) are referenced as the primary administrative mechanism, and no Linux-native alternatives (such as sfctl or bash scripts) are mentioned. The order of presentation also places Windows tooling before any mention of Linux, and Linux users are left to infer how to perform these tasks without direct guidance.
Recommendations
  • Add equivalent Linux examples using sfctl, bash, or REST API for all PowerShell commands.
  • Explicitly mention Linux administrative tools (e.g., sfctl) alongside PowerShell in all relevant sections.
  • Provide guidance or links for Linux/macOS users on how to perform scaling operations.
  • Ensure that examples alternate or present both Windows and Linux approaches side-by-side.
  • Clarify platform-specific limitations or differences in tooling, and direct users to platform-appropriate documentation.
GitHub Create Pull Request
Service Fabric Deploy a cluster across Availability Zones ...vice-fabric/service-fabric-cross-availability-zones.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias. All operational examples for cluster migration and management use PowerShell commands, with no equivalent Bash, Azure CLI, or Linux-native instructions. The sample template for the recommended deployment topology is explicitly for Windows, and Windows file paths (e.g., 'D:\\SvcFab') are used in configuration snippets. Linux or macOS users are not provided with direct guidance or parity in tooling, making it harder for them to follow the instructions.
Recommendations
  • Provide Azure CLI and Bash equivalents for all PowerShell commands, especially for cluster deployment, node disabling, and resource removal.
  • Include sample templates and configuration snippets for Linux clusters (e.g., Ubuntu), and reference them equally alongside Windows examples.
  • Use platform-neutral file paths or clarify how to set them for both Windows and Linux environments.
  • Explicitly mention cross-platform support and provide links to Linux/macOS documentation where relevant.
  • Ensure that operational steps (such as migration) are documented for both Windows and Linux users, not just Windows/PowerShell.
GitHub Create Pull Request
Service Fabric Health monitoring in Service Fabric ...s/service-fabric/service-fabric-health-introduction.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page provides a detailed conceptual overview of Service Fabric health monitoring, but the only concrete example of reporting and evaluating health uses Windows PowerShell cmdlets. There are no equivalent examples for Linux/macOS users (e.g., using REST API, CLI, or SDKs). The tools and patterns referenced (PowerShell, cluster manifest XML) are Windows-centric, and Linux parity is not demonstrated.
Recommendations
  • Add equivalent examples for Linux/macOS environments, such as using the Service Fabric CLI (sfctl), REST API, or SDKs (Python, .NET Core).
  • Explicitly mention cross-platform tools and workflows where PowerShell is referenced.
  • Provide sample commands for reporting and querying health from Linux shells (bash) and macOS.
  • Clarify which tools are available on which platforms, and link to installation/setup guides for Linux/macOS users.
  • Where XML manifests are referenced, note any platform-specific differences in deployment or configuration.
GitHub Create Pull Request
Service Fabric Networking patterns for Azure Service Fabric ...s/service-fabric/service-fabric-patterns-networking.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. All command-line deployment examples use PowerShell, with no mention of Azure CLI, Bash, or Linux/macOS workflows. Even basic connectivity checks use Windows-specific tools (RDP, Windows ping syntax), and there are no Linux/macOS equivalents or guidance. This creates friction for non-Windows users attempting to follow the steps.
Recommendations
  • Provide Azure CLI and Bash examples alongside PowerShell for all deployment commands.
  • Include Linux/macOS connectivity instructions (e.g., using SSH instead of RDP, Linux ping syntax).
  • Explicitly state cross-platform compatibility for templates and tools.
  • Add notes or sections for Linux/macOS users, highlighting any differences or requirements.
  • Where Windows tools are referenced (e.g., RDP), mention alternatives (e.g., SSH) and provide relevant instructions.
GitHub Create Pull Request
Service Fabric Add and remove node types of a Service Fabric managed cluster ...abric/tutorial-managed-cluster-add-remove-node-type.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily biased towards Windows, with all examples and instructions using Azure PowerShell. There are no CLI or Linux/macOS-specific examples, and PowerShell is listed as a prerequisite, which is primarily a Windows tool. This creates friction for Linux/macOS users who may prefer or require Azure CLI or bash-based workflows.
Recommendations
  • Include equivalent Azure CLI examples for all operations (adding/removing node types).
  • List both PowerShell and CLI as prerequisites, with installation links for Linux/macOS.
  • Explicitly mention cross-platform options and provide bash script examples where relevant.
  • Clarify which steps are platform-agnostic and which require Windows-specific tools.
GitHub Create Pull Request
Service Fabric Deploy a Service Fabric managed cluster ...cles/service-fabric/tutorial-managed-cluster-deploy.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively uses PowerShell commands and references Windows-specific tools (Service Fabric SDK and PowerShell module, Azure PowerShell), with no mention of Linux/macOS equivalents or cross-platform CLI alternatives. All examples and instructions assume a Windows environment, creating friction for users on Linux or macOS.
Recommendations
  • Provide Azure CLI examples alongside PowerShell commands, as Azure CLI is cross-platform.
  • Clarify whether the Service Fabric SDK and management tools are available for Linux/macOS, and provide installation instructions for those platforms.
  • Explicitly mention platform compatibility and offer guidance for Linux/macOS users.
  • Reorder or parallelize examples so that Windows and Linux/macOS options are presented equally.
GitHub Create Pull Request
Service Fabric Scale out a Service Fabric managed cluster ...icles/service-fabric/tutorial-managed-cluster-scale.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively uses Azure PowerShell for scaling out a Service Fabric managed cluster, providing only a PowerShell example and listing Azure PowerShell as a prerequisite. There are no CLI, Bash, or Linux/macOS-specific instructions or examples, and Windows tooling is mentioned first and exclusively.
Recommendations
  • Add equivalent Azure CLI examples for scaling out node types, which work cross-platform (Linux, macOS, Windows).
  • List both Azure PowerShell and Azure CLI as supported tools in prerequisites.
  • Explicitly mention that the operation can be performed from Linux/macOS using Azure CLI.
  • Consider providing Bash script examples alongside PowerShell.
  • Clarify any platform-specific limitations, if any exist.
GitHub Create Pull Request
Service Fabric Replica soft delete for enhanced data protection in Service Fabric ...s/service-fabric/service-fabric-replica-soft-delete.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias by exclusively referencing PowerShell-based administrative APIs (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica) and showing only PowerShell command examples. There is no mention of Linux/macOS equivalents, CLI alternatives, or cross-platform SDK usage patterns. Windows tools and terminology are used throughout, and examples are Windows-centric, creating friction for Linux/macOS users.
Recommendations
  • Provide equivalent examples using Service Fabric CLI (sfctl) for Linux/macOS users, where available.
  • Explicitly document how to perform replica soft delete and restore operations using REST APIs or FabricClient SDK in cross-platform languages (e.g., Python, .NET Core).
  • Clarify which APIs and tools are available on Linux clusters and how to access them.
  • Add a section summarizing cross-platform support and differences in administrative tooling.
  • Ensure screenshots and command outputs include Linux/macOS variants where applicable.
GitHub Create Pull Request
Service Fabric Scale a Service Fabric cluster in Azure ...ervice-fabric/service-fabric-tutorial-scale-cluster.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page exhibits a notable Windows bias. The tutorial repeatedly references creating a secure Windows cluster, with no mention or examples for Linux clusters. All code snippets and template references are for Windows clusters, and the linked sample templates are Windows-only. PowerShell commands are shown first and in greater detail, with Azure CLI as a secondary option. Windows-specific tools and concepts (e.g., RDP, Windows file paths, Windows Service Fabric node extensions) are referenced throughout, while Linux equivalents are not discussed or provided.
Recommendations
  • Add explicit instructions and examples for scaling Linux Service Fabric clusters, including template references and parameter differences.
  • Provide Linux-specific code snippets and clarify any OS-specific steps, especially for VM extensions, file paths, and node management.
  • Include links to Linux sample templates and parameter files.
  • Discuss differences in durability, reliability, and node management between Windows and Linux clusters.
  • Present Azure CLI examples before or alongside PowerShell, and clarify cross-platform compatibility.
  • Avoid Windows-specific terminology (e.g., RDP, Windows file paths) or provide Linux alternatives (e.g., SSH, Linux file paths).
GitHub Create Pull Request
Service Fabric How to view Azure Service Fabric entities' aggregated health ...bric/service-fabric-view-entities-aggregated-health.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. All command-line examples use PowerShell cmdlets, which are native to Windows and not available by default on Linux/macOS. The examples reference Windows file paths (e.g., D:\ServiceFabric, C:\), and there is no mention of Linux/macOS equivalents or cross-platform CLI tools (such as Azure CLI or Service Fabric CLI). Windows tools and patterns are presented exclusively and before REST or API alternatives, and there are no Linux-specific instructions or examples.
Recommendations
  • Add equivalent examples using Azure CLI (az sf) or Service Fabric CLI (sfctl), which are cross-platform and supported on Linux/macOS.
  • Include notes or sections clarifying how Linux/macOS users can perform the same tasks, including installation steps for CLI tools.
  • Avoid using Windows-specific file paths in examples, or provide platform-agnostic alternatives.
  • Explicitly mention the availability of PowerShell Core on Linux/macOS, if relevant, and provide usage instructions.
  • Reorder examples so that REST/API or cross-platform CLI instructions are presented before or alongside PowerShell examples.
GitHub Create Pull Request
Service Fabric Use Azure DDoS Protection in a Service Fabric managed cluster ...rvice-fabric/how-to-managed-cluster-ddos-protection.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by providing only Azure PowerShell examples for key steps, such as retrieving the Service Principal and assigning roles. There are no equivalent Azure CLI or Bash examples, and PowerShell commands are presented first and exclusively. This may create friction for Linux/macOS users who typically use Azure CLI or Bash scripts.
Recommendations
  • Add equivalent Azure CLI commands for all PowerShell examples, especially for service principal retrieval and role assignment.
  • Explicitly mention that both Azure PowerShell and Azure CLI can be used, and provide links to relevant CLI documentation.
  • Where possible, show CLI/Bash examples before or alongside PowerShell to ensure parity and inclusivity.
  • Clarify that ARM templates are platform-agnostic and can be deployed from any OS.
GitHub Create Pull Request
← Previous Page 15 of 29 Next →