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 2201-2225 of 2475 flagged pages
Service Fabric Node types and virtual machine scale sets ...les/service-fabric/service-fabric-cluster-nodetypes.md
Medium Priority View Details →
Scanned: 2026-01-30 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page provides general information about Service Fabric node types and VM scale sets, but several examples and guidance sections show Windows-centric patterns. The JSON snippet uses a Windows-style file path (D:\SvcFab) in the dataPath property, and the next steps section links to PowerShell scripts for changing RDP port ranges and admin credentials, both of which are Windows-specific tasks. There are no Linux/macOS equivalents or examples for these operations, nor is there guidance for connecting to Linux nodes or managing them.
Recommendations
  • Provide Linux-specific examples, such as using Linux file paths (e.g., /var/svcfab) in the dataPath property.
  • Include guidance or links for managing Linux node types, such as SSH connection instructions and scripts for changing SSH port ranges or admin credentials.
  • Balance examples and instructions so that both Windows and Linux users can easily follow the documentation.
  • Clearly indicate when a step or example is Windows-only, and provide alternatives for Linux/macOS where possible.
Service Fabric Service Fabric Cluster Resource Manager - Application Groups ...ice-fabric-cluster-resource-manager-application-groups.md
Medium Priority View Details →
Scanned: 2026-01-30 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides only PowerShell and C# examples for managing Service Fabric Application Groups. PowerShell is a Windows-centric tool, and there are no examples or guidance for Linux/macOS users (e.g., Azure CLI, REST API, or bash scripting). This creates friction for users operating Service Fabric clusters on Linux or from non-Windows environments.
Recommendations
  • Add equivalent examples using Azure CLI or REST API for all operations shown in PowerShell.
  • Explicitly mention cross-platform management options for Service Fabric clusters.
  • Clarify which management operations are supported on Linux clusters and how to perform them.
  • If PowerShell is required, note its availability on Linux and provide installation guidance.
Service Fabric Describe a cluster by using Cluster Resource Manager ...ce-fabric-cluster-resource-manager-cluster-description.md
Medium Priority View Details →
Scanned: 2026-01-30 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides configuration examples for both WindowsServer (ClusterManifest.xml) and generic VM nodes (ClusterConfig.json), but code samples for service creation and updates are shown only in C# and PowerShell, with no Linux CLI or Bash examples. The XML configuration is labeled for WindowsServer, and PowerShell is used exclusively for command-line operations, suggesting a Windows-first approach. There is no explicit mention of Linux Service Fabric clusters or parity for Linux-based management tools.
Recommendations
  • Add equivalent Linux/Bash/CLI examples for service creation and updates (e.g., using Service Fabric CLI or REST API).
  • Clarify whether ClusterManifest.xml configuration is applicable to Linux clusters, or provide a Linux-specific configuration example if available.
  • Explicitly mention Linux support for standalone clusters and provide links to Linux-specific Service Fabric documentation.
  • Include notes on differences (if any) in node property and capacity configuration for Linux clusters.
Scanned: 2026-01-30 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides code examples for configuring auto scaling in Azure Service Fabric using C#, application manifest (XML), and PowerShell. The PowerShell examples are Windows-specific, and there are no equivalent CLI or shell script examples for Linux/macOS users. Additionally, the use of PowerShell cmdlets and .NET types in scripting sections assumes a Windows environment, which may create friction for Linux users. While the text notes that resource monitoring is supported for containerized applications on Linux, the practical guidance and automation examples are Windows-centric.
Recommendations
  • Add equivalent examples using Azure CLI or bash scripts for Linux/macOS users where PowerShell is used.
  • Clarify in each scripting section whether the example is Windows-only, and provide Linux alternatives if available.
  • Document any limitations or differences in auto scaling configuration and management between Windows and Linux clusters.
  • Where .NET APIs are shown, mention cross-platform compatibility if applicable, or provide Python/REST API examples where possible.
