Service Fabric

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

Bias Trend Over Time

Pages with Bias Issues

1305 issues found
Showing 226-250 of 1305 flagged pages
Service Fabric Health monitoring in Service Fabric ...s/service-fabric/service-fabric-health-introduction.md
Medium Priority View Details →
Scanned: 2026-02-18 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 mentioning or demonstrating equivalent Linux/macOS methods (such as REST API or CLI). The main example uses Windows-specific PowerShell cmdlets, which may create friction for Linux/macOS users. While Service Fabric supports cross-platform management, the documentation does not show parity in examples.
Recommendations
  • Add equivalent examples using the Service Fabric CLI (sfctl) for Linux/macOS users.
  • Include REST API examples for health reporting and querying, which are platform-agnostic.
  • Explicitly mention that PowerShell is Windows-specific, and provide links or guidance for Linux/macOS users.
  • Ensure that all critical tasks demonstrated with PowerShell are also shown with cross-platform tools.
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-18 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation references PowerShell as the primary example for retrieving the cluster manifest and links to a PowerShell-based deployment guide as the next step. While .NET and REST are also mentioned, PowerShell is consistently listed first, and there are no explicit Linux/bash/CLI examples or guidance. This creates a subtle Windows-first and PowerShell-heavy bias.
Recommendations
  • Add explicit examples or references for retrieving the cluster manifest using Azure CLI or bash scripts, especially for Linux/macOS users.
  • In the 'Next steps' section, provide links to equivalent deployment guides using Azure CLI or REST, not just PowerShell.
  • When listing programmatic options (PowerShell, .NET, REST), alternate the order or clarify that all are equally supported, and consider including Azure CLI.
  • If PowerShell is cross-platform, clarify that it works on Linux/macOS as well.
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-18 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page for Service Fabric application and service manifest examples shows mild Windows bias. The only explicit mention of tooling is the ServiceFabric PowerShell module, with no Linux CLI or cross-platform alternatives referenced. Examples use Windows-centric patterns (e.g., .exe and .bat files), and user/group concepts reference Windows system groups (Administrators, NetworkService). There are no Linux-specific examples or guidance, and Windows terminology is used throughout, even though Service Fabric supports Linux clusters and .NET Core workloads.
Recommendations
  • Add equivalent Linux CLI examples (e.g., using Azure CLI or Service Fabric CLI) alongside or in place of PowerShell references.
  • Show examples using Linux-friendly entry points (e.g., shell scripts like setup.sh, service binaries without .exe extension).
  • Clarify which user/group concepts map to Linux (e.g., using 'root', 'service' users, or custom groups) and how to configure them.
  • Mention cross-platform considerations for endpoint configuration, resource governance, and package sharing.
  • Explicitly note when examples are Windows-specific and provide Linux alternatives where possible.
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-18 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides only PowerShell-based deployment examples and references Windows tools (RDP, PowerShell) without offering equivalent Linux/macOS instructions or CLI examples. Windows-centric terminology and examples (e.g., RDP, C:> prompt) are used throughout, and Linux alternatives (such as Azure CLI, SSH, or Bash) are not mentioned. This creates friction for Linux/macOS users who may not use PowerShell or Windows tools.
Recommendations
  • Add Azure CLI (az) command examples alongside PowerShell for all deployment steps.
  • Include SSH instructions for accessing VMs instead of only referencing RDP.
  • Use generic file paths and prompts (e.g., ~/SFSamples/Final/template/_existingvnet.json) in examples, or show both Windows and Linux/macOS paths.
  • Mention cross-platform tools and patterns where possible, and clarify any Windows-specific steps.
  • Explicitly note that PowerShell examples are for Windows users, and provide Linux/macOS equivalents.
GitHub Create Pull Request
Service Fabric Specifying Service Fabric service endpoints ...ce-fabric/service-fabric-service-manifest-resources.md
Medium Priority View Details →
Scanned: 2026-02-18 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page exhibits moderate Windows bias. PowerShell is the only CLI shown for application deployment, and Windows file paths and certificate store names are mentioned first or exclusively in several places. Linux equivalents are referenced but not demonstrated with examples, and Linux-specific instructions are minimal.
Recommendations
  • Provide equivalent Linux CLI examples (e.g., using Bash with sfctl or Azure CLI) alongside PowerShell commands for deploying applications.
  • When referencing file paths or certificate stores, mention Linux paths (e.g., /var/lib/sfcerts) alongside Windows paths, and do so with equal prominence.
  • Include explicit Linux/macOS examples for common tasks, such as deploying with sfctl or configuring certificates.
  • Clarify any platform-specific behaviors or limitations in endpoint/certificate handling.
  • Where possible, link to Linux/macOS-specific documentation or guides.
