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 1076-1100 of 2475 flagged pages
Service Fabric Azure Service Fabric networking best practices ...ice-fabric/service-fabric-best-practices-networking.md
Medium Priority View Details →
Scanned: 2026-02-21 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page presents several examples and explanations that prioritize Windows tools and patterns, such as referencing PowerShell APIs, Windows-specific port usage, and ARM templates for Windows clusters. Windows-related scenarios (e.g., patching, DevOps tasks) are described in detail, while Linux equivalents are either briefly mentioned or omitted. PowerShell is referenced as the primary client API example, and some sample templates are Windows-focused. Linux-specific guidance is less prominent and sometimes missing.
Recommendations
  • Provide Linux CLI (az, bash) examples alongside PowerShell for cluster management and networking tasks.
  • Include ARM template samples for Linux clusters with NSG rules, not just Windows.
  • Clarify which port ranges and rules apply to Linux clusters, and which do not (e.g., ephemeral ports).
  • Expand on Linux-specific operational tasks (e.g., patching, DevOps) and reference relevant tools (e.g., Ansible, Bash scripts).
  • Ensure parity in application networking examples for Linux containers and workloads.
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-21 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 most security best practices, including certificate creation and secret encryption. However, Windows-specific tools (PowerShell, Windows Defender, Azure DSC) are often mentioned first or exclusively, and Windows examples precede Linux equivalents in several sections. Windows Defender and DSC are discussed without Linux alternatives, and Windows-centric terminology (certificate store, PowerShell commands) is prominent. Linux examples are present but sometimes secondary.
Recommendations
  • Ensure Linux examples are presented alongside Windows examples, not after them.
  • Where Windows-specific tools (e.g., Windows Defender, DSC) are discussed, explicitly mention Linux alternatives (e.g., common Linux antivirus solutions, configuration management tools like Ansible or Chef).
  • Use neutral terminology where possible (e.g., 'certificate store' vs. 'Linux certificate location').
  • For sections that are Windows-only, clarify that Linux users should refer to their own platform-specific tools.
  • Consider adding links to Linux-focused security baseline guidance and best practices.
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-21 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page provides a comprehensive reference for Service Fabric cluster settings, but there is evidence of Windows bias. Windows terminology (e.g., 'MY' certificate store, 'LocalMachine', NTLM authentication, Windows Defender Firewall) is used throughout, and Windows-specific settings are often mentioned first or exclusively. Some settings reference Windows tools and APIs (e.g., CertGetCertificateChain, ETW traces, Windows Firewall). Linux equivalents are sometimes present, but not always explained or given equal prominence. The guidance for standalone clusters links only to a Windows Server page, and there are no Linux-specific configuration examples or references for standalone clusters.
Recommendations
  • Add explicit Linux configuration examples and references, especially for standalone clusters.
  • Where Windows-specific terminology is used (e.g., certificate store names), clarify Linux equivalents or alternatives.
  • Ensure Linux-specific settings (such as X509Folder, LinuxExternalExecutablePath, EnforceLinuxMinTlsVersion) are explained and given equal prominence.
  • Provide links to Linux documentation for standalone Service Fabric clusters, if available.
  • Review guidance and descriptions to ensure Linux/macOS users can follow all steps without ambiguity or missing information.
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-21 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation provides examples and configuration snippets for both Windows (ClusterManifest.xml with <WindowsServer>) and cross-platform/standalone (ClusterConfig.json) deployments. However, Windows-specific configuration (ClusterManifest.xml with <WindowsServer>) is presented first and more prominently, and PowerShell examples are included for service creation and updates, while Linux-native equivalents (e.g., Bash, CLI) are absent. There is no explicit mention of Linux/macOS tools or patterns, and the documentation does not clarify Linux parity or differences for standalone Service Fabric clusters.
Recommendations
  • Include explicit Linux/macOS deployment examples, such as ClusterManifest.xml with <Linux> infrastructure or reference to Linux node setup.
  • Add Bash or Azure CLI equivalents for PowerShell commands, or clarify if PowerShell is required/cross-platform.
  • Document any differences or limitations for Linux-based Service Fabric clusters, if applicable.
  • Present cross-platform configuration examples (ClusterConfig.json) before or alongside Windows-specific examples to avoid Windows-first bias.
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-21 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 Service Fabric partition health, using Windows-style paths and commands (e.g., 'PS C:\Users\User > Get-ServiceFabricPartitionHealth'). No equivalent Linux or cross-platform example is given, and the example is presented early in the article. The rest of the documentation is platform-neutral, focusing on concepts and configuration files, but the only concrete example is Windows-centric.
Recommendations
  • Add equivalent Linux/macOS CLI examples (e.g., using Azure CLI, sfctl, or Service Fabric REST API) alongside PowerShell examples.
  • When showing command-line usage, include both Windows (PowerShell) and Linux (bash) variants, or note cross-platform tools.
  • Clarify if the PowerShell example is Windows-only and provide guidance for Linux users on how to achieve the same task.
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-21 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page provides general information about Azure Service Fabric node types and virtual machine scale sets, but exhibits Windows bias in several areas. Examples and guidance reference Windows paths (e.g., 'D:\SvcFab'), and the 'Next steps' section links to PowerShell scripts for Windows-specific tasks (changing RDP port range, admin username/password), without Linux equivalents or parity. The documentation mentions both 'ServiceFabricLinuxNode' and 'ServiceFabricNode' in the extension snippet, but practical examples and tooling focus on Windows scenarios.
Recommendations
  • Provide Linux-specific examples for connecting to cluster nodes, such as using SSH instead of RDP.
  • Include guidance or scripts for changing admin credentials and port ranges on Linux clusters.
  • Show Linux file paths (e.g., '/var/lib/svcfab') alongside Windows paths in configuration examples.
  • Balance PowerShell references with Bash/CLI equivalents for common cluster management tasks.
  • Clarify which steps are OS-specific and provide links to Linux documentation where appropriate.
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-21 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 code examples in C# and PowerShell only, with no mention of Linux-native tools or cross-platform CLI alternatives. All command-line examples use PowerShell cmdlets, which are primarily associated with Windows environments, and there is no guidance for Linux/macOS users on how to perform equivalent operations.
Recommendations
  • Add Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention whether the PowerShell cmdlets are available and supported on Linux/macOS (e.g., via PowerShell Core), or provide alternatives if not.
  • Include a note or section for Linux/macOS users, clarifying how to configure placement policies using supported tools on those platforms.
  • If REST API or ARM template options exist for configuring these policies, provide examples or references.
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-21 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 policies in Azure Service Fabric using application manifests, C# APIs, and PowerShell. However, all CLI examples are exclusively PowerShell-based, with no equivalent Bash or Linux CLI examples. The PowerShell examples are presented alongside C# and manifest examples, but there is no mention of Linux tooling or cross-platform command-line approaches. This creates friction for Linux/macOS users, especially since Service Fabric supports Linux containers and clusters.
Recommendations
  • Add Bash or Azure CLI examples for configuring scaling policies, especially for Linux clusters.
  • Explicitly state which PowerShell commands are cross-platform (if any), or provide alternatives for Linux users.
  • Mention Linux-specific considerations or limitations where relevant, such as differences in resource monitoring or activation models.
  • Include links or references to Linux administration guides for Service Fabric where 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-21 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 metrics in Azure Service Fabric primarily in C# and PowerShell. PowerShell is a Windows-centric tool, and no equivalent Linux/macOS CLI (e.g., Azure CLI, Bash, or REST API) examples are provided. The PowerShell examples are presented alongside C# code, but there is no mention of cross-platform alternatives or guidance for Linux/macOS users. This creates friction for non-Windows 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.
  • Include REST API sample calls for metric configuration and reporting, which are platform-agnostic.
  • Mention Bash scripting or other Linux-native approaches where appropriate.
  • Clarify which operations are possible via Azure Portal or other graphical tools.
  • Explicitly note PowerShell's platform limitations and provide links to Linux/macOS alternatives.
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-21 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 offer equivalent CLI or scripting examples for Linux/macOS users. The PowerShell API is referenced exclusively, and there is no mention of cross-platform tools (such as Azure CLI or REST API) for these operations. This creates friction for Linux/macOS administrators who may not have access to PowerShell or prefer native tools.
Recommendations
  • Add Azure CLI or REST API examples for configuring service sensitivity and maximum load, if supported.
  • Clarify whether PowerShell commands can be run cross-platform (e.g., via PowerShell Core) or if they are Windows-only.
  • If PowerShell is the only supported scripting interface, explicitly state this limitation and suggest alternatives for Linux/macOS users.
  • Consider including sample scripts or instructions for editing cluster manifests and application manifests using standard text editors or automation tools available on Linux/macOS.
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-21 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 shows a 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, commands, or guidance, and Windows tools are mentioned exclusively for critical cluster operations.
Recommendations
  • Add equivalent Linux instructions for querying and updating cluster configuration, such as using Service Fabric CLI (sfctl) or REST APIs.
  • Provide examples for scaling standalone clusters on Linux, including relevant commands and configuration steps.
  • Clarify if standalone clusters are supported on Linux, and if not, explicitly state Windows-only support to avoid confusion.
  • If Linux is supported, ensure parity in documentation for node management and configuration upgrades.
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-21 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 procedures and tools (e.g., Patch Orchestration Application for Windows) and links to upgrade/configuration guides with 'windows-server' in their URLs. There are no explicit Linux examples, and Linux upgrade/configuration paths are not mentioned or linked, creating friction for Linux users managing Service Fabric standalone clusters.
Recommendations
  • Add explicit guidance and links for Linux-based Service Fabric standalone clusters, including upgrade and configuration procedures.
  • Ensure that references to upgrade/configuration guides are platform-neutral or provide separate links for Windows and Linux.
  • Mention whether features like Patch Orchestration Application are available for Linux, and if not, suggest alternatives or clarify limitations.
  • Include Linux-specific examples and instructions where applicable, especially for cluster configuration and upgrade steps.
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-21 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 examples for managing node tags and service requirements, but does not offer equivalent CLI or scripting examples for Linux/macOS users (e.g., Bash, Azure CLI). PowerShell is a Windows-centric tool, and its exclusive use here creates friction for non-Windows users. There is no mention of Linux-native tools or cross-platform alternatives for these operations.
Recommendations
  • Add Azure CLI examples for managing node tags and service requirements, as Azure CLI is cross-platform.
  • If REST APIs are available for these operations, provide explicit curl or HTTP request examples for Linux/macOS users.
  • Mention whether PowerShell Core (pwsh) is supported on Linux/macOS for these commands, and clarify any limitations.
  • Consider including Bash or shell script examples if relevant.
  • Clearly indicate if certain operations are only possible via PowerShell, and provide guidance for Linux/macOS users.
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-21 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page for securing an Azure Service Fabric cluster demonstrates moderate Windows bias. Windows Server clusters and Windows security mechanisms (Kerberos, group Managed Service Accounts, Windows certificate services, MakeCert.exe) are referenced frequently and often before or instead of Linux equivalents. Standalone cluster security is discussed only for Windows, with no mention of Linux standalone clusters or their security setup. Certificate creation instructions and recommendations are Windows-centric, and Linux-specific guidance is largely absent.
Recommendations
  • Add explicit guidance for securing standalone Linux Service Fabric clusters, including certificate setup and client authentication.
  • Include Linux-focused examples and instructions for certificate creation (e.g., using OpenSSL instead of MakeCert.exe or Windows certificate services).
  • Clarify whether standalone Linux clusters are supported and, if so, provide links or sections for their security configuration.
  • Balance references to Windows tools with Linux equivalents, such as mentioning OpenSSL for certificate management.
  • Ensure recommendations and best practices are platform-neutral where possible, or clearly indicate platform-specific steps.
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-21 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 exhibits a moderate Windows bias. All deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) without any mention of Azure CLI equivalents or Bash scripting. Application packaging instructions rely on Visual Studio, a Windows-centric tool, and do not provide alternatives for Linux/macOS users. The workflow assumes familiarity with Windows tools and patterns, and Linux options are omitted entirely.
Recommendations
  • Add Azure CLI examples for deployment, upgrade, and deletion tasks alongside PowerShell examples.
  • Provide instructions for packaging Service Fabric applications using cross-platform tools (e.g., dotnet CLI, sfctl, or manual zip commands) instead of only Visual Studio.
  • Include guidance for Linux/macOS users, such as using Bash or cross-platform editors.
  • Clearly indicate when a step is Windows-only and offer Linux/macOS alternatives where possible.
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-21 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation generally avoids explicit Windows-only instructions, but there are subtle biases. In the 'Upgrading OS images for cluster nodes' section, the only linked guidance is for patching Windows operating systems, with no mention or link for Linux-based clusters. Additionally, the 'Patch Orchestration Application (POA)' is described as a solution for OS patching, but only in the context of Windows. Throughout the page, when mentioning tools for management (e.g., PowerShell/Azure CLI), PowerShell is listed first, which may suggest a Windows-first approach. There are no explicit Linux-specific examples or references, and Linux parity for OS image upgrades is not addressed.
Recommendations
  • Add a parallel section or link for upgrading or patching Linux-based Service Fabric cluster nodes, if supported.
  • When listing management tools (e.g., PowerShell/Azure CLI), alternate the order or clarify that both are supported equally.
  • Explicitly state if certain features (such as POA or OS patching) are Windows-only, and provide Linux alternatives or note if not applicable.
  • Include Linux-specific examples or references where appropriate, especially in sections discussing OS upgrades and management.
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-21 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page presents Windows/PowerShell examples and tools first and in more detail, with limited mention of Linux equivalents. PowerShell cmdlets are highlighted, and Visual Studio workflows (Windows-centric) are described, while Linux-native workflows (e.g., sfctl, Jenkins) are mentioned briefly or without example. There are no explicit Linux/macOS command examples or guidance.
Recommendations
  • Add explicit Linux/macOS command-line examples for common tasks, such as using sfctl and shell scripts.
  • Provide sample scripts or workflows for Linux environments, including how to use environment variables and parameter files.
  • Ensure Jenkins and other cross-platform CI/CD tools are given equal prominence and detailed examples.
  • Clarify which tools are cross-platform and which are Windows-only, to help users choose the right workflow.
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-21 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 and administrative patterns primarily using PowerShell, which is a Windows-centric tool. No equivalent Linux command-line examples (such as Bash, CLI, or REST API) are given. Windows tools and PowerShell cmdlets are mentioned first and exclusively, creating friction for Linux users who may not have access to PowerShell or prefer native Linux tooling. While the page does mention Linux in the 'Choosing a platform' section, it does not provide Linux-specific operational guidance or parity in examples.
Recommendations
  • Add equivalent Linux command-line examples using Bash, Azure CLI, or REST API for service creation, updates, and scaling operations.
  • Mention Linux-native tools and patterns alongside PowerShell, not just in the platform comparison section.
  • Clarify which operations can be performed on Linux clusters and provide links or references to Linux-specific documentation.
  • Consider reordering examples so that Windows and Linux approaches are presented together, or alternate which is shown first.
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-21 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-centric logging mechanisms (ETW/Windows Event logs, Windows Azure diagnostics agent) and does not mention Linux equivalents or provide Linux-specific guidance. Windows tools and patterns are discussed first and exclusively, with no examples or instructions for accessing Service Fabric events on Linux clusters.
Recommendations
  • Add information about how Service Fabric events are logged and accessed on Linux clusters, including supported logging mechanisms (e.g., stdout, syslog, Azure Monitor integration for Linux).
  • Provide Linux-specific examples or clarify any differences in event access/configuration between Windows and Linux clusters.
  • Mention any limitations or differences in event availability or tooling for Linux Service Fabric clusters.
  • Ensure parity in documentation by referencing both Windows and Linux approaches where applicable.
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-21 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, mentions Visual Studio and ApplicationManifest.xml (Windows-centric patterns), and does not offer Linux CLI or cross-platform alternatives. While the page acknowledges Linux support and its limitations, practical guidance and examples are heavily Windows-focused, creating friction for Linux users.
Recommendations
  • Add equivalent Linux CLI examples (e.g., Azure CLI, Bash scripts) for setting DNS names and managing Service Fabric services.
  • Clarify how Linux users can accomplish tasks that are shown with PowerShell or ApplicationManifest.xml, including any limitations or required tools.
  • Provide guidance for enabling DNS service on Linux clusters using ARM templates, including any Linux-specific considerations.
  • Mention and link to Linux-compatible editors and workflows for editing manifests, rather than only referencing Visual Studio.
  • Explicitly state which features or steps are Windows-only and offer alternatives or workarounds for Linux users where possible.
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-21 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page shows a mild Windows bias. It references the Service Fabric SDK schema location using a Windows file path and does not mention Linux equivalents or paths. The use of Visual Studio as a primary tool is also Windows-centric, though it does mention command-line utilities. There are no explicit Linux/macOS examples or instructions, and the documentation does not clarify cross-platform packaging steps.
Recommendations
  • Add information about the location of Service Fabric SDK schema files on Linux/macOS, or clarify if the SDK is only available on Windows.
  • Include explicit instructions or examples for packaging and deploying guest executables using cross-platform tools (e.g., Azure CLI, Service Fabric CLI) where possible.
  • Mention and link to Linux/macOS-compatible development environments or tools if supported.
  • Clarify in the introduction if certain steps or tools (like Visual Studio) are Windows-only, and provide alternatives for other platforms if available.
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-21 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 and references for managing Service Fabric services, with no equivalent Linux CLI or cross-platform examples. PowerShell is presented as the primary tooling for service creation and management, and REST API and .NET SDK are mentioned, but Linux-native tools (such as sfctl or Azure CLI) are not referenced. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer platform-agnostic tools.
Recommendations
  • Add examples using sfctl (Service Fabric CLI), which is cross-platform and commonly used on Linux/macOS.
  • Include Azure CLI examples where applicable for service creation and management.
  • Clarify that PowerShell examples are Windows-specific and provide alternative instructions for Linux/macOS users.
  • Reorder examples so that REST API or cross-platform CLI examples are shown before or alongside PowerShell.
  • Link to documentation for sfctl and Azure CLI usage with Service Fabric.
