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 501-525 of 2475 flagged pages
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-03-04 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 managing node tags and service requirements, but does not include equivalent Linux/macOS CLI examples (such as Bash or Azure CLI). PowerShell is presented first and exclusively as the shell-based method, which may create friction for Linux/macOS users who typically use Bash or other shells. There is no mention of cross-platform tools or commands for these operations.
Recommendations
  • Add Azure CLI or Bash script examples for managing node tags and service requirements, if supported.
  • Clarify whether PowerShell commands are available cross-platform (PowerShell Core), or if they are Windows-only.
  • Mention REST API usage with example curl commands for Linux/macOS users.
  • Explicitly state if certain operations are only possible via PowerShell, and provide guidance for Linux/macOS users.
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-03-04 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 exhibits Windows bias by referencing PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) and linking to Windows Server-specific guides. There are no Linux-specific examples, commands, or guidance, and the tooling mentioned is Windows-centric.
Recommendations
  • Add equivalent Linux instructions and examples, such as using Service Fabric CLI (sfctl) or REST APIs for cluster management.
  • Explicitly state if standalone clusters are Windows-only, or clarify Linux support status.
  • Provide links to Linux-specific documentation or note limitations if Linux is not supported.
  • Mention cross-platform tools or approaches where possible, and avoid referencing only Windows tools.
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-03-04 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page focuses heavily on Windows Server clusters when discussing standalone cluster security, providing links and instructions only for Windows. There are no equivalent examples, links, or instructions for securing standalone Linux Service Fabric clusters, even though the text mentions that the concepts are similar for Linux and Windows. Windows security mechanisms (Kerberos, group Managed Service Accounts) are discussed without Linux alternatives, and certificate creation is described with a Windows-centric approach. Azure-hosted clusters are covered in a platform-neutral way, but standalone scenarios are Windows-only.
Recommendations
  • Add explicit guidance, links, and examples for securing standalone Linux Service Fabric clusters, including certificate setup and client authentication.
  • Clarify which security features are available or unsupported on Linux standalone clusters.
  • Provide Linux-specific instructions or references for certificate creation, installation, and management (e.g., using OpenSSL, Linux certificate stores).
  • Mention Linux authentication mechanisms or note their absence if not supported.
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-03-04 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation consistently references Windows-specific upgrade and configuration guides (e.g., links ending with '-windows-server.md'), and the only patch orchestration application mentioned is for Windows. There are no Linux-specific instructions, examples, or references, and the documentation does not clarify whether Linux clusters are supported or provide parity guidance.
Recommendations
  • Clarify early in the article whether Service Fabric standalone clusters are Windows-only or if Linux is supported.
  • If Linux standalone clusters are supported, provide equivalent Linux upgrade/configuration guides and link to them alongside or before Windows guides.
  • Mention and link to any Linux-compatible patch orchestration solutions, or explicitly state if such functionality is unavailable.
  • Ensure that examples, references, and tool mentions are either cross-platform or clearly indicate platform specificity.
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-03-04 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 for the Azure Service Fabric application resource model exhibits several Windows biases. All deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) without mentioning or providing Azure CLI equivalents. The application packaging step references Visual Studio, a Windows-centric tool, and does not offer alternatives for Linux/macOS users. There are no Linux/macOS-specific instructions or examples, and Windows tools and patterns are presented first and exclusively.
Recommendations
  • Add Azure CLI examples for deployment and deletion alongside PowerShell examples.
  • Provide instructions for packaging Service Fabric applications using cross-platform tools (e.g., dotnet CLI, sfctl, or manual zip commands).
  • Mention and link to Linux/macOS-compatible tooling for application packaging and deployment.
  • Clarify which steps are Windows-only and offer Linux/macOS alternatives where possible.
  • Consider reordering examples so that cross-platform solutions are presented before or alongside Windows-specific ones.
