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 2101-2125 of 2475 flagged pages
Service Fabric Manage apps for multiple environments ...e-fabric-manage-multiple-environment-app-configuration.md
Medium Priority View Details →
Scanned: 2026-02-01 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias by prioritizing PowerShell and Visual Studio workflows, mentioning Windows-centric tools and scripts first, and lacking explicit Linux/macOS command examples. While sfctl and Jenkins are referenced (which are cross-platform), the examples and guidance are skewed toward Windows users, potentially creating friction for Linux/macOS users.
Recommendations
  • Add explicit Linux/macOS command-line examples for creating Service Fabric applications, such as using sfctl from bash or zsh.
  • Include sample shell scripts (e.g., install.sh) for parameter substitution and deployment on Linux/macOS.
  • Clarify which tools and scripts are cross-platform and provide parity guidance (e.g., alternatives to Deploy-FabricApplication.ps1 for Linux).
  • Reorder examples to present cross-platform or Linux/macOS options before or alongside Windows/PowerShell examples.
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-01 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: it references the Windows Server 2016 Container Sample as the basis for its examples, frequently mentions Windows-specific tools (such as 'winver' for OS build detection), and describes container volume mounts using Windows-style paths (e.g., 'c:\VolumeTest\Data'). There is no mention of Linux container samples, Linux path formats, or Linux-specific configuration patterns. While some notes acknowledge Linux (e.g., certificate handling differences), the examples and guidance are overwhelmingly Windows-centric.
Recommendations
  • Include equivalent Linux-based manifest examples, referencing the Linux container sample repository if available.
  • Show volume mount examples using Linux path formats (e.g., '/mnt/data') alongside Windows paths.
  • When describing OS build detection, mention the Linux equivalent (e.g., 'cat /etc/os-release' or 'uname -r') for determining OS version.
  • Clarify which manifest elements or features are cross-platform and which are Windows-only.
  • Provide links to Linux container documentation and samples in the introduction and feature tables.
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-01 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation provides comprehensive coverage of both Kestrel (cross-platform) and HTTP.sys (Windows-only) web servers for ASP.NET Core integration with Azure Service Fabric. However, there is a notable Windows bias in several areas: HTTP.sys (a Windows-only technology) is discussed in detail and presented first in some sections, with explicit mention that it only works on Windows. There are no explicit Linux/macOS-specific examples or troubleshooting notes, and some configuration patterns (such as Endpoint registration and port sharing) are described primarily in the context of Windows tools and APIs (e.g., netsh, HTTP.sys kernel driver). While Kestrel is recommended for cross-platform scenarios, Linux users may find the documentation less tailored to their environment, especially regarding ServiceManifest.xml configuration, port management, and deployment nuances.
Recommendations
  • Add explicit Linux/macOS examples for ServiceManifest.xml configuration, deployment, and troubleshooting (e.g., how to manage ports and firewall rules on Linux nodes).
  • Clearly separate Windows-only sections (HTTP.sys) from cross-platform guidance, and consider presenting Kestrel (cross-platform) examples before HTTP.sys (Windows-only) examples.
  • Include notes or links to Linux/macOS-specific Service Fabric documentation, especially for common tasks like endpoint configuration, port assignment, and debugging.
  • Where Windows tools (e.g., netsh) are mentioned, provide Linux/macOS equivalents or clarify that these steps are not required on non-Windows platforms.
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-01 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page for Replica soft delete in Service Fabric is heavily focused on PowerShell-based APIs and tools (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica), with no mention of Linux CLI equivalents or cross-platform usage patterns. All command and API examples reference PowerShell cmdlets, and there is no guidance for Linux/macOS users on how to perform these operations using Service Fabric CLI (sfctl) or REST APIs. This creates friction for non-Windows users, even though Service Fabric itself is cross-platform.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl) for all PowerShell cmdlets mentioned (e.g., remove replica, restore replica, get replica status).
  • Explicitly state whether the new APIs (such as Restore Replica) are available via sfctl or REST, and provide usage examples.
  • Clarify any platform limitations (if any) for these APIs, and if there are none, ensure Linux/macOS users are guided on how to perform the same tasks.
  • Where screenshots or command outputs are shown, include cross-platform examples or note any differences.