Scanned: 2026-01-30 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 examples for creating and updating Service Fabric services with move cost, but does not offer equivalent Linux/macOS CLI (such as Azure CLI or SFCTL) or bash examples. PowerShell is a Windows-centric tool, and its exclusive use here creates friction for Linux/macOS users. The documentation also lacks mention of Linux-native tools or workflows for these operations.
Recommendations
  • Add equivalent examples using Azure CLI (az servicefabric) or SFCTL (Service Fabric CLI), which are cross-platform and commonly used on Linux/macOS.
  • Explicitly mention how Linux/macOS users can perform these tasks, including installation and usage of SFCTL or Azure CLI.
  • If PowerShell Core (pwsh) is supported cross-platform for these commands, clarify compatibility and provide usage notes.
  • Consider ordering examples so that cross-platform tools are shown first or alongside PowerShell.
Service Fabric Manage Azure Service Fabric app load using metrics ...ric/service-fabric-cluster-resource-manager-metrics.md
Medium Priority View Details →
Scanned: 2026-01-30 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 samples in C# and PowerShell, with PowerShell being a Windows-centric tool. There are no CLI or Bash examples for Linux/macOS users, nor is there mention of cross-platform equivalents (e.g., Azure CLI, REST API, or Bash scripting). PowerShell examples are presented as the only command-line option, which may create friction for users managing Service Fabric clusters from Linux or macOS environments.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, especially for service creation and metric configuration.
  • Explicitly mention whether the PowerShell commands are supported on PowerShell Core (cross-platform) or only on Windows PowerShell.
  • Provide REST API examples for metric management tasks, as these are platform-agnostic.
  • Include Bash script snippets or instructions for Linux/macOS users where relevant.
  • Clarify any platform-specific limitations in a dedicated section, so users know if certain features are Windows-only.
Scanned: 2026-01-30 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 Application Manifest (XML/JSON), PowerShell, and C# APIs. PowerShell examples are prominent and presented before C# API examples, with no mention of Linux/macOS CLI equivalents (such as Azure CLI, REST API, or cross-platform Service Fabric CLI). There are no Linux-specific instructions or parity for command-line operations, which may create friction for non-Windows users managing Service Fabric clusters.
Recommendations
  • Add equivalent examples using Azure CLI or Service Fabric CLI (sfctl), which are cross-platform and usable on Linux/macOS.
  • Explicitly mention REST API options for configuration where possible.
  • Clarify which operations require Windows-only tooling (e.g., PowerShell) and provide alternatives or workarounds for Linux/macOS users.
  • Reorder examples so that cross-platform methods (JSON, CLI, REST) are presented before or alongside Windows-specific tools like PowerShell.
Service Fabric Upgrade an Azure Service Fabric standalone cluster ...ce-fabric/service-fabric-cluster-upgrade-standalone.md
Medium Priority View Details →
Scanned: 2026-01-30 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page for upgrading an Azure Service Fabric standalone cluster exhibits a moderate Windows bias. Key upgrade and configuration instructions link to Windows Server-specific documentation (e.g., service-fabric-cluster-upgrade-windows-server.md, service-fabric-cluster-config-upgrade-windows-server.md), and the patch orchestration application is described only for Windows. There are no explicit Linux examples or references to Linux-specific upgrade/configuration procedures, nor is there mention of Linux equivalents for patch orchestration or cluster management.
Recommendations
  • Add explicit guidance or links for upgrading and configuring Service Fabric standalone clusters running on Linux, if supported.
  • Include Linux-specific examples and instructions alongside Windows examples, especially for cluster upgrades and configuration changes.
  • Clarify whether features like the Patch Orchestration Application are available for Linux clusters, and provide alternatives or workarounds if not.
  • Ensure that references to configuration files, tools, and commands are applicable to both Windows and Linux environments, or note platform limitations.
Service Fabric Azure Service Fabric application resource model ...ervice-fabric/service-fabric-concept-resource-model.md
Medium Priority View Details →
Scanned: 2026-01-30 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 command-line deployment and resource management examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) with no mention of Azure CLI equivalents. The application packaging workflow is described using Visual Studio, a Windows-centric tool, and screenshots reinforce this. There are no Linux/macOS-specific instructions or examples, and the PowerShell workflow is presented as the default path for deployment and deletion.
Recommendations
  • Add Azure CLI examples for deployment, resource retrieval, and deletion alongside PowerShell examples.
  • Include instructions for packaging Service Fabric applications using cross-platform tools (e.g., dotnet CLI, SF SDK on Linux/macOS).
  • Provide guidance for performing the workflow on Linux/macOS, including alternative tools and commands.
  • Present both Windows and Linux/macOS workflows in parallel or clarify which steps are platform-specific.
