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 926-950 of 2475 flagged pages
Service Fabric Define Service Configuration in StartupServices.xml for a Service Fabric Application ...service-fabric/service-fabric-startupservices-model.md
Medium Priority View Details →
Scanned: 2026-02-25 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on Visual Studio workflows and Windows-centric tooling (e.g., F5/Ctrl+F5/Publish, Visual Studio UI, PowerShell references). There are no examples or guidance for Linux/macOS users or cross-platform tooling. The page assumes deployment and development are done via Visual Studio, which is Windows-only, and does not mention alternatives for Linux/macOS users.
Recommendations
  • Add explicit guidance for Linux/macOS users, including how to manage service configuration and deployment without Visual Studio.
  • Include examples using cross-platform tools such as Azure CLI, Service Fabric CLI (sfctl), or ARM templates.
  • Clarify whether StartupServices.xml is strictly a Windows/Visual Studio feature, and if so, provide links or references to Linux/macOS-compatible workflows.
  • Mention PowerShell alternatives (e.g., Bash scripts, sfctl) for service creation and deployment.
  • If the feature is Windows-only, state this clearly at the top of the documentation.
GitHub Create Pull Request
Service Fabric Fault Analysis Service overview .../service-fabric/service-fabric-testability-overview.md
Medium Priority View Details →
Scanned: 2026-02-25 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides usage instructions for C# (via the Microsoft.ServiceFabric NuGet package) and PowerShell (via the Service Fabric SDK and PowerShell module). PowerShell is a Windows-centric tool, and no equivalent Linux/macOS CLI or scripting examples (such as Bash or Azure CLI) are provided. The PowerShell section appears before any mention of Linux tooling, and there is no guidance for Linux users on how to interact with the Fault Analysis Service.
Recommendations
  • Add examples for using the Fault Analysis Service from Linux/macOS environments, such as with Bash scripts, Azure CLI, or REST API calls.
  • Clarify whether the Fault Analysis Service APIs can be accessed from non-Windows platforms, and provide guidance for cross-platform usage.
  • If PowerShell is the only supported scripting interface, explicitly state this limitation and suggest alternatives or workarounds for Linux/macOS users.
  • Consider including sample code or command-line instructions for Linux users, or linking to relevant cross-platform documentation.
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-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides a comprehensive overview of certificate management in Azure Service Fabric clusters, but there is a notable Windows bias. PowerShell is the only scripting example given for programmatic certificate enrollment, and the Key Vault VM extension is discussed primarily in its Windows context. The 'linkOnRenewal' feature is explicitly described as Windows-only, and there is no mention of Linux equivalents or cross-platform command-line tools (e.g., Azure CLI, Bash scripts, or Linux VM extensions) for certificate management. Additionally, Windows/PowerShell tools and patterns are presented first and in detail, with no Linux-specific guidance or parity.
Recommendations
  • Include Azure CLI and/or Bash script examples for certificate enrollment and management, alongside or instead of PowerShell.
  • Document the use of the Key Vault VM extension for Linux VMs (if supported), or clearly state if it is Windows-only and provide Linux alternatives (e.g., cloud-init, custom script extensions).
  • When referencing features like 'linkOnRenewal' that are Windows-specific, provide guidance or callouts for Linux users.
  • Add explicit Linux/macOS instructions or parity notes where only Windows/PowerShell guidance is given.
  • Ensure that cross-platform tools and workflows are mentioned at least as prominently as Windows-specific ones.
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-23 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides several examples and links for Azure PowerShell modules and references PowerShell-based workflows prominently in the 'Best practices' section. PowerShell is traditionally associated with Windows, and its usage is highlighted before mentioning cross-platform tools like Azure CLI or sfctl. While Azure PowerShell is technically cross-platform, its prominence may create friction for Linux/macOS users who prefer CLI or native tools. The page does mention Azure CLI and ARM templates, but PowerShell examples are given first and in more detail.
Recommendations
  • Provide Azure CLI examples alongside PowerShell examples, especially in the 'Best practices' section.
  • Explicitly note that Azure PowerShell and Azure CLI are both cross-platform, and link to installation guides for Linux/macOS.
  • Where possible, show CLI commands before or alongside PowerShell commands to improve parity.
  • Add examples for sfctl usage where relevant, since it is a native Service Fabric CLI tool.
  • Clarify that PowerShell is not required and that all tasks can be performed with CLI or ARM templates.
