Service Fabric

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 401-425 of 1305 flagged pages
Service Fabric Azure Service Fabric image store connection string ...fabric/service-fabric-image-store-connection-string.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 the Azure Service Fabric image store connection string shows a moderate Windows/PowerShell bias. It references PowerShell as the primary method for retrieving the cluster manifest and links to a PowerShell-based deployment guide as the next step. There is no mention of Linux/macOS command-line tools (such as Azure CLI, Bash, or cross-platform SDKs) for these tasks, nor are there examples or guidance for non-Windows environments. The documentation assumes Visual Studio usage for publishing, which is also Windows-centric.
Recommendations
  • Add examples or references for retrieving the cluster manifest using cross-platform tools such as Azure CLI or Bash scripts.
  • Include guidance or links for deploying applications to Service Fabric clusters from Linux/macOS environments, such as using Azure CLI, REST API, or cross-platform SDKs.
  • When referencing PowerShell, clarify if the instructions are applicable to PowerShell Core (which is cross-platform) or only to Windows PowerShell.
  • Provide parity in 'Next steps' by including links to non-Windows deployment guides or documentation.
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-15 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exhibits a Windows-first bias. The manifest examples and explanations are based on the 'Windows Server 2016 Container Sample', and references to OS-specific behaviors (such as using 'winver' to get the build version) are Windows-centric. There are no explicit Linux container examples, nor are Linux-specific patterns or commands shown. While some notes mention Linux (e.g., certificate handling), the overall guidance and sample manifests do not provide parity for Linux container deployments on Service Fabric.
Recommendations
  • Add equivalent Linux container manifest examples, referencing Linux-based images and configuration differences.
  • Include instructions or notes for obtaining Linux OS build/version information relevant to Service Fabric container compatibility.
  • Clarify which manifest elements or features differ between Windows and Linux container deployments.
  • Where features are cross-platform, provide both Windows and Linux sample values, paths, and commands.
  • Link to Linux container samples in the Azure-Samples repository if available.
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-15 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation covers both Windows-only (HTTP.sys) and cross-platform (Kestrel) web servers for ASP.NET Core in Service Fabric. However, Windows-specific tools (HTTP.sys, netsh) and patterns are discussed in detail, often before their Linux equivalents. There are explicit notes about HTTP.sys being Windows-only, but Linux-specific guidance and examples are limited. Kestrel, the cross-platform option, is recommended for Linux, but Linux-specific configuration, troubleshooting, or parity notes are missing.
Recommendations
  • Add explicit Linux/macOS guidance for Service Fabric scenarios, including any OS-specific configuration steps or troubleshooting.
  • Provide Linux/macOS-specific examples (e.g., file paths, firewall configuration, certificate management for HTTPS with Kestrel).
  • Clarify any limitations or differences for Service Fabric on Linux (e.g., port assignment, endpoint configuration, cluster setup).
  • Mention Linux tools or commands where Windows tools (like netsh) are referenced.
  • Ensure parity in example ordering: present Kestrel (cross-platform) before HTTP.sys (Windows-only) in relevant sections.
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-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 detailed examples for reporting health in Service Fabric using PowerShell and .NET APIs, but all PowerShell examples are Windows-centric and there are no equivalent Linux/bash CLI examples. PowerShell is presented as a primary method for interacting with Service Fabric, with no mention of cross-platform alternatives like Azure CLI or Bash scripts. The REST API is mentioned but not demonstrated with a concrete example. This creates friction for Linux/macOS users, who cannot use PowerShell natively and are left without clear guidance for their platforms.
Recommendations
  • Add equivalent examples using Azure CLI or Bash scripts for health reporting tasks, especially where PowerShell is used.
  • Explicitly mention cross-platform tools and how Linux/macOS users can perform the same operations.
  • Provide concrete REST API examples (with curl or HTTPie) for health reporting, including sample request bodies and endpoints.
  • Clarify which Service Fabric management tasks can be performed using Azure CLI or REST, and link to relevant cross-platform documentation.
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-15 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation is heavily oriented toward Visual Studio workflows, referencing Windows-specific actions (Build/Rebuild/F5/Ctrl+F5/Publish) and UI elements. It does not provide equivalent guidance or examples for Linux/macOS users, nor does it mention cross-platform tooling or alternative approaches outside Visual Studio. The only mention of command-line deployment refers to PowerShell cmdlets, with no Linux CLI or Azure CLI examples.
Recommendations
  • Add explicit guidance for Linux/macOS users, including how to manage StartupServices.xml and ApplicationManifest.xml outside Visual Studio.
  • Provide examples using Azure CLI or Service Fabric CLI (sfctl) for deployment and configuration, not just PowerShell.
  • Clarify whether StartupServices.xml is supported or relevant for non-Windows development environments, and if not, state this clearly.
  • Mention alternative editors or workflows for editing XML files and deploying Service Fabric applications on Linux/macOS.
  • If the feature is Visual Studio/Windows-only, add a clear note at the top indicating this limitation.
