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 1876-1900 of 2475 flagged pages
Service Fabric Azure Service Fabric Auto Scaling Services and Containers ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-autoscaling.md
Medium Priority View Details →
Scanned: 2026-02-04 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed examples for configuring auto scaling policies in Azure Service Fabric using application manifests, C# APIs, and PowerShell. However, all CLI/script examples use PowerShell, which is Windows-centric, and there are no equivalent Linux shell (bash/CLI) examples. The documentation does mention that resource monitoring is supported for containerized applications on Linux, but practical guidance for Linux users is missing. The ordering of examples also puts PowerShell before any Linux alternatives (which are absent), reinforcing a Windows-first approach.
Recommendations
  • Add equivalent examples using Azure CLI or bash scripts for Linux users, especially for service creation and scaling policy updates.
  • Explicitly document any differences or limitations for Linux clusters, including how to manage auto scaling policies from Linux environments.
  • Where PowerShell is used, provide a note or link to Linux-compatible tooling (e.g., Azure CLI, REST API) for parity.
  • Consider reordering examples or providing a clear separation between Windows and Linux workflows.
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-04 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 mention of Linux CLI equivalents (such as Azure CLI or Service Fabric CLI), nor any explicit Linux/macOS command-line examples. All command-line instructions and links are PowerShell-focused, which may create friction for Linux/macOS users.
Recommendations
  • Add equivalent Azure CLI (az sf) or Service Fabric CLI (sfctl) examples for creating and managing services, especially for commands currently shown only in PowerShell.
  • Explicitly mention cross-platform management options for Service Fabric clusters, including links to Linux/macOS tooling.
  • Where possible, provide both Windows (PowerShell) and cross-platform (CLI/REST) examples side by side.
  • Clarify in the 'Next steps' and relevant sections that PowerShell is not the only supported management interface, and link to Linux/macOS documentation.
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-04 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides only PowerShell-based deployment instructions and command-line examples, with no mention of Azure CLI, Bash, or Linux/macOS-compatible workflows. It also references Windows-specific tools (e.g., RDP, C: drive paths, and Windows command prompt syntax for ping), and does not offer equivalent Linux/macOS guidance for accessing VMs or running network tests.
Recommendations
  • Add Azure CLI (az) command examples alongside or in place of PowerShell commands for resource group and template deployments.
  • Include Linux/macOS-compatible instructions for accessing VMs (e.g., using SSH instead of RDP) and for running network tests (e.g., using ping from a Bash shell).
  • Use platform-neutral file paths in examples, or provide both Windows and Linux/macOS path formats.
  • Explicitly state that the templates and instructions are cross-platform, and clarify any steps that are Windows-specific.
  • Consider reordering examples or providing tabs for Windows and Linux/macOS workflows to improve parity.
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-04 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides certificate management guidance for Service Fabric clusters on Azure, with a strong emphasis on Windows-centric tooling and patterns. PowerShell is the only scripting language shown for programmatic certificate enrollment, and references to Windows-specific features (such as S-channel, certificate store locations, and Key Vault VM extension for Windows) are prevalent. The documentation does not provide equivalent Linux/bash examples or discuss Linux-specific certificate handling, which may create friction for users deploying Service Fabric clusters on Linux nodes or managing certificates from non-Windows environments.
Recommendations
  • Include bash/CLI examples for certificate enrollment and management alongside PowerShell scripts.
  • Clarify which steps and tooling are applicable to Linux-based Service Fabric clusters, and provide explicit Linux guidance where possible.
  • Reference the Key Vault VM extension for Linux (if available) or alternative mechanisms for Linux VMs, and link to relevant documentation.
  • Discuss certificate store locations and access control for Linux nodes, not just Windows certificate stores.
  • Where Windows-specific features (e.g., S-channel, CERT_RENEWAL_PROP_ID) are discussed, note their applicability and provide Linux alternatives or caveats.
