Service Fabric

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

Bias Trend Over Time

Pages with Bias Issues

2475 issues found
Showing 1626-1650 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-02-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides conceptual information about Service Fabric hosting models, but operational examples and tooling references are heavily skewed toward Windows/PowerShell. The only CLI example is PowerShell, and all links to command references are for PowerShell modules. There are no Linux/macOS CLI examples (e.g., Azure CLI, Bash), nor are Linux-native tools or patterns mentioned. This creates friction for Linux/macOS users who may need to perform equivalent operations.
Recommendations
  • Add Azure CLI examples for creating services with ServicePackageActivationMode, especially for Linux/macOS users.
  • Include Bash or shell script examples where applicable.
  • Reference cross-platform tools and APIs (such as Azure CLI or REST API) alongside PowerShell, not just as secondary mentions.
  • Clarify which operations can be performed from Linux/macOS and provide guidance or links for those users.
  • Consider reordering examples so that cross-platform approaches are shown first or equally with Windows/PowerShell.
GitHub Create Pull Request
Service Fabric Azure Service Fabric container application manifest examples ...abric/service-fabric-manifest-example-container-app.md
Medium Priority View Details →
Scanned: 2026-02-12 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 Azure Service Fabric container application manifest examples demonstrates a notable Windows bias. The examples and explanations are based on the 'Windows Server 2016 Container Sample', and Windows-specific tools and patterns (such as 'winver' for OS build detection and Windows file paths like 'c:\VolumeTest\Data') are referenced exclusively or before Linux equivalents. There is no mention of Linux-specific patterns, file paths, or commands, nor are Linux-based container samples or manifest examples provided. While some features (like certificate handling) mention both Windows and Linux outcomes, the overall guidance and examples are Windows-centric.
Recommendations
  • Include Linux-based container manifest examples, such as referencing the Linux sample repo or showing Linux file paths (e.g., '/mnt/data').
  • When describing OS build detection, mention Linux equivalents (e.g., 'cat /etc/os-release' or 'uname -r') alongside 'winver'.
  • Provide guidance or notes for Linux users where behaviors or configuration differ (e.g., volume mounting, certificate formats, isolation modes).
  • Balance examples and explanations so that Linux and Windows users can both follow along and see relevant patterns.
GitHub Create Pull Request
Service Fabric Service communication with the ASP.NET Core ...vice-fabric-reliable-services-communication-aspnetcore.md
Medium Priority View Details →
Scanned: 2026-02-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation provides both Windows (HTTP.sys) and cross-platform (Kestrel) options for hosting ASP.NET Core services in Azure Service Fabric. However, Windows-specific tools and patterns (such as HTTP.sys, Windows HTTP Server API, netsh) are discussed in detail and often before their Linux equivalents. HTTP.sys is clearly marked as Windows-only, but the documentation sometimes presents Windows-centric approaches first and references Windows tools without mentioning Linux alternatives. PowerShell or Windows command-line tools are referenced for endpoint configuration, but Linux equivalents (such as firewall or port management) are not discussed.
Recommendations
  • Ensure Linux parity by providing explicit Linux/macOS guidance for endpoint configuration, port management, and firewall setup.
  • When referencing Windows tools (e.g., netsh), mention that Linux users do not need to perform these steps, or provide Linux/macOS alternatives where relevant.
  • Present cross-platform options (Kestrel) before Windows-only options (HTTP.sys) to reinforce Linux support.
  • Clarify any OS-specific limitations or requirements in each section, especially when discussing configuration or deployment steps.
  • Add troubleshooting and deployment notes for Linux/macOS Service Fabric clusters where applicable.
