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 551-575 of 718 flagged pages
Service Fabric Add a managed identity to a Service Fabric managed cluster node type ...ed-identity-managed-cluster-virtual-machine-scale-sets.md
Medium Priority View Details →
Scanned: 2026-01-12 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 command-line examples exclusively using PowerShell cmdlets (New-AzResourceGroup, New-AzUserAssignedIdentity, New-AzRoleAssignment, etc.), with no equivalent Azure CLI or Bash examples for Linux/macOS users. The VM image configuration in the ARM template defaults to Windows Server, and references to Linux VM images or deployment patterns are absent. Troubleshooting and deployment instructions reference the Azure portal and PowerShell, omitting Linux-native workflows.
Recommendations
  • Add Azure CLI examples for all PowerShell commands, ensuring Linux/macOS users can follow along without needing PowerShell.
  • Include ARM template snippets or parameter sets for Linux VM images (e.g., Ubuntu), and clarify how to use managed identities with Linux node types.
  • Reorder examples so that cross-platform (ARM template, Azure CLI) instructions appear before or alongside PowerShell examples.
  • Explicitly mention Linux support and link to relevant documentation for Linux Service Fabric clusters where applicable.
GitHub Create Pull Request
Service Fabric Monitoring data reference for Azure Service Fabric ...les/service-fabric/monitor-service-fabric-reference.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias. Performance counter examples are exclusively Windows-centric, referencing Windows-specific categories and tools (e.g., Performance Monitor). There are no Linux equivalents or instructions for collecting similar metrics on Linux-based Service Fabric clusters. Windows tools and patterns are mentioned first and exclusively, with no parity for Linux users.
Recommendations
  • Add equivalent Linux performance counter categories and metrics, such as those available via sysstat, top, or collectd.
  • Provide instructions or examples for collecting metrics on Linux nodes, including recommended tools and integration with Azure Monitor.
  • Clarify which metrics are available on Linux clusters and note any differences or limitations.
  • Include screenshots or references to Linux monitoring tools (e.g., atop, htop, Prometheus exporters) alongside Windows Performance Monitor.
  • Explicitly state platform support for each metric or counter listed.
GitHub Create Pull Request
Service Fabric Deploy a Service Fabric managed cluster using the Azure portal ...es/service-fabric/quickstart-managed-cluster-portal.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation describes deploying a Service Fabric managed cluster using the Azure portal, focusing exclusively on portal-based steps and certificate management. The cluster nodes are explicitly stated to be Windows Server 2019 VMs, and there is no mention of Linux-based Service Fabric clusters or how Linux/macOS users might interact with the cluster, especially regarding certificate import and browser integration. All instructions and screenshots assume a Windows-centric workflow, with no guidance for Linux or macOS environments.
Recommendations
  • Add notes clarifying that Service Fabric managed clusters currently only support Windows node types, or provide information about Linux support if available.
  • Include instructions for importing and using client certificates on Linux and macOS (e.g., using Firefox, Chrome, or command-line tools like OpenSSL).
  • Provide guidance for Linux/macOS users on accessing Service Fabric Explorer, including browser certificate handling.
  • If possible, mention alternative cluster deployment options (e.g., ARM templates, CLI) and link to documentation with Linux/macOS parity.
  • Explicitly state platform limitations and recommend alternatives for non-Windows users where relevant.
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-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example Powershell Heavy
Summary
The documentation page exhibits moderate Windows bias. Windows-specific tools and patterns such as Active Directory domain accounts, group managed service accounts (gMSA), and BitLocker are mentioned with more detail and prominence than their Linux equivalents. Powershell is referenced for disk encryption, while Linux disk encryption is only noted as a TODO. Examples and guidance for running services under security accounts are detailed for Windows (including AD and gMSA), but Linux approaches are not described. In several sections, Windows features are discussed first or exclusively, with Linux support only briefly mentioned or omitted.
Recommendations
  • Provide equivalent Linux examples and instructions for all security features, such as running services under specific user accounts and encrypting disks.
  • Include Linux-specific tools and patterns (e.g., systemd service accounts, Linux file permissions, LUKS disk encryption) alongside Windows features.
  • Ensure that examples and guidance are presented in a cross-platform manner, or at least alternate the order in which Windows and Linux approaches are described.
  • Remove TODOs and replace them with actual Linux guidance and links.
  • Where Powershell is referenced, add Bash or CLI equivalents for Linux users.
