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 301-325 of 718 flagged pages
Service Fabric Cluster Resource Manager - Management Integration ...fabric-cluster-resource-manager-management-integration.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 provides a detailed example of querying Service Fabric partition health using a PowerShell command, which is specific to Windows environments. There are no equivalent Linux/macOS CLI examples (such as using sfctl or REST API), and the only tool shown for interacting with Service Fabric is PowerShell. This creates friction for Linux/macOS users who cannot use PowerShell natively.
Recommendations
  • Add equivalent examples using sfctl (Service Fabric CLI) for Linux/macOS users.
  • Include REST API example for querying partition health, which is platform-agnostic.
  • When showing command-line examples, present both Windows (PowerShell) and Linux/macOS (sfctl/REST) options side-by-side.
  • Explicitly mention cross-platform tooling and provide links to installation guides for sfctl.
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-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 examples use PowerShell cmdlets (e.g., New-ServiceFabricService, Update-ServiceFabricService), with no equivalent Bash, CLI, or Linux-native examples. Windows/PowerShell tooling is referenced exclusively and before any cross-platform alternatives, and there is no mention of how to perform these tasks on Linux or macOS clusters. This creates friction for non-Windows users and may prevent them from easily following the instructions.
Recommendations
  • Provide equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform.
  • Include Bash script examples or instructions for Linux environments where appropriate.
  • Explicitly state whether the described PowerShell cmdlets are available on Linux/macOS, or provide alternatives.
  • Add a section clarifying platform support and differences in tooling between Windows and Linux clusters.
  • Reference Service Fabric REST APIs for cluster management tasks, which are platform-agnostic.
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-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 command-line examples exclusively using PowerShell, which is a Windows-centric tool. There are no CLI examples for Linux/macOS users (e.g., Bash, Azure CLI, or REST API via curl). The PowerShell examples are presented before any mention of alternatives, and no Linux-specific tools or patterns are discussed. This creates friction for users managing Service Fabric clusters from non-Windows environments.
Recommendations
  • Add equivalent command-line examples using Azure CLI or Bash scripts for Linux/macOS users.
  • Include REST API usage examples with curl or httpie to demonstrate cross-platform management.
  • Clearly indicate which tools are cross-platform and provide installation/setup guidance for Linux/macOS.
  • Reorder examples or provide parallel examples for Windows and Linux/macOS to avoid Windows-first bias.
GitHub Create Pull Request
Service Fabric Manage certificates in an Azure Service Fabric cluster ...https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-security-update-certs-azure.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. All command-line examples for deploying and managing certificates use Azure PowerShell, with no mention of Azure CLI or Bash alternatives. Certificate import instructions reference Windows certificate stores and PowerShell cmdlets exclusively. There are no Linux/macOS-specific instructions or examples for certificate management, deployment, or cluster connection, and Windows-centric tools and patterns are presented first and exclusively.
Recommendations
  • Add equivalent Azure CLI examples for template deployment, testing, and resource group management.
  • Provide instructions for importing certificates on Linux/macOS, such as using OpenSSL or system certificate stores.
  • Include Bash or shell script examples for cluster connection and certificate management.
  • Clarify any OS-specific requirements or differences in certificate handling.
  • Present cross-platform options side-by-side or indicate which steps are OS-agnostic.
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-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 configuration examples using XML, JSON, PowerShell, and C#. However, all command-line examples use PowerShell, which is Windows-specific, and there are no equivalent CLI or scripting examples for Linux/macOS environments (e.g., Bash, Azure CLI, or REST API). PowerShell examples are presented before C# API examples, reinforcing a Windows-first approach. There is no mention of Linux-native tooling or cross-platform alternatives for managing Service Fabric services.
Recommendations
  • Add equivalent examples using Azure CLI or REST API for service sensitivity and maximum load configuration, which are cross-platform.
  • Provide Bash scripting examples for Linux users where applicable.
  • Clarify which APIs and tools are supported on Linux/macOS and provide guidance for those platforms.
  • Reorder examples to present cross-platform methods (e.g., JSON config, Azure CLI) before Windows-specific tools like PowerShell.
  • Explicitly mention Linux/macOS support and any limitations in the introduction or relevant sections.
