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 1701-1725 of 2475 flagged pages
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-09 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 tool referenced for scripting, with no mention of Azure CLI or Bash equivalents. PowerShell examples are given for all major operations (add, remove, scale, configure placement properties), and are presented alongside portal and ARM template methods. There are no Linux/macOS-specific command-line examples or guidance, and PowerShell is presented as the default scripting tool, which may create friction for Linux/macOS users.
Recommendations
  • Add Azure CLI examples for all operations currently demonstrated with PowerShell, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that PowerShell can be used on Linux/macOS, or provide Bash script equivalents where appropriate.
  • Where PowerShell is referenced, clarify if the cmdlets require Windows or if they are available cross-platform.
  • Consider presenting Azure CLI examples before PowerShell, or at least in parallel, to avoid Windows-first bias.
GitHub Create Pull Request
Service Fabric X.509 Certificate-based Authentication in a Service Fabric Cluster ...ticles/service-fabric/cluster-security-certificates.md
Medium Priority View Details →
Scanned: 2026-02-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation is generally platform-neutral in its conceptual explanations, but exhibits a mild Windows bias in several areas: Windows-specific certificate store paths and tools are mentioned first or exclusively, troubleshooting steps reference Windows event logs and CAPI2 logging without Linux equivalents, and some configuration examples refer to Windows-centric APIs or behaviors. Linux paths are mentioned in passing, but Linux/macOS troubleshooting and operational guidance is largely absent.
Recommendations
  • Provide Linux/macOS equivalents for certificate storage locations, e.g., expand on the mention of /var/lib/sfcerts and describe how to manage certificates there.
  • Include troubleshooting steps for Linux clusters, such as relevant log file locations, commands (e.g., journalctl, systemd logs), and how to diagnose certificate issues on Linux nodes.
  • When referencing Windows tools (e.g., CAPI2 logging, Windows Event Viewer), add parallel instructions for Linux (e.g., OpenSSL commands, syslog, or Service Fabric logs on Linux).
  • Ensure that configuration examples and explanations explicitly state when behavior differs between Windows and Linux, and provide both sets of instructions where applicable.
  • Consider reordering explanations so that Linux and Windows are presented with equal prominence, or group platform-specific instructions under clear headings.
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-09 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 the Infrastructure Service, and references Service Fabric Explorer (a GUI tool primarily used on Windows). No Linux CLI or cross-platform alternatives are mentioned for these tasks, and Windows/PowerShell patterns are presented first and exclusively.
Recommendations
  • Add equivalent Linux/bash CLI examples for cluster operations, such as using Azure CLI or REST API.
  • Clarify whether Service Fabric Explorer is available cross-platform or provide alternatives for Linux/macOS users.
  • Mention any prerequisites or limitations for non-Windows environments when performing cluster management tasks.
  • Where possible, provide links to cross-platform tooling or documentation.
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-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page predominantly references PowerShell cmdlets (e.g., Remove-AzResource, AzSF PowerShell cmdlets) for managing Service Fabric resources, with no explicit mention of Linux/macOS alternatives or Azure CLI equivalents for key operations. This creates friction for users on non-Windows platforms, as PowerShell is traditionally Windows-centric and may not be installed or preferred on Linux/macOS systems.
Recommendations
  • Include Azure CLI examples for all operations (e.g., az resource delete, az servicefabric managed-cluster application create) alongside PowerShell cmdlets.
  • Clarify that PowerShell Core is cross-platform, but provide explicit instructions for Linux/macOS users on installation and usage.
  • Add notes or examples for ARM template deployment using Azure CLI or portal for Linux/macOS users.
  • Where possible, link to documentation for equivalent operations using Azure CLI or REST API.