GitHub Create Pull Request
Service Fabric Configure the upgrade of a Service Fabric application ...abric/service-fabric-visualstudio-configure-upgrade.md
Medium Priority View Details →
Scanned: 2026-02-15 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on Windows-centric tools, specifically Visual Studio and PowerShell, for configuring and upgrading Service Fabric applications. All examples and instructions reference Windows tools, with no mention of Linux/macOS alternatives or cross-platform CLI methods. The use of PowerShell is presented as the only manual upgrade method, and there are no examples or guidance for Linux users or those using Azure CLI or REST APIs.
Recommendations
  • Add instructions and examples for upgrading Service Fabric applications using cross-platform tools such as Azure CLI or REST API.
  • Include guidance for Linux/macOS users, such as how to perform upgrades from a Linux machine or using non-Windows tools.
  • Clarify if Visual Studio and PowerShell are required, or provide alternative workflows for users on other platforms.
  • Present PowerShell and Windows tools alongside, not before, cross-platform options to avoid Windows-first bias.
GitHub Create Pull Request
Service Fabric Fault Analysis Service overview .../service-fabric/service-fabric-testability-overview.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 provides explicit PowerShell instructions for using the Fault Analysis Service, but does not mention or provide examples for Linux/macOS command-line tools or SDKs. The PowerShell section appears before any mention of cross-platform alternatives, and there is no guidance for Linux users on how to interact with the service via CLI or REST APIs.
Recommendations
  • Add examples for using the Fault Analysis Service from Linux/macOS environments, such as via Azure CLI, REST API, or cross-platform SDKs.
  • Clarify whether PowerShell usage is required or if alternative tools are available for non-Windows users.
  • Provide parity in documentation by including Linux/macOS-specific instructions or references alongside PowerShell examples.
GitHub Create Pull Request
Service Fabric Advanced Application Upgrade Topics ...-fabric/service-fabric-application-upgrade-advanced.md
Medium Priority View Details →
Scanned: 2026-02-14 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 extensive PowerShell examples and references to PowerShell cmdlets for Service Fabric application upgrades, without offering equivalent CLI or Linux-native examples. Windows/PowerShell tools are mentioned first and exclusively, creating friction for Linux/macOS users who may use Azure CLI or REST APIs. There is no explicit mention of Linux-compatible tooling or guidance for non-Windows environments.
Recommendations
  • Add Azure CLI examples for all upgrade operations alongside PowerShell examples.
  • Explicitly mention that Service Fabric management can be performed from Linux/macOS using Azure CLI or REST API, and provide links to relevant documentation.
  • Include sample ARM template snippets for upgrade operations where possible.
  • Clarify which operations are PowerShell-only (if any), and provide guidance or alternatives for Linux users.
  • Reorder sections or examples to avoid always showing Windows/PowerShell first.
