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 651-675 of 2475 flagged pages
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-03-01 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides PowerShell examples for managing node tags and configuring services, but does not offer equivalent Linux/bash/CLI examples. PowerShell is primarily a Windows tool, and its usage is presented before C# API examples. There is no mention of Linux-native tools or Azure CLI commands, which creates friction for Linux/macOS users.
Recommendations
  • Add Azure CLI or REST API examples for managing node tags and configuring services, as these are cross-platform.
  • Explicitly mention whether PowerShell Core (cross-platform) is supported, or clarify if only Windows PowerShell is required.
  • Provide bash or shell script examples where possible, or reference relevant Linux tooling.
  • Reorder examples so that cross-platform methods (e.g., REST API, Azure CLI) are shown before or alongside PowerShell.
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-03-01 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides PowerShell examples for application removal and references PowerShell as a primary tool for managing Service Fabric resources. While the main deployment workflow is based on Azure Resource Manager templates (cross-platform), the only explicit command-line example is in PowerShell, and PowerShell is mentioned before CLI alternatives. Linux/macOS users may need to adapt these steps or use REST API/CLI equivalents, which are not shown.
Recommendations
  • Add Azure CLI examples alongside PowerShell for resource management tasks, such as removing applications.
  • Mention cross-platform tools (e.g., Azure CLI, Service Fabric CLI) equally and provide links or examples for Linux/macOS users.
  • Clarify that PowerShell commands can be substituted with Azure CLI or REST API calls, and provide sample commands for those environments.
  • Ensure that references to PowerShell are not presented as the only or primary option unless the task is Windows-specific.
GitHub Create Pull Request
Service Fabric Application lifecycle in Service Fabric ...service-fabric/service-fabric-application-lifecycle.md
Medium Priority View Details →
Scanned: 2026-03-01 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation frequently references PowerShell cmdlets and Windows-centric tools (e.g., Remove-ServiceFabricApplicationPackage, Register-ServiceFabricApplicationType) alongside .NET API methods and REST operations. PowerShell examples are given in detail, and Windows tools are often mentioned first or exclusively. There is minimal mention of cross-platform CLI tools (such as sfctl or Azure CLI), and Linux/macOS equivalents are not provided or are only referenced via a generic include link. This creates friction for Linux/macOS users, who may not use PowerShell or Windows tools.
Recommendations
  • Add explicit examples using sfctl and Azure CLI for each lifecycle operation, alongside PowerShell and .NET API examples.
  • Ensure that cross-platform tools are mentioned before or equally with Windows tools in each section.
  • Clarify which tools are available on Linux/macOS and provide links to their documentation.
  • Where PowerShell is used, note any cross-platform alternatives and how to achieve the same outcome on Linux/macOS.
  • Expand the [links to azure cli and service fabric cli] include to show concrete usage examples in the main text.