GitHub Create Pull Request
Service Fabric Service Fabric Explorer blocking operations ...ged-cluster-service-fabric-explorer-blocking-operation.md
Medium Priority View Details →
Scanned: 2026-02-23 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides management guidance for Service Fabric Explorer, referencing Az PowerShell cmdlets (e.g., Remove-AzResource) and AzSF PowerShell cmdlets for key operations. While it briefly mentions the 'az resource' CLI for deleting applications, PowerShell examples and terminology are predominant, and Linux/macOS equivalents (such as Azure CLI commands) are not consistently provided for all tasks. The ordering and emphasis on PowerShell tools may create friction for Linux/macOS users.
Recommendations
  • For every PowerShell cmdlet mentioned, provide the equivalent Azure CLI command (where available) and link to its documentation.
  • Clarify which tools are cross-platform and which are Windows-only.
  • Present Azure CLI examples before or alongside PowerShell examples to improve parity.
  • Explicitly state if certain operations can only be performed with PowerShell, and suggest alternatives for Linux/macOS users if possible.
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-23 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 presents RunToCompletion semantics in Service Fabric with a strong Windows bias. All code examples use Windows containers (nanoserver), Windows-specific commands (cmd, echo, ping, set, exit), and the application manifests are named and described as Windows-only. Querying deployment status is demonstrated only via PowerShell and C# APIs, with no mention of Linux equivalents or CLI tools. There are no examples or guidance for Linux containers or Linux-based workflows, despite Service Fabric supporting Linux containers.
Recommendations
  • Add examples using Linux containers (e.g., Ubuntu or Alpine images) with equivalent shell commands.
  • Provide guidance or code snippets for querying deployment status using Azure CLI or Service Fabric CLI on Linux/macOS.
  • Clarify whether RunToCompletion semantics are supported for Linux containers and, if so, provide parity in documentation.
  • Rename examples and descriptions to be platform-neutral where possible, or explicitly state platform limitations.
  • Include notes or links for Linux/macOS users about relevant tools and commands.
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-23 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides upgrade walkthroughs using Visual Studio and PowerShell, both of which are primarily Windows tools. There are no Linux/macOS equivalents or examples for upgrading Service Fabric applications, nor are cross-platform CLI options mentioned. The serialization guidance is C#-centric, but this is appropriate given Service Fabric's .NET focus.
Recommendations
  • Add examples and walkthroughs for upgrading applications using cross-platform tools such as Azure CLI or Service Fabric CLI (sfctl), which are available on Linux/macOS.
  • Mention and link to Linux/macOS-compatible upgrade documentation where possible.
  • Clarify that Visual Studio and PowerShell are Windows-centric, and provide alternative instructions for non-Windows users.
GitHub Create Pull Request
Service Fabric Understanding periodic backup configuration ...-fabric-backuprestoreservice-configure-periodic-backup.md
Medium Priority View Details →
Scanned: 2026-02-23 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page primarily describes Service Fabric's periodic backup configuration in a platform-neutral way, but the only on-premises backup storage example given is a Windows file share (with Windows authentication and UNC paths). There are no examples or mentions of Linux-compatible storage options (such as NFS or SMB mounts on Linux), nor guidance for Linux clusters. This creates friction for Linux users seeking to configure on-premises backups.
Recommendations
  • Add examples and guidance for configuring backup storage using Linux-compatible file shares (e.g., NFS, SMB mounts) for standalone clusters.
  • Clarify whether the file share backup storage option is supported on Linux Service Fabric clusters, and if so, provide sample paths and authentication methods relevant to Linux.
  • Mention any limitations or alternative approaches for Linux clusters if Windows file shares are not supported.
  • Consider including a note or section on cross-platform compatibility for backup storage options.
