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 1176-1200 of 2475 flagged pages
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-19 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation provides a thorough conceptual overview of X.509 certificate-based authentication in Service Fabric clusters, but exhibits Windows bias in several ways. Windows-specific terminology (e.g., certificate stores like LocalMachine\My), references to Windows APIs (Win32 CryptoAPI, CertGetCertificateChain), and troubleshooting instructions (event logs, CAPI2 logging) are presented first and in detail. Linux equivalents are mentioned briefly or parenthetically, but not explained or exemplified. No Linux-specific troubleshooting guidance or certificate store management examples are provided.
Recommendations
  • Add explicit Linux examples for certificate store paths and management (e.g., using openssl, Linux certificate directories).
  • Provide troubleshooting guidance for Linux nodes, including log locations and relevant tools.
  • When referencing Windows APIs or tools, also mention Linux equivalents (e.g., OpenSSL, systemd journal, /var/log).
  • Include Linux-specific error codes and remediation steps where applicable.
  • Ensure that all configuration examples (manifest XML, JSON) clarify any OS-specific differences.
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-19 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides examples for configuring Service Fabric managed cluster node types using the Azure Portal, ARM templates, and PowerShell. PowerShell is the only CLI example provided, and it is presented as the exclusive scripting option for command-line operations. There are no examples or mentions of Linux/macOS-compatible CLI tools (such as Azure CLI or Bash scripts), and PowerShell is shown before any Linux alternatives (which are missing). This creates friction for Linux/macOS users who may not have access to PowerShell or prefer Azure CLI.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all command-line operations (adding, removing, scaling node types, etc.).
  • Explicitly mention that PowerShell examples are Windows-centric and provide guidance for Linux/macOS users.
  • Consider including Bash script samples or references to cross-platform tools where possible.
  • Clarify whether all operations can be performed with Azure CLI or if PowerShell is required for certain advanced scenarios.
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-19 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides a PowerShell-only example for bypassing Infrastructure Service, and references Service Fabric Explorer (a GUI tool typically used on Windows). No Linux/bash equivalents or cross-platform CLI alternatives are mentioned. Most instructions and tooling references implicitly assume Windows environments, creating friction for Linux/macOS users.
Recommendations
  • Add equivalent bash or Azure CLI examples for cluster operations, especially for bypassing Infrastructure Service.
  • Clarify whether Service Fabric Explorer is available cross-platform or provide alternatives for Linux/macOS users.
  • Mention any prerequisites or limitations for Linux/macOS users explicitly.
  • Where possible, provide links to cross-platform tools or documentation.
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-19 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides examples and links for Azure PowerShell prominently, with PowerShell-based actions mentioned first in the 'Best practices' section. While Azure CLI is listed as an ARM-backed tool, PowerShell is emphasized for operational tasks, and no Linux-specific command examples or shell scripts are provided. The page does not exclusively reference Windows tools, but the focus on PowerShell may create friction for Linux/macOS users.
Recommendations
  • Add explicit Azure CLI examples for key operations (e.g., deleting NodeTypes, restarting/reimaging scale sets) alongside PowerShell examples.
  • Mention cross-platform tools (like Azure CLI and sfctl) earlier and equally in the 'Best practices' section.
  • Clarify that Azure PowerShell is available cross-platform, but provide CLI alternatives for Linux/macOS users.
  • Where possible, provide sample commands for both PowerShell and CLI for parity.
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-19 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 blocking operations. It consistently references Az PowerShell cmdlets (e.g., Remove-AzResource, AzSF PowerShell cmdlets) for resource operations, and only briefly mentions the Azure CLI ('az resource') for deleting applications. There are no explicit Linux/macOS examples or references to cross-platform tools, and PowerShell-based instructions are presented first and most often.
Recommendations
  • Add explicit Azure CLI examples for all operations (e.g., unprovisioning application type versions, creating applications/services, scaling, and deletions), since Azure CLI is cross-platform and works on Linux/macOS.
  • Where PowerShell cmdlets are referenced, provide equivalent Azure CLI commands alongside, and clarify which tools are available on which platforms.
  • Consider reorganizing sections so that cross-platform tools (Azure CLI) are presented before or alongside PowerShell examples.
  • Add notes or guidance for Linux/macOS users, indicating how they can perform the same operations without PowerShell.
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-19 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides migration guidance for Azure Service Fabric clusters to availability zone support. While most of the guidance is platform-neutral and focuses on Azure Resource Manager templates, the only explicit command-line examples are PowerShell-based and reference Windows tools (e.g., Service Fabric PowerShell cmdlets, AzureRm modules). The PowerShell examples are given exclusively, with no equivalent Bash, Azure CLI, or Linux-native instructions. Additionally, sample templates referenced are often for Windows (e.g., '15-VM-Windows-Multiple-AZ-Secure'), and Windows paths (e.g., 'D:\\SvcFab') are used in configuration snippets. Linux equivalents are not provided or are mentioned only in passing.
Recommendations
  • Add Azure CLI or Bash examples for all migration steps currently shown only in PowerShell.
  • Reference and link to Linux/Ubuntu sample templates equally alongside Windows templates.
  • When showing configuration snippets, use platform-neutral paths or provide both Windows and Linux examples (e.g., 'D:\\SvcFab' and '/var/svcfab').
  • Explicitly mention that Service Fabric clusters can run on Linux and provide guidance for Linux users where appropriate.
  • Include notes or sections for Linux-specific considerations, such as certificate management or node disabling/removal using cross-platform tools.
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-19 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation covers Azure Service Fabric application security in a cross-platform manner, but several sections show Windows bias. Windows-specific features (e.g., AD accounts, gMSA, BitLocker) are mentioned before Linux equivalents or without Linux parity. Some examples and links are Windows-centric (e.g., disk encryption via PowerShell, running services as AD users/groups), and Linux-specific guidance is missing or only briefly referenced. The section on encrypting disks has a TODO for Linux, indicating incomplete Linux coverage.
Recommendations
  • Add explicit Linux examples and guidance for disk encryption, including links to Azure documentation for encrypting disks on Linux VMSS clusters.
  • When mentioning Windows-specific features (e.g., AD accounts, gMSA, BitLocker), clarify Linux alternatives or limitations, and provide links to relevant Linux documentation.
  • Ensure parity in examples for running services under different accounts, showing both Windows and Linux approaches.
  • Review the order of presentation so Linux options are not consistently secondary to Windows options.
  • Complete the TODO for Linux disk encryption and BitLocker alternatives.
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-19 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides monitoring guidance for Azure Service Fabric clusters on both Windows and Linux, but there are several areas where Windows tools and patterns are mentioned first or exclusively. Windows-specific tools (Event Log, Event Viewer, Diagnostics Agent) are referenced before Linux equivalents, and some example/tutorial links focus on .NET/Windows scenarios. Linux alternatives are sometimes mentioned, but often as secondary or with less detail. There are few explicit Linux-focused examples or walkthroughs, and some features (like EventStore APIs) are noted as Windows-only without Linux alternatives or workarounds.
Recommendations
  • Ensure Linux monitoring tools and patterns are described with equal prominence and detail as Windows equivalents.
  • Add Linux-focused example walkthroughs and tutorials, especially for application monitoring and cluster diagnostics.
  • Where Windows-only features are mentioned (e.g., EventStore APIs), provide clear guidance or links for Linux users to achieve similar outcomes.
  • When referencing tools (e.g., Service Fabric Explorer, logging frameworks), clarify cross-platform compatibility and provide Linux/macOS setup instructions.
  • Avoid listing Windows tools or patterns first unless they are truly more relevant; alternate order or group by OS where appropriate.
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-19 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 all lifecycle phases (deploy, test, upgrade, remove, maintenance). While REST API and .NET methods are also mentioned, PowerShell examples are prominent and often listed before cross-platform alternatives. There is minimal mention of Linux-specific tools or CLI usage (such as sfctl or Azure CLI), and no explicit Linux/macOS examples are provided. The inclusion of PowerShell as the primary automation method and lack of Linux parity creates friction for non-Windows users.
Recommendations
  • Add explicit examples using sfctl (Service Fabric CLI) and Azure CLI for each lifecycle phase, especially for deployment, upgrade, and removal.
  • Ensure that cross-platform tools are mentioned alongside PowerShell cmdlets, not after or instead of them.
  • Provide sample commands and workflows for Linux/macOS environments, including file management and automation.
  • Clarify which methods and tools are available on Linux clusters and which are Windows-only.
  • Consider reordering examples so that REST API, sfctl, and Azure CLI are presented before or alongside 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-19 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page for 'Advanced Application Upgrade Topics' in Azure Service Fabric is heavily focused on PowerShell cmdlets and Windows-centric tooling. All command-line examples use PowerShell, and references to Service Fabric management are exclusively via PowerShell commands. There is no mention of Linux/macOS equivalents, such as the Service Fabric CLI (sfctl), nor are cross-platform examples provided. The documentation assumes the reader is using Windows and PowerShell, creating friction for Linux/macOS users who must translate instructions to their environment.
