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 301-325 of 1305 flagged pages
Service Fabric Azure Service Fabric Docker Compose Deployment Preview ...ticles/service-fabric/service-fabric-docker-compose.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 both PowerShell and Service Fabric CLI (sfctl) examples for deploying Docker Compose files, but PowerShell examples are presented first and in greater detail. PowerShell is a Windows-centric tool, while sfctl is cross-platform. There are no explicit Linux/macOS-specific instructions or examples, and no mention of Linux shell alternatives for PowerShell commands.
Recommendations
  • Present sfctl (Service Fabric CLI) examples before PowerShell, as sfctl is cross-platform and more relevant to Linux/macOS users.
  • Clarify that PowerShell commands are Windows-specific, and that sfctl is recommended for Linux/macOS environments.
  • Add explicit Linux/macOS instructions, such as how to install sfctl and prerequisites for running Service Fabric Compose deployments on those platforms.
  • Consider providing Bash shell examples for common tasks if applicable.
  • Mention any limitations or differences for Linux/macOS users, if present.
Service Fabric Networking patterns for Azure Service Fabric ...s/service-fabric/service-fabric-patterns-networking.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 only PowerShell-based deployment examples and references Windows-specific tools (e.g., RDP, Windows command prompt for ping). There are no equivalent examples for Linux/macOS users (such as Azure CLI or Bash), and Windows tools are mentioned first and exclusively. This creates friction for non-Windows users, as they must translate instructions or find alternative tooling.
Recommendations
  • Add Azure CLI (az) examples alongside PowerShell for all deployment steps.
  • Include Bash shell commands for template deployment and network testing (e.g., ping, ssh).
  • Mention cross-platform remote access methods (e.g., SSH for Linux VMs) in addition to RDP.
  • Clarify that PowerShell examples are for Windows users, and provide links or instructions for Linux/macOS users.
  • Consider restructuring examples so that cross-platform tools (Azure CLI) are shown first or equally.
Service Fabric Manage apps for multiple environments ...e-fabric-manage-multiple-environment-app-configuration.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 examples for managing application parameters in Azure Service Fabric, with a notable emphasis on Windows-centric tools and workflows. PowerShell is mentioned first for application creation, and Visual Studio (a Windows-first IDE) is referenced for parameter management. While sfctl and Jenkins are mentioned, Linux-native examples and workflows are less prominent, and the ordering favors Windows tools.
Recommendations
  • Provide explicit Linux/macOS command-line examples for parameter passing, such as using sfctl with install.sh, and clarify how Linux users can replicate Visual Studio/PowerShell workflows.
  • Add sample shell scripts (bash) for parameter substitution and deployment, highlighting cross-platform approaches.
  • Reorder examples so that Linux-native tools (sfctl, Jenkins) are presented before or alongside Windows tools.
  • Clarify which tools are cross-platform and which are Windows-only, to help users choose appropriate workflows.
Service Fabric Azure Service Fabric hosting activation and deactivation life cycle ...les/service-fabric/service-fabric-hosting-lifecycle.md
Medium Priority View Details →
Scanned: 2026-02-16 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page is generally platform-neutral in its conceptual explanations, but the 'Next steps' section and some linked references emphasize PowerShell for deployment/removal tasks, which is traditionally Windows-centric. There are no explicit Linux or cross-platform CLI examples or references, and the only advanced example for downloading a ServicePackage links to a PowerShell cmdlet. This creates friction for Linux/macOS users seeking parity.
Recommendations
  • Add equivalent Linux/macOS instructions and examples for deploying/removing applications, such as using Azure CLI or Service Fabric CLI (sfctl).
  • Include references to cross-platform tools and commands alongside PowerShell, especially in 'Next steps' and practical sections.
  • Clarify which steps or tools are platform-specific and provide alternatives where possible.
  • Link to documentation for Linux clusters and their management tools.
