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 226-250 of 718 flagged pages
Service Fabric Cluster Resource Manager - Management Integration ...fabric-cluster-resource-manager-management-integration.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides a PowerShell example (Get-ServiceFabricPartitionHealth) for querying health reports but does not include equivalent examples for Linux/macOS users (e.g., using sfctl or REST API). The only concrete command-line example is Windows/PowerShell-specific, which may create friction for users managing Service Fabric clusters from non-Windows environments.
Recommendations
  • Add equivalent Linux/macOS examples using sfctl (the Service Fabric CLI) or REST API calls alongside PowerShell examples.
  • Explicitly mention cross-platform management options and link to relevant documentation for Linux/macOS users.
  • When showing command-line examples, provide both PowerShell and sfctl/REST API versions to ensure parity.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager - Application Groups ...ice-fabric-cluster-resource-manager-application-groups.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides command-line examples exclusively using PowerShell cmdlets (e.g., New-ServiceFabricApplication, Update-ServiceFabricApplication, Get-ServiceFabricApplicationLoadInformation) and C# APIs. There are no examples for Linux/macOS users, such as using Azure CLI, REST API, or cross-platform tools. This creates friction for users managing Service Fabric clusters from non-Windows environments.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform.
  • Mention and link to REST API documentation for users who may wish to automate via HTTP.
  • Explicitly state if certain management operations are only possible via PowerShell or C# SDK, and if so, clarify the platform requirements.
  • If PowerShell Core (pwsh) is supported cross-platform, clarify this and provide guidance for Linux/macOS users.
  • Consider adding a section summarizing cross-platform management options for Service Fabric clusters.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation provides configuration examples for both Windows (ClusterManifest.xml) and cross-platform/standalone (ClusterConfig.json), but Windows-specific XML examples and references (e.g., <WindowsServer> element) are consistently presented first and more prominently. PowerShell examples are included, but there are no Linux shell or CLI equivalents. The documentation does not mention Linux-specific tools or patterns, nor does it clarify Linux/macOS parity for local development clusters or standalone deployments.
Recommendations
  • Present Linux/cross-platform examples (ClusterConfig.json) before or alongside Windows (ClusterManifest.xml) examples to avoid Windows-first bias.
  • Include Azure Service Fabric CLI (sfctl) or REST API examples for service creation and updates, which are cross-platform, instead of only PowerShell and C#.
  • Clarify whether standalone Service Fabric clusters can be run on Linux, and if so, provide explicit Linux/macOS guidance and examples.
  • Add notes or sections highlighting any differences or limitations for Linux/macOS users, especially for local development clusters.
  • Where possible, provide bash or shell script equivalents for PowerShell commands.
GitHub Create Pull Request
Service Fabric Manage Azure Service Fabric app load using metrics ...ric/service-fabric-cluster-resource-manager-metrics.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides code examples for C# and PowerShell, with PowerShell being the only CLI example shown. There are no Linux/macOS CLI equivalents (such as Azure CLI or Bash scripts), and PowerShell is presented before any mention of cross-platform tools. This creates friction for Linux/macOS users who may not use PowerShell or develop on Windows.
Recommendations
  • Add Azure CLI examples for service creation and metric configuration, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include Bash script examples or reference how to use REST APIs for metric management, which are platform-agnostic.
  • Clarify whether PowerShell examples are usable on PowerShell Core (cross-platform) or are Windows-only.
  • Consider providing sample YAML for ARM templates or Bicep for resource deployment, which are platform-neutral.
  • Explicitly mention any limitations or differences for Linux-based Service Fabric clusters, if applicable.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager: Movement cost ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-movement-cost.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides PowerShell and C# examples for configuring Service Fabric move cost, but does not include equivalent Linux/bash/CLI examples. PowerShell is a Windows-centric tool, and the lack of Azure CLI or REST API examples creates friction for Linux/macOS users. The configuration file examples (ClusterManifest.xml, ClusterConfig.json) are platform-neutral, but the operational examples are Windows-focused.
