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 1901-1925 of 2475 flagged pages
Service Fabric Service Fabric Cluster Resource Manager - Placement Policies ...ce-manager-advanced-placement-rules-placement-policies.md
Medium Priority View Details →
Scanned: 2026-02-04 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation consistently provides PowerShell examples for configuring Service Fabric placement policies, with no equivalent examples for Linux/macOS users (e.g., CLI, REST, or YAML). PowerShell is a Windows-centric tool, and its exclusive use may create friction for users managing Service Fabric clusters from Linux or macOS environments. Additionally, PowerShell examples are presented immediately after C# code samples, reinforcing a Windows-first approach.
Recommendations
  • Include Azure CLI examples for each placement policy, as Azure CLI is cross-platform and commonly used on Linux/macOS.
  • Document REST API approaches for configuring placement policies, if available.
  • Clarify whether PowerShell commands are supported on Linux/macOS (via PowerShell Core), and provide guidance for non-Windows users.
  • Add a note or section outlining how Linux/macOS users can perform equivalent operations, or explicitly state if certain management operations are Windows-only.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager - Application Groups ...ice-fabric-cluster-resource-manager-application-groups.md
Medium Priority View Details →
Scanned: 2026-02-04 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page provides only PowerShell and C# examples for managing Service Fabric Application Groups, with no mention of Linux CLI equivalents or cross-platform tooling. PowerShell is a Windows-centric tool, and its exclusive use in examples creates friction for Linux/macOS users who may prefer Azure CLI, REST API, or Service Fabric CLI (sfctl). There is no explicit indication that the Application Groups feature is Windows-only, so the lack of Linux-friendly instructions is a notable bias.
Recommendations
  • Add equivalent examples using Azure CLI, REST API, or Service Fabric CLI (sfctl), which are cross-platform and usable on Linux/macOS.
  • Explicitly mention platform compatibility for PowerShell commands and provide guidance for Linux/macOS users.
  • Include a table or section summarizing all available management tools for Application Groups, indicating which are cross-platform.
  • Where possible, link to documentation for Linux/macOS setup and usage of Service Fabric management tools.
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-04 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page provides general information about Service Fabric node types and VM scale sets, but several examples and references default to Windows-centric patterns. The JSON extension snippet uses a Windows-style data path (D:\\SvcFab) without a Linux equivalent, and the 'Next steps' section links to PowerShell scripts for RDP port and admin credential changes, which are Windows-specific operations. There are no explicit Linux examples or guidance for Linux users, despite Service Fabric supporting Linux nodes.
Recommendations
  • Provide Linux-specific examples alongside Windows ones, such as using a Linux-style data path (e.g., /var/svcfab) in the extension snippet.
  • Clarify which operations (like RDP port changes) are Windows-only, and offer SSH-based guidance for Linux nodes where appropriate.
  • Include links to Linux-relevant documentation in the 'Next steps' section, such as SSH connection instructions and Linux admin credential management.
  • Explicitly state OS-specific differences in configuration properties, especially where defaults or examples are Windows-centric.
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-04 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides a detailed conceptual overview of Cluster Resource Manager integration with Service Fabric management. However, the only command-line example shown uses Windows PowerShell (Get-ServiceFabricPartitionHealth), with no equivalent CLI or Linux/macOS example. This may create friction for users managing Service Fabric clusters from non-Windows environments.
Recommendations
  • Include equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • Explicitly mention how Linux/macOS users can retrieve partition health and interact with the Cluster Resource Manager.
  • Where PowerShell is used, add a note or link to cross-platform alternatives.
  • Consider listing both Windows and Linux/macOS command examples side-by-side for parity.
