Service Fabric

407
Total Pages
336
Linux-Friendly Pages
71
Pages with Bias
17.4%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

1305 issues found
Showing 326-350 of 1305 flagged pages
Service Fabric Service Fabric Cluster Resource Manager - Placement Policies ...ce-manager-advanced-placement-rules-placement-policies.md
Medium Priority View Details →
Scanned: 2026-02-16 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 code examples for configuring Service Fabric placement policies using C# and PowerShell, but does not include equivalent Linux/macOS CLI examples (such as Azure CLI or Bash). PowerShell is presented as the only scripting interface, which is primarily used on Windows, and examples are consistently shown in PowerShell before any mention of cross-platform tools.
Recommendations
  • Add Azure CLI or Bash examples for configuring placement policies, as Service Fabric supports cross-platform management.
  • Explicitly mention if PowerShell examples are applicable on Linux/macOS (via PowerShell Core), or provide guidance for non-Windows users.
  • Consider including REST API or ARM template snippets for placement policy configuration, which are platform-agnostic.
  • Where possible, clarify any differences in configuration steps for Linux-based Service Fabric clusters.
GitHub Create Pull Request
Service Fabric Cluster Resource Manager - Management Integration ...fabric-cluster-resource-manager-management-integration.md
Medium Priority View Details →
Scanned: 2026-02-16 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides a PowerShell example for querying Service Fabric partition health, using a Windows-style prompt and cmdlet. No equivalent Linux/macOS CLI example (such as Azure CLI or sfctl) is provided, and the example is presented early in the page. This creates friction for Linux/macOS users, as Service Fabric supports cross-platform management tools.
Recommendations
  • Add equivalent Linux/macOS examples using sfctl or Azure CLI for querying partition health.
  • Explicitly mention that PowerShell examples are for Windows, and provide links or instructions for Linux/macOS users.
  • Consider presenting cross-platform examples side-by-side, or defaulting to platform-neutral tools where possible.
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-16 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 managing Service Fabric metrics primarily in C# and PowerShell. PowerShell is a Windows-centric tool, and no equivalent Linux/macOS CLI examples (such as Azure CLI or Bash) are provided. The PowerShell examples are given alongside C# code, but there is no mention of cross-platform tools or patterns, nor guidance for Linux users. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other tools.
Recommendations
  • Add Azure CLI examples for service creation and metric configuration, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Mention Bash scripting or REST API usage for metric management, providing sample commands or links to relevant documentation.
  • Explicitly state PowerShell's platform limitations and suggest alternatives for non-Windows environments.
  • Ensure that any references to tooling are inclusive of Linux/macOS users, or provide parity in examples.
GitHub Create Pull Request
Service Fabric Azure Service Fabric dynamic node tags ...tps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-node-tagging.md
Medium Priority View Details →
Scanned: 2026-02-16 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 and C# API examples for managing node tags and service tag requirements in Azure Service Fabric, but does not include equivalent examples for Linux/macOS users (e.g., Bash/CLI commands). PowerShell is presented first in each section, suggesting a Windows-centric approach. There is no mention of Linux tools or cross-platform CLI usage for these tasks.
Recommendations
  • Add Azure CLI or Bash examples for managing node tags and service tag requirements, if supported.
  • Clarify whether PowerShell commands are available cross-platform or Windows-only.
  • Mention any REST API endpoints or tools that can be used from Linux/macOS environments.
  • Consider presenting cross-platform methods (e.g., REST API, Azure CLI) before or alongside PowerShell examples.
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-16 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation consistently provides PowerShell examples for all operations, but does not mention or provide equivalent Linux/macOS command-line examples (such as Azure CLI or REST API usage). PowerShell is a Windows-centric tool, and its exclusive use creates friction for Linux/macOS users. The documentation also references Windows-specific tools (PowerShell cmdlets) without alternatives, and does not clarify whether these operations can be performed from non-Windows environments.
Recommendations
  • Add Azure CLI examples for all operations shown with PowerShell, as Azure CLI is cross-platform.
  • Mention REST API endpoints or SDK usage for Linux/macOS users where applicable.
  • Clarify whether PowerShell cmdlets can be used on Linux/macOS (via PowerShell Core), and provide installation guidance if so.
  • Explicitly state if certain operations are Windows-only, or provide links to Linux/macOS-compatible tooling.
  • Consider showing Azure CLI or REST API examples before PowerShell, or side-by-side, to emphasize cross-platform parity.
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-16 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides PowerShell examples for configuring move cost, but does not include equivalent Linux CLI or bash examples. PowerShell is a Windows-centric tool, and its exclusive use creates friction for Linux/macOS users. Additionally, PowerShell examples are presented before C# code, reinforcing a Windows-first pattern. There is no mention of Linux-native tools or cross-platform CLI alternatives for Service Fabric management.
Recommendations
  • Add Azure CLI or Service Fabric CLI (sfctl) examples for move cost configuration and updates, as these are cross-platform and usable on Linux/macOS.
  • Explicitly note if certain operations are only possible via PowerShell, and provide guidance for Linux users if so.
  • Consider presenting cross-platform CLI examples before or alongside PowerShell to improve parity.
  • Clarify any limitations or differences for Linux/macOS users in a dedicated section.
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-16 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides configuration examples using XML, JSON, PowerShell, and C#. PowerShell is used extensively for service creation and updates, but there are no equivalent CLI or Bash examples for Linux/macOS users. PowerShell examples are presented before C# API examples, and no mention is made of cross-platform tools or commands (e.g., Azure CLI, Bash scripts) for managing Service Fabric clusters. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other tooling.
Recommendations
  • Add Azure CLI or Bash examples for service sensitivity and maximum load configuration, where possible.
  • Clarify whether PowerShell commands are supported on Linux/macOS (via PowerShell Core), and provide guidance if so.
  • Consider including REST API examples for service management, which are platform-neutral.
  • Explicitly state if certain operations are Windows-only, or provide links to Linux/macOS alternatives if available.