Recommendations
  • Add Azure CLI examples for creating and updating Service Fabric services with move cost settings.
  • If possible, include REST API examples for move cost operations.
  • Clarify whether PowerShell examples can be run cross-platform (e.g., with PowerShell Core on Linux/macOS), or provide bash equivalents.
  • Explicitly mention if certain operations are only supported via PowerShell or C# SDK, and provide guidance for Linux users.
GitHub Create Pull Request
Service Fabric Service sensitivity ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-sensitivity.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides configuration examples using XML, JSON, PowerShell, and C# APIs. However, all command-line examples for dynamic configuration use PowerShell, which is Windows-centric. There are no CLI or script examples for Linux/macOS users, such as Azure CLI, Bash, or REST API equivalents. This creates friction for non-Windows users wishing to automate or script these operations.
Recommendations
  • Add equivalent Azure CLI or REST API examples for creating and updating service sensitivity and maximum load, as these are cross-platform.
  • If PowerShell is required due to Service Fabric SDK limitations, explicitly state this and provide guidance for Linux users (e.g., using Azure CLI, REST, or Service Fabric CLI if available).
  • Consider including Bash or shell script examples for configuration file edits, or reference cross-platform tools where possible.
  • Clarify in the documentation if certain APIs or tools are only available on Windows, and suggest alternatives for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Azure Service Fabric application resource model ...ervice-fabric/service-fabric-concept-resource-model.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation for the Azure Service Fabric application resource model demonstrates a notable Windows bias. All command-line deployment and resource management examples use PowerShell cmdlets (e.g., New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) without providing Azure CLI equivalents. The application packaging workflow is shown using Visual Studio, a Windows-centric tool, with no mention of cross-platform alternatives. There are no Linux/macOS-specific instructions or examples, and Windows tools and patterns are presented exclusively and first.
Recommendations
  • Add Azure CLI examples for all PowerShell cmdlets used (e.g., az deployment group create, az resource delete).
  • Include instructions for packaging Service Fabric applications using cross-platform tools (e.g., dotnet CLI, SFCTL, or manual packaging via scripts).
  • Mention or provide examples for using VS Code or other cross-platform editors for application packaging.
  • Explicitly state that the steps can be performed on Linux/macOS where applicable, or clarify any Windows-only requirements.
  • Reorder or parallelize examples so that both Windows and Linux/macOS users see relevant 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-02-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides PowerShell examples for setting DNS names but does not offer equivalent Linux CLI (e.g., Bash, Azure CLI) examples. Windows tools and patterns (PowerShell, ApplicationManifest.xml/Visual Studio) are mentioned before Linux alternatives, and Linux-specific limitations are highlighted without guidance for Linux users. There are no Linux-native command examples or instructions for Linux users to accomplish the same tasks.
Recommendations
  • Add Azure CLI or Bash examples for setting DNS names and managing services, especially for Linux clusters.
  • Clarify how Linux users can set DNS names (e.g., via ARM templates, Azure CLI) and manage Service Fabric services without PowerShell.
  • Provide guidance or links for Linux users to accomplish tasks that are shown with Windows tools (e.g., ApplicationManifest.xml editing, PowerShell commands).
  • Explicitly state any differences in workflow for Linux users and offer alternatives where portal or Windows tools are not available.
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-02-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates moderate Windows bias. It references Windows file paths (e.g., 'C:\Program Files\Microsoft SDKs\Service Fabric\schemas\ServiceFabricServiceModel.xsd'), and does not provide equivalent Linux/macOS paths or instructions. The examples and directory structures use Windows conventions (e.g., .exe files), and there is no mention of Linux packaging, deployment, or cross-platform tooling. Visual Studio is mentioned as a packaging tool, but no Linux alternatives (such as CLI tools or cross-platform editors) are discussed. No PowerShell-specific commands are present, but Windows-centric patterns are evident.
Recommendations
  • Add Linux/macOS equivalents for file paths and SDK installation locations.
  • Provide examples using Linux executables (e.g., ELF binaries) and directory structures.
  • Mention and document cross-platform command-line tools for packaging and deploying guest executables.
  • Clarify whether Service Fabric supports Linux guest executables and, if so, provide guidance for Linux users.
  • Include instructions for using editors and tools available on Linux/macOS, not just Visual Studio.
