407
Total Pages
335
Linux-Friendly Pages
72
Pages with Bias
17.7%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

2475 issues found
Showing 526-550 of 2475 flagged pages
Service Fabric Azure Service Fabric hosting model ...rticles/service-fabric/service-fabric-hosting-model.md
Medium Priority View Details →
Scanned: 2026-03-03 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 and references for managing Service Fabric services, with no equivalent Linux CLI or cross-platform examples. Windows tools (PowerShell) are mentioned first and exclusively for command-line operations, creating friction for Linux/macOS users who must seek alternative methods. REST API and .NET client examples are included, but no Linux-native CLI or bash examples are provided.
Recommendations
  • Add Azure CLI or Bash examples for creating and managing Service Fabric services, especially for operations shown in PowerShell.
  • Explicitly mention cross-platform tools and workflows where possible, such as REST API usage from curl or other Linux-friendly tools.
  • Clarify which operations can be performed from Linux/macOS and provide links or references to relevant documentation.
  • Consider reordering examples so that cross-platform methods (REST, Azure CLI) are shown before or alongside PowerShell.
Service Fabric Upgrade an Azure Service Fabric standalone cluster ...ce-fabric/service-fabric-cluster-upgrade-standalone.md
Medium Priority View Details →
Scanned: 2026-03-03 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 upgrading an Azure Service Fabric standalone cluster demonstrates a Windows bias. It primarily references Windows Server-specific upgrade guides and tools, such as the Patch Orchestration Application for Windows, and links to documentation with 'windows-server' in the URL. There are no explicit Linux examples or references to Linux-based standalone clusters, and Linux upgrade/configuration paths are not discussed.
Recommendations
  • Clarify early in the document whether standalone clusters are supported on Linux, and if not, state this explicitly to avoid confusion.
  • If Linux-based standalone clusters are supported, provide equivalent upgrade and configuration instructions for Linux, including relevant examples and links.
  • When referencing tools or applications (e.g., Patch Orchestration Application), mention if Linux alternatives exist or clarify their absence.
  • Avoid using 'windows-server' URLs as the only upgrade/configuration references unless the feature is truly Windows-only; otherwise, provide Linux documentation links as well.
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-03-03 00:00
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 APIs (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica) and provides examples and links only for PowerShell usage. There is no mention of Linux/macOS equivalents, CLI commands, or cross-platform SDK usage, nor are Linux-specific instructions or examples provided. The focus on PowerShell and Windows tooling creates friction for Linux/macOS users, especially since Service Fabric supports Linux clusters and cross-platform management.
Recommendations
  • Add examples using Service Fabric CLI (sfctl) for Linux/macOS users, where applicable.
  • Clarify whether the PowerShell APIs are available or have equivalents on Linux/macOS, and provide guidance for those platforms.
  • Mention FabricClient usage in a cross-platform context, including sample code or instructions for .NET Core or other SDKs.
  • Explicitly state any limitations or differences for Linux clusters regarding replica soft delete.
  • Ensure API documentation links include both PowerShell and REST/CLI/SDK alternatives.
Service Fabric Azure Service Fabric DNS service ...n/articles/service-fabric/service-fabric-dnsservice.md
Medium Priority View Details →
Scanned: 2026-03-03 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 but lacks equivalent Linux CLI or scripting examples. Windows deployment and configuration options (such as portal-based enabling and ApplicationManifest.xml usage) are described in detail, while Linux-specific limitations are mentioned but not accompanied by alternative instructions or examples. The order of presentation often favors Windows-first approaches, and Linux users may need to infer their own methods or workarounds.
Recommendations
  • Add CLI or Bash examples for Linux users, such as using Azure CLI or REST API to set DNS names and enable DNS service.
  • Clarify how Linux users can configure DNS service without the portal, with step-by-step instructions.
  • Provide guidance for Linux clusters regarding ApplicationManifest.xml alternatives or container deployment methods.
  • Explicitly state which PowerShell commands are Windows-only and offer Linux equivalents where possible.
  • Include a summary table comparing Windows and Linux support/features, with links to Linux-specific documentation.