Service Fabric Manage certificates in a Service Fabric cluster ...vice-fabric/cluster-security-certificate-management.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 Windows First
Summary
The documentation page provides extensive PowerShell examples and references Windows-specific tools (such as the Key Vault VM extension for Windows and S-channel), with minimal or no coverage of Linux/macOS equivalents. Windows terminology and mechanisms are presented first and in detail, while Linux-specific guidance is largely absent. The certificate provisioning and management flows are described primarily in the context of Windows VM/VMSS, and troubleshooting/programmatic examples are exclusively PowerShell-based.
Recommendations
  • Add equivalent Bash/CLI examples for certificate enrollment, provisioning, and management, especially for Azure CLI and REST API usage.
  • Explicitly document how certificate provisioning and autorollover work for Linux-based Service Fabric clusters, including supported extensions and mechanisms.
  • Clarify any Windows-only limitations or features, and provide guidance for Linux/macOS users where parity is possible.
  • Include troubleshooting steps and FAQ entries relevant to Linux environments.
  • Reference and link to Linux-specific documentation for Key Vault VM extensions (if available) and Service Fabric certificate management.
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-02-16 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides examples for configuring Service Fabric managed cluster node types using Azure Portal, ARM templates, and PowerShell. PowerShell is the only CLI example shown, with no mention of Azure CLI or Bash equivalents. PowerShell is presented as the sole scripting option for command-line operations, which may create friction for Linux/macOS users. The ordering of examples also tends to show PowerShell before other CLI options, reinforcing Windows-first patterns.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all command-line operations (add, remove, scale, configure node types).
  • Explicitly mention that PowerShell commands can be run cross-platform using PowerShell Core, or provide Bash/CLI alternatives.
  • Clarify whether any steps are Windows-only, or if all operations are supported on Linux/macOS.
  • Consider including a section on using Azure CLI for Service Fabric managed clusters, or linking to relevant CLI documentation.
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-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 provides several examples and troubleshooting steps that are Windows-centric, such as referencing the Windows certificate store (LocalMachine\My), Win32 CryptoAPI, and Windows event logs. Linux equivalents are mentioned only briefly or as afterthoughts, and there are no concrete Linux command-line examples or troubleshooting guidance. This may create friction for Linux cluster administrators.
Recommendations
  • Provide explicit Linux examples for certificate storage, retrieval, and troubleshooting (e.g., using /var/lib/sfcerts, openssl, or Linux logging tools).
  • When referencing certificate stores, always mention both Windows and Linux paths equally and provide details for both.
  • Include Linux-specific troubleshooting steps and log file locations, not just Windows Event Log channels.
  • If referencing Windows APIs (e.g., CertGetCertificateChain), clarify the Linux equivalent or note how Service Fabric handles this on Linux.
  • Add examples using Linux tools (e.g., openssl, keytool) for certificate inspection and validation.
Service Fabric Azure Service Fabric container image management .../articles/service-fabric/container-image-management.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 references Windows container base images (microsoft/windowsservercore, microsoft/nanoserver) as default exclusions in cleanup, but does not mention Linux container base images or provide Linux-specific guidance. No examples or discussion of Linux container image management, nor parity in exclusion patterns for common Linux images (e.g., Ubuntu, Alpine) are provided.
Recommendations
  • Add examples or mention of Linux container base images (such as 'docker.io/library/ubuntu', 'docker.io/library/alpine') in the 'ContainerImagesToSkip' setting.
  • Clarify whether the cleanup settings and behaviors apply equally to Linux containers, and if not, provide Linux-specific guidance.
  • Provide examples of container image management for both Windows and Linux containers to ensure parity.
  • Explicitly state platform limitations if any features are Windows-only.
Scanned: 2026-02-16 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page is primarily focused on deploying custom Windows images in Azure Service Fabric Managed Clusters. Windows terminology and examples are presented first and most prominently. The PowerShell example for role assignment is given without a Linux CLI equivalent, and the text repeatedly refers to 'custom windows images' rather than generic or Linux images. However, there are references and links to Linux custom image creation and Azure CLI usage, indicating partial Linux support.
Recommendations
  • Provide equivalent Azure CLI examples for role assignment and other operations alongside PowerShell.
  • Clarify that custom images can be Linux-based as well, and update language to be OS-neutral where appropriate.
  • Add explicit examples and guidance for deploying Linux custom images, including ARM template snippets and prerequisites.
  • Ensure links to Linux documentation are as prominent as Windows documentation.
  • Review terminology to avoid defaulting to 'Windows' unless the feature is Windows-only.