GitHub Create Pull Request
Service Fabric Define Service Configuration in StartupServices.xml for a Service Fabric Application ...service-fabric/service-fabric-startupservices-model.md
Medium Priority View Details →
Scanned: 2026-02-18 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation is heavily oriented toward Visual Studio workflows, referencing Windows-specific actions (Build/Rebuild/F5/Ctrl+F5/Publish) and GUI interactions. There are no examples or instructions for Linux/macOS users, nor are cross-platform tools or command-line alternatives discussed. The only mention of non-Visual Studio deployment is a brief reference to ARM and PowerShell cmdlets, but no Linux equivalents or guidance are provided.
Recommendations
  • Add explicit guidance for Linux/macOS users, including how to manage StartupServices.xml outside Visual Studio.
  • Provide examples using Azure CLI or cross-platform tools for deploying Service Fabric applications.
  • Clarify which aspects of StartupServices.xml are Visual Studio/Windows-only and which can be used in cross-platform scenarios.
  • Include instructions for editing and deploying manifests on Linux/macOS, or state limitations clearly.
GitHub Create Pull Request
Service Fabric Service communication with the ASP.NET Core ...vice-fabric-reliable-services-communication-aspnetcore.md
Medium Priority View Details →
Scanned: 2026-02-18 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation provides comprehensive coverage of both Kestrel (cross-platform) and HTTP.sys (Windows-only) web servers for ASP.NET Core in Service Fabric. However, Windows-specific tools and patterns (e.g., HTTP.sys, netsh, Windows HTTP Server API) are discussed in detail, often before their Linux equivalents or alternatives. There are explicit notes about HTTP.sys being Windows-only, but Linux-specific guidance and examples are limited. Kestrel is correctly identified as the preferred cross-platform option, but Linux/macOS users may find the documentation less tailored to their needs, especially regarding endpoint configuration, port management, and troubleshooting.
Recommendations
  • Add explicit Linux/macOS guidance for Service Fabric scenarios, including endpoint configuration, port assignment, and firewall considerations.
  • Provide Linux/macOS-specific troubleshooting tips, especially for Kestrel usage and networking.
  • Include example workflows or code snippets for Linux/macOS environments (e.g., using systemd for service management, firewall-cmd for port opening).
  • Clarify any differences in ServiceManifest.xml handling or deployment steps for Linux clusters.
  • Ensure parity in example ordering: present Kestrel (cross-platform) examples before HTTP.sys (Windows-only) examples.
GitHub Create Pull Request
Service Fabric Add custom Service Fabric health reports ...rticles/service-fabric/service-fabric-report-health.md
Medium Priority View Details →
Scanned: 2026-02-18 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 PowerShell examples for health reporting in Service Fabric, with no equivalent Linux/macOS CLI or scripting examples. Windows tools (PowerShell cmdlets) are mentioned and demonstrated before REST or API approaches. There is no mention of Linux-compatible tooling (such as Azure CLI, Bash, or cross-platform Service Fabric CLI), nor guidance for Linux users to perform equivalent tasks.
Recommendations
  • Add examples using Azure CLI or Service Fabric CLI (sfctl), which are cross-platform and work on Linux/macOS.
  • Include Bash or shell script snippets for health reporting, where applicable.
  • Clarify which PowerShell cmdlets are available cross-platform (PowerShell Core), and provide alternatives if not.
  • Mention REST API usage more prominently, and provide sample curl commands for Linux/macOS users.
  • Reorder sections so that cross-platform methods (REST, CLI) are presented before or alongside Windows-specific tools.