GitHub Create Pull Request
Service Fabric Service Fabric application upgrade ...s/service-fabric/service-fabric-application-upgrade.md
Medium Priority View Details →
Scanned: 2026-03-01 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page for Service Fabric application upgrades demonstrates notable Windows bias. All code examples are provided exclusively in PowerShell, a Windows-centric tool, with no equivalent CLI or Linux/macOS examples. References to Windows-specific APIs (e.g., http.sys) and error messages reinforce the Windows focus. Additionally, upgrade instructions and links prioritize Windows tools (PowerShell, Visual Studio) without mentioning cross-platform alternatives such as Azure CLI or REST API. This creates friction for Linux/macOS users, who may not be able to follow the documented procedures directly.
Recommendations
  • Add equivalent examples using Azure CLI or REST API for application upgrades, especially for retrieving and passing application parameters.
  • Include guidance for Linux/macOS users, such as how to perform upgrades from non-Windows environments.
  • Mention cross-platform tools and workflows (e.g., Azure CLI, Service Fabric CLI) alongside PowerShell and Visual Studio.
  • Clarify which features or steps are Windows-only, and provide alternatives or workarounds for Linux/macOS users where possible.
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-03-01 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page for restoring backups in Azure Service Fabric is heavily biased towards Windows/PowerShell usage. All code examples use PowerShell, including REST API calls, and require installation of Microsoft.ServiceFabric.Powershell.Http module. There are no examples or guidance for Linux/macOS users (e.g., using Bash, curl, or Azure CLI), nor is there mention of cross-platform alternatives. The prerequisite to install a PowerShell module and connect to the cluster via PowerShell further reinforces the Windows-centric approach.
Recommendations
  • Add equivalent Bash/curl examples for REST API calls, showing how Linux/macOS users can trigger restores and track progress.
  • Mention Azure CLI or cross-platform tools if available for Service Fabric backup/restore operations.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is required for all platforms, or if there are alternatives for Linux/macOS.
  • Include a note about PowerShell Core compatibility on Linux/macOS, if relevant, or explicitly state if only Windows PowerShell is supported.
  • Provide guidance for Linux/macOS users on connecting to Service Fabric clusters and authenticating REST API calls.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Events ...es/service-fabric/service-fabric-diagnostics-events.md
Medium Priority View Details →
Scanned: 2026-03-01 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page for Azure Service Fabric Events primarily references Windows-specific logging mechanisms (ETW/Windows Event logs, Windows Azure diagnostics agent) and tools, with no mention of Linux equivalents or cross-platform approaches. Windows tools and patterns are mentioned first and exclusively, creating friction for Linux cluster administrators.
Recommendations
  • Add information about how Service Fabric events are logged and accessed on Linux clusters, including supported logging mechanisms (e.g., stdout, syslog, Azure Monitor integration for Linux).
  • Provide Linux-specific or cross-platform examples for accessing and analyzing events.
  • Clarify which features or instructions are Windows-only and offer Linux alternatives where possible.
  • Mention any limitations or differences in event access between Windows and Linux clusters.
GitHub Create Pull Request
Service Fabric Application upgrade: upgrade parameters ...abric/service-fabric-application-upgrade-parameters.md
Medium Priority View Details →
Scanned: 2026-03-01 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page presents Windows/PowerShell and Visual Studio parameters and examples first, with detailed tables and explanations, while Linux-centric tools (SFCTL CLI) are covered later and less prominently. The PowerShell and Visual Studio sections are more extensive and appear before SFCTL, potentially creating friction for Linux/macOS users. However, SFCTL parameters are documented, and Linux upgrade workflows are referenced in the 'Next steps' section.
Recommendations
  • Reorganize the page so that cross-platform tools (SFCTL, REST API) are presented alongside or before Windows-specific tools (PowerShell, Visual Studio).
  • Add explicit Linux/macOS usage examples for SFCTL in the main parameter tables, not just in the 'Next steps'.
  • Clarify which tools are cross-platform and which are Windows-only at the start of the article.
  • Ensure that parameter tables for SFCTL are as detailed and prominent as those for PowerShell/Visual Studio.
  • Consider adding a summary table comparing upgrade methods (PowerShell, Visual Studio, SFCTL, REST) and their platform support.