Service Fabric Service Fabric Explorer blocking operations ...ged-cluster-service-fabric-explorer-blocking-operation.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 page provides management instructions for Service Fabric Explorer and ARM-managed clusters, consistently referencing Az PowerShell cmdlets (e.g., Remove-AzResource, AzSF PowerShell) for resource operations. While the az CLI is mentioned once for deleting applications, the majority of examples and guidance prioritize PowerShell tools, which are more commonly used on Windows. There are no explicit Linux/macOS examples or references to cross-platform alternatives for provisioning, scaling, or deleting resources.
Recommendations
  • Add explicit az CLI examples for all operations (provisioning, scaling, deleting) alongside PowerShell cmdlets.
  • Clarify that Az PowerShell cmdlets can be used on Linux/macOS via PowerShell Core, or provide links to relevant installation guides.
  • Where possible, mention ARM template usage with cross-platform deployment tools (e.g., Azure CLI, Bicep).
  • Ensure that guidance for managing Service Fabric resources is equally accessible to Linux/macOS users.
Service Fabric Describing Azure Service Fabric apps and services ...ic/service-fabric-application-and-service-manifests.md
Medium Priority View Details →
Scanned: 2026-02-16 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation is generally cross-platform, focusing on XML manifest structure and concepts. However, there is a notable bias in the warning that recommends using Visual Studio and a Windows file path to open the Service Fabric XSD schema for authoring manifests. This assumes the user is on Windows and using Visual Studio, with no mention of Linux or cross-platform alternatives. Additionally, the PowerShell module is mentioned as a way to create services, but no Linux/CLI equivalent is provided or referenced.
Recommendations
  • Provide guidance for Linux/macOS users on how to validate or edit Service Fabric manifest XML files, such as using VS Code (cross-platform) or other XML editors, and where to find the XSD schema on non-Windows systems.
  • When referencing PowerShell modules, also mention equivalent Azure CLI or REST API methods for creating services, if available.
  • Clarify whether the manifest authoring and validation steps are supported on Linux/macOS, and provide platform-agnostic instructions where possible.
Service Fabric Monitor Azure Service Fabric ...main/articles/service-fabric/monitor-service-fabric.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 generally covers both Windows and Linux clusters, but there are several areas where Windows tools and patterns are mentioned first or exclusively, and Linux equivalents are not always given equal prominence or detail. Windows-specific tools (such as EventStore APIs, Event Viewer, Diagnostics Agent) are described in detail, while Linux alternatives (such as Syslog, LTTng) are referenced but not explained or linked as thoroughly. Some example/tutorial links focus on Windows/.NET, and Linux-specific guidance is less visible.
Recommendations
  • Ensure Linux monitoring tools and patterns are described with equal detail and clarity as Windows equivalents.
  • Provide Linux-specific examples and tutorials, especially for cluster monitoring and application instrumentation.
  • Where Windows tools (e.g., Event Viewer, Diagnostics Agent) are mentioned, add corresponding Linux guidance (e.g., Syslog, LTTng, Linux agent configuration) and link to relevant documentation.
  • Avoid listing Windows tools or examples first unless there is a technical reason; alternate order or group by OS.
  • Add explicit Linux-focused sample queries and alert rules where possible.
Service Fabric RunToCompletion semantics and specifications ...blob/main/articles/service-fabric/run-to-completion.md
Medium Priority View Details →
Scanned: 2026-02-16 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page provides RunToCompletion semantics for Service Fabric containers and guest executables, but all code examples, container images, and tooling references are Windows-centric. Windows container images and Windows-specific commands (cmd, set, ping) are used exclusively, and PowerShell is the only CLI example for querying deployment status. No Linux container or Linux tooling examples are provided, nor is Linux compatibility discussed.
Recommendations
  • Add equivalent Linux container examples using popular Linux base images (e.g., Ubuntu, Alpine) and shell commands (bash, echo, ping).
  • Clarify whether RunToCompletion semantics are supported for Linux containers and guest executables, and provide explicit guidance for Linux users.
  • Include Linux CLI examples (e.g., using Bash or Azure CLI) for querying deployment status, or reference cross-platform tools.
  • Mention any limitations or differences in behavior between Windows and Linux environments for RunToCompletion.
  • If Linux support is limited, state this clearly at the top of the article.