GitHub Create Pull Request
Service Fabric Application upgrade: upgrade parameters ...abric/service-fabric-application-upgrade-parameters.md
Medium Priority View Details →
Scanned: 2026-02-23 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page presents PowerShell and Visual Studio parameters and examples before SFCTL (Service Fabric CLI), which is the cross-platform tool for Linux and macOS. The parameter tables and explanations are heavily focused on PowerShell and Visual Studio, with SFCTL covered in a separate section. There are no explicit Linux/macOS-specific examples or parity notes, and Windows tools are mentioned first throughout.
Recommendations
  • Reorganize the documentation so that SFCTL (cross-platform CLI) is presented before or alongside PowerShell and Visual Studio, emphasizing its use for Linux/macOS users.
  • Add explicit Linux/macOS examples using SFCTL, including sample commands and parameter usage.
  • Clarify which tools are platform-specific and which are cross-platform, ideally in an introductory section.
  • Ensure parameter tables include SFCTL equivalents where applicable, or provide a unified comparison table.
  • Consider adding a section or callout for Linux/macOS users to highlight relevant tools and workflows.
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-23 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 presented as a separate section and is Windows-centric. In the cluster upgrade section, only PowerShell commands are given for manual upgrades, with no Linux shell (bash) or cross-platform alternatives. Windows registry keys and Windows-specific VM template properties are discussed without Linux equivalents or guidance. Windows configuration details are presented before Linux, and Linux-specific upgrade instructions are missing.
Recommendations
  • Add Linux/bash examples for manual cluster upgrades, especially for operations currently shown only in PowerShell.
  • Include Linux-specific guidance for disabling automatic updates and patch management, mirroring the Windows registry and VM template instructions.
  • Where possible, present cross-platform tools and commands (e.g., Azure CLI, REST API) before Windows-specific tools.
  • Clarify when instructions are Windows-only and provide links or references to Linux equivalents.
  • Ensure parity in upgrade and patching guidance for Linux clusters.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager - Application Groups ...ice-fabric-cluster-resource-manager-application-groups.md
Medium Priority View Details →
Scanned: 2026-02-23 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 and C# examples for managing Service Fabric Application Groups, with no mention of Linux-compatible CLI tools (such as Azure CLI or REST API) or Bash scripting. All command-line examples use PowerShell cmdlets, which are Windows-centric and may not be available or convenient for Linux/macOS users. There is no guidance or parity for Linux users on how to perform equivalent operations.
Recommendations
  • Add Azure CLI examples for all PowerShell cmdlets shown, as Azure CLI is cross-platform and works on Linux/macOS.
  • Mention REST API endpoints for relevant operations, with example requests.
  • Clarify whether PowerShell cmdlets are available on Linux (via PowerShell Core), and if so, provide installation guidance; if not, offer alternatives.
  • Consider including Bash scripting examples or references for Linux users.
  • Explicitly state any limitations or differences for Linux/macOS users when using Service Fabric management tools.
GitHub Create Pull Request
Service Fabric Azure Service Fabric standalone cluster scaling ...ce-fabric/service-fabric-cluster-scaling-standalone.md
Medium Priority View Details →
Scanned: 2026-02-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page for scaling Azure Service Fabric standalone clusters demonstrates Windows bias by exclusively referencing PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) and linking to Windows Server-specific guides. There are no Linux command examples or references to Linux tools for cluster scaling, and the process is described only in Windows-centric terms.
Recommendations
  • Add equivalent Linux command-line examples (e.g., using sfctl or REST APIs) for cluster scaling operations.
  • Clarify whether standalone Service Fabric clusters can be managed/scaled on Linux, and provide guidance if so.
  • Link to Linux-specific documentation or note limitations if Linux management is not supported.
  • Present both Windows and Linux procedures side-by-side where applicable.
