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 1601-1625 of 2475 flagged pages
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-12 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 equal prominence. In the cluster upgrade section, only PowerShell commands are provided for manual upgrades, with no Linux shell (bash) or cross-platform alternatives. Windows registry and Windows Update settings are discussed for VM configuration, with no mention of Linux equivalents or guidance for disabling updates on Linux VMs. Windows-specific configuration appears before Linux in some sections.
Recommendations
  • Provide bash or Azure CLI examples for manual cluster upgrades alongside PowerShell, or clarify if Linux users should use different methods.
  • Include guidance for disabling automatic updates on Linux VMs (e.g., using cloud-init or OS-specific package manager settings).
  • When discussing VM configuration, mention both Windows and Linux settings, or clearly indicate when a step is Windows-only.
  • Ensure Linux examples and references are given equal prominence and ordering as Windows examples, especially in sections not inherently Windows-specific.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page consistently provides PowerShell examples for configuring Service Fabric placement policies, without offering equivalent Linux/macOS CLI or scripting examples (such as Azure CLI or Bash). Windows/PowerShell commands are presented alongside C# code, but Linux-friendly alternatives are absent. This creates friction for users managing Service Fabric clusters from non-Windows environments.
Recommendations
  • Add Azure CLI examples for each placement policy configuration, where possible.
  • Include Bash scripting or REST API examples to demonstrate cross-platform management.
  • Clarify whether PowerShell examples are usable on Linux/macOS (via PowerShell Core), or provide guidance for non-Windows users.
  • Explicitly mention any limitations or differences for Linux/macOS cluster management, if applicable.
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-12 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 numerous PowerShell-based examples and instructions for scaling operations, such as using `Disable-ServiceFabricNode`, `Get-ServiceFabricNode`, and `Remove-ServiceFabricNodeState`. These commands are specific to Windows environments and PowerShell, with no equivalent Linux CLI or script examples provided. Additionally, Windows/PowerShell instructions are presented first and exclusively in several critical scaling workflows, creating friction for Linux users. While the page mentions Linux clusters in the 'Next steps' section, the main scaling guidance lacks Linux parity.
Recommendations
  • Add equivalent Linux CLI or script examples for scaling operations, such as using Service Fabric CLI (`sfctl`) or REST API calls.
  • Clearly indicate when PowerShell commands are Windows-only and provide alternative instructions for Linux clusters.
  • Include Linux-specific guidance for cluster scaling, node management, and state cleanup.
  • Ensure that both Windows and Linux workflows are covered equally in critical operational sections, not just in 'Next steps'.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides both Windows and Linux guidance for Service Fabric networking, but there is a notable Windows bias. PowerShell and Windows-specific tools are referenced more frequently and often appear first. Some examples and explanations (such as dynamic port range checks and client API usage) are Windows-centric or reference Windows tools (e.g., netsh, PowerShell) without Linux equivalents. ARM template samples and DevOps sections also highlight Windows scenarios. However, Linux support is acknowledged and linked, and most best practices are generally applicable.
Recommendations
  • Provide Linux CLI (az CLI, bash) equivalents alongside PowerShell examples, especially for port range checks and cluster management.
  • Add explicit Linux-focused ARM template samples and links, similar to the Windows sample provided.
  • Clarify when guidance is Windows-only and offer Linux alternatives or note when Linux does not require certain steps (e.g., ephemeral port range).
  • Balance the order of presentation so Linux and Windows examples are equally prominent.
  • Expand DevOps/API guidance to include Linux-compatible tools and workflows.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page describes Azure Service Fabric node types and their relationship to virtual machine scale sets. While it mentions both Linux and Windows node types in the extension configuration, the JSON example and property table default to Windows-centric patterns (e.g., Windows-style file paths like 'D:\\SvcFab', certificate store references, and RDP-related next steps). Linux-specific guidance, examples, or parity for remote connection and file paths are missing. The 'Next steps' section links to PowerShell scripts for Windows tasks (RDP port and admin credentials), but does not mention Linux equivalents.
Recommendations
  • Add Linux-specific examples for file paths (e.g., '/var/svcfab') and certificate storage.
  • Provide guidance or links for remote SSH connection to Linux nodes, alongside RDP instructions for Windows.
  • Include Linux admin credential change instructions or scripts, not just Windows/PowerShell.
  • Clarify in property tables which settings are Windows-only and which are Linux-only.
  • Balance 'Next steps' with Linux-focused operational tasks and 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-12 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 (such as Azure CLI, Bash, or REST API) or cross-platform scripting. PowerShell is a Windows-centric tool, and its exclusive use creates friction for Linux/macOS users who may not have access to PowerShell or prefer native Linux tools.
