Service Fabric

407
Total Pages
336
Linux-Friendly Pages
71
Pages with Bias
17.4%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

1305 issues found
Showing 276-300 of 1305 flagged pages
Service Fabric Azure Service Fabric application resource model ...ervice-fabric/service-fabric-concept-resource-model.md
Medium Priority View Details →
Scanned: 2026-02-17 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 the Azure Service Fabric application resource model demonstrates a notable Windows bias. All deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource), with no mention of Azure CLI equivalents or Linux/macOS workflows. The application packaging step is shown using Visual Studio, a Windows-centric tool, and directory paths are given in Windows format. There are no instructions or examples for Linux/macOS users, nor is cross-platform tooling discussed.
Recommendations
  • Add Azure CLI examples for deployment, upgrade, and deletion steps alongside PowerShell examples.
  • Include instructions for packaging applications using cross-platform tools (e.g., dotnet CLI, SF tooling) instead of only Visual Studio.
  • Show directory paths in both Windows and Linux/macOS formats, or clarify that the steps are applicable cross-platform.
  • Mention or link to Linux/macOS-specific guidance for Service Fabric application management.
  • Consider providing sample scripts or workflows for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Learn more about Azure Service Fabric ...icles/service-fabric/service-fabric-content-roadmap.md
Medium Priority View Details →
Scanned: 2026-02-17 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 page provides a broad overview of Azure Service Fabric, which supports both Windows and Linux. However, there are several instances of Windows bias: Windows-specific tools (PowerShell, Visual Studio) are mentioned before their Linux equivalents, Windows services and executables are referenced without clear Linux alternatives, and some examples or instructions are Windows-centric. Linux support is acknowledged, but Linux-specific examples, tools, and workflows are often missing or secondary.
Recommendations
  • Provide Linux-specific examples and workflows alongside Windows instructions, especially in sections referencing PowerShell, Visual Studio, and Windows executables.
  • Mention Linux CLI tools (e.g., Bash, sfctl) and package management options where PowerShell or Windows tools are discussed.
  • Clarify which features are Windows-only and which are cross-platform, linking to Linux documentation where appropriate.
  • Add explicit instructions or links for creating and managing clusters on Linux, including supported programming models and deployment methods.
  • Balance the order of presentation so Linux and Windows are treated equally in examples and tool references.
GitHub Create Pull Request
Service Fabric Azure Service Fabric hosting activation and deactivation life cycle ...les/service-fabric/service-fabric-hosting-lifecycle.md
Medium Priority View Details →
Scanned: 2026-02-17 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page on Azure Service Fabric hosting activation and deactivation life cycle is largely platform-neutral in its conceptual explanations, but the 'Next steps' section and some linked references emphasize PowerShell for deployment/removal tasks, which is most commonly associated with Windows. There is no explicit mention of Linux equivalents or cross-platform tooling, and PowerShell is presented as the default method for operational tasks.
Recommendations
  • Add examples or links for deploying/removing applications using cross-platform tools (e.g., Azure CLI, REST API, or Service Fabric CLI) alongside PowerShell.
  • Clarify whether PowerShell examples are usable on Linux/macOS (via PowerShell Core), or provide Linux-specific instructions if differences exist.
  • Include references to Linux/macOS documentation or operational guides where relevant.
  • Ensure that linked references (such as [Deploy and remove applications]) include parity for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Upgrading Azure Service Fabric clusters ...icles/service-fabric/service-fabric-cluster-upgrade.md
Medium Priority View Details →
Scanned: 2026-02-17 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides general guidance on upgrading Azure Service Fabric clusters, but in sections such as 'Upgrading OS images for cluster nodes', it references Windows-specific patching and links only to Windows patching documentation. Additionally, PowerShell is mentioned as a tool for cluster management alongside Azure CLI, but Linux-specific tools or examples are not provided. The order of mention and focus on Windows patching creates a Windows-first impression, and Linux cluster upgrade scenarios are not addressed.
Recommendations
  • Add explicit guidance and links for patching/upgrading Linux-based Service Fabric clusters, if supported.
  • Provide Linux/macOS-specific examples for cluster management tasks (e.g., using Azure CLI or Bash scripts).
  • Clarify whether Service Fabric clusters can run on Linux nodes and, if so, include parity documentation for OS image upgrades and patch orchestration.
  • When mentioning PowerShell, also mention Bash/Azure CLI usage for Linux/macOS users, with example commands.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Events ...es/service-fabric/service-fabric-diagnostics-events.md
