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 151-175 of 2475 flagged pages
Service Fabric Health monitoring in Service Fabric ...s/service-fabric/service-fabric-health-introduction.md
Medium Priority View Details →
Scanned: 2026-03-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-only example for reporting and evaluating application health in Service Fabric, without offering equivalent Linux/macOS CLI or REST API examples. While Service Fabric supports cross-platform management, the exclusive use of PowerShell creates friction for non-Windows users.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl) for Linux/macOS.
  • Include REST API sample requests for health reporting and querying.
  • Mention cross-platform tools and clarify which methods are available on all OSes.
  • Ensure examples for health reporting and querying are shown for both Windows (PowerShell) and Linux/macOS (CLI/REST).
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-03-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 PowerShell-based examples and references for managing Service Fabric services, with no equivalent examples for Linux/macOS users (e.g., Azure CLI or Bash). All command-line instructions and links are PowerShell-centric, which may create friction for users on non-Windows platforms.
Recommendations
  • Add Azure CLI or REST API command examples for creating and managing services, especially for operations currently shown only with PowerShell.
  • Clarify in each example whether the command is Windows-only, and provide platform-agnostic alternatives where possible.
  • Reference cross-platform tools (e.g., Azure CLI, REST API) before or alongside Windows-specific tools like PowerShell.
  • Add a note or section summarizing cross-platform management options for Service Fabric clusters.
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-03-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 page for 'Replica soft delete for enhanced data protection in Service Fabric' demonstrates notable Windows bias. All command-line/API examples reference PowerShell cmdlets (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica), with no mention of Linux equivalents or cross-platform CLI usage. The administrative workflow is described primarily in terms of PowerShell and Windows tooling, and Windows-specific terminology is used throughout. There are no examples or guidance for Linux/macOS users, nor are FabricClient API usage patterns shown in a cross-platform context.
Recommendations
  • Add examples for managing replica soft delete using Service Fabric CLI (sfctl), which is cross-platform and supported on Linux/macOS.
  • Document how to use FabricClient APIs in .NET Core or other cross-platform languages, including sample code for Linux/macOS environments.
  • Clarify whether the PowerShell cmdlets are available or supported on Linux (via PowerShell Core), or provide alternative instructions if not.
  • Include explicit notes or sections for Linux/macOS users, highlighting any differences or limitations.
  • Where possible, show Linux commands and configuration file edits alongside Windows/PowerShell examples.
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-03-10 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 and retrieving the cluster manifest. It mentions Visual Studio (a Windows-centric tool) for publishing to Azure, and links to PowerShell-based deployment guidance as the main 'Next steps'. While REST and .NET are briefly mentioned, Linux-native tools and workflows (such as Azure CLI or Bash) are absent. The examples and guidance are Windows-first, creating friction for Linux/macOS users.
Recommendations
  • Add Azure CLI examples for retrieving the cluster manifest and deploying applications.
  • Include Bash or cross-platform scripting examples alongside PowerShell.
  • Mention Linux/macOS-compatible tools for Service Fabric management.
  • Provide guidance for deploying from non-Windows environments (e.g., VS Code, CLI).
  • Ensure 'Next steps' links include Linux-friendly options, not just PowerShell.
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-03-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 Azure Service Fabric. However, there is a notable Windows bias in several sections: HTTP.sys (a Windows-only technology) is discussed in depth, with explicit mention of Windows tools (netsh), Windows kernel drivers, and Windows-specific endpoint configuration. HTTP.sys examples and explanations are presented before Kestrel in some sections, and Windows-specific configuration steps (such as URL reservation and endpoint setup) are detailed. While Kestrel is recommended for Linux and cross-platform scenarios, the prominence and depth of Windows-specific HTTP.sys content may create friction for Linux/macOS users. PowerShell or Windows command-line tools are referenced for endpoint management, but Linux equivalents are not provided.
Recommendations
  • Clearly mark HTTP.sys sections as Windows-only and direct Linux/macOS users to Kestrel sections.
  • Move Kestrel (cross-platform) examples and explanations before HTTP.sys (Windows-only) in each relevant section.
  • Provide explicit guidance for Linux/macOS users, including any necessary Service Fabric configuration steps for Kestrel on those platforms.
  • Avoid referencing Windows tools (such as netsh) without mentioning that they are not applicable to Linux/macOS.
  • Add a summary table or section early in the document clarifying which features are Windows-only and which are cross-platform.
  • Ensure all code samples for service communication are available for both Kestrel and HTTP.sys, with clear platform applicability.
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-03-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 Service Fabric health using C# APIs and PowerShell, with all command-line examples shown in PowerShell and Windows-style prompts. There are no equivalent examples for Linux/macOS users (e.g., Bash, Azure CLI, or cross-platform PowerShell Core), and the PowerShell examples use Windows-specific syntax and paths. REST is mentioned but not exemplified. This creates friction for Linux/macOS users, who may not have access to Windows PowerShell or may use different tools.
Recommendations
  • Add equivalent examples using Bash or Azure CLI for Linux/macOS users where possible.
  • Clarify whether PowerShell Core (pwsh) is supported cross-platform, and if so, provide examples using it with non-Windows prompts.
  • Provide explicit REST API request examples (e.g., using curl) to demonstrate a fully cross-platform approach.
  • Note any platform-specific requirements or limitations for Service Fabric management tools.
  • Where possible, use neutral prompts (e.g., $ or #) or clarify that commands are not Windows-specific.
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-03-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation focuses exclusively on Visual Studio workflows (Build/Rebuild/F5/Ctrl+F5/Publish) and references PowerShell cmdlets for service creation, both of which are Windows-centric. There are no examples or guidance for Linux/macOS users, nor any mention of cross-platform tooling or workflows for Service Fabric application configuration. The documentation assumes the use of Visual Studio, which is primarily available on Windows, and does not provide alternative instructions for Linux/macOS environments.
Recommendations
  • Add explicit guidance for Linux/macOS users, including how to configure and deploy Service Fabric applications without Visual Studio.
  • Provide CLI-based examples (using Azure CLI or cross-platform PowerShell Core) for managing StartupServices.xml and ApplicationManifest.xml.
  • Clarify whether StartupServices.xml workflows are supported or possible on Linux/macOS, and if not, provide alternatives.
  • Mention any cross-platform tools or editors that can be used for editing manifest files and deploying Service Fabric applications.
  • If the feature is Windows-only, state this clearly at the top of the documentation.
GitHub Create Pull Request
Service Fabric Learn Azure Service Fabric terminology ...es/service-fabric/service-fabric-technical-overview.md
Medium Priority View Details →
Scanned: 2026-03-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page is generally cross-platform and describes Service Fabric concepts applicable to both Windows and Linux. However, there is a subtle Windows bias in the 'Node' section, where Windows-specific tools and executables (FabricHost.exe, Fabric.exe, FabricGateway.exe) are described as auto-start Windows services, with no mention of Linux equivalents or how nodes operate on Linux. Windows terminology and patterns are presented first or exclusively in some places, such as referencing EXE/DLL files and Windows services, while Linux-specific details are missing or less prominent.
Recommendations
  • Add explicit descriptions of how Service Fabric nodes operate on Linux, including any differences in service management, process startup, and relevant Linux tools or patterns.
  • When referencing executable files, clarify that Linux deployments use ELF binaries and describe any differences in packaging or execution.
  • Ensure that examples and terminology are presented in a platform-neutral way, or provide parallel Linux-specific examples and explanations where Windows-specific terms are used.
  • Mention Linux service management (e.g., systemd) where Windows services are discussed, to help Linux users understand equivalent concepts.
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-03-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 tooling, specifically Visual Studio and PowerShell, for configuring and upgrading Service Fabric applications. All examples and upgrade instructions reference Windows tools, with no mention of Linux/macOS equivalents or cross-platform CLI options. Linux users are not provided with guidance or examples for performing upgrades, creating friction for non-Windows environments.
Recommendations
  • Add instructions and examples for upgrading Service Fabric applications using Azure CLI or Service Fabric CLI (sfctl), which are cross-platform.
  • Include guidance for configuring upgrade parameters and health policies without Visual Studio, such as editing manifest files and deploying via CLI.
  • Mention any limitations or differences for Linux/macOS users, and provide links to relevant documentation for non-Windows environments.
  • Present PowerShell and Visual Studio instructions alongside (not before) cross-platform alternatives to ensure parity.
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-03-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page provides Service Fabric manifest XML examples that are platform-agnostic, but when it comes to deployment and parameterization, it only shows PowerShell (Windows) commands (e.g., New-ServiceFabricApplication) and references Windows file paths for the schema. Linux equivalents (such as Azure CLI or sfctl) are not mentioned, and the PowerShell example is given without Linux parity. The documentation also references the Service Fabric SDK schema path using a Windows directory, with only a brief note about the Linux certificate store location.
Recommendations
  • Add equivalent Linux/macOS deployment examples using Azure CLI (az sf application create) or sfctl.
  • When referencing file paths (such as the Service Fabric SDK schema), provide both Windows and Linux paths.
  • If showing PowerShell examples, always follow with Linux/macOS equivalents or a note linking to cross-platform instructions.
  • Clarify any platform-specific behaviors, such as certificate store handling, in all relevant sections.
GitHub Create Pull Request
Service Fabric Monitor Azure Service Fabric ...main/articles/service-fabric/monitor-service-fabric.md
Medium Priority View Details →
Scanned: 2026-03-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation covers monitoring for Azure Service Fabric across Windows and Linux clusters, but there is a noticeable Windows bias. Windows-specific tools (such as EventStore APIs, Event Log, Diagnostics Agent) are mentioned first or in more detail, and some examples/tutorials focus on .NET applications (typically Windows-centric). Linux equivalents are referenced, but often as secondary notes or with less detail. Some sections lack explicit Linux examples or guidance, especially around cluster monitoring and event access.
Recommendations
  • Provide Linux-specific examples and walkthroughs alongside Windows ones, especially for cluster monitoring and event access.
  • Ensure Linux tools (such as LTTng, Syslog, and relevant agents) are described in equal detail and prominence as Windows tools.
  • Add tutorials for monitoring Service Fabric applications on Linux, including instrumenting with Application Insights and logging frameworks.
  • Clarify which features are Windows-only and which are cross-platform, to help users understand parity.
  • Include sample queries and alert rules that are applicable to Linux clusters, and reference Linux event sources explicitly.
GitHub Create Pull Request
Service Fabric RunToCompletion semantics and specifications ...blob/main/articles/service-fabric/run-to-completion.md
Medium Priority View Details →
Scanned: 2026-03-09 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page for RunToCompletion semantics in Azure Service Fabric is notably Windows-centric. All code examples reference Windows containers (nanoserver), Windows-specific commands (cmd, set, ping), and Windows container compatibility. Query instructions are given only for PowerShell and C#, with no mention of Linux shell or cross-platform tools. There is no example or guidance for Linux containers or Linux-based Service Fabric clusters, despite Service Fabric supporting Linux containers.
Recommendations
  • Add equivalent examples using Linux containers (e.g., Ubuntu or Alpine images) and Linux shell commands.
  • Include instructions for querying deployment status using Linux tools (e.g., Bash, sfctl CLI).
  • Clarify whether RunToCompletion semantics are supported for Linux containers and, if so, provide relevant guidance.
  • Present examples for both Windows and Linux environments, or explicitly state if the feature is Windows-only.
  • Mention cross-platform tools (like sfctl) alongside PowerShell.
GitHub Create Pull Request
Service Fabric Advanced Application Upgrade Topics ...-fabric/service-fabric-application-upgrade-advanced.md
Medium Priority View Details →
Scanned: 2026-03-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 numerous PowerShell-based examples and references, with no equivalent CLI or Linux/macOS instructions. All command-line upgrade operations are shown using PowerShell cmdlets, and the workflow assumes familiarity with Windows tooling. There is no mention of Service Fabric CLI (sfctl) or Bash scripting, nor are Linux/macOS users guided on how to perform these tasks. The page also references Visual Studio as a deployment tool, which is primarily Windows-centric.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and supported on Linux/macOS.
  • Explicitly mention that PowerShell examples can be adapted for PowerShell Core on Linux/macOS, if applicable.
  • Provide Bash or shell script snippets for common upgrade tasks.
  • Include a section or note clarifying which tools are available for Linux/macOS users and link to relevant documentation.
  • When referencing Visual Studio, also mention cross-platform alternatives (e.g., VS Code, CLI tools) for non-Windows environments.
GitHub Create Pull Request
Service Fabric Cluster Resource Manager - Management Integration ...fabric-cluster-resource-manager-management-integration.md
Medium Priority View Details →
Scanned: 2026-03-09 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 partition health, using Windows-style paths and commands (e.g., 'PS C:\Users\User > Get-ServiceFabricPartitionHealth'). No equivalent Linux/macOS CLI example (such as Service Fabric CLI or REST API usage) is given. The example is presented early and exclusively, which may create friction for Linux/macOS users managing Service Fabric clusters.
Recommendations
  • Add equivalent Linux/macOS examples using Service Fabric CLI (sfctl) or REST API for querying partition health.
  • Mention cross-platform management tools and provide links or examples for Linux/macOS users.
  • Clarify that PowerShell is one option, and highlight alternatives for non-Windows environments.
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-03-09 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 is notable Windows bias: Windows-specific tools (e.g., PowerShell, Visual Studio) are mentioned before Linux equivalents, and Windows terminology (e.g., auto-start Windows service, FabricHost.exe) is used without parallel Linux explanations. Standalone cluster creation is only described for Windows, with Linux support explicitly missing. Examples and instructions often default to Windows-first, and Linux-specific guidance is limited or absent.
Recommendations
  • Provide Linux-specific examples and instructions alongside Windows ones, especially for cluster creation, management, and lifecycle operations.
  • Mention Linux tools (e.g., Bash, Linux CLI usage) equally with Windows tools like PowerShell.
  • Clarify when features or instructions are Windows-only, and provide alternative Linux guidance where possible.
  • Add links and references to Linux documentation and tutorials in 'Next steps' and throughout the article.
  • Use neutral language when describing concepts that apply to both platforms, and explicitly note differences where relevant.
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-03-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides upgrade guidance for Azure Service Fabric clusters, but exhibits mild Windows bias. Windows-specific tools (PowerShell) are mentioned alongside Azure CLI, but Linux-specific tools or examples are not provided. The section on OS image upgrades links only to Windows patching guidance, omitting Linux node upgrade information. Windows terminology and tools are referenced first or exclusively in some sections.
Recommendations
  • Add explicit Linux node upgrade guidance and link to relevant documentation for patching/upgrading Linux-based Service Fabric clusters.
  • Provide examples using Bash/Azure CLI for cluster management tasks, not just PowerShell.
  • Clarify when instructions or links are Windows-specific and provide Linux equivalents where possible.
  • Mention Linux support and limitations for Service Fabric clusters where relevant.
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-03-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page presents Windows/PowerShell examples first and in more detail, notably referencing the PowerShell cmdlet New-ServiceFabricApplication before mentioning sfctl (the cross-platform CLI). Visual Studio and PowerShell scripts are emphasized, which are primarily Windows tools, while Linux/macOS equivalents are less prominent. However, sfctl and Jenkins are mentioned, providing some Linux parity.
Recommendations
  • Present sfctl (the cross-platform CLI) examples before or alongside PowerShell examples.
  • Include explicit Linux/macOS command-line examples for application creation and parameter passing.
  • Clarify which tools are cross-platform and which are Windows-only, to help users choose the right workflow.
  • Expand on Jenkins usage with example scripts for parameter substitution, not just a brief mention.
  • Add guidance for configuring applications using Linux/macOS development environments.
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-03-09 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates notable Windows bias. All deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) with no mention of Azure CLI or other cross-platform tools. Application packaging instructions reference Visual Studio, a Windows-centric IDE, and do not provide alternatives for Linux/macOS users. There are no Linux/macOS-specific examples or guidance, and Windows tools and patterns are presented exclusively and first.
Recommendations
  • Add Azure CLI examples for deployment and deletion tasks alongside PowerShell.
  • Provide instructions for packaging Service Fabric applications using cross-platform tools (e.g., dotnet CLI, SF SDK, or manual zip commands).
  • Mention and link to Visual Studio Code or other cross-platform editors for application packaging.
  • Clearly indicate if certain steps are Windows-only and provide Linux/macOS alternatives where possible.
  • Consider including bash shell commands for file manipulation (zipping, renaming) and uploading blobs using Azure CLI.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Events ...es/service-fabric/service-fabric-diagnostics-events.md