GitHub Create Pull Request
Service Fabric Manage Azure Service Fabric app load using metrics ...ric/service-fabric-cluster-resource-manager-metrics.md
Medium Priority View Details →
Scanned: 2026-02-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 both C# and PowerShell examples for managing Service Fabric metrics, but all command-line examples use PowerShell exclusively, with no mention of Linux equivalents (such as Azure CLI, Bash, or REST API). PowerShell is a Windows-centric tool, and its exclusive use creates friction for Linux/macOS users. Additionally, PowerShell examples are presented before any mention of cross-platform alternatives, and there is no guidance for Linux users on how to perform these operations.
Recommendations
  • Add equivalent Azure CLI or REST API examples for service creation and metric management, which are cross-platform and usable on Linux/macOS.
  • Explicitly mention which tools are available for Linux/macOS users and provide links to relevant documentation.
  • Where PowerShell is used, clarify its platform limitations and suggest alternatives for non-Windows environments.
  • Consider including Bash script examples or instructions for using Service Fabric SDK tools on Linux.
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-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 scaling Azure Service Fabric standalone clusters demonstrates Windows bias by exclusively referencing PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) and linking to Windows Server-specific guides. There are no Linux or cross-platform examples, nor any mention of Linux-compatible tools or workflows for cluster scaling, despite Service Fabric standalone clusters being deployable on both Windows and Linux.
Recommendations
  • Include equivalent Linux instructions and examples, such as using Service Fabric CLI (sfctl) or REST APIs for cluster management.
  • Reference Linux-compatible tools and workflows for querying and updating cluster configuration.
  • Add links to documentation for scaling Service Fabric standalone clusters on Linux.
  • Clearly indicate which steps or tools are Windows-only, and provide alternatives for Linux users 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-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 PowerShell examples for configuring Service Fabric service move cost, but does not offer equivalent Linux/macOS CLI (e.g., Bash, Azure CLI, or SFCTL) examples. PowerShell is primarily a Windows tool, and its exclusive use creates friction for Linux/macOS users. The absence of cross-platform command-line instructions means Linux users may struggle to perform these operations without additional research.
Recommendations
  • Add equivalent examples using Azure CLI or SFCTL (Service Fabric CLI), which are cross-platform and supported on Linux/macOS.
  • Clearly indicate whether PowerShell commands can be run on Linux/macOS (e.g., via PowerShell Core), or provide links to relevant installation guides.
  • Where possible, show both Windows (PowerShell) and Linux/macOS (Bash/Azure CLI/SFCTL) command examples side-by-side.
  • Reference official documentation for Service Fabric CLI usage for service creation and update tasks.
GitHub Create Pull Request
Service Fabric Service sensitivity ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-sensitivity.md
Medium Priority View Details →
Scanned: 2026-02-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 configuration examples using XML, JSON, PowerShell, and C# APIs. However, all command-line examples use PowerShell, which is Windows-centric, and there are no equivalent CLI or scripting examples for Linux/macOS users (e.g., Azure CLI, Bash, or REST API). PowerShell examples are presented before C# API examples, reinforcing a Windows-first approach.
Recommendations
  • Add equivalent Azure CLI or REST API examples for configuring service sensitivity and maximum load, suitable for Linux/macOS users.
  • Clarify whether PowerShell commands can be run cross-platform (e.g., with PowerShell Core), or provide Bash scripting alternatives if possible.
  • Explicitly mention Linux/macOS support and provide guidance for users managing Service Fabric clusters from non-Windows environments.
  • Consider reordering examples so that platform-neutral methods (e.g., REST API, JSON manifest edits) are shown before Windows-specific 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-02-04 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides security guidance for Azure Service Fabric clusters and standalone clusters, but consistently references Windows Server clusters when discussing standalone deployments. All example links for standalone clusters point to Windows-specific guides, and Windows authentication (Kerberos) is discussed without mention of Linux equivalents. There is no explicit guidance or examples for securing standalone Linux clusters, nor are Linux authentication patterns or tools mentioned. The document does state that the concept of secure clusters is the same for Linux or Windows, but does not provide Linux-specific instructions or parity in examples.