Service Fabric Learn about Azure Service Fabric application security ...ric/service-fabric-application-and-service-security.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 covers Azure Service Fabric application security in a cross-platform context, but there is a noticeable Windows bias. Windows-specific features (such as AD accounts, gMSA, BitLocker, and references to Windows standalone clusters) are discussed in detail, while Linux equivalents are either missing, mentioned only briefly, or flagged as TODOs. Examples and guidance for Linux users (e.g., disk encryption, user accounts, container security) are less comprehensive or absent.
Recommendations
  • Add explicit Linux examples for securing application data at rest (disk encryption) and clarify supported tools and patterns for Linux clusters.
  • Provide parity in user account and group management guidance for Linux clusters, including how to run services under different user accounts on Linux.
  • Include Linux-specific instructions and examples for certificate management and container security.
  • Ensure that all code snippets and configuration examples are applicable to both Windows and Linux, or provide separate examples for each platform.
  • Address the TODOs regarding disk encryption on Linux clusters with concrete guidance and links.
Service Fabric Application upgrade: upgrade parameters ...abric/service-fabric-application-upgrade-parameters.md
Medium Priority View Details →
Scanned: 2026-02-16 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page presents upgrade parameters for Service Fabric applications, but it displays a notable Windows bias. PowerShell and Visual Studio (Windows tools) are discussed first and in greater detail, with extensive parameter tables and explanations. SFCTL (the cross-platform CLI) is covered only after the Windows tools, and its section is less prominent and less detailed. There are no explicit Linux/macOS-specific examples or walkthroughs in the main content, though a Linux CLI tutorial is linked in 'Next steps'.
Recommendations
  • Reorganize the page to present SFCTL (cross-platform CLI) examples and parameters before or alongside PowerShell/Visual Studio, rather than after them.
  • Provide explicit Linux/macOS usage examples for SFCTL, including sample commands and parameter usage.
  • Clarify that SFCTL is the recommended tool for Linux/macOS users, and highlight its parity with PowerShell.
  • Add a comparison table showing which tools are available on which platforms.
  • Ensure that parameter explanations for SFCTL are as detailed as those for PowerShell/Visual Studio.
Service Fabric Advanced Application Upgrade Topics ...-fabric/service-fabric-application-upgrade-advanced.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 for advanced Service Fabric application upgrade topics relies heavily on PowerShell cmdlet examples (e.g., New-ServiceFabricService, Update-ServiceFabricService, Start-ServiceFabricApplicationUpgrade), which are Windows-centric. There are no equivalent examples or guidance for Linux/macOS users, such as using the Service Fabric CLI (sfctl) or REST APIs. The documentation also references Visual Studio for diff package upgrades, another Windows-first tool, and consistently presents Windows tools and patterns before any mention of cross-platform alternatives.
Recommendations
  • Add equivalent examples using the Service Fabric CLI (sfctl), which is cross-platform and supported on Linux/macOS.
  • Include REST API examples for relevant operations (e.g., creating/upgrading services, application upgrades).
  • Mention and link to documentation for Linux/macOS deployment workflows, including how to perform upgrades without PowerShell or Visual Studio.
  • Clarify which operations are possible on Linux clusters and provide guidance for Linux users where PowerShell/Visual Studio are not available.
  • Reorder sections or add notes to ensure Linux/macOS alternatives are presented alongside or before Windows-specific tools.
