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 1776-1800 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-08 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 Resource Manager templates, but PowerShell is presented as a separate section, and manual upgrade instructions are PowerShell-only. Windows-specific registry keys and template properties are discussed in detail, while Linux equivalents are not mentioned. The documentation references both Windows and Linux clusters, but operational examples and upgrade instructions are heavily Windows-oriented.
Recommendations
  • Add Linux-specific operational examples, such as Bash or shell commands for manual cluster upgrades.
  • Include information about disabling automatic updates on Linux VM scale sets (e.g., using cloud-init or relevant Linux configuration).
  • Provide parity for registry/configuration guidance for Linux hosts, or clarify when steps are Windows-only.
  • When showing PowerShell examples, also provide Bash/Linux equivalents where applicable.
  • Clarify which steps are Windows-specific and which are cross-platform.
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-08 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, but Windows-specific tools and examples (e.g., PowerShell, Windows Defender, Windows security baselines) are often presented first or exclusively. Windows-specific recommendations and tooling (PowerShell, Windows Defender, DSC) are prominent, while Linux equivalents are less detailed or referenced later. Some sections (e.g., Windows Defender, security baselines) are Windows-only, but this is acknowledged. Linux examples are present for certificate generation and secret encryption, but Windows examples are shown first.
Recommendations
  • Present Linux and Windows examples side-by-side or alternate their order to avoid Windows-first bias.
  • Expand Linux-specific guidance for security baselines and endpoint protection (e.g., recommend common Linux security tools or practices).
  • Where Windows tools (PowerShell, DSC, Defender) are mentioned, provide equivalent Linux tools or explicitly state if no direct equivalent exists.
  • Clarify when a section is Windows-only and provide links to Linux alternatives where relevant.
  • Ensure Linux guidance is as detailed as Windows guidance, especially for certificate management and secret encryption.
GitHub Create Pull Request
Service Fabric Change Azure Service Fabric cluster settings ...rvice-fabric/service-fabric-cluster-fabric-settings.md
Medium Priority View Details →
Scanned: 2026-02-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation provides a comprehensive reference for Service Fabric cluster settings, covering both Azure-hosted and standalone clusters. However, there is evidence of Windows bias: Windows terminology and tools (such as certificate store names like 'My', 'LocalMachine', and references to NTLM authentication) are used throughout, often without explicit Linux equivalents or clarifications. Windows-specific features (e.g., Windows Update, NTLM, log file paths) are mentioned more frequently and sometimes without clear Linux alternatives. In some places, Windows defaults are listed first or exclusively, even when Linux is supported.
Recommendations
  • Where certificate store names or NTLM authentication are referenced, clarify Linux equivalents or note Linux limitations.
  • Add explicit notes or columns indicating Linux-specific behaviors, defaults, or paths where they differ from Windows.
  • Where Windows-only features are mentioned (e.g., Windows Update, NTLM), clearly mark them as Windows-only and provide Linux alternatives or state if not applicable.
  • Ensure Linux terminology (e.g., certificate locations, user accounts, log paths) is included alongside Windows terminology.
  • Review parameter defaults and guidance for parity, ensuring Linux defaults are documented where they differ.
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-08 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 code examples for configuring Service Fabric placement policies using C# and PowerShell. All CLI examples use PowerShell, with no mention of Linux/macOS equivalents (such as Azure CLI or REST API). PowerShell is a Windows-centric tool, and its exclusive use creates friction for Linux/macOS users. Additionally, PowerShell examples are consistently shown alongside C# code, with no Linux-first or cross-platform alternatives.
Recommendations
  • Add Azure CLI examples for each placement policy configuration, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Mention REST API options for configuring placement policies, with example requests.
  • Clarify whether PowerShell examples are only applicable to Windows clusters, and provide guidance for Linux-based Service Fabric clusters.
  • Consider including Bash scripts or references to Service Fabric SDK tools available on Linux/macOS.
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-08 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 PowerShell and C# examples exclusively for managing Service Fabric Application Groups, without offering equivalent Linux/bash/CLI examples. It assumes the use of PowerShell cmdlets, which are native to Windows, and does not mention cross-platform tools or workflows. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer bash/CLI interfaces.
Recommendations
  • Add Azure CLI examples for all operations shown (application creation, updating, querying load, removing capacity).
  • Mention whether PowerShell cmdlets are available cross-platform (via PowerShell Core) or if there are limitations.
  • Provide bash or shell script equivalents, or reference REST API usage for Linux/macOS users.
  • Clarify platform requirements for Service Fabric management tools and link to cross-platform options if available.
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-08 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 a Windows-centric tool, and its exclusive use creates friction for Linux/macOS users. The documentation also presents PowerShell examples before C# code, reinforcing Windows-first patterns. No mention is made of Azure CLI, REST API, or bash scripting alternatives, which would be relevant for cross-platform parity.
Recommendations
  • Add Azure CLI or REST API examples for configuring and updating move cost, as these are cross-platform and commonly used on Linux/macOS.
  • Explicitly mention whether PowerShell examples are supported on Linux (via PowerShell Core), or clarify if they are Windows-only.
  • Consider providing bash or shell script equivalents where possible, or link to documentation covering Linux/macOS workflows.
  • Reorder examples so that cross-platform options (CLI, REST API) are presented before or alongside 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-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed examples for configuring auto scaling in Azure Service Fabric using application manifests, C# APIs, and PowerShell. However, all PowerShell examples are Windows-centric, and there are no equivalent Linux shell or CLI examples. The documentation does not mention or demonstrate Linux-native tools or commands for configuring auto scaling, despite Service Fabric supporting Linux containers. Additionally, PowerShell examples are presented alongside C# and manifest examples, but no Linux-first or cross-platform CLI guidance is given.
