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 251-275 of 2475 flagged pages
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-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides several manual scaling instructions that rely exclusively on PowerShell cmdlets (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState) without mentioning or providing equivalent Linux/bash/CLI commands. There are no bash, Azure CLI, or cross-platform alternatives shown for these critical operations, which may create friction for Linux/macOS users managing Service Fabric clusters.
Recommendations
  • Provide equivalent Azure CLI or REST API examples for all PowerShell commands used in scaling operations.
  • Explicitly mention if certain operations can only be performed via PowerShell, and suggest alternatives or workarounds for Linux/macOS users.
  • Add bash or cross-platform scripting examples where possible, especially for cluster management tasks.
  • Clarify in each section whether the instructions are valid for both Windows and Linux clusters, or if there are differences.
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-03-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation provides some evidence of Windows bias. The 'dataPath' example in the extension snippet uses a Windows-style path (D:\\SvcFab) without a Linux equivalent. The 'Next steps' section links to PowerShell scripts for changing RDP port ranges and admin credentials, which are Windows-centric tasks and tools, and does not mention Linux/SSH equivalents or guidance. While the extension snippet does mention both 'ServiceFabricLinuxNode' and 'ServiceFabricNode', the practical examples and follow-up tasks are Windows-focused.
Recommendations
  • Provide Linux-style path examples (e.g., /var/lib/sf) alongside Windows paths in the extension snippet.
  • Include or link to Linux/SSH-based instructions for remote connection, port management, and credential changes in the 'Next steps' section.
  • Clarify when instructions or scripts are Windows-only, and offer Linux alternatives where possible.
  • Balance PowerShell/Windows tool references with Bash/SSH/Linux tool equivalents.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager - Placement Policies ...ce-manager-advanced-placement-rules-placement-policies.md
Medium Priority View Details →
Scanned: 2026-03-08 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 code samples for placement policies in C# and PowerShell, but does not include equivalent examples for Linux/macOS environments (e.g., Bash, CLI, or REST API). PowerShell is a Windows-centric tool and is presented as the primary scripting method for service configuration, with no mention of cross-platform alternatives. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other tools.
Recommendations
  • Add Azure CLI or REST API examples for configuring placement policies, as these are cross-platform and accessible from Linux/macOS.
  • Explicitly mention whether PowerShell examples are usable on Linux (via PowerShell Core), or provide Bash scripts if possible.
  • Clarify any platform-specific requirements for Service Fabric management tools, and link to documentation for Linux/macOS users.
  • Consider including a table or section comparing Windows and Linux management approaches for Service Fabric clusters.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Auto Scaling Services and Containers ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-autoscaling.md
Medium Priority View Details →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides example code for configuring auto scaling policies in Azure Service Fabric using application manifests, C# APIs, and PowerShell. However, all CLI/script examples are PowerShell-based, with no equivalent Bash or Linux CLI examples. PowerShell is shown as the only scripting interface, and there is no mention of Linux-native tools or commands. While Service Fabric supports Linux containers, the documentation does not demonstrate how Linux users can configure auto scaling from the command line, creating friction for non-Windows users.
Recommendations
  • Add Bash or Azure CLI examples for configuring scaling policies, especially for Linux-based clusters.
  • Mention cross-platform tools (e.g., Azure CLI, REST API) where applicable, and provide links or examples.
  • Clarify which PowerShell commands are available via Azure CLI or REST API for Linux users.
  • Explicitly note any limitations or differences for Linux clusters in relevant sections.
