407
Total Pages
336
Linux-Friendly Pages
71
Pages with Bias
17.4%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

1305 issues found
Showing 376-400 of 1305 flagged pages
Service Fabric Application lifecycle in Service Fabric ...service-fabric/service-fabric-application-lifecycle.md
Medium Priority View Details →
Scanned: 2026-02-15 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 (e.g., Register-ServiceFabricApplicationType, Remove-ServiceFabricApplicationPackage) alongside .NET APIs and REST operations. PowerShell examples are consistently provided, but Linux equivalents (such as Azure CLI or sfctl) are not explicitly shown or described. The page mentions the Service Fabric CLI (sfctl) in an include, but does not provide concrete examples or parity for Linux/macOS users. Windows tools and patterns are often mentioned first or exclusively, creating friction for non-Windows users.
Recommendations
  • Add explicit examples using sfctl (Service Fabric CLI) and Azure CLI for each lifecycle operation, alongside PowerShell and .NET API references.
  • Where PowerShell cmdlets are mentioned, provide the equivalent sfctl or Azure CLI command and link to relevant documentation.
  • Clarify which tools are cross-platform and which are Windows-only, to help Linux/macOS users navigate the options.
  • Consider reordering examples so that cross-platform tools (sfctl, REST API, Azure CLI) are presented before or alongside Windows-specific tools.
  • Add a section summarizing tool parity and supported platforms for Service Fabric management.
Service Fabric Advanced Application Upgrade Topics ...-fabric/service-fabric-application-upgrade-advanced.md
Medium Priority View Details →
Scanned: 2026-02-15 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page for advanced Service Fabric application upgrade topics heavily relies on PowerShell cmdlets for examples and guidance, with no mention of Linux/macOS equivalents or cross-platform CLI tools. All command-line examples use PowerShell syntax, and references to tooling (such as Visual Studio) are Windows-centric. There is no discussion of Linux-compatible approaches (e.g., Azure CLI, REST API, or sfctl), nor are Linux/macOS users provided with alternative instructions or examples.
Recommendations
  • Add examples using sfctl (Service Fabric CLI), which is cross-platform and supported on Linux/macOS.
  • Mention and provide examples for Azure CLI or REST API where applicable.
  • Clarify which PowerShell cmdlets are available cross-platform (PowerShell Core) and which are Windows-only.
  • Include notes or links for Linux/macOS users on how to perform equivalent operations.
  • Reorder sections or examples so that Windows and Linux approaches are presented equally, or explicitly state if a feature is Windows-only.
Service Fabric Service Fabric application upgrade ...s/service-fabric/service-fabric-application-upgrade.md
Medium Priority View Details →
Scanned: 2026-02-15 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 demonstrates a notable Windows bias. PowerShell is used exclusively for command-line examples, and only PowerShell cmdlets (e.g., Get-ServiceFabricApplication, Start-ServiceFabricApplicationUpgrade) are shown for performing upgrades. There are no equivalent examples or guidance for Linux/macOS users (e.g., using sfctl or REST APIs). Windows-specific tools and APIs (http.sys, PowerShell) are referenced without mention of cross-platform alternatives. This creates friction for Linux users, who must translate the instructions themselves.
Recommendations
  • Add equivalent examples using sfctl (the Service Fabric CLI, which is cross-platform) for all PowerShell command examples.
  • Where PowerShell cmdlets are referenced, also mention or link to REST API documentation or sfctl equivalents.
  • Clarify which features or commands are Windows-only, and provide Linux/macOS alternatives where possible.
  • In sections referencing Windows-specific components (e.g., http.sys), note the Linux/macOS behavior or limitations.
  • Reorder examples or provide parallel examples so that Linux/macOS users are not always second-class.
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-15 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides several manual scaling instructions using PowerShell cmdlets (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState) without mentioning Linux equivalents or cross-platform alternatives. PowerShell is referenced as the primary tool for cluster operations, and Windows-centric tooling is presented first. While Service Fabric supports Linux clusters, the guidance for scaling operations is heavily oriented toward Windows/PowerShell users, creating friction for Linux users who may need to find their own methods or tools.
Recommendations
  • Add equivalent Linux instructions for manual scaling, such as using Service Fabric CLI (sfctl) or REST API calls.
  • Explicitly mention cross-platform tools and provide examples for both Windows (PowerShell) and Linux (sfctl/REST).
  • Clarify which steps are universal and which are platform-specific, and link to platform-specific guides where appropriate.
  • Consider providing bash shell examples alongside PowerShell examples for parity.