Recommendations
  • Add Azure CLI or Bash shell examples for configuring scaling policies, especially for Linux-based Service Fabric clusters.
  • Explicitly mention which steps or commands are cross-platform, and clarify any Windows-specific limitations.
  • Provide guidance or links for Linux users on how to perform equivalent operations (e.g., using REST APIs, Azure CLI, or SDKs on Linux/macOS).
  • Consider including a table or section summarizing cross-platform support and differences.
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-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation provides configuration examples for both Windows (ClusterManifest.xml) and cross-platform/standalone (ClusterConfig.json), but the Windows-specific XML example is consistently presented first and referenced more often. The only explicit platform mention is <WindowsServer> in the XML example, and PowerShell examples are included for service creation and updates, but no Linux shell or CLI equivalents are given. There is no explicit Linux/macOS example or guidance, and the Windows terminology (e.g., 'WindowsServer') is used without clarifying Linux support.
Recommendations
  • Present Linux/cross-platform examples (ClusterConfig.json) before or alongside Windows examples.
  • Clarify that Service Fabric standalone clusters can run on Linux, and provide explicit Linux configuration examples (e.g., referencing <Linux> infrastructure in ClusterManifest.xml if supported).
  • Add Azure CLI or Bash examples for service creation and updates, or reference relevant cross-platform tools.
  • Avoid using Windows terminology exclusively (such as <WindowsServer>) without mentioning Linux equivalents or applicability.
  • Include a short section or note about Linux/macOS support and any platform-specific differences.
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-08 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 app load using 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. Additionally, PowerShell examples are presented 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 platform-agnostic tools.
Recommendations
  • Add Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used.
  • Explicitly mention which tools are Windows-only and provide alternatives for Linux/macOS users.
  • Consider including Bash script examples or references to REST API usage for metric management.
  • Clarify any prerequisites or limitations for Linux/macOS users in the relevant sections.
  • Where possible, link to documentation on using Service Fabric tools on Linux clusters.
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-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides PowerShell examples for configuring service sensitivity and maximum load, but does not include equivalent Linux/macOS CLI examples (e.g., Bash, Azure CLI). PowerShell is presented as the primary scripting interface, which may create friction for Linux/macOS users. The C# API is platform-neutral, but operational examples (service creation/update) are Windows-centric.
Recommendations
  • Add Azure CLI or Bash script examples for service creation and updates, where possible.
  • Clarify whether PowerShell Core (cross-platform) is supported, or if only Windows PowerShell is valid.
  • Mention any Linux/macOS-compatible tooling for Service Fabric management.
  • If PowerShell is required, explicitly state its platform support and alternatives for Linux users.
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-08 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 Linux/bash/CLI 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 API being referenced earlier.
Recommendations
  • Add examples using Service Fabric CLI (sfctl), which is cross-platform and commonly used on Linux/macOS.
  • Include REST API request examples for adding/removing node tags and updating service tag requirements.
  • Explicitly mention which PowerShell commands are available on Linux (if any), or clarify if they are Windows-only.
  • Consider providing bash or shell script snippets for Linux users where applicable.
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-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page on scaling Azure Service Fabric standalone clusters demonstrates Windows bias by referencing PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) and linking to a Windows Server-specific guide for scaling standalone clusters. There are no Linux-specific examples, tools, or instructions, and the guidance assumes the use of Windows-based Service Fabric clusters and management tools.
Recommendations
  • Add equivalent Linux instructions and examples for scaling standalone Service Fabric clusters, including relevant CLI commands (e.g., sfctl) or scripts.
  • Clarify whether standalone Service Fabric clusters can be managed on Linux, and if so, provide parity in documentation for Linux environments.
  • Reference Linux-compatible tools and workflows alongside PowerShell examples, or explicitly state if only Windows is supported for standalone cluster management.
  • Update links and guidance to include Linux-specific scaling procedures if available.
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-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page for securing an Azure Service Fabric cluster presents security scenarios and technologies applicable to both Azure-hosted clusters and standalone Windows clusters. However, it repeatedly mentions standalone clusters as 'running on Windows' and provides links and guidance only for Windows Server clusters, with no equivalent instructions or links for standalone Linux clusters. Windows security (Kerberos) is discussed, but Linux authentication mechanisms are not mentioned. Certificate creation guidance references Windows Server certificate services and Windows tools, with no Linux-specific alternatives or examples. The concept of Linux clusters is acknowledged, but practical guidance is missing.
Recommendations
  • Add explicit guidance and links for securing standalone Linux Service Fabric clusters, including certificate setup and authentication options.
  • Provide Linux-specific examples for certificate creation and management (e.g., using OpenSSL or Linux CA tools).
  • Clarify which security scenarios and technologies are supported on Linux clusters, and highlight any differences.
  • Include references to Linux authentication mechanisms if applicable, or state their absence.
  • Ensure parity in example coverage and instructions for both Windows and Linux standalone clusters.
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-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page provides numerous PowerShell examples and references to Windows-specific tools (e.g., PowerShell cmdlets like Update-ServiceFabricService and New-ServiceFabricService) without equivalent Linux CLI or scripting examples. Windows tools and patterns are mentioned first and exclusively in code samples, creating friction for Linux users. The only explicit Linux mention is in the 'Choosing a platform' section, which discusses implementation differences, but does not provide Linux-specific operational guidance or examples.
Recommendations
  • Add equivalent Linux CLI examples (e.g., using sfctl or REST API) alongside PowerShell samples for all service management operations.
  • Explicitly mention Linux-compatible tools and workflows where PowerShell is referenced.
  • Where possible, provide code samples in Bash or cross-platform scripting languages.
  • Clarify any platform-specific limitations or differences in operational procedures.
  • Ensure Linux instructions are given equal prominence and not only in a dedicated section.
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-08 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 covers both Windows and Linux usage of Azure Service Fabric, but there is a notable Windows bias. Windows-specific tools (PowerShell, Visual Studio) and terminology (Windows service, FabricHost.exe) are mentioned first or exclusively in several sections. Examples and instructions often default to Windows, with Linux equivalents referenced later or not at all. Standalone clusters are only supported on Windows, and this is clearly stated. CLI and REST API options are mentioned, but PowerShell is often listed first. There are few explicit Linux command examples or Linux-focused workflows.
Recommendations
  • Provide Linux-specific examples and workflows alongside Windows instructions, especially for cluster management and health monitoring.
  • List CLI commands (sfctl) and REST API options before or equally with PowerShell, to improve parity for Linux/macOS users.
  • Clarify which tools and steps are cross-platform, and which are Windows-only, to reduce ambiguity.
  • Add links or references to Linux development environments and tools where appropriate.
  • Highlight Java programming model and Linux container support more prominently in relevant sections.