GitHub Create Pull Request
Service Fabric Upgrade an Azure Service Fabric standalone cluster ...ce-fabric/service-fabric-cluster-upgrade-standalone.md
Medium Priority View Details →
Scanned: 2026-02-23 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page references Windows-specific upgrade and configuration guides (e.g., links ending with '-windows-server.md') and the Patch Orchestration Application for Windows, without mentioning Linux equivalents or providing Linux-specific instructions. There are no explicit Linux examples or guidance, and Windows is implicitly prioritized.
Recommendations
  • Add links and instructions for Linux-based Service Fabric standalone clusters, if supported.
  • Clarify in each section whether the guidance applies to both Windows and Linux, or only Windows.
  • Provide Linux-specific examples for cluster upgrades, configuration, and patch orchestration if available.
  • If Linux is not supported for standalone clusters, state this explicitly to avoid confusion.
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-02-23 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page is generally platform-neutral, but there are a few areas where Windows-specific terminology and tools are mentioned first or exclusively. For example, the 'Node' definition references an auto-start Windows service and Windows executables (FabricHost.exe, Fabric.exe, FabricGateway.exe) without mentioning Linux equivalents or clarifying Linux behavior. The 'Code package' section references EXE/DLL files, which are Windows formats, and does not mention Linux binaries. However, the page does acknowledge Linux support in several places, such as container support and development clusters.
Recommendations
  • Clarify Linux node behavior: In the 'Node' section, add information about how Service Fabric nodes operate on Linux, including relevant processes or services.
  • Mention Linux binary formats: In the 'Code package' section, note that Linux services may use ELF binaries or other executable formats.
  • Balance Windows/Linux references: When referencing Windows-specific tools or services, add equivalent Linux information or explicitly state differences.
  • Add Linux examples: Where possible, provide examples or notes for Linux users alongside Windows references.
GitHub Create Pull Request
Service Fabric Fault Analysis Service overview .../service-fabric/service-fabric-testability-overview.md
Medium Priority View Details →
Scanned: 2026-02-23 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 the Fault Analysis Service overview provides usage instructions primarily for C# and PowerShell, with explicit mention of the Service Fabric SDK and PowerShell module installation. There are no examples or guidance for Linux/macOS users, such as using CLI tools or REST APIs, nor is there mention of cross-platform alternatives. The PowerShell focus and lack of Linux-specific instructions create friction for non-Windows users.
Recommendations
  • Add examples for using the Fault Analysis Service via Azure CLI or REST API, which are cross-platform.
  • Clarify whether the Fault Analysis Service APIs can be accessed from Linux/macOS environments, and provide relevant instructions.
  • Mention any limitations or requirements for Linux users, such as SDK availability or cluster configuration.
  • Provide links or references to Linux/macOS-compatible tools for managing Service Fabric clusters and invoking Fault Analysis Service actions.
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-23 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides examples for modifying Service Fabric managed cluster node types using the Azure Portal, ARM templates, and PowerShell. PowerShell is the only CLI example provided, with no mention of Azure CLI or Bash equivalents. PowerShell is a Windows-centric tool, and its exclusive use creates friction for Linux/macOS users. Additionally, PowerShell examples are given for every operation (add, remove, scale, configure placement properties), and are presented alongside or after portal and ARM template methods, but never with Linux-friendly CLI options.
Recommendations
  • Add Azure CLI examples for all operations (add, remove, scale, configure placement properties, etc.) to ensure Linux/macOS users have parity.
  • Explicitly mention that PowerShell examples are Windows-centric and provide links or guidance for Linux/macOS users.
  • Where possible, clarify if ARM template operations can be performed equally from Linux/macOS environments (e.g., using Azure CLI or REST API).
  • Consider including Bash scripts or references to cross-platform tools for cluster management.
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-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page for Initializer CodePackages in Service Fabric presents only Windows container examples, referencing Windows-specific images (mcr.microsoft.com/windows/nanoserver:1809), Windows paths (C:\...), and Windows shell commands (cmd, echo, type, ping). There are no Linux container examples, nor any mention of Linux-compatible patterns, tools, or file paths. The page assumes familiarity with creating Windows container applications and does not provide parity for Linux users.
Recommendations
  • Add a complete example using Linux containers (e.g., mcr.microsoft.com/ubuntu or other Linux images), with Linux shell commands (bash, echo, cat, etc.) and Linux file paths (/workspace/log.txt).
  • Clarify whether Initializer CodePackages are supported for Linux containers and, if so, provide guidance and examples for Linux users.
  • If Initializer CodePackages are Windows-only, explicitly state this at the top of the article to avoid confusion for Linux users.
  • Ensure that references to container creation and Service Fabric usage include links and guidance for both Windows and Linux environments.