Service Fabric Change Azure Service Fabric cluster settings ...rvice-fabric/service-fabric-cluster-fabric-settings.md
Medium Priority View Details →
Scanned: 2026-02-15 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation provides a comprehensive reference for Service Fabric cluster settings, covering both Azure-hosted and standalone clusters. However, there is evidence of Windows bias: Windows terminology and tools (such as certificate store names like 'MY', 'LocalMachine', and references to NTLM authentication) are used throughout, often without explicit Linux equivalents or clarifications. Windows-specific features (e.g., Windows Update, NTLM, log file paths) are mentioned, sometimes without clear Linux alternatives. In some cases, Windows defaults are listed first or exclusively, even for settings that are cross-platform.
Recommendations
  • Where certificate store names or authentication mechanisms are mentioned (e.g., 'MY', 'LocalMachine', NTLM), clarify Linux equivalents or note differences in Linux deployments.
  • For parameters with Windows-only defaults (e.g., ContainerNetworkSetup, log file settings), explicitly state Linux defaults and behaviors.
  • Add notes or examples for Linux-specific configuration where relevant (e.g., file paths, certificate storage, authentication).
  • Review guidance text for implicit Windows assumptions and add Linux/macOS parity notes.
  • Consider adding a summary table or section highlighting which settings are platform-specific and which are cross-platform.
Service Fabric Service Fabric Cluster Resource Manager - Application Groups ...ice-fabric-cluster-resource-manager-application-groups.md
Medium Priority View Details →
Scanned: 2026-02-15 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page provides only PowerShell and C# examples for managing Service Fabric Application Groups, with no mention of Linux-compatible CLI tools or examples. PowerShell is a Windows-centric tool, and its exclusive use in the examples creates friction for Linux/macOS users who may use Azure CLI or REST APIs instead. There is no guidance or parity for Linux users, nor are alternative tools or commands referenced.
Recommendations
  • Add Azure CLI examples for all operations shown (creation, update, querying, removal) if supported.
  • Mention REST API endpoints for managing Application Groups, with example requests.
  • Clarify which management operations are possible from Linux/macOS and provide links to relevant cross-platform tools.
  • If PowerShell is required, explicitly state its availability on Linux/macOS and provide installation instructions.
  • Consider including Bash or shell script examples where applicable.
Service Fabric Service Fabric Cluster Resource Manager - Placement Policies ...ce-manager-advanced-placement-rules-placement-policies.md
Medium Priority View Details →
Scanned: 2026-02-15 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation consistently provides PowerShell examples for configuring placement policies, but does not include equivalent Linux/macOS CLI (e.g., Azure CLI, Bash, or REST API) examples. PowerShell is primarily used on Windows, and its exclusive presence creates friction for Linux/macOS users. Additionally, PowerShell examples are presented immediately after C# code samples, with no mention of cross-platform alternatives.
Recommendations
  • Add Azure CLI examples for each placement policy configuration, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include REST API or ARM template snippets where applicable, to provide platform-neutral configuration options.
  • Explicitly mention that PowerShell examples are Windows-centric, and provide guidance or links for Linux/macOS users.
  • Consider reordering examples so that cross-platform options (Azure CLI, REST) are shown before or alongside PowerShell.
