Service Fabric

810
Total Pages
600
Linux-Friendly Pages
210
Pages with Bias
25.9%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

718 issues found
Showing 451-475 of 718 flagged pages
Service Fabric Azure Service Fabric Programmatic Scaling ...-fabric/service-fabric-cluster-programmatic-scaling.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias. PowerShell cmdlets are referenced as the only scripting alternative to the .NET SDK, with no mention of Linux/macOS equivalents (such as Bash, Azure CLI, or REST API usage). All code examples are in C#/.NET, which is most commonly used on Windows. Windows tools and patterns (PowerShell, .NET libraries) are mentioned exclusively and before any cross-platform alternatives. There are no Linux/macOS-specific instructions or examples, and the documentation does not clarify cross-platform compatibility for the SDK or scripting approaches.
Recommendations
  • Add Azure CLI and Bash examples for scaling operations, showing how to query and update VMSS capacity from Linux/macOS.
  • Mention REST API options for programmatic scaling, which are platform-agnostic.
  • Clarify whether the .NET Fluent SDK and FabricClient can be used on Linux/macOS (e.g., via .NET Core), and provide guidance if so.
  • Include a section comparing scripting options across platforms (PowerShell, Azure CLI, Bash, REST API).
  • Ensure that references to PowerShell are accompanied by equivalent Azure CLI commands, especially for credential management and scaling.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager - Placement Policies ...ce-manager-advanced-placement-rules-placement-policies.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation consistently provides PowerShell command examples for configuring Service Fabric placement policies, with no equivalent examples for Linux/macOS users (e.g., Bash, CLI, or REST API). PowerShell is a Windows-centric tool, and its exclusive use in examples creates friction for users on non-Windows platforms. Additionally, the documentation does not mention or prioritize Linux-native tools or workflows, and Windows/PowerShell examples are presented first and exclusively.
Recommendations
  • Add Azure CLI examples for each placement policy configuration, as Azure CLI is cross-platform and commonly used on Linux/macOS.
  • Include REST API or ARM template snippets where applicable, which are platform-agnostic.
  • Explicitly mention Linux/macOS support for Service Fabric and provide guidance or links for non-Windows users.
  • If PowerShell is required, clarify whether PowerShell Core (cross-platform) is supported and provide installation instructions for Linux/macOS.
  • Reorder examples so that platform-agnostic methods (CLI, REST) are shown before or alongside PowerShell.
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-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation consistently provides PowerShell examples for all operations related to Application Groups, with no mention of Linux/macOS command-line equivalents (such as Azure CLI, Bash, or REST API). PowerShell is a Windows-centric tool, and its use is presented first and exclusively in all code snippets, followed by C# SDK examples. There is no guidance for users on Linux or macOS platforms regarding how to perform these tasks, nor any mention of cross-platform alternatives.
Recommendations
  • Add Azure CLI examples for all operations (creating, updating, querying, and removing Application Groups/Capacity).
  • Include REST API sample calls for relevant operations, as these are platform-agnostic.
  • Explicitly state PowerShell's cross-platform availability if relevant, or clarify any limitations.
  • Provide Bash or shell script examples where possible.
  • Reorder examples so that platform-agnostic methods (CLI, REST) are presented before or alongside PowerShell.
  • Add a note or section addressing Linux/macOS users and how they can perform these tasks.
GitHub Create Pull Request
Service Fabric Cluster Resource Manager - Management Integration ...fabric-cluster-resource-manager-management-integration.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides a detailed example of querying health reports using PowerShell (Get-ServiceFabricPartitionHealth), which is a Windows-centric tool. There are no equivalent examples or instructions for Linux or macOS users, such as using Service Fabric CLI (sfctl) or REST APIs. The only command-line example is Windows PowerShell, and the documentation does not mention Linux management tools or provide parity in operational guidance.
Recommendations
  • Include equivalent Linux/macOS examples using sfctl or REST API for querying partition health.
  • Explicitly mention cross-platform management options and tools where PowerShell is referenced.
  • Add notes or sections clarifying how Linux users can perform the same tasks, with sample commands.
  • Ensure that all operational examples are provided for both Windows and Linux environments.
