Service Fabric

407
Total Pages
335
Linux-Friendly Pages
72
Pages with Bias
17.7%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

2475 issues found
Showing 1676-1700 of 2475 flagged pages
Service Fabric Upgrading Azure Service Fabric clusters ...icles/service-fabric/service-fabric-cluster-upgrade.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 provides general guidance for upgrading Azure Service Fabric clusters, but it demonstrates Windows bias in several areas. References to PowerShell are made without equivalent Linux/bash examples, and the section on OS image upgrades links only to Windows-specific patching guidance. The mention of 'Patch Orchestration Application' is tied to Windows OS patching, with no mention of Linux node patching or upgrade procedures. Additionally, Windows tools (PowerShell) are mentioned before Azure CLI, and Linux-specific workflows are not described.
Recommendations
  • Include Linux-specific guidance for OS image upgrades, such as linking to documentation about patching Linux nodes in Service Fabric clusters.
  • Provide examples for managing certificates, opening application ports, and other cluster operations using bash/Azure CLI, not just PowerShell.
  • Clarify whether Service Fabric clusters can run on Linux nodes and, if so, provide parity in upgrade instructions and references.
  • When mentioning PowerShell, always mention Azure CLI/bash alternatives alongside or before it.
  • Add a section or links for Linux node patching and upgrade best practices.
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: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. All deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource), with no equivalent Azure CLI or Linux/macOS shell instructions. The application packaging step references Visual Studio (a Windows-centric tool), and the directory paths use Windows-style notation. There are no Linux/macOS alternatives or guidance, and Windows tools are mentioned first and exclusively.
Recommendations
  • Add Azure CLI examples for deployment and deletion tasks alongside PowerShell examples.
  • Provide instructions for packaging the application using cross-platform tools (e.g., dotnet CLI, SF SDK, or manual zip commands) instead of only Visual Studio.
  • Use platform-neutral directory paths or clarify the location for Linux/macOS users.
  • Mention that all steps can be performed from Linux/macOS, and provide any necessary prerequisites or differences.
  • Include screenshots or references for Linux/macOS environments where appropriate.
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 for Azure Service Fabric Events demonstrates a Windows bias by primarily referencing Windows Event logs, ETW, and the Windows Azure diagnostics agent as the default mechanisms for event access and monitoring. There are no explicit Linux or cross-platform examples or instructions, and Windows tools are mentioned first and exclusively in the 'How to access events' section. This creates friction for Linux/macOS users, as Service Fabric supports Linux clusters but the documentation does not address their event access or monitoring workflows.
Recommendations
  • Add explicit guidance for accessing Service Fabric events on Linux clusters, including supported logging mechanisms (e.g., stdout, syslog, Azure Monitor integration).
  • Provide examples or references for configuring diagnostics and event collection on Linux nodes.
  • Mention cross-platform tools and APIs (such as EventStore REST APIs) earlier and highlight their applicability to both Windows and Linux clusters.
  • Clarify which instructions are Windows-specific and offer Linux alternatives where possible.
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, references ApplicationManifest.xml (a Windows-centric workflow), and does not offer Linux CLI or scripting equivalents. Windows portal workflows are described in detail, while Linux-specific limitations are mentioned but not accompanied by alternative instructions or parity examples. The ARM template approach is platform-neutral, but practical Linux workflows (e.g., Bash, Azure CLI) are missing.
Recommendations
  • Add Linux-specific examples for setting DNS names, such as using Bash scripts, Azure CLI, or REST API.
  • Clarify how Linux users can configure DNS service, especially since portal workflows are unavailable for Linux clusters.
  • Provide guidance for containerized Linux services, including Docker Compose or Kubernetes YAML examples for DNS integration.
  • Where PowerShell is used, offer equivalent Azure CLI or Bash commands for Linux users.
  • Explicitly note which steps are Windows-only and provide Linux alternatives where possible.
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 First Missing Linux Example
Summary
The documentation page for Azure Service Fabric hosting model presents PowerShell examples exclusively for service creation and management, with no equivalent Linux CLI (e.g., Azure CLI or Bash) examples. Windows/PowerShell tools are referenced first and most prominently, while Linux-native workflows are not mentioned. This creates friction for Linux/macOS users, who may need to adapt instructions or search for alternative tooling.
Recommendations
  • Add Azure CLI examples for service creation and management, especially for specifying ServicePackageActivationMode.
  • Explicitly mention cross-platform management options (e.g., REST API usage from Bash/curl, Azure CLI, or SDKs usable on Linux/macOS).
  • Clarify which PowerShell commands are available on PowerShell Core (cross-platform) versus Windows PowerShell.
  • Provide links or references to Linux/macOS-specific documentation or tooling where applicable.
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: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation shows a moderate Windows bias. It references the Service Fabric SDK schema file using a Windows path (C:\Program Files\Microsoft SDKs\Service Fabric\schemas\...), and does not mention Linux/macOS equivalents or installation paths. There is also an implicit assumption of Windows environments (e.g., use of .exe in examples), and Visual Studio is mentioned as a primary tool before command-line utilities, which may suggest Windows-first orientation. However, the content does not explicitly exclude Linux/macOS, and Service Fabric supports Linux clusters.
Recommendations
  • Add Linux/macOS paths for the Service Fabric SDK schema file, or clarify if it is only available on Windows.
  • Provide examples using Linux-compatible executables (e.g., .sh or ELF binaries) in the directory structure.
  • Mention cross-platform tools (such as VS Code or CLI tools) alongside Visual Studio, or clarify which steps are Windows-only.
  • Explicitly state platform support and any limitations for Linux/macOS 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-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 examples and command-line instructions, with no mention of Azure CLI, Bash, or Linux/macOS-compatible workflows. Windows-specific tools (PowerShell, RDP) are referenced exclusively and shown 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 commands for template deployment and resource management.
  • Mention Bash scripting or cross-platform shell options where appropriate.
  • Clarify that Azure Resource Manager templates can be deployed from any OS, and link to relevant cross-platform documentation.
  • Provide guidance for accessing Service Fabric clusters from Linux/macOS (e.g., SSH instead of RDP, using Service Fabric Explorer via browser).
  • Where ping or other commands are shown, use generic syntax or note platform differences.
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 Missing Linux Example
Summary
The documentation provides thorough coverage of both Kestrel (cross-platform) and HTTP.sys (Windows-only) web servers for ASP.NET Core integration with Azure Service Fabric. However, Windows-specific tools and patterns (such as HTTP.sys, netsh, and Windows HTTP Server API) are discussed in detail, often before or alongside Kestrel. The HTTP.sys section is Windows-only, but this is clearly noted. Some example configurations and endpoint setup instructions reference Windows tools (e.g., netsh) without Linux equivalents or alternatives. Visual Studio debugging is mentioned in 'Next steps,' which is Windows-centric, and there are no explicit Linux/macOS development environment instructions or troubleshooting guidance.
Recommendations
  • Add explicit Linux/macOS development environment setup instructions, including recommended tools and troubleshooting.
  • Provide examples for configuring and running Service Fabric Reliable Services with Kestrel on Linux, including endpoint and port management.
  • Clarify when Windows-only features (like HTTP.sys) are not available on Linux/macOS and suggest alternatives (e.g., always use Kestrel on Linux).
  • Include links or references to Linux/macOS-specific Service Fabric documentation or tutorials.
  • Mention cross-platform debugging tools or alternatives to Visual Studio for Linux/macOS users.
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 for enhanced data protection in Service Fabric' heavily references PowerShell cmdlets (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica, Get-ServiceFabricReplica) as the primary means of interacting with the feature. There are no examples or explicit instructions for Linux/macOS users, such as using Service Fabric CLI (sfctl) or REST APIs, even though Service Fabric supports cross-platform management. The documentation assumes PowerShell as the default administrative interface, which may create friction for non-Windows users.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl) for all PowerShell cmdlet operations (remove, restore, get replica).
  • Mention REST API alternatives where available for managing replicas.
  • Clarify in the introduction that PowerShell is one option and that cross-platform tools are available.
  • Provide links to cross-platform tooling documentation (sfctl, REST API) alongside PowerShell references.
  • Where screenshots or command output are shown, consider including sfctl or REST API output as well.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page shows a moderate Windows bias. PowerShell is the only CLI example given for deploying applications, and the documentation references Windows file paths and certificate stores before mentioning Linux equivalents. The Service Fabric SDK schema path is given in a Windows format, and PowerShell is used for deployment commands without Bash or Linux CLI alternatives. Linux-specific information is present but less prominent and often appears after Windows details.