GitHub Create Pull Request
Service Fabric Azure Service Fabric infrastructure as Code Best Practices ...tps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-best-practices-infrastructure-as-code.md
Medium Priority View Details →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Service Fabric clusters, but PowerShell (a Windows-centric tool) is given a dedicated section and detailed usage, while Linux-native alternatives (like Bash scripting or Linux-specific deployment steps) are not shown. For cluster upgrades, only PowerShell commands are provided, with no Linux equivalent (e.g., Bash or sfctl). Windows-specific configuration (such as registry keys and Windows Update settings) is discussed in detail, while Linux equivalents are not mentioned or are missing. In several sections, Windows tools and patterns are discussed before or instead of Linux options.
Recommendations
  • Provide Linux-native command examples (e.g., Bash scripts, sfctl usage) alongside PowerShell for cluster management and upgrades.
  • Include Linux-specific configuration guidance for patch management and OS upgrades, such as disabling unattended-upgrades or equivalent settings.
  • When referencing registry keys or Windows Update settings, add parallel instructions for Linux (if applicable), or clarify when a step is Windows-only.
  • Balance the order of presentation so that Linux and Windows examples are given equal prominence.
  • Where only Windows instructions are possible, explicitly state that the step is Windows-only and provide links to Linux documentation if available.
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-03-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 are several areas where Windows bias is evident. PowerShell and Windows tools are referenced more frequently and often appear first. Some examples and links (e.g., ARM templates, network configuration, DevOps tasks) are Windows-centric or reference Windows-specific tooling before Linux equivalents. The Client API port is described as 'used by PowerShell', and Azure DevOps classic tasks are discussed primarily in a Windows context. However, Linux support is acknowledged and included in key sections.
Recommendations
  • Provide Linux CLI examples alongside PowerShell examples wherever possible, especially for cluster management and networking tasks.
  • When referencing ARM templates or sample clusters, include links to Linux-focused templates in addition to Windows ones.
  • Clarify when guidance applies equally to both Windows and Linux, and avoid phrasing that implies Windows is the default (e.g., 'Client API used by PowerShell' should mention Linux CLI usage as well).
  • Ensure DevOps and operational guidance includes Linux agent/task scenarios, not just classic PowerShell tasks.
  • When listing tools (e.g., reverse proxy), mention Linux-native options and usage patterns explicitly.
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-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page lists Service Fabric cluster settings in a platform-neutral way, but there are several signs of Windows bias. Windows terminology (e.g., 'certificate store', 'MY', 'LocalMachine'), Windows-specific defaults, and references to Windows tools (such as NTLM authentication, Windows Defender Firewall, and Windows log paths) appear throughout. Where Linux equivalents exist, they are sometimes mentioned second or not at all. Some settings are described as 'Windows only' without Linux alternatives or guidance. There are no explicit Linux/macOS configuration examples or clarifications for cross-platform differences, which may create friction for non-Windows users.
Recommendations
  • For each setting that references Windows-specific concepts (e.g., certificate stores, NTLM, log paths), add Linux/macOS equivalents or clarify if the setting is not applicable.
  • Where settings are 'Windows only', explicitly state Linux/macOS alternatives or limitations.
  • Provide Linux/macOS configuration examples, especially for certificate management, log locations, and firewall settings.
  • Review default values and descriptions to ensure Linux defaults are documented equally.
  • Add a summary table or section highlighting platform-specific differences for key settings.
GitHub Create Pull Request
Service Fabric Describe a cluster by using Cluster Resource Manager ...ce-fabric-cluster-resource-manager-cluster-description.md
Medium Priority View Details →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Windows-specific (ClusterManifest.xml, PowerShell) and cross-platform (ClusterConfig.json) configuration examples. However, Windows-centric formats and tools (ClusterManifest.xml, PowerShell) are presented first and more frequently, with PowerShell examples given for service creation and updates, while Linux/macOS equivalents (such as CLI or REST API) are missing. The documentation does not mention Linux-specific tools or patterns, nor does it provide parity for Linux/macOS users in command-line examples.
Recommendations
  • Add Azure CLI or REST API examples for service creation and updates, alongside PowerShell.
  • Clarify which configuration files and formats are used for Linux/macOS standalone deployments (e.g., ClusterConfig.json vs ClusterManifest.xml).
  • Explicitly mention Linux/macOS support and any differences in cluster setup or management.
  • Provide links or references to Linux/macOS-specific documentation or tooling where applicable.
  • Ensure that example order alternates or is balanced between Windows and Linux/macOS formats.
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-03-08 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 and C# examples for configuring Service Fabric MoveCost, but does not include equivalent Linux/Unix shell (e.g., Bash/CLI) examples or mention cross-platform tools. PowerShell is Windows-centric, and the lack of Azure CLI or REST API examples creates friction for Linux/macOS users.
Recommendations
  • Add Azure CLI examples for creating and updating Service Fabric services with MoveCost, if supported.
  • Mention REST API options for MoveCost configuration, if available, and provide example requests.
  • Clarify whether PowerShell commands can be run cross-platform (e.g., with PowerShell Core on Linux/macOS), or provide Bash equivalents if possible.
  • Explicitly state if certain operations are only possible via PowerShell or C# SDK, and suggest alternatives for non-Windows users.
