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 476-500 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-03-04 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 operations such as deleting or creating applications/services, with only a brief mention of the Azure CLI (az resource) for application deletion. There are no explicit Linux/macOS examples or references to cross-platform tools, and PowerShell cmdlets are presented first and most frequently.
Recommendations
  • Include Azure CLI equivalents for all PowerShell cmdlet examples (e.g., az resource delete, az servicefabric managed-cluster application create).
  • Present both PowerShell and Azure CLI options side-by-side, clarifying which are cross-platform.
  • Explicitly note that Azure CLI is supported on Linux/macOS and provide links to relevant CLI documentation.
  • Where possible, add ARM template examples and clarify their cross-platform nature.
GitHub Create Pull Request
Service Fabric Azure Service Fabric container image management .../articles/service-fabric/container-image-management.md
Medium Priority View Details →
Scanned: 2026-03-04 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation references Windows container base images (microsoft/windowsservercore, microsoft/nanoserver) as default exclusions in cleanup, and these are mentioned before Linux equivalents. The examples and explanations focus on Windows images, with Linux images only referenced in an example regex. No Linux-specific guidance or parity is provided.
Recommendations
  • Include Linux container base images (e.g., 'docker.io/library/ubuntu', 'docker.io/library/alpine') in the explanation of default exclusions and examples.
  • Clarify whether the cleanup and management features apply equally to Linux containers and Windows containers, and provide explicit guidance for Linux scenarios.
  • Add examples showing how to skip Linux base images, and discuss any differences in image management between Windows and Linux nodes.
  • Ensure documentation is clear about cross-platform applicability, especially for clusters running Linux VMs.
GitHub Create Pull Request
Service Fabric Configure or modify a Service Fabric managed cluster node type ...vice-fabric/how-to-managed-cluster-modify-node-type.md
Medium Priority View Details →
Scanned: 2026-03-04 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides examples for managing Service Fabric managed cluster node types using the Azure Portal, ARM templates, and PowerShell. However, all CLI-based examples use PowerShell cmdlets (e.g., New-AzServiceFabricManagedNodeType), with no mention of Azure CLI (az) equivalents or Bash scripting. This creates a bias towards Windows/PowerShell users and omits guidance for Linux/macOS users who may prefer or require Azure CLI or Bash.
Recommendations
  • Add Azure CLI (az) command examples for all tasks currently shown with PowerShell, such as adding, removing, and scaling node types.
  • Explicitly mention that PowerShell examples can be run on macOS/Linux using PowerShell Core, or clarify if they require Windows.
  • Where possible, provide Bash scripting examples or note cross-platform alternatives.
  • Consider listing Azure CLI examples before or alongside PowerShell to promote parity.
GitHub Create Pull Request
Service Fabric Deny assignment policy for Service Fabric managed clusters ...cles/service-fabric/managed-cluster-deny-assignment.md
Medium Priority View Details →
Scanned: 2026-03-04 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides examples and links primarily for Azure PowerShell modules when describing best practices for managing Service Fabric managed clusters. PowerShell is a Windows-centric tool, and its mention precedes Azure CLI and other cross-platform tools. While Azure CLI and ARM/Bicep templates are referenced in a table, actionable examples and guidance are PowerShell-heavy, which may create friction for Linux/macOS users.
Recommendations
  • Add explicit Azure CLI command examples alongside PowerShell examples for key tasks (e.g., deleting NodeTypes, restarting/reimaging scale sets).
  • Mention Azure CLI and cross-platform tools in the narrative text, not just in the table.
  • Clarify that PowerShell modules are available cross-platform (if true), or provide equivalent CLI/Bicep instructions.
  • Ensure all guidance and examples are platform-neutral or provide parity for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Migrate an Azure Service Fabric cluster to availability zone support ...ce-fabric/migrate-service-fabric-availability-zones.md