GitHub Create Pull Request
Service Fabric Application lifecycle in Service Fabric ...service-fabric/service-fabric-application-lifecycle.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation consistently references PowerShell cmdlets and Windows-centric tools (e.g., Copy-ServiceFabricApplicationPackage, Register-ServiceFabricApplicationType) as primary command-line interfaces for managing Service Fabric applications. These are listed before or alongside REST API and .NET methods, but Linux-native equivalents (such as Azure CLI or sfctl) are not directly mentioned in step-by-step instructions or examples. The only nod to cross-platform tooling is a brief link to a page about Azure CLI and sfctl, without any concrete usage examples or parity in the main lifecycle walkthroughs.
Recommendations
  • Add explicit Linux/macOS-friendly command examples using Azure CLI and sfctl for each lifecycle phase (deploy, upgrade, remove, etc.), alongside PowerShell examples.
  • In each step where PowerShell cmdlets are referenced, include equivalent Azure CLI/sfctl commands and clearly indicate cross-platform options.
  • Reorder or parallelize examples so that Windows and Linux/macOS approaches are presented with equal prominence.
  • Expand the 'includes/service-fabric-sfctl.md' section to provide concrete, in-context examples rather than just a link.
GitHub Create Pull Request
Service Fabric Deploy and upgrade with Azure Resource Manager ...vice-fabric/service-fabric-application-arm-resource.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. PowerShell is the only command-line example provided for resource removal, with no equivalent Bash, Azure CLI, or Linux/macOS instructions. Windows-centric tools (PowerShell, Remove-AzResource) are mentioned exclusively or before Linux alternatives. The 'Next steps' section lists PowerShell before CLI, and there is no explicit guidance for Linux/macOS users or parity in examples.
Recommendations
  • Add equivalent Azure CLI and Bash examples for all PowerShell commands, especially for resource removal.
  • Explicitly mention that all operations can be performed from Linux/macOS using Azure CLI or REST API, and provide links.
  • In 'Next steps', list cross-platform tools (CLI, REST API) before or alongside PowerShell.
  • Include notes or sections clarifying platform compatibility and any differences in workflow for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Advanced Application Upgrade Topics ...-fabric/service-fabric-application-upgrade-advanced.md
Medium Priority View Details →
Scanned: 2026-01-12 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 exhibits a strong Windows bias, primarily by providing PowerShell-only examples and referencing Windows-centric tools and workflows (PowerShell cmdlets, Visual Studio) without mentioning or demonstrating equivalent Linux/macOS approaches (such as Azure CLI, REST API, or cross-platform SDKs). There are no Linux/macOS shell examples, and the guidance assumes familiarity with Windows tooling, which may hinder non-Windows users.
Recommendations
  • Add equivalent Azure CLI and/or REST API examples for all PowerShell cmdlets mentioned, especially for service creation, updates, and upgrades.
  • Explicitly mention cross-platform alternatives (e.g., Azure CLI, .NET SDK, REST API) and link to their documentation.
  • Provide sample commands for Linux/macOS environments (bash, CLI) alongside PowerShell examples.
  • Clarify which features or tools are available cross-platform and note any limitations.
  • Include a section on upgrading applications using Linux/macOS, with step-by-step instructions.