Scanned: 2026-02-15 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides example code for configuring auto scaling policies in Service Fabric using application manifests, C# APIs, and PowerShell. All CLI examples are PowerShell-based, with no equivalent Bash or Linux CLI examples. PowerShell is a Windows-centric tool, and its exclusive use creates friction for Linux/macOS users. The documentation does not mention or demonstrate Linux-native tools or workflows for configuring auto scaling, nor does it clarify how Linux users should perform these tasks. Additionally, PowerShell examples are presented alongside C# and manifest examples, but no Linux-first or cross-platform CLI guidance is given.
Recommendations
  • Add Bash or Azure CLI examples for configuring scaling policies, especially for Linux clusters.
  • Clarify which steps and tools are supported on Linux and macOS, and provide guidance for Linux users.
  • Mention any limitations or differences in auto scaling configuration between Windows and Linux clusters.
  • If PowerShell is required, note its availability on Linux and provide installation instructions, or recommend cross-platform alternatives.
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-15 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation provides configuration examples for Service Fabric clusters using both ClusterManifest.xml (with <WindowsServer> element) and ClusterConfig.json, but the XML example is explicitly Windows Server-focused and appears first. PowerShell examples are included for service creation and updates, but there are no Linux shell (bash/CLI) equivalents. The documentation does not mention Linux-specific node configuration or tools, nor does it clarify Linux support for standalone clusters. However, JSON-based configuration is shown, which is cross-platform, and the overall concepts are platform-agnostic.
Recommendations
  • Add explicit Linux configuration examples (e.g., using ClusterManifest.xml for Linux, or clarify if only JSON is supported for Linux standalone clusters).
  • Include Linux/macOS shell (bash/CLI) equivalents for PowerShell commands, or reference Azure CLI where applicable.
  • Clarify platform support for standalone Service Fabric clusters (Windows vs. Linux) and note any limitations.
  • If ClusterManifest.xml is only for Windows, state this clearly and provide Linux alternatives.
  • Ensure examples and tools are presented in a platform-neutral order, or group them by platform.
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-15 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 primarily in C# and PowerShell. PowerShell is a Windows-centric tool, and no equivalent Linux/macOS CLI examples (such as Azure CLI or Bash scripts) are provided. The PowerShell examples are presented alongside C# code, but there is no mention of cross-platform alternatives or guidance for Linux/macOS users. This creates friction for users running Service Fabric clusters on Linux or developing from non-Windows environments.
Recommendations
  • Add Azure CLI examples for service creation and metric management, as Azure CLI is cross-platform.
  • Include Bash script examples or reference REST API usage for metric operations, which are accessible from any OS.
  • Explicitly mention whether PowerShell Core (cross-platform) is supported, and provide guidance for Linux/macOS users if so.
  • Clarify any limitations or differences for Service Fabric metric management on Linux clusters.
  • Reorder examples so that cross-platform tools (Azure CLI, REST API) are shown before or alongside PowerShell.
Scanned: 2026-02-15 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 and C# examples for configuring Service Fabric movement cost, but does not include equivalent Linux/bash/CLI examples. PowerShell is a Windows-centric tool, and its usage is presented first, which may create friction for Linux/macOS users. There is no mention of Service Fabric CLI or REST API alternatives, nor guidance for Linux-based deployments.
Recommendations
  • Add Azure CLI or Service Fabric CLI examples for creating and updating services with move cost, where possible.
  • Include bash or shell script snippets for Linux users, or reference REST API documentation for cross-platform usage.
  • Clarify whether PowerShell examples are usable on Linux (e.g., via PowerShell Core), or provide explicit guidance for Linux/macOS environments.
  • Present examples in a platform-neutral order, or group them by platform to avoid implicit prioritization.
Scanned: 2026-02-15 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides extensive 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), Bash, or cross-platform tools. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer native tools.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • Explicitly mention that PowerShell examples are for Windows and provide guidance for Linux/macOS users.
  • Include Bash or shell script examples where applicable.
  • Clarify any platform-specific requirements for the APIs and tools used.