Recommendations
  • Add equivalent examples using the Service Fabric CLI (sfctl), which is cross-platform and supported on Linux/macOS.
  • Mention that PowerShell examples are for Windows and provide links or instructions for Linux/macOS users.
  • Where possible, provide ARM template or REST API examples alongside PowerShell to ensure platform neutrality.
  • Update 'Next steps' to include tutorials for Linux/macOS users, such as upgrading applications using sfctl.
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-19 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides links to application upgrade tutorials using Visual Studio and PowerShell, both of which are primarily Windows tools. The PowerShell example is explicitly mentioned, while there is no reference to Linux-native tools or CLI equivalents for application upgrades. The serialization discussion is focused on C# and .NET, but this is appropriate for Service Fabric workloads and does not constitute bias. However, the upgrade guidance leans towards Windows-centric tooling.
Recommendations
  • Add references or links to application upgrade tutorials using Azure CLI or Service Fabric CLI (sfctl), which are cross-platform and commonly used on Linux/macOS.
  • Clarify whether PowerShell Core (pwsh) is supported for Linux/macOS users, or provide alternative instructions for those environments.
  • Consider including examples or guidance for upgrading applications from Linux/macOS environments, if supported by Service Fabric.
  • If Visual Studio is Windows-only, mention cross-platform alternatives such as Visual Studio Code or command-line tools.