GitHub Create Pull Request
Service Fabric Learn more about Azure Service Fabric ...icles/service-fabric/service-fabric-content-roadmap.md
Medium Priority View Details →
Scanned: 2026-03-04 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation provides a broad overview of Azure Service Fabric, which supports both Windows and Linux. However, there is a noticeable Windows bias: Windows-specific tools (e.g., PowerShell, Visual Studio) are often mentioned first or exclusively, and several examples reference Windows services and executables (e.g., FabricHost.exe). Standalone cluster creation and upgrades are only described for Windows, with Linux standalone clusters explicitly noted as unsupported. Linux equivalents (e.g., Bash, Linux CLI usage) are rarely mentioned, and Linux-specific guidance is minimal or missing in several sections.
Recommendations
  • Provide Linux-specific examples and instructions alongside Windows ones, especially for cluster management, health monitoring, and application lifecycle tasks.
  • Mention Linux tools (e.g., Bash, Linux CLI) and workflows where PowerShell or Visual Studio are referenced.
  • Clarify which features are Windows-only and which are cross-platform, linking to Linux documentation where available.
  • Add parity for standalone cluster creation and upgrades when Linux support becomes available, or provide alternative guidance for Linux users.
  • Ensure CLI examples are platform-neutral or include both Windows and Linux variants.
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-03-04 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 but does not offer equivalent Linux CLI or cross-platform alternatives. Windows-centric tools (PowerShell, ApplicationManifest.xml in Visual Studio) are mentioned before Linux options, and Linux limitations are noted without guidance for Linux users. There are no Linux-specific examples or instructions, creating friction for Linux users.
Recommendations
  • Add CLI examples for Linux, such as Azure CLI or bash scripts, for setting DNS names and managing Service Fabric services.
  • Include instructions or examples for editing service manifests and deploying services on Linux clusters using cross-platform tools.
  • Clarify how Linux users can accomplish tasks that are currently only documented with PowerShell or Windows tooling.
  • Provide guidance for enabling DNS service on Linux clusters, including steps for containerized services and alternatives to the Azure portal.
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-03-04 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation provides upgrade guidance for Azure Service Fabric clusters, which can run on both Windows and Linux. However, there are several areas where Windows bias is evident: references to 'Patch the Windows operating system in your Service Fabric cluster' are given as the only OS patching example, and PowerShell is mentioned before Azure CLI in several places. There are no explicit Linux-specific examples or guidance, and the OS upgrade section only links to Windows patching documentation.
Recommendations
  • Add explicit guidance and links for patching/upgrading Linux-based Service Fabric clusters, including relevant documentation for Linux OS image upgrades.
  • When mentioning PowerShell and Azure CLI, ensure both are presented equally, and provide Bash/Linux CLI examples where appropriate.
  • Clarify which features or upgrade steps are Windows-only and which are cross-platform, to help Linux users identify relevant instructions.
  • Include examples or references for managing certificates, ports, and node properties using Linux tools or Azure CLI from a Linux/macOS environment.