GitHub Create Pull Request
Service Fabric Roll over an Azure Service Fabric cluster certificate ...vice-fabric/service-fabric-cluster-rollover-cert-cn.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 provides only a PowerShell script for certificate rollover, with Windows-style file paths and no mention of Linux or cross-platform alternatives. There are no Bash, CLI, or Linux/macOS-specific instructions, and the use of PowerShell and Windows file conventions is assumed throughout.
Recommendations
  • Add equivalent Bash/Azure CLI examples for certificate upload and VMSS update.
  • Use cross-platform file path examples or note differences for Linux/macOS users.
  • Explicitly state whether the process can be completed on Linux/macOS, and provide guidance for those platforms.
  • Mention prerequisites or alternative tooling for non-Windows environments (e.g., Azure CLI, OpenSSL).
GitHub Create Pull Request
Service Fabric Secure an Azure Service Fabric cluster ...cles/service-fabric/service-fabric-cluster-security.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 exhibits a moderate Windows bias. Standalone cluster security is described only for Windows Server, with explicit references to Windows security (Kerberos, group Managed Service Accounts, Windows accounts) and Windows certificate tools. There are no equivalent instructions or references for standalone Linux clusters, nor are Linux-specific security mechanisms or certificate management tools mentioned. Windows scenarios are described in detail, while Linux is only referenced generically or in passing.
Recommendations
  • Add explicit instructions and links for securing standalone Linux clusters, including certificate setup and supported authentication mechanisms.
  • Include Linux-specific examples and references (e.g., using OpenSSL for certificate creation, Linux account management, integration with Linux-based identity providers).
  • Clarify which features and recommendations apply to Linux clusters and which are Windows-only.
  • Present Azure and Linux options before or alongside Windows-specific options to avoid 'windows_first' ordering.
  • Reference cross-platform certificate authorities and tools, not just Windows Server certificate service.
GitHub Create Pull Request
Service Fabric Upgrade Linux OS for Azure Service Fabric ...es/service-fabric/service-fabric-cluster-upgrade-os.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 provides a Linux-focused migration guide, but the step-by-step instructions and code samples are heavily reliant on Az PowerShell cmdlets and Windows-centric tooling. PowerShell examples are given for nearly every major operation, with only one section (disabling nodes) using Linux-native tools (ssh, bash, jq, sfctl). There is no parity for Linux CLI (Azure CLI) or bash scripting for the majority of steps, and PowerShell is presented as the default method for both production and non-production clusters.
Recommendations
  • Provide equivalent Azure CLI (az) commands for all PowerShell cmdlets, especially for updating vmImage, adding/removing node types, and querying cluster state.
  • Include bash script examples for common operations, such as node type management and cluster upgrades.
  • Clearly indicate which steps can be performed from Linux/macOS environments and provide guidance for cross-platform users.
  • Reorder examples so that Linux-native tools (Azure CLI, bash, sfctl) are shown before or alongside PowerShell examples.
  • Mention installation and usage of Azure CLI for Linux users, and link to relevant documentation.
GitHub Create Pull Request
Service Fabric Upgrading Azure Service Fabric clusters ...icles/service-fabric/service-fabric-cluster-upgrade.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 demonstrates a moderate Windows bias. While most upgrade concepts are platform-neutral, operational examples and references to tooling (such as PowerShell) are Windows-centric. The section on OS patching links only to Windows-specific guidance, with no mention of Linux patching or Linux Service Fabric clusters. Where command-line tooling is referenced, PowerShell is listed before Azure CLI, and no Linux/macOS shell examples are provided.
Recommendations
  • Add explicit examples and instructions for Linux-based Service Fabric clusters, especially for OS patching and upgrades.
  • When referencing command-line tools, present Azure CLI and PowerShell equally, and provide bash/zsh examples where appropriate.
  • Include links to Linux-specific documentation for cluster management and patching, or clarify platform applicability.
  • Avoid using 'Windows operating system' as the default context; specify when instructions are Windows-only and provide Linux alternatives.
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-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias by referencing Windows-specific upgrade guides and tools, such as the Patch Orchestration Application for Windows, and by linking only to Windows Server-specific upgrade instructions. There is no mention of Linux-specific upgrade procedures, tools, or examples, which may leave Linux users without clear guidance.
Recommendations
  • Provide equivalent upgrade guides and documentation for Linux-based Service Fabric clusters, including links to Linux-specific instructions.
  • Mention Linux patch orchestration options or clarify whether POA is available for Linux clusters.
  • Ensure examples and configuration instructions are platform-neutral or include both Windows and Linux variants.
  • Explicitly state any platform limitations or differences in upgrade and patching procedures.