GitHub Create Pull Request
Service Fabric Architecture of Azure Service Fabric ...articles/service-fabric/service-fabric-architecture.md
Medium Priority View Details →
Scanned: 2026-02-19 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation mentions PowerShell cmdlets as a primary management interface for Service Fabric, without referencing equivalent Linux/macOS tooling (such as Azure CLI or REST APIs). Additionally, Windows security is mentioned alongside X509 certificates in the transport subsystem, with no discussion of Linux authentication patterns. These choices suggest a Windows-first bias, though most architectural concepts are platform-neutral.
Recommendations
  • Add references to Linux/macOS-compatible management tools, such as Azure CLI and REST APIs, alongside PowerShell.
  • Clarify that PowerShell cmdlets are available cross-platform, or provide Linux/macOS-specific examples where relevant.
  • Mention Linux authentication mechanisms (e.g., certificate-based, SSH) in the transport subsystem discussion.
  • Ensure that all platform-neutral concepts are illustrated with examples or notes for both Windows and Linux environments.
GitHub Create Pull Request
Service Fabric Restoring backup in Azure Service Fabric ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-backup-restore-service-trigger-restore.md
Medium Priority View Details →
Scanned: 2026-02-19 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page for restoring backups in Azure Service Fabric is heavily biased towards Windows and PowerShell usage. All code examples and instructions rely on PowerShell modules and cmdlets, with no mention of Linux/macOS-compatible tooling or CLI alternatives. The prerequisite section explicitly requires installation of a PowerShell module, and all REST API usage is demonstrated via PowerShell scripts. There are no Bash, Azure CLI, or curl examples, nor any guidance for non-Windows environments.
Recommendations
  • Add equivalent Bash or shell script examples using curl or HTTPie for REST API calls.
  • Document how to use Azure CLI or other cross-platform tools to trigger backup and restore operations.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is supported on PowerShell Core (pwsh) for Linux/macOS, and provide installation instructions if so.
  • Explicitly state any limitations or requirements for Windows-only tooling, and provide workarounds or alternatives for Linux/macOS users.
  • Consider including a section or callout for Linux/macOS users, outlining supported approaches and any differences.