Medium Priority View Details →
Scanned: 2026-03-04 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides migration guidance for Azure Service Fabric clusters to availability zone support. While much of the guidance is platform-neutral (focused on ARM templates and Azure resources), the only CLI/script examples given are in PowerShell, and the sample templates referenced are primarily for Windows clusters. PowerShell is a Windows-centric tool, and no Bash, Azure CLI, or Linux-native scripting examples are provided. Additionally, the first sample template referenced is for Windows, and only later is an Ubuntu template mentioned, but no Linux-specific migration commands are shown.
Recommendations
  • Add Azure CLI or Bash script examples for resource deployment, node disabling, and removal, alongside PowerShell.
  • Reference and provide Linux/Ubuntu sample templates equally and early in the document.
  • Clarify which steps are platform-agnostic and which require Windows tools, and provide alternatives where possible.
  • Explicitly note any platform-specific requirements and offer guidance for Linux/macOS users.
  • Include links to Linux/macOS Service Fabric tooling documentation.
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-03-04 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation contains a warning that recommends opening the Service Fabric XSD schema file in Visual Studio using a Windows file path, suggesting a Windows-centric workflow and toolset. There is no mention of Linux or cross-platform alternatives for schema validation or authoring manifests. Additionally, the only tool-specific guidance is Windows-first.
Recommendations
  • Provide instructions or suggestions for validating the Service Fabric manifest XML schema on Linux/macOS, such as using cross-platform editors (e.g., VS Code with XML extensions) or command-line tools (e.g., xmllint, xmlstarlet).
  • Mention the location of the schema file on Linux clusters, if applicable, or clarify if the schema is only available on Windows.
  • When referencing tools like Visual Studio, note cross-platform alternatives or explicitly state if a feature is Windows-only.
  • Include example workflows for authoring and validating manifests on Linux/macOS, or link to relevant guidance.
GitHub Create Pull Request
Service Fabric Monitor Azure Service Fabric ...main/articles/service-fabric/monitor-service-fabric.md
Medium Priority View Details →
Scanned: 2026-03-04 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 for Azure Service Fabric clusters on both Windows and Linux, but there is a noticeable Windows bias in several areas. Windows-specific tools (e.g., EventStore APIs, Diagnostics Agent) are mentioned first or exclusively, and some example/tutorial links focus on Windows or .NET applications. Linux equivalents are referenced, but often with less detail or as secondary mentions. Some sections lack explicit Linux examples or guidance, especially for cluster-level monitoring and event access.
Recommendations
  • Provide parallel Linux examples and tutorials for cluster monitoring, application monitoring, and event access, matching the detail given for Windows.
  • Ensure Linux-specific tools and patterns (e.g., LTTng, Syslog, Linux agent configuration) are described with equal prominence and clarity.
  • Add links to Linux-focused tutorials and documentation where Windows tutorials are referenced.
  • Clarify which features are Windows-only and provide alternative approaches for Linux users where possible.
  • Balance the order of presentation so Linux and Windows are treated equally, rather than Windows-first.
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-03-04 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 mostly platform-neutral way, but there are several subtle Windows biases. Windows-specific tools and features (e.g., Active Directory, gMSA, BitLocker) are mentioned with more detail or before Linux equivalents. Some sections (e.g., disk encryption) reference Windows solutions (BitLocker, PowerShell) and leave Linux solutions as TODOs, without examples or guidance. Windows user account types and AD integration are described, but Linux equivalents (e.g., Linux user/group management, disk encryption) are not provided or are missing.
Recommendations
  • Add Linux-specific examples and guidance, especially for disk encryption and user/group management in Service Fabric clusters.
  • Ensure parity in describing how to secure applications and resources on Linux clusters, including how to run services under Linux user accounts and manage secrets/certificates.
  • Provide links or references to Linux documentation where appropriate (e.g., encrypting disks on Linux clusters, using Linux containers).
  • Avoid listing Windows tools/features first unless they are more broadly applicable; present both Windows and Linux options together.
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-04 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page for 'Application lifecycle in Service Fabric' demonstrates notable Windows bias. PowerShell cmdlets are consistently referenced alongside .NET APIs and REST operations, but Linux-native tools or CLI examples (such as sfctl or Azure CLI) are missing or relegated to a generic link. Windows tools and PowerShell patterns are mentioned throughout, often before REST or .NET alternatives, and no Linux/macOS-specific guidance or examples are provided. This creates friction for non-Windows users, especially since Service Fabric supports cross-platform development and management.
Recommendations
  • Add explicit sfctl (Service Fabric CLI) and Azure CLI command examples for each lifecycle operation (deploy, upgrade, remove, etc.), not just links.
  • Where PowerShell cmdlets are mentioned, provide equivalent CLI commands and highlight their parity.
  • Clarify which tools are cross-platform and which are Windows-only, to help users choose the right approach.
  • Consider including bash or shell script snippets for common workflows.
  • Review and update links to ensure Linux/macOS users can easily find relevant instructions.
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-04 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. All code examples are provided exclusively in PowerShell, a Windows-centric tool, with no equivalent examples for Linux/macOS users. The documentation references Windows-specific technologies (e.g., http.sys, Windows HTTP Server API) without clarifying cross-platform alternatives or limitations. Additionally, the 'Next steps' section prioritizes Visual Studio and PowerShell workflows, both of which are primarily Windows-based, and does not mention Linux-native tools or workflows.
Recommendations
  • Provide equivalent CLI (Azure CLI or Service Fabric CLI) commands for application upgrade tasks, especially for Linux/macOS users.
  • Explicitly state any platform limitations or differences, such as http.sys and certificate handling, and offer Linux-specific guidance where possible.
  • Include Linux/macOS examples alongside PowerShell, or at least reference cross-platform tools in all relevant sections.
  • In the 'Next steps' section, add links or references to Linux/macOS-compatible upgrade workflows and tooling.
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-04 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-only examples for application removal and references PowerShell as a primary tool for managing Service Fabric resources. There are no CLI or Linux/macOS equivalent examples for critical operations, and PowerShell is mentioned before CLI in the 'Next steps' section. 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 application removal and other management tasks alongside PowerShell examples.
  • Explicitly mention cross-platform tools (such as Azure CLI and Service Fabric CLI) in all relevant sections, not just in 'Next steps'.
  • Provide guidance or links for Linux/macOS users on how to perform equivalent operations.
  • Ensure that REST API examples are shown where possible, as these are platform-agnostic.