GitHub Create Pull Request
Service Fabric Scalability of Service Fabric services .../service-fabric/service-fabric-concepts-scalability.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides code examples for scaling Service Fabric services using C# and PowerShell, but does not include equivalent Linux CLI (e.g., Bash with sfctl) examples. PowerShell and Windows-centric tools are referenced exclusively for command-line operations, creating friction for Linux users. There is a brief mention of platform differences, but practical Linux usage is not demonstrated.
Recommendations
  • Add examples using sfctl (Service Fabric CLI), which is cross-platform and works on Linux/macOS, alongside PowerShell examples.
  • Explicitly mention Linux-compatible tools and commands where administrative actions are discussed.
  • Where PowerShell cmdlets are referenced (e.g., New-ServiceFabricService, Update-ServiceFabricService), provide equivalent sfctl commands.
  • Clarify in each example which platforms the commands apply to, and link to Linux/macOS setup guides for Service Fabric CLI.
  • Consider including a short section or appendix summarizing cross-platform management options for Service Fabric clusters.
GitHub Create Pull Request
Service Fabric Learn more about Azure Service Fabric ...icles/service-fabric/service-fabric-content-roadmap.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides a broad overview of Azure Service Fabric, which supports both Windows and Linux. However, there is a notable Windows bias: Windows-specific tools and processes (e.g., PowerShell, Visual Studio, Windows services like FabricHost.exe) are often mentioned first or exclusively, with Linux equivalents either omitted or referenced only briefly. Some sections (e.g., standalone clusters) are Windows-only, but this is called out. Linux support is acknowledged, but practical Linux examples, commands, and tools are largely missing.
Recommendations
  • Add Linux-specific examples and commands (e.g., using Bash/CLI instead of or alongside PowerShell).
  • When referencing tools like Visual Studio, also mention cross-platform alternatives (e.g., VS Code, CLI tools) for Linux users.
  • Where Windows services/executables are described (e.g., FabricHost.exe), clarify Linux equivalents or note differences explicitly.
  • In 'Next steps' and quickstart links, include Linux getting started guides and not just Windows-focused ones.
  • Ensure that CLI and REST API examples are shown alongside PowerShell, not as an afterthought.
  • Where features are Windows-only, clearly call this out (as is done for standalone clusters), and provide alternative guidance for Linux where possible.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page on Azure Service Fabric Events demonstrates a Windows bias by primarily referencing ETW/Windows Event logs and the Windows Azure diagnostics agent as the default mechanisms for event logging and collection. There is no mention of Linux equivalents or guidance for accessing Service Fabric events on Linux clusters, nor are Linux-specific tools or patterns discussed. Windows tools and patterns are presented first and exclusively.
Recommendations
  • Add explicit guidance on how Service Fabric events are logged and accessed on Linux clusters, including any differences in event sources or logging mechanisms.
  • Include examples or references to Linux-compatible monitoring tools (e.g., syslog, journald, or Azure Monitor integration for Linux nodes).
  • Clarify if certain event types or logging features are Windows-only, and provide Linux alternatives or note any limitations.
  • Reorder or balance the documentation so that Linux and Windows approaches are presented with equal prominence where both are supported.
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-02-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides only PowerShell and C# examples for managing Service Fabric services, with no equivalent examples for Linux/macOS users (e.g., Azure CLI, Bash, or REST via curl). All command-line instructions reference PowerShell cmdlets, which are primarily Windows-centric, and there is no mention of Linux-native tools or workflows.
Recommendations
  • Add Azure CLI examples for creating and managing Service Fabric services, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include REST API examples using curl or similar tools to demonstrate platform-agnostic management.
  • Clarify whether PowerShell Core (pwsh) is supported on Linux/macOS for Service Fabric management, and provide examples if so.
  • Where possible, provide Bash or shell script equivalents for common operations.
  • Explicitly mention any differences or limitations for Linux/macOS users, and link to relevant cross-platform documentation.