GitHub Create Pull Request
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-08 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 offer equivalent Linux/bash/CLI examples. PowerShell is primarily a Windows tool, and its prominence, along with the lack of Linux-specific instructions, creates friction for Linux users managing Service Fabric clusters. The C# API examples are platform-neutral, but operational/command-line guidance is Windows-centric.
Recommendations
  • Add Azure CLI or bash examples for node tag management and service configuration, if supported.
  • Explicitly mention whether PowerShell commands can be run cross-platform (e.g., PowerShell Core on Linux/macOS), or provide alternatives for Linux users.
  • Clarify any limitations or differences for Linux-hosted Service Fabric clusters regarding node tag management.
  • Consider including REST API examples, which are platform-agnostic, for operational tasks.
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-08 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 shows 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, tools, or instructions provided, and the guidance assumes the use of Windows tooling for cluster management.
Recommendations
  • Add equivalent Linux/Unix instructions for querying and updating cluster manifests, such as using Service Fabric CLI (sfctl) or REST APIs.
  • Include examples for scaling clusters managed on Linux hosts, if supported.
  • Clarify whether standalone Service Fabric clusters can be managed from Linux, and if not, explicitly state Windows-only limitations.
  • Provide links to Linux-specific documentation or note the absence of Linux support if applicable.
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-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page for securing an Azure Service Fabric cluster exhibits moderate Windows bias. While it acknowledges that Service Fabric clusters can run on both Windows and Linux, the majority of security configuration examples, links, and recommendations are focused on Windows Server clusters. Windows security (Kerberos) and Windows certificate services are discussed in detail, with explicit links to Windows-specific guides. There is a lack of equivalent guidance, examples, or references for Linux-based standalone clusters, and Linux-specific certificate creation or security patterns are not mentioned. The concept section briefly states that secure clusters are the same for Linux and Windows, but practical Linux guidance is missing.
Recommendations
  • Add explicit guidance and links for securing standalone Linux Service Fabric clusters, including certificate management and client authentication.
  • Provide Linux-specific examples for certificate creation (e.g., using OpenSSL), installation, and cluster configuration.
  • Mention Linux tools and patterns (such as using systemd, OpenSSL, or Linux account management) where relevant, alongside Windows tools.
  • Ensure parity in recommendations and best practices for Linux environments, not just Windows.
  • Clarify which security features are cross-platform and which are Windows-only, to avoid confusion.