GitHub Create Pull Request
Service Fabric Learn Azure Service Fabric terminology ...es/service-fabric/service-fabric-technical-overview.md
Medium Priority View Details →
Scanned: 2026-02-18 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page provides a general overview of Azure Service Fabric terminology and concepts. While Service Fabric is a cross-platform technology, several sections (notably the 'Node' definition) reference Windows-specific tools and patterns first, such as auto-start Windows services and EXE/DLL files. Linux equivalents are not mentioned or are only referenced later. The documentation also uses Windows terminology (e.g., EXE/DLL, Windows service names) without providing Linux-specific details or parity in examples.
Recommendations
  • In the 'Node' section, clarify how Service Fabric nodes operate on Linux (e.g., which processes/services are used, how startup is handled).
  • When referencing executable formats (EXE/DLL), mention Linux equivalents (e.g., ELF binaries, .so files) and note cross-platform support.
  • Provide Linux-specific terminology and examples alongside Windows ones, especially in sections discussing deployment, node management, and code packages.
  • Where Windows services are mentioned, describe the Linux process/service model for Service Fabric nodes.
  • Consider adding a table or section explicitly comparing Windows and Linux operational differences for Service Fabric clusters.
GitHub Create Pull Request
Service Fabric Configure the upgrade of a Service Fabric application ...abric/service-fabric-visualstudio-configure-upgrade.md
Medium Priority View Details →
Scanned: 2026-02-18 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on Windows tooling, specifically Visual Studio and PowerShell, for configuring and upgrading Service Fabric applications. All examples and instructions reference Windows tools, with no mention of Linux/macOS equivalents or cross-platform alternatives. Linux users are not provided guidance for performing upgrades or configuring parameters outside of Windows environments.
Recommendations
  • Add instructions and examples for upgrading Service Fabric applications using cross-platform tools such as Azure CLI or REST APIs.
  • Document how to configure upgrade parameters and health policies using methods available on Linux/macOS (e.g., editing manifest files, using sfctl).
  • Include references to Linux-compatible Service Fabric SDKs and tools.
  • Clearly indicate which steps are Windows-only and provide Linux/macOS alternatives where possible.
GitHub Create Pull Request
Service Fabric RunToCompletion semantics and specifications ...blob/main/articles/service-fabric/run-to-completion.md
Medium Priority View Details →
Scanned: 2026-02-17 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page presents RunToCompletion semantics in Service Fabric with a strong Windows bias. All code examples use Windows containers (nanoserver), Windows-specific commands (cmd, echo, ping, set, exit), and the only CLI example for querying deployment status is via PowerShell. There are no Linux container examples, nor any mention of Linux-compatible commands, tools, or workflows. The documentation assumes familiarity with Windows container development and does not provide Linux parity.
Recommendations
  • Add equivalent examples using Linux containers (e.g., Ubuntu or Alpine images) with bash commands.
  • Include instructions for querying deployment status using Linux tools (such as Azure CLI or REST API), not just PowerShell.
  • Clarify whether RunToCompletion semantics are supported for Linux containers and guest executables, and if so, provide Linux-specific guidance.
  • Present examples for both Windows and Linux environments, or explicitly state if the feature is Windows-only.
GitHub Create Pull Request
Service Fabric Application upgrade: upgrade parameters ...abric/service-fabric-application-upgrade-parameters.md
Medium Priority View Details →
Scanned: 2026-02-17 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page presents upgrade parameters for Service Fabric applications, but gives primary focus to Windows-centric tools (PowerShell and Visual Studio) in both structure and examples. The PowerShell and Visual Studio sections are detailed and appear first, while Linux-compatible tools (SFCTL CLI) are covered later and with less depth. No explicit Linux/macOS examples are provided for parameter usage, and PowerShell examples are shown before SFCTL, potentially creating friction for Linux users.
Recommendations
  • Add explicit Linux/macOS examples for parameter usage with SFCTL, including sample commands.
  • Reorganize the page to present cross-platform tools (SFCTL, REST API) before or alongside Windows tools.
  • Clarify which parameters are available or behave differently across platforms.
  • Ensure parity in detail and guidance for SFCTL usage as is provided for PowerShell and Visual Studio.
  • Consider adding a comparison table showing parameter mapping between PowerShell, Visual Studio, and SFCTL.