Service Fabric X.509 Certificate-based Authentication in a Service Fabric Cluster ...ticles/service-fabric/cluster-security-certificates.md
Medium Priority View Details →
Scanned: 2026-03-03 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation provides a thorough conceptual overview of X.509 certificate-based authentication in Service Fabric clusters, but exhibits Windows bias in several areas. Windows-specific terminology (e.g., certificate stores like LocalMachine\My), references to Windows APIs (Win32 CryptoAPI, CertGetCertificateChain), and troubleshooting instructions (event logs, CAPI2 logging) are given either exclusively or before Linux equivalents. Linux paths and behaviors are mentioned briefly (e.g., /var/lib/sfcerts), but Windows concepts dominate, and Linux/macOS troubleshooting guidance is largely absent.
Recommendations
  • Provide Linux/macOS equivalents for certificate store locations, certificate management, and troubleshooting steps (e.g., relevant log files, commands, and tools).
  • Include examples and instructions for certificate validation and presentation rules on Linux, such as using OpenSSL or Linux-native certificate stores.
  • Clarify which settings, APIs, and error codes are platform-specific, and offer cross-platform guidance where possible.
  • Expand troubleshooting guidance to cover Linux/macOS scenarios, including how to diagnose certificate issues using Linux tools.
Service Fabric Describing Azure Service Fabric apps and services ...ic/service-fabric-application-and-service-manifests.md
Medium Priority View Details →
Scanned: 2026-03-03 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation contains a warning that specifically references opening the Service Fabric XSD schema file in Visual Studio using a Windows file path (C:\Program Files\...), which is a Windows-only tool and path. There is no mention of equivalent tools or instructions for Linux/macOS users. Additionally, the only tooling guidance is Windows-centric and appears early in the article.
Recommendations
  • Provide instructions or suggestions for Linux/macOS users on how to validate the Service Fabric manifest XML schema, such as using cross-platform editors (e.g., VS Code with XML extensions) or command-line tools (e.g., xmllint, xmlstarlet).
  • Mention the location of the schema file on Linux clusters, if applicable, or provide a download link.
  • Avoid referencing only Windows file paths and tools; include cross-platform alternatives where possible.
  • If Visual Studio is not available on Linux/macOS, recommend VS Code or other editors that support XSD validation.
Service Fabric Deploy and upgrade with Azure Resource Manager ...vice-fabric/service-fabric-application-arm-resource.md
Medium Priority View Details →
Scanned: 2026-03-03 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides PowerShell examples for application removal and references PowerShell as a primary tool for managing Service Fabric resources. While the main deployment workflow is based on Azure Resource Manager templates (which are cross-platform), the only concrete command-line example is PowerShell, and PowerShell is mentioned before CLI alternatives. There is no explicit Linux CLI example (such as Azure CLI or Bash), and PowerShell is presented as the default scripting environment.
Recommendations
  • Add Azure CLI examples for application removal and management alongside PowerShell, especially for tasks like deleting resources.
  • Mention cross-platform tools (such as Azure CLI and Service Fabric CLI) equally or before PowerShell in relevant sections.
  • Clarify that PowerShell commands can be run on Linux/macOS via PowerShell Core, or provide Bash/CLI equivalents.
  • Where possible, link to documentation for both PowerShell and CLI workflows.
Service Fabric Initializer CodePackages in Service Fabric ...in/articles/service-fabric/initializer-codepackages.md
Medium Priority View Details →
Scanned: 2026-03-03 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 Initializer CodePackages in Service Fabric is heavily focused on Windows containers. All examples use Windows container images (nanoserver), Windows paths, and Windows command syntax. There are no examples or guidance for Linux containers or Linux-based workloads, nor is there any mention of Linux compatibility or equivalent patterns.
Recommendations
  • Add examples demonstrating Initializer CodePackages with Linux container images (e.g., Ubuntu, Alpine) and Linux command syntax.
  • Clarify whether Initializer CodePackages are supported for Linux containers and, if so, provide guidance and sample manifests.
  • Include notes or sections addressing any limitations or differences for Linux-based Service Fabric clusters.
  • Present Windows and Linux examples side-by-side, or at least mention Linux support and provide links to relevant documentation.