GitHub Create Pull Request
Service Fabric Cluster Resource Manager - Management Integration ...fabric-cluster-resource-manager-management-integration.md
Medium Priority View Details →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides a PowerShell example (Get-ServiceFabricPartitionHealth) for querying health reports, with no equivalent Linux/CLI example. The example is presented without mention of cross-platform alternatives, and the PowerShell syntax is shown first and exclusively. This creates friction for Linux/macOS users, as Service Fabric supports cross-platform management via CLI and REST APIs, but these are not referenced or exemplified.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl) for Linux/macOS users.
  • Mention REST API options for querying health reports, with example requests.
  • Clarify that PowerShell is one option and provide links or references to cross-platform tools.
  • Where possible, show both Windows and Linux/macOS command examples side by side.
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-03-08 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 primarily in C# and PowerShell, with PowerShell being the only CLI example shown for creating and managing Service Fabric services and metrics. There are no equivalent examples for Linux/macOS users (e.g., Bash, Azure CLI, or REST API), and PowerShell is presented before any alternative tooling. This creates friction for users on non-Windows platforms, as Service Fabric can be run and managed from Linux nodes and cross-platform tools.
Recommendations
  • Add Azure CLI or REST API examples for creating and managing Service Fabric services and metrics, as these are cross-platform and accessible from Linux/macOS.
  • Explicitly mention which PowerShell commands are available via Azure CLI or REST API, and provide links or references.
  • If certain operations are only possible via PowerShell, clarify this limitation and suggest alternatives or workarounds for Linux/macOS users.
  • Consider adding Bash script examples or guidance for Linux environments where applicable.
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-03-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides PowerShell examples for configuring service sensitivity and maximum load, but does not offer equivalent Linux/macOS CLI examples (such as Bash or Azure CLI). PowerShell is presented as the primary scripting interface, and no mention is made of cross-platform alternatives or Linux-native tools. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other interfaces.
Recommendations
  • Add Azure CLI or Bash examples for all PowerShell commands, highlighting cross-platform usage.
  • Explicitly mention whether PowerShell Core (pwsh) is supported on Linux/macOS, and provide guidance if so.
  • Document any REST API or SDK alternatives for configuring service sensitivity, with sample requests.
  • Clarify if Service Fabric management can be performed from Linux/macOS, and link to relevant docs if available.
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-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page primarily references Windows-specific upgrade paths and tools for Azure Service Fabric standalone clusters. Key upgrade and configuration links point to Windows Server-specific guides, and the Patch Orchestration Application is described only for Windows. There are no explicit Linux examples or equivalent Linux upgrade/configuration documentation referenced, despite Service Fabric standalone clusters being supported on both Windows and Linux.
Recommendations
  • Add links and guidance for upgrading Service Fabric standalone clusters on Linux, including relevant configuration and upgrade steps.
  • Mention and describe the Patch Orchestration Application (POA) for Linux, if available, or clarify its absence.
  • Ensure that references to configuration files and upgrade procedures are platform-neutral or provide separate sections/examples for Windows and Linux.
  • Update 'Next steps' and other sections to include Linux-specific documentation where applicable.
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-08 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 instructions primarily using PowerShell, which is a Windows-centric tool. There are no equivalent Linux CLI or scripting examples (such as Bash or Azure CLI), nor are Linux-native tools or patterns mentioned. Windows tools (PowerShell cmdlets) are referenced first and exclusively, creating friction for Linux/macOS users who may not have access to PowerShell or prefer other tooling.
Recommendations
  • Add equivalent Linux examples using Bash, Azure CLI, or REST API calls for administrative tasks such as creating/updating services.
  • Mention Linux-native tools and patterns alongside PowerShell, ensuring parity in instructions.
  • Clarify when a PowerShell example is Windows-specific and provide alternative approaches for Linux users.
  • Consider referencing cross-platform tools (e.g., Azure CLI) before or alongside PowerShell.
  • Include notes or links to Linux-specific Service Fabric documentation where relevant.
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-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides upgrade guidance for Azure Service Fabric clusters and generally avoids platform-specific bias. However, in sections about managing certificates and opening application ports, PowerShell is mentioned alongside Azure CLI, but no explicit Linux/macOS shell examples are shown. Additionally, the 'Patch Orchestration Application' section links only to Windows OS patching documentation, suggesting a Windows-first approach for OS upgrades.
Recommendations
  • Where PowerShell is mentioned, ensure equivalent Bash/Azure CLI examples are provided or clarify cross-platform support.
  • If Patch Orchestration Application supports Linux clusters, add links and guidance for Linux OS patching; otherwise, clarify Windows-only applicability.
  • Explicitly state when a feature or example is Windows-specific to reduce ambiguity for Linux/macOS users.
  • Where possible, provide Azure CLI commands in Bash syntax for Linux/macOS users, especially in certificate and port management sections.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Events ...es/service-fabric/service-fabric-diagnostics-events.md