GitHub Create Pull Request
Service Fabric Azure Service Fabric networking best practices ...ice-fabric/service-fabric-best-practices-networking.md
Medium Priority View Details →
Scanned: 2026-02-17 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides both Windows and Linux guidance for Service Fabric networking, but there is a notable Windows bias. Windows/PowerShell examples and terminology appear first or exclusively in several sections, such as API endpoints, DevOps integration, and application networking. PowerShell is referenced as the primary client API example, and Windows-specific tools and scenarios (e.g., RDP, Windows Updates, Windows containers) are described in detail, while Linux equivalents are often missing or less prominent. Linux-specific guidance is present but less detailed and sometimes referenced second.
Recommendations
  • Ensure Linux examples and terminology are presented alongside Windows examples, not after or omitted.
  • Add explicit Linux CLI/API usage examples (e.g., Azure CLI, Service Fabric CLI) where PowerShell is referenced.
  • Include Linux container networking scenarios and best practices, matching the detail given for Windows containers.
  • Provide Linux-specific DevOps integration guidance (e.g., using Azure DevOps tasks with Linux clusters).
  • Balance the order of examples so Linux and Windows are treated equally in tables and lists.
GitHub Create Pull Request
Service Fabric Application lifecycle in Service Fabric ...service-fabric/service-fabric-application-lifecycle.md
Medium Priority View Details →
Scanned: 2026-02-17 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation consistently references PowerShell cmdlets and .NET API methods for managing the Service Fabric application lifecycle, with no explicit examples or instructions for Linux users. While REST API options are mentioned, there is a lack of parity in terms of CLI (e.g., Azure CLI, sfctl) usage examples, and no Linux shell or cross-platform command-line instructions are provided. This creates friction for Linux/macOS users, who must infer or research equivalent commands.
Recommendations
  • Add explicit examples using Azure CLI and/or sfctl for each lifecycle operation (deploy, upgrade, remove, etc.), especially where PowerShell cmdlets are currently shown.
  • Where PowerShell is referenced, provide equivalent bash/shell or cross-platform CLI commands, or at least link to relevant Linux instructions.
  • Clarify in each section that REST API and CLI tools are cross-platform, and provide sample usage for non-Windows environments.
  • In 'Preserving disk space' and 'Cleaning up files' sections, include Linux shell command examples or reference to sfctl/Azure CLI documentation for automation.
GitHub Create Pull Request
Service Fabric Understanding periodic backup configuration ...-fabric-backuprestoreservice-configure-periodic-backup.md
Medium Priority View Details →
Scanned: 2026-02-17 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page for Azure Service Fabric periodic backup configuration shows minor Windows bias. The only on-premises backup storage example provided is a Windows file share (with Windows authentication and UNC path syntax), and there are no examples or mentions of Linux-compatible storage options (such as NFS or SMB mounts on Linux). The file share configuration and authentication methods are Windows-centric, and Linux users are not given guidance or parity examples for configuring on-premises backup storage.
Recommendations
  • Add examples and guidance for configuring backup storage using Linux-compatible file shares, such as NFS or SMB mounts.
  • Clarify whether the file share backup storage option supports Linux-based clusters and, if so, provide sample paths and authentication methods for Linux.
  • Mention any limitations or requirements for Linux users when configuring on-premises backup storage.
  • Consider including a note or section about cross-platform compatibility for backup storage options.
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-17 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides PowerShell examples for configuring service sensitivity and maximum load, but does not include equivalent Linux/macOS CLI examples (such as Azure CLI or REST API). PowerShell is presented as the primary scripting interface, which may create friction for Linux/macOS users. The C# API is also shown, but this is cross-platform. The overall configuration (XML/JSON manifests) is platform-neutral, but operational scripting is Windows-centric.
Recommendations
  • Add Azure CLI or REST API examples for creating and updating services with sensitivity and maximum load settings, if supported.
  • Clarify whether PowerShell examples are usable on Linux/macOS (via PowerShell Core), or provide Bash shell equivalents.
  • Explicitly mention any limitations or alternative workflows for Linux/macOS users.
  • Consider reordering examples so that platform-neutral (manifest, JSON) approaches are shown first, followed by scripting interfaces.
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-17 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides only PowerShell and C# examples for managing Service Fabric Application Groups, with no mention of Linux-compatible CLI tools (such as sfctl) or Bash equivalents. PowerShell is a Windows-centric tool, and its exclusive use creates friction for Linux/macOS users. There is no guidance or example for Linux users, even though Service Fabric supports cross-platform management.
Recommendations
  • Add examples using sfctl (Service Fabric CLI), which is cross-platform and works on Linux/macOS.
  • Include Bash or shell command equivalents where possible.
  • Explicitly mention that PowerShell examples are for Windows, and provide Linux/macOS alternatives.
  • Link to documentation about using Service Fabric on Linux, including management tools and APIs.
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-17 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides code examples and administrative patterns primarily using PowerShell and C#, with PowerShell being a Windows-centric tool. There are no equivalent Linux CLI or scripting examples (e.g., Bash, sfctl), and Windows tools are referenced first and exclusively in administrative sections. This creates friction for Linux users, who must translate Windows-centric instructions to Linux-compatible commands.
Recommendations
  • Add Linux CLI examples using sfctl or Bash scripts alongside PowerShell examples.
  • Mention Linux administrative tools and patterns (e.g., sfctl, REST API) wherever PowerShell is referenced.
  • Present examples for both platforms in parallel, or clarify when a tool is Windows-only.
  • Include links to Linux-specific Service Fabric documentation or guides.
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-17 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page for scaling Azure Service Fabric standalone clusters exhibits Windows bias. It references PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) without providing equivalent Linux or cross-platform CLI examples. The linked 'scale a standalone cluster' guide is titled 'service-fabric-cluster-windows-server-add-remove-nodes.md', further suggesting a Windows-centric approach. No Linux-specific guidance or parity is offered, leaving Linux users without clear instructions.
Recommendations
  • Add examples using Service Fabric CLI (sfctl) or REST APIs, which are cross-platform.
  • Explicitly state if standalone cluster scaling is Windows-only; if not, provide Linux/macOS instructions.
  • Include guidance for Linux-based deployments, such as how to query cluster manifests and perform configuration upgrades on Linux.
  • Link to or create documentation for scaling standalone clusters on Linux, if supported.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Docker Compose Deployment Preview ...ticles/service-fabric/service-fabric-docker-compose.md