Recommendations
  • Add explicit guidance and example links for securing standalone Service Fabric clusters on Linux, including certificate setup and authentication patterns.
  • Include Linux-specific instructions or references for node-to-node and client-to-node security, such as relevant Linux tools for certificate management and authentication.
  • Clarify any differences or limitations for Linux clusters, and provide parity in documentation structure and examples.
  • If standalone Linux clusters are not supported, state this clearly to avoid confusion.
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-04 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides upgrade guidance for Azure Service Fabric clusters and generally presents platform-neutral instructions. However, in sections about managing certificates and opening application ports, PowerShell is mentioned before Azure CLI, and there is no explicit mention of Linux/macOS command-line usage or examples. The link for OS patching refers specifically to Windows ('Patch the Windows operating system in your Service Fabric cluster'), and Patch Orchestration Application (POA) is described only in the context of Windows. There are no Linux-specific upgrade instructions or parity notes for OS patching, which may create friction for Linux cluster operators.
Recommendations
  • Explicitly mention and provide Azure CLI examples alongside PowerShell for all management tasks, especially for certificate and port management.
  • Clarify whether Patch Orchestration Application (POA) and OS image upgrades are available for Linux-based Service Fabric clusters, and provide links or instructions for Linux if supported.
  • Add notes or sections indicating any differences or limitations for Linux clusters, or confirm parity where it exists.
  • Where possible, avoid listing PowerShell before Azure CLI, or alternate the order to avoid implicit Windows-first bias.
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-04 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation references PowerShell as the primary example for retrieving the cluster manifest and links to a PowerShell-based deployment guide as the next step. While .NET and REST are mentioned as alternatives, PowerShell is presented first and most prominently. There are no explicit Linux/macOS CLI examples or guidance for cross-platform tools, which may create friction for non-Windows users.
Recommendations
  • Add Azure CLI or Service Fabric CLI (sfctl) examples for retrieving the cluster manifest and managing deployments, as these are cross-platform.
  • Include explicit instructions or links for Linux/macOS users where PowerShell is referenced, such as using PowerShell Core or alternative tools.
  • Balance example ordering so that cross-platform options (e.g., REST, CLI) are presented alongside or before Windows-specific tools.
  • Clarify that PowerShell examples can be run on Linux/macOS using PowerShell Core, if applicable.
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-04 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 exhibits a moderate Windows bias. Key upgrade and configuration instructions link 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 described only for Windows, with no mention of Linux equivalents or guidance. There are no explicit Linux examples, and Windows terminology/tools are referenced without Linux parity.
Recommendations
  • Add or link to equivalent Linux upgrade and configuration documentation if Service Fabric standalone clusters are supported on Linux.
  • Provide Linux-specific examples and instructions for cluster upgrades, configuration changes, and patch orchestration.
  • Clarify in the introduction if Service Fabric standalone clusters are Windows-only, or explicitly state platform support.
  • If Linux is not supported, state this clearly to avoid confusion for non-Windows 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-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 demonstrates a notable Windows bias. All command-line deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) without mention of Azure CLI equivalents. The application packaging workflow is shown using Visual Studio, a Windows-centric tool, with no alternative for Linux/macOS users. No Linux/macOS-specific instructions or examples are provided for key steps such as packaging, uploading, or deploying applications.
Recommendations
  • Add Azure CLI examples for deployment and resource management alongside PowerShell examples.
  • Include instructions for packaging Service Fabric applications using cross-platform tools (e.g., dotnet CLI, SF SDK for Linux/macOS) instead of only Visual Studio.
  • Provide guidance or links for Linux/macOS users on how to zip and rename application packages, and upload them to Azure Storage using CLI or portal.
  • Explicitly state which steps are cross-platform and which are Windows-specific, to help users on non-Windows systems navigate the process.
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-04 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 demonstrates a moderate Windows bias. It references Windows-specific event logging mechanisms (ETW/Windows Event logs) and the Windows Azure diagnostics agent as the default method for collecting and forwarding events. There is no mention of Linux equivalents, nor are Linux-specific event collection or monitoring patterns discussed. The examples and instructions assume a Windows environment, potentially creating friction for Linux-based Service Fabric clusters.
Recommendations
  • Add documentation about how Service Fabric events are logged and accessed on Linux clusters, including supported logging mechanisms (e.g., syslog, journald, or custom log files).
  • Provide Linux-specific examples for event collection, forwarding, and integration with Azure Monitor or other monitoring tools.
  • Clarify which features or instructions are Windows-only, and offer alternative guidance for Linux users where possible.
  • Include a comparison table or section outlining differences in diagnostics between Windows and Linux clusters.
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-04 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page on Service Fabric scalability provides both C# and PowerShell examples for scaling operations, but exclusively uses PowerShell for command-line examples, which is a Windows-centric tool. References to administrative actions and tooling (e.g., New-ServiceFabricService) are PowerShell-focused, with no mention of Linux-native equivalents (such as Bash, CLI, or REST API usage). Windows tooling is presented first and exclusively, creating friction for Linux users who may not use PowerShell.
Recommendations
  • Add equivalent Linux command-line examples using Azure CLI, Bash scripts, or REST API calls for service and application management.
  • Explicitly mention cross-platform management options and tooling, such as the Service Fabric CLI (sfctl), and provide usage examples.
  • Where PowerShell is referenced, clarify its platform limitations and suggest alternatives for Linux/macOS users.
  • Reorder or balance example order so that Windows and Linux approaches are presented with equal prominence.
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-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 are multiple instances where Windows concepts, tools, and examples are presented first or exclusively. For example, references to cluster nodes mention auto-start Windows services and Windows executables before mentioning Linux support. PowerShell is listed first among management tools, and standalone cluster creation is only described for Windows, with Linux standalone clusters explicitly noted as unsupported. There are few Linux-specific examples or CLI-first instructions, and Windows-centric terminology (e.g., 'Windows service', 'FabricHost.exe') is used throughout, even in general sections.
Recommendations
  • When describing cluster nodes and management, provide parallel Linux details (e.g., systemd services, Linux process names) alongside Windows information.
  • List CLI tools (sfctl) and REST APIs before or alongside PowerShell, especially in cross-platform sections.
  • Add explicit Linux examples or links for cluster creation, management, and application lifecycle wherever possible.
  • Clarify which features are Windows-only and which are cross-platform, and ensure Linux parity is highlighted where available.
  • In sections where Windows executables are mentioned, add Linux equivalents or note differences in process management.