GitHub Create Pull Request
Service Fabric Secure an Azure Service Fabric cluster ...cles/service-fabric/service-fabric-cluster-security.md
Medium Priority View Details →
Scanned: 2026-02-16 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page covers securing Azure Service Fabric clusters and references both Azure-hosted and standalone Windows clusters. However, it consistently provides explicit guidance and links for Windows standalone clusters, while omitting equivalent instructions or links for standalone Linux clusters. Windows security (Kerberos) is discussed in detail, but there is no mention of Linux authentication mechanisms or how to secure standalone Linux clusters. Certificate creation is described with a Windows-centric focus, referencing Windows Server certificate services and tools like MakeCert.exe, with no Linux alternatives or guidance. The overall pattern is Windows-first, with Linux standalone scenarios largely missing.
Recommendations
  • Add explicit sections or links for securing standalone Linux Service Fabric clusters, including certificate setup and authentication options.
  • Provide Linux-specific examples for certificate creation and management (e.g., using OpenSSL or Linux CA tools).
  • Clarify which security scenarios and recommendations apply equally to Linux clusters, and highlight any differences.
  • Include guidance for Linux client authentication and node-to-node security, or state if Linux standalone clusters are not supported.
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-02-16 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 scaling Azure Service Fabric standalone clusters demonstrates a Windows bias. It references PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) and links to further instructions that appear Windows-specific. There are no Linux-specific examples, tools, or guidance, and the terminology and tooling are focused on Windows environments.
Recommendations
  • Add equivalent Linux instructions and examples, such as using Service Fabric CLI (sfctl) or REST APIs for cluster management.
  • Explicitly mention whether standalone clusters can be managed from Linux/macOS, and provide guidance if so.
  • Include links to Linux/macOS documentation or clarify if the process is Windows-only.
  • If PowerShell is required, note any cross-platform alternatives or limitations.