GitHub Create Pull Request
Service Fabric RunToCompletion semantics and specifications ...blob/main/articles/service-fabric/run-to-completion.md
Medium Priority View Details →
Scanned: 2026-02-09 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation page presents RunToCompletion semantics for Service Fabric containers and guest executables, but all code examples and walkthroughs are Windows-centric. The container examples use Windows Server container images and Windows-specific commands (cmd, echo, ping, set, exit). Querying deployment status is described only via PowerShell and C# APIs, with no mention of Linux or cross-platform CLI tools. There is no guidance or example for Linux containers or Linux-based workflows, despite Service Fabric supporting Linux containers.
Recommendations
  • Add equivalent examples using Linux container images (e.g., Ubuntu or Alpine) and Linux shell commands.
  • Include instructions for querying deployment status using Azure CLI or Service Fabric CLI (sfctl), which are cross-platform.
  • Clarify whether RunToCompletion semantics are supported for Linux containers and, if so, provide Linux-specific guidance.
  • Present Windows and Linux examples side-by-side, or at least mention Linux alternatives where applicable.
GitHub Create Pull Request
Service Fabric Describing Azure Service Fabric apps and services ...ic/service-fabric-application-and-service-manifests.md
Medium Priority View Details →
Scanned: 2026-02-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation contains a notable Windows bias in its guidance for validating manifest XML schemas. It exclusively references opening the schema file in Visual Studio using a Windows file path, with no mention of Linux or cross-platform alternatives. Additionally, the PowerShell module is mentioned as a way to create service instances, but no Linux equivalent (such as Azure CLI or cross-platform tools) is referenced.
Recommendations
  • Provide guidance for validating XML schema on Linux/macOS, such as using cross-platform editors (e.g., VS Code) or command-line tools (e.g., xmllint, xmlstarlet).
  • When referencing file paths, include Linux/macOS equivalents or clarify if the schema file is available on those platforms.
  • Mention cross-platform alternatives to the ServiceFabric PowerShell module, such as Azure CLI, where applicable.
  • Ensure that examples and tooling recommendations are not Windows-exclusive unless the feature is truly Windows-only.
GitHub Create Pull Request
Service Fabric Advanced Application Upgrade Topics ...-fabric/service-fabric-application-upgrade-advanced.md
Medium Priority View Details →
Scanned: 2026-02-09 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 heavily features PowerShell cmdlets for upgrade operations, with all command-line examples given in PowerShell syntax and explicit references to PowerShell module documentation. There are no examples or guidance for Linux/macOS users, such as using the Service Fabric CLI (sfctl) or REST APIs, nor is there mention of cross-platform tooling. The structure and examples assume Windows/PowerShell as the default environment, creating friction for non-Windows users.
Recommendations
  • Add equivalent examples using sfctl (Service Fabric CLI), which is cross-platform and supported on Linux/macOS.
  • Include REST API usage examples for upgrade operations, as these are platform-agnostic.
  • Mention and link to Linux/macOS-specific documentation or guides for Service Fabric application upgrades.
  • Clarify which features or commands are Windows-only, and provide alternatives for Linux/macOS where possible.
  • Reorder sections or examples so that cross-platform tools are presented alongside PowerShell, not only after or instead of.