GitHub Create Pull Request
Service Fabric Service Fabric application upgrade ...s/service-fabric/service-fabric-application-upgrade.md
Medium Priority View Details →
Scanned: 2026-02-19 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation for Service Fabric application upgrades demonstrates a notable Windows bias. PowerShell is used exclusively in code examples, and Windows-specific tools (e.g., http.sys) are referenced without Linux equivalents. There are no CLI or Linux-native examples, and PowerShell-based upgrade instructions are presented first and exclusively. This creates friction for Linux/macOS users, who may use Service Fabric clusters on Linux or need cross-platform automation.
Recommendations
  • Add equivalent Azure CLI or Service Fabric CLI (sfctl) examples for all PowerShell commands, especially for application parameter retrieval and upgrade operations.
  • Explicitly mention cross-platform tools and workflows where possible, and clarify any Windows-only limitations.
  • When referencing Windows-specific components (e.g., http.sys), provide Linux equivalents or note if the limitation is Windows-only.
  • Reorder or parallelize examples so that Linux/macOS and Windows instructions are presented together or with equal prominence.
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-19 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on PowerShell and the Microsoft.ServiceFabric.Powershell.Http module, with all command-line examples using PowerShell syntax and cmdlets. There are no equivalent examples for Linux/macOS users (e.g., using Bash, curl, or cross-platform Service Fabric CLI tools). The only alternative mentioned is Service Fabric Explorer (a web UI), but no guidance is provided for Linux command-line users.
Recommendations
  • Provide equivalent examples using Bash and curl for REST API calls, including certificate authentication steps for Linux/macOS.
  • Mention and demonstrate the use of cross-platform Service Fabric CLI tools (if available) for backup operations.
  • Clarify in the prerequisites whether the PowerShell module is supported on PowerShell Core (pwsh) on Linux/macOS, or if it is strictly Windows-only.
  • Add a section or callout for Linux/macOS users explaining how to perform on-demand backups without relying on Windows-specific tools.
GitHub Create Pull Request
Service Fabric Understanding periodic backup configuration ...-fabric-backuprestoreservice-configure-periodic-backup.md
Medium Priority View Details →
Scanned: 2026-02-19 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page is generally platform-neutral, focusing on Azure Service Fabric's backup configuration concepts and REST APIs. However, in the 'File share' backup storage section, examples and instructions exclusively reference Windows-style file shares (\\StorageServer\BackupStore) and Integrated Windows Authentication, without mentioning or providing Linux-compatible alternatives (such as SMB mounting on Linux or NFS). The documentation also describes Windows authentication patterns first and does not clarify Linux support or provide parity guidance.
Recommendations
  • Add explicit guidance for Linux clusters, including how to configure file share backup storage using SMB or NFS mounts on Linux.
  • Provide examples for mounting and accessing file shares from Linux nodes, including authentication options (e.g., username/password, Kerberos).
  • Clarify whether Integrated Windows Authentication is required or if Linux-compatible authentication methods are supported.
  • Mention any limitations or considerations for Linux clusters regarding file share backup storage.
  • If file share backup is Windows-only, state this clearly to avoid confusion.
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-19 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 featured prominently and used for cluster upgrade operations without Linux shell equivalents. Windows-specific tools and registry keys are mentioned for VM patching, and PowerShell is used exclusively for manual cluster upgrades. Windows configuration properties are shown before Linux equivalents, and Linux-specific guidance is less detailed.
Recommendations
  • Add Bash or Linux shell equivalents for manual cluster upgrade steps (e.g., using deb packages and Linux commands).
  • Provide Linux-specific VM configuration examples, such as disabling automatic updates for Linux VMs.
  • Include Linux registry/configuration guidance where relevant, or clarify when steps are Windows-only.
  • Ensure Linux examples are given equal prominence and detail as Windows examples, especially for upgrade and patching scenarios.