Recommendations
  • Provide equivalent Bash or Azure CLI examples for Linux/macOS users alongside PowerShell commands.
  • Mention Linux file paths and certificate store locations at the same time as Windows paths, not after.
  • Clarify when instructions or tools are cross-platform, and explicitly note any Windows-only steps.
  • Add a section or callouts for Linux/macOS deployment workflows, especially for common tasks like application deployment.
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, with explicit PowerShell commands and Windows-style prompts (e.g., 'PS C:\>'). API examples are given in C#, but there are no Linux/macOS shell (bash) or cross-platform CLI examples. The PowerShell approach is presented before REST, and REST is only briefly mentioned without concrete examples. There is no mention of Linux equivalents (such as Azure CLI, bash scripts, or cross-platform tools), nor guidance for Linux users on how to perform similar tasks.
Recommendations
  • Add Azure CLI examples for reporting health, if supported, or clarify if only PowerShell is available.
  • Provide bash shell script examples for REST calls (using curl or similar) to demonstrate health reporting from Linux/macOS.
  • Explicitly state platform requirements for PowerShell commands, and offer alternatives for Linux/macOS users.
  • Ensure REST examples include concrete sample requests (e.g., curl commands) for cross-platform parity.
  • Mention any limitations or differences for Linux-based Service Fabric clusters, if applicable.
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 Missing Linux Example
Summary
The documentation provides explicit PowerShell instructions for using the Fault Analysis Service but does not mention or provide examples for Linux/macOS users (e.g., Bash, CLI, or REST API usage). This creates friction for non-Windows developers who may not use PowerShell.
Recommendations
  • Add instructions or examples for using the Fault Analysis Service from Linux/macOS environments, such as via Azure CLI, Bash scripts, or REST API.
  • Clarify whether the Fault Analysis Service can be managed using cross-platform tools, and provide links or references if so.
  • If PowerShell is required, explicitly state this limitation and suggest workarounds or alternatives for Linux/macOS users.
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: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation is heavily focused on Windows tooling, specifically Visual Studio and PowerShell, for configuring and upgrading Service Fabric applications. All examples and instructions reference Windows tools, with no mention of Linux/macOS equivalents or cross-platform CLI options. Linux users are not provided guidance for performing upgrades outside of PowerShell or Visual Studio.
Recommendations
  • Add instructions and examples for upgrading Service Fabric applications using Azure CLI or REST API, which are cross-platform.
  • Mention and link to any Linux/macOS compatible tools for Service Fabric application management.
  • Clarify whether PowerShell Core (cross-platform) is supported, and provide examples if so.
  • Provide guidance for editing application manifest files and performing upgrades from Linux/macOS environments.