GitHub Create Pull Request
Service Fabric Introduction to the Service Fabric Infrastructure Service .../articles/service-fabric/infrastructure-service-faq.md
Medium Priority View Details →
Scanned: 2026-02-04 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides a PowerShell-only example for bypassing Infrastructure Service throttling, with no equivalent CLI or Linux/macOS instructions. It references Service Fabric Explorer (a web tool, but often Windows-centric in usage) and omits any mention of Linux-native management tools or cross-platform command-line alternatives.
Recommendations
  • Provide equivalent Azure CLI or REST API examples for bypassing Infrastructure Service, suitable for Linux/macOS users.
  • Clarify whether the PowerShell command is required or if cross-platform alternatives exist.
  • Explicitly mention if Service Fabric Explorer and other tools are accessible and fully functional from non-Windows environments.
  • Add notes or links to Linux/macOS management guidance for Service Fabric clusters.
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-04 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page for Initializer CodePackages in Service Fabric provides examples and guidance exclusively for Windows containers, using Windows-specific images, file paths, and commands. There are no Linux container examples or references to Linux-compatible patterns, which creates friction for users deploying Service Fabric on Linux or with Linux containers.
Recommendations
  • Add equivalent examples using Linux containers (e.g., Ubuntu or Alpine images) to demonstrate Initializer CodePackages in a cross-platform manner.
  • Include Linux-compatible file paths and shell commands (e.g., /workspace/log.txt, echo, cat, tail, etc.) in the examples.
  • Clarify in the introduction whether Initializer CodePackages are supported for Linux containers, and if so, provide guidance for Linux users.
  • If there are limitations for Linux containers, explicitly state them and link to relevant documentation.
GitHub Create Pull Request
Service Fabric Custom Image .../articles/service-fabric/how-to-deploy-custom-image.md
Medium Priority View Details →
Scanned: 2026-02-04 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page on deploying custom images in Azure Service Fabric Managed Clusters demonstrates a Windows bias. The introductory sections and examples refer primarily to 'custom windows images', and the only command-line example provided uses PowerShell (New-AzRoleAssignment), with no equivalent Linux CLI or Bash example. While there are references to Linux custom image creation and Azure CLI usage, these are secondary and not illustrated with concrete examples.
Recommendations
  • Provide equivalent Azure CLI or Bash examples for role assignment and other operations, especially for Linux/macOS users.
  • Clarify that custom images can be Windows or Linux, and show examples for both where applicable.
  • Rephrase sections to avoid implying that custom images are only for Windows, unless a feature is truly Windows-only.
  • Ensure that references to Linux documentation are accompanied by actionable examples, not just links.
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-02-04 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed PowerShell examples for managing Service Fabric managed cluster node types, but does not offer equivalent CLI (az CLI), Bash, or Linux/macOS shell examples. PowerShell is presented as the only scripting option, which may create friction for users on Linux or macOS who prefer or require cross-platform tools. The documentation also refers to drive letters (e.g., S, C, D), a Windows-centric concept, without clarifying Linux disk mapping. Portal and ARM template methods are platform-neutral, but scripting guidance is Windows-biased.
Recommendations
  • Add Azure CLI (az CLI) examples for all operations currently shown with PowerShell, such as adding, removing, scaling, and configuring node types.
  • Clarify disk mapping for Linux-based node types, or note any differences in how disk letters are handled on Linux VMs.
  • Explicitly state PowerShell Core (pwsh) compatibility and provide cross-platform instructions if PowerShell is required.
  • Where possible, show both PowerShell and CLI examples side-by-side, or link to equivalent CLI documentation.
  • Review and update documentation to ensure Linux/macOS users can complete all tasks without needing Windows-specific tools.
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-04 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 deny assignment policy in Service Fabric managed clusters shows a moderate Windows/PowerShell bias. PowerShell is referenced first and exclusively in several examples, with direct links to PowerShell cmdlets for key operations (deleting, restarting, reimaging NodeTypes). While Azure CLI and sfctl are mentioned in a utility table, the step-by-step examples and guidance focus on PowerShell, and there are no equivalent CLI or sfctl command examples provided for Linux/macOS users.
Recommendations
  • Add Azure CLI and sfctl command examples alongside PowerShell examples for all major operations (delete, restart, reimage NodeType).
  • In the 'Best practices' section, mention CLI and sfctl as alternatives to PowerShell, and provide links to their documentation.
  • Ensure examples and guidance do not assume PowerShell as the default tool, and present cross-platform options equally.
  • Consider ordering tool references alphabetically or by platform neutrality, rather than listing PowerShell first.