Recommendations
  • Add Azure CLI examples for all operations shown (creation, update, querying, removal of application capacity).
  • Mention REST API endpoints or provide sample REST calls for managing Application Groups.
  • Clarify whether PowerShell examples are usable on Linux (via PowerShell Core), and if so, provide guidance; otherwise, offer alternatives.
  • Include Bash or shell script examples where possible, or link to cross-platform tools.
  • Explicitly state platform requirements for each example/tool used.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Windows-specific (ClusterManifest.xml, PowerShell) and cross-platform (ClusterConfig.json) configuration examples. However, Windows-centric examples (XML format, PowerShell commands) are consistently presented first and more prominently. PowerShell is the only CLI example given, with no Linux shell or CLI parity. The XML configuration is shown before the JSON configuration, and the infrastructure example is explicitly labeled as <WindowsServer>, with no mention of Linux clusters or their configuration specifics.
Recommendations
  • Add explicit Linux cluster configuration examples, such as <Linux> sections in ClusterManifest.xml or references to Linux node setup.
  • Provide CLI examples using Azure CLI or Bash for Linux users, alongside PowerShell.
  • Clarify any differences in cluster setup or resource management for Linux-based Service Fabric clusters.
  • Ensure JSON configuration examples are given equal prominence and placement to XML/Windows examples.
  • Mention Linux/macOS support status for Service Fabric clusters and link to relevant platform-specific documentation.
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-12 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 partition health, using Windows-style paths and commands (e.g., 'PS C:\Users\User > Get-ServiceFabricPartitionHealth'), without offering equivalent Linux/macOS CLI examples. The example is presented early and exclusively, which may create friction for Linux users seeking parity.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl) for Linux/macOS users, e.g., 'sfctl partition health --partition-id ...'.
  • Mention cross-platform management tools and clarify which commands are available on which OS.
  • Where PowerShell is used, provide alternative commands or note if PowerShell Core is supported on Linux/macOS.
  • Ensure examples and instructions are not Windows-centric unless the feature is Windows-only.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides PowerShell examples for configuring move cost, but does not offer equivalent Linux/bash/CLI examples. PowerShell is primarily a Windows tool, and its exclusive use creates friction for Linux/macOS users. The C# examples are cross-platform, but administrative scripting is often done via CLI tools, and only Windows-centric options are shown.