GitHub Create Pull Request
Service Fabric Initializer CodePackages in Service Fabric ...in/articles/service-fabric/initializer-codepackages.md
Medium Priority View Details →
Scanned: 2026-02-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page provides examples and guidance exclusively for Windows containers in Service Fabric, including Windows-specific container images, file paths, and commands. No Linux container examples, Linux file paths, or Linux command syntax are provided, and the page assumes familiarity with Windows container workflows. This creates friction for Linux users wishing to use Initializer CodePackages with Linux containers.
Recommendations
  • Add parallel examples for Linux containers, including Linux-based container images (e.g., Ubuntu, Alpine) and Linux command syntax (e.g., bash, sh).
  • Show Linux file paths and volume mounts (e.g., /workspace/log.txt) alongside Windows paths.
  • Clarify whether Initializer CodePackages are supported for Linux containers and, if so, provide guidance and examples.
  • If Initializer CodePackages are Windows-only, explicitly state this early in the documentation.
GitHub Create Pull Request
Service Fabric Capacity planning and scaling for Azure Service Fabric ...bric/service-fabric-best-practices-capacity-scaling.md
Medium Priority View Details →
Scanned: 2026-02-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page provides several PowerShell-based instructions (e.g., using Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState) for cluster scaling operations, but does not offer equivalent Linux/CLI/bash examples or guidance. This creates friction for Linux users, who may not have access to PowerShell or may prefer bash/CLI tools. The documentation also references Windows-centric tools and patterns without mentioning Linux alternatives.
Recommendations
  • For every PowerShell command or workflow, provide equivalent Azure CLI, bash, or REST API examples suitable for Linux/macOS users.
  • Explicitly mention if certain commands are only available on Windows, and provide alternative approaches for Linux clusters (e.g., using Service Fabric CLI (sfctl), Azure CLI, or REST API).
  • Add a section or callout for Linux users, summarizing the recommended tools and commands for common scaling operations.
  • Ensure that code snippets and step-by-step instructions are platform-agnostic or include both Windows and Linux variants where possible.