GitHub Create Pull Request
Service Fabric Replica soft delete for enhanced data protection in Service Fabric ...s/service-fabric/service-fabric-replica-soft-delete.md
Medium Priority View Details →
Scanned: 2026-02-12 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' primarily references PowerShell APIs (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica) and provides examples and command references exclusively in PowerShell syntax. There is no mention of Linux or cross-platform equivalents, nor are CLI or REST API examples provided. The documentation assumes familiarity with Windows tooling and does not address how Linux/macOS users can perform equivalent operations or whether these APIs are accessible via other means.
Recommendations
  • Add examples using Azure CLI or REST API if available, to demonstrate cross-platform usage.
  • Clarify whether the PowerShell APIs are supported on Linux/macOS (via PowerShell Core), and provide guidance for those environments.
  • Mention or link to FabricClient API usage in non-Windows environments, including sample code or commands.
  • Explicitly state any platform limitations if the feature or APIs are Windows-only, to avoid confusion.
  • Provide parity in documentation by showing Linux/macOS workflows alongside Windows/PowerShell examples.
GitHub Create Pull Request
Service Fabric Add custom Service Fabric health reports ...rticles/service-fabric/service-fabric-report-health.md
Medium Priority View Details →
Scanned: 2026-02-12 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 detailed examples for reporting health in Azure Service Fabric using PowerShell, including command-line snippets and configuration, but does not offer equivalent examples for Linux/macOS environments. PowerShell is presented as the primary CLI method, with no mention of cross-platform alternatives (such as Bash, Azure CLI, or REST via curl). The REST API is mentioned but not demonstrated with practical, platform-neutral examples. This creates friction for Linux/macOS users, who may not have access to PowerShell or Windows-specific Service Fabric tools.
Recommendations
  • Add equivalent CLI examples using Azure CLI or Bash scripts for Linux/macOS users.
  • Demonstrate REST API usage with curl or HTTPie, including sample requests and responses.
  • Clarify which PowerShell commands are available cross-platform (via PowerShell Core) and which are Windows-only.
  • Mention any Linux-native Service Fabric tools or SDKs, if available.
  • Reorder sections to present REST and platform-neutral methods before Windows/PowerShell-specific examples.
GitHub Create Pull Request
Service Fabric Fault Analysis Service overview .../service-fabric/service-fabric-testability-overview.md
Medium Priority View Details →
Scanned: 2026-02-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides explicit PowerShell instructions for using the Fault Analysis Service but does not mention or provide examples for Linux/macOS users (e.g., Bash, CLI, or REST API usage). It references the Service Fabric PowerShell module and SDK, which are Windows-centric tools, without discussing cross-platform alternatives.
Recommendations
  • Add examples for using the Fault Analysis Service via Azure CLI, Bash, or REST API to support Linux/macOS users.
  • Clarify whether the Fault Analysis Service APIs can be accessed from non-Windows environments, and provide guidance if so.
  • If PowerShell Core (cross-platform) is supported, mention this explicitly and provide installation instructions for Linux/macOS.
  • Link to or document any cross-platform SDKs or tools that can be used to interact with the Fault Analysis Service.
GitHub Create Pull Request
Service Fabric RunToCompletion semantics and specifications ...blob/main/articles/service-fabric/run-to-completion.md
Medium Priority View Details →
Scanned: 2026-02-10 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 provides RunToCompletion semantics for Service Fabric, but the code examples and guidance are exclusively focused on Windows containers (using Windows NanoServer images and Windows-specific commands). Querying deployment status is described only with PowerShell and C# APIs, with no mention of Linux tooling or Bash equivalents. There are no examples or guidance for Linux containers or cross-platform scenarios, despite Service Fabric supporting Linux containers.
Recommendations
  • Add equivalent examples for Linux containers, using a Linux base image (e.g., Ubuntu or Alpine) and Linux shell commands.
  • Clarify whether RunToCompletion semantics are supported for Linux containers, and if so, provide guidance and code samples.
  • Include instructions for querying deployment status using Bash/CLI tools on Linux, such as Azure CLI or REST API.
  • Avoid using Windows-specific terminology (e.g., 'cmd', 'set', 'exitCode') in generic sections; provide cross-platform alternatives.
  • Explicitly state any limitations or differences for Linux users if certain features are Windows-only.