GitHub Create Pull Request
Service Fabric Application upgrade: upgrade parameters ...abric/service-fabric-application-upgrade-parameters.md
Medium Priority View Details →
Scanned: 2026-02-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page presents upgrade parameters for Service Fabric applications, but it shows a notable Windows bias. Windows tools (PowerShell, Visual Studio) are discussed first and in greater detail, including parameter tables and usage patterns. SFCTL (the cross-platform CLI) is covered later and less extensively. There are no explicit Linux/macOS command examples or walkthroughs in the main content; Linux users must refer to external links for guidance. The PowerShell-centric parameter descriptions and lack of Linux-first or parity examples create friction for non-Windows users.
Recommendations
  • Reorder sections so that SFCTL (the cross-platform CLI) is presented before or alongside PowerShell/Visual Studio.
  • Provide explicit command-line examples for SFCTL usage on Linux/macOS within the main documentation, not just in linked pages.
  • Clarify which parameters are available or behave differently in SFCTL versus PowerShell/Visual Studio.
  • Add a comparison table showing parameter mapping between PowerShell, Visual Studio, and SFCTL.
  • Ensure that Linux/macOS users are not required to consult external pages for basic upgrade operations.
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-09 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 a notable Windows bias. The only code example provided uses PowerShell cmdlets, which are native to Windows environments. References to Windows-specific tools (e.g., http.sys) and error messages from the Windows HTTP Server API are present. There are no equivalent examples or instructions for Linux/macOS users, nor are cross-platform CLI alternatives (such as Azure CLI or Service Fabric CLI) mentioned. The 'Next steps' section also prioritizes Visual Studio and PowerShell tutorials, both Windows-centric tools.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl) or Azure CLI for Linux/macOS users.
  • Clarify which upgrade steps and APIs are cross-platform and which are Windows-only.
  • Provide guidance or links for performing upgrades from Linux/macOS environments.
  • Mention any platform-specific limitations or differences explicitly.
  • Reorder or balance 'Next steps' to include Linux/macOS-friendly tooling before or alongside Windows tools.
GitHub Create Pull Request
Service Fabric Monitor Azure Service Fabric ...main/articles/service-fabric/monitor-service-fabric.md
Medium Priority View Details →
Scanned: 2026-02-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation covers monitoring Azure Service Fabric clusters on both Windows and Linux, but there are several areas where Windows tools and patterns are mentioned first or exclusively. Windows-specific tools (e.g., Event Log, Event Viewer, Diagnostics Agent) are referenced before Linux equivalents, and some examples/tutorials focus on .NET/Windows scenarios. Linux-specific guidance is present but less prominent, and some sections lack Linux-specific examples or configuration details.
Recommendations
  • Ensure Linux monitoring tools and patterns are mentioned alongside Windows equivalents, not after.
  • Provide Linux-specific examples and tutorials (e.g., instrumenting applications, configuring monitoring agents, reading logs via Syslog/LTTng).
  • Clarify which features are Windows-only and which are cross-platform, and provide parity guidance where possible.
  • Add links to Linux-focused tutorials and documentation in the 'Recommended setup' and 'Related content' sections.
  • Balance references to Windows tools (Event Viewer, Diagnostics Agent) with Linux equivalents (Syslog, LTTng, Linux agent configuration).
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-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation covers Service Fabric application security in a cross-platform context but exhibits mild Windows bias. Windows-specific tools and patterns (e.g., Active Directory domain accounts, group managed service accounts, BitLocker) are mentioned before or more prominently than Linux equivalents. Several examples and links focus on Windows scenarios, and Linux-specific guidance (e.g., disk encryption, user accounts) is either missing or noted as a TODO. Some sections (e.g., container certificate access, HTTPS endpoints) do mention Linux, but overall, Linux parity is incomplete.
Recommendations
  • Add explicit Linux examples for securing user accounts, running services under different principals, and disk encryption.
  • Ensure Linux tools and patterns (e.g., Linux disk encryption methods, Linux user/group management) are mentioned alongside Windows equivalents.
  • Provide links to Linux-specific documentation where available.
  • Clarify which features are cross-platform and which are Windows-only, to help users understand applicability.
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-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page primarily discusses data serialization in the context of Azure Service Fabric, focusing on C# and .NET serialization. In the 'Next steps' section, upgrade tutorials are offered for Visual Studio and PowerShell, both of which are Windows-centric tools. There are no explicit Linux/macOS alternatives or examples provided, nor is there mention of cross-platform tooling for application upgrades.
Recommendations
  • Add guidance or links for upgrading Service Fabric applications using cross-platform tools such as Azure CLI or REST APIs, which are available on Linux/macOS.
  • Include examples or references for performing application upgrades from Linux/macOS environments.
  • Clarify whether PowerShell Core (cross-platform) is supported, and provide relevant instructions if so.
  • Mention any limitations or considerations for Linux/macOS users, especially if certain features are Windows-only.