GitHub Create Pull Request
Service Fabric Advanced Application Upgrade Topics ...-fabric/service-fabric-application-upgrade-advanced.md
Medium Priority View Details →
Scanned: 2026-03-04 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 advanced Service Fabric application upgrade topics demonstrates a notable Windows/PowerShell bias. All command-line examples use PowerShell cmdlets (e.g., New-ServiceFabricService, Start-ServiceFabricApplicationUpgrade), with no mention of Linux/macOS equivalents such as the Service Fabric CLI (sfctl). References to ARM templates and XML manifest editing are platform-neutral, but all interactive/command-line instructions assume a Windows/PowerShell environment. There are no examples or guidance for Linux users, and PowerShell is presented as the default tool for upgrades and service management.
Recommendations
  • Add equivalent examples using the Service Fabric CLI (sfctl), which is cross-platform and supported on Linux/macOS.
  • Where PowerShell cmdlets are referenced, include a note or table mapping them to their sfctl equivalents.
  • Clarify in the introduction that both PowerShell and sfctl can be used for Service Fabric management, and link to relevant cross-platform documentation.
  • Ensure that at least one example in each section demonstrates the Linux/macOS workflow.
  • Where possible, use platform-neutral language (e.g., 'use a command-line tool such as PowerShell or sfctl') instead of only referencing PowerShell.
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-04 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 and 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 reliance on PowerShell and Windows-specific tooling creates friction for non-Windows users.
Recommendations
  • Add equivalent examples using Bash and curl for REST API calls, suitable for Linux/macOS users.
  • Document how to authenticate and interact with Service Fabric REST APIs from Linux/macOS (e.g., using OpenSSL for certificate handling).
  • Mention Azure CLI or other cross-platform tools if available.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http Module is required only for Windows, and provide alternatives for other platforms.
  • Reorder examples so that REST API usage is shown in a generic, cross-platform way first, followed by PowerShell-specific examples.
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-03-04 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides several manual scaling instructions using PowerShell cmdlets (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState) without offering equivalent Linux CLI or cross-platform alternatives. Additionally, PowerShell is mentioned first and exclusively in step-by-step guides, which may create friction for Linux/macOS users. However, the page does reference Linux clusters in the 'Next steps' section, and the overall guidance is not Windows-only.
Recommendations
  • Add equivalent Linux CLI instructions (e.g., using sfctl or REST API) alongside PowerShell examples for manual scaling operations.
  • Clearly indicate which commands are Windows-only and provide cross-platform alternatives where possible.
  • Consider showing cross-platform examples first or in parallel, rather than defaulting to PowerShell.
  • Link to documentation for Linux/macOS management tools (e.g., sfctl, Azure CLI) when referencing PowerShell commands.
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-04 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 Windows/PowerShell-centric examples and references, such as mentioning PowerShell APIs and classic PowerShell tasks in Azure DevOps, referencing Windows-specific tools (e.g., netsh), and linking to Windows ARM templates before Linux equivalents. Linux is mentioned, but examples and explanations are often Windows-first or Windows-only, with Linux alternatives sometimes missing or less detailed.
Recommendations
  • Provide Linux CLI (az, bash) examples alongside PowerShell examples, especially for cluster management and networking tasks.
  • Reference Linux ARM template samples equally with Windows samples.
  • Clarify which networking rules and port ranges apply to Linux clusters, and provide Linux-specific guidance where Windows-only tools (e.g., netsh) are referenced.
  • Expand explanations for Linux scenarios, such as application networking, DevOps integration, and reverse proxy usage.
  • Ensure Linux documentation links are as prominent as Windows links throughout the page.