GitHub Create Pull Request
Service Fabric Azure Service Fabric image store connection string ...fabric/service-fabric-image-store-connection-string.md
Medium Priority View Details →
Scanned: 2026-02-21 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page references PowerShell as the primary example for interacting with Service Fabric clusters and retrieving the cluster manifest. It also links to a PowerShell-based deployment guide as the main 'Next steps'. While Service Fabric is cross-platform, the documentation prioritizes Windows/PowerShell tools and does not provide equivalent Linux/macOS CLI or scripting examples.
Recommendations
  • Add examples using Azure CLI or Service Fabric CLI (sfctl) for Linux/macOS users, especially for tasks like retrieving the cluster manifest and deploying/removing applications.
  • Include links to Linux/macOS-specific documentation or guides alongside PowerShell references.
  • Mention cross-platform tooling (e.g., sfctl, REST API) earlier in the documentation, not just as an afterthought.
  • Provide sample commands for both Windows (PowerShell) and Linux/macOS (bash/CLI) wherever possible.
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-21 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page for Azure Service Fabric container application manifest examples demonstrates a Windows bias. The manifest examples are explicitly based on a Windows Server 2016 container sample, and several instructions reference Windows-specific tools and patterns (e.g., using 'winver' to get the OS build version). There is no mention of Linux-based Service Fabric clusters, nor are there Linux-specific manifest examples or guidance. Some explanations (such as certificate handling) mention both Windows and Linux, but the overall focus and examples are Windows-centric.
Recommendations
  • Provide equivalent manifest examples based on Linux container samples, or clarify if Linux clusters are not supported for these scenarios.
  • When referencing OS build versions, include instructions for obtaining the build/version on Linux (e.g., 'cat /etc/os-release' or 'uname -r').
  • Add notes or sections highlighting any differences or limitations when deploying to Linux-based Service Fabric clusters.
  • Ensure that any referenced sample repositories include Linux examples if Linux is supported.
  • Explicitly state in the introduction if the guidance is only applicable to Windows clusters, to set user expectations.
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-21 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page provides Service Fabric application and service manifest examples. While the manifest XML itself is platform-neutral, there are subtle indications of Windows bias: Windows tools (e.g., PowerShell) are mentioned as the default for service creation, and batch scripts (.bat) are used in examples. Windows-specific accounts (e.g., NetworkService, Administrators) are referenced, and Windows terminology appears before Linux equivalents. No explicit Linux examples or guidance are provided.
Recommendations
  • Add Linux-specific examples, such as using shell scripts (.sh) for SetupEntryPoint, alongside batch (.bat) examples.
  • Mention Linux user/group equivalents when describing security principals (e.g., use 'root' or custom Linux users/groups).
  • Provide instructions or references for creating services using Linux tools (e.g., Azure CLI, Bash) in addition to PowerShell.
  • Clarify which features and manifest elements are supported on Linux Service Fabric clusters, and note any platform-specific limitations.
  • Include a section or links for Linux/macOS users, highlighting differences and best practices.
GitHub Create Pull Request
← Previous Page 44 of 99 Next →