Service Fabric Deny assignment policy for Service Fabric managed clusters ...cles/service-fabric/managed-cluster-deny-assignment.md
Medium Priority View Details →
Scanned: 2026-03-03 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides best practice examples primarily using Azure PowerShell, with PowerShell-based tools mentioned first and in detail. While Azure CLI and ARM/Bicep are listed, PowerShell is emphasized in guidance and linked examples. There is no explicit Linux/macOS example or mention of cross-platform command usage, and the CLI is not demonstrated in the main workflow.
Recommendations
  • Add explicit Azure CLI examples for all recommended actions (e.g., deleting NodeTypes, restarting/reimaging VMSS) alongside PowerShell examples.
  • Mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Reorder tool recommendations to avoid always listing PowerShell first; alternate or group by platform neutrality.
  • Clarify that all ARM-backed tools (including CLI and Bicep) are equally recommended for Linux/macOS users.
Service Fabric Service Fabric Explorer blocking operations ...ged-cluster-service-fabric-explorer-blocking-operation.md
Medium Priority View Details →
Scanned: 2026-03-03 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page primarily references Az PowerShell cmdlets for managing Service Fabric resources, with no explicit mention of Linux/macOS equivalents or Azure CLI commands in several sections. PowerShell examples are given first and exclusively in some cases, creating friction for non-Windows users.
Recommendations
  • Add Azure CLI examples alongside PowerShell cmdlets for all management operations, as Azure CLI is cross-platform.
  • Clarify that Az PowerShell cmdlets can be used on Linux/macOS (if true), or provide guidance for Linux/macOS users.
  • Ensure that ARM template usage instructions are platform-neutral and include links to relevant documentation for all OSes.
Service Fabric Migrate an Azure Service Fabric cluster to availability zone support ...ce-fabric/migrate-service-fabric-availability-zones.md
Medium Priority View Details →
Scanned: 2026-03-03 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-based migration steps for Service Fabric clusters, especially in the 'Basic SKU' migration scenario. All operational examples (disabling nodes, removing nodes, updating DNS) are given exclusively in PowerShell, with no equivalent Bash, Azure CLI, or Linux-native instructions. Additionally, the sample templates referenced for Standard SKU scenarios are Windows-based, and Windows paths (e.g., 'D:\\SvcFab') are used in configuration examples. Linux options are mentioned in passing (e.g., a sample template for Ubuntu), but no operational guidance or CLI examples are provided for Linux/macOS users.
Recommendations
  • Add Azure CLI or Bash equivalents for all PowerShell migration steps, especially for node disablement, removal, and DNS updates.
  • Provide explicit Linux/macOS instructions for connecting to Service Fabric clusters and managing nodes.
  • Reference and link to Linux sample templates more prominently, and provide operational walkthroughs for those scenarios.
  • Avoid using Windows paths in configuration examples unless they are required; if so, clarify Linux alternatives.
  • Ensure that migration steps are platform-agnostic or provide parallel guidance for both Windows and Linux users.
Service Fabric Monitor Azure Service Fabric ...main/articles/service-fabric/monitor-service-fabric.md
Medium Priority View Details →
Scanned: 2026-03-03 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation generally covers both Windows and Linux clusters for Azure Service Fabric monitoring, but there are several instances where Windows tools (such as Event Log/Event Viewer, ETW, Diagnostics Agent) are mentioned first or exclusively, and Linux equivalents are referenced later or less prominently. Some sections (e.g., EventStore APIs) are Windows-only, but this is clearly stated. There are more detailed examples and links for Windows monitoring solutions, while Linux-specific guidance is often limited to a brief mention or a link. PowerShell is referenced for automation, but Linux CLI or Bash alternatives are not provided. The overall bias is moderate, as Linux users can complete most tasks, but may need to search for equivalent tools or instructions.
Recommendations
  • Provide Linux-specific examples and step-by-step instructions alongside Windows ones, especially for cluster monitoring and log collection.
  • Mention Linux tools (such as LTTng, Syslog) equally and provide links to relevant tutorials or documentation.
  • When referencing automation via PowerShell, also mention Bash/CLI alternatives for Linux/macOS users.
  • Ensure Linux configuration steps are as detailed as Windows ones, including troubleshooting and sample queries.
  • Clarify which features are Windows-only and provide alternative solutions or workarounds for Linux clusters where possible.
