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 801-825 of 2475 flagged pages
Service Fabric Service communication with the ASP.NET Core ...vice-fabric-reliable-services-communication-aspnetcore.md
Medium Priority View Details →
Scanned: 2026-02-27 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation covers both Kestrel (cross-platform) and HTTP.sys (Windows-only) web servers for ASP.NET Core integration with Azure Service Fabric. However, Windows-specific tools and patterns (HTTP.sys, netsh, Windows HTTP Server API) are described in detail, often before their Linux equivalents. The HTTP.sys section is Windows-only, and while Kestrel is recommended for Linux, explicit Linux examples, troubleshooting, or environment-specific guidance are missing. Windows-centric configuration steps (e.g., netsh, ServiceManifest.xml for HTTP.sys) are presented without Linux alternatives or clarifications.
Recommendations
  • Add explicit Linux/macOS guidance and examples for Service Fabric Reliable Services with Kestrel, including environment setup, deployment, and troubleshooting.
  • Clearly indicate which sections are Windows-only and which are cross-platform, especially in configuration instructions.
  • Provide Linux-specific notes for ServiceManifest.xml endpoint configuration and port management.
  • Include sample code snippets or references for running Service Fabric Reliable Services on Linux, such as using Kestrel with Linux container images or Service Fabric clusters.
  • Mention any limitations or differences for Linux users (e.g., debugging, certificate management, firewall configuration) and link to relevant documentation.