GitHub Create Pull Request
Service Fabric Migrate an Azure Service Fabric cluster to availability zone support ...ce-fabric/migrate-service-fabric-availability-zones.md
Medium Priority View Details →
Scanned: 2026-02-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides extensive PowerShell examples for migration steps, especially in the 'Basic SKU load balancer and IP resources' scenario. PowerShell commands and Windows-specific paths (e.g., 'D:\\SvcFab') are used throughout, and Windows-based sample templates are referenced before Linux equivalents. There is minimal guidance or examples for Linux/macOS users, and the only Linux sample template is mentioned in passing without corresponding CLI or Bash instructions.
Recommendations
  • Add Azure CLI or Bash script equivalents for all PowerShell migration steps, especially for resource deployment, node disabling, and DNS updates.
  • Reference Linux/Ubuntu sample templates alongside Windows ones, and provide clear instructions for Linux-based clusters.
  • Avoid using Windows paths (e.g., 'D:\\SvcFab') in generic examples; use platform-neutral or Linux paths where appropriate.
  • Ensure that all critical operations (e.g., node management, resource cleanup) are documented with cross-platform tooling.
  • Explicitly state when a step is Windows-only and provide alternatives for Linux/macOS users.
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-02-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation provides a generally cross-platform overview of X.509 certificate-based authentication in Service Fabric clusters, but there are several areas where Windows bias is evident. Windows certificate store paths (e.g., LocalMachine\My) and Windows-specific troubleshooting tools (e.g., CAPI2 logging, Win32 CryptoAPI references) are mentioned first or exclusively, with Linux equivalents only briefly referenced or omitted. Troubleshooting and configuration examples focus on Windows-centric patterns, and some error codes and provider types are Windows-specific.
Recommendations
  • Wherever Windows certificate store paths are mentioned (e.g., LocalMachine\My), provide the Linux equivalent (e.g., /var/lib/sfcerts) with equal prominence and detail.
  • In troubleshooting sections, add Linux-specific guidance, such as relevant log file locations, commands (e.g., using OpenSSL or Linux system logs), and error messages.
  • When referencing Windows-specific tools (e.g., CAPI2 logging, Win32 CryptoAPI), also mention Linux alternatives or clarify which steps are Windows-only.
  • For error codes and cryptographic provider types, note any Linux-specific equivalents or differences, or explicitly state if a concept is Windows-only.
  • Ensure all configuration examples and explanations are clearly applicable to both Windows and Linux clusters, or provide parallel examples where necessary.
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-23 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation includes a PowerShell-only example for bypassing Infrastructure Service, and references Service Fabric Explorer (a GUI tool typically used on Windows). No Linux/macOS equivalent commands or tools are mentioned, and the PowerShell command is presented as the sole method for manual intervention.
Recommendations
  • Provide equivalent CLI examples for Linux/macOS users, such as using Azure CLI or REST API if available.
  • Mention whether the PowerShell command can be run via PowerShell Core on Linux/macOS, or clarify if it is Windows-only.
  • Include instructions for accessing Service Fabric Explorer from non-Windows platforms, or alternative troubleshooting methods.
  • Add notes about cross-platform support for Service Fabric management tools.
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-23 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 Azure Service Fabric clusters on both Windows and Linux, but there is a notable tendency to mention Windows tools and patterns first, such as EventStore APIs being Windows-only, Event Log/Event Viewer, and Diagnostics Agent. Linux equivalents are sometimes referenced later or in passing, and some examples/tutorials focus on .NET/Windows scenarios. There are also sections where Linux-specific guidance is less detailed or deferred to linked pages, and some Windows-specific features (like EventStore APIs) lack Linux alternatives.
Recommendations
  • Ensure Linux monitoring tools and patterns are described with equal prominence and detail as Windows equivalents.
  • Provide Linux-specific examples and walkthroughs alongside Windows/PowerShell examples, especially for cluster and infrastructure monitoring.
  • Clarify when features are Windows-only and offer alternative Linux guidance or links where possible.
  • Add explicit Linux-focused tutorials for application monitoring and diagnostics, not just .NET/Windows.
  • Where EventStore APIs are Windows-only, highlight Linux alternatives (such as querying Syslog or using LTTng) with practical examples.
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-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides several examples and references that are Windows-centric, such as running services under Active Directory domain accounts, gMSA, BitLocker, and PowerShell disk encryption. Linux equivalents are either missing, mentioned only in passing, or flagged as 'TO DO' items. Windows-specific tools and patterns (e.g., BitLocker, PowerShell) are referenced without Linux alternatives or parity.
Recommendations
  • Add explicit Linux examples for running services under local user accounts, securing resources, and disk encryption.
  • Provide guidance or links for Linux disk encryption (e.g., using dm-crypt/LUKS) in the 'Encrypt application data at rest' section.
  • Ensure that Linux container security features are described with equal detail as Windows/gMSA.
  • Where Windows tools (e.g., PowerShell, BitLocker) are referenced, include Linux equivalents or note platform differences.
  • Review and update 'TO DO' sections to provide actionable Linux guidance.
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-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page for the Service Fabric application lifecycle consistently references PowerShell cmdlets and Windows-centric tooling throughout critical lifecycle phases (deploy, upgrade, remove, maintenance). While REST API and .NET methods are also mentioned, PowerShell examples and terminology are prominent and often listed first. There is little explicit mention of Linux-native CLI tools (such as sfctl or Azure CLI) or Linux/macOS workflows, despite Service Fabric supporting cross-platform clusters and management.
Recommendations
  • Add examples and references for Linux/macOS users, such as using sfctl and Azure CLI commands for each lifecycle phase.
  • Where PowerShell cmdlets are mentioned, also provide equivalent sfctl or Azure CLI commands, ideally side-by-side.
  • Clarify which management operations are cross-platform and which are Windows-only, to help users choose the right tools.
  • Update 'Preserving disk space' and 'Cleaning up files' sections to include Linux-native approaches and commands.
  • Consider linking to or embedding Linux/macOS-specific guides for Service Fabric application lifecycle management.