Medium Priority View Details →
Scanned: 2026-02-17 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page for Azure Service Fabric Events primarily references Windows-specific logging mechanisms (ETW/Windows Event logs) and the Windows Azure diagnostics agent. There are no explicit examples or guidance for accessing or monitoring Service Fabric events on Linux-based clusters, nor are Linux-native tools or patterns mentioned. Windows tools and approaches are presented first and exclusively, creating friction for Linux users.
Recommendations
  • Add documentation and examples for accessing Service Fabric events on Linux clusters, including supported logging mechanisms (e.g., stdout, syslog, or Azure Monitor integration for Linux).
  • Mention Linux-native monitoring tools and how they can be used to visualize or analyze Service Fabric events.
  • Clarify which approaches are Windows-only and provide Linux equivalents where possible.
  • Ensure parity in guidance for configuring diagnostics and event collection on both Windows and Linux clusters.
GitHub Create Pull Request
Service Fabric Azure Service Fabric DNS service ...n/articles/service-fabric/service-fabric-dnsservice.md
Medium Priority View Details →
Scanned: 2026-02-17 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 setting DNS names, references ApplicationManifest.xml (a Windows-centric deployment artifact), and describes enabling DNS service via Azure portal (Windows clusters only). Linux support is mentioned as limited, but there are no Linux-specific examples or guidance for equivalent tasks (e.g., using CLI, ARM templates, or other Linux-friendly tools). Windows tools and patterns are presented first and in greater detail, creating friction for Linux users.
Recommendations
  • Add explicit Linux-focused examples for setting DNS names, such as using Azure CLI, ARM templates, or other Linux-compatible methods.
  • Clarify which steps are Windows-only and provide alternative instructions for Linux clusters where possible.
  • Include guidance on how Linux users can enable DNS service (since portal is not supported), with step-by-step ARM template or CLI instructions.
  • Balance the order of examples so Linux methods are not always secondary or omitted.
  • Mention any limitations or workarounds for Linux clusters more prominently, and link to relevant Linux-specific documentation.
GitHub Create Pull Request
Service Fabric Azure Service Fabric hosting model ...rticles/service-fabric/service-fabric-hosting-model.md
Medium Priority View Details →
Scanned: 2026-02-17 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-based examples and references for managing Service Fabric services, with no equivalent CLI or Linux-native examples. PowerShell is featured as the primary command-line tool, and there is no mention of Service Fabric CLI (sfctl) or Bash examples, which are relevant for Linux/macOS users. This creates friction for non-Windows users, though the underlying concepts are cross-platform.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • When referencing PowerShell commands, also provide the analogous sfctl or REST API commands.
  • Explicitly mention that PowerShell examples are for Windows and provide guidance for Linux/macOS users.
  • Consider adding a table or section summarizing management options for both Windows and Linux environments.
GitHub Create Pull Request
Service Fabric Azure Service Fabric image store connection string ...fabric/service-fabric-image-store-connection-string.md
Medium Priority View Details →
Scanned: 2026-02-17 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page references PowerShell as the primary example for interacting with Service Fabric clusters, and links to PowerShell-based deployment/removal guides as the main 'next steps'. While Service Fabric is cross-platform, the examples and guidance are Windows-centric, with PowerShell mentioned before .NET and REST alternatives. There are no explicit Linux/macOS CLI or scripting examples, nor is Azure CLI or Bash referenced.
Recommendations
  • Add examples and links for deploying and managing Service Fabric clusters using cross-platform tools such as Azure CLI, Bash, or Python SDK.
  • Include Linux/macOS-specific instructions or clarify that the guidance applies equally to those platforms.
  • Reorder references so that cross-platform or platform-neutral tools (e.g., REST API, .NET Core) are mentioned before or alongside PowerShell.
  • Provide explicit guidance for verifying cluster manifests and connection strings on Linux/macOS environments.
