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 1726-1750 of 2475 flagged pages
Service Fabric Secure an Azure Service Fabric cluster ...cles/service-fabric/service-fabric-cluster-security.md
Medium Priority View Details →
Scanned: 2026-02-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page primarily discusses security scenarios for Azure Service Fabric clusters, but consistently references standalone clusters as 'running on Windows' and provides links and guidance only for Windows Server clusters. There are no equivalent examples, instructions, or links for standalone Linux clusters, nor is it clear how Linux users should secure their clusters outside of Azure. Windows-specific terminology and tools (e.g., Windows authentication, Windows certificate services) are mentioned without Linux alternatives, and Windows instructions are presented first or exclusively.
Recommendations
  • Add explicit guidance and links for securing standalone Linux Service Fabric clusters, including certificate setup and client authentication.
  • Clarify whether standalone Linux clusters are supported and, if so, provide parity in documentation for Linux users.
  • Include Linux-specific examples, such as using OpenSSL for certificate generation, and mention Linux authentication patterns where relevant.
  • Avoid presenting Windows instructions first unless the feature is Windows-only; otherwise, structure sections to address both platforms equally.
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-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation provides general guidance on upgrading Azure Service Fabric clusters and mostly avoids platform-specific bias. However, in the section about OS image upgrades, it references 'Patch the Windows operating system in your Service Fabric cluster' and links to a Windows-specific guide, without mentioning Linux equivalents or clarifying if Linux node patching is supported. Additionally, PowerShell is mentioned alongside Azure CLI for cluster management tasks, but Linux tools or Bash examples are not provided.
Recommendations
  • Clarify whether OS image upgrades and patching guidance apply to Linux-based Service Fabric clusters, and provide links or instructions for Linux node patching if supported.
  • When mentioning PowerShell/Azure CLI, add Bash or Linux shell examples where relevant, or explicitly state if the guidance is platform-agnostic.
  • If Service Fabric clusters support Linux nodes, ensure parity in upgrade and management documentation, including examples and links.
  • Add a note if certain features (like Patch Orchestration Application) are Windows-only, to avoid confusion for Linux users.
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-09 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 demonstrates notable Windows bias. All deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) without any mention of Azure CLI or Bash equivalents. The application packaging step is described using Visual Studio, a Windows-centric tool, with no alternative for Linux/macOS users. There are no Linux/macOS-specific instructions or examples, and Windows tools and patterns are presented exclusively and first.
Recommendations
  • Add Azure CLI examples for deployment and deletion alongside PowerShell examples.
  • Provide instructions for packaging applications using cross-platform tools (e.g., dotnet CLI, sfctl, or manual zip commands) instead of only Visual Studio.
  • Include guidance for Linux/macOS users on uploading application packages (e.g., using Azure CLI or azcopy).
  • Ensure screenshots and walkthroughs are not exclusively Windows/Visual Studio-centric, or provide alternatives for other platforms.
  • Clearly indicate when steps are Windows-only and offer Linux/macOS alternatives where possible.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager: Movement cost ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-movement-cost.md
Medium Priority View Details →
Scanned: 2026-02-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides PowerShell examples for configuring Service Fabric service move costs, but does not offer equivalent Linux/CLI examples. PowerShell is primarily a Windows tool, and its use here without mentioning cross-platform alternatives (such as Azure CLI or REST API) creates friction for Linux/macOS users. Additionally, PowerShell examples are presented before C# code, reinforcing a Windows-first approach.
Recommendations
  • Add Azure CLI or REST API examples for configuring and updating MoveCost, as these are cross-platform and usable on Linux/macOS.
  • Explicitly mention whether PowerShell commands are supported on Linux/macOS, or provide guidance for non-Windows users.
  • Consider presenting cross-platform examples (CLI, REST) before or alongside PowerShell to avoid Windows-first ordering.
  • Clarify any platform limitations for Service Fabric management tools, and link to relevant Linux/macOS documentation if available.
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-09 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 demonstrates Windows bias by referencing PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) and linking to a Windows Server-specific guide for adding/removing nodes. There are no Linux-specific examples, tools, or guidance provided, and the terminology and instructions assume a Windows environment.
Recommendations
  • Provide equivalent Linux commands or scripts for querying and updating cluster configuration (e.g., using sfctl or REST APIs).
  • Clarify whether standalone clusters can be managed on Linux, and if so, add Linux-specific instructions or links.
  • Add examples for scaling operations using Linux-native tools or cross-platform approaches.
  • Explicitly mention any limitations or differences for Linux users if Windows-only tools are required.