GitHub Create Pull Request
Service Fabric Upgrade an Azure Service Fabric standalone cluster ...ce-fabric/service-fabric-cluster-upgrade-standalone.md
Medium Priority View Details →
Scanned: 2026-02-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page references Windows-specific upgrade guides and tools (e.g., Patch Orchestration Application for Windows), and links to upgrade/configuration instructions with 'windows-server' in their URLs. There is no mention of Linux-specific upgrade instructions, examples, or tools, nor is Linux parity addressed. The page assumes Windows as the default platform for Service Fabric standalone clusters, which may create friction for Linux users.
Recommendations
  • Add explicit guidance or links for upgrading Service Fabric standalone clusters running on Linux, if supported.
  • Provide Linux-specific examples and configuration instructions alongside Windows instructions.
  • Clarify whether Service Fabric standalone clusters are Windows-only or if Linux is supported, to set expectations for users.
  • If Linux is not supported, state this clearly to avoid confusion.
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-08 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 notable Windows bias. All deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) without any Azure CLI or Bash equivalents. Application packaging instructions reference Visual Studio (a Windows-centric tool) and do not mention cross-platform alternatives. There are no Linux/macOS-specific instructions or examples, and Windows tools are presented first and exclusively.
Recommendations
  • Add Azure CLI examples for deployment and deletion alongside PowerShell examples.
  • Provide instructions for packaging applications using cross-platform tools (e.g., dotnet CLI, SF tooling, or manual zip commands) instead of only Visual Studio.
  • Include Bash or shell script examples for relevant steps, such as uploading to blob storage.
  • Explicitly note that all steps can be performed on Linux/macOS, and highlight any platform-specific differences.
  • Reorder examples so that cross-platform tools are presented before or alongside Windows tools.
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-08 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 instructions for accessing Service Fabric events on Linux clusters, nor are Linux-native tools or patterns mentioned. Windows tools and approaches are discussed first and exclusively, creating friction for Linux users.
Recommendations
  • Add explicit guidance 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 or patterns alongside Windows tools, such as using Azure Monitor with Linux clusters or exporting logs to Linux-friendly formats.
  • Clarify which features or approaches are Windows-only and provide Linux alternatives where available.
  • Include example workflows or commands for Linux environments, ensuring parity with Windows examples.
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-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. It references Windows file paths (e.g., Service Fabric SDK schema location), mentions Visual Studio as a packaging/deployment tool, and does not provide Linux/macOS equivalents or examples. There are no explicit PowerShell examples, but Windows tools and patterns are mentioned first or exclusively. The application package structure and manifest files are described generically, but the lack of Linux-specific guidance or examples may create friction for non-Windows users.
Recommendations
  • Add examples or instructions for packaging and deploying guest executables using Linux/macOS tools (e.g., CLI, VS Code, or cross-platform SDK usage).
  • Mention the location of schema files or SDK installation paths for Linux/macOS, if available.
  • Provide sample directory structures and file paths using both Windows and Linux conventions.
  • Clarify whether Visual Studio is required, or if cross-platform alternatives exist.
  • Link to Linux/macOS-specific Service Fabric documentation or guides, if available.
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-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation covers both Windows and Linux clusters, but there is a notable Windows-first bias. PowerShell examples are provided for setting DNS names, with no Linux CLI or scripting equivalents. Enabling DNS service via the Azure portal is only available for Windows clusters, and this is mentioned, but Linux users are left to infer their workflow from ARM template instructions. There are no Linux-specific command-line examples (e.g., Azure CLI, Bash, or REST API) for common tasks, and the ApplicationManifest.xml workflow is presented in a way that assumes Visual Studio, which is Windows-centric.
Recommendations
  • Add Azure CLI or Bash scripting examples for Linux users, especially for tasks currently only shown with PowerShell.
  • Explicitly document the Linux workflow for enabling DNS service (e.g., using ARM templates or REST API), including step-by-step instructions.
  • Where Visual Studio is referenced, mention cross-platform alternatives (e.g., VS Code, nano, vim) for editing manifest files.
  • When showing command-line examples, provide Linux equivalents alongside or immediately after Windows/PowerShell examples.
  • Clarify any limitations for Linux users up front, and provide links to relevant Linux-specific guidance where available.