Service Fabric Secure an Azure Service Fabric cluster ...cles/service-fabric/service-fabric-cluster-security.md
Medium Priority View Details →
Scanned: 2026-02-15 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page for securing an Azure Service Fabric cluster demonstrates moderate Windows bias. Windows Server clusters and Windows authentication methods are mentioned prominently and often before Linux equivalents. Several sections, especially those about node-to-node and client-to-node security, provide links and guidance specifically for Windows standalone clusters, with no equivalent guidance for Linux standalone clusters. Windows tools (such as Windows Server certificate service and MakeCert.exe) are referenced for certificate creation, while Linux certificate creation tools are not mentioned. The concept of Linux clusters is acknowledged, but practical instructions and examples for Linux users are missing.
Recommendations
  • Add explicit instructions, examples, and links for securing standalone Linux Service Fabric clusters, including certificate setup and authentication methods.
  • Mention Linux-compatible certificate creation tools (e.g., OpenSSL) alongside Windows tools like MakeCert.exe.
  • Provide parity in guidance for Linux clusters wherever Windows clusters are discussed, especially in node-to-node and client-to-node security sections.
  • Clarify which features are cross-platform and which are Windows-only, to reduce ambiguity for Linux users.
Service Fabric Azure Service Fabric application resource model ...ervice-fabric/service-fabric-concept-resource-model.md
Medium Priority View Details →
Scanned: 2026-02-15 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 demonstrates notable Windows bias. All deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) with no mention of Azure CLI or other cross-platform tools. Application packaging instructions reference Visual Studio, a Windows-centric IDE, and do not provide alternatives for Linux/macOS users. The workflow assumes Windows tools and patterns throughout, with no Linux/macOS parity or guidance.
Recommendations
  • Add Azure CLI examples for deployment and resource management alongside PowerShell examples.
  • Provide instructions for packaging Service Fabric applications using cross-platform tools (e.g., dotnet CLI, sfctl, or manual zip commands).
  • Mention and link to Linux/macOS-compatible development environments (e.g., VS Code) for application packaging.
  • Explicitly state which steps are Windows-only and offer Linux/macOS alternatives where possible.
  • Show both PowerShell and Azure CLI commands in parallel for resource operations.
Service Fabric Azure Service Fabric Events ...es/service-fabric/service-fabric-diagnostics-events.md
Medium Priority View Details →
Scanned: 2026-02-15 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page on Azure Service Fabric Events primarily references Windows-specific logging mechanisms (ETW/Windows Event logs) and the Windows Azure diagnostics agent. There are no explicit examples or instructions for accessing Service Fabric events on Linux clusters, nor are Linux-native tools or patterns mentioned. Windows tools are discussed first and exclusively, creating friction for Linux users.
Recommendations
  • Add explicit guidance for accessing Service Fabric events on Linux clusters, including supported logging mechanisms and monitoring tools.
  • Mention Linux-native equivalents (e.g., journald, syslog, or Azure Monitor integration for Linux nodes) alongside Windows tools.
  • Clarify which methods are cross-platform and which are Windows-only, to help users understand applicability.
  • Provide example workflows or commands for Linux environments where possible.
Scanned: 2026-02-15 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 tag 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 non-Windows users. The C# API examples are cross-platform, but operational/administrative tasks are only shown via PowerShell.
Recommendations
  • Add Azure CLI or Bash script examples for managing node tags and service tag requirements.
  • Include REST API usage examples for tag operations, which are platform-neutral.
  • Clearly indicate if PowerShell is required due to Service Fabric limitations, or provide guidance for Linux/macOS users.
  • Consider referencing any available cross-platform tools for Service Fabric administration.
Service Fabric Azure Service Fabric standalone cluster scaling ...ce-fabric/service-fabric-cluster-scaling-standalone.md
Medium Priority View Details →
Scanned: 2026-02-15 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 exhibits Windows bias by referencing PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) and linking to guides that are Windows Server-specific. There are no examples or instructions for Linux-based standalone clusters, nor are Linux tools or commands mentioned.
Recommendations
  • Add equivalent Linux instructions and examples for scaling standalone clusters, including relevant CLI commands (e.g., sfctl or REST APIs).
  • Clarify whether standalone clusters can be run on Linux, and if so, provide guidance for Linux environments.
  • Include links to Linux-specific documentation or note any limitations if Linux standalone clusters are not supported.
  • When referencing PowerShell or Windows tools, also mention Linux alternatives or explicitly state if the feature is Windows-only.