GitHub Create Pull Request
Service Fabric Reliable services app manifest examples ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-manifest-example-reliable-services-app.md
Medium Priority View Details →
Scanned: 2026-02-01 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page for Service Fabric reliable services app manifest examples demonstrates a moderate Windows bias. It references Windows-specific tools and patterns, such as .bat scripts for setup and mentions the ServiceFabric PowerShell module for service creation. The examples and explanations assume Windows conventions (e.g., NETWORKSERVICE account, .exe executables, .bat scripts) and do not provide Linux equivalents or guidance for cross-platform scenarios. Linux-specific details, such as shell script usage or Linux service accounts, are missing.
Recommendations
  • Add Linux-specific examples, such as using shell scripts (.sh) in SetupEntryPoint and EntryPoint, and explain how to configure working folders and permissions for Linux deployments.
  • Mention and provide examples for using Linux service accounts (e.g., 'sfuser') and clarify differences in account types and permissions between Windows and Linux clusters.
  • Reference Linux-compatible deployment tools (such as Azure CLI or Service Fabric CLI) alongside PowerShell, and provide command examples for both platforms.
  • Explicitly state which manifest elements and patterns are cross-platform, and note any Windows-only features or behaviors.
  • Where .exe or .bat files are referenced, include parallel examples for Linux (.sh, ELF binaries) and clarify platform-specific requirements.
GitHub Create Pull Request
Service Fabric Overview of Azure Service Fabric ...ain/articles/service-fabric/service-fabric-overview.md
Medium Priority View Details →
Scanned: 2026-02-01 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation mentions both Windows and Linux support for Service Fabric, but Windows development tools (Visual Studio, PowerShell, .NET SDK) are listed before Linux equivalents (Eclipse, Yeoman, Java SDK). The quickstart link points to a .NET/Windows-focused guide, and Windows development is described first. There are no explicit Linux examples or Linux-first instructions, and PowerShell is referenced as the main automation tool for Windows, with no Linux CLI or shell alternatives mentioned.
Recommendations
  • Present Windows and Linux development options in parallel, rather than listing Windows first.
  • Provide links to both Windows and Linux quickstart guides in the 'Next steps' section.
  • Mention Linux CLI tools (e.g., Bash, Azure CLI) alongside PowerShell for automation.
  • Include examples or references for both .NET and Java development paths, and clarify cross-platform support.
  • Ensure that Linux-specific documentation is as discoverable and detailed as Windows documentation.
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-01 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 'Networking patterns for Azure Service Fabric' demonstrates a Windows bias by exclusively providing PowerShell-based deployment instructions and examples, referencing Windows command-line patterns (e.g., RDP, C:\ paths, ping commands in Windows syntax), and omitting equivalent instructions for Linux/macOS users (such as Azure CLI or Bash). The examples and deployment workflows assume a Windows environment, which may create friction for users on other platforms.
Recommendations
  • Provide Azure CLI (az) command examples alongside PowerShell for all deployment steps, as Azure CLI is cross-platform.
  • Include Linux/macOS-specific notes for accessing VMs (e.g., using SSH instead of RDP, Linux ping syntax).
  • Clarify that Service Fabric clusters can be managed from Linux/macOS and link to relevant cross-platform tooling documentation.
  • Use generic file paths or show both Windows and Linux path formats in examples.
  • Explicitly state platform requirements or parity where applicable.
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-01 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 PowerShell examples for health reporting and cluster connection, but does not offer equivalent Linux/macOS CLI examples or mention cross-platform alternatives. PowerShell commands are shown first and exclusively for command-line usage, which may create friction for users on non-Windows platforms. REST and API methods are mentioned, but practical, platform-agnostic CLI examples are missing.
Recommendations
  • Add equivalent CLI examples using Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • Explicitly mention that PowerShell commands are for Windows and provide guidance for Linux/macOS users.
  • Reorder examples so that REST and CLI methods are presented before or alongside PowerShell, emphasizing cross-platform options.
  • Include notes or links to documentation for Service Fabric CLI installation and usage on Linux/macOS.
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-01 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-specific tools (Visual Studio and PowerShell) for configuring and upgrading Service Fabric applications. All examples and instructions reference Visual Studio dialogs and PowerShell cmdlets, with no mention of Linux/macOS alternatives or cross-platform CLI workflows. This creates friction for users on non-Windows platforms, as they are not provided guidance for performing upgrades outside of Windows environments.
Recommendations
  • Add equivalent instructions for upgrading Service Fabric applications using Azure CLI or Service Fabric CLI (sfctl), which are cross-platform.
  • Include examples of configuring upgrade parameters and health policies using command-line tools available on Linux/macOS.
  • Clarify which steps are Windows-only and provide links or references to Linux/macOS documentation where available.
  • If Visual Studio is required, explicitly state that these instructions are for Windows users and link to alternative workflows for other platforms.
