Service Fabric

810
Total Pages
600
Linux-Friendly Pages
210
Pages with Bias
25.9%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

718 issues found
Showing 476-500 of 718 flagged pages
Service Fabric Set up monitoring with Azure Monitor logs ...service-fabric/service-fabric-diagnostics-oms-setup.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. Windows clusters and tools (Service Fabric Analytics, WAD, PowerShell) are mentioned first and in detail, with step-by-step instructions and code samples. Linux clusters are referenced only in notes or as links to separate articles, with no direct examples or walkthroughs. All command-line examples use PowerShell, and Windows-specific tooling (WAD, Service Fabric Analytics) is emphasized, while Linux equivalents (OMS Syslog, Linux agent setup) are not described or shown.
Recommendations
  • Provide parallel Linux examples and walkthroughs directly in this page, not just as external links.
  • Include command-line instructions using Bash/CLI for Linux users, alongside PowerShell.
  • Clarify which steps are Windows-only and offer Linux alternatives where possible.
  • Describe Linux-specific tools and patterns (e.g., OMS Syslog, Linux diagnostics agent) with equal detail.
  • Ensure sample templates and code snippets are available for both Windows and Linux clusters.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Diagnose Common Scenarios ...-fabric/service-fabric-diagnostics-common-scenarios.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias, primarily by listing Windows performance counters and examples first, referencing Windows-specific counter formats, and providing more detailed examples for Windows than Linux. Linux is mentioned as an alternative in some places, but Linux-specific examples, counter formats, and troubleshooting steps are not provided. The documentation assumes familiarity with Windows tools and patterns, which may create friction for Linux/macOS users.
Recommendations
  • Provide Linux-specific examples for performance counters, including typical Linux counter names and formats.
  • Include screenshots or walkthroughs from Linux environments (e.g., Azure portal views for Linux clusters).
  • Clarify any differences in setup or troubleshooting steps for Linux clusters, especially where agent configuration or counter collection differs.
  • List Linux options and examples before or alongside Windows ones, rather than after.
  • Explicitly mention macOS where relevant, or clarify if steps apply equally to macOS.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Event Aggregation with EventFlow ...service-fabric-diagnostics-event-aggregation-eventflow.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Visual Studio and its Solution Explorer for NuGet package management, and by instructing users to observe the Debug output window in Visual Studio for verification. There are no instructions or examples for Linux/macOS users, such as using the dotnet CLI for package management or alternative methods for log verification. The documentation assumes a Windows development environment and omits guidance for cross-platform scenarios.
Recommendations
  • Add instructions for installing EventFlow NuGet packages using the dotnet CLI (e.g., 'dotnet add package') for Linux/macOS users.
  • Include guidance on editing and placing configuration files using cross-platform tools and editors.
  • Provide verification steps that do not rely on Visual Studio, such as using command-line tools or viewing logs in the terminal.
  • Explicitly mention that Service Fabric development can be performed on Linux/macOS and link to relevant cross-platform setup guides.
  • Present examples and instructions for both Windows and Linux/macOS environments, or clearly indicate when steps are Windows-specific.
GitHub Create Pull Request
Service Fabric Performance monitoring with Azure Diagnostics .../service-fabric/service-fabric-diagnostics-perf-wad.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily focused on Windows clusters, specifically using the Windows Azure Diagnostics (WAD) extension and ARM templates with Windows performance counters. Linux clusters are mentioned only briefly, with a link to a separate page for Log Analytics agent setup, and no Linux-specific configuration or counter examples are provided. All code samples and deployment instructions (e.g., PowerShell commands) are Windows-centric, with no equivalent Linux or cross-platform guidance.
Recommendations
  • Add parallel Linux-specific examples for performance counter collection, including sample configuration for the Log Analytics agent.
  • Include Linux performance counter specifiers and typical metrics relevant to Service Fabric on Linux.
  • Provide deployment instructions using Azure CLI or other cross-platform tools, not just PowerShell.
  • Clearly separate Windows and Linux workflows, or provide a unified table comparing both approaches.
  • Reference Linux documentation and tools earlier and more prominently, not just as a side note.