GitHub Create Pull Request
Service Fabric Describing Azure Service Fabric apps and services ...ic/service-fabric-application-and-service-manifests.md
Medium Priority View Details →
Scanned: 2026-02-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation contains a notable Windows bias in its tooling recommendations. The only explicit tooling advice is to use Visual Studio on Windows and a Windows file path for validating manifest XML schemas. Additionally, the PowerShell module is mentioned for service creation, but no Linux or cross-platform alternatives are referenced. There are no Linux/macOS-specific examples or guidance, and Windows tools are mentioned first and exclusively.
Recommendations
  • Add instructions for validating XML schema on Linux/macOS, such as using xmllint or VS Code with XML plugins.
  • Mention cross-platform alternatives to Visual Studio, like Visual Studio Code or JetBrains Rider.
  • Provide examples for creating services using Azure CLI or other cross-platform tools, not just PowerShell.
  • Include Linux/macOS file path conventions where relevant.
  • Clarify which steps are Windows-only and which are cross-platform.
GitHub Create Pull Request
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides numerous manual scaling instructions using PowerShell cmdlets (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState), but does not mention equivalent Linux CLI commands or tools. PowerShell is referenced as the primary method for manual node management, and Windows-centric tools are presented first or exclusively. While Service Fabric supports Linux clusters, the documentation does not offer Linux-specific guidance or examples for these operations, creating friction for Linux users.
Recommendations
  • Add equivalent Linux CLI instructions for node management (e.g., using sfctl or Service Fabric CLI).
  • Include Linux-specific examples and workflows alongside PowerShell examples.
  • Clarify which commands are cross-platform and which are Windows-only.
  • Provide links to Linux tooling documentation (e.g., sfctl, Azure CLI) where relevant.
  • Ensure parity in example ordering (e.g., show Linux and Windows approaches side by side).
GitHub Create Pull Request
Service Fabric Understanding periodic backup configuration ...-fabric-backuprestoreservice-configure-periodic-backup.md
Medium Priority View Details →
Scanned: 2026-02-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page is generally platform-neutral, focusing on Azure Service Fabric's backup configuration concepts and REST APIs. However, in the 'File share' backup storage section, only Windows-style file share paths (\\StorageServer\BackupStore) and Windows authentication methods are described, with no mention of Linux-compatible SMB mounting or examples. The file share authentication options are Windows-centric, and Windows terminology is used first and exclusively. There are no Linux-specific examples or guidance for configuring file share backups from Linux nodes.
Recommendations
  • Add examples and guidance for configuring file share backup storage from Linux-based Service Fabric clusters, including SMB mount instructions and authentication methods.
  • Mention Linux-compatible file share path formats and clarify any platform limitations.
  • If file share backup is Windows-only, explicitly state this to avoid confusion for Linux users.
  • Consider including parity examples for Linux/macOS where possible, or linking to relevant platform-specific documentation.
GitHub Create Pull Request
Service Fabric Deny assignment policy for Service Fabric managed clusters ...cles/service-fabric/managed-cluster-deny-assignment.md
Medium Priority View Details →
Scanned: 2026-02-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides examples and links primarily for Azure PowerShell, with PowerShell-based tools mentioned before Azure CLI and sfctl. While Azure CLI and ARM templates are referenced, the best practices section highlights PowerShell commands first and does not provide equivalent CLI or Linux-native examples for key actions. This creates friction for Linux/macOS users who may prefer CLI or other cross-platform tools.
Recommendations
  • Add Azure CLI examples for deleting NodeTypes, restarting, and reimaging scale sets alongside PowerShell examples.
  • Mention Azure CLI and sfctl before or equally with PowerShell in best practices to avoid Windows-first ordering.
  • Clarify which tools are cross-platform and provide guidance for Linux/macOS users.
  • Include sample commands for ARM/Bicep deployments using CLI.
  • Explicitly state that PowerShell examples are also available via Azure CLI for parity.