GitHub Create Pull Request
Service Fabric Understanding periodic backup configuration ...-fabric-backuprestoreservice-configure-periodic-backup.md
Medium Priority View Details →
Scanned: 2026-02-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page primarily describes Azure Service Fabric's periodic backup configuration, which is cross-platform. However, in the section about file share backup storage, only Windows-specific patterns (e.g., Integrated Windows Authentication and UNC paths) are described, with no mention of Linux-compatible file share approaches (such as SMB mounting on Linux or NFS). There are no Linux-specific examples or guidance for configuring file share backups from Linux-based Service Fabric clusters.
Recommendations
  • Add examples and guidance for configuring file share backup storage from Linux-based Service Fabric clusters, such as using SMB mounts with Linux credentials or NFS shares.
  • Clarify whether file share backup storage is supported on Linux clusters, and if so, provide Linux-specific authentication and path examples.
  • If file share backup is Windows-only, explicitly state this limitation to avoid confusion for Linux users.
  • Ensure parity in documentation by mentioning any Linux-compatible backup storage options (e.g., Azure Blob, NFS) and providing relevant configuration examples.
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-09 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 exclusively for certain operations (e.g., cluster upgrades). Windows-specific tools and registry keys are mentioned without Linux equivalents. Windows configuration examples and guidance appear before Linux references, and some upgrade instructions are Windows-only.
Recommendations
  • Add Linux-specific upgrade instructions and examples, such as using shell scripts or relevant Linux tools for cluster upgrades.
  • Provide equivalent Linux configuration guidance for disabling automatic updates, such as using cloud-init or other Linux-native mechanisms.
  • When mentioning PowerShell commands, also include Bash or Azure CLI alternatives where possible, especially for cluster upgrade operations.
  • Ensure Linux examples and references are presented alongside Windows ones, not only in 'Next steps' but throughout the documentation.
  • Clarify when a step is Windows-only, and provide Linux alternatives or explicitly state if Linux users should skip that step.
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-09 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-based workflows, with all command-line examples using PowerShell cmdlets or PowerShell-based REST calls. There are no examples for Linux/macOS users (e.g., using Bash, curl, or Azure CLI), and the required tooling (Microsoft.ServiceFabric.Powershell.Http) is Windows/PowerShell-specific. This creates friction for non-Windows users, even though the REST API is platform-agnostic.
Recommendations
  • Add equivalent Bash/curl examples for REST API calls to demonstrate on-demand backup from Linux/macOS.
  • Clarify whether the PowerShell module is required or if REST API calls can be made directly from any platform.
  • If possible, provide Azure CLI or cross-platform .NET Core examples for common tasks.
  • Explicitly mention platform support and any limitations for Linux/macOS users.
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-09 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 toward Windows/PowerShell usage. All code examples use PowerShell, including REST API calls, and require the Microsoft.ServiceFabric.Powershell.Http module. There are no examples or guidance for Linux/macOS users (e.g., using Bash, curl, or cross-platform tools). The documentation assumes the reader is using Windows and PowerShell, creating friction for non-Windows 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.
  • Mention any cross-platform CLI tools (e.g., Azure CLI) that can be used for these operations.
  • Clarify if the Microsoft.ServiceFabric.Powershell.Http module functionality is available via REST API or other cross-platform means.
  • Provide guidance for Linux/macOS users on prerequisites and setup.
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-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides networking best practices for Azure Service Fabric clusters and covers both Windows and Linux scenarios. However, there is a noticeable Windows bias: PowerShell is referenced as the primary API client, Windows-specific tools and terminology (e.g., RDP, netsh) are used without Linux equivalents, and Windows examples or references often appear before Linux ones. Some sections (e.g., Azure DevOps, API Management) focus on PowerShell and Windows-centric workflows, while Linux alternatives are not always mentioned or are referenced second.
Recommendations
  • Include Linux CLI (az CLI, bash) examples alongside PowerShell where relevant, especially for cluster management and networking tasks.
  • Mention Linux tools and commands (e.g., iptables, ss, netstat) when discussing port ranges, dynamic ports, and firewall configuration.
  • Provide Linux-specific guidance for DevOps and API Management scenarios, including references to cross-platform tools.
  • Ensure parity in documentation structure by presenting Windows and Linux options equally, rather than Windows-first.
  • Clarify when a feature or recommendation is Windows-only, and offer Linux alternatives or workarounds where possible.
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-09 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: certificate store names default to Windows values (e.g., 'My', 'LocalMachine'), references to Windows-specific tools and concepts (e.g., NTLM authentication, Windows Defender Firewall, Windows Fabric Replicator), and some parameters are described with Windows terminology or defaults. Windows-specific settings (e.g., log directories, firewall configuration) are mentioned without always providing Linux equivalents or clarifying cross-platform differences. Linux is referenced in some settings, but Windows concepts/tools are often presented first or exclusively.
Recommendations
  • Where parameters reference Windows concepts (e.g., certificate store names, NTLM authentication, log directories), add explicit notes or examples for Linux equivalents (e.g., Linux certificate paths, Linux authentication mechanisms, Linux log directories).
  • Clarify which settings are platform-specific and which are cross-platform, ideally with a table or section indicating applicability.
  • For settings like firewall configuration, mention Linux firewall equivalents (e.g., iptables, firewalld) or note if the setting is Windows-only.
  • When referencing Windows tools or patterns (e.g., Windows Defender Firewall, NTLM), provide Linux alternatives or clarify if the feature is not available on Linux.
  • Review default values and descriptions to ensure Linux defaults are mentioned where applicable, not just Windows defaults.
  • Consider providing Linux-first or Linux-parity examples where possible, especially for certificate management and authentication.
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-09 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 PowerShell and C# examples exclusively for managing Application Groups in Service Fabric. PowerShell is a Windows-centric tool, and no equivalent Linux/macOS command-line examples (such as Azure CLI, Bash, or REST API) are provided. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer cross-platform tools.
Recommendations
  • Add Azure CLI examples for all operations shown (application creation, updating, querying load, removing capacity).
  • Include REST API sample requests for relevant actions, as these are platform-agnostic.
  • Mention that PowerShell examples are Windows-specific and provide guidance for Linux/macOS users.
  • If PowerShell Core is supported cross-platform, clarify its usage and limitations.
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-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page provides general information about Azure Service Fabric node types and virtual machine scale sets. However, there are signs of Windows bias: the 'dataPath' example uses a Windows-style path (D:\SvcFab), and the 'Next steps' section links to PowerShell scripts for changing RDP port ranges and admin credentials, which are Windows-centric tasks. There are no explicit Linux/macOS examples or equivalent guidance for Linux users, despite the mention of 'ServiceFabricLinuxNode' in the extension configuration.
Recommendations
  • Provide Linux/macOS equivalents for remote connection and admin credential changes, such as SSH-based instructions or Bash scripts.
  • Include examples of Linux-style paths (e.g., /var/svcfab) alongside Windows paths in configuration snippets.
  • Clarify which tasks are Windows-only and which are cross-platform, and provide parity guidance where possible.
  • Add links or references to Linux-specific documentation for managing Service Fabric clusters.
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-02-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides code examples for configuring auto scaling in Service Fabric using C#, XML (application manifest), and PowerShell. The PowerShell examples are Windows-specific, and there are no equivalent CLI or scripting examples for Linux/macOS users. The documentation does mention that resource monitoring is supported for containerized applications on Linux, but all operational/scripted examples are Windows-centric.
Recommendations
  • Add Azure CLI or Bash scripting examples for configuring scaling policies, especially for Linux/macOS users.
  • Clarify which steps or tools are cross-platform and which are Windows-only.
  • Provide guidance or links for Linux users on how to perform equivalent operations (e.g., using REST APIs, Service Fabric CLI (sfctl), or ARM templates).
  • Explicitly state if certain management operations (such as PowerShell cmdlets) are only available on Windows, and suggest alternatives where possible.
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-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation shows a moderate Windows bias. While Service Fabric supports both Windows and Linux clusters, the configuration and code examples (e.g., ClusterManifest.xml, PowerShell cmdlets, .NET/C# code) are Windows-centric or shown first. Linux-specific configuration (e.g., Linux-based manifest examples, Bash/CLI commands) is not provided. The XML manifest examples use <WindowsServer> as the only infrastructure type, and PowerShell is the only shell scripting example given. There is no explicit mention of Linux clusters or their configuration differences.
Recommendations
  • Add Linux-specific configuration examples (e.g., using <Linux> infrastructure in ClusterManifest.xml or Linux node configuration in ClusterConfig.json).
  • Include Azure CLI or Bash examples for service creation and updates, alongside or instead of PowerShell.
  • Clarify in the text where configuration or behavior differs between Windows and Linux clusters.
  • Provide .NET Core or cross-platform SDK code examples, or note if only .NET Framework is supported.
  • Explicitly state if any features or configuration are Windows-only, to avoid confusion.
GitHub Create Pull Request
Service Fabric Cluster Resource Manager - Management Integration ...fabric-cluster-resource-manager-management-integration.md
Medium Priority View Details →
Scanned: 2026-02-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides a PowerShell example for querying Service Fabric partition health, but does not include equivalent Linux/macOS CLI examples or mention cross-platform tools. This creates friction for non-Windows users, as Service Fabric can be managed from Linux/macOS using the Service Fabric CLI (sfctl), but this is not referenced.
Recommendations
  • Add equivalent Linux/macOS examples using the Service Fabric CLI (sfctl) for health queries.
  • Mention that Service Fabric management can be performed from Linux/macOS and provide links to relevant documentation.
  • Where possible, show both PowerShell and CLI examples side-by-side to improve parity.
  • Clarify any platform-specific limitations if certain commands are Windows-only.
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-09 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, with PowerShell commands shown for service creation and metric configuration. There are no Linux CLI (e.g., Bash, Azure CLI) or cross-platform examples, and PowerShell is presented as the main scripting interface for operational tasks. This creates friction for Linux/macOS users, as Service Fabric supports Linux clusters and the Azure CLI is available cross-platform.
Recommendations
  • Add Azure CLI examples for service creation and metric configuration, where possible.
  • Explicitly mention cross-platform alternatives to PowerShell for Linux/macOS users.
  • Clarify which commands and APIs are available on Linux clusters and which are Windows-only.
  • Consider including Bash scripts or references to REST API usage for metric management.
  • Reorder examples so that cross-platform options (Azure CLI, REST API) are shown before or alongside PowerShell.
GitHub Create Pull Request
Service Fabric Azure Service Fabric dynamic node tags ...tps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-node-tagging.md
Medium Priority View Details →
Scanned: 2026-02-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides PowerShell command examples for managing node tags and service requirements, but does not include equivalent CLI examples for Linux/macOS users (e.g., Bash, Azure CLI, or REST API usage). PowerShell is a Windows-centric tool, and its exclusive use creates friction for non-Windows users. The documentation also references 'standard Service Fabric interface mechanisms' but only demonstrates PowerShell and C# APIs, omitting practical Linux-friendly alternatives.
Recommendations
  • Add examples using Azure CLI or Bash scripts for managing node tags and service requirements.
  • Include REST API usage examples, which are platform-agnostic and accessible from Linux/macOS.
  • Explicitly mention cross-platform tools and clarify which commands are available on Linux clusters.
  • If PowerShell Core is supported on Linux, note this and provide installation guidance.
GitHub Create Pull Request
← Previous Page 69 of 99 Next →