GitHub Create Pull Request
Service Fabric Azure Service Fabric image store connection string ...fabric/service-fabric-image-store-connection-string.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation frequently references PowerShell for interacting with Service Fabric clusters (e.g., retrieving the cluster manifest), and the main example for programmatic access is PowerShell. There is no mention of Linux/macOS command-line tools (such as Azure CLI or Bash scripts), nor are there examples for these platforms. The 'Next steps' section also points only to PowerShell-based deployment guidance, reinforcing a Windows-first perspective.
Recommendations
  • Add equivalent examples for Linux/macOS users, such as using Azure CLI or Bash scripts to retrieve the cluster manifest.
  • Include references to cross-platform tools (e.g., Azure CLI, REST API usage with curl) alongside PowerShell.
  • Update 'Next steps' to include links to documentation for deploying applications using Linux/macOS tools.
  • Clarify in the text that Service Fabric management can be performed from non-Windows platforms and provide relevant guidance.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation provides comprehensive coverage of both Kestrel (cross-platform) and HTTP.sys (Windows-only) web servers for ASP.NET Core in Service Fabric. However, there is a notable Windows bias in several areas: HTTP.sys (a Windows-only technology) receives extensive coverage and is discussed before Kestrel in many sections, with detailed explanations and code samples. Windows-specific tools and concepts (such as netsh and Windows HTTP Server API) are referenced without Linux equivalents. While Kestrel is recommended for Linux and cross-platform scenarios, the documentation often presents Windows patterns first and provides more depth for Windows-specific features.
Recommendations
  • Reorder sections to present Kestrel (cross-platform) before HTTP.sys (Windows-only), emphasizing Linux/macOS parity.
  • Clearly mark HTTP.sys sections as Windows-only and provide links or notes for Linux/macOS users.
  • Add explicit Linux/macOS guidance for Service Fabric scenarios, including any OS-specific configuration steps or troubleshooting.
  • Where Windows tools (like netsh) are mentioned, clarify their purpose and note that they are not required for Linux/Kestrel scenarios.
  • Ensure all code samples and configuration instructions for Kestrel are as detailed as those for HTTP.sys, including HTTPS setup and endpoint configuration.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page for Replica soft delete in Service Fabric heavily references PowerShell cmdlets (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica, Get-ServiceFabricReplica) as the primary method for interacting with the feature. There are no examples or explicit instructions for Linux/macOS users, such as using the Service Fabric CLI (sfctl) or REST APIs, nor is it clarified whether equivalent functionality is available cross-platform. This creates friction for non-Windows users.
Recommendations
  • Add equivalent examples using sfctl (Service Fabric CLI) commands for Linux/macOS users, if available.
  • Document REST API usage for managing replica soft delete, if supported.
  • Clarify in the documentation whether the PowerShell cmdlets are Windows-only and what alternatives exist for Linux/macOS users.
  • Explicitly state platform support for the feature and its management APIs.
  • Consider including a table summarizing management options (PowerShell, sfctl, REST) and their platform compatibility.
GitHub Create Pull Request
Service Fabric Azure Service Fabric hosting activation and deactivation life cycle ...les/service-fabric/service-fabric-hosting-lifecycle.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation references PowerShell for deployment/removal tasks and links to a PowerShell module for downloading ServicePackages. There are no explicit Linux or cross-platform CLI examples, and PowerShell is mentioned as the primary tool for operational tasks, suggesting a Windows-first approach. However, the core lifecycle concepts are platform-neutral.
Recommendations
  • Add equivalent Linux/macOS CLI examples (e.g., Azure CLI, Bash) alongside PowerShell instructions.
  • Clarify which steps/tools are cross-platform and which are Windows-specific.
  • Provide links to Linux/macOS documentation for Service Fabric operations where available.
  • Mention if PowerShell Core (pwsh) is supported on Linux/macOS for relevant tasks.