Scanned: 2026-02-16 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides links to application upgrade tutorials using Visual Studio and PowerShell, both of which are primarily Windows-centric tools. There are no explicit Linux/macOS examples or equivalent upgrade instructions using cross-platform tools (e.g., Azure CLI, Bash, or SDKs). The serialization guidance is focused on C# and .NET, but this is appropriate for Service Fabric workloads. However, the upgrade guidance implicitly prioritizes Windows tools.
Recommendations
  • Add upgrade instructions or links for Linux/macOS users, such as using Azure CLI, Bash scripts, or cross-platform SDKs.
  • Clarify whether PowerShell examples are compatible with PowerShell Core on Linux/macOS, or provide alternatives.
  • Consider including upgrade walkthroughs using Visual Studio Code (cross-platform) or other non-Windows IDEs.
  • Explicitly mention if Service Fabric application upgrades can be performed from Linux/macOS, and provide relevant guidance.
Service Fabric Service Fabric application upgrade ...s/service-fabric/service-fabric-application-upgrade.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 provides PowerShell-only examples and references to Windows-specific tools (e.g., http.sys), with no equivalent CLI or Linux-native commands. There are no Linux or cross-platform examples for performing Service Fabric application upgrades, which may hinder Linux/macOS users.
Recommendations
  • Add equivalent examples using Azure CLI or Service Fabric CLI (sfctl), which are cross-platform.
  • Explicitly mention if certain upgrade operations are only supported via PowerShell/Windows, and provide alternatives or workarounds for Linux users.
  • Clarify any Windows-only limitations (e.g., http.sys) and, where possible, suggest Linux-compatible approaches.
  • Include links to Linux/macOS-specific guidance for Service Fabric application management.
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 page for restoring backup in Azure Service Fabric exclusively provides PowerShell-based examples and instructions, relying on the Microsoft.ServiceFabric.Powershell.Http module and Windows-specific tooling (e.g., PowerShell, certificate thumbprints, Windows-style paths). No Linux/macOS CLI, Bash, or cross-platform REST API examples are provided, nor is there guidance for Linux users on how to perform equivalent operations. The REST API is referenced, but only invoked via PowerShell, and there are no explicit instructions or code samples for using curl or other cross-platform tools.
Recommendations
  • Add cross-platform examples using Bash and curl for REST API calls, showing how to authenticate and trigger restore operations from Linux/macOS.
  • Document any prerequisites or limitations for Linux/macOS users, including how to obtain and use certificates for authentication.
  • Mention and link to any available Service Fabric CLI tools that work on Linux/macOS, or clarify if PowerShell is required.
  • Provide guidance for Linux users on installing PowerShell Core if it is required, and clarify compatibility.
  • Ensure REST API documentation is referenced with clear instructions for non-Windows environments.
Scanned: 2026-02-16 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 Resource Manager templates, but PowerShell is emphasized for cluster upgrades and VM configuration. Windows-specific tools and registry keys are mentioned without Linux equivalents. Windows configuration examples and PowerShell commands are presented before or instead of Linux alternatives, creating friction for Linux users.
Recommendations
  • Include Linux-specific upgrade instructions and examples, such as using Bash or relevant Linux commands for cluster upgrades.
  • Provide Linux VM configuration examples alongside Windows registry and osProfile settings.
  • When referencing PowerShell, also show Bash or CLI alternatives for Linux clusters.
  • Clarify which steps are Windows-only and which are cross-platform, to help Linux users navigate the documentation.
  • Ensure parity by linking to Linux-specific resources and tutorials where appropriate.
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 for on-demand backup in Azure Service Fabric is heavily focused on PowerShell-based workflows, with all code examples and module instructions provided exclusively for PowerShell. There are no Bash, CLI, or Linux/macOS-compatible examples or instructions, and PowerShell is presented as the default and only method for scripting and API calls. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer native tools.
Recommendations
  • Add equivalent examples using Azure CLI, Bash, or curl for REST API calls, making it clear how Linux/macOS users can perform the same operations.
  • Document prerequisites and installation steps for PowerShell Core (pwsh) on Linux/macOS, if PowerShell is required, and clarify any limitations.
  • Where possible, provide cross-platform guidance for connecting to Service Fabric clusters and triggering backups, including authentication methods compatible with Linux/macOS.
  • Explicitly state whether the Microsoft.ServiceFabric.Powershell.Http module is supported on PowerShell Core and non-Windows platforms, and offer alternatives if not.