GitHub Create Pull Request
Service Fabric Architecture of Azure Service Fabric ...articles/service-fabric/service-fabric-architecture.md
Medium Priority View Details →
Scanned: 2026-03-01 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation references PowerShell cmdlets as a primary management interface for Service Fabric, and mentions Windows security as a transport option before X509 certificates. No Linux-specific management tools or examples are provided, and PowerShell is presented as the default for provisioning and lifecycle operations, which may create friction for Linux/macOS users.
Recommendations
  • Include references to cross-platform management tools, such as Azure CLI or REST APIs, alongside PowerShell cmdlets.
  • Clarify whether PowerShell cmdlets are available and supported on Linux/macOS, or provide alternative instructions for those platforms.
  • Mention Linux security mechanisms (e.g., certificate-based authentication) equally when discussing transport subsystem security.
  • Add examples or links for Linux/macOS users to manage Service Fabric clusters, if available.
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-03-01 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 on-demand backup in Azure Service Fabric is heavily biased toward Windows/PowerShell usage. All code examples use PowerShell, including REST API calls, and there are no examples or guidance for Linux/macOS users (e.g., Bash, curl, or Azure CLI). The prerequisite section mandates installation of a PowerShell module, and the workflow assumes PowerShell as the primary tool, creating friction for non-Windows users.
Recommendations
  • Add equivalent Bash/curl examples for REST API calls, so Linux/macOS users can trigger backups and track progress without PowerShell.
  • Mention Azure CLI commands if available for backup/restore operations.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is required only for PowerShell users, and provide alternative instructions for Linux/macOS environments.
  • Reorganize examples so that REST API usage is shown independently of PowerShell, and provide cross-platform guidance.
  • Explicitly state platform requirements and limitations, if any, for Service Fabric backup/restore operations.