GitHub Create Pull Request
Service Fabric Azure Service Fabric networking best practices ...ice-fabric/service-fabric-best-practices-networking.md
Medium Priority View Details →
Scanned: 2026-01-31 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 generally covers both Windows and Linux Service Fabric clusters, but there is a noticeable Windows bias in several areas. Windows/PowerShell tools and terminology are mentioned first or exclusively in some sections (e.g., Client API described as 'used by PowerShell', DevOps section references classic PowerShell tasks, and ARM template example is for Windows). Some operational examples and references (such as netsh commands, Patch Orchestration Application, and Windows container specifics) focus on Windows, with Linux equivalents either missing or less detailed. Linux-specific guidance is present but often secondary.
Recommendations
  • Provide Linux CLI (az, bash) examples alongside PowerShell commands where relevant, especially for networking and cluster management tasks.
  • Include ARM template samples for Linux clusters, or clarify differences in NSG setup for Linux clusters.
  • In sections referencing Windows tools (e.g., netsh, Patch Orchestration Application), add Linux equivalents or note if not applicable.
  • Balance the order of presentation so Linux and Windows are treated equally (e.g., mention both in parallel when describing features or requirements).
  • Clarify which recommendations or rules are Windows-only and which apply to Linux, to reduce ambiguity.
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-01-31 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 on-demand backup in Azure Service Fabric demonstrates a notable Windows bias. All command-line examples use PowerShell, and the prerequisite is to install a PowerShell module. There are no CLI, Bash, or Linux-native examples provided, nor is there guidance for running these operations from Linux/macOS environments. The documentation assumes the use of Windows tools and patterns throughout, which may create friction for Linux/macOS users managing Service Fabric clusters.
Recommendations
  • Provide equivalent examples using Azure CLI, Bash, or REST API calls with curl for Linux/macOS users.
  • Clarify whether the PowerShell module is required for all platforms, and if so, provide installation instructions for PowerShell Core on Linux/macOS.
  • Add notes or sections explicitly addressing how to perform these operations from non-Windows environments.
  • Where possible, show REST API usage with generic tools (e.g., curl, httpie) rather than only PowerShell's Invoke-WebRequest.
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-01-31 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Windows (ClusterManifest.xml, PowerShell) and cross-platform (ClusterConfig.json) configuration examples. However, Windows-centric formats and tools (XML manifests, PowerShell) are consistently presented first and in greater detail, with PowerShell being the only CLI example shown. There are no Linux shell or CLI examples, and the use of 'WindowsServer' in XML examples may cause confusion for Linux cluster operators.
Recommendations
  • Provide explicit Linux/Unix parity by including bash/CLI examples (e.g., using sfctl or REST API) alongside PowerShell for service creation and updates.
  • Clarify that ClusterConfig.json applies to both Windows and Linux standalone clusters, and provide examples or notes for Linux-specific scenarios if any differences exist.
  • When showing XML configuration, clarify if/when it is Windows-only, and provide equivalent Linux configuration steps if available.
  • Alternate the order of examples or explicitly state cross-platform applicability to avoid the impression that Windows is the default or only supported platform.
GitHub Create Pull Request
Service Fabric Advanced Application Upgrade Topics ...-fabric/service-fabric-application-upgrade-advanced.md
Medium Priority View Details →
Scanned: 2026-01-31 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page for advanced Service Fabric application upgrades is heavily focused on PowerShell-based workflows and examples, which are most relevant to Windows environments. All command-line examples use PowerShell cmdlets, and there is no mention of Linux CLI equivalents (such as Azure CLI, REST API, or Service Fabric CLI). The documentation assumes the reader is using Windows tooling, creating friction for Linux/macOS users who may need to perform similar upgrade operations.
Recommendations
  • Add equivalent examples using Azure CLI, Service Fabric CLI (sfctl), or REST API for common upgrade operations, especially for creating/updating services and managing upgrades.
  • Clearly indicate which commands are Windows-only and provide guidance for Linux/macOS users on alternative workflows.
  • Include links to cross-platform tooling documentation (e.g., sfctl, Azure CLI) in relevant sections.
  • Reorder or balance examples so that Windows and Linux workflows are presented with equal prominence.