GitHub Create Pull Request
Service Fabric Monitor Azure Service Fabric ...main/articles/service-fabric/monitor-service-fabric.md
Medium Priority View Details →
Scanned: 2026-02-04 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 instances where Windows tools and patterns (such as EventStore APIs, Event Log/Event Viewer, Diagnostics Agent) are mentioned first or exclusively, with Linux equivalents referenced later or less prominently. Some examples and tutorials focus on .NET applications, which are often Windows-centric, and there is a lack of explicit Linux-specific step-by-step examples or parity in tool coverage. Linux diagnostics are described as requiring 'different configuration' without detailed guidance or examples in this main page.
Recommendations
  • Ensure Linux-specific monitoring tools and workflows are described with equal detail and prominence as Windows equivalents.
  • Provide explicit Linux examples and step-by-step instructions for configuring diagnostics, collecting logs, and using monitoring agents.
  • When referencing tutorials or sample setups, include links or sections for Linux clusters and applications (e.g., .NET Core on Linux, containerized workloads).
  • Where Windows tools (Event Viewer, Diagnostics Agent) are mentioned, immediately follow with Linux alternatives (Syslog, LTTng, Azure Monitor agent) and provide usage examples.
  • Clarify which features are Windows-only and which are cross-platform, to help users quickly identify relevant guidance.
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-02-04 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation page for RunToCompletion semantics in Service Fabric demonstrates a notable Windows bias. All code examples use Windows containers (nanoserver), Windows-specific shell commands (cmd, set, exit), and reference Windows container compatibility. Querying deployment status is shown only via PowerShell and C# APIs, with no Linux shell or cross-platform CLI examples. There is no mention of Linux containers, nor examples using Linux images or shell commands.
Recommendations
  • Add equivalent examples using Linux containers (e.g., Ubuntu or Alpine images) and Linux shell commands (bash/sh) in ServiceManifest.xml.
  • Clarify whether RunToCompletion semantics are supported for Linux containers and, if so, provide Linux-specific code samples.
  • Include instructions for querying deployment status using Azure CLI, REST API, or Service Fabric CLI (sfctl), which are cross-platform.
  • Explicitly state any limitations or differences for Linux container support in Service Fabric RunToCompletion semantics.
GitHub Create Pull Request
Service Fabric Learn about Azure Service Fabric application security ...ric/service-fabric-application-and-service-security.md
Medium Priority View Details →
Scanned: 2026-02-04 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation generally aims to be cross-platform, referencing both Windows and Linux clusters in several sections. However, there is a notable Windows bias: Windows-specific features (e.g., Active Directory, gMSA, BitLocker) are described in detail, while equivalent Linux guidance is missing or relegated to TODO comments. Examples and links for Windows scenarios (e.g., disk encryption, service accounts) are provided, but Linux alternatives are not, or are mentioned only in passing.
Recommendations
  • Provide explicit Linux examples and instructions for key security tasks, such as disk encryption and service account configuration.
  • Add links to Linux-specific documentation where available (e.g., encrypting disks on Linux clusters, using Linux service accounts).
  • Ensure that for every Windows-specific feature discussed, the Linux equivalent (if available) is described with equal detail, or a clear statement is made if no equivalent exists.
  • Remove or resolve TODO comments regarding Linux features, replacing them with actionable guidance or links.
  • Where examples are given (e.g., PowerShell for disk encryption), provide Bash/CLI equivalents for Linux clusters.
GitHub Create Pull Request
Service Fabric Application upgrade: data serialization ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-application-upgrade-data-serialization.md
Medium Priority View Details →
Scanned: 2026-02-04 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides next steps that prioritize Windows-centric tools: Visual Studio and PowerShell, both of which are primarily used on Windows. There are no explicit Linux/macOS CLI or cross-platform examples or references, and the recommended serialization approach (Data Contract serializer) is .NET-specific, but not Windows-only. The main content does not mention Linux/macOS alternatives for application upgrade workflows.
Recommendations
  • Add examples or references for upgrading Service Fabric applications using cross-platform tools such as Azure CLI or Service Fabric CLI (sfctl), which are available on Linux/macOS.
  • Clarify whether the PowerShell and Visual Studio tutorials are Windows-only, and provide links to equivalent Linux/macOS workflows if available.
  • Mention that Service Fabric supports Linux clusters and provide guidance or links for Linux users regarding data serialization and upgrade processes.
  • Include notes or sections for .NET Core/.NET 5+ users, as these runtimes are cross-platform.