GitHub Create Pull Request
Service Fabric Manage Azure Service Fabric app load using metrics ...ric/service-fabric-cluster-resource-manager-metrics.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits a Windows bias by providing PowerShell examples exclusively for command-line operations, with no equivalent Linux or cross-platform CLI examples (such as Azure CLI or Bash). Windows/PowerShell commands are presented as the only way to create and manage Service Fabric services via the command line, and these examples appear before any mention of alternatives. There is no guidance for Linux users on how to perform these tasks, nor are Linux tools or patterns referenced.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and works on Linux, macOS, and Windows.
  • Include Bash script examples or instructions for Linux environments where applicable.
  • Explicitly mention Linux/macOS support and provide links or references to Service Fabric documentation for those platforms.
  • Clarify which tools and APIs are available on Linux clusters, and provide guidance for users operating outside Windows.
GitHub Create Pull Request
Service Fabric Azure Service Fabric dynamic node tags ...tps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-node-tagging.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page provides extensive PowerShell examples for managing dynamic node tags and service requirements in Azure Service Fabric, but omits equivalent Linux/macOS command-line examples (e.g., Bash, CLI). PowerShell is a Windows-centric tool, and its prominence, along with the lack of Linux-native instructions, creates friction for non-Windows users. Windows tools and patterns are mentioned exclusively for command-line operations.
Recommendations
  • Add Azure CLI or Bash examples for all PowerShell commands, demonstrating how to add/remove node tags and set service tag requirements from Linux/macOS.
  • Explicitly mention cross-platform alternatives to PowerShell, such as REST API usage via curl or Azure CLI.
  • Reorder examples so that cross-platform or Linux-native methods are presented before or alongside Windows/PowerShell examples.
  • Clarify which tools are available on Linux/macOS and provide installation or usage guidance.
GitHub Create Pull Request
Service Fabric Roll over an Azure Service Fabric cluster certificate ...vice-fabric/service-fabric-cluster-rollover-cert-cn.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides only a Windows PowerShell script for rolling over a Service Fabric cluster certificate, with file paths and commands tailored to Windows environments. There are no equivalent examples or instructions for Linux or macOS users, nor are cross-platform Azure CLI alternatives mentioned. This creates friction for users on non-Windows platforms.
Recommendations
  • Provide equivalent Azure CLI examples for certificate rollover steps, which work on Linux/macOS as well as Windows.
  • Include Linux/macOS-specific instructions for file paths and certificate handling.
  • Explicitly state cross-platform options and clarify which steps are OS-agnostic.
  • Add a note or section on how to perform these tasks from Linux/macOS terminals.
GitHub Create Pull Request
Service Fabric Scale a Service Fabric cluster in or out .../service-fabric/service-fabric-cluster-scale-in-out.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. PowerShell is used extensively for examples and instructions, with Windows-specific cmdlets (e.g., Get-AzVmss, Remove-ServiceFabricNodeState) featured prominently and often before CLI or cross-platform alternatives. While Azure CLI and sfctl (cross-platform tools) are included, PowerShell examples are more detailed and appear first in several sections. There are no explicit Linux shell (bash) or macOS-specific examples, and no mention of Linux-specific considerations or troubleshooting. The documentation assumes familiarity with Windows tools and patterns, which may create friction for Linux/macOS users.
Recommendations
  • Provide bash shell equivalents for all PowerShell examples, especially for tasks like listing nodes, scaling sets, and removing node state.
  • Ensure Azure CLI and sfctl examples are as detailed and comprehensive as PowerShell ones, including error handling and step-by-step logic.
  • Explicitly mention that all Azure CLI and sfctl commands work on Linux/macOS, and clarify any OS-specific differences or limitations.
  • Reorder examples so that cross-platform tools (Azure CLI, sfctl) appear before or alongside PowerShell, not after.
  • Add troubleshooting notes or tips for Linux/macOS environments, such as common permission issues or environment setup steps.
GitHub Create Pull Request
Service Fabric Manage certificates in an Azure Service Fabric cluster ...https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-security-update-certs-azure.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias. All command-line examples for deploying and managing certificates use Azure PowerShell, with no mention of Azure CLI or Bash alternatives. Certificate management steps reference Windows certificate stores (e.g., Cert:\CurrentUser\TrustedPeople), and instructions for importing certificates are provided only for Windows environments. There are no Linux/macOS-specific instructions or examples for certificate handling, deployment, or cluster connection. The documentation assumes familiarity with Windows tooling and does not offer parity for users on Linux or macOS.
Recommendations
  • Add equivalent Azure CLI and Bash examples for template deployment and certificate management.
  • Include instructions for importing certificates on Linux/macOS (e.g., using openssl, update-ca-certificates, or keytool).
  • Document how to connect to Service Fabric clusters from Linux/macOS, including certificate usage.
  • Reference cross-platform tools and avoid assuming the use of Windows certificate stores.
  • Present examples for both Windows and Linux/macOS, or explicitly state platform requirements.