GitHub Create Pull Request
Service Fabric Manage Service Fabric cluster upgrades ...fabric/service-fabric-cluster-upgrade-version-azure.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 exhibits a moderate Windows bias. The only command-line example for validating upgrade paths is provided using PowerShell, with no equivalent Linux/macOS CLI (such as Azure CLI or Bash) example. In the REST API output, Windows environments are listed first, and PowerShell is the only scripting language shown for operational tasks. There is no mention of Linux/macOS-specific tools or workflows, nor are cross-platform alternatives presented.
Recommendations
  • Add Azure CLI or Bash examples alongside PowerShell for upgrade path validation and other cluster management tasks.
  • Explicitly state that the procedures can be performed on Linux/macOS and provide relevant commands.
  • Ensure REST API output examples alternate or equally represent Windows and Linux environments.
  • Include notes or sections addressing cross-platform usage and any OS-specific caveats.
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-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias. All command-line examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) with no mention of Azure CLI equivalents, which are cross-platform. The application packaging workflow is described using Visual Studio (Windows-only) and Windows file paths, with no alternative instructions for Linux/macOS users (e.g., using dotnet CLI or other tools). The screenshots and step-by-step instructions are tailored to Windows environments, and there is no guidance for Linux/macOS users on how to perform these tasks.
Recommendations
  • Provide Azure CLI examples alongside PowerShell cmdlets for deployment and resource management.
  • Include instructions for packaging Service Fabric applications using cross-platform tools (e.g., dotnet CLI, manual zipping) instead of relying solely on Visual Studio.
  • Show file paths and commands in both Windows and Linux/macOS formats.
  • Add screenshots or descriptions for Linux/macOS workflows where relevant.
  • Explicitly state which steps are Windows-specific and offer Linux/macOS alternatives.
GitHub Create Pull Request
Service Fabric Common questions about Microsoft Azure Service Fabric ...cles/service-fabric/service-fabric-common-questions.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 page demonstrates a moderate Windows bias. Several examples and recommendations reference Windows-specific tools (e.g., PowerShell, Windows Server upgrade), and antivirus exclusions list only Windows-style paths and processes. Linux equivalents, where relevant, are missing or not mentioned. Windows-centric terminology and examples are presented first or exclusively in key sections, such as authentication to Key Vault and OS upgrade guidance.
Recommendations
  • Provide Linux-specific instructions and examples alongside Windows ones, especially for OS upgrades and Service Fabric node management.
  • Include Linux paths and process names in the antivirus exclusion section, or clarify if exclusions are only relevant for Windows clusters.
  • Offer Bash or CLI examples for Key Vault authentication, not just PowerShell.
  • Explicitly mention Linux support and parity in sections discussing cluster setup, management, and application deployment.
  • Where Windows terminology is used (e.g., 'Program Files'), add Linux equivalents or clarify platform-specific differences.
GitHub Create Pull Request
Service Fabric Connect securely to an Azure Service Fabric cluster ...ice-fabric/service-fabric-connect-to-secure-cluster.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 provides extensive PowerShell and Windows-centric instructions and examples for connecting to Azure Service Fabric clusters, including certificate management and cluster connection. Linux/macOS equivalents are missing or only briefly mentioned, with no CLI or scripting examples for certificate installation or management on non-Windows platforms. Windows tools and patterns (PowerShell, certificate stores) are referenced first and in detail, while Linux and macOS users are left with minimal guidance.
Recommendations
  • Add explicit Linux and macOS instructions for installing client certificates (e.g., using openssl, certutil, or browser-specific steps).
  • Provide CLI-based examples for certificate management on Linux/macOS, such as using openssl or keytool.
  • Include cross-platform scripting examples for connecting to clusters, not just PowerShell.
  • Reorder sections or provide parity so that Linux/macOS instructions are presented alongside Windows, not as an afterthought.
  • Clarify browser certificate import steps for Linux, with references to common browsers (Chrome, Firefox) and their certificate management interfaces.