GitHub Create Pull Request
Service Fabric Manage apps for multiple environments ...e-fabric-manage-multiple-environment-app-configuration.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides examples for managing application parameters in Service Fabric, with a noticeable emphasis on PowerShell and Visual Studio workflows. PowerShell is mentioned first for application creation, and Visual Studio parameter files are discussed in detail, both of which are Windows-centric tools. Linux equivalents (sfctl and install.sh) are mentioned, but not as prominently or with as much detail.
Recommendations
  • Provide more detailed examples and workflows for Linux/macOS users, such as using sfctl and install.sh for parameter passing.
  • Ensure that Linux tools and commands are given equal prominence and explanation as Windows/PowerShell tools.
  • Add explicit guidance for configuring and deploying applications from Linux/macOS environments, including sample scripts.
  • Consider reordering sections so that cross-platform tools (sfctl, install.sh) are presented before Windows-specific tools.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides only PowerShell-based deployment commands and examples, with no mention of Azure CLI, Bash, or Linux/macOS workflows. Windows tools and patterns (such as RDP and Windows command prompt ping) are referenced exclusively or before any cross-platform alternatives. This creates friction for Linux/macOS users, who must translate instructions or find their own equivalents.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all deployment steps, as Azure CLI is cross-platform.
  • Mention Bash or shell scripting options for Linux/macOS users where relevant.
  • Provide guidance for accessing Service Fabric nodes using SSH instead of RDP, and show SSH-based 'ping' commands.
  • Clarify that all ARM template operations can be performed from any OS, and link to cross-platform tooling documentation.
  • Where PowerShell is used, note that Azure CLI is available and provide equivalent commands.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides detailed examples for reporting health in Service Fabric using PowerShell, which is primarily a Windows tool. PowerShell examples are prominent and shown before REST examples. There are no equivalent Linux/macOS CLI or scripting examples (e.g., Bash, curl, Azure CLI), nor is there mention of Linux-native tools or patterns for health reporting. This creates friction for Linux/macOS users, who must rely on REST or API without clear guidance or parity.
Recommendations
  • Add examples using Bash and curl for REST health report submission.
  • Mention and demonstrate use of Azure CLI (az) for Service Fabric health reporting if supported.
  • Clarify which PowerShell commands are cross-platform (PowerShell Core) and which are Windows-only.
  • Provide guidance for Linux/macOS users on how to perform equivalent tasks, including prerequisites and authentication.
  • Consider reordering examples so REST or cross-platform methods are shown before or alongside PowerShell.
GitHub Create Pull Request
Service Fabric Define Service Configuration in StartupServices.xml for a Service Fabric Application ...service-fabric/service-fabric-startupservices-model.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily oriented towards Visual Studio workflows, referencing Windows-specific tools and patterns (e.g., F5/Ctrl+F5/Publish, right-click in Visual Studio, Visual Studio deployments). There are no examples or guidance for Linux/macOS users or for cross-platform tooling (e.g., CLI, VS Code). PowerShell is mentioned as an alternative for service creation, but only in passing. The documentation does not clarify whether or how StartupServices.xml can be used outside Visual Studio/Windows.
Recommendations
  • Clarify whether StartupServices.xml is supported or relevant for Linux/macOS users and non-Visual Studio workflows.
  • If possible, provide equivalent instructions or guidance for cross-platform tools (e.g., Azure CLI, Service Fabric CLI, VS Code).
  • Explicitly state if StartupServices.xml is a Visual Studio/Windows-only feature at the top of the documentation.
  • If the feature is Windows-only, add a clear note to prevent confusion for Linux/macOS users.
  • If partial support exists for non-Windows environments, provide examples and workflows for those platforms.