GitHub Create Pull Request
Service Fabric Replica soft delete for enhanced data protection in Service Fabric ...s/service-fabric/service-fabric-replica-soft-delete.md
Medium Priority View Details →
Scanned: 2026-02-27 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 'Replica soft delete for enhanced data protection in Service Fabric' consistently references PowerShell APIs (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica) and provides examples and links only for PowerShell usage. There is no mention of Linux or cross-platform CLI equivalents, nor are FabricClient API examples shown for non-Windows environments. The documentation assumes familiarity with Windows tools and patterns, creating friction for Linux/macOS users who may need to perform these operations using other methods.
Recommendations
  • Add examples for using the FabricClient APIs in .NET Core or other cross-platform SDKs, including code snippets for Linux/macOS environments.
  • Mention or link to any available Service Fabric CLI tools or REST APIs that can be used from Linux/macOS.
  • Clarify whether the PowerShell APIs are available on Linux (via PowerShell Core), and if so, provide guidance; if not, explicitly state the alternatives.
  • Include sample commands or workflows for Linux/macOS users, or note limitations if certain operations are Windows-only.
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-27 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page is generally cross-platform in its XML manifest examples and explanations, but it demonstrates bias by providing only a PowerShell (Windows) example for application deployment, referencing Windows file paths for schema locations, and mentioning the Service Fabric PowerShell module as the way to create service instances. Linux equivalents (such as Azure CLI or sfctl) are not mentioned, and Linux-specific deployment examples are missing.
Recommendations
  • Add Linux/macOS deployment examples using Azure CLI or sfctl alongside or instead of PowerShell.
  • When referencing file paths (such as schema locations), provide both Windows and Linux paths or clarify platform differences.
  • Mention Linux tools and workflows (e.g., sfctl, Bash scripts) wherever PowerShell or Windows tools are referenced.
  • If the Service Fabric PowerShell module is not available on Linux, explicitly state this and link to Linux alternatives.
  • Consider providing a table or section summarizing platform-specific differences for endpoint and certificate management.
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-27 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily oriented toward Windows development workflows, specifically Visual Studio usage. All deployment, editing, and publishing instructions reference Visual Studio features (Build/Rebuild/F5/Ctrl+F5/Publish), which are Windows-only. There are no examples or guidance for Linux/macOS users or cross-platform tools. The only mention of alternative deployment methods is a brief reference to ARM and PowerShell cmdlets, but no Linux equivalents or CLI examples are provided.
Recommendations
  • Add explicit guidance for Linux/macOS users, including how to manage service configuration and deploy Service Fabric applications without Visual Studio.
  • Provide examples using Azure CLI, Service Fabric CLI (sfctl), or other cross-platform tools for deployment and configuration.
  • Clarify which features are Visual Studio/Windows-only and offer alternative workflows for non-Windows environments.
  • Include sample scripts or instructions for editing and deploying StartupServices.xml on Linux/macOS.
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-27 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 detailed examples for API (C#) and PowerShell usage, with PowerShell commands shown prominently and exclusively for command-line interaction. There are no examples or mentions of Linux/macOS equivalents (such as Bash, CLI, or cross-platform tools), and PowerShell is presented as the primary scripting interface for Service Fabric health reporting. REST API is mentioned, but no concrete Linux/macOS command-line examples (e.g., curl) are given.
Recommendations
  • Add Bash or Azure CLI examples for sending health reports and querying health status, especially for REST API usage (e.g., using curl or az commands).
  • Explicitly mention cross-platform support for Service Fabric health reporting and clarify which tools are available on Linux/macOS.
  • Provide guidance for Linux/macOS users on how to install and use Service Fabric CLI or REST endpoints for health reporting.
  • Reorder sections so that REST and cross-platform methods are presented before or alongside PowerShell, not after.
  • Include notes about PowerShell Core availability on Linux/macOS if relevant, or clarify if the PowerShell commands are Windows-only.
GitHub Create Pull Request
Service Fabric Fault Analysis Service overview .../service-fabric/service-fabric-testability-overview.md
Medium Priority View Details →
Scanned: 2026-02-27 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page for the Fault Analysis Service overview provides usage instructions primarily for C# (via the Microsoft.ServiceFabric NuGet package) and PowerShell (via the Service Fabric SDK and ServiceFabric PowerShell module). There are no examples or instructions for Linux/macOS users, such as using CLI tools, Bash scripts, or cross-platform SDKs. The PowerShell example is Windows-centric, and no Linux equivalents (e.g., Azure CLI, Bash, or REST API usage) are mentioned.
Recommendations
  • Add examples for using the Fault Analysis Service from Linux/macOS environments, such as via Azure CLI, Bash, or REST API.
  • Mention cross-platform SDKs or tools that can be used to interact with the Fault Analysis Service.
  • Clarify whether the Fault Analysis Service APIs and features are available and supported on Linux-based Service Fabric clusters.
  • If PowerShell is required, note any cross-platform support (e.g., PowerShell Core) or alternatives for Linux users.
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-27 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation is heavily focused on Windows tools, specifically Visual Studio and PowerShell, for configuring and upgrading Service Fabric applications. All examples and step-by-step instructions reference Visual Studio (a Windows-only IDE) and PowerShell (primarily used on Windows for Service Fabric management). There are no examples or guidance for Linux/macOS users, such as using Azure CLI, REST API, or cross-platform tools for application upgrades.
Recommendations
  • Add instructions and examples for upgrading Service Fabric applications using cross-platform tools like Azure CLI or REST API.
  • Mention and link to any available Linux/macOS-compatible tooling for Service Fabric application upgrades.
  • Clarify which steps are Windows-only and provide alternative workflows for Linux/macOS users where possible.
  • Include sample scripts or commands for Linux shells (bash) alongside PowerShell examples.
GitHub Create Pull Request
Service Fabric Introduction to the Service Fabric Infrastructure Service .../articles/service-fabric/infrastructure-service-faq.md
Medium Priority View Details →
Scanned: 2026-02-26 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides a PowerShell-only example for bypassing the Infrastructure Service, and references Service Fabric Explorer (a Windows-centric tool) without mentioning Linux/macOS alternatives. No Linux CLI or cross-platform guidance is given for critical operations, creating friction for non-Windows users.
Recommendations
  • Add equivalent CLI examples using Azure CLI or REST API for Linux/macOS users.
  • Clarify whether Service Fabric Explorer is accessible from Linux/macOS, or provide alternatives.
  • Explicitly state platform requirements for commands and tools.
  • Include cross-platform instructions for connecting to Service Fabric clusters and performing administrative tasks.
GitHub Create Pull Request
Service Fabric Service Fabric application upgrade ...s/service-fabric/service-fabric-application-upgrade.md
Medium Priority View Details →
Scanned: 2026-02-26 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides PowerShell-only examples for key upgrade operations and references Windows-specific tools (e.g., http.sys), with no equivalent CLI or Linux/macOS instructions. This creates friction for users managing Service Fabric clusters from non-Windows environments.
Recommendations
  • Add equivalent Azure CLI or Service Fabric CLI (sfctl) examples for application upgrade operations alongside PowerShell examples.
  • Explicitly mention cross-platform management options and link to relevant documentation for Linux/macOS users.
  • Clarify when a feature or limitation (such as http.sys or certificate handling) is Windows-specific, and provide Linux alternatives or workarounds if available.
  • Ensure that all critical upgrade workflows are documented with at least one cross-platform method.
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-26 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 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), and reference Windows container compatibility. Querying deployment status is only shown via PowerShell and C# APIs, with no mention of Linux CLI or Bash alternatives. There are no Linux container examples or guidance for Linux/macOS users.
Recommendations
  • Add equivalent Linux container examples (e.g., using Ubuntu or Alpine images) with Bash commands.
  • Provide instructions for querying deployment status using Azure CLI or Bash, if available.
  • Clarify whether RunToCompletion semantics are supported for Linux containers and guest executables, and if so, provide relevant examples.
  • If Windows-only support is intentional, explicitly state this in the introduction to avoid confusion.
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-26 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page provides general information about Azure Service Fabric node types and virtual machine scale sets, with some Windows-centric patterns. The JSON snippet for the Service Fabric Virtual Machine extension uses a Windows-style file path (D:\\SvcFab) in the 'dataPath' property, and the 'Next steps' section links to PowerShell scripts for RDP port and admin credential changes, which are Windows-specific tasks. There is no explicit Linux/macOS example or guidance for equivalent operations, and Windows patterns (such as RDP and file paths) are referenced without Linux alternatives.
Recommendations
  • Provide Linux-specific examples for the 'dataPath' property (e.g., /var/svcfab or similar) alongside the Windows example.
  • Add guidance or links for connecting to Linux nodes (e.g., SSH instructions) in the 'Next steps' section, not just Windows RDP.
  • Include Linux/macOS equivalent scripts or instructions for changing admin credentials and port ranges.
  • Clarify when instructions are Windows-only and offer Linux alternatives where possible.
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-26 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides a PowerShell example for querying Service Fabric partition health, using Windows-specific syntax and paths (e.g., 'PS C:\Users\User >'). No equivalent Linux/macOS CLI example is given, and PowerShell is presented as the default/only method for interacting with Service Fabric health. This creates friction for Linux/macOS users, as Service Fabric supports cross-platform management via REST APIs and sfctl (Service Fabric CLI), but these are not mentioned.
Recommendations
  • Add equivalent Linux/macOS examples using sfctl (Service Fabric CLI) or REST API calls for health queries.
  • Mention that Service Fabric management can be performed on Linux/macOS using sfctl and REST APIs, and provide links to relevant documentation.
  • Avoid presenting Windows/PowerShell examples as the default; instead, offer both Windows and Linux/macOS examples side-by-side.
  • Clarify any platform-specific limitations if certain commands/tools are Windows-only.
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-26 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page provides general guidance on upgrading Azure Service Fabric clusters and includes references to using PowerShell and Azure CLI for management tasks. However, it notably references Windows-specific upgrade procedures (such as Patch Orchestration Application and a link to 'Patch the Windows operating system in your Service Fabric cluster') without mentioning Linux equivalents or providing Linux-specific guidance. Examples and tool references (PowerShell) are presented without Linux parity or explicit mention of Bash/CLI usage, and Windows OS patching is discussed exclusively.
Recommendations
  • Add explicit Linux cluster upgrade guidance, including links to relevant documentation for patching Linux nodes.
  • When referencing PowerShell, also mention Bash/Azure CLI usage for Linux/macOS users, and provide examples for both platforms.
  • Clarify which sections are Windows-only and provide Linux alternatives or note if Linux clusters are managed differently.
  • Include links or references to Linux Service Fabric cluster maintenance and upgrade documentation, if available.
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-26 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), with no mention of Azure CLI equivalents or Linux/macOS workflows. Application packaging is described using Visual Studio, a Windows-centric tool, and directory paths are given in Windows format. 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 tasks alongside PowerShell examples.
  • Include instructions for packaging applications using cross-platform tools (e.g., dotnet CLI, SF SDK, or manual zip commands) instead of only Visual Studio.
  • Provide directory path examples in both Windows and Linux/macOS formats.
  • Mention alternative editors or tools for non-Windows users.
  • Clearly indicate which steps are Windows-only and offer Linux/macOS 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-26 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 Azure Service Fabric networking patterns demonstrates Windows bias primarily through the exclusive use of PowerShell commands for deployment and management examples. There are no Linux/macOS CLI (e.g., Azure CLI/bash) equivalents provided, and Windows tools (such as RDP and ping from a Windows command prompt) are referenced without mentioning cross-platform alternatives. Windows-centric examples are presented first and throughout, creating friction for Linux/macOS users.