GitHub Create Pull Request
Service Fabric Azure Service Fabric disaster recovery ...les/service-fabric/service-fabric-disaster-recovery.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation page demonstrates moderate Windows bias. It references Windows-specific tools and APIs (such as Repair-ServiceFabricPartition PowerShell cmdlet and .NET APIs), links to Windows Server setup for standalone clusters, and omits explicit Linux or cross-platform command-line examples. Windows terminology and tools are mentioned before or instead of Linux equivalents, and there is no guidance for Linux users on how to perform equivalent operations (e.g., troubleshooting, cluster creation, recovery).
Recommendations
  • Add Linux-specific examples and instructions for key operations, such as partition repair, cluster creation, and troubleshooting.
  • Reference cross-platform Service Fabric tools (e.g., Service Fabric CLI) and provide parity in examples for both Windows and Linux environments.
  • Clarify which APIs and commands are available on Linux and macOS, and provide alternatives where necessary.
  • Include links to Linux cluster setup documentation alongside Windows Server references.
  • Explicitly mention support and limitations for Linux-based Service Fabric clusters in relevant sections.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Docker Compose Deployment Preview ...ticles/service-fabric/service-fabric-docker-compose.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page presents PowerShell-based deployment instructions first and in greater detail, with multiple example commands for creating, managing, upgrading, and rolling back Docker Compose deployments on Azure Service Fabric. PowerShell is a Windows-centric tool, and its prominence suggests a Windows-first approach. While the Service Fabric CLI (sfctl), which is cross-platform, is mentioned as an alternative, it is introduced only after the PowerShell section. There are no explicit Linux/macOS shell examples (e.g., Bash), nor is there guidance for Linux-specific scenarios or troubleshooting. The mention of 'Isolation (only for Windows)' in supported Compose directives further highlights Windows-specific features.
Recommendations
  • Present CLI (sfctl) instructions before or alongside PowerShell examples to emphasize cross-platform support.
  • Include explicit Linux/macOS shell examples and troubleshooting notes for non-Windows environments.
  • Clarify which tools are supported on which platforms, and provide installation/setup guidance for Linux/macOS users.
  • Highlight any platform-specific limitations or differences (e.g., 'Isolation' only for Windows) in a dedicated section.
  • Ensure parity in example depth and coverage for both PowerShell and CLI instructions.
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-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation exhibits a moderate Windows bias. Windows support is broader and described first, with Linux limitations emphasized. PowerShell is the only CLI example for setting DNS names, with no Linux CLI (e.g., Bash, Azure CLI) alternatives. Visual Studio is mentioned for editing manifests, a Windows-centric tool. Enabling DNS service via Azure portal is only available for Windows clusters, with Linux users required to use ARM templates, but no Linux-specific guidance or examples are provided.
Recommendations
  • Add Linux-specific instructions and examples for enabling DNS service, including ARM template steps tailored for Linux clusters.
  • Provide CLI examples for Linux users, such as Azure CLI, Bash, or REST API commands, for setting DNS names and managing services.
  • Mention cross-platform editors (e.g., VS Code) alongside Visual Studio for editing manifests.
  • Clarify any differences in service deployment and management for Linux clusters, and provide troubleshooting steps for common Linux issues.
  • Ensure examples and screenshots are relevant to both Windows and Linux environments, or clearly label them as platform-specific.
GitHub Create Pull Request
Service Fabric Enable disk encryption for Linux clusters ...c/service-fabric-enable-azure-disk-encryption-linux.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page for enabling disk encryption for Linux clusters in Azure Service Fabric exhibits several Windows-centric biases. PowerShell commands are presented first and in greater detail, with explicit references to Windows file paths (e.g., 'c:\certificates'), and the use of PowerShell-specific cmdlets throughout. Azure CLI examples are provided, but often as secondary or 'equivalent' commands, and they also use Windows-style paths. There is minimal coverage of Linux-native tooling or shell scripting, and no examples using bash or Linux file system conventions. The documentation assumes familiarity with PowerShell and Windows patterns, which may create friction for Linux/macOS users.
Recommendations
  • Provide Linux-first examples, using bash shell and Linux file paths (e.g., '/home/user/certificates') in CLI commands.
  • Include step-by-step instructions for Linux environments, such as certificate generation using OpenSSL and file management in Linux.
  • Avoid presenting PowerShell commands before CLI or bash examples; alternate or parallelize examples for both platforms.
  • Clarify which commands are platform-agnostic (Azure CLI) and which are Windows-specific (PowerShell), and recommend CLI for cross-platform use.
  • Add notes or sections for Linux/macOS users highlighting any differences or additional steps required.
  • Remove or supplement Windows-specific references (e.g., 'c:\templates') with Linux equivalents.