GitHub Create Pull Request
Service Fabric Fault Analysis Service overview .../service-fabric/service-fabric-testability-overview.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides usage instructions for the Fault Analysis Service in Service Fabric, mentioning C# and PowerShell as the primary ways to interact with the service. PowerShell is a Windows-centric tool, and no Linux/macOS CLI or scripting examples (such as Bash, Azure CLI, or REST API usage) are given. Additionally, PowerShell is mentioned before any Linux-friendly alternatives, and there is no guidance for Linux users on how to use the Fault Analysis Service.
Recommendations
  • Add examples for interacting with the Fault Analysis Service using Azure CLI, Bash scripts, or REST API calls, which are cross-platform.
  • Clarify whether the Fault Analysis Service APIs can be used from Linux/macOS environments, and provide guidance if so.
  • If PowerShell Core (cross-platform) is supported, specify this and provide examples for Linux/macOS users.
  • Mention any limitations or prerequisites for Linux/macOS users explicitly.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on Windows-centric tools and workflows, specifically Visual Studio and PowerShell. All upgrade instructions and examples reference Visual Studio dialogs and PowerShell cmdlets, with no mention of Linux/macOS alternatives or cross-platform CLI tools. There are no examples or guidance for users on Linux or macOS, and the PowerShell requirement for manual upgrades is presented without alternatives.
Recommendations
  • Add instructions and examples for upgrading Service Fabric applications using cross-platform tools such as Azure CLI or REST APIs.
  • Include guidance for Linux/macOS users, such as how to configure upgrades without Visual Studio or PowerShell.
  • Mention and link to any available Service Fabric SDKs or tools for Linux/macOS, if applicable.
  • Clarify if certain upgrade scenarios are Windows-only, or provide parity where possible.
GitHub Create Pull Request
Service Fabric Azure Service Fabric reverse proxy diagnostics ...ice-fabric/service-fabric-reverse-proxy-diagnostics.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation page exhibits Windows bias primarily through references to Windows-specific tools and terminology (e.g., 'Windows Azure Diagnostics', 'ERROR_WINHTTP_TIMEOUT', 'winHttpError'), and by mentioning Windows-centric workflows and tools before any Linux alternatives. There are no explicit Linux or macOS examples, nor are cross-platform diagnostic tools or log collection methods discussed. The examples and troubleshooting steps assume a Windows environment, which may create friction for Linux/macOS users.
Recommendations
  • Include equivalent Linux/macOS error codes and diagnostic patterns alongside Windows-specific ones.
  • Add instructions and examples for collecting and viewing Service Fabric reverse proxy logs on Linux clusters (e.g., using Linux diagnostics agents, journald, or syslog).
  • Reference cross-platform tools (such as Azure Monitor, Log Analytics, or open-source log shippers) for event aggregation and troubleshooting.
  • Clarify which steps or error codes are Windows-only and provide Linux/macOS alternatives where possible.
  • Reorder sections to present cross-platform or OS-neutral approaches first, then provide OS-specific details.
GitHub Create Pull Request
Service Fabric Azure Service Fabric set up reverse proxy ...es/service-fabric/service-fabric-reverseproxy-setup.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Standalone cluster instructions and references are consistently tied to Windows Server and Windows-specific configuration files (ClusterConfig.json), with links and upgrade instructions pointing to Windows Server documentation. There is no mention of Linux-based standalone clusters or how to configure reverse proxy on Linux. The certificate management examples and references are Windows-centric (e.g., X509StoreName: 'My'), and no Linux equivalents or cross-platform notes are provided. While Azure-hosted clusters use platform-agnostic ARM templates, standalone cluster guidance is Windows-only.
Recommendations
  • Add explicit guidance for Linux-based standalone clusters, if supported, including configuration file locations and certificate management steps.
  • Clarify whether standalone clusters can be hosted on Linux and, if so, provide parity in instructions and examples.
  • When referencing certificate stores (e.g., 'My'), note Linux equivalents or provide cross-platform instructions.
  • Update links and references to include Linux/macOS documentation where available.
  • Consider rewording section titles and upgrade instructions to avoid implying Windows-only support unless that is a product limitation.
GitHub Create Pull Request
← Previous Page 10 of 29 Next →