GitHub Create Pull Request
Service Fabric Restoring backup in Azure Service Fabric ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-backup-restore-service-trigger-restore.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page for restoring backup in Azure Service Fabric is heavily biased toward Windows and PowerShell usage. All command-line examples use PowerShell, including REST API calls, with no mention of Linux/macOS alternatives (such as Bash, curl, or Azure CLI). The prerequisite section requires installation of a PowerShell module, and the workflow assumes the use of Windows tools. There are no Linux/macOS-specific instructions or parity examples, which creates friction for non-Windows users.
Recommendations
  • Add equivalent Bash/curl examples for REST API calls, showing how to trigger backup and restore operations from Linux/macOS.
  • Mention Azure CLI commands if available for relevant operations.
  • Clarify whether the PowerShell module is cross-platform or Windows-only; if Windows-only, provide alternative guidance for Linux/macOS users.
  • Include notes or sections for Linux/macOS users, outlining any differences or limitations.
  • Consider providing sample scripts or guidance for using Service Fabric REST APIs directly from non-Windows environments.
GitHub Create Pull Request
Service Fabric On-demand backup in Azure Service Fabric ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-backup-restore-service-ondemand-backup.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily focused on PowerShell-based workflows and the Microsoft.ServiceFabric.Powershell.Http module, with all code examples using PowerShell. There are no CLI, Bash, or cross-platform examples, nor is there guidance for Linux/macOS users on how to perform on-demand backups. The REST API is only demonstrated via PowerShell, not with curl or other cross-platform tools.
Recommendations
  • Add equivalent examples using Azure CLI or Bash scripts where possible.
  • Demonstrate REST API usage with curl or HTTPie for Linux/macOS users.
  • Clarify whether the PowerShell module is supported on PowerShell Core (pwsh) on Linux/macOS, and provide installation instructions if so.
  • Explicitly mention if certain features are Windows-only, or provide alternative guidance for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Service Fabric Explorer blocking operations ...ged-cluster-service-fabric-explorer-blocking-operation.md
Medium Priority View Details →
Scanned: 2026-02-10 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 cmdlets (Az PowerShell, AzSF PowerShell) for managing Service Fabric resources, with no mention of Linux/macOS equivalents or Azure CLI commands except a single reference to 'az resource'. The examples and instructions are PowerShell-centric, which may create friction for Linux/macOS users who typically use Azure CLI or REST APIs.
Recommendations
  • Include Azure CLI examples for all operations (e.g., deleting resources, creating applications/services) alongside PowerShell cmdlets.
  • Clarify which commands are cross-platform and which are Windows-only.
  • Reference REST API options where available for platform-agnostic management.
  • Add notes or links for Linux/macOS users on how to perform equivalent operations.
GitHub Create Pull Request
Service Fabric Service sensitivity ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-sensitivity.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides PowerShell examples for configuring service sensitivity and maximum load, but does not offer equivalent Linux/macOS CLI or scripting examples (such as Bash or Azure CLI). PowerShell is presented before C# API examples, and there is no mention of cross-platform tools or commands, creating friction for Linux/macOS users who may not have access to PowerShell or prefer other tools.
Recommendations
  • Add Azure CLI or REST API examples for configuring service sensitivity and maximum load, as these are cross-platform and accessible from Linux/macOS.
  • Clarify whether PowerShell examples are usable on Linux (via PowerShell Core), or provide Bash script equivalents if possible.
  • Mention any limitations or prerequisites for Linux/macOS users, such as required SDKs or tools.
  • Consider including sample commands for cluster configuration using cross-platform tools (e.g., Azure CLI, Bash, Python SDK).