GitHub Create Pull Request
Service Fabric Upgrade an Azure Service Fabric standalone cluster ...ce-fabric/service-fabric-cluster-upgrade-standalone.md
Medium Priority View Details →
Scanned: 2026-02-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page for upgrading an Azure Service Fabric standalone cluster demonstrates a notable Windows bias. References and links to upgrade instructions and configuration guides are consistently directed to Windows Server-specific documentation (e.g., 'service-fabric-cluster-upgrade-windows-server.md', 'service-fabric-cluster-config-upgrade-windows-server.md'). The patch orchestration application is also described only for Windows. There are no Linux-specific instructions, examples, or references, and no mention of Linux equivalents or support, which may leave Linux users without clear guidance.
Recommendations
  • Add explicit statements clarifying whether standalone clusters are supported on Linux, and if not, state this clearly at the top of the article.
  • If Linux support exists, provide parallel Linux-specific upgrade and configuration instructions, or link to relevant Linux documentation.
  • For features like the Patch Orchestration Application, clarify if there is a Linux equivalent or explicitly state that it is Windows-only.
  • Ensure that examples and references are balanced between Windows and Linux, or explain platform limitations up front.
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-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides code examples for scaling Service Fabric services using C# and PowerShell, but does not include equivalent Linux CLI (e.g., Azure CLI, Bash) examples. PowerShell, a Windows-centric tool, is used exclusively for command-line operations, and there is no mention of Linux-native tools or commands. This creates friction for Linux users who may not use PowerShell or develop on Windows.
Recommendations
  • Add Azure CLI or Bash examples for all PowerShell command snippets (e.g., using 'az sf service update' or 'az sf service create').
  • Explicitly mention Linux support and provide guidance for Linux users where platform differences exist.
  • Where PowerShell is referenced, clarify if cross-platform PowerShell Core is supported, or provide alternatives.
  • Include notes or links to Linux-specific Service Fabric documentation or tools.
GitHub Create Pull Request
Service Fabric Learn more about Azure Service Fabric ...icles/service-fabric/service-fabric-content-roadmap.md
Medium Priority View Details →
Scanned: 2026-02-09 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 notable Windows bias: Windows-specific tools (e.g., PowerShell, Visual Studio) are mentioned before Linux equivalents, and examples or instructions for Linux are often missing or less prominent. Standalone cluster creation is described only for Windows, with Linux standalone clusters explicitly not supported. References to Windows services and executables (FabricHost.exe, etc.) are frequent, and PowerShell is often listed first among management tools. Linux support is acknowledged, but practical parity in examples and guidance is lacking.
Recommendations
  • Add equivalent Linux examples and instructions wherever Windows-specific steps are described (e.g., cluster creation, management, scaling).
  • Mention Linux CLI tools (e.g., sfctl) and bash scripting alongside PowerShell, and provide sample commands for both platforms.
  • Clarify when features are Windows-only and provide alternative guidance for Linux users where possible.
  • Highlight Linux support earlier in relevant sections, and ensure that Linux users are guided to appropriate resources.
  • Provide links to Linux-specific tutorials and troubleshooting guides.