GitHub Create Pull Request
Service Fabric Service sensitivity ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-sensitivity.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
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 configuring service sensitivity and maximum load, but does not offer equivalent command-line instructions for Linux/macOS users (e.g., Bash, CLI, or REST API). PowerShell is a Windows-centric tool, and its exclusive use in examples creates friction for users on other platforms. The ordering also places PowerShell before C# API, reinforcing Windows-first patterns.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • Include REST API examples for service sensitivity and maximum load configuration.
  • Explicitly mention platform compatibility for each method (PowerShell, CLI, C# API).
  • Reorder examples so that platform-neutral or cross-platform methods (CLI, REST) appear before Windows-specific ones.
  • Add notes or links for Linux/macOS users on how to perform these operations without PowerShell.
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-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page on scaling Azure Service Fabric standalone clusters demonstrates a notable Windows bias. It references PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) as the primary tooling for cluster management, without mentioning Linux equivalents or cross-platform alternatives. The linked 'scale a standalone cluster' guide is explicitly for Windows Server, and there are no examples or instructions for Linux-based clusters or tools. This creates friction for users managing Service Fabric clusters on Linux or non-Windows environments.
Recommendations
  • Include examples and instructions for scaling standalone clusters on Linux, using Bash, CLI, or REST APIs.
  • Reference cross-platform tools (such as Azure CLI or Service Fabric REST APIs) alongside PowerShell cmdlets.
  • Provide parity in documentation links, ensuring Linux-specific guides are available and visible.
  • Clearly indicate which steps or tools are Windows-specific and offer alternatives for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Secure an Azure Service Fabric cluster ...cles/service-fabric/service-fabric-cluster-security.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Standalone cluster scenarios are described only for Windows Server, with explicit references to Windows authentication (Kerberos), Windows security, and Windows certificate services. Instructions and links for securing clusters on-premises are exclusively for Windows, with no mention of Linux equivalents or guidance for Linux-based standalone clusters. Windows tools (e.g., MakeCert.exe) are referenced for certificate creation, and Windows terminology (Active Directory, group Managed Service Accounts) is used without Linux alternatives. While Azure-based clusters are described in a platform-neutral way, standalone cluster security is presented as Windows-only.
Recommendations
  • Add explicit guidance and examples for securing standalone Service Fabric clusters running on Linux, including certificate management and authentication options.
  • Reference Linux-compatible certificate creation tools (e.g., OpenSSL) alongside or instead of Windows tools like MakeCert.exe.
  • Clarify whether standalone Linux clusters are supported and, if so, provide links and instructions for their security configuration.
  • Include Linux-specific terminology and patterns (e.g., PAM, system users, Linux file permissions) where relevant.
  • Ensure that examples and instructions are presented in a platform-neutral order, or provide parallel sections for Windows and Linux.
GitHub Create Pull Request
Service Fabric Upgrade Linux OS for Azure Service Fabric ...es/service-fabric/service-fabric-cluster-upgrade-os.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page for upgrading Linux OS in Azure Service Fabric is heavily focused on PowerShell and Az PowerShell cmdlets for cluster management tasks. Most step-by-step instructions and code samples use PowerShell, with only a single section (node disablement for Bronze durability) providing Linux-native (bash/ssh) commands. Windows-centric tools and patterns (PowerShell, Az PowerShell, Service Fabric Explorer) are mentioned first and/or exclusively in critical steps, with minimal guidance for Linux-native alternatives.
Recommendations
  • Provide equivalent CLI (az CLI) and REST API examples for all management tasks currently shown only in PowerShell.
  • Include bash scripts or Linux-native command sequences for cluster and node type management, not just for node disablement.
  • Mention Linux tools (e.g., az CLI, sfctl) before or alongside PowerShell in all relevant steps.
  • Clarify which steps can be performed entirely from Linux/macOS and provide explicit instructions for those environments.
  • Add troubleshooting guidance using Linux-native tools (e.g., sfctl, az CLI, SSH) instead of or in addition to Service Fabric Explorer.