Recommendations
  • Add Azure CLI (az) command examples alongside PowerShell for all deployment steps.
  • Mention cross-platform alternatives for accessing VMs (e.g., SSH instead of RDP) and for network testing (e.g., ping from Linux/macOS terminal).
  • Clarify that Service Fabric clusters can be managed from Linux/macOS and provide relevant instructions or links.
  • Where possible, provide template deployment instructions using the Azure portal and Azure CLI, not just PowerShell.
  • Review all examples to ensure Linux/macOS users can follow along without needing Windows-specific tools.
GitHub Create Pull Request
Service Fabric Fault Analysis Service overview .../service-fabric/service-fabric-testability-overview.md
Medium Priority View Details →
Scanned: 2026-02-26 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page presents PowerShell as the primary scripting interface for interacting with the Fault Analysis Service, without mentioning or providing examples for Linux/macOS command-line tools or SDKs. PowerShell is highlighted as the main way to use the service after C#, and no Linux-specific instructions or CLI alternatives (such as Bash or Azure CLI) are given.
Recommendations
  • Add examples or instructions for using the Fault Analysis Service from Linux/macOS environments, such as via Azure CLI, Bash scripts, or REST API.
  • Mention cross-platform SDKs or tools (e.g., Python, Java) if available, and provide sample usage.
  • Clarify whether PowerShell Core (cross-platform) is supported, and provide guidance for Linux/macOS users if so.
  • If the Fault Analysis Service is accessible only via PowerShell on Windows, explicitly state this limitation.
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-26 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 deploying Service Fabric applications, which is Windows-centric. The Service Fabric schema location is referenced using a Windows file path first, and Windows terminology (e.g., 'MY' certificate store) is used before mentioning Linux equivalents. Linux-specific deployment instructions or CLI examples are missing, and Linux file paths and tools are only briefly referenced.
Recommendations
  • Add Linux/macOS deployment examples using Azure CLI or Bash scripts alongside PowerShell examples.
  • Reference Linux file paths and certificate stores equally and earlier in relevant sections.
  • Clarify which steps or commands differ between Windows and Linux clusters, and provide explicit guidance for Linux users.
  • Where possible, avoid Windows-centric terminology or provide Linux equivalents in parallel.
  • Include links to Linux-specific Service Fabric documentation or tutorials.
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-26 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page provides extensive PowerShell examples and references Windows-specific tools and patterns, such as the Key Vault VM extension for Windows and S-channel certificate linking. Windows terminology and mechanisms (e.g., certificate store locations, ACLing, S-channel, CERT_RENEWAL_PROP_ID) are used throughout, often without Linux/macOS equivalents or guidance. While the Service Fabric cluster can run on Linux, the examples and explanations are heavily Windows-centric, and Linux-specific instructions or parity are missing.
Recommendations
  • Add equivalent Linux/macOS examples for certificate provisioning, rotation, and management, using Bash, Azure CLI, or relevant Linux tools.
  • Clarify which mechanisms (e.g., Key Vault VM extension, certificate linking) are Windows-only and provide alternative approaches for Linux clusters.
  • Include guidance for Linux certificate stores and permissions (e.g., /etc/ssl/certs, file permissions) alongside Windows certificate store and ACLing.
  • Provide troubleshooting steps and automation scripts for Linux environments, not just PowerShell.
  • Explicitly state platform limitations and supported OSes for each mechanism and example.