GitHub Create Pull Request
Service Fabric Azure Service Fabric DNS service ...n/articles/service-fabric/service-fabric-dnsservice.md
Medium Priority View Details →
Scanned: 2026-02-09 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 (e.g., Bash, Azure CLI) examples. Windows-centric tools and patterns (PowerShell, ApplicationManifest.xml, Visual Studio) are mentioned first or exclusively, while Linux support is described as limited and lacks practical guidance. There are no Linux-specific instructions or examples for enabling or configuring DNS service, especially for containerized workloads.
Recommendations
  • Add Azure CLI or Bash examples for setting DNS names and managing Service Fabric services, especially for Linux clusters.
  • Include instructions for Linux users on how to enable DNS service (e.g., via ARM templates or CLI), highlighting any differences or limitations.
  • Mention and demonstrate Linux-friendly editors and workflows (e.g., VS Code, nano, vim) for editing manifest files.
  • Clarify any Linux-specific steps or caveats, such as how to verify DNS service status or troubleshoot issues on Linux clusters.
  • Where PowerShell is used, provide equivalent commands for Linux environments if possible.
GitHub Create Pull Request
Service Fabric Health monitoring in Service Fabric ...s/service-fabric/service-fabric-health-introduction.md
Medium Priority View Details →
Scanned: 2026-02-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides a PowerShell-only example for reporting and evaluating application health in Service Fabric, without offering equivalent Linux/macOS CLI or REST API examples. While Service Fabric is cross-platform, the exclusive use of PowerShell in the example creates friction for Linux/macOS users.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl) for Linux/macOS environments.
  • Include REST API examples for health reporting and querying, which are platform-agnostic.
  • Clearly indicate that PowerShell is just one option, and reference cross-platform tools earlier in the section.
  • Provide links or inline examples for Linux/macOS users to accomplish the same tasks.
GitHub Create Pull Request
Service Fabric Azure Service Fabric hosting model ...rticles/service-fabric/service-fabric-hosting-model.md
Medium Priority View Details →
Scanned: 2026-02-09 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 examples and references Service Fabric PowerShell cmdlets prominently, without providing equivalent Linux CLI (e.g., Bash, sfctl) or cross-platform guidance. Windows/PowerShell tools are mentioned first and exclusively in several sections, creating friction for Linux/macOS users who may need to use sfctl or REST APIs instead.
Recommendations
  • Add equivalent Linux/macOS command-line examples using sfctl (Service Fabric CLI) alongside PowerShell examples.
  • Explicitly mention that PowerShell examples are Windows-centric and provide links or guidance for Linux/macOS users.
  • Where REST API or FabricClient examples are given, clarify their cross-platform applicability.
  • Update 'Next steps' and operational sections to include Linux/macOS management options, not just PowerShell.
  • Consider a table or section summarizing management tool parity (PowerShell vs sfctl vs REST).
GitHub Create Pull Request
Service Fabric Azure Service Fabric container application manifest examples ...abric/service-fabric-manifest-example-container-app.md
Medium Priority View Details →
Scanned: 2026-02-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page provides manifest examples and explanations for Azure Service Fabric container applications. The examples and narrative are based on the Windows Server 2016 Container Sample, with explicit references to Windows paths (e.g., 'c:\VolumeTest\Data'), Windows-specific commands (e.g., 'winver'), and Windows build versions. There is no mention of Linux container equivalents, Linux paths, or Linux-specific configuration patterns. While some features (like certificate handling) acknowledge Linux (PEM files), the overall examples and guidance are Windows-centric, and Linux users are left to infer how to adapt the manifests for their environment.
Recommendations
  • Provide equivalent manifest examples for Linux containers, including Linux file paths and volume mounts.
  • Include instructions or references for obtaining OS build/version information on Linux (e.g., 'cat /etc/os-release' or 'uname -r').
  • Clarify which manifest settings and patterns are cross-platform and which are Windows-specific.
  • Add links or references to Linux container samples for Service Fabric.
  • Explicitly note any differences in resource governance, certificate handling, or isolation modes between Windows and Linux clusters.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Events ...es/service-fabric/service-fabric-diagnostics-events.md