Service Fabric Secure an Azure Service Fabric cluster ...cles/service-fabric/service-fabric-cluster-security.md
Medium Priority View Details →
Scanned: 2026-01-30 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation frequently references standalone Windows Server clusters and provides explicit links and instructions for securing them, while omitting equivalent guidance for standalone Linux clusters. Windows-specific security mechanisms (Windows security/Kerberos) are described in detail, but there is no mention of Linux authentication options or links to Linux-specific setup guides. Certificate-based security is presented as cross-platform, but examples and walkthroughs are only given for Azure and Windows clusters, not Linux.
Recommendations
  • Add explicit instructions and links for securing standalone Linux Service Fabric clusters, including certificate setup and any Linux-specific considerations.
  • If Linux clusters support authentication mechanisms other than certificates, document those options and provide setup guidance.
  • When listing security options, avoid presenting Windows options first or exclusively; ensure Linux parity in examples and references.
  • Clarify which security features and recommendations apply equally to Linux and Windows clusters, and note any differences.
Service Fabric Upgrading Azure Service Fabric clusters ...icles/service-fabric/service-fabric-cluster-upgrade.md
Medium Priority View Details →
Scanned: 2026-01-30 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page provides upgrade guidance for Azure Service Fabric clusters and generally maintains platform neutrality. However, in sections about managing certificates, opening application ports, and other cluster updates, PowerShell is mentioned before Azure CLI, and references to Windows-specific tools (such as Patch Orchestration Application for Windows OS patching) are present. The link for OS patching is explicitly Windows-focused, and there is no mention of Linux OS image upgrade options or parity. Examples and instructions for Linux environments (such as Bash, Linux-specific tools, or Linux node pools) are missing or not referenced, which may create friction for Linux users.
Recommendations
  • Include explicit examples for Linux users (e.g., Bash/Azure CLI commands) alongside PowerShell instructions.
  • Clarify whether Patch Orchestration Application or OS image upgrade guidance is available for Linux-based Service Fabric clusters, and provide links if so.
  • When listing management options (e.g., certificates, ports), mention Azure CLI and Bash scripts before or alongside PowerShell, and provide example commands for both.
  • If certain features are Windows-only (such as Patch Orchestration Application), clearly state this and provide Linux alternatives or note the lack thereof.
Service Fabric Scalability of Service Fabric services .../service-fabric/service-fabric-concepts-scalability.md
Medium Priority View Details →
Scanned: 2026-01-30 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides code examples for scaling Service Fabric services using C# and PowerShell, but does not include equivalent Linux CLI (e.g., Bash, Azure CLI, or sfctl) examples. PowerShell is a Windows-centric tool, and its exclusive use for command-line examples creates friction for Linux/macOS users. Additionally, the documentation references Windows-specific implementation details (e.g., kernel driver for logging) before describing Linux differences, but does not provide Linux-first or parity in operational guidance.
Recommendations
  • Add equivalent Linux command-line examples using sfctl or Azure CLI where PowerShell examples are provided.
  • Clearly indicate when a command or tool is Windows-only, and provide Linux/macOS alternatives where possible.
  • Where implementation differences are discussed, provide actionable guidance for both platforms (e.g., how to monitor or manage logs on Linux).
  • Consider including a table or section summarizing platform-specific commands and behaviors for common scaling operations.
Service Fabric Overview of Azure and standalone Service Fabric clusters ...icles/service-fabric/service-fabric-deploy-anywhere.md
Medium Priority View Details →
Scanned: 2026-01-30 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation discusses both Windows Server and Linux as platforms for Service Fabric clusters, but it notes that standalone clusters are not available on Linux. The explanations and benefits sections do not provide Linux-specific examples or guidance, and the mention of standalone clusters is implicitly Windows-focused due to the lack of Linux support. The page does not provide parity in examples or operational guidance for Linux users.
Recommendations
  • Explicitly clarify the limitations for Linux users regarding standalone clusters, including a direct statement about the lack of support and possible alternatives.
  • Provide links or references to documentation for deploying Service Fabric clusters on Linux within Azure, if available.
  • Add a comparison table summarizing feature differences between Windows and Linux clusters, with clear guidance for Linux users.
  • Ensure that next steps or related links include Linux-relevant documentation where applicable.