GitHub Create Pull Request
Service Fabric Azure Service Fabric dynamic node tags ...tps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-node-tagging.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation 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 primarily a Windows tool, and its exclusive use creates friction for non-Windows users. The C# API examples are cross-platform, but scripting and command-line operations are only shown for Windows.
Recommendations
  • Add Azure CLI or Bash examples for managing node tags and service tag requirements.
  • Include REST API sample calls for tag operations, as REST is platform-neutral.
  • Explicitly mention whether PowerShell cmdlets are available cross-platform (PowerShell Core) or only on Windows.
  • Reorder examples so that platform-neutral methods (REST, CLI) are shown before or alongside PowerShell.
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-02-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides a broad overview of Azure Service Fabric, covering both Windows and Linux support. However, there are several instances of Windows bias: Windows services and executables (e.g., FabricHost.exe) are described in detail before Linux equivalents are mentioned, and some examples (such as standalone clusters) are Windows-only. PowerShell is frequently referenced as a management tool, with Linux CLI alternatives mentioned but not emphasized equally. There are missing Linux-specific examples, especially for cluster creation and management, and some features are described as Windows-only without Linux parity.
Recommendations
  • Provide Linux-specific examples and workflows alongside Windows ones, especially for cluster creation, management, and standalone deployment.
  • When describing Service Fabric node architecture, clarify Linux equivalents or note differences more explicitly.
  • Ensure CLI (sfctl) and REST API usage are shown equally with PowerShell, and highlight Linux-friendly tooling where available.
  • Where features are Windows-only (e.g., standalone clusters), clearly state the limitation and link to Linux alternatives or roadmap.
  • In 'Next steps', add links to Linux cluster creation and management guides if available.
GitHub Create Pull Request
Service Fabric Health monitoring in Service Fabric ...s/service-fabric/service-fabric-health-introduction.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides a PowerShell-only example for reporting and evaluating application health in Service Fabric, without offering equivalent Linux/macOS CLI or REST API examples. The main walkthrough for health reporting is Windows-centric, creating friction for non-Windows users.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl) for Linux/macOS environments.
  • Include REST API examples for health reporting and querying, which are cross-platform.
  • Clearly indicate which tools are available on each platform and link to relevant installation guides.
  • Where PowerShell is used, provide alternative commands for Bash or other common Linux shells.
GitHub Create Pull Request
Service Fabric Azure Service Fabric image store connection string ...fabric/service-fabric-image-store-connection-string.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation repeatedly references PowerShell for cluster manifest retrieval and application deployment, and links primarily to PowerShell-based workflows. There is no mention of Linux/macOS equivalents (such as Bash, Azure CLI, or cross-platform Service Fabric SDK usage), nor are examples provided for non-Windows environments. The focus on Visual Studio and PowerShell further reinforces a Windows-centric approach, despite Service Fabric supporting Linux clusters.
Recommendations
  • Include examples for retrieving the cluster manifest and deploying applications using Azure CLI and Bash scripts.
  • Reference cross-platform Service Fabric SDK tools and workflows, clarifying which steps apply to Linux clusters.
  • Add links to documentation or guides for Linux/macOS users, especially for local development and deployment.
  • Mention any differences or limitations when configuring ImageStoreConnectionString on Linux clusters.
GitHub Create Pull Request
Service Fabric Manage apps for multiple environments ...e-fabric-manage-multiple-environment-app-configuration.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides examples for managing application parameters in Service Fabric, with a notable emphasis on PowerShell and Visual Studio workflows. PowerShell is mentioned first for application creation, and Visual Studio parameter files are discussed in detail. Linux-friendly tools like sfctl and Jenkins are referenced, but Windows-centric tools and patterns are prioritized.
Recommendations
  • Present Linux-native tools (sfctl, install.sh) before or alongside PowerShell examples.
  • Expand examples for Jenkins and other Linux/macOS CI/CD tools, including sample scripts.
  • Clarify which steps are cross-platform and which are Windows-specific.
  • Add explicit guidance for Linux/macOS users, including command-line examples and parameter file handling outside Visual Studio.
GitHub Create Pull Request
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-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation is largely OS-agnostic in its technical explanations, but the 'Next steps' section and some linked references focus on PowerShell for deployment and management tasks, which can create a perception of Windows bias. There are no explicit Linux examples or mentions of Linux-specific tools or workflows, and PowerShell is referenced before any cross-platform alternatives.
Recommendations
  • Include equivalent Linux/bash examples or references alongside PowerShell, especially in the 'Next steps' section.
  • Clarify when PowerShell commands are cross-platform (PowerShell Core) or Windows-only.
  • Add links to documentation for deploying and managing Service Fabric applications on Linux clusters using CLI or bash scripts.
  • Where possible, mention both Windows and Linux management workflows to ensure parity.