Service Fabric RunToCompletion semantics and specifications ...blob/main/articles/service-fabric/run-to-completion.md
Medium Priority View Details →
Scanned: 2026-03-03 00:00
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 RunToCompletion semantics in Service Fabric presents Windows container examples exclusively, references Windows-specific container images (nanoserver), and assumes familiarity with Windows container workflows. Querying deployment status is described only via PowerShell and C# APIs, with no mention of Linux/macOS equivalents or CLI tools. There are no examples or guidance for Linux containers or cross-platform scenarios, despite Service Fabric supporting Linux containers.
Recommendations
  • Add equivalent examples using Linux containers (e.g., Ubuntu-based images) to demonstrate RunToCompletion semantics for non-Windows environments.
  • Include instructions for querying deployment status using cross-platform tools such as Azure CLI or REST APIs, not just PowerShell.
  • Clarify whether RunToCompletion semantics are supported for Linux containers, and if so, provide code samples and considerations for Linux users.
  • Present examples for both Windows and Linux containers, or note any limitations if Linux support is partial.
  • Avoid assuming Windows container familiarity; provide links or guidance for Linux container workflows where relevant.
Service Fabric Service Fabric application upgrade ...s/service-fabric/service-fabric-application-upgrade.md
Medium Priority View Details →
Scanned: 2026-03-03 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 for Service Fabric application upgrades demonstrates a notable Windows bias. PowerShell is the only command-line interface shown for upgrade operations, and Windows-specific tools (e.g., http.sys, PowerShell cmdlets) are referenced exclusively. There are no examples or guidance for Linux-based Service Fabric clusters or cross-platform CLI usage. Additionally, Windows tools and patterns are mentioned first or exclusively throughout the article.
Recommendations
  • Add equivalent examples using the Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • Where PowerShell cmdlets are shown, provide parallel sfctl commands or REST API examples.
  • Clarify when a feature or limitation is Windows-only (e.g., http.sys certificate handling), and provide Linux-specific notes or alternatives where applicable.
  • Include a section or callouts for Linux/macOS users, especially for common upgrade tasks.
  • Update 'Next steps' to include Linux-compatible upgrade tutorials (e.g., using sfctl or REST API).
Service Fabric Azure Service Fabric networking best practices ...ice-fabric/service-fabric-best-practices-networking.md
Medium Priority View Details →
Scanned: 2026-03-03 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides both Windows and Linux guidance for Service Fabric networking, but several sections show Windows bias. PowerShell and Windows-specific tools are referenced more prominently, and Windows examples or terminology often appear before Linux equivalents. Some explanations (e.g., Client API port usage) focus on PowerShell, and ARM template samples are Windows-centric. Linux examples are present but less emphasized.
Recommendations
  • Where PowerShell is mentioned for cluster management or API access, add equivalent CLI or Bash examples for Linux users.
  • Provide ARM template samples for Linux clusters alongside Windows samples.
  • Clarify when guidance applies to both Windows and Linux, and avoid defaulting to Windows terminology (e.g., 'Client API used by PowerShell'—mention CLI or SDK usage as well).
  • Ensure reverse proxy and container networking guidance includes Linux-specific considerations and examples.
  • When referencing tools (e.g., 'netsh'), provide Linux equivalents (e.g., 'ss', 'netstat', or 'lsof').
Service Fabric Azure Service Fabric security best practices ...rvice-fabric/service-fabric-best-practices-security.md
Medium Priority View Details →
Scanned: 2026-03-03 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation generally presents Windows-specific tools and examples (such as PowerShell commands and Windows Defender) before or in greater detail than their Linux equivalents. In some sections, Windows-only features are described without Linux alternatives or with less detail for Linux users. For example, the encryption of secrets section provides detailed PowerShell commands for Windows, while Linux instructions are present but less emphasized. Windows Defender and security baselines are discussed without equivalent Linux security guidance. Some sections mention Windows tools or patterns without always providing Linux parity.
Recommendations
  • Ensure that Linux examples are presented alongside Windows examples, ideally with equal prominence and detail.
  • Where Windows-specific tools (e.g., PowerShell, Windows Defender) are discussed, provide Linux equivalents (e.g., bash/openssl for encryption, Linux security best practices, or common Linux antimalware solutions) or explicitly state if no equivalent exists.
  • Avoid presenting Windows examples or tools first by default; alternate the order or present both together.
  • Expand sections like 'Windows security baselines' and 'Windows Defender' to include Linux security hardening recommendations, such as CIS Linux benchmarks, common Linux antimalware tools, or links to relevant Azure Linux VM security documentation.
  • In summary tables or lists, clearly indicate which guidance applies to Windows, Linux, or both.