GitHub Create Pull Request
Service Fabric Change Azure Service Fabric cluster settings ...rvice-fabric/service-fabric-cluster-fabric-settings.md
Medium Priority View Details →
Scanned: 2026-02-19 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page provides a comprehensive reference for Service Fabric cluster settings, but exhibits mild Windows bias in several areas. Windows terminology (e.g., 'Windows Fabric', 'Windows only') is used in parameter descriptions, and Windows certificate store names ('MY', 'LocalMachine') are referenced without Linux equivalents or clarification. Some settings (e.g., NTLM authentication, Windows Update integration, log file settings) are marked as 'Windows only' or default to Windows values, with Linux-specific guidance missing or less prominent. The introductory guidance and links reference Windows standalone clusters before Linux, and Linux-specific settings (like certificate folders or executable paths) are less visible or explained. No explicit Linux examples or parity guidance are provided for settings that differ between platforms.
Recommendations
  • Add Linux-specific examples and guidance for settings where behavior or defaults differ (e.g., certificate stores, log file locations, NTLM authentication).
  • Clarify which parameters are Windows-only and which are cross-platform, and provide Linux equivalents or alternatives where possible.
  • Ensure Linux terminology and paths are shown alongside Windows ones, especially for certificate management and file paths.
  • Add explicit notes or tables summarizing platform-specific differences for key settings.
  • Review introductory guidance and links to ensure Linux clusters are referenced equally and not only after Windows.
  • Where settings are marked 'Windows only', provide Linux alternatives or state if the feature is unavailable.
GitHub Create Pull Request
Service Fabric Azure Service Fabric networking best practices ...ice-fabric/service-fabric-best-practices-networking.md
Medium Priority View Details →
Scanned: 2026-02-19 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 provides both Windows and Linux guidance in several areas, but there are notable Windows biases. Windows/PowerShell examples and terminology are often presented first or exclusively (e.g., PowerShell APIs, Windows container networking, ARM template samples for Windows clusters). Some explanations reference Windows-specific tools (e.g., netsh, PowerShell) without Linux equivalents. Linux examples are sometimes missing or less detailed, and Windows-centric scenarios (like patching) are described in more depth.
Recommendations
  • Ensure Linux examples (e.g., CLI commands, Linux container networking) are provided alongside Windows/PowerShell examples.
  • Where PowerShell or Windows tools are mentioned, add equivalent Linux commands (e.g., show dynamic port range on Linux).
  • Balance the order of examples and explanations so Linux is not consistently secondary.
  • Expand Linux-specific best practices, such as patching, monitoring, and application networking.
  • Provide ARM template samples for Linux clusters with NSG setup, not just Windows.
  • Clarify when guidance is Windows-only and provide Linux alternatives where possible.
GitHub Create Pull Request
Service Fabric Azure Service Fabric security best practices ...rvice-fabric/service-fabric-best-practices-security.md
Medium Priority View Details →
Scanned: 2026-02-19 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Windows and Linux guidance for key security tasks, but Windows-specific examples (e.g., PowerShell commands, Windows Defender, Windows security baselines) are often presented first or in greater detail. Windows tools and terminology (PowerShell, Windows Defender, DSC) are mentioned exclusively or before Linux equivalents. Some sections (e.g., Windows Defender, Windows security baselines) are Windows-only, but these are clearly marked as such. Linux examples are present for certificate generation and secret encryption, but Windows examples are more prominent and detailed.
Recommendations
  • Ensure Linux examples are presented alongside Windows examples, not after them, and with equal prominence.
  • Where possible, provide Linux equivalents for security baseline guidance (e.g., reference CIS Linux benchmarks or Azure Linux security extensions).
  • Add clarifying notes when a feature or tool is Windows-only, and link to Linux alternatives or best practices.
  • For sections like certificate management and secret encryption, ensure Linux instructions are as detailed as Windows instructions.
  • Consider structuring sections so that Windows and Linux guidance are parallel, rather than Windows-first.