GitHub Create Pull Request
Service Fabric Cluster Resource Manager - Management Integration ...fabric-cluster-resource-manager-management-integration.md
Medium Priority View Details →
Scanned: 2026-01-31 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides a detailed conceptual overview of Cluster Resource Manager integration with Service Fabric cluster management. However, the only command-line example shown uses PowerShell (Get-ServiceFabricPartitionHealth), with no equivalent CLI or Linux/macOS example provided. This may create friction for users managing Service Fabric clusters from non-Windows environments.
Recommendations
  • Include equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • Explicitly mention that the PowerShell example is for Windows, and provide alternative commands for Linux/macOS users.
  • Add a short section or note clarifying cross-platform management options for Service Fabric clusters.
GitHub Create Pull Request
Service Fabric Azure Service Fabric DNS service ...n/articles/service-fabric/service-fabric-dnsservice.md
Medium Priority View Details →
Scanned: 2026-01-31 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates several Windows biases: PowerShell is the only CLI example given for setting DNS names, and there are no Linux CLI (e.g., Bash, Azure CLI) equivalents. The ApplicationManifest.xml example implicitly assumes Visual Studio, a Windows-centric tool, and does not mention Linux development workflows. The limitations section notes Linux support is restricted, but the documentation does not provide Linux-specific guidance or parity for key tasks such as enabling DNS service or setting DNS names outside ARM templates. Windows tools and patterns are mentioned first or exclusively in several sections.
Recommendations
  • Add Linux CLI examples (e.g., Bash, Azure CLI, REST API) for tasks such as setting DNS names and enabling DNS service.
  • Clarify how Linux users can set DNS names for services, especially for non-containerized workloads (if/when supported).
  • Provide guidance for Linux development workflows, including alternatives to Visual Studio and ApplicationManifest.xml editing on Linux.
  • Explicitly state limitations for Linux and offer workarounds or links to Linux-specific documentation where possible.
  • Balance example ordering so that Linux and Windows approaches are presented equally.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Auto Scaling Services and Containers ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-autoscaling.md
Medium Priority View Details →
Scanned: 2026-01-31 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides code examples for configuring auto scaling in Azure Service Fabric using application manifests, C# APIs, and PowerShell. However, all command-line/script examples are exclusively in PowerShell, which is primarily a Windows tool. There are no equivalent examples for Linux/macOS users (e.g., Bash, CLI, or REST API). The documentation also presents PowerShell examples before mentioning Linux support, and does not clarify how Linux users should perform these tasks, despite Service Fabric supporting Linux containers.
Recommendations
  • Add equivalent examples using Azure CLI, Bash scripts, or REST API for configuring auto scaling policies, especially for Linux/macOS users.
  • Explicitly state which steps or tools are Windows-only and provide alternative instructions for Linux environments.
  • Reorder examples or provide parallel Windows and Linux instructions to avoid Windows-first bias.
  • Clarify if PowerShell Core (cross-platform) is supported, and if so, provide usage notes.
GitHub Create Pull Request
Service Fabric Azure Service Fabric standalone cluster scaling ...ce-fabric/service-fabric-cluster-scaling-standalone.md
Medium Priority View Details →
Scanned: 2026-01-31 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page on scaling Azure Service Fabric standalone clusters shows a notable Windows bias. It references PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) without mentioning Linux equivalents or cross-platform tooling. There are no examples or instructions for Linux environments, and the linked 'scale a standalone cluster' page is Windows Server-specific, further reinforcing the bias.
Recommendations
  • Add equivalent Linux instructions and examples, such as using Service Fabric CLI (sfctl) or REST APIs for cluster management tasks.
  • Clarify whether standalone clusters can be managed on Linux, and if so, provide guidance for Linux users.
  • Where PowerShell cmdlets are referenced, include alternative commands for Linux/macOS environments.
  • Explicitly state any platform limitations if standalone clusters are Windows-only, to avoid confusion.