GitHub Create Pull Request
Service Fabric Overview of Azure and standalone Service Fabric clusters ...icles/service-fabric/service-fabric-deploy-anywhere.md
Medium Priority View Details →
Scanned: 2026-02-04 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation acknowledges both Windows Server and Linux as supported platforms for Service Fabric clusters, but it notes that standalone clusters are not available on Linux. The page does not provide Linux-specific examples or guidance, and Windows is mentioned first throughout. While the page is concept-focused and not a how-to, the lack of Linux parity in standalone cluster support is a notable omission.
Recommendations
  • Clearly state the limitations for Linux users regarding standalone clusters at the beginning of the page.
  • Provide links or guidance for Linux users on alternative deployment strategies or supported scenarios.
  • Ensure that any feature comparison tables or documentation sections explicitly highlight platform differences and offer actionable next steps for Linux users.
GitHub Create Pull Request
Service Fabric Package an existing executable to Azure Service Fabric ...abric/service-fabric-guest-executables-introduction.md
Medium Priority View Details →
Scanned: 2026-02-04 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. It references Windows file paths for the Service Fabric SDK schema location, mentions Visual Studio as a primary tool, and does not provide Linux/macOS equivalents or examples. The directory structure and packaging concepts are platform-neutral, but the lack of Linux/macOS tooling guidance and examples creates friction for non-Windows users.
Recommendations
  • Include instructions or references for packaging and deploying guest executables using Linux/macOS command-line tools.
  • Mention cross-platform alternatives to Visual Studio, such as Visual Studio Code or CLI-based workflows.
  • Provide Linux/macOS file path examples for SDK schema locations, if applicable.
  • Clarify which steps are platform-agnostic and which require Windows-specific tooling.
GitHub Create Pull Request
Service Fabric Manage apps for multiple environments ...e-fabric-manage-multiple-environment-app-configuration.md
Medium Priority View Details →
Scanned: 2026-02-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 examples and tooling references that prioritize Windows/PowerShell workflows (e.g., PowerShell cmdlets, Visual Studio, Deploy-FabricApplication.ps1) and mentions them before Linux equivalents. While sfctl and Jenkins are referenced, there is a lack of explicit Linux/macOS command-line examples or parity in detail, which may create friction for non-Windows users.
Recommendations
  • Add explicit Linux/macOS command-line examples for creating applications and passing parameters, such as using sfctl with sample JSON.
  • Include step-by-step instructions for parameter substitution using common Linux tools (e.g., sed, envsubst) alongside Jenkins.
  • Clarify which scripts and workflows are cross-platform and provide alternatives where Windows-specific tooling (e.g., PowerShell scripts, Visual Studio) is mentioned.
  • Reorder examples so that cross-platform or Linux/macOS options are presented alongside or before Windows-specific ones.
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-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 predominantly references PowerShell-based administrative APIs (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica) and provides examples and links only for PowerShell usage. There is no mention of equivalent Linux/macOS command-line tools, nor are there examples using Service Fabric CLI (sfctl) or REST APIs, which are commonly used on non-Windows platforms. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer native tools.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl) for all administrative operations (remove, restore, query replicas).
  • Clarify whether PowerShell APIs are available cross-platform or provide alternative instructions for Linux/macOS users.
  • Include REST API references or examples where applicable.
  • Explicitly state platform requirements for each tool/API mentioned.
  • Add a section or note on how Linux/macOS users can perform these tasks.
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-04 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 focused on Visual Studio workflows and Windows-centric tooling (e.g., F5/Ctrl+F5/Publish, right-click Publish, Visual Studio project templates). It references PowerShell as a deployment method but does not mention or provide examples for Linux/macOS alternatives (such as Azure CLI, Bash, or cross-platform editors). There are no instructions or examples for performing equivalent tasks outside of Visual Studio or on non-Windows platforms.
Recommendations
  • Add explicit notes clarifying that StartupServices.xml is only supported for Visual Studio (Windows) deployments and is not available for Linux/macOS users.
  • Provide alternative guidance or links for Linux/macOS users on how to manage service configuration using ApplicationManifest.xml and ARM templates, Azure CLI, or other cross-platform tools.
  • Include examples or references for deploying Service Fabric applications from Linux/macOS environments, if supported, and clarify any platform limitations.
  • List non-Windows deployment options (e.g., Azure CLI, REST API) alongside PowerShell, and avoid implying PowerShell is the only method.
  • Consider reordering sections so that platform-neutral or cross-platform methods are presented before Windows/Visual Studio-specific workflows.
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-04 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page for Service Fabric reliable services app manifest examples displays moderate Windows bias. It references Windows-specific tools (e.g., PowerShell module for service creation), uses Windows-centric terminology (e.g., NetworkService, Administrators group), and provides examples using Windows batch scripts (.bat) and .exe files. There is no mention of Linux equivalents (such as shell scripts or Linux service accounts), nor are Linux-specific patterns or recommendations provided. The documentation assumes a Windows environment for service setup and execution.
Recommendations
  • Include Linux-specific examples alongside Windows ones, such as using shell scripts (.sh) for SetupEntryPoint and EntryPoint.
  • Document Linux service account equivalents and how to configure principals and policies for Linux clusters.
  • Clarify which manifest features and patterns are cross-platform and which are Windows-only, especially for RunAsPolicy and system groups.
  • Add notes or links to Linux Service Fabric documentation for users deploying on Linux clusters.
  • When referencing tools (e.g., PowerShell), mention Linux alternatives (such as Azure CLI or Service Fabric CLI).