GitHub Create Pull Request
Service Fabric Manage Azure Service Fabric application secrets ...fabric/service-fabric-application-secret-management.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both Windows and Linux links for certificate setup, but in the critical section on deploying applications with encrypted secrets, only PowerShell (Windows) and C# examples are given. There is no Linux CLI or bash example for creating application instances with encrypted parameters, and the scripting example is Windows-centric (PowerShell). Windows tools and patterns (PowerShell) are mentioned exclusively for scripting, and Windows is implicitly prioritized in example order and tooling.
Recommendations
  • Add equivalent Linux CLI/bash examples for creating Service Fabric application instances with encrypted parameters (e.g., using sfctl or REST API).
  • Explicitly mention Linux tooling and scripting options alongside PowerShell, such as sfctl, Azure CLI, or bash scripts.
  • Ensure example order alternates or is grouped by platform, rather than defaulting to Windows/PowerShell first.
  • Clarify any platform-specific differences in scripting and deployment, and link to Linux-specific guides where appropriate.
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-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates Windows bias by listing Visual Studio and PowerShell upgrade tutorials as the only explicit 'next steps', both of which are primarily Windows tools. There are no Linux/macOS equivalents or examples provided, nor is there mention of cross-platform CLI alternatives. The focus on C# and Data Contract serialization is expected for Service Fabric, but the upgrade guidance is Windows-centric.
Recommendations
  • Add explicit instructions or links for upgrading applications using cross-platform tools such as Azure CLI or Service Fabric CLI (sfctl), which work on Linux/macOS.
  • Include examples or tutorials for performing upgrades from Linux/macOS environments.
  • Mention platform-agnostic approaches alongside Windows-specific tools in the 'Next steps' section.
  • Clarify which steps are Windows-only and provide Linux/macOS alternatives where possible.
GitHub Create Pull Request
Service Fabric Troubleshooting application upgrades ...https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-application-upgrade-troubleshooting.md
Medium Priority View Details →
Scanned: 2026-01-12 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 exclusively uses PowerShell commands and outputs for all troubleshooting and recovery examples, with no mention of Linux/macOS equivalents (such as Service Fabric CLI or REST API). Windows tooling (PowerShell, Visual Studio) is referenced throughout, and alternative Linux/macOS workflows are not described or linked. This creates friction for users on non-Windows platforms.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl) for Linux/macOS users alongside PowerShell commands.
  • Include references and links to documentation for CLI and REST API usage for troubleshooting and upgrades.
  • Explicitly state platform requirements for each command/tool and provide guidance for cross-platform users.
  • Balance the order of examples so that Linux/macOS tools are presented alongside or before Windows tools where appropriate.
  • Add troubleshooting steps and outputs for CLI/REST API workflows.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Central Secret Service ...vice-fabric/service-fabric-application-secret-store.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. All command-line examples for interacting with the Central Secret Service REST API use PowerShell and Windows-specific tooling (Invoke-WebRequest), with no equivalent Linux/macOS examples (e.g., curl). File paths and mount points show Windows first, with Linux alternatives only mentioned in comments. There is no guidance for Linux users on how to perform key actions, such as secret creation or management, using native Linux tools.
Recommendations
  • Provide Linux/macOS command-line examples using curl or similar tools alongside PowerShell examples.
  • Show both Windows and Linux file paths/mount points equally in documentation, not just as commented alternatives.
  • Explicitly mention authentication and certificate handling steps for Linux clusters, including how to install and reference certificates.
  • Add notes or sections clarifying any platform-specific differences in Service Fabric cluster configuration and secret management.
  • Where XML snippets reference file paths, show both Windows and Linux formats side by side.
GitHub Create Pull Request
Service Fabric Application upgrade: upgrade parameters ...abric/service-fabric-application-upgrade-parameters.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by prioritizing PowerShell and Visual Studio (Windows-only tools) in both structure and detail. The main parameter tables and explanations are presented first for PowerShell and Visual Studio, with SFCTL (the cross-platform CLI) covered only after. Examples and parameter formats are given for PowerShell (hashtable syntax) and Visual Studio dialogs, with less detail for SFCTL. There are no Linux/macOS-specific examples or notes, and Windows tools are mentioned and described before their Linux equivalents.
Recommendations
  • Reorder sections so that SFCTL (cross-platform CLI) is presented before or alongside PowerShell/Visual Studio.
  • Provide explicit Linux/macOS examples for SFCTL commands, including sample CLI invocations and parameter formats.
  • Add notes clarifying platform compatibility for each tool (e.g., PowerShell: Windows, SFCTL: Windows/Linux/macOS).
  • Include a table or summary comparing upgrade workflows across platforms.
  • Ensure that parameter descriptions and examples are equally detailed for SFCTL as for PowerShell.
  • Reference Linux/macOS upgrade tutorials more prominently, not just in 'Next steps'.