Medium Priority View Details →
Scanned: 2026-02-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page for Azure Service Fabric Events primarily references Windows-centric logging mechanisms (ETW/Windows Event logs, Windows Azure diagnostics agent) and does not mention Linux equivalents or provide Linux-specific guidance. Windows tools and patterns are mentioned first and exclusively, with no examples or instructions for accessing Service Fabric events on Linux clusters.
Recommendations
  • Add documentation about how Service Fabric events are logged and accessed on Linux clusters, including supported logging mechanisms (e.g., stdout, syslog, Azure Monitor integration).
  • Include examples or references for Linux-based monitoring tools and how to configure diagnostics on Linux nodes.
  • Clarify which features or instructions are Windows-only and provide Linux alternatives where possible.
  • Ensure parity in example commands and tool references for both Windows and Linux environments.
GitHub Create Pull Request
Service Fabric Azure Service Fabric hosting activation and deactivation life cycle ...les/service-fabric/service-fabric-hosting-lifecycle.md
Medium Priority View Details →
Scanned: 2026-02-09 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 Azure Service Fabric hosting activation and deactivation life cycle contains a notable bias toward Windows/PowerShell usage. The only explicit tooling example for deploying or managing Service Fabric applications is via PowerShell, and the 'Next steps' section links to PowerShell-based deployment/removal instructions. There are no Linux/Bash/CLI equivalents or mentions of cross-platform tools, which may hinder Linux/macOS users.
Recommendations
  • Add equivalent examples or references for Linux/macOS users, such as using Azure CLI, Bash scripts, or Service Fabric CLI (sfctl) where applicable.
  • In the 'Next steps' section, provide links to documentation for deploying/removing applications using cross-platform tools (e.g., sfctl, Azure CLI) in addition to PowerShell.
  • Where PowerShell cmdlets are referenced (such as in [p1]), clarify if there are cross-platform alternatives, and link to them.
  • Consider including a note early in the article clarifying which tools are cross-platform and which are Windows-only.
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-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page frequently references PowerShell and Visual Studio for interacting with the ImageStoreConnectionString, both of which are traditionally Windows-centric tools. Examples and next steps focus on PowerShell, with no mention of Linux/macOS equivalents (such as Azure CLI, Bash, or cross-platform .NET Core tools). This creates friction for users on non-Windows platforms, as they may not know how to retrieve or set the connection string without Windows tools.
Recommendations
  • Add examples for retrieving and setting the ImageStoreConnectionString using Azure CLI, Bash, or REST API, which are cross-platform.
  • Include instructions or links for deploying applications from Linux/macOS environments.
  • Clarify which tools and workflows are available on non-Windows platforms, and provide parity where possible.
  • Mention .NET Core-based approaches if relevant, as these are cross-platform.
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-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page provides Service Fabric application and service manifest examples, but it exhibits mild Windows bias. Windows concepts (such as local admin accounts, NetworkService, Setup.bat, and references to ServiceFabric PowerShell module) are mentioned without Linux equivalents or alternatives. The manifest examples use Windows-centric terminology and tools (e.g., .bat files, NetworkService), and instructions reference Windows user/group patterns. There are no explicit Linux examples or notes about cross-platform differences.
Recommendations
  • Add explicit notes or examples for Linux deployments, such as using shell scripts (.sh) instead of .bat files for SetupEntryPoint.
  • Clarify how user accounts and groups are handled on Linux clusters, and provide equivalent manifest snippets.
  • Mention Linux-specific service accounts (e.g., 'sfuser') or patterns where relevant.
  • Where PowerShell is referenced, add equivalent CLI or bash commands for Linux users.
  • Document any limitations or differences in resource governance, security, and endpoint configuration between Windows and Linux clusters.
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-09 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 'Replica soft delete for enhanced data protection in Service Fabric' demonstrates a notable Windows/PowerShell bias. All command-line/API examples reference PowerShell cmdlets (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica, Get-ServiceFabricReplica), with no mention of equivalent CLI commands, REST APIs, or Linux/macOS tooling. The documentation assumes the use of PowerShell and does not provide guidance or examples for Linux users, despite Service Fabric supporting cross-platform clusters.
Recommendations
  • Include equivalent examples using Service Fabric CLI (sfctl) or REST APIs where available, alongside PowerShell examples.
  • Explicitly mention if certain APIs or features are only available via PowerShell, and provide Linux/macOS alternatives or workarounds if possible.
  • Add a section or callout clarifying cross-platform support and how Linux/macOS users can perform the same operations.
  • Reference documentation for managing Service Fabric clusters from Linux/macOS environments.