Service Fabric Service Fabric Cluster Resource Manager - Application Groups ...ice-fabric-cluster-resource-manager-application-groups.md
Medium Priority View Details →
Scanned: 2026-03-03 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 examples creates friction for Linux/macOS users, who would typically use Azure CLI or REST APIs. There is no guidance or parity for Linux users to accomplish the same tasks.
Recommendations
  • Add Azure CLI examples for all PowerShell commands shown, as Azure CLI is cross-platform and commonly used on Linux/macOS.
  • Mention REST API endpoints or provide sample requests for relevant operations.
  • Explicitly note if certain operations are only possible via PowerShell or C# and provide alternatives or workarounds for Linux/macOS users.
  • Include a section clarifying tool support and platform compatibility for Service Fabric management.
Scanned: 2026-03-03 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 on-demand backup in Azure Service Fabric exclusively uses PowerShell for all command-line examples and module instructions. There are no examples or instructions for Linux/macOS users, such as Bash, CLI, or cross-platform REST calls. The documentation assumes the use of Windows tools and patterns, creating friction for non-Windows users.
Recommendations
  • Add Azure CLI or Bash examples for triggering backups and tracking progress, especially for REST API calls.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is available or supported on PowerShell Core (pwsh) for Linux/macOS, or provide alternatives.
  • Include explicit instructions for Linux/macOS users on how to authenticate and connect to Service Fabric clusters (e.g., using certificates with curl or Azure CLI).
  • Mention cross-platform tools or REST API usage outside of PowerShell, and provide sample requests using curl or HTTPie.
  • Where possible, provide parity in examples so Linux/macOS users can follow the same workflow.
Service Fabric Understanding periodic backup configuration ...-fabric-backuprestoreservice-configure-periodic-backup.md
Medium Priority View Details →
Scanned: 2026-03-03 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page for configuring periodic backups in Azure Service Fabric is largely platform-neutral, focusing on REST API usage and JSON configuration. However, the 'File share' backup storage section exclusively references Windows-style UNC paths (\\StorageServer\BackupStore) and Integrated Windows Authentication, without mentioning or providing examples for Linux-compatible file share paths (such as SMB mounts on Linux) or authentication methods. Windows authentication is discussed first and exclusively, which may create friction for Linux users seeking parity.
Recommendations
  • Add examples and guidance for configuring file share backup storage using Linux-compatible paths and authentication methods (e.g., SMB mounts, NFS, or Azure Files with Linux authentication).
  • Clarify whether file share backup storage is supported on Linux clusters, and if so, provide relevant instructions.
  • Mention alternatives for Linux users if Integrated Windows Authentication is not available, such as username/password or Azure Files with SAS tokens.
  • Consider including a note about platform compatibility for each storage option.
Scanned: 2026-03-03 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page for restoring backup in Azure Service Fabric demonstrates notable Windows bias. All command-line examples use PowerShell, including module installation, cluster connection, and REST API calls. There are no equivalent examples for Linux/macOS users (e.g., Bash, curl, Azure CLI). The documentation references the Microsoft.ServiceFabric.Powershell.Http module, which is Windows-centric, and does not mention cross-platform alternatives or clarify if REST API calls can be made from other environments. This creates friction for Linux/macOS users who may need to restore backups but lack guidance.
Recommendations
  • Add Bash/curl examples for REST API calls, showing how to authenticate and trigger restores from Linux/macOS.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is required or if REST API calls can be made from any platform.
  • Mention Azure CLI or other cross-platform tools if available for Service Fabric backup/restore operations.
  • Explicitly state platform requirements for each tool or command, and provide alternatives where possible.
  • Add a section for Linux/macOS users outlining the restore process and any limitations.