GitHub Create Pull Request
Service Fabric Architecture of Azure Service Fabric ...articles/service-fabric/service-fabric-architecture.md
Medium Priority View Details →
Scanned: 2026-02-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page for Azure Service Fabric architecture mentions PowerShell cmdlets as a primary management interface and references Windows security as a transport option. PowerShell is a Windows-centric tool, and its mention as the first or only example for management tasks suggests a Windows-first bias. There are no explicit Linux management examples or references to Linux-native tools (e.g., Bash, CLI), which may create friction for Linux/macOS users.
Recommendations
  • Add examples or references to Azure CLI or Bash scripts for management tasks alongside PowerShell.
  • Clarify whether management APIs and tools are cross-platform, and provide guidance for Linux/macOS users.
  • Mention Linux security mechanisms (e.g., certificate-based authentication) in the transport subsystem section, not just Windows security.
  • Consider providing links to Linux-specific documentation or guides for Service Fabric management.
GitHub Create Pull Request
Service Fabric Deny assignment policy for Service Fabric managed clusters ...cles/service-fabric/managed-cluster-deny-assignment.md
Medium Priority View Details →
Scanned: 2026-02-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides examples and links primarily for Azure PowerShell modules, with PowerShell-based tools mentioned before Azure CLI and sfctl. While Azure PowerShell is cross-platform, its usage and prominence may create friction for Linux/macOS users who typically prefer CLI or native tools. The 'Best practices' section highlights PowerShell commands first and provides links to PowerShell modules before CLI equivalents.
Recommendations
  • Provide Azure CLI examples alongside PowerShell examples, especially for key operations like deleting NodeTypes or restarting/reimaging scale sets.
  • List Azure CLI and sfctl tools before or equally with PowerShell in tool tables and best practices.
  • Clarify that Azure PowerShell is cross-platform, but offer parity in examples for CLI and sfctl.
  • Add explicit Linux/macOS guidance or callouts where workflows differ.
