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 701-725 of 2475 flagged pages
Service Fabric Service Fabric Explorer blocking operations ...ged-cluster-service-fabric-explorer-blocking-operation.md
Medium Priority View Details →
Scanned: 2026-02-28 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 and ARM-managed clusters. It consistently recommends Az PowerShell cmdlets (e.g., Remove-AzResource, AzSF PowerShell cmdlets) for resource operations, mentioning them before or instead of Azure CLI equivalents. While az resource (Azure CLI) is referenced once for application deletion, most examples and links are PowerShell-centric, which may create friction for Linux/macOS users who typically use Azure CLI.
Recommendations
  • Include Azure CLI equivalents for all PowerShell cmdlets mentioned (e.g., az resource delete, az servicefabric managed-cluster application create).
  • Present both PowerShell and CLI options side-by-side, or clarify which tools are cross-platform.
  • Link to Azure CLI documentation where relevant, not just PowerShell modules.
  • Explicitly note that Azure CLI is fully supported on Linux/macOS for these operations.
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-28 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation covers both Windows and Linux clusters for Azure Service Fabric monitoring, 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 examples/tutorials focus on .NET applications (typically Windows-centric). Linux-specific guidance is present but less prominent, and some features (EventStore APIs) are Windows-only without clear Linux alternatives or workarounds. The overall structure and example flow tends to prioritize Windows scenarios, creating friction for Linux users.
Recommendations
  • Ensure Linux-specific tools and patterns (such as LTTng, Syslog, Linux agent setup) are given equal prominence and described before or alongside Windows equivalents.
  • Provide Linux-focused examples and tutorials, especially for application monitoring and cluster diagnostics, not just referencing Windows/.NET scenarios.
  • Clarify which features are Windows-only and offer Linux alternatives or workarounds where possible.
  • Add explicit Linux sample code, configuration snippets, and screenshots where Windows examples are shown.
  • Review the order of tool and agent recommendations to avoid Windows-first bias.
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-28 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides a general overview of Service Fabric application security, but several sections show Windows bias. Windows-specific tools and patterns (e.g., Active Directory, gMSA, BitLocker, NetworkService account) are mentioned, often before or instead of Linux equivalents. Linux-specific guidance is minimal or absent in areas such as disk encryption, user accounts, and container security. Some features are described as Windows-only without clear Linux alternatives or parity.
Recommendations
  • Add explicit Linux examples and guidance alongside Windows instructions, especially for disk encryption, user accounts, and container certificate access.
  • Mention Linux tools and patterns (e.g., Linux user/group management, LUKS for disk encryption) where Windows tools are referenced.
  • Clarify which features are cross-platform and which are Windows-only, and provide Linux alternatives or workarounds where possible.
  • Ensure parity in example ordering (e.g., do not always mention Windows first; alternate or combine examples).
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-28 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides upgrade tutorials for Visual Studio and PowerShell, both of which are primarily Windows-centric tools. No Linux/macOS equivalents (such as CLI or cross-platform tools) are mentioned or linked, and Windows-oriented upgrade paths are listed first. The core serialization guidance is platform-neutral, but upgrade workflow examples are Windows-focused.
Recommendations
  • Add links or sections for upgrading applications using Azure CLI or Service Fabric CLI (sfctl), which are cross-platform.
  • Mention and provide examples for Linux/macOS users, such as using sfctl or REST APIs for application upgrades.
  • Clarify which tools are Windows-only and suggest alternatives for other platforms.
  • Consider listing cross-platform options before or alongside Windows-specific tools in the 'Next steps' section.