GitHub Create Pull Request
Service Fabric Package an existing executable to Azure Service Fabric ...abric/service-fabric-guest-executables-introduction.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows file paths (e.g., C:\Program Files\...), mentioning Visual Studio as a primary tool, and omitting explicit Linux/macOS equivalents or examples. There are no instructions or examples for packaging or deploying guest executables from Linux/macOS environments, nor are alternative tools or directory paths mentioned for non-Windows platforms.
Recommendations
  • Add explicit instructions and examples for Linux/macOS users, including command-line utilities and directory paths.
  • Mention cross-platform tools (such as Azure CLI, Service Fabric CLI) and provide parity in examples for both Windows and Linux/macOS.
  • Reference the location of schema files or SDK installation paths for Linux/macOS, not just Windows.
  • Include sample workflows for packaging and deploying guest executables using Linux/macOS environments.
  • Clarify whether Visual Studio is required or if alternatives exist for non-Windows platforms.
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-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides a detailed conceptual overview of Service Fabric health monitoring, but the only concrete example of interacting with the health system uses PowerShell cmdlets, which are Windows-centric. There are no equivalent examples for Linux/macOS users (e.g., using REST API, CLI, or SDKs), and PowerShell is presented as the default/primary method for reporting and querying health. This creates friction for users running Service Fabric clusters on Linux or managing them from non-Windows environments.
Recommendations
  • Add equivalent examples using cross-platform tools, such as Azure CLI, REST API, or SDKs (e.g., Python, .NET Core) for reporting and querying health.
  • Explicitly mention Linux/macOS support and provide guidance for those platforms where relevant.
  • Reorder or supplement examples so that Windows/PowerShell is not presented as the only or primary method.
  • Link to documentation or guides for Linux-based Service Fabric cluster management.
GitHub Create Pull Request
Service Fabric Azure Service Fabric hosting model ...rticles/service-fabric/service-fabric-hosting-model.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing PowerShell as the only command-line example for service creation and management, referencing Windows-centric tools and cmdlets throughout. There is no mention of Linux equivalents (such as Azure CLI, Bash, or cross-platform tools), and PowerShell is presented as the primary or sole method for operational tasks. This may create friction for Linux/macOS users who do not use PowerShell or Windows tools.
Recommendations
  • Add equivalent Linux/macOS command-line examples using Azure CLI, Bash, or REST API calls.
  • Explicitly mention cross-platform management options and tools, and provide links to relevant documentation.
  • Clarify which tools are available on which platforms, and avoid presenting Windows/PowerShell as the default or only option.
  • Where PowerShell is referenced, also show how to perform the same operation using REST API, Azure CLI, or SDKs on Linux/macOS.
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-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. It references PowerShell and Visual Studio as primary tools for interacting with Service Fabric clusters, both of which are traditionally Windows-centric. The 'Next steps' section links only to PowerShell-based deployment instructions, and there are no explicit examples or guidance for Linux or macOS users (e.g., using Bash, CLI, or cross-platform tools). The documentation mentions .NET and REST APIs as alternatives for retrieving cluster manifests, but these are listed after PowerShell and without concrete Linux/macOS usage examples.
Recommendations
  • Add explicit examples for Linux/macOS users, such as using Azure CLI or Bash scripts to interact with Service Fabric clusters.
  • Include links to cross-platform deployment guides alongside PowerShell instructions in the 'Next steps' section.
  • Mention and demonstrate how to retrieve and configure the ImageStoreConnectionString using tools available on Linux/macOS.
  • Clarify whether Visual Studio is required or if alternatives (e.g., VS Code, command-line tools) are supported for non-Windows environments.
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-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples and tools (New-ServiceFabricApplication, Deploy-FabricApplication.ps1) are mentioned first and in more detail, with Visual Studio workflows highlighted. Linux alternatives (sfctl, install.sh) are referenced but receive less explanation and are not shown first. There is a heavier emphasis on Windows-centric tools and patterns, which may create friction for Linux/macOS users.
Recommendations
  • Present Linux/macOS tools (sfctl, install.sh) before or alongside Windows/PowerShell examples.
  • Provide equivalent step-by-step examples for Linux/macOS users, including shell commands and scripts.
  • Expand on Linux/macOS workflows, such as using sfctl and shell scripts, with clear instructions and parity with Windows examples.
  • Mention cross-platform editors and deployment tools, not just Visual Studio.
  • Clarify which steps or tools are platform-specific and offer alternatives where needed.
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-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows bias by referencing the Windows Server 2016 Container Sample as the basis for its examples, using Windows-specific paths (e.g., 'c:\VolumeTest\Data'), and mentioning Windows tools (e.g., 'winver' command) for OS build detection. The certificate import section describes Windows behavior first and in more detail, while Linux is mentioned only as an aside. There are no explicit Linux container manifest examples, nor are Linux-specific patterns or tools discussed. The examples and explanations are tailored to Windows environments, with Linux support implied but not demonstrated.
Recommendations
  • Include explicit Linux-based container manifest examples, such as referencing Ubuntu or other Linux container samples.
  • Provide Linux-specific instructions for tasks like OS build detection (e.g., using 'uname -a' or '/etc/os-release').
  • Show Linux file system paths (e.g., '/mnt/VolumeTest/Data') in volume binding examples.
  • Describe certificate handling in Linux with equal detail, including how PEM files are managed and accessed.
  • Balance explanations so that Linux and Windows behaviors are presented side-by-side, rather than Windows-first.
  • Reference Linux container images and registry authentication patterns where applicable.