Medium Priority View Details →
Scanned: 2026-03-09 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, with no mention of Linux equivalents or guidance for accessing Service Fabric events on Linux clusters. Windows tools and patterns are discussed first and exclusively, creating friction for Linux users seeking parity.
Recommendations
  • Add explicit guidance for accessing Service Fabric events on Linux clusters, including supported logging mechanisms (e.g., stdout, syslog, Azure Monitor integration for Linux).
  • Mention Linux-compatible diagnostic agents or methods, and clarify any differences in event collection or visualization.
  • Provide examples or links for querying and monitoring Service Fabric events on Linux, ensuring parity with Windows instructions.
  • If certain event types or logging channels are Windows-only, clearly state this and provide alternatives for Linux users.
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-03-09 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 schema file path is given only in Windows format. Linux-specific information is limited to a single note about certificate storage, and Linux deployment commands or examples are missing. Windows tools and patterns (PowerShell, Windows file paths) are mentioned first and exclusively in critical deployment sections.
Recommendations
  • Add equivalent Linux deployment examples using Azure CLI or bash scripts.
  • Mention Linux file paths and schema locations alongside Windows paths.
  • Clarify which steps or commands differ for Linux clusters, especially for endpoint and certificate configuration.
  • Provide links or references to Linux-specific Service Fabric tooling and documentation.
  • Ensure that Linux/macOS users can follow the deployment workflow without relying on Windows-only tools.