GitHub Create Pull Request
Service Fabric Architecture of Azure Service Fabric ...articles/service-fabric/service-fabric-architecture.md
Medium Priority View Details →
Scanned: 2026-02-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page on the architecture of Azure Service Fabric briefly mentions PowerShell cmdlets as a primary management interface, suggesting a Windows-centric approach to cluster and application lifecycle management. There is no mention of Linux equivalents (such as Bash, CLI, or REST API usage), nor are Linux tools or patterns referenced. The mention of Windows security as an option for securing transport is secondary and does not dominate the content, but the management section's focus on PowerShell creates friction for Linux users.
Recommendations
  • Add examples or references to Azure CLI, Bash scripts, or REST API usage for cluster and application management, alongside PowerShell.
  • Clarify that management operations can be performed from Linux/macOS using Azure CLI or REST APIs, not just PowerShell.
  • Mention Linux-compatible security mechanisms (such as X509 certificates) more prominently when discussing transport security.
  • Ensure that administrative APIs are described in a cross-platform way, not just via Windows tooling.
GitHub Create Pull Request
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides configuration examples for both Windows (ClusterManifest.xml) and generic/standalone (ClusterConfig.json), but code samples and CLI usage are heavily focused on PowerShell and .NET/C#. There are no Linux-specific CLI examples (e.g., Bash, SFCTL), and the WindowsServer element is shown first in infrastructure configuration. This creates friction for Linux users, especially those running Service Fabric on Linux or using cross-platform tools.
Recommendations
  • Add equivalent Linux/Bash/SFCTL command examples alongside PowerShell for service creation and updates.
  • Clarify that ClusterManifest.xml is for Windows clusters and ClusterConfig.json is for cross-platform/standalone deployments; consider showing Linux infrastructure configuration first or equally.
  • Include explicit guidance or links for Linux users, such as how to configure clusters using Linux node types and relevant tools.
  • Mention cross-platform Service Fabric SDKs and management tools where applicable.
GitHub Create Pull Request
Service Fabric Cluster Resource Manager - Management Integration ...fabric-cluster-resource-manager-management-integration.md
Medium Priority View Details →
Scanned: 2026-02-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides a PowerShell example for querying partition health, using Windows-style paths and commands (e.g., 'PS C:\Users\User > Get-ServiceFabricPartitionHealth'). No equivalent Linux/macOS CLI or REST API example is provided, and the PowerShell example appears early in the page. The rest of the documentation is largely platform-neutral, focusing on concepts and configuration files, but the example section is Windows-centric.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl) for Linux/macOS users.
  • Mention REST API alternatives for querying health, which are cross-platform.
  • When showing command-line examples, provide both Windows (PowerShell) and Linux/macOS (bash/sfctl) versions side-by-side.
  • Clarify that PowerShell is not required and that Linux/macOS users can use sfctl or REST APIs.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page presents Windows/PowerShell tooling (New-ServiceFabricApplication cmdlet, Visual Studio, Deploy-FabricApplication.ps1) before mentioning Linux-compatible options (sfctl, install.sh). PowerShell and Visual Studio examples are prioritized, and Linux-specific workflows are only briefly referenced. There are no explicit Linux/macOS examples or screenshots, and the scripting guidance is predominantly Windows-centric.
Recommendations
  • Add explicit Linux/macOS examples for application creation, such as using sfctl and install.sh, with sample commands and parameter formats.
  • Reorder sections to present cross-platform tools (sfctl) before Windows-specific tools (PowerShell, Visual Studio).
  • Include guidance for editing parameter files and deploying from Linux/macOS environments.
  • Clarify which tools are cross-platform and which are Windows-only, to help users choose the right workflow.