GitHub Create Pull Request
Service Fabric Start and stop cluster nodes .../service-fabric/service-fabric-node-transition-apis.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell cmdlets alongside managed API calls, but does not mention or provide examples for Linux or macOS command-line usage. All sample code is in C#, which is cross-platform, but there are no bash, CLI, or Linux-native instructions. Windows/PowerShell tools are mentioned first and exclusively, with no Linux equivalents or parity.
Recommendations
  • Add equivalent examples using Azure CLI or bash scripts for Linux/macOS users.
  • Reference Linux-compatible Service Fabric tools (e.g., sfctl) where PowerShell cmdlets are mentioned.
  • Explicitly state cross-platform support and provide guidance for Linux/macOS environments.
  • Reorder documentation to present cross-platform or Linux examples alongside or before Windows/PowerShell examples.
GitHub Create Pull Request
Service Fabric Package an Azure Service Fabric app ...articles/service-fabric/service-fabric-package-apps.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias: all directory listing examples use Windows 'tree' command syntax, all command-line packaging and validation examples use PowerShell and Windows paths, and only Windows tools (Visual Studio, msbuild.exe, PowerShell cmdlets) are mentioned. There are no Linux/macOS equivalents, nor are cross-platform alternatives or instructions provided. This creates friction for non-Windows users attempting to package and validate Service Fabric applications.
Recommendations
  • Add Linux/macOS equivalents for directory listing (e.g., 'ls -R' or 'tree' on Linux).
  • Provide examples using Bash or cross-platform .NET CLI tools where possible.
  • Document how to package and validate Service Fabric applications on Linux/macOS, including any required tools or scripts.
  • Clarify which steps are Windows-only and suggest alternatives or workarounds for Linux/macOS.
  • Mention cross-platform editors (e.g., VS Code) and build tools (e.g., dotnet CLI) where applicable.
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-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates a Windows bias in several ways: it references Windows-specific tools and concepts (such as ServiceFabric PowerShell module, .bat scripts, EXE files, and Windows account types like NetworkService and Administrators), and examples are tailored to Windows environments (e.g., Setup.bat, VotingWeb.exe). There is no mention of Linux equivalents, nor are Linux/macOS-specific patterns or examples provided. The documentation assumes familiarity with Windows conventions and omits guidance for Linux deployments.
Recommendations
  • Add Linux/macOS-specific examples, such as using shell scripts (.sh) instead of batch files (.bat), and ELF binaries instead of .exe.
  • Document how Service Fabric manifests and policies map to Linux environments, including supported account types and security principals.
  • Reference Linux-native tools and deployment patterns, and clarify any differences in resource governance, endpoint configuration, and user/group management.
  • Explicitly state platform compatibility for each feature and example, and provide parity in guidance for both Windows and Linux clusters.
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-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias. All deployment and management command-line examples use PowerShell, with no mention of Azure CLI, Bash, or Linux/macOS-compatible workflows. Windows tools (PowerShell, RDP, Windows-style paths) are referenced exclusively and shown first, while Linux equivalents (SSH, Azure CLI, Bash) are absent. This creates friction for Linux/macOS users who cannot directly use the provided examples and must translate them to their environment.
Recommendations
  • Add Azure CLI and Bash examples alongside PowerShell for all deployment steps.
  • Include Linux/macOS-compatible instructions for accessing VMs (e.g., SSH instead of RDP).
  • Use platform-neutral file paths in examples, or show both Windows and Linux paths.
  • Explicitly state cross-platform support and link to relevant Azure CLI documentation.
  • Provide guidance for Linux users on prerequisites and environment setup.