GitHub Create Pull Request
Service Fabric Azure Service Fabric infrastructure as Code Best Practices ...tps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-best-practices-infrastructure-as-code.md
Medium Priority View Details →
Scanned: 2026-03-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Service Fabric clusters, but PowerShell (a Windows-centric tool) is given a dedicated section and is the only scripting language shown for advanced cluster upgrade operations. Windows-specific registry settings and template properties are discussed in detail, while Linux equivalents are not mentioned. Windows configuration is described first and in more depth, with Linux-specific guidance only referenced via external links.
Recommendations
  • Provide equivalent Linux/bash examples for all PowerShell commands, especially for cluster upgrade operations.
  • Include Linux-specific configuration guidance (e.g., how to disable automatic updates on Linux VMSS nodes) alongside Windows instructions.
  • When discussing OS-specific settings (like registry keys or Windows Update), add parallel Linux instructions or explicitly state if not applicable.
  • Balance the order of presentation so that Linux and Windows are treated equally (e.g., alternate which OS is discussed first or present both together).
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-03-09 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation demonstrates a notable bias toward Windows environments and tooling. PowerShell is the only scripting example provided for certificate enrollment and management. The Key Vault VM extension is discussed exclusively in its Windows variant, and the documentation references Windows-specific certificate store concepts (e.g., 'LocalMachine', 'MY'). There is no mention of Linux equivalents, such as the Key Vault VM extension for Linux, nor are there any Bash/CLI examples. The documentation also discusses Windows-specific certificate linking and S-channel behaviors without referencing Linux or cross-platform considerations.
Recommendations
  • Provide equivalent Bash/Azure CLI examples for certificate enrollment and management, especially for tasks currently shown only in PowerShell.
  • Include guidance and examples for using the Key Vault VM extension for Linux (if supported), or clarify if autorollover and certificate provisioning are Windows-only.
  • When discussing certificate stores and provisioning, mention Linux equivalents (e.g., file paths, OpenSSL, or system trust stores) and how Service Fabric on Linux nodes should be configured.
  • If certain features are Windows-only, explicitly call this out at the start of relevant sections to set expectations for Linux/macOS users.
  • Add troubleshooting and FAQ entries relevant to Linux environments, or link to cross-platform documentation where appropriate.