GitHub Create Pull Request
Service Fabric Service Fabric application upgrade ...s/service-fabric/service-fabric-application-upgrade.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. The only code example provided uses PowerShell, a Windows-centric tool, with no equivalent Bash or Linux CLI example. References to Windows-specific technologies (e.g., http.sys, PowerShell cmdlets) are present, and upgrade instructions prioritize Windows tools and workflows. There is no mention of Linux/macOS equivalents or cross-platform alternatives, making it difficult for non-Windows users to follow the upgrade process.
Recommendations
  • Provide equivalent Bash or Service Fabric CLI examples for Linux/macOS users alongside PowerShell examples.
  • Explicitly mention cross-platform tools (e.g., sfctl) and link to their documentation.
  • Clarify which instructions or features are Windows-only and offer alternatives where possible.
  • Add troubleshooting and upgrade workflow guidance for Linux/macOS environments.
  • Reorder examples so that cross-platform or Linux options are presented before or alongside Windows-specific ones.
GitHub Create Pull Request
Service Fabric Understanding periodic backup configuration ...-fabric-backuprestoreservice-configure-periodic-backup.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily in the backup storage section, where file share examples and authentication methods are described exclusively using Windows-style UNC paths (\\StorageServer\BackupStore) and Windows authentication mechanisms. There is no mention of Linux-compatible file share paths (such as NFS or SMB mounts), nor are Linux authentication patterns or examples provided. Windows terminology and tooling (Integrated Windows Authentication) are presented first and exclusively, with no Linux alternatives or parity.
Recommendations
  • Add examples for configuring backup storage using Linux-compatible file shares, such as NFS or SMB mounts, including sample paths and authentication methods.
  • Include instructions for mounting and accessing file shares from Linux nodes, with relevant commands and configuration details.
  • Clarify whether the backup feature supports Linux-based clusters and, if so, provide explicit guidance for Linux/macOS environments.
  • Present both Windows and Linux options in parallel, rather than Windows-first or Windows-only.
  • Mention any platform-specific limitations or requirements for backup storage types.
GitHub Create Pull Request
Service Fabric Upgrade the configuration of an Azure Service Fabric cluster ...-fabric/service-fabric-cluster-config-upgrade-azure.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation lists Windows-centric tools (PowerShell) before cross-platform alternatives (Azure CLI), and provides specific PowerShell command references. No explicit Linux/macOS examples or guidance are given, though Azure CLI is mentioned as an option.
Recommendations
  • Present Azure CLI examples and references before or alongside PowerShell, emphasizing CLI's cross-platform compatibility.
  • Include explicit Linux/macOS instructions or notes to reassure non-Windows users that all steps are supported on their platforms.
  • Provide sample commands for both PowerShell and Azure CLI, clearly labeling which platforms they work on.
  • Mention that Azure Resource Explorer and Azure Portal are web-based and platform-agnostic.
GitHub Create Pull Request
Service Fabric Architecture of Azure Service Fabric ...articles/service-fabric/service-fabric-architecture.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily in the Management subsystem section, where PowerShell cmdlets are mentioned as the main tooling for lifecycle management. There is no mention of Linux equivalents (such as Bash scripts, CLI commands, or REST APIs), nor are cross-platform tools highlighted. The transport subsystem also references Windows security as an option for securing communication, but does not mention Linux authentication mechanisms. No explicit Linux/macOS examples or tools are provided anywhere in the document.
Recommendations
  • Include references to cross-platform management tools, such as Azure CLI, REST APIs, or Bash scripts, alongside PowerShell.
  • Mention Linux authentication mechanisms (e.g., OpenSSL, PAM, or Kerberos) in the transport subsystem section.
  • Add explicit examples or notes for Linux/macOS users where platform-specific tooling is discussed.
  • Ensure that all tooling and command references are presented in a platform-neutral way, or provide parallel examples for both Windows and Linux/macOS.
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-01-12 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 exclusively provides PowerShell-based examples and instructions, which are native to Windows. All command-line operations (module installation, cluster connection, backup triggering, REST calls) are shown using PowerShell syntax and Windows-specific modules. There are no Linux/macOS CLI equivalents (e.g., Bash, curl, Azure CLI), nor any mention of how to perform these tasks on non-Windows platforms. The documentation assumes the use of Windows tooling throughout, creating friction for Linux/macOS users.
Recommendations
  • Add equivalent examples using Bash and curl for REST API calls.
  • Document how to authenticate and connect to Service Fabric clusters from Linux/macOS.
  • Provide Azure CLI or Service Fabric CLI (sfctl) examples for backup operations.
  • Clarify platform requirements for the Microsoft.ServiceFabric.Powershell.Http module and suggest alternatives for Linux/macOS.
  • Reorder examples so that cross-platform methods (REST API, Azure CLI) are shown before or alongside PowerShell.
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-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Service Fabric clusters, but PowerShell (a Windows-centric tool) is given a dedicated section and is used for cluster upgrades without Linux alternatives. Windows-specific registry and template settings are discussed in detail, while Linux equivalents are not mentioned. Upgrade instructions and disabling updates focus on Windows, with no Linux guidance. Although links to both Windows and Linux cluster creation tutorials are provided at the end, the main body of the documentation is notably Windows-focused.
Recommendations
  • Add Linux-specific instructions and examples for cluster upgrades, including shell commands and package formats (e.g., .deb for Linux).
  • Provide Linux equivalents for registry and update management (e.g., systemd, apt, yum, or configuration files).
  • Include Bash or other cross-platform scripting examples alongside PowerShell.
  • Clarify which steps are Windows-only and provide parity for Linux users where possible.
  • Present examples for both platforms in parallel, or alternate which platform is shown first.