Recommendations
  • Add Azure CLI or REST API examples for configuring move cost, as these are cross-platform and commonly used on Linux/macOS.
  • Explicitly mention whether PowerShell examples are supported on Linux/macOS (via PowerShell Core), or provide bash equivalents if possible.
  • Reorder examples so that cross-platform options (Azure CLI, REST API, C#) are shown before or alongside PowerShell.
  • Clarify any platform limitations for Service Fabric management commands.
GitHub Create Pull Request
Service Fabric Azure Service Fabric dynamic node tags ...tps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-node-tagging.md
Medium Priority View Details →
Scanned: 2026-02-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides detailed PowerShell examples for managing node tags and service requirements, but does not offer equivalent CLI/bash or Linux-native examples. PowerShell is a Windows-centric tool, and its exclusive use here creates friction for Linux/macOS users. No mention is made of Service Fabric CLI or REST API usage for these tasks, despite REST APIs being referenced earlier.
Recommendations
  • Add examples using Service Fabric CLI (sfctl) for node tag management and service configuration, which is cross-platform and works on Linux/macOS.
  • Provide REST API sample requests for adding/removing node tags and setting service tag requirements, as REST APIs are mentioned as a supported mechanism.
  • Clarify which PowerShell commands are available on Linux (if any), or note their Windows-only nature.
  • Consider including bash or shell script examples where appropriate.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides PowerShell examples for configuring service sensitivity and maximum load, but does not mention or provide equivalent CLI or scripting examples for Linux/macOS users. The PowerShell API is highlighted as a primary method for dynamic configuration, and no Linux-native tools or cross-platform alternatives (such as Azure CLI or REST API) are referenced. This creates friction for users managing Service Fabric clusters from non-Windows environments.
Recommendations
  • Add Azure CLI or REST API examples for configuring service sensitivity and maximum load, if supported.
  • Clarify whether PowerShell examples are usable on Linux/macOS (via PowerShell Core), or provide guidance for cross-platform usage.
  • Mention any limitations or alternatives for Linux/macOS users, such as using JSON/XML manifests or C# SDK.
  • Consider providing bash or shell script examples if applicable.
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-12 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. PowerShell commands are shown before any mention of cross-platform alternatives, and there is no guidance for Linux users on how to perform these tasks. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other tools.
Recommendations
  • Add Azure CLI examples for service creation and metric management, as Azure CLI is cross-platform.
  • Provide Bash script examples or reference REST API usage for metric operations.
  • Explicitly mention which tools are available on Linux/macOS and provide links or instructions for installation.
  • Clarify whether PowerShell Core (cross-platform) is supported, and if so, provide guidance for Linux/macOS users.
  • Ensure that documentation sections using PowerShell are supplemented with cross-platform alternatives.
GitHub Create Pull Request
Service Fabric Azure Service Fabric standalone cluster scaling ...ce-fabric/service-fabric-cluster-scaling-standalone.md
Medium Priority View Details →
Scanned: 2026-02-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page for scaling Azure Service Fabric standalone clusters demonstrates a Windows bias by referencing PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) without mentioning Linux equivalents or cross-platform tooling. The linked instructions for scaling standalone clusters point to a Windows Server-specific guide, and there are no examples or guidance for Linux-based Service Fabric deployments, which are possible but not addressed.
Recommendations
  • Include examples and instructions for scaling Service Fabric standalone clusters deployed on Linux machines, if supported.
  • Reference cross-platform tools (such as Service Fabric CLI or REST API) alongside PowerShell, and provide usage examples for both Windows and Linux environments.
  • Clarify in the documentation whether standalone clusters are supported on Linux, and if not, explicitly state this to avoid confusion.
  • If Linux is supported, add links to Linux-specific scaling guides or sections within the documentation.
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-12 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 demonstrates a notable Windows bias. All deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) without mention of Azure CLI equivalents or Linux/macOS-friendly approaches. Application packaging is described via Visual Studio, a Windows-centric tool, with no alternative for Linux/macOS users. There are no examples or guidance for Linux users, and Windows tools are presented first and exclusively.
Recommendations
  • Add Azure CLI examples for deployment and deletion alongside PowerShell examples.
  • Provide guidance for packaging Service Fabric applications using cross-platform tools (e.g., dotnet CLI, sfctl, or manual zip commands).
  • Mention and link to Linux/macOS-compatible tooling and workflows.
  • Clarify which steps are Windows-only and offer alternatives where possible.
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-12 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 provides a broad overview of Azure Service Fabric, covering both Windows and Linux support. However, there is a notable Windows bias: Windows-specific tools and processes (e.g., PowerShell, Visual Studio, Windows services/executables) are mentioned first or exclusively in several sections. Examples and links for creating standalone clusters are Windows-only, and Linux standalone clusters are explicitly not supported. PowerShell is often referenced before CLI, and Windows-specific executables (FabricHost.exe, Fabric.exe) are described as core components. While Linux support is acknowledged, Linux-specific instructions, examples, and tools are less prominent or missing.
Recommendations
  • Provide Linux-first or Linux-parity examples and instructions alongside Windows ones, especially for cluster creation, management, and health monitoring.
  • Highlight CLI usage equally or before PowerShell, as CLI is cross-platform.
  • Add explicit guidance for Linux users where features are supported, including links to Linux documentation and tools.
  • Clarify Windows-only limitations early and consistently, and provide alternatives or workarounds for Linux users where possible.
  • Include Linux-specific troubleshooting, monitoring, and diagnostic tools and workflows.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page on 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 instructions for accessing Service Fabric events on Linux-based clusters, nor are Linux-native tools or patterns mentioned. Windows tools and patterns are discussed first and exclusively, creating friction for Linux users.
Recommendations
  • Add information about how Service Fabric events are logged and accessed on Linux clusters, including any differences in event channels or monitoring tools.
  • Mention Linux-native logging mechanisms (e.g., syslog, journald) if applicable, and provide examples or references for integrating Service Fabric diagnostics with these tools.
  • Clarify whether the Azure diagnostics agent and EventStore REST APIs are supported and configured differently on Linux clusters.
  • Ensure parity in examples and instructions for both Windows and Linux environments.