GitHub Create Pull Request
Service Fabric Configure or modify a Service Fabric managed cluster node type ...vice-fabric/how-to-managed-cluster-modify-node-type.md
Medium Priority View Details →
Scanned: 2026-03-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides examples for managing Service Fabric managed cluster node types using the Azure Portal, ARM templates, and PowerShell. PowerShell is the only CLI tool shown for scripting/command-line automation, with no mention of Azure CLI, Bash, or cross-platform scripting alternatives. PowerShell examples are presented as the primary automation method, and there is no guidance for Linux/macOS users who may not have access to PowerShell or prefer other tools. This creates friction for non-Windows users, though the ARM template and Portal methods are cross-platform.
Recommendations
  • Add Azure CLI examples for all operations currently shown with PowerShell (e.g., adding/removing/scaling node types, configuring properties). Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that PowerShell examples require Azure PowerShell module, and provide guidance or links for installing PowerShell Core on Linux/macOS if PowerShell is to remain the only CLI example.
  • Where possible, clarify that ARM templates and the Azure Portal are fully cross-platform and can be used from any OS.
  • Consider reordering sections so that cross-platform methods (Portal, ARM template, Azure CLI) are presented before Windows-specific tools like PowerShell.
  • If some operations are only possible with PowerShell, clearly state this and provide workarounds or alternatives for Linux/macOS users.
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-03-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides examples and links primarily for Azure PowerShell modules when describing best practices for managing Service Fabric managed clusters. PowerShell is a Windows-centric tool, and its mention precedes alternatives like Azure CLI or sfctl. While Azure CLI and ARM/Bicep are referenced, the step-by-step guidance and linked examples focus on PowerShell, which may create friction for Linux/macOS users.
Recommendations
  • Add explicit Azure CLI command examples alongside PowerShell examples for all recommended actions (e.g., deleting NodeTypes, restarting/reimaging scale sets).
  • Ensure that CLI and cross-platform tools are mentioned equally or before PowerShell in guidance sections.
  • Clarify that Azure CLI and sfctl are fully supported on Linux/macOS and provide links to their documentation.
  • Where possible, provide code snippets for both PowerShell and CLI to improve accessibility.