Service Fabric Understanding periodic backup configuration ...-fabric-backuprestoreservice-configure-periodic-backup.md
Medium Priority View Details →
Scanned: 2026-02-16 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page is generally platform-neutral, focusing on Service Fabric's backup configuration concepts and REST API usage. However, in the 'File share' backup storage section, only Windows-style file share paths (\\StorageServer\BackupStore) and Windows authentication mechanisms are described. There are no examples or guidance for Linux-based file shares (e.g., SMB/CIFS mounts, NFS), nor is there mention of how Linux clusters might configure or access file shares. This creates a subtle but notable bias toward Windows environments.
Recommendations
  • Add examples and guidance for configuring file share backup storage using Linux-based clusters, including supported file share types (e.g., SMB/CIFS, NFS) and path formats.
  • Clarify whether Linux clusters can use file share backup storage, and if so, provide authentication and access instructions relevant to Linux.
  • If file share backup storage is Windows-only, explicitly state this limitation to inform Linux/macOS users.
  • Consider including both Windows and Linux path examples and authentication methods where applicable.
Service Fabric Change Azure Service Fabric cluster settings ...rvice-fabric/service-fabric-cluster-fabric-settings.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 page provides a comprehensive reference for Service Fabric cluster settings, covering both Azure-hosted and standalone clusters. However, there is evidence of Windows bias: Windows terminology and tools (such as certificate store names like 'MY', 'LocalMachine', and references to NTLM authentication) are used throughout, and Windows-specific defaults are often mentioned before Linux equivalents. Some parameters and guidance reference Windows APIs (e.g., CertGetCertificateChain), and Windows-only features (like Windows Update integration) are present without clear Linux alternatives or parity. Linux-specific guidance is minimal, though some Linux settings are mentioned (e.g., LinuxExternalExecutablePath, EnforceLinuxMinTlsVersion).
Recommendations
  • Where Windows-specific terms (e.g., certificate store names, NTLM authentication) are used, add Linux equivalents or clarify Linux behavior.
  • Ensure Linux-specific settings are documented with equal detail and visibility, including certificate management, authentication, and file storage.
  • When referencing Windows APIs or tools, provide Linux alternatives or note if the feature is not applicable on Linux.
  • Add explicit notes or tables indicating which settings are platform-specific, and provide Linux/macOS guidance where possible.
  • Review default values and descriptions to ensure Linux defaults are equally clear and not overshadowed by Windows defaults.
Service Fabric Node types and virtual machine scale sets ...les/service-fabric/service-fabric-cluster-nodetypes.md
Medium Priority View Details →
Scanned: 2026-02-16 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page provides general information about Azure Service Fabric node types and virtual machine scale sets, but exhibits Windows bias in several areas. Examples and guidance reference Windows paths (e.g., 'D:\\SvcFab'), and the 'Next steps' section links to PowerShell scripts for Windows-specific tasks (changing RDP port ranges, admin username/password), without Linux or cross-platform alternatives. Linux-specific guidance is minimal, and Windows tools/patterns are mentioned first or exclusively.
Recommendations
  • Provide equivalent Linux/Bash examples for remote connection, port range changes, and admin credential updates.
  • Clarify when steps are Windows-only and offer Linux/macOS alternatives or links.
  • Use platform-neutral paths and examples where possible, or show both Windows and Linux variants.
  • Add guidance for managing Service Fabric clusters on Linux VM scale sets, including SSH access and Linux admin user management.
Service Fabric Health monitoring in Service Fabric ...s/service-fabric/service-fabric-health-introduction.md
Medium Priority View Details →
Scanned: 2026-02-16 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 is cross-platform, the exclusive use of PowerShell in the example creates friction for Linux/macOS users who cannot use PowerShell natively.
Recommendations
  • Add equivalent examples using REST API or Service Fabric CLI (sfctl), which are cross-platform and supported on Linux/macOS.
  • Clearly indicate that PowerShell is Windows-specific and provide links or references to Linux/macOS-compatible tools.
  • Where possible, show REST or sfctl examples before or alongside PowerShell examples to improve parity.