GitHub Create Pull Request
Service Fabric Azure Files volume driver for Service Fabric ...ic/service-fabric-containers-volume-logging-drivers.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 demonstrates a moderate Windows bias. Windows-specific prerequisites and limitations are described in detail, with Windows versions listed first and more prominently. PowerShell is the primary scripting tool shown for both Windows and Linux deployments, even though Linux users typically use Bash or other shell environments. Examples and configuration snippets often use Windows paths (e.g., c:\tmp, c:\VolumeTest\Data) and Windows-centric patterns, with Linux equivalents either shown after or omitted. Some sections, such as application manifest examples, only show Windows-style paths and do not provide Linux-specific guidance or examples.
Recommendations
  • Provide Linux-first or side-by-side examples for all commands, especially for deployment and configuration steps.
  • Include Linux-specific prerequisites and limitations with equal detail as Windows.
  • Use Linux-style paths (e.g., /tmp, /mnt/volume) in manifest and configuration examples, or show both Windows and Linux variants.
  • Offer Bash or shell script alternatives to PowerShell scripts for Linux users.
  • Clarify any differences in application manifest structure or deployment steps for Linux clusters.
  • Ensure that documentation sections do not assume Windows as the default environment.
GitHub Create Pull Request
Service Fabric Induce Chaos in Service Fabric clusters ...cles/service-fabric/service-fabric-controlled-chaos.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 detailed examples for running Chaos in Service Fabric clusters using C# and PowerShell, both of which are Windows-centric tools. PowerShell is featured heavily, with no equivalent Bash, Linux CLI, or cross-platform shell examples. Windows-specific tools and patterns (e.g., Connect-ServiceFabricCluster, Start-ServiceFabricChaos) are mentioned exclusively, and there is no guidance for Linux/macOS users on how to perform these operations. The REST API is mentioned in passing but not demonstrated, and Windows tooling is presented first and in greater detail.
Recommendations
  • Add explicit examples using the REST API, including sample curl commands and JSON payloads, to demonstrate cross-platform usage.
  • Provide equivalent instructions for Linux/macOS environments, such as using Bash scripts or Service Fabric CLI (sfctl) where available.
  • Clarify which tools are cross-platform and which are Windows-only, and direct users to platform-appropriate tooling.
  • Reorder or balance examples so that Windows and Linux/macOS approaches are presented with equal prominence.
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-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 terminology, tools, and examples (e.g., PowerShell, Windows services, Visual Studio) are mentioned first or exclusively in several sections. Linux support is acknowledged, but Linux-specific instructions, examples, and parity are often missing or relegated to secondary mentions. Some features (e.g., standalone clusters) are noted as Windows-only, and Windows-centric tools (PowerShell, Visual Studio) are referenced before or instead of Linux alternatives.
Recommendations
  • Provide Linux-specific examples and instructions alongside Windows ones, especially for cluster creation, management, and upgrades.
  • Reference Linux-native tools (e.g., Bash, systemd, Linux CLI) where appropriate, and ensure CLI examples are cross-platform.
  • Clarify feature parity and limitations for Linux users upfront, and link to Linux-specific documentation where available.
  • Avoid using Windows terminology (e.g., 'Windows service') without explaining or providing Linux equivalents.
  • Include Linux-first or at least equal examples in 'Next steps' and quickstart sections.
  • Highlight cross-platform development tools (e.g., VS Code, JetBrains Rider) alongside Visual Studio.
GitHub Create Pull Request
Service Fabric Azure Service Fabric deployment with FabricClient ...service-fabric-deploy-remove-applications-fabricclient.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 page demonstrates a notable Windows bias. It references Visual Studio and PowerShell as the default tools for packaging and deploying Service Fabric applications, provides file paths and examples in Windows format, and omits Linux/macOS equivalents for key steps such as local development, package verification, and troubleshooting. No cross-platform CLI (e.g., sfctl) or Linux/macOS file path examples are given, and all code and troubleshooting examples assume a Windows environment.
Recommendations
  • Add explicit instructions and examples for Linux/macOS users, including file paths and environment setup.
  • Include sfctl (Service Fabric CLI) usage for deployment, package upload, and troubleshooting, as it is cross-platform.
  • Document how to verify and compress packages on Linux/macOS (e.g., using tar/gzip and sfctl commands).
  • Provide troubleshooting steps using CLI tools available on Linux/macOS, not just PowerShell.
  • Clarify which steps are Windows-specific and offer alternatives for other platforms.
  • Mention and link to Service Fabric SDK installation instructions for Linux/macOS.