GitHub Create Pull Request
Service Fabric Application upgrade: upgrade parameters ...abric/service-fabric-application-upgrade-parameters.md
Medium Priority View Details →
Scanned: 2026-02-04 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page prioritizes Windows-centric tools (PowerShell, Visual Studio) in both structure and example coverage. The PowerShell and Visual Studio sections are presented first and in greater detail, with explicit parameter tables and example formats, while Linux/macOS equivalents (Service Fabric CLI/SFCTL) are covered later and with less depth. There are no explicit Linux shell command examples or walkthroughs in the main content, and parameter explanations often reference PowerShell-specific syntax (e.g., hashtables) without showing equivalent Linux CLI usage.
Recommendations
  • Reorder sections so that cross-platform tools (SFCTL/CLI) are presented alongside or before Windows-specific tools.
  • Provide explicit Linux/macOS shell command examples for SFCTL, including parameter usage and JSON formatting.
  • Clarify which tools are cross-platform and which are Windows-only at the start of the article.
  • Add a comparison table showing how to perform upgrades using PowerShell, Visual Studio, and SFCTL, with example commands for each.
  • Ensure parameter explanations include both PowerShell and SFCTL syntax where applicable.
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-04 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation references PowerShell cmdlets as the primary example for cluster and application management, and mentions Windows security as a transport option before X509 certificates. There are no Linux-specific management tool examples or mentions of cross-platform CLI alternatives, which may create friction for Linux/macOS users.
Recommendations
  • Include references to cross-platform management tools such as Azure CLI or Service Fabric CLI (sfctl) alongside PowerShell.
  • Clarify that management operations can be performed from Linux/macOS using these tools.
  • Mention Linux security options (such as certificate-based authentication) equally with Windows security in the transport subsystem section.
  • Provide links or brief examples for Linux/macOS management workflows where relevant.
GitHub Create Pull Request
Service Fabric Describing Azure Service Fabric apps and services ...ic/service-fabric-application-and-service-manifests.md
Medium Priority View Details →
Scanned: 2026-02-04 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation contains a notable Windows bias in its guidance for authoring and validating manifest XML files. It explicitly recommends opening the Service Fabric XSD schema in Visual Studio using a Windows file path, with no mention of Linux/macOS equivalents or cross-platform tooling. Additionally, PowerShell is referenced before any cross-platform CLI alternatives for service creation, and all example file paths and tooling are Windows-centric.
Recommendations
  • Provide guidance for validating manifest XML files on Linux/macOS, such as using VS Code with the XML extension, xmllint, or other cross-platform editors.
  • Include Linux/macOS file paths and instructions alongside Windows paths when referencing schema files.
  • Mention cross-platform Service Fabric CLI (sfctl) or Azure CLI for service management, not just PowerShell.
  • Clarify when a tool or workflow is Windows-only, and offer alternatives 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-04 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page heavily references PowerShell cmdlets and Windows-centric tools for managing the Service Fabric application lifecycle, often without providing equivalent Azure CLI, Service Fabric CLI (sfctl), or Linux-native examples. While REST API and .NET SDK methods are mentioned, practical command-line guidance is almost exclusively PowerShell-focused, which creates friction for Linux/macOS users.
Recommendations
  • For every PowerShell cmdlet mentioned, provide equivalent Azure CLI and/or Service Fabric CLI (sfctl) commands, especially for common lifecycle operations (deploy, upgrade, remove, etc.).
  • Add explicit Linux/macOS command-line examples where possible, or clearly indicate when a tool is cross-platform.
  • In sections describing automation (e.g., automatic cleanup), include CLI or scripting options that work on Linux.
  • Where REST API is referenced, consider providing curl or HTTPie examples for Linux users.
  • Review linked example pages to ensure Linux parity is maintained there as well.