GitHub Create Pull Request
Service Fabric Secure an Azure Service Fabric cluster ...cles/service-fabric/service-fabric-cluster-security.md
Medium Priority View Details →
Scanned: 2026-02-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page frequently references Windows Server clusters and provides links and instructions specifically for securing standalone clusters on Windows. There are no equivalent examples, links, or instructions for securing standalone Linux clusters, nor are Linux-specific security patterns or tools mentioned. Windows security (Kerberos) is discussed, but Linux authentication options are not. While Azure-hosted clusters are mentioned (which can be Linux or Windows), standalone cluster guidance is Windows-only.
Recommendations
  • Add explicit guidance and links for securing standalone Linux Service Fabric clusters, including certificate setup and any Linux-specific authentication options.
  • Include Linux examples and instructions alongside Windows examples, especially for node-to-node and client-to-node security.
  • Mention Linux tools and patterns (e.g., OpenSSL for certificate creation, Linux account management) where relevant.
  • Clarify which security scenarios apply equally to Linux and Windows, and which are Windows-specific.
  • Provide parity in recommendations for Linux clusters, not just Windows clusters.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation generally avoids OS-specific bias in most upgrade scenarios, but in the 'Upgrading OS images for cluster nodes' section, it only references patching Windows operating systems and links exclusively to Windows-specific instructions. Additionally, the 'Patch Orchestration Application (POA)' is described as a solution for Windows OS patching, with no mention of Linux equivalents or guidance for clusters running Linux nodes. In other sections, both PowerShell and Azure CLI are mentioned together, but PowerShell is listed first, which may indicate a subtle 'windows_first' ordering bias.
Recommendations
  • Add explicit guidance or links for upgrading or patching Linux-based Service Fabric cluster nodes, if supported.
  • Clarify whether Patch Orchestration Application (POA) or similar solutions exist for Linux clusters, or state if it is Windows-only.
  • When mentioning management tools, alternate the order of PowerShell and Azure CLI, or mention Azure CLI first in some cases to balance perceived bias.
  • If certain features (like OS patching) are Windows-only, clearly state this to avoid confusion for Linux users.
GitHub Create Pull Request
Service Fabric Scalability of Service Fabric services .../service-fabric/service-fabric-concepts-scalability.md
Medium Priority View Details →
Scanned: 2026-02-12 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 and administrative instructions primarily using PowerShell, which is a Windows-centric tool. All command-line examples are in PowerShell, with no equivalent Linux (bash/CLI) examples or references to Linux-native tools. Windows tools and patterns are mentioned first and exclusively in example sections, creating friction for Linux users who may not be familiar with PowerShell or lack access to it.
Recommendations
  • Add equivalent bash/CLI examples for Service Fabric operations, such as scaling services, creating/removing instances, and updating configurations.
  • Reference Linux-native tools or Service Fabric CLI where appropriate, alongside PowerShell examples.
  • Clarify which commands are platform-specific and provide guidance for Linux users on how to achieve the same tasks.
  • Consider reordering examples so that platform-neutral or Linux examples are presented alongside or before Windows/PowerShell examples.
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-12 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, but does not offer equivalent Linux CLI or scripting examples. Windows tools and patterns (e.g., ApplicationManifest.xml, Visual Studio) are mentioned before Linux alternatives, and Linux-specific limitations are described without offering Linux-native workflows or parity in examples. There are no Linux CLI (e.g., Bash, Azure CLI) examples for managing DNS service or setting DNS names, and enabling DNS service via portal is only available for Windows clusters.
Recommendations
  • Add Azure CLI or Bash examples for setting DNS names and managing DNS service, especially for Linux clusters.
  • Explicitly document Linux-native workflows for cluster and service management, including how to enable DNS service on Linux clusters (e.g., via ARM templates or CLI).
  • Where PowerShell is used, provide equivalent Linux command-line instructions or scripts.
  • Clarify which steps are Windows-only and which are cross-platform, and ensure Linux users are guided through their supported scenarios.
  • Mention Linux-friendly editors (e.g., VS Code) alongside Visual Studio when discussing ApplicationManifest.xml editing.