Scanned: 2026-03-03 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Service Fabric clusters, but when it comes to cluster upgrades, only PowerShell commands are shown, which are Windows-specific. Additionally, registry key and Windows Update settings are discussed without Linux equivalents or guidance. There are no Linux shell (bash) or cross-platform upgrade examples, and some configuration snippets are Windows-focused.
Recommendations
  • Add Linux/bash equivalents for cluster upgrade operations, or clarify if these operations are only supported on Windows.
  • When discussing disabling updates or configuring OS settings, provide Linux-specific instructions or explicitly state if not applicable.
  • Balance PowerShell examples with bash/CLI examples where possible, especially for critical management tasks.
  • Clearly indicate when a step or command is Windows-only, and provide links or guidance for Linux users.
Service Fabric Service Fabric Cluster Resource Manager - Placement Policies ...ce-manager-advanced-placement-rules-placement-policies.md
Medium Priority View Details →
Scanned: 2026-03-03 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 for configuring Service Fabric placement policies using C# and PowerShell. All CLI examples are PowerShell-based, with no mention of Linux/macOS equivalents (such as Azure CLI, Bash, or REST API). PowerShell examples are presented immediately after the C# code, and no cross-platform command-line guidance is given. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other tools.
Recommendations
  • Add Azure CLI examples for each placement policy configuration, where possible.
  • Include REST API or ARM template snippets for configuring placement policies, to provide platform-neutral options.
  • Explicitly mention whether PowerShell commands can be run on Linux/macOS (using PowerShell Core), or clarify if they are Windows-only.
  • Provide guidance for Linux/macOS users on how to configure placement policies using available tools.
Scanned: 2026-03-03 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed examples for configuring auto scaling in Azure Service Fabric using application manifests, C# APIs, and PowerShell. However, all CLI/script examples are exclusively in PowerShell, which is primarily a Windows tool. There are no equivalent Linux/macOS command-line examples (e.g., Bash, Azure CLI, or REST API). The documentation also presents PowerShell examples before mentioning any cross-platform alternatives, and does not clarify Linux support for these operations, despite Service Fabric supporting Linux containers.
Recommendations
  • Add equivalent examples using Azure CLI or Bash scripts for Linux/macOS users.
  • Clarify which operations and tools are supported on Linux clusters, especially for containerized workloads.
  • Mention REST API options for configuring scaling policies, if available.
  • Explicitly state any limitations or differences for Linux users in relevant sections.
  • Consider reordering examples so that cross-platform methods (e.g., Azure CLI, REST API) are presented before or alongside PowerShell.
Scanned: 2026-03-03 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides PowerShell and C# examples for configuring Service Fabric MoveCost, but does not include equivalent Linux shell (e.g., Bash/CLI) examples. PowerShell is Windows-centric, and the absence of Azure CLI or Bash examples creates friction for Linux/macOS users.
Recommendations
  • Add Azure CLI examples for creating and updating Service Fabric services with MoveCost settings, if supported.
  • If PowerShell is the only supported scripting interface, explicitly state this and provide guidance for Linux/macOS users (e.g., using Azure Cloud Shell or cross-platform PowerShell).
  • Clarify any platform limitations for Service Fabric management tools.
  • Consider including REST API examples, which are platform-agnostic.
Scanned: 2026-03-03 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides PowerShell examples for configuring service sensitivity and maximum load, but does not mention or provide equivalent CLI or scripting examples for Linux/macOS users. The PowerShell API is featured prominently, and there is no reference to cross-platform tools (such as Azure CLI or REST API) for these operations. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other tools.
Recommendations
  • Add examples using Azure CLI or REST API for configuring service sensitivity and maximum load, if supported.
  • Clarify whether PowerShell commands can be run cross-platform (e.g., with PowerShell Core), or provide guidance for Linux/macOS users.
  • If certain operations are only possible via PowerShell, explicitly state this limitation and suggest alternatives or workarounds.
  • Consider including Bash or shell script examples if relevant APIs are available.
  • Document any GUI or portal-based configuration options for users on non-Windows platforms.