GitHub Create Pull Request
Service Fabric Scalability of Service Fabric services .../service-fabric/service-fabric-concepts-scalability.md
Medium Priority View Details →
Scanned: 2026-01-31 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides code examples for scaling Service Fabric services using C# and PowerShell, but omits equivalent Linux CLI (sfctl) or bash examples. PowerShell is a Windows-centric tool, and its exclusive use in examples creates friction for Linux/macOS users. Additionally, the documentation references administrative actions primarily via PowerShell before mentioning programmatic APIs, reinforcing a Windows-first approach.
Recommendations
  • Add Linux CLI (sfctl) or bash examples alongside PowerShell for all administrative actions, such as creating or updating services.
  • Explicitly mention cross-platform management tools (e.g., sfctl, REST API) and provide usage examples.
  • Where PowerShell is referenced, clarify its platform limitations and direct Linux/macOS users to alternative tools.
  • Ensure that code samples and instructions are presented in a platform-neutral order, or grouped by platform.
GitHub Create Pull Request
Service Fabric Reliable services app manifest examples ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-manifest-example-reliable-services-app.md
Medium Priority View Details →
Scanned: 2026-01-31 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page for Service Fabric reliable services app manifest examples demonstrates a moderate Windows bias. Examples reference Windows tools and patterns (such as .bat scripts, EXE programs, and Windows account types like NetworkService and Administrators), and mention PowerShell as a way to create service instances. There are no explicit Linux equivalents or examples (e.g., shell scripts, Linux user/group patterns, or Linux-specific deployment notes), and Windows terminology appears first and exclusively throughout the manifest examples.
Recommendations
  • Add Linux-specific examples alongside Windows ones, such as using shell scripts (.sh) in SetupEntryPoint and EntryPoint, and referencing ELF binaries instead of only .exe files.
  • Document Linux-compatible account types and group patterns, clarifying how principals map to Linux environments (e.g., using 'root', 'nobody', or custom service users).
  • Include notes or sections on deploying Service Fabric applications on Linux clusters, highlighting any differences in manifest configuration, resource governance, or security policies.
  • When mentioning tools (e.g., PowerShell), also reference Linux alternatives (such as Azure CLI or Bash scripts) for creating service instances.
  • Clarify which features or manifest elements are cross-platform and which are Windows-only, to help users understand applicability.