GitHub Create Pull Request
Service Fabric Secure an Azure Service Fabric cluster ...cles/service-fabric/service-fabric-cluster-security.md
Medium Priority View Details →
Scanned: 2026-02-14 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 exhibits moderate Windows bias. Windows Server clusters and Windows security patterns are mentioned repeatedly and often before Linux equivalents. There are explicit references to Windows authentication (Kerberos), Windows certificate services, and Windows-specific tools (MakeCert.exe). While the concept of securing clusters is stated to be the same for Linux and Windows, practical guidance and links for Linux standalone clusters are missing, and Windows-focused instructions and links are provided first or exclusively.
Recommendations
  • Add explicit guidance and links for securing standalone Linux Service Fabric clusters, including certificate setup and client authentication.
  • Provide Linux-specific examples and tools for certificate creation and management (e.g., OpenSSL usage, Linux certificate authorities).
  • Ensure parity in documentation structure: mention Linux options alongside Windows options, not only after or as an afterthought.
  • Clarify any Azure Service Fabric features that are Windows-only, and highlight Linux limitations or differences where relevant.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation provides a detailed conceptual overview of Service Fabric health monitoring, which is cross-platform in nature. However, the only practical example for reporting and evaluating application health is given using PowerShell cmdlets, which are Windows-specific. There are no equivalent Linux/macOS CLI or REST API examples, and PowerShell is presented as the default method for interacting with Service Fabric health reporting. Additionally, the example section does not mention Linux tooling or provide parity for non-Windows users.
Recommendations
  • Add equivalent examples using Azure CLI, REST API, or Service Fabric SDKs for Linux/macOS environments.
  • Explicitly mention that PowerShell is Windows-specific and provide guidance for Linux users on how to accomplish the same tasks.
  • Include sample code snippets for health reporting and querying using cross-platform tools (e.g., curl for REST API, Azure CLI, or Python SDK).
  • Reorder or supplement the example section to show Linux/macOS methods alongside or before Windows/PowerShell examples.
GitHub Create Pull Request
Service Fabric Networking patterns for Azure Service Fabric ...s/service-fabric/service-fabric-patterns-networking.md
Medium Priority View Details →
Scanned: 2026-02-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation consistently provides only PowerShell-based deployment commands and Windows-centric operational examples (e.g., RDP, Windows command prompt usage), with no mention of Azure CLI, Bash, or cross-platform alternatives. This creates friction for Linux/macOS users, who must translate or adapt the instructions themselves.
Recommendations
  • Add Azure CLI equivalents for all PowerShell deployment commands (e.g., resource group and template deployments).
  • Include Bash shell examples where relevant, especially for operations like pinging VMs.
  • Mention cross-platform remote access options (e.g., SSH) alongside or instead of RDP, and clarify when RDP is only applicable to Windows nodes.
  • Explicitly state when a step is Windows-only and provide Linux/macOS alternatives where possible.
  • Consider providing a table or toggle for PowerShell vs. Azure CLI commands, as seen in other Azure documentation.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Events ...es/service-fabric/service-fabric-diagnostics-events.md
Medium Priority View Details →
Scanned: 2026-02-14 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 Events primarily describes event access via Windows-centric channels such as ETW/Windows Event logs and the Windows Azure diagnostics agent. Linux equivalents (e.g., Linux diagnostics agents, log access methods, or monitoring tools) are not mentioned, and Windows tools are referenced first and exclusively. This creates friction for Linux-based Service Fabric clusters, as guidance for event access and monitoring is not provided for those environments.
Recommendations
  • Add explicit instructions or examples for accessing Service Fabric events on Linux clusters, including supported logging channels and monitoring tools.
  • Mention Linux diagnostics agents and how to configure them for event collection and forwarding.
  • Clarify which event access methods are cross-platform (e.g., EventStore REST APIs) and which are Windows-only.
  • Provide parity in documentation by listing Linux methods alongside Windows methods, rather than only referencing Windows tools.