GitHub Create Pull Request
Service Fabric Node types and virtual machine scale sets ...les/service-fabric/service-fabric-cluster-nodetypes.md
Medium Priority View Details →
Scanned: 2026-02-19 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page provides general information about Azure Service Fabric node types and virtual machine scale sets, but there are subtle signs of Windows bias. While the JSON extension snippet references both 'ServiceFabricLinuxNode' and 'ServiceFabricNode', the example settings (e.g., 'dataPath': 'D:\\SvcFab') use Windows-style paths. Additionally, the 'Next steps' section links to PowerShell scripts for RDP port changes and admin credential updates, which are Windows-centric tasks, without mentioning equivalent Linux guidance or SSH examples.
Recommendations
  • Provide Linux/Unix-style examples for paths (e.g., '/var/svcfab') alongside Windows paths in configuration snippets.
  • Add links or guidance for managing Linux nodes, such as SSH access, changing SSH port ranges, and updating Linux admin credentials.
  • Ensure parity in 'Next steps' by including Linux-focused operational tasks and scripts.
  • Clarify when examples are Windows-specific and offer Linux alternatives where possible.
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-02-19 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 code examples in C# and PowerShell for configuring Service Fabric placement policies, but does not include equivalent Linux/macOS CLI or scripting examples (e.g., Bash, Azure CLI). PowerShell is featured prominently and exclusively for command-line configuration, suggesting a Windows-centric approach. There is no mention of Linux tools or cross-platform alternatives, and PowerShell examples are shown before any Linux equivalents (which are missing).
Recommendations
  • Add Azure CLI examples for configuring placement policies, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include Bash or shell script snippets where applicable, especially for service deployment and configuration.
  • Explicitly mention whether the PowerShell commands can be run on PowerShell Core (cross-platform) or if they are Windows-only.
  • Provide guidance for Linux/macOS users on how to achieve the same configurations, referencing relevant tools or APIs.
  • Clarify any platform-specific limitations or requirements for Service Fabric clusters (e.g., if certain policies are only supported on Windows nodes).
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-19 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 provides only PowerShell and C# examples for managing Application Groups in Service Fabric clusters. PowerShell is a Windows-centric tool, and no equivalent Linux/macOS CLI or scripting examples (such as Bash, Azure CLI, or REST API) are given. The PowerShell examples are consistently presented before C# code, reinforcing Windows-first patterns. There is no mention of Linux-native tools or cross-platform approaches, creating friction for Linux/macOS users.
Recommendations
  • Add Azure CLI examples for all operations (creation, update, querying, removal) alongside PowerShell.
  • Include REST API sample calls for managing Application Groups, which are platform-agnostic.
  • Explicitly note any limitations or differences for Linux-based Service Fabric clusters, if applicable.
  • Consider Bash scripting examples or references to cross-platform tools where possible.
  • Clarify whether PowerShell examples are usable on PowerShell Core (cross-platform) or only Windows PowerShell.
GitHub Create Pull Request
Service Fabric Describe a cluster by using Cluster Resource Manager ...ce-fabric-cluster-resource-manager-cluster-description.md
Medium Priority View Details →
Scanned: 2026-02-19 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides configuration examples for both Windows (ClusterManifest.xml) and cross-platform/standalone (ClusterConfig.json) deployments, but consistently presents Windows-specific XML examples first and includes PowerShell commands for service creation and updates without equivalent Linux CLI or SDK examples. The use of WindowsServer in XML examples and PowerShell for operational tasks may create friction for Linux users, though JSON-based configuration and .NET SDK examples are also present.
Recommendations
  • Present Linux/standalone (ClusterConfig.json) examples before or alongside Windows (ClusterManifest.xml) examples to avoid Windows-first ordering.
  • Add equivalent Linux CLI (e.g., Azure CLI, sfctl) or bash script examples for service creation and updates, alongside PowerShell commands.
  • Clarify when XML examples are Windows-only and when JSON examples are cross-platform, to help users identify relevant sections.
  • Explicitly mention Linux support for standalone Service Fabric clusters and link to Linux-specific operational documentation where relevant.
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-02-19 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides code examples for managing Service Fabric metrics primarily in C# and PowerShell. PowerShell is a Windows-centric tool, and no equivalent Linux/macOS CLI examples (such as Azure CLI or Bash scripts) are provided. The PowerShell examples are given alongside C# code, but there is no mention of cross-platform tools or patterns for Linux users. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other scripting environments.
Recommendations
  • Add Azure CLI examples for service creation and metric management, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Mention Bash scripting or REST API usage for metric configuration and dynamic load reporting, with sample commands.
  • Clarify whether the PowerShell commands can be run in PowerShell Core (which is cross-platform) or if they require Windows PowerShell.
  • Provide guidance or links for Linux/macOS users on how to perform equivalent operations without PowerShell.
  • Consider reordering examples so that cross-platform tools are shown first or alongside Windows-specific tools.
GitHub Create Pull Request
← Previous Page 48 of 99 Next →