GitHub Create Pull Request
Service Fabric Specifying Service Fabric service endpoints ...ce-fabric/service-fabric-service-manifest-resources.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page exhibits Windows bias primarily through the use of Windows-specific tooling and examples. The only explicit deployment example uses PowerShell (New-ServiceFabricApplication), and the Service Fabric SDK schema path is given only in Windows format. Linux-specific details are minimal and appear later in the document, such as the mention of the certificate store location. There are no Linux CLI or deployment examples, and Windows tools and patterns are referenced before their Linux equivalents (if any).
Recommendations
  • Provide equivalent Linux/macOS deployment examples using Azure CLI or Service Fabric CLI (sfctl), alongside PowerShell examples.
  • Mention Linux file paths and tooling (e.g., where the ServiceManifest schema is located on Linux) alongside Windows paths.
  • Clarify cross-platform differences in endpoint configuration and certificate management earlier in the document.
  • Add explicit notes or sections for Linux/macOS users, especially for steps that differ from Windows.
  • Ensure that all code snippets and instructions are platform-neutral or provide alternatives for each platform.
GitHub Create Pull Request
Service Fabric Change ReliableDictionaryActorStateProvider settings ...e-actors-reliabledictionarystateprovider-configuration.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits several Windows-centric biases. It references Visual Studio and its solution structure as the default workflow for configuration, mentions the Get-ServiceFabricClusterManifest PowerShell command as the way to view the cluster manifest, and uses Windows-style file paths (e.g., f:\SharedLog.Log) in examples. Linux-specific instructions are minimal, limited to a note about PEM-formatted certificates, and there are no Linux/macOS equivalents for key tasks such as viewing the cluster manifest or configuring the environment outside Visual Studio. No Linux/macOS configuration file locations, tools, or command-line examples are provided.
Recommendations
  • Provide Linux/macOS equivalents for all Windows-specific commands, such as how to view the cluster manifest (e.g., using sfctl or direct file access).
  • Include Linux/macOS file path examples alongside Windows paths in configuration samples.
  • Describe how to locate and edit configuration files when not using Visual Studio, such as with cross-platform editors or command-line tools.
  • Add explicit Linux/macOS workflow steps for configuring ReliableDictionaryActorStateProvider, including where files are located and how to deploy changes.
  • Ensure parity in security configuration examples, showing both Windows and Linux certificate handling.