GitHub Create Pull Request
Service Fabric Fault Analysis Service overview .../service-fabric/service-fabric-testability-overview.md
Medium Priority View Details →
Scanned: 2026-02-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides explicit instructions for using the Fault Analysis Service with PowerShell and references the Service Fabric SDK, which is primarily Windows-focused. There are no examples or guidance for Linux/macOS users, such as using the Service Fabric CLI (sfctl) or REST APIs, nor is there mention of cross-platform tooling. This creates friction for non-Windows users.
Recommendations
  • Add examples for using the Fault Analysis Service with sfctl (Service Fabric CLI), which is cross-platform.
  • Include references or examples for using the REST API to interact with the Fault Analysis Service.
  • Clarify which features are available on Linux clusters and provide parity in documentation where possible.
  • Explicitly state any Windows-only limitations, if applicable, to set expectations for Linux/macOS users.
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-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation provides comprehensive coverage of both Kestrel (cross-platform) and HTTP.sys (Windows-only) web servers for ASP.NET Core integration with Azure Service Fabric Reliable Services. However, there is a notable Windows bias in several areas: HTTP.sys (a Windows-only technology) is discussed in depth, with explicit mention of Windows-specific tools (netsh), kernel drivers, and endpoint configuration. Windows-specific details and examples (such as HTTP.sys usage and endpoint registration) are presented before Linux equivalents, and Windows tools are referenced without Linux alternatives. While Kestrel is recommended for Linux and cross-platform scenarios, the documentation sometimes leads with Windows-centric approaches and does not always clarify Linux-specific setup or troubleshooting. There are no PowerShell scripts or commands, but the use of Windows tools and APIs is prominent.
Recommendations
  • Ensure that Linux/macOS users are explicitly guided on how to configure endpoints and ports for Kestrel, including any OS-specific firewall or networking considerations.
  • When referencing Windows tools (such as netsh), provide a note or alternative for Linux/macOS users, or clarify that these steps are not required for Kestrel.
  • Consider reorganizing sections so that cross-platform solutions (Kestrel) are discussed before Windows-only solutions (HTTP.sys), or clearly mark Windows-only content.
  • Add troubleshooting tips or common issues for Linux/macOS users running Service Fabric Reliable Services with ASP.NET Core.
  • Explicitly state which features or examples are Windows-only, and which are cross-platform, to avoid confusion.
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-09 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 reporting health in Service Fabric, but does not include equivalent Linux/macOS CLI examples (such as Azure CLI, Bash, or cross-platform tools). PowerShell is presented as the primary scripting interface, and Windows-style paths and prompts are used. REST and API usage are described, but scripting and command-line examples are Windows-centric.
Recommendations
  • Add equivalent examples using Azure CLI or Bash scripts for Linux/macOS users.
  • Clarify whether PowerShell Core (cross-platform) is supported, and provide examples if so.
  • Mention any Linux-specific Service Fabric tools or commands, or note if PowerShell cmdlets are available on Linux.
  • Reorder sections so that REST and API examples are presented before PowerShell, or present them together 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-02-09 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 build/deploy actions (F5/Ctrl+F5/Publish) and GUI interactions. There are no Linux/macOS equivalents or CLI examples for managing StartupServices.xml, and PowerShell is mentioned as a way to create service instances, but no Linux tools or commands are provided. The documentation assumes use of Visual Studio, which is primarily a Windows tool.