Service Fabric Learn more about Azure Service Fabric ...icles/service-fabric/service-fabric-content-roadmap.md
Medium Priority View Details →
Scanned: 2026-01-30 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 (e.g., PowerShell, Visual Studio) are mentioned before or more prominently than Linux equivalents, and some examples (such as standalone cluster creation and scaling) are Windows-only. The documentation often refers to Windows services and executables (FabricHost.exe, etc.) without clarifying Linux equivalents or differences. Linux support is acknowledged, but Linux-specific instructions, examples, and tooling are less visible or missing in key lifecycle and management sections.
Recommendations
  • Ensure Linux equivalents are mentioned alongside Windows tools (e.g., highlight sfctl CLI and bash scripting where PowerShell is referenced).
  • Provide explicit Linux examples for cluster creation, scaling, and management, or clearly state limitations where Linux support is not available.
  • When describing node services and executables, clarify differences between Windows and Linux implementations.
  • Balance the order of presentation so Linux options are not consistently listed after Windows ones.
  • Add links to Linux-specific quickstarts, tutorials, and troubleshooting guides where available.
Service Fabric Health monitoring in Service Fabric ...s/service-fabric/service-fabric-health-introduction.md
Medium Priority View Details →
Scanned: 2026-01-30 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 health reporting and querying in Service Fabric, but does not offer equivalent examples for Linux/macOS environments (such as Bash, CLI, or REST). The only concrete example is Windows PowerShell, and Windows-specific tools (PowerShell cmdlets) are mentioned before REST or other cross-platform options. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer platform-agnostic approaches.
Recommendations
  • Add equivalent examples using Azure CLI, Bash, or REST API for health reporting and querying.
  • Explicitly mention cross-platform tools and workflows before or alongside Windows-specific ones.
  • Clarify which tools are available on Linux/macOS and provide links or instructions for their use.
  • Where PowerShell is used, note its availability on Linux/macOS or suggest alternatives if not supported.
Service Fabric Azure Service Fabric DNS service ...n/articles/service-fabric/service-fabric-dnsservice.md
Medium Priority View Details →
Scanned: 2026-01-30 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page for Azure Service Fabric DNS service exhibits several Windows-centric biases. PowerShell is the only CLI example provided for setting DNS names, with no Linux CLI (e.g., Bash, Azure CLI) alternatives. The ApplicationManifest.xml example assumes Visual Studio, a Windows tool, and does not mention Linux development workflows. The limitations section clearly states that Linux support is restricted and that DNS service cannot be enabled via the Azure portal for Linux clusters, but the documentation does not offer Linux-specific guidance or parity in examples. Windows methods and tools are presented first and in greater detail.
Recommendations
  • Add Linux/Bash/Azure CLI examples for service creation and DNS name assignment.
  • Clarify Linux development workflows for ApplicationManifest.xml editing (e.g., using VS Code, nano, or other editors).
  • Explicitly document how Linux users can enable DNS service (e.g., via ARM templates or REST API), since portal support is missing.
  • Where PowerShell is shown, provide equivalent commands for Linux environments (e.g., Azure CLI, REST API calls).
  • Add a section summarizing the differences and workarounds for Linux users, including limitations and alternative approaches.