GitHub Create Pull Request
Service Fabric Fault Analysis Service overview .../service-fabric/service-fabric-testability-overview.md
Medium Priority View Details →
Scanned: 2026-02-14 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 examples and guidance for using the Fault Analysis Service primarily via C# and PowerShell, both of which are Windows-centric tools. There is no mention of Linux/macOS equivalents, such as Bash, CLI commands, or cross-platform scripting approaches. The PowerShell example assumes a Windows environment and does not address how Linux users can interact with the Fault Analysis Service, nor does it reference Azure CLI or REST API usage.
Recommendations
  • Add examples for using the Fault Analysis Service from Linux/macOS environments, such as via Azure CLI, Bash scripts, or REST API.
  • Clarify whether the Fault Analysis Service APIs can be accessed from non-Windows platforms and provide guidance for cross-platform usage.
  • Include instructions for installing and using Service Fabric SDK and tools on Linux/macOS, if supported.
  • Mention alternative scripting tools (e.g., Bash, Python) for interacting with Service Fabric clusters.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page provides a comprehensive overview of certificate management in Azure Service Fabric clusters, but exhibits Windows bias in several areas. PowerShell is used exclusively for scripting examples, and the Key Vault VM extension discussed is Windows-specific. The documentation references Windows concepts (such as certificate store locations, ACLing, S-channel, and renewal linking) without Linux equivalents or alternatives. Windows tools and patterns are mentioned first and exclusively, with no Linux-specific guidance or parity for certificate provisioning, automation, or management.
Recommendations
  • Add Linux-specific scripting examples (e.g., Bash, Azure CLI) alongside PowerShell.
  • Explicitly document how certificate provisioning and management can be accomplished on Linux-based Service Fabric clusters, including any limitations or differences.
  • Clarify which VM extensions or provisioning mechanisms are supported on Linux and provide guidance for Linux users.
  • Mention Linux certificate store locations and access control mechanisms where relevant.
  • If certain features are Windows-only (e.g., Key Vault VM extension for Windows), clearly state this and provide Linux alternatives or workarounds.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation is generally cross-platform and describes Service Fabric's X.509 certificate authentication in an OS-neutral way. However, there are several subtle Windows biases: Windows certificate store paths and tools are mentioned first or exclusively in some places, troubleshooting instructions and error logs reference Windows event logs and Win32 APIs, and Linux-specific equivalents are only briefly mentioned or omitted. There are no PowerShell-heavy examples, but Windows-centric patterns and terminology are more prominent.
Recommendations
  • Wherever the Windows certificate store (e.g., LocalMachine\My) is referenced, explicitly mention the Linux equivalent (e.g., /var/lib/sfcerts) each time, not just once.
  • In troubleshooting sections, provide Linux log file paths and diagnostic steps alongside Windows Event Log instructions.
  • When referencing Windows-specific APIs (e.g., Win32 CryptoAPI), clarify how equivalent functionality is handled on Linux, or note if not applicable.
  • If there are differences in certificate provisioning or management between Windows and Linux nodes, provide parallel examples or links to Linux-specific guidance.
  • Add explicit Linux/macOS troubleshooting tips for common certificate issues (e.g., permissions, file locations, service restarts).
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides examples for configuring Service Fabric managed cluster node types using the Azure Portal, ARM templates, and PowerShell. PowerShell is the only CLI example given, with no mention of Azure CLI or Bash scripting alternatives. PowerShell is a Windows-centric tool, and its exclusive use creates friction for Linux/macOS users. Additionally, PowerShell examples are presented before any potential cross-platform alternatives, reinforcing a Windows-first approach.
Recommendations
  • Add Azure CLI examples for all tasks currently demonstrated with PowerShell, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that PowerShell examples are Windows-centric and provide guidance for Linux/macOS users.
  • Consider including Bash scripting or REST API examples where appropriate.
  • Where possible, clarify that ARM templates and portal are platform-agnostic.
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-14 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, and references Service Fabric Explorer, which is primarily a Windows tool. There are no Linux CLI or cross-platform alternatives mentioned for cluster operations, and the PowerShell command is presented as the sole method for manual intervention.
Recommendations
  • Add equivalent Linux/macOS CLI examples (e.g., Azure CLI, Bash) for manual cluster operations.
  • Clarify whether Service Fabric Explorer is accessible or usable from Linux/macOS, or provide alternatives if available.
  • Where possible, provide cross-platform guidance for connecting to and managing Service Fabric clusters.
  • Explicitly note if certain commands or tools are Windows-only, and offer Linux/macOS workarounds or alternatives.
GitHub Create Pull Request
← Previous Page 17 of 53 Next →