GitHub Create Pull Request
Service Fabric Upgrade an Azure Service Fabric standalone cluster ...ce-fabric/service-fabric-cluster-upgrade-standalone.md
Medium Priority View Details →
Scanned: 2026-02-16 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page on upgrading an Azure Service Fabric standalone cluster demonstrates a Windows bias. It consistently links to Windows-specific guides (e.g., 'service-fabric-cluster-upgrade-windows-server.md', 'service-fabric-cluster-config-upgrade-windows-server.md') and references the Patch Orchestration Application only for Windows. There are no Linux-specific instructions, examples, or links, and the documentation does not clarify if Linux standalone clusters are supported or provide guidance for them.
Recommendations
  • Clarify early in the article whether standalone clusters are Windows-only, or explicitly state Linux support status.
  • If Linux standalone clusters are supported, provide equivalent upgrade and configuration instructions, or link to Linux-specific guides.
  • Reference or document the Patch Orchestration Application (POA) for Linux if available, or clarify its absence.
  • Where possible, use neutral language and examples, or present Linux and Windows options side by side.
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-16 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 and administrative instructions primarily in PowerShell and C#, both of which are more closely associated with Windows environments. There are no equivalent Linux CLI or scripting examples (e.g., Bash, Azure CLI) for scaling operations. Windows tools and patterns (PowerShell cmdlets) are mentioned exclusively and before any Linux alternatives, which are absent. While the page does acknowledge platform differences, the practical guidance is Windows-centric.
Recommendations
  • Add Linux-specific examples for scaling operations, such as using Bash scripts or Azure CLI commands.
  • Include instructions or references for managing Service Fabric clusters on Linux, especially for tasks currently shown only in PowerShell.
  • Present code samples for both Windows and Linux platforms, or clarify when a sample is Windows-only.
  • Mention Linux administrative tools or patterns alongside PowerShell cmdlets, such as systemd or relevant Linux cluster management commands.
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-16 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, references ApplicationManifest.xml (a Windows-centric deployment artifact), and does not offer equivalent Linux CLI or scripting examples (e.g., Bash, Azure CLI). Windows tools and patterns (PowerShell, Visual Studio) are mentioned before or instead of Linux alternatives. Linux limitations are noted, but Linux-centric workflows are not demonstrated.
Recommendations
  • Add Azure CLI or Bash examples for setting DNS names and managing Service Fabric services, especially for Linux clusters.
  • Include guidance for Linux users on editing deployment artifacts (e.g., Docker Compose, YAML) and deploying services without ApplicationManifest.xml.
  • Clarify how Linux users can enable DNS service (since portal is not supported), with step-by-step instructions using ARM templates or Azure CLI.
  • Mention and show Linux-friendly editors (e.g., VS Code) instead of only Visual Studio.
  • Provide explicit examples or links for containerized service deployments on Linux clusters.