GitHub Create Pull Request
Service Fabric Azure Service Fabric container image management .../articles/service-fabric/container-image-management.md
Medium Priority View Details →
Scanned: 2026-02-26 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page for Azure Service Fabric container image management references Windows container base images (microsoft/windowsservercore, microsoft/nanoserver) as default exclusions in cleanup settings, and these are mentioned before any Linux equivalents. The examples and explanations focus on Windows images and do not mention common Linux container images or provide Linux-specific guidance, despite Service Fabric supporting Linux containers.
Recommendations
  • Include examples of Linux container images (e.g., 'docker.io/library/ubuntu', 'docker.io/library/alpine') in the 'ContainerImagesToSkip' setting.
  • Clarify that the cleanup settings apply to both Windows and Linux containers, and provide parity in documentation for Linux scenarios.
  • Mention Linux base images in the default exclusions or explain how to configure exclusions for Linux containers.
  • Add a note or section describing any differences in image management between Windows and Linux nodes, if applicable.
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-26 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 overview of X.509 certificate-based authentication in Service Fabric clusters, but exhibits Windows bias in several areas. Windows-specific terminology (e.g., certificate store paths like LocalMachine\My), Windows API references (Win32 CryptoAPI, CertGetCertificateChain), and troubleshooting guidance (event logs, CAPI2 logging) are presented first or exclusively. Linux equivalents are mentioned briefly (e.g., /var/lib/sfcerts), but Windows concepts and tools dominate the examples and troubleshooting advice.
Recommendations
  • Expand Linux-specific guidance: Provide explicit instructions and examples for Linux certificate management, including certificate store locations, relevant commands (e.g., openssl, Linux file permissions), and troubleshooting steps.
  • Balance troubleshooting advice: Include Linux log locations, error codes, and diagnostic tools (e.g., journalctl, syslog, Service Fabric logs on Linux) alongside Windows event log guidance.
  • Clarify cross-platform differences: Where Windows APIs or concepts are referenced (e.g., CertGetCertificateChain, CAPI2 logging), explain Linux equivalents or note platform-specific behavior.
  • Show Linux-first or parallel examples: When presenting configuration snippets or procedures, offer Linux examples or note differences in order and prominence.
  • Reference Linux documentation: Link to Service Fabric Linux-specific docs or Azure docs covering Linux cluster setup and certificate management.