Service Fabric Upgrade an Azure Service Fabric standalone cluster ...ce-fabric/service-fabric-cluster-upgrade-standalone.md
Medium Priority View Details →
Scanned: 2026-02-15 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page primarily references Windows-specific upgrade paths and tools, such as linking to 'service-fabric-cluster-upgrade-windows-server.md' and 'service-fabric-cluster-config-upgrade-windows-server.md'. The Patch Orchestration Application is described as 'for Windows', with no mention of Linux equivalents or guidance. There are no explicit Linux examples or references, and Windows terminology/tools are mentioned first or exclusively.
Recommendations
  • Add explicit guidance or links for upgrading Service Fabric standalone clusters running on Linux, if supported.
  • Provide Linux-specific configuration and upgrade documentation, or clarify if Linux standalone clusters are not supported.
  • Mention Linux patch orchestration options or clarify their absence.
  • Ensure that examples and references are balanced between Windows and Linux, or clearly state platform limitations.
Service Fabric Scalability of Service Fabric services .../service-fabric/service-fabric-concepts-scalability.md
Medium Priority View Details →
Scanned: 2026-02-15 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, which is a Windows-centric tool. There are no equivalent Linux CLI or bash examples, nor is there mention of Linux-native tools or commands for managing Service Fabric clusters. Windows/PowerShell commands are presented first and exclusively, creating friction for Linux users who may need to translate these steps to their environment.
Recommendations
  • Add equivalent Linux CLI/bash examples for Service Fabric administrative actions (e.g., scaling services, creating/deleting services/applications).
  • Reference Linux-native tools or commands (such as sfctl or REST API usage) alongside PowerShell examples.
  • Explicitly mention cross-platform support and differences, including links to Linux-specific documentation where relevant.
  • Present examples for both Windows and Linux platforms, ideally side-by-side, to improve parity and accessibility.
Service Fabric Package an existing executable to Azure Service Fabric ...abric/service-fabric-guest-executables-introduction.md
Medium Priority View Details →
Scanned: 2026-02-15 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation references the Service Fabric SDK schema path using a Windows directory (C:\Program Files\Microsoft SDKs\Service Fabric\schemas\...), and does not mention Linux/macOS equivalents. The overall structure and examples assume a Windows environment, and Visual Studio is mentioned as a primary tool, which is Windows-centric for Service Fabric development. However, the documentation does not explicitly exclude Linux, and Service Fabric does have Linux support.
Recommendations
  • Add notes or examples for Linux/macOS users, such as where the Service Fabric SDK schema files are located on those platforms.
  • Clarify whether the packaging and deployment steps can be performed on Linux/macOS, and if so, provide equivalent instructions or references.
  • When mentioning Visual Studio, also mention cross-platform alternatives (e.g., Visual Studio Code, CLI tools) if available.
  • Ensure that file paths and tooling instructions are not Windows-only, or provide both Windows and Linux/macOS variants.