GitHub Create Pull Request
Service Fabric Azure Service Fabric container application manifest examples ...abric/service-fabric-manifest-example-container-app.md
Medium Priority View Details →
Scanned: 2026-02-17 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page for Azure Service Fabric container application manifest examples demonstrates a notable Windows bias. The manifest examples and explanations are explicitly based on a Windows Server 2016 container sample. Several features and instructions (such as obtaining the OS build version with 'winver', Windows-style paths like 'c:\VolumeTest\Data', and references to the ServiceFabric PowerShell module) are Windows-specific or presented with Windows-first terminology. There are no Linux-specific examples, paths, or instructions, and Linux parity is only briefly mentioned in passing (e.g., certificate handling).
Recommendations
  • Add equivalent Linux-based manifest examples or clarify which sections apply to Linux clusters.
  • When referencing Windows tools (e.g., 'winver'), provide the Linux equivalent (e.g., 'cat /etc/os-release' or 'uname -r').
  • Use cross-platform path examples or provide both Windows and Linux path formats where relevant.
  • Clarify in the introduction whether the examples are intended for Windows-only clusters, or provide guidance for Linux clusters if supported.
  • When mentioning PowerShell or Windows-specific tools, also reference Linux equivalents (e.g., Azure CLI, Bash scripts) if available.
GitHub Create Pull Request
Service Fabric Manage apps for multiple environments ...e-fabric-manage-multiple-environment-app-configuration.md
Medium Priority View Details →
Scanned: 2026-02-17 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page presents Windows/PowerShell examples first and in greater detail, with explicit mention of PowerShell cmdlets and Visual Studio workflows. Linux tooling (sfctl) is mentioned, but with less detail and no explicit Linux shell example. There is no clear example or workflow for Linux/macOS users outside of a brief mention of sfctl and Jenkins.
Recommendations
  • Provide explicit Linux/macOS shell examples for application creation, such as using sfctl with sample JSON parameter input.
  • Balance the order of examples: present Linux/macOS workflows alongside or before Windows/PowerShell examples.
  • Expand on Jenkins and other cross-platform CI/CD tools with sample scripts for parameter substitution.
  • Clarify which tools are cross-platform and which are Windows-only, to help users choose appropriate workflows.
GitHub Create Pull Request
Service Fabric Networking patterns for Azure Service Fabric ...s/service-fabric/service-fabric-patterns-networking.md
Medium Priority View Details →
Scanned: 2026-02-17 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 only PowerShell-based deployment examples and references Windows tools (e.g., RDP, Windows command prompt for ping), with no equivalent Linux/macOS CLI (such as Azure CLI or Bash) examples. Windows-centric terminology and patterns are presented first and exclusively, creating friction for Linux/macOS users who may not use PowerShell or RDP.
Recommendations
  • Add Azure CLI (az) command examples alongside PowerShell for template deployments, resource creation, and querying.
  • Provide Linux/macOS-friendly instructions for accessing VMs (e.g., SSH instead of RDP), and for network testing (e.g., ping from Bash shell).
  • Explicitly mention cross-platform options for template deployment and management, clarifying that PowerShell is not required.
  • Where Windows command prompt examples are given (e.g., ping), add Bash equivalents.
  • Consider including a note at the start clarifying that all examples can be adapted for Linux/macOS users, and link to relevant cross-platform Azure documentation.
GitHub Create Pull Request
Service Fabric Add custom Service Fabric health reports ...rticles/service-fabric/service-fabric-report-health.md
Medium Priority View Details →
Scanned: 2026-02-17 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 'Add custom Service Fabric health reports' demonstrates a notable Windows bias. PowerShell is used extensively for command-line examples, and all CLI examples are given in PowerShell syntax with Windows-style prompts (PS C:\>). There is no mention of Linux/macOS equivalents, such as Bash or Azure CLI, nor are cross-platform command-line tools referenced. Windows tools and patterns (PowerShell) are presented before REST API options, and no Linux-specific guidance is provided.
Recommendations
  • Add equivalent Bash or Azure CLI examples for health reporting, especially for REST and cluster management tasks.
  • Clarify whether PowerShell cmdlets are available cross-platform (e.g., via PowerShell Core), and provide guidance for Linux/macOS users.
  • Explicitly mention how Linux-based Service Fabric clusters can report health, including any limitations or differences.
  • Consider reordering sections so that REST API examples (which are platform-neutral) are presented before PowerShell.
  • Add notes about cross-platform support for Service Fabric tooling, and link to relevant Linux/macOS documentation.