GitHub Create Pull Request
Service Fabric Azure Service Fabric security best practices ...rvice-fabric/service-fabric-best-practices-security.md
Medium Priority View Details →
Scanned: 2026-02-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Windows and Linux examples for key security tasks, but Windows-specific tools (PowerShell, Windows Defender, DSC) are mentioned first or exclusively in several sections. Windows-centric terminology and recommendations (e.g., Windows Defender, DSC, security baselines) are prominent, and PowerShell commands are presented before Linux equivalents. Some sections (Windows Defender, DSC, Windows security baselines) are Windows-only by nature, but Linux alternatives or clarifications are not always provided.
Recommendations
  • Ensure Linux examples are presented alongside Windows examples, not after them, and consider alternating order.
  • Where Windows-specific tools are discussed (e.g., Windows Defender, DSC), explicitly mention Linux alternatives or clarify their absence.
  • Add references to Linux security baselines (e.g., CIS benchmarks) and tools (e.g., SELinux, AppArmor) where relevant.
  • For sections with PowerShell-heavy examples, provide equivalent Bash/CLI commands for Linux clusters.
  • Clarify when a feature or recommendation is Windows-only, and provide guidance for Linux users where possible.
GitHub Create Pull Request
Service Fabric Application lifecycle in Service Fabric ...service-fabric/service-fabric-application-lifecycle.md
Medium Priority View Details →
Scanned: 2026-02-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page for the Service Fabric application lifecycle consistently references PowerShell cmdlets and Windows-centric tooling (e.g., PowerShell commands, .NET APIs) as primary examples for operational tasks such as deployment, upgrade, removal, and cleanup. REST API alternatives are mentioned, but PowerShell is often listed first and is the only shell scripting example provided. There is minimal mention of Linux-specific tools or workflows, and no CLI (sfctl or Azure CLI) command examples are shown directly in the main lifecycle sections, despite a link to CLI documentation.
Recommendations
  • Add explicit examples using Service Fabric CLI (sfctl) and Azure CLI for each lifecycle operation, alongside PowerShell and .NET examples.
  • Ensure CLI and REST API options are presented before or equally with PowerShell cmdlets, especially in introductory or summary lists.
  • Include Linux/macOS-friendly shell scripting examples where PowerShell is used, or reference equivalent bash commands.
  • Clarify which tools are cross-platform and which are Windows-only, to help users choose the right approach for their environment.
  • Consider adding a section or table comparing available tooling for Windows and Linux/macOS users.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager - Placement Policies ...ce-manager-advanced-placement-rules-placement-policies.md
Medium Priority View Details →
Scanned: 2026-02-09 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 primarily using C# and PowerShell. All CLI examples are PowerShell-based, with no equivalent Bash, Linux CLI, or cross-platform Azure CLI examples. PowerShell is a Windows-centric tool, and its exclusive use creates friction for Linux/macOS users. Additionally, PowerShell examples are consistently shown alongside C# code, with no mention of Linux-native tools or patterns.
Recommendations
  • Add equivalent examples using Azure CLI or Bash scripts for configuring placement policies, where possible.
  • Clarify whether the PowerShell commands can be run on Linux/macOS (e.g., via PowerShell Core), or provide guidance for non-Windows users.
  • Mention any cross-platform tools or APIs available for managing Service Fabric clusters.
  • If certain operations are only possible via PowerShell, explicitly state this limitation.
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-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides extensive PowerShell examples for configuring service sensitivity and maximum load, but does not mention or provide equivalent CLI or scripting examples for Linux/macOS users. PowerShell is presented as the primary scripting interface, and there is no guidance for Linux-native tools or cross-platform alternatives. This creates friction for non-Windows users, especially those managing Service Fabric clusters on Linux.
Recommendations
  • Add equivalent examples using Azure CLI or REST API, which are cross-platform and usable on Linux/macOS.
  • Clarify whether PowerShell examples are supported on Linux (via PowerShell Core), and provide instructions if so.
  • Include bash or shell script examples where possible, or reference cross-platform management tools.
  • Explicitly state any limitations or differences for Linux-based Service Fabric clusters, if applicable.
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-09 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 Azure Service Fabric, with a notable 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 detailed examples.
Recommendations
  • Provide explicit Linux/macOS examples for parameter management, such as using sfctl and install.sh, including sample commands and workflows.
  • Balance the order of examples so that Linux tools (sfctl) are not secondary to PowerShell.
  • Expand on Jenkins usage for parameter substitution, including sample scripts for Linux environments.
  • Clarify which tools are cross-platform and which are Windows-only, to help users choose the right workflow.