Service Fabric Package an existing executable to Azure Service Fabric ...abric/service-fabric-guest-executables-introduction.md
Medium Priority View Details →
Scanned: 2026-01-30 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a mild Windows bias. The only explicit file path given for the Service Fabric SDK schema is a Windows path (C:\Program Files\Microsoft SDKs\Service Fabric\schemas\ServiceFabricServiceModel.xsd), and there is no mention of Linux/macOS equivalents or installation locations. The examples and directory structures use Windows-style naming (e.g., .exe files), and Visual Studio is referenced as a primary tool for packaging and deploying, which is predominantly a Windows application. There are no Linux/macOS-specific instructions or examples, nor is there guidance for cross-platform tooling.
Recommendations
  • Include Linux/macOS installation paths for Service Fabric SDK schemas, or clarify if the SDK is Windows-only.
  • Provide examples or notes for packaging non-Windows executables (e.g., .sh, ELF binaries) and clarify cross-platform support.
  • Mention cross-platform alternatives to Visual Studio, such as Visual Studio Code or command-line tools available on Linux/macOS.
  • Add explicit guidance for Linux/macOS users where relevant, or clarify platform limitations if Service Fabric guest executables are Windows-only.
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-01-30 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation is generally OS-neutral in its technical explanations, but the only concrete example of deployment/removal references PowerShell, and the 'Next steps' section links to a PowerShell-specific guide for deploying/removing applications. No Linux or cross-platform CLI examples or links are provided, and PowerShell is mentioned before any Linux equivalent tools.
Recommendations
  • Add references or links to cross-platform deployment/removal guides, such as using Azure CLI or Service Fabric CLI (sfctl), alongside or instead of PowerShell.
  • Where possible, provide examples or notes for both Windows (PowerShell) and Linux/macOS (Bash, CLI) users.
  • Clarify in the 'Next steps' section that PowerShell is one option, and mention alternatives for Linux/macOS users.
Service Fabric Azure Service Fabric hosting model ...rticles/service-fabric/service-fabric-hosting-model.md
Medium Priority View Details →
Scanned: 2026-01-30 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 the Azure Service Fabric hosting model provides conceptual information applicable to all platforms, but operational examples and tooling references are heavily Windows/PowerShell-centric. The only concrete command-line example is a PowerShell cmdlet, and all operational instructions (creating services, querying service state, reporting health, restarting code packages) reference PowerShell modules without mentioning Linux equivalents or cross-platform CLI options. There are no bash, Azure CLI, or Linux-native examples, and PowerShell is presented as the default/primary method for management tasks.
Recommendations
  • Add equivalent examples using Azure CLI (az service-fabric) or REST API calls for service creation and management, especially for Linux/macOS users.
  • Explicitly mention cross-platform management options and clarify which tools are supported on Linux/macOS clusters.
  • Where PowerShell is referenced, provide a note or link to Linux-compatible alternatives, or clarify if PowerShell Core is supported on Linux for Service Fabric management.
  • Consider including bash or shell script examples for common tasks.
  • Update references to management tasks to include both Windows and Linux tooling, or clarify platform limitations if any exist.
Service Fabric Overview of Azure Service Fabric ...ain/articles/service-fabric/service-fabric-overview.md
Medium Priority View Details →
Scanned: 2026-01-30 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation mentions both Windows and Linux support for Service Fabric, but Windows development tools (Visual Studio, PowerShell) are listed first and in more detail than Linux equivalents. The Linux section is shorter, and there are no direct Linux command-line or deployment examples. The quickstart link points to a .NET/Windows-centric tutorial, with no immediate parity for Linux users.
Recommendations
  • Present Windows and Linux development options with equal prominence and detail.
  • Include direct Linux command-line examples (e.g., using Bash, CLI) alongside PowerShell examples.
  • Add quickstart links for Linux development (e.g., Java SDK, .NET Core on Linux) in the 'Next steps' section.
  • Clarify tooling parity (e.g., Visual Studio vs. Eclipse/Yeoman) and provide links to Linux-specific guides.
  • Ensure that deployment and management instructions cover both Windows and Linux workflows.
Service Fabric Azure Service Fabric image store connection string ...fabric/service-fabric-image-store-connection-string.md
Medium Priority View Details →
Scanned: 2026-01-30 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 the Service Fabric cluster manifest and links to PowerShell-based deployment guides. It mentions Visual Studio (a Windows-centric tool) for publishing, and PowerShell is listed first among programmatic options, with no explicit Linux/macOS CLI or Bash examples. This creates a subtle Windows-first bias, though the underlying concepts are cross-platform.
Recommendations
  • Include equivalent Linux/macOS examples using Azure CLI or Bash where applicable.
  • Reference cross-platform tools (e.g., Azure CLI, Service Fabric CLI) alongside PowerShell and Visual Studio.
  • Clarify that PowerShell and Visual Studio are examples, and provide links or instructions for non-Windows environments.
  • Add guidance for retrieving the cluster manifest and deploying applications from Linux/macOS.