GitHub Create Pull Request
Service Fabric Understanding periodic backup configuration ...-fabric-backuprestoreservice-configure-periodic-backup.md
Medium Priority View Details →
Scanned: 2026-03-01 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page is generally platform-neutral, focusing on Service Fabric backup configuration via REST APIs and JSON payloads. However, the only example for file share backup storage uses Windows-style UNC paths (\\StorageServer\BackupStore) and references 'Integrated Windows Authentication', with no mention of Linux-compatible file share paths or authentication methods. There are no Linux-specific examples or guidance for configuring file share backups from Linux-based Service Fabric clusters.
Recommendations
  • Add examples for file share backup storage using Linux-compatible paths (e.g., SMB/CIFS mounts, NFS, or local file system paths).
  • Document authentication methods for file shares on Linux (e.g., username/password, mount options) and clarify any limitations or requirements.
  • Explicitly state whether file share backup storage is supported on Linux clusters, and if so, provide parity examples and guidance.
  • If file share backup is Windows-only, clarify this explicitly in the documentation to avoid confusion.
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-03-01 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides several examples and references that prioritize Windows and PowerShell usage, such as mentioning PowerShell APIs and classic PowerShell tasks in Azure DevOps, referencing Windows-specific ARM templates, and describing Windows container networking patterns. Linux equivalents are sometimes mentioned but often appear after Windows examples or lack detailed guidance. Some sections, like port usage and tooling, are Windows-centric, and Linux-specific instructions or examples are limited or missing.
Recommendations
  • Add equivalent Linux CLI (az CLI, bash) examples alongside PowerShell examples, especially for cluster management and networking tasks.
  • Ensure Linux-specific ARM templates and sample links are provided, not just Windows-focused ones.
  • Clarify which networking patterns, port ranges, and tooling apply to Linux clusters, and provide explicit Linux guidance where differences exist.
  • Expand Linux container networking best practices and reference Linux container orchestration tools where relevant.
  • Where Windows tools (e.g., netsh) are mentioned, provide Linux alternatives (e.g., ss, ip, netstat) for port range checks.
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-03-01 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 the only scripting language shown for cluster upgrades. Windows-specific registry keys and VM configuration examples are included, while Linux equivalents or guidance are missing or not given equal prominence. Some upgrade and patching instructions focus on Windows (e.g., registry settings, disabling Windows Update) without Linux alternatives.
Recommendations
  • Provide equivalent Linux/bash examples for all PowerShell scripts, especially for cluster upgrade operations.
  • When discussing VM configuration (e.g., disabling automatic updates), include Linux-specific instructions or clarify when a step is Windows-only.
  • If a section is Windows-specific, clearly label it as such, and provide a parallel Linux section where applicable.
  • Ensure that Linux and Windows examples are presented with equal prominence, or alternate their order to avoid 'windows_first' bias.
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-03-01 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page provides only PowerShell and C# examples for managing Service Fabric Application Groups, with no mention of Linux-compatible CLI tools or commands. PowerShell is a Windows-centric tool, and its exclusive use in examples creates friction for Linux/macOS users, who typically use Bash or Azure CLI. There is no guidance or parity for Linux users, nor are cross-platform alternatives referenced.
Recommendations
  • Add Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and supported on Linux/macOS.
  • Mention and link to documentation for Service Fabric CLI (sfctl), which is the official cross-platform command-line tool for Service Fabric.
  • Clarify which management operations can be performed using sfctl or Azure CLI, and provide equivalent examples.
  • If PowerShell is required for certain operations, explicitly state this and explain any Linux/macOS workarounds or limitations.
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-03-01 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Windows-specific (ClusterManifest.xml with <WindowsServer> infrastructure) and cross-platform (ClusterConfig.json) examples for cluster configuration. However, Windows terminology and XML examples are presented first and more prominently. PowerShell examples are given for service creation and updates, but there are no equivalent Linux CLI or Bash examples. The documentation does not mention Linux-specific tools or patterns, nor does it clarify how Linux users should perform these tasks, even though Service Fabric supports Linux clusters.
Recommendations
  • Add explicit Linux cluster configuration examples (e.g., <Linux> infrastructure in ClusterManifest.xml) alongside Windows examples.
  • Include Bash or Azure CLI examples for service creation and updates, not just PowerShell.
  • Clarify any differences or limitations for Linux clusters, if applicable.
  • Ensure that cross-platform JSON examples are presented equally and not secondary to Windows XML examples.
  • Mention Linux node support and reference relevant documentation for Linux users.
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-03-01 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation provides a comprehensive reference for Service Fabric cluster settings, covering both Azure-hosted and standalone clusters. However, there is evidence of Windows bias: Windows terminology and tools (such as certificate store names like 'My', NTLM authentication, and references to Windows Defender Firewall) are used as defaults or examples, and Windows-specific settings are often mentioned before Linux equivalents. Some parameters and guidance reference Windows APIs or documentation (e.g., CertGetCertificateChain), and certain settings (like NTLM authentication) are inherently Windows-centric. Linux-specific settings are present but less prominent and sometimes only noted in parentheses.
Recommendations
  • Where parameters have different defaults or behaviors on Linux, clarify these explicitly and provide Linux-first examples.
  • For certificate store names and locations, add Linux equivalents and explain differences (e.g., file-based certificate storage vs. Windows store).
  • When referencing Windows APIs or documentation, provide Linux alternatives or note if the feature is not applicable.
  • Highlight Linux-specific settings (e.g., LinuxExternalExecutablePath) more prominently and ensure parity in guidance.
  • For authentication and firewall settings, clarify Linux support and alternatives, avoiding Windows-centric language where possible.
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-03-01 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 a conceptual overview of Service Fabric node types and their relationship to Azure VM scale sets. While the JSON snippet includes both 'ServiceFabricLinuxNode' and 'ServiceFabricNode' types, the example configuration uses a Windows-style file path ('D:\\SvcFab') and certificate store parameters, which are Windows-centric. The 'Next steps' section links to PowerShell scripts for RDP port and admin credential changes, which are Windows-specific tasks, without Linux/SSH equivalents or guidance. There is no explicit Linux/macOS example for connecting to nodes or managing credentials, and Windows tools and patterns are referenced first or exclusively.
Recommendations
  • Provide equivalent Linux/macOS examples for connecting to scale set instances (e.g., SSH instead of RDP).
  • Include sample configuration snippets that use Linux-style paths (e.g., '/var/svcfab') and certificate locations.
  • Add links or guidance for managing Linux admin credentials and SSH port ranges.
  • Clarify which steps or scripts are Windows-only and provide Linux alternatives where possible.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Auto Scaling Services and Containers ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-autoscaling.md