Service Fabric Networking patterns for Azure Service Fabric ...s/service-fabric/service-fabric-patterns-networking.md
Medium Priority View Details →
Scanned: 2026-02-15 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 demonstrates a notable Windows bias. All deployment and resource management examples use PowerShell cmdlets (e.g., New-AzResourceGroup, Get-AzPublicIpAddress), with no mention of Azure CLI, Bash, or cross-platform alternatives. Even basic network testing is shown with Windows command prompt syntax (e.g., ping from C:\>). There are no Linux/macOS-specific instructions or examples, and PowerShell is presented as the default/only method for template deployment.
Recommendations
  • Provide equivalent Azure CLI (az) commands alongside PowerShell for all resource group, deployment, and resource management steps.
  • Include Bash shell examples for network testing (e.g., using ping from a Linux/macOS terminal).
  • Explicitly state that both PowerShell and Azure CLI can be used, and link to Azure CLI documentation.
  • Where possible, use platform-agnostic language and tools in code snippets and instructions.
  • Add a note clarifying that the instructions are valid for all platforms, and highlight any platform-specific differences.
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-02-15 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page for 'Replica soft delete for enhanced data protection in Service Fabric' consistently references PowerShell APIs (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica) and provides examples and links exclusively for PowerShell usage. There is no mention of Linux or macOS command-line equivalents, nor are cross-platform SDK usage patterns (such as .NET Core or REST APIs) highlighted. The documentation assumes familiarity with Windows tooling and does not clarify whether these operations can be performed on Linux clusters or with non-Windows tools.
Recommendations
  • Add explicit examples for Linux environments, such as using Service Fabric CLI (sfctl) or REST APIs where applicable.
  • Clarify whether the PowerShell APIs are available or supported on Linux/macOS, and provide alternative instructions if not.
  • Mention and link to cross-platform SDKs (e.g., .NET Core, Java) for performing replica management operations.
  • Include sample commands or code snippets for Linux users, and note any limitations or differences in feature support.
Service Fabric Azure Service Fabric DNS service ...n/articles/service-fabric/service-fabric-dnsservice.md
Medium Priority View Details →
Scanned: 2026-02-15 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 artifact), and describes enabling DNS service through the Azure portal (which is not supported for Linux clusters). There are no Linux-specific CLI examples (e.g., Bash, Azure CLI), and Linux limitations are mentioned but not addressed with alternative guidance. Windows tools and patterns are presented first and more completely.
Recommendations
  • Add Azure CLI or Bash examples for Linux users to set DNS names and manage services.
  • Clarify how Linux users can enable DNS service (e.g., via ARM templates), and provide step-by-step instructions.
  • Explicitly note which features are Windows-only and provide Linux alternatives or workarounds where possible.
  • Include guidance for containerized services on Linux, since this is the supported scenario.
  • Balance example ordering so Linux approaches are not always secondary to Windows/PowerShell.
Service Fabric Health monitoring in Service Fabric ...s/service-fabric/service-fabric-health-introduction.md
Medium Priority View Details →
Scanned: 2026-02-15 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides a detailed conceptual overview of Service Fabric health monitoring, which is cross-platform in nature. However, the only concrete example given for reporting and evaluating application health uses PowerShell cmdlets, with no equivalent Linux/macOS CLI or REST API example. The documentation mentions REST as a reporting option but does not demonstrate it, and PowerShell is the only example shown. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other tools.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • Provide REST API example for health reporting and querying, as REST is mentioned as an option.
  • Clarify that PowerShell is Windows-specific and suggest alternatives for Linux/macOS users.
  • Consider showing CLI or REST examples before or alongside PowerShell examples to improve parity.
Service Fabric Azure Service Fabric hosting activation and deactivation life cycle ...les/service-fabric/service-fabric-hosting-lifecycle.md
Medium Priority View Details →
Scanned: 2026-02-15 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page is largely platform-neutral in its conceptual explanations, but the 'Next steps' section and one example link reference PowerShell, which is primarily a Windows tool. There are no explicit Linux/macOS command examples or references to Linux-native tools for deploying or managing Service Fabric applications. The link for downloading a ServicePackage in advance points to a PowerShell cmdlet, and the 'Deploy and remove applications' link is also PowerShell-focused, suggesting Windows as the primary platform for operational tasks.
Recommendations
  • Add equivalent Linux/macOS instructions or links for deploying and managing Service Fabric applications, such as using Azure CLI, REST API, or Service Fabric CLI (sfctl).
  • Where PowerShell is referenced, clarify if cross-platform PowerShell Core is supported, or provide alternative commands for Linux/macOS users.
  • Include examples or links for Linux-native tools and workflows, ensuring parity in operational guidance.
  • Explicitly state platform requirements or limitations where relevant, so users know if a task is Windows-only.