GitHub Create Pull Request
Service Fabric Service Fabric application upgrade ...s/service-fabric/service-fabric-application-upgrade.md
Medium Priority View Details →
Scanned: 2026-02-04 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 Service Fabric application upgrades exhibits a notable Windows bias. The only concrete command-line example provided uses PowerShell cmdlets (e.g., Get-ServiceFabricApplication, Start-ServiceFabricApplicationUpgrade), which are Windows-specific tools. There are no equivalent examples for Linux/macOS users (e.g., using sfctl or REST API). Additionally, the documentation references Windows-specific components like http.sys and error messages from the Windows HTTP Server API without clarifying cross-platform implications or alternatives. The 'Next steps' section also prioritizes Visual Studio and PowerShell, both of which are primarily Windows tools, with no mention of Linux/macOS workflows.
Recommendations
  • Add equivalent Linux/macOS command-line examples using sfctl (Service Fabric CLI) or REST API for all PowerShell examples.
  • When referencing Windows-specific tools or APIs (e.g., http.sys, Windows HTTP Server API), clarify their relevance to Linux clusters and provide Linux-specific guidance or caveats.
  • In the 'Next steps' section, include links or references to Linux/macOS upgrade workflows, such as tutorials using sfctl or REST API.
  • Where possible, present cross-platform tools and examples first, or clearly indicate when a tool is Windows-only.
GitHub Create Pull Request
Service Fabric Restoring backup in Azure Service Fabric ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-backup-restore-service-trigger-restore.md
Medium Priority View Details →
Scanned: 2026-02-04 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation for restoring backups in Azure Service Fabric is heavily focused on PowerShell-based workflows, with all CLI examples and code snippets using PowerShell cmdlets and scripting. The prerequisite steps require installation of a PowerShell module (Microsoft.ServiceFabric.Powershell.Http), and all REST API usage is demonstrated via PowerShell scripts. There are no examples for Linux/macOS users (e.g., Bash, curl, Azure CLI), nor is there guidance for performing these operations outside of PowerShell. Windows tools and patterns are mentioned exclusively and first, which may create friction for users on non-Windows platforms.
Recommendations
  • Provide equivalent examples using Bash/curl for REST API calls to demonstrate how Linux/macOS users can perform backup and restore operations.
  • Document how to authenticate and interact with Service Fabric REST APIs from non-Windows environments, including certificate handling.
  • Mention Azure CLI or cross-platform tools if available for Service Fabric backup/restore operations.
  • Clarify whether the PowerShell module is required on all platforms, and if so, provide installation and usage instructions for Linux/macOS (if supported).
  • Add a note on platform compatibility and explicitly state if any steps are Windows-only.
GitHub Create Pull Request
Service Fabric Understanding periodic backup configuration ...-fabric-backuprestoreservice-configure-periodic-backup.md
Medium Priority View Details →
Scanned: 2026-02-04 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page provides configuration details for periodic backup in Azure Service Fabric, including examples for Azure Blob storage and file shares. The file share backup examples and instructions are exclusively Windows-centric, referencing Integrated Windows Authentication and UNC paths (\\StorageServer\BackupStore), with no mention of Linux-compatible file share access methods (such as NFS or SMB mounting on Linux). There are no Linux/macOS-specific examples or guidance for configuring backup storage on non-Windows platforms.
Recommendations
  • Add examples for configuring file share backup storage using Linux-compatible protocols (e.g., NFS, SMB via CIFS) and provide sample configuration for Linux clusters.
  • Clarify whether file share backup is supported for Linux Service Fabric clusters and, if so, document authentication and mounting procedures for Linux.
  • Where authentication is discussed, mention Linux alternatives (e.g., Kerberos, username/password via mount.cifs) and provide sample configuration.
  • Explicitly state platform limitations if file share backup is Windows-only, to avoid confusion for Linux users.
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-04 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 instructions for scaling Service Fabric clusters, but the manual scaling steps rely exclusively on PowerShell commands (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState) without mentioning Linux equivalents or cross-platform alternatives. Windows/PowerShell tooling is presented first and exclusively in critical operational steps, with no Bash, CLI, or Linux-specific guidance. This creates friction for Linux users, who must infer or research how to perform these actions on non-Windows platforms.
Recommendations
  • Include equivalent Azure CLI or Bash commands for all PowerShell examples, especially for node disablement and removal.
  • Clarify whether the PowerShell commands can be run from Linux/macOS using Azure PowerShell modules, or provide direct Linux-native alternatives.
  • Add explicit instructions or links for performing Service Fabric management tasks on Linux clusters, including cluster scaling and node management.
  • Ensure that cross-platform tooling (e.g., Azure CLI, REST API) is mentioned and demonstrated alongside PowerShell.
  • If certain operations are only possible on Windows, clearly state this limitation.