Medium Priority View Details →
Scanned: 2026-02-17 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both PowerShell and Service Fabric CLI (sfctl) examples for deploying Docker Compose files on Azure Service Fabric. However, PowerShell examples are presented first, with more detailed command coverage and explanations, which may create friction for Linux/macOS users. The CLI examples are included and cover equivalent functionality, but PowerShell is emphasized and described as the default approach.
Recommendations
  • Present CLI (sfctl) examples before or alongside PowerShell examples to avoid Windows-first bias.
  • Expand CLI example explanations to match the detail provided for PowerShell commands.
  • Explicitly note that sfctl is cross-platform and recommended for Linux/macOS users.
  • Consider adding a short section clarifying OS compatibility for each tool.
  • If possible, provide Bash or shell script examples for common workflows.
GitHub Create Pull Request
Service Fabric Define Service Configuration in StartupServices.xml for a Service Fabric Application ...service-fabric/service-fabric-startupservices-model.md
Medium Priority View Details →
Scanned: 2026-02-17 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation is heavily oriented around Visual Studio workflows (Build/Rebuild/F5/Ctrl+F5/Publish), which are Windows-centric. All deployment and configuration examples reference Visual Studio and Windows-specific patterns. There are no examples or guidance for Linux/macOS users, nor mention of cross-platform tooling or workflows for Service Fabric application development.
Recommendations
  • Add explicit guidance for Linux/macOS users, including how to manage service configuration and deployment without Visual Studio.
  • Provide examples using cross-platform tools such as Azure CLI, Service Fabric CLI (sfctl), or PowerShell Core (if applicable).
  • Clarify which features are Visual Studio/Windows-only and offer alternative approaches for Linux/macOS environments.
  • Include sample workflows for editing and deploying StartupServices.xml and ApplicationManifest.xml on Linux/macOS.