Service Fabric Manage apps for multiple environments ...e-fabric-manage-multiple-environment-app-configuration.md
Medium Priority View Details →
Scanned: 2026-01-30 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 detail for application parameterization, while Linux-native workflows (e.g., sfctl, shell scripting) are referenced but not elaborated. There is a lack of concrete Linux/macOS examples, such as shell commands or parameter file usage outside Visual Studio, which may create friction for non-Windows users.
Recommendations
  • Provide explicit Linux/macOS examples for parameterization, such as using sfctl with install.sh and sample shell commands.
  • Clarify how parameter files can be used in non-Visual Studio workflows (e.g., with Azure DevOps on Linux agents).
  • Balance the order of examples so that Linux/macOS tools (sfctl, shell scripts) are presented alongside or before Windows tools.
  • Include sample scripts or command lines for Linux/macOS environments where appropriate.
Service Fabric Azure Service Fabric container application manifest examples ...abric/service-fabric-manifest-example-container-app.md
Medium Priority View Details →
Scanned: 2026-01-30 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 a notable Windows bias. The manifest examples and explanations are based on the 'Windows Server 2016 Container Sample', with explicit references to Windows tools (e.g., 'winver' for OS build detection) and Windows file paths (e.g., 'c:\VolumeTest\Data'). There is no mention of Linux-specific patterns, tools, or examples, and Linux container scenarios are not illustrated, even though Service Fabric supports both Windows and Linux containers. The certificate handling section does mention both PFX (Windows) and PEM (Linux) formats, but practical Linux usage details are missing.
Recommendations
  • Provide parallel Linux-based manifest examples, including Linux file paths and volume mounts (e.g., '/mnt/data').
  • Reference Linux tools for OS build/version detection (e.g., 'cat /etc/os-release') alongside 'winver'.
  • Clarify which manifest settings and features are cross-platform and which are Windows-only.
  • Include links or references to Linux container samples in addition to the Windows sample.
  • Explicitly document any differences in behavior or configuration between Windows and Linux containers in Service Fabric.
Service Fabric Networking patterns for Azure Service Fabric ...s/service-fabric/service-fabric-patterns-networking.md
Medium Priority View Details →
Scanned: 2026-01-30 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 command-line instructions, which are specific to Windows. There are no equivalent examples for Linux/macOS users (e.g., Azure CLI or Bash). Additionally, Windows tools and patterns (such as RDP and Windows-style paths) are referenced without mention of Linux alternatives. This creates friction for users on non-Windows platforms, though the underlying Azure features are cross-platform.
Recommendations
  • Add Azure CLI (az) command examples alongside PowerShell for all deployment steps.
  • Include Bash shell examples for template deployments.
  • Mention SSH as an alternative to RDP for accessing VMs, and provide relevant instructions.
  • Use platform-neutral file paths in examples, or clarify differences for Linux/macOS users.
  • Explicitly state that the steps can be performed from Linux/macOS using Azure CLI, and link to relevant documentation.
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-01-30 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 'Replica soft delete for enhanced data protection in Service Fabric' demonstrates a bias towards Windows environments. All command-line/API examples reference PowerShell cmdlets (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica, Get-ServiceFabricReplica), with no mention of Linux equivalents, CLI commands, or REST API usage. The documentation assumes familiarity with Windows tooling and does not provide guidance for Linux/macOS users, even though Service Fabric supports Linux clusters.
Recommendations
  • Include equivalent examples using Service Fabric CLI (sfctl) or REST APIs where available, especially for operations like removing, restoring, and querying replicas.
  • Explicitly state if certain APIs or features are only available via PowerShell and provide alternative guidance for Linux users if possible.
  • Add a section or callout clarifying cross-platform support and any limitations for Linux/macOS clusters.
  • Provide links to Linux/macOS-specific documentation or tools for managing Service Fabric clusters.