GitHub Create Pull Request
Service Fabric Application upgrade: upgrade parameters ...abric/service-fabric-application-upgrade-parameters.md
Medium Priority View Details →
Scanned: 2026-02-28 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 workflows first, with detailed tables and explanations. SFCTL (Service Fabric CLI), which is cross-platform and used on Linux/macOS, is covered after the Windows tools and receives less prominence. Examples and parameter descriptions are more extensive for PowerShell/Visual Studio, while SFCTL is described more briefly. There are no Linux-specific examples or patterns, and Windows tools are mentioned before their Linux equivalents.
Recommendations
  • Reorganize the page so that cross-platform tools (SFCTL) are presented before or alongside Windows/PowerShell and Visual Studio sections.
  • Provide Linux/macOS-specific examples and workflows, especially for SFCTL usage.
  • Ensure parameter tables for SFCTL are as detailed as those for PowerShell/Visual Studio.
  • Add explicit notes about cross-platform compatibility and highlight SFCTL as the recommended tool for Linux/macOS users.
  • Consider including a comparison table showing which tools are available on which platforms.
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-28 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 Linux or cross-platform alternatives (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 mechanisms. These examples and tools are presented as default or primary, creating friction for Linux/macOS users.
Recommendations
  • Add references to cross-platform management tools such as Azure CLI or REST APIs alongside PowerShell cmdlets.
  • Clarify whether Linux-based clusters can use the same management subsystem and tools, and provide examples for Linux environments.
  • Mention Linux authentication mechanisms (such as certificate-based authentication) explicitly, and clarify Windows-specific aspects where relevant.
  • Ensure that examples and tool references are presented in a platform-neutral or parallel manner (e.g., 'PowerShell cmdlets or Azure CLI/REST APIs').
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-28 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 exclusively provides PowerShell-based examples and instructions, including module installation and REST API usage via PowerShell. There are no Linux/macOS shell (e.g., Bash, curl) equivalents, nor is there guidance for cross-platform tools. The reliance on PowerShell and Windows-centric modules creates friction for Linux/macOS users, who may not have access to PowerShell or may prefer native tools.
Recommendations
  • Add Bash/curl examples for REST API calls, showing how to trigger backups and track progress using standard Linux/macOS tools.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is available cross-platform (PowerShell Core), and provide installation instructions for Linux/macOS if so.
  • Mention alternative approaches for Linux users, such as using Azure CLI or direct REST API calls.
  • Where possible, provide parity in example order (show Bash/curl 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-28 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 Service Fabric application upgrade topics heavily relies on PowerShell cmdlets for examples and workflows, with no mention of Linux/macOS equivalents or cross-platform CLI tools. All command-line instructions are given in PowerShell, and there is no guidance for users running Service Fabric clusters on Linux or using Azure CLI. This creates friction for non-Windows users, as they must translate PowerShell examples or seek alternative tooling.
Recommendations
  • Add Azure CLI or REST API examples alongside PowerShell for all upgrade operations.
  • Clearly indicate which commands are Windows-only and provide Linux/macOS alternatives where available.
  • Include guidance or links for managing Service Fabric upgrades on Linux clusters, including references to sfctl (Service Fabric CLI).
  • Structure examples so that cross-platform options are shown first or equally, rather than PowerShell exclusively.
  • Mention any limitations or differences for Linux clusters in relevant sections.
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-28 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 upgrade demonstrates notable Windows bias. PowerShell is the only CLI example provided, and references to Service Fabric PowerShell cmdlets are prominent throughout. There are no Linux or cross-platform CLI examples (such as Azure CLI or REST API usage), and Windows-specific tools and APIs (e.g., http.sys, Windows HTTP Server API) are mentioned without Linux equivalents. The 'Next steps' section also prioritizes Windows tools (Visual Studio, PowerShell) and lacks Linux/macOS guidance.
Recommendations
  • Add equivalent examples for Linux/macOS users, such as using Azure CLI, Service Fabric CLI (sfctl), or REST APIs for application upgrades.
  • Include guidance for performing upgrades on Linux-based Service Fabric clusters, noting any differences in process or tooling.
  • When referencing Windows-specific APIs (e.g., http.sys), clarify if the limitation applies only to Windows clusters and provide Linux-specific notes if applicable.
  • Balance 'Next steps' by linking to tutorials or documentation for Linux/macOS users, including cross-platform tools.
  • Where possible, present cross-platform examples first or side-by-side, rather than Windows/PowerShell examples exclusively.
GitHub Create Pull Request
Service Fabric Understanding periodic backup configuration ...-fabric-backuprestoreservice-configure-periodic-backup.md
Medium Priority View Details →
Scanned: 2026-02-28 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page primarily describes backup configuration for Azure Service Fabric, which is a cross-platform technology. However, in the section describing file share backup storage, only Windows-style UNC paths (\\StorageServer\BackupStore) and Windows authentication methods are mentioned. There are no examples or guidance for Linux-based file shares (such as SMB/CIFS mounts or NFS), nor is there mention of Linux authentication patterns. This omission may create friction for Linux users wishing to use on-premises file shares for backups.
Recommendations
  • Add examples and guidance for configuring file share backup storage using Linux-based file shares (e.g., SMB/CIFS or NFS mounts).
  • Include authentication patterns relevant to Linux (such as mount options, credential files, or Kerberos).
  • Clarify whether Linux clusters can use file share backup storage and, if so, provide parity in documentation.
  • If file share backup is Windows-only, explicitly state this limitation to avoid confusion.
GitHub Create Pull Request
Service Fabric Capacity planning and scaling for Azure Service Fabric ...bric/service-fabric-best-practices-capacity-scaling.md
Medium Priority View Details →
Scanned: 2026-02-28 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides several manual scaling steps using PowerShell cmdlets (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState) without offering equivalent Linux CLI or cross-platform alternatives. Additionally, PowerShell examples are presented first and exclusively in critical operational sections, creating friction for Linux users. However, the page does mention Linux clusters in the 'Next steps' section and does not focus on Windows-only features.
Recommendations
  • Add equivalent Linux CLI commands (e.g., Service Fabric CLI or REST API) for scaling operations alongside PowerShell examples.
  • Clearly indicate which commands are platform-specific and provide guidance for Linux/macOS users.
  • Where possible, use cross-platform tools (such as Azure CLI or Service Fabric CLI) in examples.
  • Ensure that manual and programmatic scaling instructions are accessible for both Windows and Linux clusters.
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-28 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 only, with PowerShell being the exclusive CLI example for configuring placement policies. There are no examples or instructions for Linux/macOS users, such as using Azure CLI, REST API, or cross-platform tools. The PowerShell examples are shown alongside C# code, but no Linux-native equivalents are given.
Recommendations
  • Add Azure CLI examples for configuring placement policies, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include REST API example calls for placement policy configuration, which are platform-agnostic.
  • Mention and link to any available Linux/macOS-compatible Service Fabric management tools.
  • Clarify if PowerShell examples are only applicable on Windows, and provide alternatives for Linux/macOS users.
  • Consider providing bash scripts or instructions for Linux environments where applicable.
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-28 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page provides only PowerShell-based examples and instructions for restoring backups in Azure Service Fabric. All CLI and REST API usage is demonstrated via PowerShell scripts, and the prerequisite is to install a Microsoft.ServiceFabric.Powershell.Http module. There are no Bash, Linux, or cross-platform CLI examples, nor is there mention of Linux-compatible tools or workflows. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer native tools.
Recommendations
  • Add Bash or cross-platform CLI examples for REST API calls (e.g., using curl or az CLI).
  • Mention that PowerShell Core is available on Linux/macOS and clarify if the Microsoft.ServiceFabric.Powershell.Http module is compatible with PowerShell Core on non-Windows platforms.
  • Provide guidance for Linux/macOS users on how to authenticate and make REST API calls without PowerShell.
  • Include references to Service Fabric CLI (sfctl) if applicable, or note its limitations.
  • Explicitly state platform requirements and alternatives for non-Windows users.
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-28 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 Service Fabric clusters, but PowerShell (a Windows-centric tool) is given a dedicated section and is used for advanced cluster upgrade operations without Linux/bash equivalents. Windows-specific configuration details (e.g., registry keys, Windows Update settings) are described without mentioning Linux alternatives or clarifying their applicability. In several places, Windows tools and patterns are mentioned first or exclusively.
Recommendations
  • For every PowerShell example, provide an equivalent Bash/Azure CLI or Linux-native example where possible, especially for cluster upgrade operations.
  • When discussing OS-specific configuration (e.g., registry keys, Windows Update), clarify that these steps are Windows-only and, if relevant, provide Linux equivalents or state if not applicable.
  • Balance the order of presentation: alternate or parallelize Windows and Linux instructions/examples to avoid implicit prioritization.
  • Explicitly indicate when a step or configuration is Windows-only, and link to Linux-specific documentation or guidance where available.
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-28 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides a generally balanced overview of Service Fabric networking best practices, but there are several instances of Windows bias. PowerShell and Windows-specific tools are mentioned more frequently and sometimes before their Linux equivalents. Windows examples and terminology (such as PowerShell APIs, netsh commands, and Windows container guidance) are often presented first or exclusively, while Linux-specific instructions or CLI alternatives are less prominent or referenced later. Some example links and templates are Windows-focused, and there is occasional lack of parity in example depth for Linux users.
Recommendations
  • Where PowerShell is referenced, provide equivalent Azure CLI or bash examples for Linux users.
  • When mentioning Windows tools (e.g., netsh), include Linux alternatives (e.g., 'ss', 'lsof', or 'cat /proc/net/tcp').
  • Ensure that ARM template examples and sample links include both Windows and Linux cluster templates.
  • When discussing application networking, clarify Linux container support and provide Linux-specific guidance where relevant.
  • In tables and lists, avoid presenting Windows-specific information before Linux unless the feature is Windows-only.
  • Expand Linux-specific instructions (e.g., for enabling Accelerated Networking, port ranges, and cluster creation) to match the detail provided for Windows.
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-28 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 page presents some evidence of Windows bias. While it describes both Windows and Linux node types in Service Fabric clusters, it uses Windows-style paths (e.g., 'D:\\SvcFab') in JSON snippets, and the 'Next steps' section links exclusively to Windows/PowerShell-specific tasks (RDP port range, admin username/password changes) without Linux/SSH equivalents. There are no Linux-specific examples or guidance for connecting to Linux nodes or managing them, and Windows tools/patterns (RDP, PowerShell) are mentioned without parity for Linux/macOS users.
Recommendations
  • Add Linux/SSH-specific guidance and examples for connecting to Linux node types (e.g., SSH port management, changing SSH user/password).
  • Provide Linux-style paths (e.g., '/var/svcfab') in JSON snippets or clarify that the 'dataPath' should be OS-appropriate.
  • Include links to Linux management scripts or documentation alongside Windows/PowerShell scripts.
  • Ensure that guidance for node management covers both Windows and Linux scenarios equally.
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-28 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 examples for key security tasks, such as certificate generation and secret encryption. However, Windows-specific tools (PowerShell, Windows Defender, Azure DSC) are often mentioned first or exclusively, and Windows-centric patterns (e.g., certificate store behavior, Defender exclusions) are described in detail, while Linux equivalents are less prominent or omitted. Some sections (Windows Defender, DSC) are Windows-only by nature, but others could improve Linux parity.
Recommendations
  • Ensure Linux examples are presented alongside Windows examples, not after them, especially for certificate and secret management.
  • Where Windows tools (PowerShell, DSC, Defender) are discussed, provide equivalent Linux guidance or clarify if no direct equivalent exists.
  • Add more explicit references to Linux security baselines and tools (e.g., SELinux, AppArmor, Linux antivirus solutions) where relevant.
  • Clarify which sections are Windows-only and which apply to both platforms, to reduce ambiguity.
  • Consider reordering sections so Linux and Windows examples are equally prominent.
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-28 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-specific terminology (e.g., 'Windows Fabric', 'Windows only' flags, 'Windows Defender Firewall', 'NTLM authentication', 'MY' certificate store, 'LocalMachine' store location) is used throughout, and Windows-related settings are often mentioned first or exclusively. Linux equivalents are sometimes referenced (e.g., LinuxExternalExecutablePath, container network setup defaults), but Windows tools and patterns dominate, and Linux-specific guidance is sparse.
Recommendations
  • Where Windows-specific settings are mentioned, add Linux equivalents or clarify if the setting is cross-platform.
  • For parameters like certificate store names ('MY', 'LocalMachine'), provide Linux equivalents or note differences.
  • Expand guidance for Linux users, especially around security, networking, and file store configuration.
  • Ensure that examples and descriptions reference both Windows and Linux patterns equally.
  • Clarify which features are Windows-only and which are supported on Linux, ideally in a summary table.
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-28 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides example code for configuring auto scaling in Azure Service Fabric using application manifests, C# APIs, and PowerShell. However, all CLI/script examples are PowerShell-based, with no equivalent Bash or Linux CLI examples. PowerShell is a Windows-centric tool, and its exclusive use creates friction for Linux/macOS users. There is no mention of Linux-native tools or cross-platform CLI approaches (e.g., Azure CLI, Bash scripts). Additionally, PowerShell examples are presented alongside C# and manifest examples, but Linux alternatives are absent.
Recommendations
  • Add equivalent Bash or Azure CLI examples for configuring auto scaling policies, especially for Linux-based Service Fabric clusters.
  • Explicitly mention any cross-platform tools or APIs available for Linux/macOS users.
  • Clarify which steps or commands are Windows-only and provide Linux alternatives where possible.
  • Consider referencing or linking to Linux-specific Service Fabric management documentation.
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-28 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exclusively provides PowerShell command examples for managing Service Fabric Application Groups, alongside C# API usage. There are no examples or instructions for Linux/macOS users, such as Bash/CLI equivalents or references to cross-platform tools. PowerShell is a Windows-centric tool, and its use here assumes a Windows environment, creating friction for Linux/macOS users.
Recommendations
  • Add Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and supported on Linux/macOS.
  • Explicitly mention whether PowerShell Core (cross-platform) can be used, or clarify if only Windows PowerShell is supported.
  • Provide Bash shell script examples or reference REST API endpoints for users on Linux/macOS.
  • Include a note about platform support for Service Fabric management tools, and link to relevant installation guides for Linux/macOS users.
  • Consider reordering examples so that cross-platform tools (Azure CLI, REST API) are shown before or alongside PowerShell.
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-28 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides a PowerShell example for querying Service Fabric partition health, using Windows-specific syntax and paths. No equivalent Linux/macOS CLI or REST API example is given. The example is presented early in the page, and references to Windows tools (PowerShell) are made before any mention of cross-platform alternatives. However, the rest of the documentation is largely conceptual and platform-neutral.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • Include REST API examples for health queries, which are platform-independent.
  • When showing command-line examples, present both Windows (PowerShell) and Linux/macOS (bash/CLI) versions side-by-side.
  • Clarify that PowerShell is just one option, and link to documentation for cross-platform tools.
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-02-28 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 configuring service sensitivity and maximum load, but does not offer equivalent Linux/macOS CLI examples (such as Bash or cross-platform Azure CLI). PowerShell is presented as the primary scripting interface, and there is no mention of Linux-native tools or commands. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other interfaces.
Recommendations
  • Add cross-platform Azure CLI examples for all PowerShell commands shown.
  • Clarify whether PowerShell Core (pwsh) is supported on Linux/macOS for Service Fabric management, and provide usage instructions if so.
  • Mention any REST API or SDK alternatives for configuring sensitivity and maximum load, with example requests.
  • Explicitly state platform requirements for each example (e.g., 'Windows-only', 'cross-platform').
  • Consider including Bash or shell script examples if supported.
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-28 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Windows and cross-platform (JSON) configuration examples for Service Fabric clusters, but Windows-specific XML (ClusterManifest.xml) and PowerShell examples are presented first and more frequently. PowerShell is the only CLI example shown, with no Linux shell or CLI parity. The XML configuration is labeled as 'WindowsServer', and the PowerShell examples are not accompanied by Linux CLI equivalents. However, JSON examples for standalone deployments are included, and the overall concepts are platform-neutral.
Recommendations
  • Add Linux CLI examples (e.g., Bash with sfctl or Azure CLI) alongside PowerShell for service creation and updates.
  • Clarify when XML/WindowsServer configuration is Windows-only and when JSON applies to Linux clusters.
  • Present JSON configuration examples before or alongside XML/WindowsServer examples to emphasize cross-platform support.
  • Mention Linux/macOS tools (such as sfctl) where PowerShell is referenced.
  • Explicitly state platform applicability for each example.
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-28 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides code examples primarily in C# and PowerShell, with PowerShell being the only CLI example shown. There are no Linux CLI equivalents (such as Bash or Azure CLI), and PowerShell is presented as the default scripting tool for service creation and management. This creates friction for Linux/macOS users, as Service Fabric can be managed from Linux using Azure CLI or REST APIs, but these options are not mentioned or demonstrated.
Recommendations
  • Add Azure CLI examples for service creation and metric management, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Mention REST API options for metric configuration and load reporting, with links to relevant documentation.
  • Clarify which management operations are available from Linux/macOS and provide parity in examples where possible.
  • If PowerShell is required for certain operations, explicitly state this and provide alternative guidance for Linux users.
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-02-28 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 and C# examples for configuring movement cost in Service Fabric clusters, but does not include equivalent Linux/bash/CLI examples. PowerShell is a Windows-centric tool, and its use is presented before any mention of cross-platform alternatives. There is no indication of how Linux/macOS users can perform these tasks, creating friction for non-Windows users.
Recommendations
  • Add Azure CLI or REST API examples for configuring and updating MoveCost, as these are cross-platform and usable on Linux/macOS.
  • Explicitly mention whether PowerShell examples are usable on PowerShell Core (cross-platform) or only Windows PowerShell.
  • Provide bash or shell script equivalents where possible, or clarify if certain operations are only possible via PowerShell.
  • Document any limitations or differences for Linux/macOS users in a dedicated section.
GitHub Create Pull Request
← Previous Page 29 of 99 Next →