GitHub Create Pull Request
Service Fabric Fault Analysis Service overview .../service-fabric/service-fabric-testability-overview.md
Medium Priority View Details →
Scanned: 2026-01-31 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides usage instructions for C# (via the Microsoft.ServiceFabric NuGet package) and PowerShell (via the Service Fabric SDK and PowerShell module), but does not mention or provide examples for Linux/macOS command-line tools or scripting environments. PowerShell is highlighted as the only CLI example, which is Windows-centric, and there are no references to Bash, CLI, or cross-platform alternatives.
Recommendations
  • Add examples for using the Fault Analysis Service from Linux/macOS environments, such as via Azure CLI, Bash scripts, or REST API calls.
  • Clarify whether PowerShell Core (cross-platform) is supported, and provide instructions if so.
  • If the Fault Analysis Service can be accessed via REST APIs, include sample curl commands or links to API documentation.
  • Explicitly state platform requirements and limitations for each usage method.
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-01-31 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation provides extensive coverage of both Kestrel (cross-platform) and HTTP.sys (Windows-only) web servers for ASP.NET Core integration with Azure Service Fabric. However, it gives detailed HTTP.sys examples and configuration steps (including references to Windows-only tools like netsh and Windows HTTP Server API) before clarifying that HTTP.sys is Windows-only. There are no explicit Linux/macOS development or deployment examples, and Windows-specific configuration steps (such as endpoint reservation) are described in detail, while Linux equivalents or considerations are omitted.
Recommendations
  • Add explicit Linux/macOS development and deployment examples, especially for Kestrel, to demonstrate parity and clarify platform-specific steps.
  • Clearly mark Windows-only sections (e.g., HTTP.sys) at the beginning, and provide alternative instructions for Linux users where applicable.
  • Include troubleshooting notes or configuration guidance for running Service Fabric Reliable Services with ASP.NET Core on Linux clusters.
  • Provide links or references to Service Fabric Linux documentation, and clarify any differences in endpoint configuration or port management on Linux.
  • When listing options, mention cross-platform (Kestrel) first, and make Windows-only options secondary.
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-01-31 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 demonstrates a moderate Windows bias. While it discusses Service Fabric's cross-platform certificate-based authentication, it consistently references Windows-specific tools, APIs, and patterns (e.g., certificate stores like LocalMachine\My, Win32 CryptoAPI, CAPI1/CNG providers, and Windows event logs) before or instead of Linux equivalents. Troubleshooting and configuration examples focus on Windows, with only brief or parenthetical mentions of Linux paths. There are no explicit Linux/macOS command-line examples or troubleshooting steps.
Recommendations
  • Add explicit Linux/macOS examples for certificate storage, retrieval, and troubleshooting (e.g., show how to locate certificates in /var/lib/sfcerts, use OpenSSL or Linux-native tools for diagnostics).
  • When referencing certificate stores, always mention both Windows and Linux equivalents side-by-side, not just as a parenthetical note.
  • Provide Linux/macOS-specific troubleshooting steps, such as relevant log file locations, commands to check certificate permissions, and how to manage private keys.
  • If referencing Windows APIs (e.g., CertGetCertificateChain), clarify the Linux equivalent or note if the behavior is abstracted in Service Fabric.
  • Include examples of how to create or rotate certificates using cross-platform tools (e.g., OpenSSL) rather than only referencing Windows certificate providers.
  • Mention any platform-specific limitations or differences explicitly, so Linux/macOS users are aware of what applies to them.
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-01-31 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page provides extensive PowerShell-based examples and references to Windows-specific tooling (such as the Key Vault VM extension for Windows and S-channel APIs). While the overall guidance is Azure-centric and Service Fabric clusters can run on both Windows and Linux, the hands-on examples, troubleshooting scripts, and extension documentation are almost exclusively Windows-focused. There is little to no mention of Linux equivalents, and Windows patterns/tools are presented first and in detail.
Recommendations
  • Add Linux-specific examples for certificate provisioning and management, such as using Azure CLI, Bash scripts, or Linux-compatible VM extensions.
  • Explicitly document any differences or limitations for Service Fabric clusters running on Linux nodes, especially regarding certificate autorollover and VM extensions.
  • Reference or link to Key Vault VM extension documentation for Linux, if available, and clarify any platform-specific behaviors (e.g., linking on renewal is Windows-only).
  • Provide troubleshooting steps and automation scripts using cross-platform tools (Azure CLI, REST API) alongside PowerShell.
  • Indicate clearly when a feature or example is Windows-only, and suggest Linux alternatives where possible.
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-01-31 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides a PowerShell-only command for bypassing Infrastructure Service throttling, with no equivalent example for Linux/macOS users. The use of PowerShell and Service Fabric Explorer (a Windows-centric tool) is presented without alternatives or parity for Linux environments, which may create friction for non-Windows users managing Service Fabric clusters.
Recommendations
  • Provide equivalent command-line instructions for Linux/macOS users, such as using Azure CLI, REST API, or Service Fabric CLI (sfctl) where possible.
  • Clarify whether the PowerShell command can be run from Azure Cloud Shell (which supports PowerShell and Bash) or if there are REST API alternatives.
  • Mention if Service Fabric Explorer is accessible via browser and platform-agnostic, or suggest alternatives for Linux users.
  • Add notes or links to cross-platform management tools for Service Fabric clusters.
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-01-31 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 examples and guidance that prioritize Azure PowerShell for cluster management tasks, with explicit links to PowerShell cmdlets for deleting, restarting, and reimaging node types. While Azure CLI and sfctl are mentioned in the utility table, the best practices section exclusively highlights PowerShell examples and does not provide equivalent Azure CLI or sfctl command examples, which are more commonly used on Linux/macOS. This creates friction for non-Windows users who may not use PowerShell.
Recommendations
  • Include Azure CLI and sfctl command examples alongside PowerShell in the best practices section for all major operations (delete, restart, reimage).
  • Clarify that Azure CLI and sfctl are cross-platform and suitable for Linux/macOS users.
  • Reorder examples so that cross-platform tools (Azure CLI, sfctl) are presented before or alongside PowerShell, rather than PowerShell-only examples.
  • Add explicit guidance for Linux/macOS users on how to perform these tasks without PowerShell.
GitHub Create Pull Request
← Previous Page 85 of 99 Next →