Medium Priority View Details →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page primarily references Windows-specific event logging mechanisms (ETW/Windows Event logs, Windows Azure diagnostics agent) and tools, with no mention of Linux equivalents or examples. Access methods and default configurations are described in a Windows-centric manner, creating friction for Linux cluster administrators.
Recommendations
  • Add information about how Service Fabric events are logged and accessed on Linux clusters, including supported logging mechanisms and tools.
  • Provide examples or references for monitoring and diagnostics setup on Linux (e.g., using syslog, journald, or other Linux-native logging solutions).
  • Clarify which features or access methods are Windows-only and provide Linux alternatives where available.
  • Ensure parity in documentation by including Linux-specific instructions alongside Windows instructions.
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-03-08 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 Service Fabric health monitoring, but the only practical example for reporting and evaluating health is given using PowerShell cmdlets. There are no equivalent examples for Linux/macOS users (e.g., REST API, CLI, or SDK usage), and PowerShell is a Windows-centric tool. The documentation mentions REST and FabricClient APIs but does not show how to use them, nor does it provide Linux-friendly command-line or code samples.
Recommendations
  • Add equivalent examples using REST API calls for health reporting and querying, suitable for Linux/macOS users.
  • Include sample code snippets using the Service Fabric SDK in languages/platforms that are cross-platform (e.g., Python, .NET Core).
  • Provide Azure CLI or Bash shell examples where possible.
  • Explicitly mention Linux/macOS support and tools for health reporting and querying.
  • Reorder examples so that Windows and Linux approaches are presented equally, or at least clarify which tools are platform-specific.
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-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page is based on Windows Server 2016 container samples and frequently references Windows-specific patterns (e.g., 'c:\VolumeTest\Data', 'winver' command, Windows build numbers, and Windows certificate stores). Linux equivalents are not provided or are only mentioned in passing. The manifest examples and explanations focus on Windows containers and settings, with no explicit Linux container examples or guidance.
Recommendations
  • Provide equivalent Linux container manifest examples, including Linux file paths and volume mounts.
  • Add instructions for obtaining OS build/version information on Linux (e.g., 'cat /etc/os-release' or 'uname -r') alongside the Windows 'winver' command.
  • Clarify which settings and patterns are Windows-only and which are cross-platform.
  • Include Linux-specific guidance for certificate handling, volume drivers, and image overrides.
  • Reference Linux container samples in addition to the Windows sample repository.
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-03-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation references PowerShell for deployment/removal tasks and links to PowerShell-specific modules for downloading service packages. There are no explicit Linux or cross-platform CLI examples, and the 'Next steps' section points users to PowerShell for application deployment/removal, implying Windows as the default environment.
Recommendations
  • Add equivalent examples and links for Linux/macOS users, such as Azure CLI or Service Fabric CLI (sfctl) commands for deploying/removing applications.
  • Clarify in the 'Next steps' section that PowerShell is one option, and provide guidance for Linux/macOS environments.
  • Where PowerShell modules are referenced (e.g., Copy-ServiceFabricServicePackageToNode), mention or link to cross-platform alternatives if available.
  • Review the documentation for any implicit assumptions about Windows environments and update language to be more platform-neutral 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-08 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 conceptual information about Service Fabric hosting models, but operational examples and tooling references are heavily Windows/PowerShell-centric. PowerShell is the only CLI example shown for creating services, and all links to command references are for PowerShell modules. There are no Linux CLI (e.g., Azure CLI, Bash) or cross-platform examples, nor is it clarified how Linux users should perform equivalent tasks.
Recommendations
  • Add Azure CLI examples for service creation and management, highlighting cross-platform usage.
  • Mention or link to Linux-compatible tools and workflows for Service Fabric operations.
  • Clarify whether PowerShell Core (cross-platform) is supported, and provide guidance for Linux/macOS users.
  • Include Bash or REST API command examples where possible, especially for critical operations.
  • Reorder examples so that cross-platform options are presented alongside or before Windows-specific ones.
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-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides examples for managing application parameters in Azure Service Fabric, with a notable emphasis on Windows/PowerShell tools. PowerShell is mentioned first for application creation, and Visual Studio (a Windows-centric IDE) is referenced for parameter file management. While sfctl (a cross-platform CLI) and Jenkins (cross-platform CI tool) are mentioned, Linux/macOS-specific workflows or examples are not explicitly provided.
Recommendations
  • Add explicit Linux/macOS examples for application creation and parameter passing, such as using sfctl from a Bash shell.
  • Provide sample shell scripts (e.g., install.sh) for Linux/macOS environments alongside PowerShell scripts.
  • Clarify cross-platform support for tools and highlight any differences in workflows between Windows and Linux/macOS.
  • Include references to Linux/macOS-friendly editors or IDEs (such as VS Code) for managing parameter files.
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-03-08 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 shows mild Windows bias. Windows-specific tools (e.g., 'Setup.bat', '.exe' files, references to 'Administrators' system group, and PowerShell module) are used in examples and explanations. Windows terminology and patterns (such as NETWORKSERVICE, local admin accounts, and console redirection warnings) are prominent, and Windows-centric examples (batch scripts, EXE hosts) are given without Linux equivalents. However, the manifest XML itself is cross-platform, and the page does not explicitly exclude Linux, but Linux-specific guidance is missing.
Recommendations
  • Add Linux-specific examples for service startup scripts (e.g., using shell scripts like 'Setup.sh' instead of 'Setup.bat').
  • Mention Linux equivalents for user/group management (e.g., mapping to Linux system users/groups).
  • Clarify that EXE hosts can be replaced with ELF binaries on Linux, and provide example manifest snippets for Linux deployments.
  • Include instructions or references for deploying and managing Service Fabric applications on Linux clusters, including relevant CLI commands.
  • When referencing PowerShell, also mention Azure CLI or Bash alternatives for Linux/macOS users.
GitHub Create Pull Request
← Previous Page 11 of 99 Next →