Recommendations
  • Add guidance for Linux/macOS users, such as how to manage StartupServices.xml using CLI tools (e.g., Azure CLI, Service Fabric CLI, or PowerShell Core on Linux).
  • Provide examples for deploying and configuring Service Fabric applications without Visual Studio, including relevant commands and scripts.
  • Clarify which features are Visual Studio/Windows-only and offer alternative workflows for cross-platform users.
  • Mention any limitations or differences for Linux/macOS users explicitly, so expectations are clear.
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-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page is generally cross-platform and describes Service Fabric concepts applicable to both Windows and Linux. However, some terminology and examples, such as references to 'auto-start Windows service' and EXE/DLL files, are Windows-centric and appear before Linux equivalents. The mention of Windows-specific executables and services (e.g., FabricHost.exe, Fabric.exe, FabricGateway.exe) is prominent, and Linux equivalents or clarifications are not provided in those sections. The page does acknowledge Linux support for containers and guest executables, but Windows terminology and tools are presented first and more frequently.
Recommendations
  • Where Windows-specific services or executables are mentioned (e.g., FabricHost.exe), clarify if/how these concepts apply on Linux nodes, or explicitly state differences.
  • When describing code packages, supplement EXE/DLL references with Linux equivalents (e.g., ELF binaries, .so files) to improve parity.
  • In sections referencing Windows services, add notes or examples for Linux (e.g., systemd services or relevant Linux process management).
  • Ensure that descriptions of cluster nodes, application packaging, and deployment reference both Windows and Linux environments equally, or provide links to Linux-specific documentation where appropriate.
GitHub Create Pull Request
Service Fabric Service Fabric Explorer blocking operations ...ged-cluster-service-fabric-explorer-blocking-operation.md
Medium Priority View Details →
Scanned: 2026-02-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides management guidance for Service Fabric Explorer and ARM-managed clusters. It consistently recommends Az PowerShell cmdlets for resource operations, mentioning them before or instead of Azure CLI equivalents. While Azure CLI is referenced once for deleting applications, most examples and links are PowerShell-focused, which may create friction for Linux/macOS users who prefer or require CLI tools.
Recommendations
  • Provide Azure CLI equivalents for all PowerShell cmdlet examples, especially for provisioning and deleting resources.
  • Mention both PowerShell and CLI options equally in best practices sections.
  • Clarify that Az PowerShell cmdlets are cross-platform, but highlight CLI usage for Linux/macOS users.
  • Add explicit examples for ARM template deployment using CLI tools.
GitHub Create Pull Request
Service Fabric Describing Azure Service Fabric apps and services ...ic/service-fabric-application-and-service-manifests.md
Medium Priority View Details →
Scanned: 2026-02-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation contains a notable Windows bias in its guidance for validating manifest XML files, specifically recommending opening the schema file in Visual Studio using a Windows file path. The only explicit tool and workflow mentioned for schema validation is Windows/Visual Studio-centric, with no mention of cross-platform alternatives. Additionally, the PowerShell module is referenced before any Linux or cross-platform equivalents for service creation.
Recommendations
  • Provide instructions or examples for validating manifest XML files using cross-platform tools (e.g., xmllint, VS Code with XML extensions, or other schema validation tools available on Linux/macOS).
  • When referencing the Service Fabric PowerShell module, also mention the Service Fabric CLI (sfctl) or Azure CLI as cross-platform alternatives for managing services.
  • Where file paths or tooling are given, clarify if the guidance is Windows-specific and offer Linux/macOS equivalents if available.
  • Consider adding a note that Service Fabric development is supported on both Windows and Linux, and link to platform-specific setup guides.
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-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides both Windows and Linux guidance for Azure Service Fabric networking, but there is a notable Windows bias. PowerShell and Windows-specific tools are referenced more frequently, and Windows examples or terminology often appear before Linux equivalents. Some explanations (e.g., client API usage, DevOps tasks) focus on PowerShell, and sample ARM templates link to Windows-specific resources. Linux is mentioned, but often as an afterthought or secondary option.
Recommendations
  • Provide Linux CLI (az CLI or bash) examples alongside PowerShell, especially for cluster management and networking tasks.
  • Reference Linux ARM template samples equally, not just Windows ones.
  • Clarify when instructions or port requirements differ for Linux clusters (e.g., ephemeral ports section).
  • Expand explanations of DevOps and client API usage to include Linux tooling (e.g., Azure CLI, REST, bash scripts).
  • Ensure Linux and Windows guidance appear together, or alternate which is presented first.
GitHub Create Pull Request
← Previous Page 70 of 99 Next →