GitHub Create Pull Request
Service Fabric Deploy an existing executable to Azure Service Fabric ...s/service-fabric/service-fabric-deploy-existing-app.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 page demonstrates a Windows bias by presenting Windows/Visual Studio tooling and workflows first and in greater detail, providing PowerShell-only deployment scripts, and referencing Windows-centric tools (Visual Studio, batch files, .cmd scripts) without equivalent Linux examples or alternatives. Linux instructions are brief and lack deployment scripting or detailed guidance, making the process less clear for Linux/macOS users.
Recommendations
  • Provide Linux/macOS deployment instructions and scripts, e.g., using Azure CLI or Bash equivalents for PowerShell commands.
  • Include Linux-first or parallel examples for packaging and deploying guest executables, matching the detail given to Visual Studio workflows.
  • Offer guidance for using Linux-native tools (e.g., Yeoman, Bash scripts) for setup and initialization, and clarify how to handle .sh scripts in place of .cmd/.bat files.
  • Add screenshots or walkthroughs for Linux environments (e.g., terminal output, file locations).
  • Ensure all references to Windows-specific tooling are matched by Linux/macOS alternatives, and avoid presenting Windows-first unless justified by user base.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Diagnose Common Scenarios ...-fabric/service-fabric-diagnostics-common-scenarios.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 generally focuses on Azure-native tools and portal workflows, which are cross-platform. However, there is a notable Windows bias in the 'Monitor performance counters' section, where Windows Performance Counters are described first and in detail, with Linux mentioned only parenthetically and no Linux-specific counter examples provided. The counter examples and screenshots are all Windows-centric. There is also a lack of explicit Linux command-line or tooling examples throughout, and Windows patterns (such as .NET CLR counters) are used exclusively in examples.
Recommendations
  • Add explicit Linux performance counter examples and screenshots, showing how to configure and query Linux counters in Log Analytics.
  • Provide parity in documentation by listing Linux steps and counter formats alongside Windows, not just as a parenthetical note.
  • Include references to Linux diagnostic tools or commands (e.g., collectd, sysstat) where appropriate.
  • Ensure that examples and screenshots alternate between Windows and Linux environments, or show both.
  • Clarify any differences in agent setup or data collection for Linux clusters.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Event Aggregation with EventFlow ...service-fabric-diagnostics-event-aggregation-eventflow.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a Windows bias by exclusively referencing Windows development tools (Visual Studio, Solution Explorer), providing setup instructions only for Visual Studio, and omitting any guidance for Linux/macOS users (e.g., command-line NuGet usage, .NET CLI, or cross-platform editors). There are no examples or instructions for Linux or macOS environments, and all screenshots and workflow descriptions assume a Windows/Visual Studio context.
Recommendations
  • Add instructions for installing EventFlow NuGet packages using the .NET CLI (dotnet add package) and/or NuGet command-line tools, which work on Linux/macOS.
  • Include guidance for editing project files and configuration (eventFlowConfig.json) using cross-platform editors (e.g., VS Code, vim, nano) instead of only referencing Visual Studio.
  • Clarify how to set the target framework and build actions in non-Visual Studio environments (e.g., editing .csproj files directly).
  • Provide verification steps that do not rely on Visual Studio (e.g., using dotnet run, checking logs/output on the console, or using cross-platform debugging tools).
  • Explicitly mention Linux/macOS compatibility and any platform-specific considerations for Service Fabric and EventFlow.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Events ...es/service-fabric/service-fabric-diagnostics-events.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 demonstrates a notable Windows bias: it references Windows Event logs, ETW, and the Windows Azure diagnostics agent as primary mechanisms for accessing Service Fabric events. There is no mention of Linux equivalents (e.g., journald, syslog, or Linux diagnostics agents), nor are Linux-specific event access patterns or examples provided. Windows tools and terminology are presented first and exclusively, leaving Linux/macOS users without clear guidance.