GitHub Create Pull Request
Service Fabric Azure Service Fabric networking best practices ...ice-fabric/service-fabric-best-practices-networking.md
Medium Priority View Details →
Scanned: 2026-02-04 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page for Azure Service Fabric networking best practices shows moderate Windows bias. Several examples and explanations reference Windows-specific tools (e.g., PowerShell), mention Windows scenarios before Linux, and provide more detail for Windows use cases. Linux equivalents are sometimes mentioned but often lack parity in example depth or clarity. Some network port explanations and ARM template samples are Windows-centric, and PowerShell is referenced as the default API client without equal CLI or Linux guidance.
Recommendations
  • Provide Linux CLI (az CLI) examples alongside PowerShell for cluster management and networking tasks.
  • Ensure ARM template samples and references include both Windows and Linux cluster configurations.
  • When describing API endpoints or client tools, mention Linux-friendly options (e.g., Azure CLI, REST API) with equal prominence.
  • Clarify when a recommendation or example is Windows-specific, and offer Linux alternatives where possible.
  • Balance references to Windows and Linux in introductory and summary sections to avoid Windows-first impression.
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-04 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation generally presents Windows-specific tools and examples (e.g., PowerShell commands, Windows Defender, Windows security baselines) before Linux equivalents, and references Windows tooling (PowerShell, Windows Defender) without always providing Linux alternatives or parity. However, for key security tasks like secret encryption, both Windows and Linux examples are provided. Some sections (Windows Defender, security baselines) are inherently Windows-only, but their placement and prominence may create friction for Linux users.
Recommendations
  • Ensure Linux examples are presented alongside or before Windows examples in sections relevant to both platforms.
  • Clearly label Windows-only sections and, where possible, provide Linux alternatives or explicitly state when no equivalent exists.
  • Add references to Linux security best practices and tools (e.g., SELinux, AppArmor, Linux antivirus solutions) where appropriate.
  • Balance the coverage of platform-specific security guidance to avoid the perception that Windows is the default or preferred platform.
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-02-04 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 is featured prominently and exclusively for some upgrade operations. Windows-specific configuration (e.g., registry keys, Windows Update settings) is described in detail, while Linux equivalents are not mentioned. Some upgrade instructions use PowerShell and MSI packages, which are Windows-centric, with no Linux alternative shown. Windows configuration details are presented before Linux ones in several sections.
Recommendations
  • Provide Linux-specific examples for cluster upgrade operations, including commands for .deb packages and shell scripts.
  • Include guidance for disabling automatic updates and configuring patch management on Linux VMs (e.g., using apt or yum, or systemd timers).
  • When mentioning registry keys or Windows Update settings, add equivalent instructions for Linux systems (such as disabling unattended-upgrades or configuring update policies).
  • Balance PowerShell examples with Bash or shell script equivalents where possible, especially for cluster management tasks.
  • Where possible, present Windows and Linux instructions side-by-side, or clearly separate them to reduce confusion.
GitHub Create Pull Request
Service Fabric Change Azure Service Fabric cluster settings ...rvice-fabric/service-fabric-cluster-fabric-settings.md
Medium Priority View Details →
Scanned: 2026-02-04 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation lists Service Fabric cluster settings in a platform-neutral way, but there are signs of Windows bias. Windows terminology and tools (e.g., certificate store names like 'My', references to NTLM, and Windows-specific logging) are prevalent, and Windows-centric configuration patterns (such as X.509 store locations and NTLM authentication) are described without Linux equivalents or with Windows defaults shown first. Some settings mention Windows-only features (e.g., Windows Update integration, Windows log file quotas, NTLM authentication) without clarifying Linux alternatives. Linux-specific settings are present but less visible and often appear after Windows options. There are no explicit Linux configuration examples or guidance for Linux users, and some settings (e.g., certificate management, file store service authentication) are described only in Windows terms.
Recommendations
  • Add explicit Linux configuration examples and guidance, especially for certificate management, authentication, and logging.
  • Clarify which settings are Windows-only and which have Linux equivalents; provide Linux-specific defaults and patterns where appropriate.
  • Where Windows terminology is used (e.g., 'My' certificate store), explain the Linux equivalent or alternative.
  • Ensure Linux-specific features (e.g., LinuxExternalExecutablePath, EnforceLinuxMinTlsVersion) are documented with equal prominence and detail.
  • For authentication and file store service, describe Linux-compatible approaches (e.g., use of PEM files, Linux user accounts) alongside Windows methods.
GitHub Create Pull Request
← Previous Page 76 of 99 Next →