Medium Priority View Details →
Scanned: 2026-03-01 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides examples for configuring auto scaling policies in Azure Service Fabric using application manifests, C# APIs, and PowerShell. All CLI/script examples are PowerShell-based, which is primarily a Windows tool. There are no Linux shell (bash/CLI) equivalents, and PowerShell examples are presented alongside C# and manifest examples without alternatives for Linux users. Additionally, PowerShell is shown before any mention of Linux tooling, and there is no guidance for Linux users on how to perform equivalent operations.
Recommendations
  • Add bash/CLI examples for Linux users, such as using Azure CLI or REST API to configure scaling policies.
  • Explicitly mention cross-platform options where available, and clarify which steps are Windows-only.
  • If PowerShell is required, note that PowerShell Core is cross-platform and provide instructions for Linux/macOS users.
  • Include a section or note describing how Linux users can manage Service Fabric scaling policies (e.g., via Azure CLI, REST API, or Service Fabric CLI).
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-03-01 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 C# and PowerShell, but does not include equivalent Linux/macOS CLI examples (e.g., Azure CLI, Bash, or REST API). PowerShell commands are shown prominently, and there is no mention of Linux-native tools or cross-platform alternatives for managing Service Fabric metrics. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other tools.
Recommendations
  • Add Azure CLI examples for service creation and metric configuration, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Mention REST API options for managing Service Fabric metrics, with example requests.
  • Clarify whether PowerShell examples are Windows-only, and provide guidance for Linux/macOS users (e.g., using Azure CLI or Service Fabric CLI).
  • Where possible, include Bash script examples or references to Service Fabric CLI (sfctl), which is cross-platform.
  • Ensure that documentation sections do not assume PowerShell as the default scripting environment.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager: Movement cost ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-movement-cost.md
Medium Priority View Details →
Scanned: 2026-03-01 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 PowerShell examples for configuring move cost, but does not offer equivalent Linux/Unix shell (e.g., Bash/CLI) examples. PowerShell is primarily a Windows tool, and its exclusive use creates friction for Linux/macOS users. Additionally, PowerShell examples are presented before C# examples, reinforcing a Windows-first pattern. No mention is made of Azure CLI or REST API alternatives, which are cross-platform.
Recommendations
  • Add Azure CLI examples for service creation and updating move cost, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • If REST APIs exist for these operations, provide example requests and responses.
  • Explicitly note if PowerShell is required due to feature limitations, and link to any Linux-compatible tools or workarounds.
  • Consider presenting cross-platform examples (CLI, REST) before or alongside PowerShell to avoid Windows-first ordering.
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-03-01 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides configuration examples using Application Manifest (XML/JSON), PowerShell, and C# APIs. However, PowerShell is featured prominently for service creation and updates, with no equivalent CLI or Bash examples for Linux/macOS users. The PowerShell examples are shown before C# API examples, and there is no mention of cross-platform tools (such as Azure CLI or REST API) for these operations. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other tooling.
Recommendations
  • Add Azure CLI or REST API examples for service sensitivity and maximum load configuration, if supported.
  • Explicitly mention whether PowerShell commands can be run cross-platform (e.g., via PowerShell Core), or provide Bash equivalents.
  • Clarify if these operations can be performed via SDKs in other languages (Python, Java) and provide sample code.
  • Consider reordering examples so that cross-platform methods (XML/JSON, CLI, REST) are shown before Windows-specific tools like PowerShell.
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-03-01 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently presents Windows-specific guidance and links before Linux equivalents, and in several sections, Linux standalone clusters are not mentioned at all. While Azure-hosted clusters are implied to be cross-platform, standalone cluster security instructions are exclusively for Windows Server, with no Linux standalone guidance or links. Certificate creation recommendations focus on Windows tools and services, and there are no explicit Linux example workflows or references.
Recommendations
  • Add explicit guidance and links for securing standalone Linux Service Fabric clusters, including certificate and authentication setup.
  • Provide Linux-specific examples for certificate creation, installation, and cluster configuration (e.g., using OpenSSL, Linux file paths, and relevant tools).
  • Clarify which security scenarios apply equally to Linux and Windows, and highlight any platform-specific differences.
  • Ensure parity in recommendations and next steps for Linux users, including links to Linux-focused documentation where available.