GitHub Create Pull Request
Service Fabric Differences between Cloud Services (extended support) and Service Fabric ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cloud-services-migration-differences.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation references Service Fabric running on both Windows and Linux, but examples, API mappings, and tooling references (e.g., Connect-WindowsFabricCluster) are Windows-centric. There are no explicit Linux or cross-platform command-line examples, and Windows tools are mentioned without Linux equivalents. The ordering and language often put Windows first, and there is a lack of practical guidance for Linux users.
Recommendations
  • Provide explicit Linux examples and tooling references alongside Windows ones (e.g., show how to connect to a Service Fabric cluster from Linux).
  • Mention cross-platform tools and APIs where available, or clarify platform-specific differences.
  • Ensure that when listing supported platforms, Linux is mentioned equally and not as a secondary option.
  • Add migration guidance and code samples that work on Linux, including deployment and management steps.
  • Where Windows-specific tools are referenced (e.g., Connect-WindowsFabricCluster), include Linux alternatives or note their absence.
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-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias, particularly in its operational examples and tooling references. Key scaling procedures (both vertical and horizontal) are described using PowerShell commands and Windows-centric tools, with no equivalent Linux CLI or script examples provided. The step-by-step instructions for scaling in/out reference PowerShell and Service Fabric PowerShell cmdlets exclusively, omitting Linux alternatives such as Bash scripts or Service Fabric CLI commands. Additionally, Windows tools and patterns are mentioned first and more frequently, while Linux guidance is relegated to a single link in the 'Next steps' section.
Recommendations
  • Add Linux-specific examples for scaling operations, using Bash and Service Fabric CLI (sfctl) commands.
  • Include cross-platform instructions for disabling/removing nodes, not just PowerShell cmdlets.
  • Present both Windows and Linux procedures side-by-side or clearly indicate platform-specific steps.
  • Reference Linux tools (e.g., sfctl, Azure CLI) where appropriate, and provide links to their documentation.
  • Ensure that operational guidance (e.g., for scaling, node management) is not exclusively tied to Windows environments.
GitHub Create Pull Request
Service Fabric Service Fabric cluster capacity planning considerations ...cles/service-fabric/service-fabric-cluster-capacity.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. It references Windows-specific tools (such as Remove-ServiceFabricNodeState and Patch Orchestration Application) and provides instructions for standalone clusters only for Windows, with no equivalent Linux guidance. Additionally, when discussing configuration changes, Windows instructions are given before Linux/Azure instructions, and Linux/Unix-specific examples or tools are missing.
Recommendations
  • Add explicit guidance and examples for managing standalone clusters on Linux, including configuration upgrade instructions and relevant tooling.
  • When referencing tools or commands (e.g., Remove-ServiceFabricNodeState), clarify whether Linux equivalents exist or provide alternative Linux instructions.
  • Include Patch Orchestration Application alternatives or guidance for Linux clusters, or clarify its applicability.
  • Ensure that instructions for Azure-hosted clusters and standalone clusters are presented in parallel for both Windows and Linux, with equal prominence.
  • Where possible, use cross-platform terminology and avoid assuming Windows as the default environment.