GitHub Create Pull Request
Service Fabric Common questions about Microsoft Azure Service Fabric ...cles/service-fabric/service-fabric-common-questions.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits several signs of Windows bias. Windows-specific tools and patterns (such as PowerShell and Visual Studio) are mentioned exclusively or before Linux equivalents. Examples for tasks like authenticating to Key Vault reference PowerShell scripts and Windows MSI hosts, with no Linux alternatives provided. Antivirus exclusions list only Windows-style paths and processes. The development experience is described in terms of Visual Studio and Windows node configurations, with no mention of Linux/macOS workflows or tools. Linux-specific instructions, examples, or parity are generally missing throughout the page.
Recommendations
  • Provide Linux/macOS equivalents for PowerShell and MSI-based authentication workflows, such as Bash scripts or Azure CLI examples.
  • Include Linux-specific antivirus exclusion paths and processes, or clarify cross-platform requirements.
  • Mention Linux/macOS development workflows and tools (e.g., VS Code, CLI) alongside Visual Studio.
  • Ensure examples and instructions for cluster management, upgrades, and patching are available for both Windows and Linux environments.
  • Where Windows tools or patterns are referenced, add Linux/macOS alternatives or note platform differences.
GitHub Create Pull Request
Service Fabric Azure Files volume driver for Service Fabric ...ic/service-fabric-containers-volume-logging-drivers.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Minor Windows Path Examples
Summary
The documentation demonstrates a moderate Windows bias. Windows prerequisites are listed first and in more detail, PowerShell is the primary scripting tool for both Windows and Linux deployments (even for Linux clusters), and Windows paths and application manifest examples dominate. Linux equivalents (sfctl, bash) are present but often secondary, and Linux-specific patterns or troubleshooting are not covered in depth.
Recommendations
  • Present Linux and Windows instructions in parallel, giving equal prominence to both.
  • Provide bash scripts or native Linux command examples for Linux clusters, rather than relying on PowerShell for Linux deployments.
  • Include Linux-specific troubleshooting notes and configuration details, especially for application manifests and volume mappings.
  • Use platform-agnostic paths and examples in documentation snippets, or provide both Windows and Linux variants.
  • Clarify when instructions apply to Linux, Windows, or both, and avoid assuming PowerShell is available on Linux.
GitHub Create Pull Request
Service Fabric Azure Service Fabric application resource model ...ervice-fabric/service-fabric-concept-resource-model.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a notable Windows bias. It uses Visual Studio for packaging applications, provides only PowerShell examples for deployment and deletion, and omits Linux/macOS equivalents (such as Azure CLI or cross-platform packaging methods). Windows tools and workflows are referenced exclusively, making it harder for Linux/macOS users to follow the instructions without additional research.
Recommendations
  • Add Azure CLI examples for deployment and deletion alongside PowerShell commands.
  • Include instructions for packaging Service Fabric applications without Visual Studio (e.g., using dotnet CLI or other cross-platform tools).
  • Mention and demonstrate Linux/macOS-compatible workflows for zipping and renaming files.
  • Clearly state which steps are platform-specific and provide alternatives where possible.
  • Reorder examples so that cross-platform methods (Azure CLI, REST API) are shown before or alongside Windows-specific tools.
GitHub Create Pull Request
Service Fabric Scalability of Service Fabric services .../service-fabric/service-fabric-concepts-scalability.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias. Code examples for scaling Service Fabric services are provided in C# and PowerShell only, with no equivalent Linux shell (bash/CLI) examples. References to administrative actions and tooling (e.g., New-ServiceFabricService) are PowerShell-centric, which is native to Windows. There is no mention of Linux command-line tools or scripts, nor are Linux-specific workflows or examples presented. Additionally, Windows tooling is mentioned first and exclusively in several sections, and Linux parity is only briefly discussed in the context of platform differences, not in practical usage or examples.
Recommendations
  • Add equivalent Linux CLI (bash/az CLI) examples alongside PowerShell for all code snippets.
  • Explicitly mention Linux tooling and workflows where administrative actions are described.
  • Where PowerShell cmdlets are referenced, provide links or examples for Linux users (e.g., az servicefabric CLI commands).
  • Ensure that Linux examples are presented with equal prominence and detail as Windows/PowerShell examples.
  • Clarify any platform-specific limitations or differences in the context of scaling operations, not just in logging.