GitHub Create Pull Request
Service Fabric X.509 Certificate-based Authentication in a Service Fabric Cluster ...ticles/service-fabric/cluster-security-certificates.md
Medium Priority View Details →
Scanned: 2026-03-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation provides thorough coverage of X.509 certificate-based authentication in Service Fabric clusters, but exhibits Windows bias in several areas. Windows terminology and tools (e.g., certificate store paths like LocalMachine\My, Win32 CryptoAPI references, and event log channels) are mentioned first or exclusively, with Linux equivalents only briefly referenced or omitted. Troubleshooting and configuration examples focus on Windows-specific patterns, and PowerShell/C++ error codes are given without Linux alternatives. While Linux is supported for Service Fabric, parity in examples and troubleshooting guidance is lacking.
Recommendations
  • Add Linux-specific certificate store paths and management instructions alongside Windows examples (e.g., expand on /var/lib/sfcerts).
  • Include troubleshooting steps for Linux nodes, such as relevant log locations and commands (e.g., journalctl, syslog, openssl).
  • Provide Linux equivalents for error codes and certificate provider types, or clarify cross-platform differences.
  • Reference Linux certificate management tools (e.g., openssl, certutil) and include sample commands.
  • Ensure that configuration examples and explanations are platform-neutral or explicitly show both Windows and Linux variants.
GitHub Create Pull Request
← Previous Page 7 of 99 Next →