GitHub Create Pull Request
Service Fabric Scalability of Service Fabric services .../service-fabric/service-fabric-concepts-scalability.md
Medium Priority View Details →
Scanned: 2026-03-04 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, which is a Windows-centric tool. There are no equivalent Linux CLI or bash examples, and PowerShell is mentioned before any Linux alternatives. While the page does acknowledge platform differences in the 'Choosing a platform' section, the practical guidance and examples are heavily skewed toward Windows users, creating friction for Linux/macOS users.
Recommendations
  • Add equivalent Linux CLI/bash examples for administrative tasks (e.g., scaling services, creating/removing services/applications).
  • Mention and link to Linux-specific Service Fabric management tools (such as sfctl) alongside PowerShell.
  • Present Windows and Linux examples side by side, or alternate which platform is shown first.
  • Clarify when a command is Windows-only and provide Linux alternatives where possible.
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-03-04 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 hosting model presents PowerShell as the primary CLI example for service creation and management, with no mention of Linux-compatible CLI tools (such as sfctl) or Bash equivalents. Windows/PowerShell examples are given first and exclusively, creating friction for Linux/macOS users who may not have access to PowerShell or prefer native tools. REST API and .NET code examples are included, but CLI guidance is Windows-centric.
Recommendations
  • Add equivalent examples using sfctl (Service Fabric CLI) for Linux/macOS users alongside PowerShell examples.
  • Explicitly mention that sfctl can be used on Linux/macOS and provide links to its documentation.
  • Clarify which tools are cross-platform and which are Windows-only, to help users select the right approach.
  • Consider providing Bash script examples where relevant, or note any limitations for Linux/macOS users.
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-03-04 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 (New-ServiceFabricApplication) as the first and most prominent example for specifying parameters during application creation. Linux tooling (sfctl) is mentioned second, but with less detail. There are no explicit Linux/macOS shell examples (e.g., Bash), and Visual Studio (a Windows-centric tool) is referenced without alternatives for Linux/macOS users. The page assumes familiarity with Windows tools and workflows, creating friction for Linux/macOS users.
Recommendations
  • Provide explicit Bash or shell examples for Linux/macOS users alongside PowerShell examples.
  • Mention and detail cross-platform tools (e.g., sfctl) before Windows-specific tools.
  • Include instructions for using parameter files and deployment scripts in Linux/macOS environments.
  • Reference alternative editors or IDEs (e.g., VS Code) for Linux/macOS users instead of only Visual Studio.
  • Clarify which tools are cross-platform and which are Windows-only.
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-03-04 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page for Replica Soft Delete in Service Fabric heavily references PowerShell APIs (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica) and provides examples and links exclusively for PowerShell usage. There is no mention of Linux CLI equivalents, nor are examples provided for Linux/macOS users. The documentation assumes familiarity with Windows tooling and patterns, creating friction for users operating Service Fabric clusters on Linux.
Recommendations
  • Add examples and references for managing replicas using Service Fabric CLI (sfctl) or REST APIs, which are cross-platform.
  • Clarify whether the PowerShell APIs are available or have equivalents on Linux/macOS, and provide guidance for those platforms.
  • Include sample commands for Linux environments, such as using sfctl or FabricClient APIs in .NET Core.
  • Explicitly state platform limitations if certain APIs are Windows-only, so Linux/macOS users are not misled.
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-03-04 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 links to PowerShell-based deployment/removal guides. While Service Fabric is cross-platform, the documentation does not provide Linux/macOS CLI or scripting alternatives, nor does it mention tools like Azure CLI or Bash. Windows-centric tools and workflows (PowerShell, Visual Studio) are mentioned first and exclusively, creating friction for Linux/macOS users.
Recommendations
  • Add equivalent examples and links for Linux/macOS users, such as using Azure CLI, Bash scripts, or cross-platform .NET Core tools.
  • Explicitly mention cross-platform options for retrieving cluster manifests and deploying applications.
  • Provide guidance for configuring and managing Service Fabric clusters from non-Windows environments.
  • Include references to relevant Linux/macOS documentation or tools alongside PowerShell and Visual Studio.
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-03-04 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 Service Fabric container application manifest examples based on a Windows Server 2016 Container sample. Windows-specific tools and patterns are referenced first and sometimes exclusively (e.g., 'winver' for OS version, Windows file paths, and the use of 'process' isolation). There is minimal mention of Linux equivalents, and no Linux-specific manifest examples or guidance are provided, despite Service Fabric supporting Linux containers.
Recommendations
  • Add equivalent Linux-based manifest examples, or clearly indicate which features are Windows-only.
  • When referencing Windows tools (e.g., 'winver'), also mention Linux equivalents (e.g., 'uname -r' or '/etc/os-release').
  • Use platform-neutral file paths in examples, or provide both Windows and Linux variants where applicable.
  • Clarify in the introduction which features or manifest elements are cross-platform and which are Windows-specific.
  • If features are not supported on Linux, explicitly state this to avoid confusion.
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-03-04 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-based deployment commands and examples, with no mention of Azure CLI, Bash, or Linux/macOS workflows. It also references Windows tools (e.g., RDP, Windows command prompt for ping) and uses Windows-centric file paths and command syntax. There are no Linux/macOS equivalents or guidance for users on those platforms.
Recommendations
  • Add Azure CLI (az) command examples alongside PowerShell for all deployment steps, as Azure CLI is cross-platform.
  • Include Bash/Linux/macOS command-line examples for common tasks (e.g., using ssh instead of RDP, using ping from a Unix shell).
  • When referencing file paths, use platform-agnostic or dual examples (e.g., C:\... and ~/...).
  • Mention alternatives to Windows-specific tools like RDP (e.g., SSH for Linux/macOS users) when discussing VM access.
  • Explicitly state that the templates and workflows are supported on both Windows and Linux/macOS, and provide links to relevant cross-platform tooling documentation.
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-03-04 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 APIs (such as HTTP.sys and netsh) are mentioned exclusively and in detail, with Windows-focused explanations and examples appearing before Linux equivalents. There is a lack of explicit Linux/macOS guidance, and no Linux-specific examples or troubleshooting advice are provided. The documentation assumes familiarity with Windows concepts and tools, and does not offer parity for Linux users in areas such as endpoint configuration, port reservation, or debugging.
Recommendations
  • Add explicit Linux/macOS guidance for Service Fabric scenarios, including port reservation and firewall configuration.
  • Provide Linux-specific examples (e.g., how to configure Kestrel endpoints and firewall rules on Linux).
  • Clarify which features are Windows-only (such as HTTP.sys) and offer alternative approaches for Linux users.
  • Include troubleshooting tips for Linux/macOS environments, especially for common issues like port conflicts or permissions.
  • Balance the order of presentation so that cross-platform solutions (Kestrel) are discussed before Windows-only solutions (HTTP.sys), or clearly mark Windows-only sections.
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-03-04 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page provides detailed examples for reporting health in Service Fabric using C# APIs and PowerShell, with all shell-based examples using PowerShell cmdlets and Windows-style prompts. There are no CLI or shell examples for Linux/macOS users (e.g., Azure CLI, Bash, or cross-platform tools), and PowerShell is presented as the primary scripting interface. REST is mentioned but not exemplified. This creates friction for Linux/macOS users, who may not have access to PowerShell or prefer other tools.
Recommendations
  • Add equivalent examples using Azure CLI (az sf) or Bash scripts for common health reporting tasks.
  • Explicitly mention cross-platform alternatives to PowerShell for interacting with Service Fabric clusters.
  • Provide REST API request examples (e.g., using curl) for health reporting, with sample payloads.
  • Clarify which PowerShell cmdlets are available cross-platform (PowerShell Core) and which are Windows-only.
  • Reorder sections or provide parallel examples so that REST or CLI options are presented before or alongside PowerShell.
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-03-04 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page describes Azure Service Fabric terminology and concepts. While it is intended to be cross-platform, there are several instances where Windows-specific tools and patterns are mentioned first or exclusively. For example, the 'Node' definition references an auto-start Windows service and Windows executables (FabricHost.exe, Fabric.exe, FabricGateway.exe) without mentioning Linux equivalents or patterns. The code package section refers to EXE/DLL files, which are Windows-centric, and does not clarify Linux support or file types. However, the page does acknowledge Linux support in container and guest executable sections, and mentions development clusters for Windows, Linux, and Mac.
Recommendations
  • Add Linux-specific terminology and examples where Windows executables or services are mentioned (e.g., clarify what runs on Linux nodes, such as systemd services or relevant binaries).
  • When describing code packages, mention Linux executable formats (e.g., ELF binaries) and clarify that Service Fabric supports both Windows and Linux code types.
  • Ensure that descriptions of node startup and service management reference both Windows and Linux mechanisms.
  • Where Windows tools or patterns are referenced, provide Linux equivalents or note differences in operation.
  • Consider alternating the order of Windows and Linux mentions to avoid 'windows_first' bias.
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-03-04 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation is heavily focused on Visual Studio workflows, which are primarily Windows-centric. All examples and instructions reference Visual Studio features (Build/Rebuild/F5/Ctrl+F5/Publish), with no mention of Linux/macOS equivalents or alternative tooling. There are references to PowerShell modules for service creation, but no Linux CLI or cross-platform alternatives are discussed. The documentation does not provide guidance for Linux/macOS users on how to achieve similar outcomes, nor does it clarify whether StartupServices.xml can be used outside Visual Studio/Windows environments.
Recommendations
  • Add explicit guidance for Linux/macOS users, including whether StartupServices.xml is supported outside Visual Studio and on non-Windows platforms.
  • Provide examples using Azure CLI, Service Fabric CLI (sfctl), or other cross-platform tools for service deployment and configuration.
  • Clarify limitations or alternative workflows for users developing Service Fabric applications on Linux/macOS.
  • Mention any relevant SDK or tooling for Linux/macOS, or state if the feature is 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-03-04 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides explicit PowerShell instructions for using the Fault Analysis Service but does not mention or provide examples for Linux/macOS users (e.g., Bash, CLI, or REST API usage). There is no guidance for non-Windows environments, which may create friction for developers working on Linux or macOS.