Recommendations
  • Add explicit instructions and examples for accessing Service Fabric events on Linux clusters, such as using journald, syslog, or Linux diagnostics agents.
  • Clarify whether the described mechanisms (ETW, Windows Event logs, Windows Azure diagnostics agent) apply to Linux clusters, and if not, provide Linux alternatives.
  • Include parity in documentation for configuring diagnostics and monitoring on Linux, referencing relevant tools and log locations.
  • Present cross-platform guidance, or at minimum, alternate sections for Windows and Linux users.
GitHub Create Pull Request
Service Fabric Set up monitoring with Azure Monitor logs ...service-fabric/service-fabric-diagnostics-oms-setup.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 Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias: Windows clusters and tools (such as PowerShell and WAD) are referenced first and most extensively, with step-by-step instructions and code samples provided only for Windows. The Service Fabric Analytics solution is explicitly stated as Windows-only, and all example commands use PowerShell. Linux clusters are mentioned only in passing, with users redirected to a separate article for setup, and no Linux-specific instructions, CLI examples, or syslog integration details are present.
Recommendations
  • Provide equivalent step-by-step instructions and code samples for Linux clusters, using Azure CLI and/or Bash scripts.
  • Include direct links and summaries for Linux setup within this page, rather than only redirecting to another article.
  • Clarify which features are Windows-only and offer alternative solutions for Linux users where possible.
  • Present Windows and Linux instructions in parallel sections, or clearly label which steps apply to each platform.
  • Add examples for configuring diagnostics and log integration for Linux clusters, including syslog and OMS agent setup.
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-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation displays several forms of Windows bias. Windows support is described as more complete and is mentioned first in the OS support section. PowerShell is the only CLI tool shown for service creation and DNS name assignment, with no Linux CLI (e.g., Bash, Azure CLI) equivalents. Visual Studio is referenced for editing manifests, which is a Windows-centric tool. There are no Linux-specific instructions or examples for enabling or managing DNS service, and enabling DNS service via the Azure portal is only available for Windows clusters. Linux limitations are mentioned, but Linux workflows are not documented.
Recommendations
  • Provide equivalent Linux/Bash/Azure CLI examples for service creation and DNS name assignment.
  • Include instructions for editing manifests using cross-platform editors (e.g., VS Code, nano, vim) instead of or alongside Visual Studio.
  • Document Linux-specific workflows for enabling DNS service, including ARM template modifications and any required manual steps.
  • Clarify which steps are platform-agnostic and which are Windows- or Linux-specific, and present Linux options alongside Windows ones.
  • Add explicit guidance for Linux users regarding portal limitations and alternative management strategies.
GitHub Create Pull Request
Service Fabric Azure Service Fabric disaster recovery ...les/service-fabric/service-fabric-disaster-recovery.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 page for Azure Service Fabric disaster recovery demonstrates a moderate Windows bias. Windows-specific tools and APIs (e.g., PowerShell cmdlets like Repair-ServiceFabricPartition) are referenced exclusively, with no mention of Linux equivalents or cross-platform CLI usage. Standalone cluster setup is linked only for Windows Server, and troubleshooting steps (such as collecting crash dumps and restarting VMs) use terminology and tooling more familiar to Windows users. There are no Linux/macOS-specific examples or guidance, and Windows-centric patterns are presented without cross-platform alternatives.
Recommendations
  • Include equivalent Linux/macOS commands and examples (e.g., using Service Fabric CLI (sfctl) for partition repair, process management, and troubleshooting).
  • Provide links or sections for Linux/macOS cluster setup and management, not just Windows Server.
  • Clarify which instructions are cross-platform and which are Windows-only; add notes or tables for parity.
  • Reference Linux-native tools for crash dump collection, process management, and service recovery.
  • Ensure that API usage examples (such as RecoverPartitionAsync) are shown in cross-platform contexts (e.g., Python, Bash, sfctl), not just PowerShell or .NET.
GitHub Create Pull Request
← Previous Page 13 of 29 Next →