GitHub Create Pull Request
Service Fabric On-demand backup in Azure Service Fabric ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-backup-restore-service-ondemand-backup.md
Medium Priority View Details →
Scanned: 2026-02-23 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page for on-demand backup in Azure Service Fabric is heavily focused on PowerShell and Windows tooling. All command-line examples use PowerShell, including REST API calls, and require installation of a PowerShell module (Microsoft.ServiceFabric.Powershell.Http). There are no examples or guidance for Linux/macOS users, such as using Bash, curl, or cross-platform Service Fabric CLI tools. The documentation assumes the use of Windows-centric tools and patterns throughout, creating friction for Linux/macOS users.
Recommendations
  • Add equivalent Bash/curl examples for REST API calls, showing how to trigger backups and track progress from Linux/macOS.
  • Document any cross-platform Service Fabric CLI tools (e.g., sfctl) and provide usage examples.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is required for all scenarios, or if REST API calls can be made directly from any platform.
  • Explicitly state platform requirements and provide guidance for Linux/macOS users where possible.
  • Reorder examples to show cross-platform approaches first, or at least in parallel with PowerShell.
GitHub Create Pull Request
Service Fabric Advanced Application Upgrade Topics ...-fabric/service-fabric-application-upgrade-advanced.md
Medium Priority View Details →
Scanned: 2026-02-23 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 extensive PowerShell examples and references, with no mention of Linux/macOS CLI equivalents (such as Azure CLI or REST API). Windows/PowerShell tools and cmdlets are used exclusively for all upgrade operations, and PowerShell examples are shown first or only. There is no guidance for Linux/macOS users on how to perform these tasks, creating friction for non-Windows users.
Recommendations
  • Add Azure CLI examples for all upgrade operations, including creating, updating, and rolling back Service Fabric applications.
  • Include REST API references and sample payloads for relevant operations.
  • Clarify which operations are only possible via PowerShell, if any, and provide alternatives or workarounds for Linux/macOS users.
  • Add notes or sections indicating cross-platform support and parity, and link to relevant Linux/macOS documentation.
  • Ensure that ARM template examples are accompanied by CLI/REST instructions for deployment.
GitHub Create Pull Request
← Previous Page 38 of 99 Next →