GitHub Create Pull Request
Service Fabric Package an existing executable to Azure Service Fabric ...abric/service-fabric-guest-executables-introduction.md
Medium Priority View Details →
Scanned: 2026-02-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias. It references Windows file paths (e.g., Service Fabric SDK schema location in C:\Program Files\...), and mentions Visual Studio as a packaging tool without Linux alternatives. There are no explicit Linux/macOS examples or guidance, and the directory structure example uses a Windows-style executable (.exe). However, the content does not explicitly state that the process is Windows-only, and Service Fabric supports Linux clusters and non-Windows workloads.
Recommendations
  • Add explicit Linux/macOS guidance for packaging guest executables, including references to cross-platform tools (e.g., CLI, VS Code, or other IDEs).
  • Provide Linux file path examples for schema files and directory structure.
  • Clarify that guest executables can be any platform-supported binary (not just .exe), and show examples for Linux binaries.
  • Mention Linux deployment scenarios and provide links to Linux-specific documentation where relevant.
  • Ensure parity in sample links and instructions for Linux users.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page primarily describes Azure Service Fabric hosting lifecycle concepts in a platform-neutral manner, but the 'Next steps' section and some linked references emphasize PowerShell for deployment/removal tasks, which is traditionally Windows-centric. There are no explicit Linux/bash examples or references to Linux-native tools, and the only advanced example for downloading a ServicePackage in advance links to a PowerShell cmdlet. This creates friction for Linux/macOS users, who may need to use Service Fabric CLI or REST APIs instead.
Recommendations
  • Add Linux/bash examples alongside PowerShell for deployment and removal tasks.
  • Mention Service Fabric CLI (sfctl) and REST API options for Linux/macOS users.
  • Provide links to Linux/macOS-specific documentation or tools where applicable.
  • Clarify when PowerShell is cross-platform (PowerShell Core) vs. Windows-only.
  • Ensure that advanced scenarios (like downloading ServicePackages) include Linux-compatible instructions.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell and Visual Studio (Windows-centric tools) are mentioned first and in more detail, while Linux-native workflows are only briefly referenced (e.g., sfctl and install.sh) without concrete examples. There are no explicit Linux/macOS command-line examples, and the guidance assumes familiarity with Windows tooling.
Recommendations
  • Add explicit Linux/macOS command-line examples using sfctl and install.sh, including sample commands for passing parameters.
  • Reorder sections or provide parallel examples so that Linux-native tools (sfctl, bash scripts) are presented alongside or before Windows/PowerShell equivalents.
  • Clarify when a tool or script is Windows-only (e.g., Deploy-FabricApplication.ps1) and provide Linux alternatives.
  • Expand on the Jenkins/script task example to show a concrete Linux shell script for token replacement.
  • Where Visual Studio is referenced, note cross-platform alternatives or clarify if the workflow is Windows-only.
GitHub Create Pull Request
Service Fabric Reliable services app manifest examples ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-manifest-example-reliable-services-app.md
Medium Priority View Details →
Scanned: 2026-02-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page for Service Fabric application and service manifest examples exhibits mild Windows bias. Windows-specific concepts (such as local admin accounts, NetworkService, Setup.bat, and EXE-based entry points) are referenced throughout, and PowerShell is mentioned as the primary tool for service creation. There is no explicit mention of Linux equivalents, nor are Linux-specific examples or guidance provided. However, the XML manifest format itself is cross-platform, and the examples are not strictly Windows-only.
Recommendations
  • Add explicit notes or examples for Linux deployments, such as using shell scripts (.sh) instead of batch files (.bat) for SetupEntryPoint.
  • Clarify how user accounts and principals map to Linux (e.g., use of system users, groups, and service accounts).
  • Mention Linux tools (such as Azure CLI or Bash) for application/service creation, alongside PowerShell.
  • Where Windows-specific terms are used (e.g., NetworkService), provide Linux equivalents or note differences.
  • Ensure that references to executables (e.g., VotingWeb.exe) are accompanied by guidance for Linux (e.g., dotnet binaries or other formats).
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-12 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 command-line patterns (e.g., RDP, ping from C:\ prompt), without offering equivalent Azure CLI or Bash examples for Linux/macOS users. All deployment steps use PowerShell, and Windows-centric terminology and tools are mentioned first or exclusively. No Linux-specific guidance or parity is provided.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all deployment steps, especially for template deployment and resource creation.
  • Include Bash shell command examples for common tasks (e.g., ping, SSH access) instead of only Windows CMD/RDP.
  • Mention Linux/macOS-compatible tools and workflows (e.g., SSH instead of RDP, Azure CLI instead of PowerShell).
  • Clarify that Service Fabric clusters can be managed from Linux/macOS and provide links or sections for cross-platform guidance.
  • Where possible, show both Windows and Linux command-line examples side-by-side.
GitHub Create Pull Request
← Previous Page 65 of 99 Next →