GitHub Create Pull Request
Service Fabric Reliable Collection object serialization ...c-reliable-services-reliable-collections-serialization.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. In the 'Next steps' section, upgrade tutorials are provided for Visual Studio and PowerShell—both Windows-centric tools—without mention of Linux/macOS alternatives or cross-platform CLI options. No Linux-specific instructions, examples, or tooling are referenced, and Windows tools are listed before any potential alternatives. The main content does not reference platform-specific code, but the guidance and linked resources favor Windows environments.
Recommendations
  • Add equivalent upgrade tutorials for Linux/macOS users, such as using Azure CLI or Service Fabric CLI (sfctl).
  • Include references to cross-platform tools and workflows in the 'Next steps' section.
  • Ensure that examples and linked resources cover both Windows and Linux environments, or explicitly state platform requirements.
  • Where PowerShell is mentioned, also mention Bash or other Linux shell alternatives if available.
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-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias. PowerShell is the only CLI example provided, and all command-line snippets use Windows paths and conventions (e.g., 'PS C:\>'). There is no mention of Linux or macOS equivalents, nor are cross-platform CLI tools or shell examples (such as Bash or Azure CLI) provided. The use of PowerShell cmdlets and Windows-centric terminology appears before REST or API options, and there is no guidance for users running Service Fabric on Linux clusters or accessing the health reporting features from non-Windows environments.
Recommendations
  • Add equivalent examples using Bash or shell commands for Linux/macOS environments.
  • Include Azure CLI or cross-platform CLI examples for health reporting.
  • Explicitly mention how Linux-based Service Fabric clusters can report health, including any differences in tooling or authentication.
  • Reorder sections so REST and API examples are presented before or alongside PowerShell, emphasizing platform neutrality.
  • Clarify which commands and tools are Windows-only and provide alternatives for other platforms.
GitHub Create Pull Request
Service Fabric Change FabricTransport settings ...service-fabric-reliable-actors-fabrictransportsettings.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias by exclusively referencing Windows certificate store concepts (e.g., 'LocalMachine', 'My'), using Windows-centric certificate naming conventions (e.g., 'WinFabric-Test-SAN1-Alice'), and omitting concrete Linux configuration examples. Although there is a brief mention that Linux nodes require PEM-formatted certificates and a link to Linux certificate configuration, all XML configuration samples and parameter values are tailored to Windows environments, with no Linux equivalents or guidance on Linux-specific settings (such as file paths, store locations, or certificate handling patterns).
Recommendations
  • Add explicit XML configuration examples for Linux, showing how to specify PEM file paths and relevant parameters.
  • Document Linux-specific values for parameters like CertificateStoreLocation and CertificateStoreName, or clarify which parameters are ignored on Linux.
  • Provide sample certificate naming conventions and common names for Linux environments.
  • Include a table comparing Windows and Linux configuration differences for FabricTransport security settings.
  • Reference Linux tools or commands for certificate management alongside Windows concepts.
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-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example Powershell Heavy
Summary
The documentation demonstrates a moderate Windows bias, primarily through its extensive focus on HTTP.sys, a Windows-only web server, and references to Windows-specific tools (e.g., netsh). HTTP.sys is described in detail, with code samples and configuration guidance, but it is explicitly stated to be unavailable on Linux. While Kestrel, the cross-platform web server, is also covered and recommended for Linux, the documentation gives HTTP.sys significant attention and places Windows-specific instructions before Linux alternatives. There are no Linux/macOS-specific configuration or troubleshooting examples, and Windows tools are referenced without Linux equivalents.
Recommendations
  • Add explicit Linux/macOS sections or examples, especially for endpoint configuration and troubleshooting.
  • Where Windows tools (e.g., netsh) are mentioned, provide Linux/macOS alternatives or clarify that they are not needed for Kestrel.
  • Reorder sections so that cross-platform solutions (Kestrel) are presented before Windows-only solutions (HTTP.sys).
  • Include notes or tables summarizing platform compatibility for each approach.
  • Add troubleshooting guidance for Linux/macOS environments, including common issues and solutions.
  • Clarify in all configuration examples which are Windows-only and which are cross-platform.
GitHub Create Pull Request
Service Fabric Secure service remoting communications with C# ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-reliable-services-secure-communication.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page focuses exclusively on securing service remoting communications for C# services, with all code samples and configuration instructions tailored to Windows environments. Windows certificate store concepts (StoreLocation, StoreName) are used throughout, and there are no Linux-specific code examples or configuration patterns for C# on Linux. Linux is only mentioned in passing regarding certificate file location, with no parity in code or workflow examples.
Recommendations
  • Provide C# code examples and configuration instructions for Linux environments, including how to reference PEM certificates and any differences in API usage or deployment.
  • Include explicit Linux/macOS setup steps for certificate management, such as how to generate, store, and reference certificates in the Service Fabric cluster.
  • Clarify which settings or APIs are platform-specific and offer alternatives or notes for cross-platform compatibility.
  • Present examples for both Windows and Linux side-by-side, or clearly indicate platform differences in each step.
GitHub Create Pull Request
← Previous Page 20 of 29 Next →