GitHub Create Pull Request
Service Fabric Upgrading Azure Service Fabric clusters ...icles/service-fabric/service-fabric-cluster-upgrade.md
Medium Priority View Details →
Scanned: 2026-02-16 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation provides general guidance on upgrading Azure Service Fabric clusters, but there is a subtle Windows bias. References to PowerShell and Azure CLI are made for certificate management and port configuration, but Linux equivalents (such as Bash or Linux-specific CLI usage) are not explicitly mentioned. The section on OS image upgrades links only to Windows-specific patching guidance, suggesting Windows as the primary platform. However, most upgrade instructions are platform-agnostic, and no critical steps are Windows-only.
Recommendations
  • Explicitly mention that Azure CLI commands can be run from Bash on Linux/macOS, not just PowerShell.
  • Add examples or links for Linux/macOS users where PowerShell is referenced, such as using Azure CLI in Bash.
  • Provide guidance or links for patching cluster nodes running Linux OS images, if supported.
  • Clarify which features or steps are Windows-only and which are cross-platform, to avoid confusion.
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-16 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 provides a broad overview of Azure Service Fabric, which supports both Windows and Linux. However, there are several instances where Windows-specific tools, services, and examples are mentioned first or exclusively. For example, references to 'FabricHost.exe' as an auto-start Windows service, standalone cluster creation only for Windows, and frequent mention of PowerShell cmdlets without equal prominence for Linux equivalents. Linux support is acknowledged, but Linux-specific instructions, tools, and examples are often missing or secondary.
Recommendations
  • Provide Linux-specific examples and instructions alongside Windows ones, especially for cluster setup, management, and health monitoring.
  • Mention Linux CLI tools (such as sfctl) and bash scripts with equal prominence to PowerShell.
  • Clarify which features are Windows-only and which are cross-platform, linking to the differences page where relevant.
  • Add explicit guidance for Linux users in sections where only Windows tools or workflows are described.
  • Ensure that references to Windows executables (e.g., FabricHost.exe) are accompanied by Linux equivalents or notes about platform differences.
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-16 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page primarily references Windows-specific event logging mechanisms (ETW/Windows Event logs, Windows Azure diagnostics agent) and tools, without mentioning Linux equivalents or providing Linux-specific guidance. Windows tools and patterns are discussed first and exclusively, creating friction for Linux cluster administrators.
Recommendations
  • Explicitly mention how Service Fabric events are logged and accessed on Linux clusters, including any differences in event channels, logging mechanisms, or monitoring tools.
  • Provide examples or references for accessing Service Fabric events on Linux (e.g., using syslog, journald, or Azure Monitor integration for Linux nodes).
  • Clarify whether the Azure diagnostics agent and event logging methods are applicable to Linux clusters, and if not, suggest Linux-compatible alternatives.
  • Ensure parity in guidance and examples for both Windows and Linux Service Fabric clusters.
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-16 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. It references Visual Studio as a packaging tool and provides a path to the Service Fabric SDK schema in a Windows directory (C:\Program Files\...), without mentioning Linux/macOS equivalents or alternatives. There are no explicit Linux/macOS examples or guidance, and the directory structure example uses a Windows executable (.exe), which may imply Windows-centric usage.
Recommendations
  • Add explicit instructions or examples for packaging and deploying guest executables on Linux/macOS, including references to relevant tools and SDK locations.
  • Mention cross-platform command-line utilities and their usage for packaging and deployment, not just Visual Studio.
  • Provide sample directory structures and file naming conventions that are platform-agnostic (e.g., using .sh or .out for Linux executables alongside .exe).
  • Clarify whether the Service Fabric SDK and schema files are available on Linux/macOS, and if so, provide their typical installation paths.
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-16 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-based command-line examples for creating services with the Exclusive Process model, but does not include equivalent examples for Linux environments (e.g., Azure CLI, Bash, or Service Fabric CLI). The only command-line example is PowerShell, and the documentation refers to PowerShell cmdlets for management tasks, which are Windows-centric. There is no mention of Linux tools or workflows, nor are Linux/macOS equivalents shown or referenced.
Recommendations
  • Add Azure CLI or Service Fabric CLI (sfctl) examples for creating and managing services, especially for commands currently only shown in PowerShell.
  • Explicitly mention Linux/macOS support and provide guidance or links for non-Windows users.
  • Where PowerShell cmdlets are referenced, provide equivalent REST API or CLI commands, or at least note their availability.
  • Consider adding a short section or callout clarifying cross-platform management options for Service Fabric clusters.
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-16 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation references PowerShell as the primary example for interacting with Service Fabric clusters (e.g., retrieving the cluster manifest), and links to a PowerShell-based deployment guide as the next step. While .NET and REST are mentioned, PowerShell is presented first and most prominently. There are no explicit Linux or cross-platform CLI examples (such as Azure CLI or Bash), nor is there mention of Linux tooling or workflows.
Recommendations
  • Add Azure CLI or Bash examples for retrieving the cluster manifest and deploying applications, highlighting cross-platform approaches.
  • Mention Linux/macOS compatibility for Service Fabric tooling where applicable.
  • Provide links to documentation or guides for Linux users, such as using Service Fabric CLI (sfctl) or REST APIs from non-Windows environments.
  • Balance example ordering so that PowerShell is not always presented first, or clarify that PowerShell is just one option.
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-16 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation is notably Windows-centric: all manifest examples are based on a Windows Server 2016 container sample, and several explanations reference Windows-specific tools (e.g., 'winver' for OS build detection). There is little to no mention of Linux container scenarios, and no Linux-specific manifest examples or guidance are provided, despite Service Fabric supporting Linux containers.
Recommendations
  • Add parallel manifest examples based on a Linux container sample, or clarify which elements differ for Linux containers.
  • When referencing OS build detection, include Linux equivalents (e.g., 'uname -r' or '/etc/os-release') alongside Windows instructions.
  • Explicitly call out any settings or patterns that are Windows-only, and provide Linux alternatives or note when features are cross-platform.
  • Update references to file paths (e.g., 'c:\VolumeTest\Data') to include Linux-style paths or clarify platform-specific differences.
  • Where PowerShell or Windows command-line tools are mentioned, provide equivalent Linux shell commands if applicable.
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-16 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation covers both Kestrel (cross-platform) and HTTP.sys (Windows-only) for ASP.NET Core in Service Fabric. However, HTTP.sys (a Windows-only web server) is described in detail and presented before Kestrel in several sections, with extensive configuration and code examples. The documentation also references Windows-specific tools (e.g., netsh) and concepts (e.g., Windows HTTP Server API, kernel driver) without always providing Linux/macOS equivalents or clarifying cross-platform alternatives early. While Kestrel is ultimately recommended for cross-platform scenarios, the ordering and depth of HTTP.sys coverage may create friction for Linux/macOS users.
Recommendations
  • Move Kestrel (cross-platform) guidance and examples before HTTP.sys (Windows-only) in all sections, making it the default/primary path.
  • Explicitly call out HTTP.sys as Windows-only at the start of relevant sections, and direct Linux/macOS users to Kestrel.
  • Where Windows-specific tools (e.g., netsh) or configuration are mentioned, clarify that these are not applicable to Linux/macOS and provide alternative guidance or state 'not required on Linux/macOS'.
  • Add a short summary table or decision tree at the top to help users quickly choose the correct web server for their OS.
  • Ensure all critical code/configuration examples are shown for Kestrel first, and only then for HTTP.sys as a Windows-specific option.
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-16 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page provides Service Fabric application and service manifest examples, but the examples and descriptions are implicitly Windows-centric. Batch scripts (.bat), references to Windows accounts (NetworkService, Administrators), and mentions of ServiceFabric PowerShell module are present, with no Linux-specific equivalents or guidance. There are no examples or notes for Linux clusters, nor for using shell scripts or Linux user/group patterns. This creates friction for Linux users, though the content is not strictly Windows-only.
Recommendations
  • Add Linux-specific examples, such as using shell scripts (.sh) in SetupEntryPoint and EntryPoint elements.
  • Clarify which manifest features and account types are supported on Linux clusters, and provide guidance for Linux user/group configuration.
  • Mention and provide examples for Linux deployment tools (e.g., Azure CLI, sfctl) alongside or before Windows/PowerShell references.
  • Explicitly note any cross-platform differences in supported features (e.g., RunAsPolicy, account types, endpoint configuration) and link to relevant Linux documentation.
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-16 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 for enhanced data protection in Service Fabric' demonstrates a notable Windows/PowerShell bias. All command-line/API usage examples reference PowerShell cmdlets (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica, Get-ServiceFabricReplica), with no mention of Linux CLI equivalents or cross-platform tooling. There are no examples or guidance for Linux/macOS users, and the documentation assumes familiarity with Windows/PowerShell tools.
Recommendations
  • Include equivalent examples using cross-platform Service Fabric CLI (sfctl) commands where available.
  • Explicitly mention whether the described PowerShell cmdlets are available or not on Linux/macOS, and provide alternative instructions if possible.
  • Add notes or links for Linux/macOS users on how to perform the same operations (e.g., using REST APIs, sfctl, or SDKs in other languages).
  • Clarify any platform limitations if the APIs or features are only available on Windows.
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-16 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation is heavily focused on Visual Studio workflows and Windows-centric development patterns for Service Fabric applications. All examples and instructions reference Visual Studio features (Build/Rebuild/F5/Ctrl+F5/Publish), which are only available on Windows. There are no Linux/macOS equivalents or guidance for cross-platform development, and no mention of alternative tooling or workflows for non-Windows users.
Recommendations
  • Add explicit guidance for Linux/macOS users, including how to manage service configuration without Visual Studio.
  • Provide examples or references for command-line tools (e.g., Azure CLI, Service Fabric CLI, PowerShell Core) that work on Linux/macOS for deploying and configuring Service Fabric applications.
  • Clarify which parts of the workflow are Windows-only and offer alternative approaches for cross-platform scenarios.
  • Mention any limitations or differences for Linux/macOS users in the context of StartupServices.xml and Service Fabric SDK usage.
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-16 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 in Service Fabric, with no equivalent Linux/macOS CLI examples (such as Bash, Azure CLI, or cross-platform tools). PowerShell is presented as the primary scripting interface, and Windows-style command prompts are used. REST and API options are mentioned, but scripting and command-line guidance is Windows-centric.
Recommendations
  • Add cross-platform CLI examples using Azure CLI or Bash scripts for health reporting.
  • Clarify whether PowerShell examples are usable on Linux/macOS (PowerShell Core), and provide guidance for those platforms.
  • Mention and demonstrate any available Linux-native Service Fabric CLI tools (e.g., sfctl) for health reporting.
  • Explicitly note platform support for each method (API, PowerShell, REST) and highlight Linux/macOS options where available.
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-02-16 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides a PowerShell example for deploying Service Fabric applications, which is Windows-centric. The Service Fabric tooling and SDK path references are Windows-first (e.g., C:\Program Files\Microsoft SDKs\Service Fabric\schemas\...), and the PowerShell deployment example is given without a Linux equivalent. While there is a brief mention of Linux clusters regarding certificate storage, Linux deployment patterns and CLI examples are missing.
Recommendations
  • Add equivalent Linux deployment instructions and examples, such as using Azure CLI or Service Fabric CLI (sfctl) for application deployment.
  • Mention the Linux SDK/schema location alongside the Windows path.
  • Provide cross-platform guidance for endpoint configuration and certificate management.
  • Ensure that all PowerShell examples are accompanied by Linux/macOS alternatives.
GitHub Create Pull Request
← Previous Page 14 of 53 Next →