GitHub Create Pull Request
Service Fabric Health monitoring in Service Fabric ...s/service-fabric/service-fabric-health-introduction.md
Medium Priority View Details →
Scanned: 2026-02-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides a PowerShell-only example for reporting and evaluating application health in Service Fabric, without offering equivalent Linux/macOS CLI or REST API examples. While Service Fabric is cross-platform, the exclusive use of PowerShell in the example creates friction for Linux/macOS users, who may not have access to PowerShell or prefer native tools.
Recommendations
  • Add equivalent examples using the Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • Include REST API examples for health reporting and querying, as these are platform-agnostic.
  • Mention PowerShell as one option, but ensure Linux/macOS-friendly alternatives are presented alongside or before it.
  • Clarify which tools are available on each platform, and link to relevant installation guides.
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-08 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 presents PowerShell as the primary CLI example for creating services, with no Linux CLI (such as Azure CLI or Bash) equivalents. Windows/PowerShell tools are referenced first and exclusively in command-line instructions, and there is no mention of Linux-specific management patterns or tools. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer cross-platform tools.
Recommendations
  • Add Azure CLI examples for service creation and management, especially for commands currently shown only in PowerShell.
  • Clarify which management tools are cross-platform and provide guidance for Linux/macOS users.
  • Mention or link to any available Bash scripts or REST API usage examples for Linux users.
  • Explicitly state PowerShell's cross-platform availability if relevant, or note any limitations for Linux/macOS users.
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-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page presents Service Fabric container application manifest examples based on Windows Server 2016 containers, with explicit references to Windows-specific tools (e.g., 'winver' for OS build detection) and Windows file paths (e.g., 'c:\VolumeTest\Data'). Linux equivalents are not mentioned, and Linux-specific guidance or examples are missing. While some sections acknowledge Linux (e.g., certificate handling), the overall focus and examples are Windows-centric, creating friction for Linux users.
Recommendations
  • Provide equivalent Linux-based manifest examples, including sample paths and OS build detection methods (e.g., 'cat /etc/os-release' or 'uname -r').
  • Clarify which features and manifest settings are cross-platform and which are Windows-only.
  • Add guidance for Linux container image tagging and compatibility, similar to the Windows 'ImageOverrides' section.
  • Include Linux file path examples alongside Windows paths in volume binding.
  • Reference Linux-specific documentation or Service Fabric samples where available.
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-08 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 extensive PowerShell-based deployment instructions and command examples, with no mention of Azure CLI, Bash, or Linux/macOS-compatible workflows. Windows tools and patterns (e.g., RDP, PowerShell, Windows file paths) are referenced exclusively or before any Linux alternatives. This creates friction for Linux/macOS users, who must translate instructions or find their own equivalents.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all deployment steps.
  • Include Bash shell command alternatives for template deployments.
  • Mention SSH as a remote access method in addition to RDP, especially for Linux-based clusters.
  • Use platform-neutral file paths or clarify when Windows paths are used.
  • Explicitly state that the instructions apply to both Windows and Linux clusters, or provide Linux-specific guidance where relevant.
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-08 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 generally platform-neutral in its conceptual explanations. However, there is evidence of Windows bias in the 'Next steps' section, which only links to PowerShell-based deployment instructions. Additionally, the only example for downloading a ServicePackage in advance references a PowerShell cmdlet, without mentioning Linux equivalents or cross-platform tools. No Linux-specific commands, tools, or guidance are provided, and PowerShell is implicitly presented as the default or primary method for operational tasks.
Recommendations
  • Add links to Linux/macOS deployment instructions using Service Fabric CLI (sfctl) or REST API, alongside PowerShell.
  • Provide examples for downloading ServicePackages in advance using cross-platform tools (e.g., sfctl, curl, or REST API), not just PowerShell.
  • Clarify which operational steps are platform-agnostic and which require platform-specific tooling.
  • In 'Next steps', include links to documentation for Linux/macOS users, not just PowerShell.
  • Where possible, mention both Windows and Linux tools in parallel, or note any platform limitations.
GitHub Create Pull Request
← Previous Page 72 of 99 Next →