GitHub Create Pull Request
Service Fabric Custom Image .../articles/service-fabric/how-to-deploy-custom-image.md
Medium Priority View Details →
Scanned: 2026-02-26 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page primarily discusses deploying custom Windows images in Service Fabric Managed Clusters, with Windows terminology and PowerShell examples shown. While there are references to Linux custom image creation and Azure CLI usage, Windows is emphasized first and PowerShell is used for role assignment, with no equivalent Linux/bash example provided.
Recommendations
  • Clarify in the introduction that both Windows and Linux custom images are supported if applicable.
  • Provide equivalent Linux/bash commands for role assignment (e.g., using Azure CLI instead of PowerShell).
  • Include ARM template examples for Linux node types if Service Fabric Managed Cluster supports them.
  • Ensure links to Linux documentation are as prominent as Windows links.
  • Explicitly state any limitations or parity differences between Windows and Linux custom image support.
GitHub Create Pull Request
Service Fabric Initializer CodePackages in Service Fabric ...in/articles/service-fabric/initializer-codepackages.md
Medium Priority View Details →
Scanned: 2026-02-26 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 Initializer CodePackages in Service Fabric presents only Windows container examples, exclusively references Windows container images (mcr.microsoft.com/windows/nanoserver:1809), and uses Windows-specific paths and commands (e.g., C:\, cmd, echo, type, ping). There are no Linux container examples, nor any mention of Linux-compatible patterns or tools. The ApplicationManifest and ServiceManifest examples are Windows-centric, and the 'IMPORTANT' note explicitly assumes familiarity with Windows container applications.
Recommendations
  • Add equivalent examples using Linux containers (e.g., mcr.microsoft.com/linux/base images) and Linux shell commands.
  • Show how Initializer CodePackages can be used with Linux containers, including appropriate volume mounts and command syntax.
  • Clarify whether Initializer CodePackages are supported for Linux containers, and if so, provide guidance for Linux users.
  • If Initializer CodePackages are Windows-only, explicitly state this limitation at the top of the article.