Recommendations
  • Add examples for using the Fault Analysis Service via Azure CLI, Bash, or REST API to support Linux/macOS users.
  • Clarify whether the Fault Analysis Service APIs can be used from non-Windows environments and provide relevant instructions.
  • Mention cross-platform SDKs or tools (if available) and how to install/use them on Linux/macOS.
  • If PowerShell Core (pwsh) is supported, specify its usage for Linux/macOS.
GitHub Create Pull Request
Service Fabric Application lifecycle in Service Fabric ...service-fabric/service-fabric-application-lifecycle.md
Medium Priority View Details →
Scanned: 2026-03-03 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 frequently references PowerShell cmdlets and Windows-centric tools for managing the Service Fabric application lifecycle. While REST API and .NET methods are mentioned, PowerShell examples are consistently provided, and Linux equivalents (such as Azure CLI or sfctl commands) are missing or not highlighted. The page does not provide explicit Linux/macOS command examples, and Windows tools are often listed before REST or cross-platform options.
Recommendations
  • Add Azure CLI and sfctl command examples alongside PowerShell cmdlets for all lifecycle operations.
  • Clearly indicate which tools are cross-platform and which are Windows-only.
  • Where PowerShell is referenced, provide equivalent Linux/macOS instructions or links.
  • Reorder examples so that cross-platform tools (REST, CLI, sfctl) are listed before or alongside Windows tools.
  • Include a section or note about managing Service Fabric applications from Linux/macOS environments.