GitHub Create Pull Request
Service Fabric Manage certificates in a Service Fabric cluster ...vice-fabric/cluster-security-certificate-management.md
Medium Priority View Details →
Scanned: 2026-02-17 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides a mix of platform-neutral JSON ARM template examples and PowerShell scripts, but the only explicit scripting example for certificate enrollment is in PowerShell. The Key Vault VM extension is described as 'for Windows', and its documentation links and schema are Windows-specific. The 'linkOnRenewal' feature is explicitly noted as Windows-only, and troubleshooting sections reference Windows APIs (S-channel, CERT_RENEWAL_PROP_ID). Linux equivalents (such as Azure Key Vault Linux VM extension, Bash/CLI examples, or Linux certificate store handling) are not mentioned or demonstrated. Windows-centric tools and patterns (PowerShell, Windows certificate store, S-channel) are referenced before or instead of Linux alternatives.
Recommendations
  • Add Azure CLI or Bash scripting examples for certificate enrollment and management alongside PowerShell.
  • Explicitly mention and link to the Key Vault VM extension for Linux, and clarify any differences in behavior or limitations.
  • Provide guidance or examples for managing certificates on Linux nodes (e.g., certificate store locations, permissions, monitoring).
  • Where Windows-specific features are discussed (e.g., linkOnRenewal, S-channel), note Linux alternatives or limitations.
  • Ensure troubleshooting and FAQ sections address Linux scenarios, including relevant APIs and certificate handling.
  • Balance example order so Linux and Windows are equally represented, or clarify when features are Windows-only.
GitHub Create Pull Request
Service Fabric X.509 Certificate-based Authentication in a Service Fabric Cluster ...ticles/service-fabric/cluster-security-certificates.md
Medium Priority View Details →
Scanned: 2026-02-17 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation provides a thorough conceptual overview of X.509 certificate-based authentication in Service Fabric clusters, but exhibits mild Windows bias. Windows terminology and tools (e.g., certificate store paths like 'LocalMachine\My', references to Win32 CryptoAPI, and event log locations) are mentioned first or exclusively. Troubleshooting sections focus on Windows event logs and CAPI2 logging, with no equivalent Linux guidance. While Linux paths are briefly mentioned (e.g., '/var/lib/sfcerts'), Windows-centric examples and APIs dominate, creating friction for Linux users.
Recommendations
  • Add Linux-specific examples for certificate store locations, certificate management, and troubleshooting (e.g., relevant log files, commands for viewing certificates).
  • When referencing Windows tools or APIs (e.g., CertGetCertificateChain, CAPI2 logging), provide Linux equivalents or clarify if the guidance is Windows-only.
  • Ensure troubleshooting steps include Linux/macOS guidance, such as how to access Service Fabric logs, check certificate permissions, and validate certificate chains.
  • Where possible, present cross-platform examples side-by-side, or note differences in behavior and configuration between Windows and Linux clusters.
GitHub Create Pull Request
Service Fabric Custom Image .../articles/service-fabric/how-to-deploy-custom-image.md
Medium Priority View Details →
Scanned: 2026-02-17 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias by focusing on custom Windows images, providing PowerShell examples for role assignment, and referencing Windows/PowerShell tools and patterns before their Linux equivalents. Although there are links to Linux documentation for creating custom images and using Azure CLI, the main narrative and examples prioritize Windows terminology and tools.
Recommendations
  • Provide equivalent Linux/bash examples for role assignment (e.g., using Azure CLI instead of PowerShell).
  • Clarify that custom images can be Linux-based and provide explicit Linux image deployment examples.
  • Ensure that references to Linux documentation are as prominent as Windows documentation.
  • Add ARM template examples for Linux node types if supported.
  • Mention any limitations or differences for Linux custom images in Service Fabric Managed Clusters.
GitHub Create Pull Request
Service Fabric Configure or modify a Service Fabric managed cluster node type ...vice-fabric/how-to-managed-cluster-modify-node-type.md
Medium Priority View Details →
Scanned: 2026-02-17 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides examples for configuring Service Fabric managed cluster node types using Azure Portal, ARM templates, and PowerShell. PowerShell is the only CLI example provided, with no equivalent Bash, Azure CLI, or Linux/macOS shell examples. The PowerShell examples are presented prominently and repeatedly, creating friction for Linux/macOS users who cannot use PowerShell natively. There is no explicit mention of Windows-only features, so the bias is not justified by feature scope.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all tasks (add, remove, scale, configure placement properties, etc.), as Azure CLI is cross-platform and works on Linux/macOS.
  • Clarify that PowerShell examples are for Windows users and provide guidance for Linux/macOS users.
  • Consider referencing Bash scripting or ARM template deployment via Azure CLI for Linux/macOS users.
  • Review all sections where PowerShell is used and ensure parity with Azure CLI or Bash examples.
GitHub Create Pull Request
← Previous Page 10 of 53 Next →