GitHub Create Pull Request
Service Fabric Azure Service Fabric container application manifest examples ...abric/service-fabric-manifest-example-container-app.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. The manifest examples are explicitly based on a Windows Server 2016 container sample, and Windows-specific tools (e.g., 'winver' for OS build detection) are referenced without Linux equivalents. The certificate handling section does mention both Windows (PFX) and Linux (PEM) formats, but Linux-specific instructions and examples are missing. The volume mount paths use Windows-style paths (e.g., 'c:\VolumeTest\Data'), and there are no Linux path examples or guidance. Overall, Linux parity is not achieved, and Linux users may encounter friction or confusion.
Recommendations
  • Provide equivalent Linux-based manifest examples, referencing Linux container samples.
  • Include instructions for obtaining OS build/version on Linux (e.g., 'cat /etc/os-release' or 'uname -r') alongside 'winver'.
  • Show Linux-style volume mount paths (e.g., '/mnt/volume/data') in examples.
  • Clarify which manifest settings and features are cross-platform and which are Windows-only.
  • Add links or references to Linux container documentation and samples for Service Fabric.
GitHub Create Pull Request
Service Fabric Define Service Configuration in StartupServices.xml for a Service Fabric Application ...service-fabric/service-fabric-startupservices-model.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation is heavily focused on Visual Studio workflows, referencing Windows-centric concepts such as F5/Ctrl+F5/Publish and right-click actions. There are no examples or guidance for Linux/macOS users or CLI-based workflows, and all deployment instructions assume the use of Visual Studio, which is primarily a Windows tool.
Recommendations
  • Add explicit guidance for Linux/macOS users, including how to manage service configuration outside Visual Studio.
  • Provide CLI-based examples (e.g., using Azure CLI, Service Fabric CLI, or PowerShell Core) for defining and deploying StartupServices.xml.
  • Clarify whether StartupServices.xml is supported or relevant for non-Windows environments, and if not, suggest alternatives.
  • Mention cross-platform tools and workflows where applicable, or explicitly state Windows-only limitations.
GitHub Create Pull Request
Service Fabric Learn Azure Service Fabric terminology ...es/service-fabric/service-fabric-technical-overview.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page is mostly neutral and conceptual, but some sections show Windows bias. The 'Node' definition references an 'auto-start Windows service, FabricHost.exe', and describes node startup in Windows-centric terms, without mentioning Linux equivalents or patterns. Executable examples (EXE/DLL) are Windows-first, and Windows containers are mentioned before Linux containers. However, the page does acknowledge Linux support and guest executables, and Service Fabric's cross-platform nature.
Recommendations
  • In the 'Node' section, clarify how Service Fabric nodes operate on Linux (e.g., what processes/services are involved, and whether FabricHost.exe is relevant).
  • When mentioning executable formats (EXE/DLL), add Linux equivalents (e.g., ELF binaries, .so files) to ensure parity.
  • When discussing containers, mention Linux container support before or alongside Windows containers.
  • Where Windows-specific tools or terminology are used, provide Linux/macOS equivalents or note differences.
GitHub Create Pull Request
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-02-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation is largely OS-neutral in its conceptual explanations, but when it comes to practical details, there is a notable Windows bias. Windows-specific certificate store paths and troubleshooting tools (e.g., LocalMachine\My, CAPI2 logging, Win32 CryptoAPI references) are mentioned first or exclusively, with Linux equivalents only briefly referenced or omitted. Troubleshooting and operational guidance focus on Windows event logs and tools, with little to no Linux-specific instructions or examples.
Recommendations
  • For every mention of Windows certificate store paths (e.g., LocalMachine\My), provide the Linux equivalent (e.g., /var/lib/sfcerts) consistently and with equal prominence.
  • Include Linux-specific troubleshooting steps, such as where to find Service Fabric logs on Linux nodes, and how to diagnose certificate issues using Linux-native tools (e.g., openssl, journalctl, or SF log locations).
  • When referencing Windows tools like CAPI2 logging or Win32 CryptoAPI, add Linux alternatives or clarify which steps are Windows-only and provide Linux guidance where possible.
  • In code/configuration examples, ensure both Windows and Linux paths/formats are shown side-by-side, especially for certificate loading and management.
  • Explicitly mention any differences in certificate handling or requirements between Windows and Linux clusters, if applicable.