GitHub Create Pull Request
Service Fabric Capacity planning and scaling for Azure Service Fabric ...bric/service-fabric-best-practices-capacity-scaling.md
Medium Priority View Details →
Scanned: 2026-03-03 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 several PowerShell-based examples and instructions for scaling operations, particularly for disabling and removing nodes. These examples are given without Linux equivalents (such as Bash/CLI commands), and PowerShell is referenced as the primary/manual method for cluster operations. Additionally, Windows tooling and patterns (PowerShell cmdlets) are mentioned first and exclusively, creating friction for Linux users who may need to perform similar tasks using different tools.
Recommendations
  • Add equivalent Linux/Bash/Azure CLI examples for node management operations (e.g., disabling/removing nodes).
  • Explicitly mention cross-platform tools or provide links to Linux-specific guidance where PowerShell is referenced.
  • Clarify whether PowerShell cmdlets are supported on Linux clusters, or provide alternative approaches for Linux environments.
  • Reorder examples to show both Windows and Linux methods, or indicate parity where possible.
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-03-03 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation for changing Azure Service Fabric cluster settings exhibits mild Windows bias. Windows-specific terminology (e.g., 'certificate store', 'NTLM', 'MY', 'LocalMachine'), references to Windows-only features (such as Windows Update), and default values that differ between Windows and Linux are present. Windows concepts (like certificate store names and NTLM authentication) are mentioned without clear Linux equivalents or guidance. Some settings (e.g., ContainerNetworkSetup) have different defaults for Windows and Linux, but Linux-specific guidance is minimal. There are no explicit Linux configuration examples or clarifications for Linux users, and Windows terminology is used throughout, sometimes without explanation for Linux users.
Recommendations
  • Add explicit Linux configuration examples and clarify Linux-specific settings, especially where defaults differ (e.g., ContainerNetworkSetup, certificate store paths).
  • Document Linux equivalents for Windows concepts such as certificate stores (e.g., explain how 'MY' maps to Linux certificate locations or how to configure certificates on Linux nodes).
  • Where Windows-only features are mentioned (e.g., Windows Update, NTLM authentication), clearly indicate if/how they apply to Linux, or provide Linux alternatives.
  • Review parameter descriptions to ensure Linux users can easily map Windows terminology to their environment (e.g., clarify certificate store names, file paths, and authentication mechanisms).
  • Consider adding a section or table summarizing key differences between Windows and Linux Service Fabric clusters.
GitHub Create Pull Request
Service Fabric Learn about Azure Service Fabric application security ...ric/service-fabric-application-and-service-security.md
Medium Priority View Details →
Scanned: 2026-03-03 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation presents several security concepts for Azure Service Fabric applications, but exhibits mild Windows bias. Windows-specific features (such as running services under AD domain accounts or gMSA) are mentioned before Linux equivalents, and some examples (e.g., disk encryption) reference Windows tools (BitLocker, PowerShell) with Linux alternatives marked as TODO or missing. There are references to both Windows and Linux clusters, but Linux-specific guidance is less detailed or omitted in some sections.
Recommendations
  • Add Linux-specific examples and instructions where currently missing, especially for disk encryption and service account management.
  • Ensure parity in example ordering: mention Linux and Windows options together, or alternate which is presented first.
  • Provide links to Linux documentation or tools (e.g., dm-crypt/LUKS for disk encryption, Linux user/group management for service accounts).
  • Clarify when features are Windows-only and provide Linux alternatives or workarounds where possible.
GitHub Create Pull Request
Service Fabric Scalability of Service Fabric services .../service-fabric/service-fabric-concepts-scalability.md
Medium Priority View Details →
Scanned: 2026-03-03 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides code examples primarily in C# and PowerShell, with PowerShell being a Windows-centric tool. There are no equivalent Linux CLI or scripting examples (e.g., Bash, sfctl) provided. Additionally, administrative actions are described using PowerShell cmdlets before mentioning their programmatic equivalents, which may create friction for Linux users. However, the page does acknowledge platform differences in the 'Choosing a platform' section, and Service Fabric itself is cross-platform.
Recommendations
  • Add Linux-specific command-line examples using sfctl or Bash scripts alongside PowerShell examples.
  • Mention Linux tools and workflows (e.g., sfctl, REST API) when describing administrative actions.
  • Ensure that examples and instructions are presented in a platform-neutral way or provide both Windows and Linux alternatives.
  • Clarify when a tool or example is Windows-only and suggest Linux equivalents where possible.
GitHub Create Pull Request
← Previous Page 21 of 99 Next →