GitHub Create Pull Request
Service Fabric Connect securely to an Azure Service Fabric cluster ...ice-fabric/service-fabric-connect-to-secure-cluster.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias: PowerShell is the only shell shown for command-line examples outside of sfctl, and Windows certificate management tools and patterns (e.g., certificate stores, Import-PfxCertificate) are described in detail, while Linux equivalents are missing. Windows instructions and tools are presented first and in greater detail than those for Mac or Linux. Linux users are left to infer steps for certificate installation and management, and there are no Linux-specific CLI or API examples for connecting to clusters.
Recommendations
  • Add explicit Linux instructions for installing client certificates (e.g., using openssl, certutil, or browser settings for certificate import).
  • Provide Linux/macOS equivalents for PowerShell commands, such as using OpenSSL, keytool, or other native tools.
  • Include Linux/macOS examples for connecting to clusters using the Service Fabric CLI and APIs, especially for certificate management and authentication.
  • Balance the order and detail of Windows and Linux/macOS instructions to ensure parity and reduce friction for non-Windows users.
GitHub Create Pull Request
Service Fabric Induce Chaos in Service Fabric clusters ...cles/service-fabric/service-fabric-controlled-chaos.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation provides detailed examples for running Chaos in Service Fabric using C# and PowerShell, both of which are Windows-centric. PowerShell is a Windows-native tool, and no Linux/macOS command-line examples (e.g., Bash, Azure CLI, or cross-platform REST usage) are provided. Windows tools and patterns (PowerShell cmdlets, .NET types) are mentioned exclusively and before any Linux equivalents, which are absent. This creates friction for Linux/macOS users who cannot use PowerShell and may not be familiar with .NET APIs.
Recommendations
  • Add Linux/macOS-friendly examples using Bash and curl to demonstrate REST API usage for Chaos operations.
  • Include Azure CLI examples if available for Service Fabric Chaos management.
  • Explicitly mention cross-platform options and clarify which tools/APIs work on Linux/macOS.
  • Reorder examples so REST API or cross-platform methods are shown first, followed by platform-specific (Windows/PowerShell) examples.
  • Provide guidance on installing and using Service Fabric SDK/tools on Linux/macOS.
GitHub Create Pull Request
Service Fabric Create a cluster using certificate common name ...-fabric/service-fabric-create-cluster-using-cert-cn.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exclusively provides PowerShell-based instructions and examples for certificate management, key vault operations, and deployment, all using Windows file paths and tools. There are no CLI, Bash, or Linux/macOS-specific examples or guidance. The template references and deployment steps assume a Windows environment, creating friction for Linux/macOS users.
Recommendations
  • Add equivalent Azure CLI (az) commands for certificate upload, resource group creation, and template deployment.
  • Provide Bash shell examples for Linux/macOS users, including file path conventions.
  • Explicitly mention cross-platform support and note any differences or limitations for Linux/macOS users.
  • Include a section or links for Linux/macOS certificate generation and handling.
  • Ensure template instructions do not assume Windows-only paths or tools.
GitHub Create Pull Request
Service Fabric Deploy a cluster across Availability Zones ...vice-fabric/service-fabric-cross-availability-zones.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias, especially in migration and operational steps. All command-line examples use PowerShell cmdlets, with no Bash, Azure CLI, or Linux-native instructions. The sample templates referenced are Windows-first, and Windows-centric tools (PowerShell, Windows file paths) are used exclusively. Linux equivalents are missing, and the only explicit Linux reference is a template link, not a walkthrough.
Recommendations
  • Provide Azure CLI and Bash examples alongside PowerShell for all deployment, migration, and operational steps.
  • Include Linux/macOS-specific instructions for connecting to clusters, managing nodes, and updating resources.
  • Reference and walk through Linux-based sample templates with equal prominence as Windows ones.
  • Avoid Windows-specific file paths (e.g., D:\SvcFab) in generic configuration examples, or provide Linux equivalents.
  • Clearly indicate which steps or scripts are OS-specific, and provide alternatives where needed.