GitHub Create Pull Request
Service Fabric Overview of Azure Service Fabric ...ain/articles/service-fabric/service-fabric-overview.md
Medium Priority View Details →
Scanned: 2026-02-04 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation generally presents Azure Service Fabric as cross-platform, mentioning both Windows and Linux support. However, there is a subtle Windows bias: Windows development tools (Visual Studio, PowerShell) are mentioned first and in more detail than Linux equivalents, and the quickstart link points to a .NET (typically Windows-centric) example without highlighting Linux or cross-platform alternatives. Linux development tools (Eclipse, Yeoman) are mentioned, but less prominently and with less detail. No explicit Linux command-line examples or Linux-specific quickstart links are provided.
Recommendations
  • Provide equal prominence and detail for Linux development workflows, including command-line examples and links to Linux-specific quickstarts.
  • Include examples or links for deploying and managing Service Fabric clusters on Linux, using Linux-native tools.
  • Ensure quickstart and getting started sections offer both Windows (.NET/PowerShell/Visual Studio) and Linux (Java/Eclipse/Yeoman/CLI) options side-by-side.
  • Clarify that .NET Core/.NET 5+ workloads are cross-platform and provide examples for both Windows and Linux environments.
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-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, there is a notable Windows bias in several areas: HTTP.sys (a Windows-only technology) receives detailed attention, including configuration and usage examples, while there are no explicit Linux/macOS-specific instructions or examples. Windows-specific tools (e.g., netsh) and APIs are referenced without Linux equivalents. In some sections, Windows/HTTP.sys is discussed before Kestrel, and the documentation does not clarify Linux/macOS limitations or provide parity guidance for those platforms.
Recommendations
  • Clearly indicate at the start of the HTTP.sys sections that it is Windows-only, and suggest Kestrel as the cross-platform alternative for Linux/macOS users.
  • Where Windows-specific tools (e.g., netsh) or APIs are mentioned, provide a note or alternative for Linux/macOS, or clarify that these steps are not required for Kestrel.
  • Add explicit Linux/macOS guidance or examples, especially for common deployment and configuration scenarios (e.g., ServiceManifest.xml for Kestrel on Linux).
  • In summary tables and recommendations, consistently list Kestrel (cross-platform) before HTTP.sys (Windows-only), and clarify platform support.
  • Add a section or callout summarizing platform support and limitations for both web servers.
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-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 detailed PowerShell examples for health reporting, with explicit Windows paths and cmdlets, but does not offer equivalent Linux or cross-platform CLI examples. PowerShell is presented before REST, and there is no mention of Service Fabric CLI (sfctl) or Bash scripting, which are common on Linux/macOS. This creates friction for non-Windows users who may not have access to PowerShell or prefer platform-agnostic tools.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • Include Bash or shell script examples for common health reporting tasks.
  • Clarify which tools are available on each platform and recommend REST or CLI for Linux/macOS users.
  • Reorder sections so REST and CLI examples are presented before or alongside PowerShell, to avoid Windows-first impression.
  • Explicitly state PowerShell examples are for Windows, and provide guidance for Linux/macOS users.
GitHub Create Pull Request
← Previous Page 77 of 99 Next →