GitHub Create Pull Request
Service Fabric Replica soft delete for enhanced data protection in Service Fabric ...s/service-fabric/service-fabric-replica-soft-delete.md
Medium Priority View Details →
Scanned: 2026-02-17 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation consistently references PowerShell cmdlets (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica, Get-ServiceFabricReplica) as the primary or sole method for interacting with the replica soft delete feature. There are no CLI, REST, or Linux-native examples or references, and the use of PowerShell is assumed throughout. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other tooling.
Recommendations
  • Include equivalent examples using Service Fabric CLI (sfctl) or REST APIs, if available, alongside PowerShell examples.
  • Explicitly mention if the PowerShell cmdlets are cross-platform (e.g., available in PowerShell Core on Linux/macOS), or provide guidance for Linux/macOS users.
  • Document FabricClient API usage with code snippets in a cross-platform language (e.g., C#/.NET Core, Python) to show how to invoke the same operations programmatically.
  • Clarify any platform limitations (e.g., if certain APIs are only available on Windows nodes) to set expectations for non-Windows users.
GitHub Create Pull Request
Service Fabric Specifying Service Fabric service endpoints ...ce-fabric/service-fabric-service-manifest-resources.md
Medium Priority View Details →
Scanned: 2026-02-17 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 deploying Service Fabric applications, which is Windows-centric. The schema file path is given only for Windows (C:\Program Files\Microsoft SDKs\Service Fabric\schemas\ServiceFabricServiceModel.xsd), and PowerShell is referenced as the tool for deployment, with no Linux CLI or Bash equivalent shown. While there is a brief mention of Linux certificate storage, Linux deployment workflows are not demonstrated.
Recommendations
  • Add equivalent Linux/macOS deployment examples using Azure CLI or Bash scripts.
  • Mention the location of schema files for Linux installations, if applicable.
  • Provide guidance for Linux users on how to deploy Service Fabric applications (e.g., using sfctl or Azure CLI).
  • Ensure that references to tools (like PowerShell) are accompanied by cross-platform alternatives.
GitHub Create Pull Request
Service Fabric Fault Analysis Service overview .../service-fabric/service-fabric-testability-overview.md
Medium Priority View Details →
Scanned: 2026-02-17 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 usage examples for C# and PowerShell, but does not mention or provide equivalent examples for Linux/macOS command-line tools or scripting environments (such as Bash or CLI). The PowerShell example assumes a Windows environment and references the Service Fabric SDK, which is primarily Windows-focused. There is no mention of Linux-native tools or how to use the Fault Analysis Service from Linux/macOS, despite Service Fabric supporting Linux clusters.
Recommendations
  • Add examples for using the Fault Analysis Service from Linux/macOS environments, such as via Bash scripts, Azure CLI, or REST API.
  • Clarify whether the PowerShell module is available and supported on Linux (via PowerShell Core), or provide alternative instructions for Linux users.
  • Mention any prerequisites or limitations for Linux clusters, and provide guidance for Linux developers on how to access Fault Analysis Service features.
  • Ensure parity in documentation by including Linux/macOS-specific instructions alongside Windows/PowerShell examples.
GitHub Create Pull Request
Service Fabric Configure the upgrade of a Service Fabric application ...abric/service-fabric-visualstudio-configure-upgrade.md
Medium Priority View Details →
Scanned: 2026-02-17 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 is heavily focused on Windows tools, specifically Visual Studio and PowerShell, for configuring and upgrading Service Fabric applications. All examples and workflows reference Windows-centric tools, with no mention of Linux/macOS alternatives or cross-platform CLI usage. Linux users are not provided with equivalent instructions or examples, creating friction for those not on Windows.
Recommendations
  • Add instructions and examples for upgrading Service Fabric applications using Azure CLI or REST API, which are cross-platform.
  • Mention and link to any Linux-compatible Service Fabric tooling or workflows, such as sfctl.
  • Clarify which steps are Windows-only and provide Linux/macOS alternatives where possible.
  • Include sample commands and manifest edits using Linux shell syntax where relevant.
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-16 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides a PowerShell-only example for bypassing Infrastructure Service, and references Service Fabric Explorer (a Windows-centric tool) without mentioning Linux/macOS alternatives. While Service Fabric is cross-platform, the guidance and examples are Windows-focused, creating friction for Linux/macOS users.
Recommendations
  • Add equivalent CLI or REST API examples for bypassing Infrastructure Service, suitable for Linux/macOS users.
  • Mention and link to cross-platform management tools (e.g., Azure CLI, Service Fabric CLI) where possible.
  • Clarify if Service Fabric Explorer is available cross-platform or suggest alternatives for Linux/macOS users.
  • Provide Linux/macOS-specific instructions or note any limitations for non-Windows users.
GitHub Create Pull Request
Service Fabric Deny assignment policy for Service Fabric managed clusters ...cles/service-fabric/managed-cluster-deny-assignment.md
Medium Priority View Details →
Scanned: 2026-02-16 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides best practice examples using Azure PowerShell modules and references PowerShell-based tools prominently. While Azure CLI and ARM/Bicep are mentioned, PowerShell examples are given first and in more detail, which may create friction for Linux/macOS users who prefer CLI or scripting tools native to their platforms.
Recommendations
  • Add explicit Azure CLI examples for key operations (e.g., deleting NodeTypes, restarting/reimaging scale sets) alongside PowerShell examples.
  • Ensure CLI and Bicep/ARM template usage is described with equal prominence to PowerShell.
  • Clarify that all recommended tools (Azure CLI, ARM templates, Bicep) are fully cross-platform and provide links to their documentation.
  • Consider listing Azure CLI examples before or alongside PowerShell to avoid 'windows_first' bias.
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-16 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation mentions PowerShell cmdlets as a primary management interface for Service Fabric, without referencing Linux/macOS equivalents such as Azure CLI or REST APIs. This may give the impression that management is Windows-centric, and Linux users may not realize alternative tools exist.
Recommendations
  • Explicitly mention cross-platform management options, such as Azure CLI or REST APIs, alongside PowerShell cmdlets.
  • Provide links or references to documentation on managing Service Fabric clusters from Linux/macOS environments.
  • Clarify which management tools are available on which platforms to avoid confusion.
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-16 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Windows and Linux guidance for key security tasks, such as certificate generation and secret encryption, but Windows-specific tools (PowerShell, Windows Defender, Azure DSC) are mentioned first or exclusively in several sections. Windows examples and terminology appear before Linux equivalents, and some sections (Windows Defender, DSC, security baselines) are Windows-only without Linux alternatives or parity suggestions.
Recommendations
  • Where possible, present Windows and Linux examples side-by-side or in parallel sections, rather than Windows-first.
  • For sections like security baselines and antimalware, provide links or references to Linux security best practices (e.g., CIS Linux benchmarks, Linux antivirus solutions) or clarify Linux equivalents.
  • Mention Linux tooling (such as openssl, Linux security modules, etc.) alongside Windows tools, and avoid PowerShell-heavy bias unless the task is Windows-only.
  • Clarify when a feature or recommendation is Windows-only and provide Linux-specific guidance or alternatives where applicable.
  • Ensure that template snippets and instructions are equally applicable to Linux clusters, or note any differences.
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-16 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides several manual scaling instructions using PowerShell cmdlets (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState) without mentioning Linux/macOS equivalents or CLI alternatives. Windows/PowerShell-based steps are given first and exclusively in critical scaling workflows, while Linux clusters are only referenced in the 'Next steps' section. There are no Bash, Azure CLI, or cross-platform examples for these operations.
Recommendations
  • Add Azure CLI or Bash examples for scaling operations, especially for disabling/removing nodes and managing cluster state.
  • Explicitly mention cross-platform tools or workflows for Linux/macOS users, such as using Azure CLI or REST API for node management.
  • Clarify if PowerShell cmdlets are available on Linux/macOS (via PowerShell Core), or provide alternative commands.
  • Ensure that instructions for scaling clusters are equally accessible for both Windows and Linux clusters, not just in 'Next steps'.
GitHub Create Pull Request
Service Fabric Application lifecycle in Service Fabric ...service-fabric/service-fabric-application-lifecycle.md
Medium Priority View Details →
Scanned: 2026-02-16 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page heavily references PowerShell cmdlets and Windows-centric tooling (e.g., Remove-ServiceFabricApplicationPackage, Register-ServiceFabricApplicationType) throughout all lifecycle phases, often as the primary or only command-line example. While REST API and .NET SDK methods are also mentioned, there is a notable lack of explicit Linux/macOS CLI examples (such as Azure CLI or Service Fabric CLI [sfctl]), and no bash or cross-platform shell commands are provided. This creates friction for Linux/macOS users, who must infer or research equivalent commands.
Recommendations
  • Add explicit examples using Service Fabric CLI (sfctl) and/or Azure CLI for all major operations alongside PowerShell examples.
  • Where PowerShell cmdlets are referenced, provide equivalent bash or cross-platform command-line snippets.
  • Clarify in each section which tools are cross-platform and which are Windows-only.
  • Link to Linux/macOS-specific guidance or quickstarts where available.
  • Consider reordering examples to show cross-platform tools (sfctl, REST API) before or alongside Windows PowerShell.
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-16 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 auto scaling policies, but does not offer equivalent Linux/macOS command-line examples (e.g., Bash, CLI, or cross-platform tools). Windows-specific tools (PowerShell) are presented alongside C# and manifest examples, but Linux users are left without guidance for command-line operations. The documentation also presents PowerShell examples before mentioning Linux support, and does not clarify how Linux users should perform these tasks.
Recommendations
  • Add Azure CLI or Bash examples for configuring scaling policies, especially for Linux-based Service Fabric clusters.
  • Explicitly state which PowerShell commands are cross-platform (if any), or provide alternatives for Linux/macOS users.
  • Clarify any limitations or differences for Linux clusters, and link to relevant Linux-specific documentation.
  • Consider reordering examples so that cross-platform or manifest-based approaches are shown before Windows-specific tools.
  • Mention any GUI or portal-based configuration options if available, for broader accessibility.
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-16 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides both Windows and Linux guidance in several sections, but there is a notable Windows bias in example ordering, tool references, and some explanations. Windows/PowerShell examples and terminology are often presented first or exclusively, while Linux equivalents are sometimes missing or referenced second. Some sections (e.g., Azure DevOps, Client API, application networking) focus on Windows-specific tools or patterns without Linux parity.
Recommendations
  • Ensure all PowerShell/API examples are accompanied by equivalent CLI or Linux-native examples, especially in sections referencing 'Client API' and Azure DevOps.
  • When referencing tools (e.g., Service Fabric Explorer, reverse proxy), clarify Linux compatibility and provide Linux-specific instructions or links.
  • Avoid presenting Windows examples or terminology first unless the feature is Windows-only; alternate ordering or group by OS.
  • Expand application networking guidance to include Linux container scenarios and networking modes.
  • Where possible, provide ARM template samples for both Windows and Linux clusters, not just Windows.
  • Clarify when a feature or tool is Windows-only to reduce confusion for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Azure Service Fabric application resource model ...ervice-fabric/service-fabric-concept-resource-model.md
Medium Priority View Details →
Scanned: 2026-02-16 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 the Azure Service Fabric application resource model demonstrates notable Windows bias. All deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) without mention of Azure CLI equivalents or Bash scripting. Application packaging instructions reference Visual Studio, a Windows-centric tool, and do not provide alternatives for Linux/macOS users. No Linux-specific guidance or cross-platform examples are present, and Windows tools are mentioned first and exclusively.
Recommendations
  • Add Azure CLI examples for deployment, upgrade, and deletion alongside PowerShell examples.
  • Provide instructions for packaging applications using cross-platform tools (e.g., dotnet CLI, SF SDK for Linux/macOS).
  • Mention and link to Linux/macOS-compatible development environments (e.g., VS Code, command-line tools) for application packaging.
  • Clarify which steps are Windows-only and offer Linux/macOS alternatives where possible.
  • Ensure screenshots and walkthroughs are not exclusively tied to Windows UI (e.g., Visual Studio), or supplement them with cross-platform options.
GitHub Create Pull Request
← Previous Page 12 of 53 Next →