GitHub Create Pull Request
Service Fabric Overview of Azure and standalone Service Fabric clusters ...icles/service-fabric/service-fabric-deploy-anywhere.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation mentions both Windows Server and Linux as supported platforms for Service Fabric clusters, but it highlights that standalone clusters are not available on Linux. There are no Linux-specific examples, tools, or operational patterns discussed, and the limitations for Linux are referenced only via a link. Windows is mentioned first and appears to be the primary focus for standalone clusters.
Recommendations
  • Explicitly state the limitations for Linux standalone clusters in the main text, not just via a link.
  • Provide examples or guidance for Linux users regarding Service Fabric cluster deployment and management on Azure.
  • Include a comparison table or section summarizing feature parity and gaps between Windows and Linux clusters.
  • If possible, offer alternative solutions or workarounds for Linux users who require standalone clusters.
GitHub Create Pull Request
Service Fabric Azure Service Fabric deployment with FabricClient ...service-fabric-deploy-remove-applications-fabricclient.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias. It references Visual Studio and PowerShell as the primary tools for packaging and deploying Service Fabric applications, with file paths and workflows specific to Windows environments. All example paths use Windows conventions (e.g., C:\Users\...), and troubleshooting steps rely on PowerShell cmdlets and Windows SDK modules. There are no Linux/macOS equivalents or cross-platform CLI examples for key steps such as package verification, upload, or troubleshooting. The documentation does not mention how to perform these tasks on Linux/macOS, nor does it provide guidance for non-Windows environments.
Recommendations
  • Add explicit instructions and examples for Linux/macOS users, including file path conventions and alternative tools.
  • Provide Service Fabric CLI (sfctl) examples for all major steps (upload, register, remove, troubleshoot) alongside or before PowerShell examples.
  • Clarify how to verify and compress application packages using cross-platform tools (e.g., zip, tar, sfctl).
  • Include troubleshooting steps using CLI or REST API methods that work on Linux/macOS.
  • Avoid assuming Visual Studio or PowerShell as the default workflow; mention cross-platform development environments.
  • Use generic or platform-neutral file paths in code samples where possible.
GitHub Create Pull Request
Service Fabric Learn more about Azure Service Fabric ...icles/service-fabric/service-fabric-content-roadmap.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example Powershell Heavy
Summary
The documentation exhibits a moderate Windows bias. Windows-specific tools and patterns (such as PowerShell cmdlets and Visual Studio) are mentioned before or more prominently than their Linux equivalents. Examples and instructions for cluster creation and management often default to Windows, with Linux support described as secondary or unavailable (e.g., standalone clusters). Windows services and executables are referenced without Linux equivalents or explanations. Linux support is acknowledged but not given equal example coverage.
Recommendations
  • Provide Linux-specific examples and instructions alongside Windows ones, especially for cluster creation, management, and lifecycle operations.
  • Mention Linux CLI tools (e.g., sfctl) and scripting options before or alongside PowerShell, not after.
  • Include references to Linux service management (systemd, etc.) and equivalents for Windows services like FabricHost.exe.
  • Clarify feature parity and limitations for Linux up front, and link to Linux-specific guides where relevant.
  • Add sample workflows for Linux users, including container orchestration and application deployment.
  • Avoid listing Windows tools (PowerShell, Visual Studio) first; present both platforms equally.
GitHub Create Pull Request
Service Fabric Event Aggregation with Microsoft Azure Diagnostics ...ic/service-fabric-diagnostics-event-aggregation-wad.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias. Windows-specific tools (WAD, PowerShell, Visual Studio) are referenced throughout, with configuration examples and instructions focused almost exclusively on Windows clusters. The main body, code snippets, and step-by-step guides all assume use of Windows diagnostics (WAD) and ETW, with no Linux-specific configuration or troubleshooting guidance. While a Linux selector is present at the top, the actual content and examples are Windows-centric, and Linux equivalents (such as LAD, Bash, or Linux logging patterns) are missing or relegated to a separate page.
Recommendations
  • Integrate Linux (LAD) examples and configuration steps directly into the main documentation, not just as a separate page.
  • Provide equivalent Bash/CLI commands for cluster deployment and diagnostics extension management, alongside PowerShell.
  • Include Linux logging and event collection patterns, such as syslog, journald, or LAD configuration, with sample templates.
  • Reference Linux troubleshooting and monitoring tools (e.g., journalctl, logrotate) where Visual Studio or ETW is mentioned for Windows.
  • Ensure parity in guidance for Application Insights and Azure Monitor integration for both Windows and Linux clusters.
GitHub Create Pull Request
← Previous Page 19 of 29 Next →