GitHub Create Pull Request
Service Fabric Migrate an Azure Service Fabric cluster to availability zone support ...ce-fabric/migrate-service-fabric-availability-zones.md
Medium Priority View Details →
Scanned: 2026-02-26 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 migration guidance for Azure Service Fabric clusters to availability zone support. While much of the content is platform-neutral (focused on ARM templates and Azure resources), the only explicit command-line examples are PowerShell-based, and these are used for critical migration steps (disabling nodes, removing nodes, updating DNS). There are no equivalent Bash/CLI or Linux/macOS instructions, and PowerShell is presented as the default tool for these operations. Additionally, the sample template for Basic SKU migration references a Windows-specific template first, with the Ubuntu template mentioned only in passing.
Recommendations
  • Add Azure CLI or Bash script examples for node management, resource removal, and DNS updates to provide parity for Linux/macOS users.
  • Explicitly mention that PowerShell examples are for Windows and provide links or instructions for Linux/macOS users.
  • Reference both Windows and Linux sample templates equally, and clarify which template is suitable for each OS.
  • Where possible, use platform-agnostic Azure CLI commands instead of PowerShell for resource management.
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-26 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides examples for managing Service Fabric managed cluster node types using the Azure Portal, ARM templates, and PowerShell. PowerShell is the only CLI example provided for scripting/automation, with no mention of Azure CLI (az), Bash, or cross-platform scripting. PowerShell is presented as the default scripting tool, and there are no Linux/macOS-specific instructions or parity for command-line operations.
Recommendations
  • Add Azure CLI (az) examples for all operations currently shown with PowerShell, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that PowerShell examples require PowerShell Core (pwsh) for cross-platform use, or clarify if only Windows PowerShell is supported.
  • Where possible, provide Bash scripting examples or reference REST API usage for automation.
  • Reorder sections to present cross-platform methods (Portal, ARM template, Azure CLI) before Windows-specific tools like PowerShell.
  • Add a note clarifying the supported platforms for each tool and recommend Azure CLI for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Deny assignment policy for Service Fabric managed clusters ...cles/service-fabric/managed-cluster-deny-assignment.md
Medium Priority View Details →
Scanned: 2026-02-26 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides best practice examples primarily using Azure PowerShell, with PowerShell-based tools mentioned before Azure CLI and sfctl. While Azure PowerShell is cross-platform, the emphasis on PowerShell may create friction for Linux/macOS users who typically prefer CLI or other native tools. The examples and guidance do not include Linux-specific command-line usage or highlight Azure CLI usage equivalently.
Recommendations
  • Add explicit Azure CLI examples for key operations (e.g., deleting NodeTypes, restarting/reimaging scale sets) alongside PowerShell examples.
  • Mention Azure CLI before or equally with PowerShell in best practices, recognizing CLI as the default for many Linux/macOS users.
  • Clarify that Azure PowerShell is cross-platform, but provide links to CLI documentation for parity.
  • Include sample sfctl commands where appropriate, especially for Linux users.
  • Consider a table or section comparing PowerShell and CLI usage for common tasks.
GitHub Create Pull Request
← Previous Page 33 of 99 Next →