GitHub Create Pull Request
Service Fabric Configure or modify a Service Fabric managed cluster node type ...vice-fabric/how-to-managed-cluster-modify-node-type.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides examples for modifying Service Fabric managed cluster node types using Azure Portal, ARM templates, and PowerShell. PowerShell is the only CLI example provided, with no mention of Azure CLI or Bash scripting. PowerShell is a Windows-centric tool, and its exclusive use in CLI examples creates friction for Linux/macOS users. Additionally, PowerShell examples are given equal prominence to ARM templates and Portal, rather than being secondary or accompanied by cross-platform alternatives.
Recommendations
  • Add Azure CLI examples for all operations currently demonstrated with PowerShell (add, remove, scale, configure placement properties, etc.).
  • Explicitly mention that PowerShell examples are Windows-centric and provide guidance for Linux/macOS users (e.g., using Azure CLI or REST API).
  • Where possible, show Azure CLI examples before or alongside PowerShell to ensure Linux parity.
  • Clarify if any operations are only possible via PowerShell and, if so, explain why and suggest alternatives for Linux users.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager: Movement cost ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-movement-cost.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides PowerShell examples for configuring MoveCost, but does not offer equivalent Linux CLI or Bash examples. PowerShell is primarily a Windows tool, and its exclusive use creates friction for Linux/macOS users. Additionally, PowerShell examples are presented before C# code, reinforcing Windows-first bias. There is no mention of Linux-native tools or Service Fabric CLI usage for these operations.
Recommendations
  • Add examples using Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • Include Bash or shell script snippets where applicable.
  • Clarify whether PowerShell commands can be run on Linux (via PowerShell Core), or provide guidance for Linux users.
  • Present CLI examples before or alongside PowerShell to avoid Windows-first ordering.
GitHub Create Pull Request
Service Fabric Manage certificates in a Service Fabric cluster ...vice-fabric/cluster-security-certificate-management.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides extensive PowerShell examples and references Windows-specific tools and behaviors (such as Key Vault VM extension for Windows, S-channel, and certificate linking), with little to no mention of Linux/macOS equivalents or cross-platform alternatives. Windows terminology and mechanisms are presented first and in detail, while Linux-specific guidance is largely absent.
Recommendations
  • Add equivalent Bash/CLI examples for certificate enrollment and management, especially for Key Vault operations.
  • Clarify which steps and tools are Windows-only and provide Linux/macOS alternatives where possible (e.g., for certificate provisioning and VM extensions).
  • Explicitly state platform limitations and supported OSes for each mechanism (e.g., Key Vault VM extension for Windows vs. Linux).
  • Include references or links to Linux/macOS documentation for Service Fabric certificate management.
  • Where PowerShell is used, offer Azure CLI or REST API alternatives for cross-platform users.
GitHub Create Pull Request
Service Fabric Introduction to the Service Fabric Infrastructure Service .../articles/service-fabric/infrastructure-service-faq.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides a PowerShell-only example for bypassing Infrastructure Service throttling, without mentioning equivalent Linux/macOS command-line options or tools. Service Fabric Explorer is referenced, but no cross-platform alternatives or clarifications are given. While Service Fabric clusters can run on both Windows and Linux, the guidance and tooling examples are Windows-centric.
Recommendations
  • Add equivalent Linux/macOS command-line instructions (e.g., using sfctl or REST API) for cluster operations.
  • Clarify whether the PowerShell cmdlet is available on Linux (via PowerShell Core) or provide alternatives.
  • Mention cross-platform tools like sfctl or REST endpoints for managing Service Fabric clusters.
  • Explicitly state if certain operations are Windows-only, or provide guidance for Linux users.
GitHub Create Pull Request
← Previous Page 66 of 99 Next →