GitHub Create Pull Request
Service Fabric Understanding periodic backup configuration ...-fabric-backuprestoreservice-configure-periodic-backup.md
Medium Priority View Details →
Scanned: 2026-03-04 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 Azure Service Fabric's backup configuration. However, the only on-premises backup storage example provided is for a Windows file share, using Windows authentication and UNC paths (\\StorageServer\BackupStore). No Linux or cross-platform file share example (e.g., SMB with Linux, NFS, or guidance for Linux clusters) is given. This may create friction for Linux users deploying standalone Service Fabric clusters who wish to use local backup storage.
Recommendations
  • Add examples or guidance for configuring file share backup storage on Linux clusters, such as using SMB/CIFS mounts or NFS.
  • Clarify whether file share backup storage is supported on Linux Service Fabric clusters, and if so, provide sample configurations.
  • Mention any platform-specific limitations for backup storage options (e.g., if file share is Windows-only, state this explicitly).
  • Provide parity in documentation by including Linux authentication mechanisms or mount instructions where relevant.
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-04 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Service Fabric clusters, but only PowerShell is used for advanced cluster upgrade operations. Windows-specific tools and registry settings are mentioned without Linux equivalents or guidance. There are missing Linux-specific examples for tasks like manual cluster upgrades, and disabling Windows Update is discussed without mentioning Linux patch management.
Recommendations
  • Provide Linux-native command examples (e.g., Bash scripts or Linux CLI equivalents) for cluster upgrade operations currently shown only in PowerShell.
  • Include guidance or references for managing OS updates and patching on Linux-based Service Fabric clusters, similar to the Windows Update/registry section.
  • When mentioning Windows-specific tools or settings, add parallel Linux guidance or explicitly state if the step is not required/applicable for Linux.
  • Where possible, balance PowerShell and Bash/CLI examples throughout the documentation, not just for initial deployment.
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-03-04 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation generally provides both Windows and Linux guidance for key security tasks, but there is a recurring pattern of presenting Windows/PowerShell examples and tools first, and in some sections, Windows-specific tooling (e.g., Windows Defender, PowerShell cmdlets) is discussed in detail while Linux equivalents are only briefly mentioned or omitted. Some sections (like Windows Defender) are Windows-only by nature, but others (such as encryption and certificate management) could benefit from more balanced Linux coverage.
Recommendations
  • When presenting example commands or workflows, alternate the order or present Linux and Windows examples side by side to avoid the perception of Windows-first bias.
  • Where Windows-specific tools (e.g., PowerShell, Windows Defender) are discussed, provide equivalent Linux guidance or explicitly state when no equivalent exists.
  • In sections like 'Encrypting Service Fabric package secret values', ensure Linux and Windows instructions are equally detailed and parallel in structure.
  • For security baseline recommendations, mention or link to industry-standard Linux security baselines (e.g., CIS Benchmarks) alongside Windows baselines.
  • In sections where only Windows tooling is described (e.g., Windows Defender exclusions), add a note or section about recommended Linux antimalware practices or clarify that Linux users should refer to their distribution's documentation.
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-04 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation covers Service Fabric cluster settings for both Azure-hosted and standalone clusters. However, there is evidence of Windows bias: Windows terminology and tools (e.g., certificate store names like 'MY', 'LocalMachine', NTLM authentication, Windows Defender Firewall) are referenced throughout, often without explicit Linux equivalents or with Windows defaults shown first. Some parameters (e.g., ContainerNetworkSetup) have Windows defaults prioritized. Certificate store references and NTLM authentication are Windows-centric, and explanations often reference Windows APIs (e.g., CertGetCertificateChain). While Linux is mentioned in some places, parity is not always clear.
Recommendations
  • Explicitly document Linux equivalents for certificate store names, authentication mechanisms, and file paths.
  • Where Windows tools or terminology are used (e.g., NTLM, Windows Defender Firewall), add Linux alternatives or clarify if the feature is Windows-only.
  • Ensure that Linux-specific configuration options and defaults are shown alongside Windows, not only as afterthoughts.
  • Add links or references to Linux-specific documentation where relevant.
  • Clarify which settings are cross-platform and which are platform-specific, ideally with a table or annotation.
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-03-04 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 Service Fabric Cluster Resource Manager - Placement Policies consistently provides PowerShell examples for configuring placement policies, but does not offer equivalent Linux/macOS CLI (e.g., sfctl) or REST API examples. The PowerShell examples are shown alongside C# code, with no mention of cross-platform tools or commands, creating friction for Linux/macOS users who may not have access to PowerShell or prefer native tools.
Recommendations
  • Add equivalent examples using sfctl (Service Fabric CLI), which is cross-platform and supported on Linux/macOS.
  • Include REST API examples for placement policy configuration, as these are platform-agnostic.
  • Clearly indicate which tools are Windows-only and provide guidance for Linux/macOS users on how to achieve the same tasks.
  • Consider reordering examples so that cross-platform tools (sfctl, REST) are shown before or alongside PowerShell.
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-04 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 Bash equivalents. PowerShell is a Windows-centric tool, and its exclusive use in examples creates friction for Linux/macOS users, who may use Azure CLI or REST APIs instead. There is no guidance or parity for non-Windows environments.
Recommendations
  • Add Azure CLI examples for all PowerShell commands shown, as Azure CLI is cross-platform and supported on Linux/macOS.
  • Mention REST API options for managing Application Groups, with example requests.
  • Clarify which management tools are available on Linux/macOS and provide links or instructions for their use.
  • If PowerShell Core (pwsh) is supported for these commands, specify this and provide Linux/macOS installation guidance.
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-04 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides code examples for managing Service Fabric metrics primarily in C# and PowerShell. PowerShell is a Windows-centric tool, and no equivalent Linux/macOS CLI examples (such as Azure CLI or Bash scripts) are provided. The PowerShell examples are given alongside C# code, but there is no mention of cross-platform alternatives or guidance for Linux users. This creates friction for users running Service Fabric clusters on Linux or managing them from non-Windows environments.
Recommendations
  • Add Azure CLI examples for service creation and metric configuration, as Azure CLI is cross-platform.
  • Mention Bash scripting or REST API usage for metric management tasks, with sample commands.
  • Clarify whether the PowerShell commands are supported on PowerShell Core (cross-platform) or only Windows PowerShell.
  • Provide guidance or links for Linux/macOS users on how to perform equivalent tasks.
  • Explicitly state any limitations or differences for Linux clusters in Service Fabric regarding metrics management.
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-04 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 XML, JSON, PowerShell, and C#. However, all CLI/API examples are given exclusively in PowerShell, with no equivalent Bash, Linux CLI, or cross-platform REST API examples. PowerShell is presented as the primary scripting interface for dynamic operations, creating friction for Linux/macOS users who cannot use PowerShell natively. The C# examples are platform-neutral, but the lack of Linux-friendly CLI guidance is notable.
Recommendations
  • Add Bash or Azure CLI examples for service sensitivity and maximum load configuration, where possible.
  • Clarify whether PowerShell commands can be run on Linux/macOS (e.g., via PowerShell Core), or provide REST API equivalents.
  • Mention cross-platform tools or interfaces (such as Azure CLI or REST API) before or alongside PowerShell.
  • Explicitly state if certain operations are only possible via PowerShell, and suggest alternatives for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Cluster Resource Manager - Management Integration ...fabric-cluster-resource-manager-management-integration.md