GitHub Create Pull Request
Service Fabric Specifying Service Fabric service endpoints ...ce-fabric/service-fabric-service-manifest-resources.md
Medium Priority View Details →
Scanned: 2026-02-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides a PowerShell-based deployment example (New-ServiceFabricApplication) without equivalent Linux/macOS CLI examples, and references Windows file paths and tools first (e.g., schema location in C:\Program Files\...). Linux is mentioned only briefly, and Linux/macOS users are left to infer or seek out their own equivalents.
Recommendations
  • Provide equivalent Azure CLI or sfctl (Service Fabric CLI) examples for application deployment, especially for overriding endpoints, alongside or before PowerShell examples.
  • When referencing file paths (e.g., schema files), include both Windows and Linux locations, or clarify the Linux equivalent.
  • Add explicit notes or sections for Linux/macOS users where behavior or commands differ, such as certificate store locations, deployment commands, or file system paths.
  • Where PowerShell is used, link to documentation for Linux/macOS deployment or provide a cross-platform table of commands.
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-09 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 examples and references Windows tools (e.g., RDP, Windows command prompt ping). There are no equivalent examples for Linux/macOS users (such as Azure CLI or Bash), and Windows-specific patterns (like PowerShell and RDP) are mentioned before any cross-platform alternatives. This creates friction for Linux/macOS users wishing to deploy or manage Service Fabric clusters using Azure networking features.
Recommendations
  • Add Azure CLI (az) command examples alongside PowerShell for all deployment steps.
  • Include Bash shell examples for common tasks (e.g., ping, SSH) instead of only Windows command prompt and RDP.
  • Mention SSH access as an alternative to RDP for connecting to VMs, especially for Linux/macOS users.
  • Clearly indicate which steps are cross-platform and which are Windows-specific, and provide guidance for Linux/macOS users where appropriate.
  • Consider reordering examples so that cross-platform tools (Azure CLI, Bash) are presented before or alongside Windows tools.
GitHub Create Pull Request
Service Fabric Manage certificates in a Service Fabric cluster ...vice-fabric/cluster-security-certificate-management.md
Medium Priority View Details →
Scanned: 2026-02-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides a mix of conceptual and hands-on guidance for managing certificates in Azure Service Fabric clusters. While the overall guidance is platform-agnostic, there is a notable bias toward Windows in several areas: PowerShell is the only scripting example given for certificate enrollment, and the Key Vault VM extension is discussed exclusively in its Windows variant. The extension's schema and behaviors are described as 'Only Windows,' and Windows-specific concepts (such as S-channel and certificate linking) are explained in detail. Linux equivalents (e.g., Key Vault VM extension for Linux, Bash/Az CLI examples) are not mentioned or provided, and Windows terminology and tools are presented first or exclusively in critical automation sections.
Recommendations
  • Add Linux-specific examples for certificate provisioning and management, such as using the Key Vault VM extension for Linux or alternative mechanisms.
  • Provide Bash/Az CLI scripting examples alongside PowerShell for certificate enrollment and management.
  • Clarify which steps or mechanisms are Windows-only and offer Linux alternatives or links to relevant documentation.
  • Mention cross-platform considerations explicitly in sections discussing VM extensions, certificate stores, and automation.
  • Ensure that JSON template examples are annotated to indicate any OS-specific settings or requirements.
GitHub Create Pull Request
← Previous Page 68 of 99 Next →