GitHub Create Pull Request
Service Fabric Upgrade an Azure Service Fabric standalone cluster ...ce-fabric/service-fabric-cluster-upgrade-standalone.md
Medium Priority View Details →
Scanned: 2026-03-01 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page primarily references Windows-specific upgrade instructions and tools, such as linking to Windows Server-specific guides and the Patch Orchestration Application for Windows. There are no explicit Linux examples or references to Linux cluster upgrade procedures, even though Service Fabric standalone clusters can be deployed on both Windows and Linux. This creates friction for Linux users seeking upgrade guidance.
Recommendations
  • Add links and examples for upgrading Service Fabric standalone clusters on Linux, including Linux-specific configuration and upgrade steps.
  • Mention Linux equivalents for patch orchestration and cluster configuration where applicable.
  • Ensure that references to upgrade guides and configuration settings are platform-neutral or provide separate sections for Windows and Linux.
  • Clarify in the introduction that the guidance applies to both Windows and Linux clusters, or specify if certain sections are Windows-only.
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-03-01 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page for the Azure Service Fabric application resource model demonstrates a notable Windows bias. All deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) without providing equivalent Azure CLI or Bash examples. The packaging step references Visual Studio, a Windows-centric tool, and screenshots are from Windows environments. There is no mention of Linux/macOS workflows or tools, nor are cross-platform alternatives presented.
Recommendations
  • Add Azure CLI examples for deployment, upgrade, and deletion tasks alongside PowerShell.
  • Include instructions for packaging applications using cross-platform tools (e.g., dotnet CLI, sfctl, or manual zip commands) instead of only Visual Studio.
  • Provide sample commands and screenshots from Linux/macOS environments where applicable.
  • Clarify that PowerShell is not required and highlight cross-platform options for users on non-Windows systems.
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-03-01 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page on scaling Azure Service Fabric standalone clusters demonstrates Windows bias by referencing PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) and linking to Windows Server-specific guides. No Linux-specific examples, tools, or guidance are provided, despite Service Fabric standalone clusters being theoretically cross-platform. This may create friction for Linux users attempting to scale clusters.
Recommendations
  • Add equivalent Linux instructions, including examples using Bash, CLI, or relevant Linux-native tools.
  • Clarify whether Service Fabric standalone clusters can be managed on Linux, and if so, provide guidance for Linux environments.
  • If PowerShell is required on Linux, explicitly state this and provide installation instructions.
  • Link to or create documentation for scaling standalone clusters on Linux, if supported.
GitHub Create Pull Request
Service Fabric Upgrading Azure Service Fabric clusters ...icles/service-fabric/service-fabric-cluster-upgrade.md
Medium Priority View Details →
Scanned: 2026-03-01 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides general guidance on upgrading Azure Service Fabric clusters, but exhibits mild Windows bias. Windows-specific tools (PowerShell) are mentioned alongside Azure CLI, but Linux equivalents (e.g., Bash, Linux-specific guidance) are not explicitly referenced. The section on OS image upgrades links only to Windows patching guidance, omitting Linux cluster node upgrade information. Windows terminology and tools are mentioned first or exclusively in several places.
Recommendations
  • Add explicit Linux guidance and examples where PowerShell is mentioned, such as Bash or Azure CLI commands for Linux.
  • Include links or sections for patching/upgrading Linux cluster node OS images, not just Windows.
  • When referencing Azure CLI, clarify its cross-platform nature and provide sample commands for both Windows (PowerShell) and Linux (Bash).
  • Ensure that portal and scripting instructions are equally applicable to Linux clusters, or note any differences.
GitHub Create Pull Request
← Previous Page 27 of 99 Next →