Medium Priority View Details →
Scanned: 2026-03-04 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 (Get-ServiceFabricPartitionHealth) for querying health reports, but does not include equivalent examples for Linux/macOS users (e.g., using sfctl or REST API). The only command-line interaction shown is Windows/PowerShell-specific, which may create friction for users managing Service Fabric clusters from non-Windows environments.
Recommendations
  • Add equivalent Linux/macOS examples using sfctl (the cross-platform Service Fabric CLI) for querying partition health and other management tasks.
  • Where possible, provide REST API examples for cluster management operations, as these are platform-agnostic.
  • When showing command-line examples, present both Windows (PowerShell) and Linux/macOS (bash/sfctl) options, or note the cross-platform alternatives.
  • Explicitly mention that the PowerShell example is for Windows and direct Linux/macOS users to the appropriate tools.
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-04 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 and C# examples for configuring Service Fabric MoveCost, but does not include equivalent Linux/Unix shell (e.g., Bash/CLI) examples or mention cross-platform tools. PowerShell is featured as the only command-line interface, which may create friction for Linux/macOS users.
Recommendations
  • Add Azure CLI examples for creating and updating Service Fabric services with MoveCost, if supported.
  • If PowerShell is required, clarify whether Azure PowerShell Core (cross-platform) is supported, and provide Bash/CLI alternatives where possible.
  • Explicitly mention any platform limitations (e.g., if MoveCost configuration is only possible via PowerShell or C#).
  • Include notes or links to Linux/macOS setup guides for Service Fabric management.
GitHub Create Pull Request
← Previous Page 20 of 99 Next →