GitHub Create Pull Request
Service Fabric Create an Azure Service Fabric cluster template ...ric/service-fabric-cluster-creation-create-template.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias, primarily by providing only PowerShell examples for testing the Resource Manager template, referencing Windows-centric sample templates, and omitting equivalent Linux/macOS CLI instructions. The sample template linked is for a Windows cluster, and there is no mention of using Azure CLI or Bash for Linux/macOS users. Windows tools and workflows are presented as the default, with Linux-specific guidance limited to a single note about Microsoft Entra ID setup.
Recommendations
  • Add Azure CLI and Bash examples for testing and deploying Resource Manager templates, alongside PowerShell.
  • Include links to sample templates for Linux clusters, not just Windows.
  • Present Windows and Linux/macOS instructions side-by-side or in separate tabs/sections for parity.
  • Clarify which steps and parameters are OS-agnostic and which are platform-specific.
  • Reference cross-platform tools (e.g., Azure CLI) before or alongside Windows-only tools.
GitHub Create Pull Request
Service Fabric Create an Azure Service Fabric cluster ...vice-fabric/service-fabric-cluster-creation-via-arm.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation exhibits a moderate Windows bias. PowerShell (a Windows-centric tool) is consistently presented first in all command examples, and Windows file paths (e.g., c:\certificates) are used in both PowerShell and Azure CLI examples, even when the CLI is cross-platform. There are no explicit Linux shell (bash) examples, and the use of Windows-specific tools and patterns (e.g., ConvertTo-SecureString, Set-AzKeyVaultAccessPolicy) is prevalent. While Ubuntu templates are referenced and the Azure CLI is shown, Linux/macOS users may encounter friction due to the lack of native shell examples and persistent Windows-centric defaults.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present CLI (cross-platform) first.
  • Provide native bash/Linux shell examples for all CLI commands, using Linux-style paths (e.g., /home/user/certificates) and environment variable syntax.
  • Explicitly note when a command or tool is Windows-only, and provide Linux/macOS equivalents where possible.
  • Use OS-agnostic language and file paths in documentation, or provide both Windows and Linux/macOS path examples.
  • Highlight any differences in prerequisites or setup steps for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Programmatic Scaling ...-fabric/service-fabric-cluster-programmatic-scaling.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias: PowerShell cmdlets are mentioned as the only scripting alternative to the .NET SDK, with no Linux/macOS equivalents (such as Azure CLI or Bash examples). Windows tools and patterns (PowerShell, .NET SDK) are referenced exclusively, and scripting examples are provided only for PowerShell, not for cross-platform shells. This may create friction for Linux/macOS users who do not use PowerShell.
Recommendations
  • Add Azure CLI examples for scaling operations, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Mention Bash scripting as an alternative to PowerShell for automation.
  • Present cross-platform examples (e.g., Azure CLI) before or alongside PowerShell examples.
  • Clarify which tools and SDKs are supported on Linux/macOS and provide relevant links.
  • Explicitly state that PowerShell is available on Linux/macOS, if recommending its use.
GitHub Create Pull Request
Service Fabric Specifying Service Fabric service endpoints ...ce-fabric/service-fabric-service-manifest-resources.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates a moderate Windows bias. It references Windows file paths for SDK/schema locations, uses PowerShell exclusively for deployment examples, and mentions Windows certificate stores before Linux equivalents. Linux-specific instructions are present but secondary, and no Linux shell (bash) deployment examples are provided.
Recommendations
  • Include Linux/macOS equivalents for all Windows-specific instructions, such as schema file locations and certificate stores.
  • Provide deployment examples using Azure CLI, Bash, or other cross-platform tools alongside PowerShell.
  • Mention Linux paths and procedures at the same prominence and order as Windows ones.
  • Clarify any platform-specific differences in endpoint configuration, certificate management, and port ACLing.
  • Add explicit notes or sections for Linux/macOS users where behaviors or commands differ.
GitHub Create Pull Request
← Previous Page 23 of 29 Next →