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 2001-2025 of 2475 flagged pages
Service Fabric X.509 Certificate-based Authentication in a Service Fabric Cluster ...ticles/service-fabric/cluster-security-certificates.md
Medium Priority View Details →
Scanned: 2026-02-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation provides a thorough conceptual overview of X.509 certificate-based authentication in Service Fabric clusters, with configuration examples in XML. However, there is a notable Windows bias in troubleshooting guidance and tool references. Windows-specific certificate store paths and troubleshooting tools (e.g., CAPI2 logging, Win32 CryptoAPI references) are mentioned first or exclusively, while Linux equivalents are only briefly referenced or omitted. Some error codes and remediation steps are Windows-centric, and there is little guidance for Linux/macOS users on equivalent certificate management or troubleshooting.
Recommendations
  • Provide Linux/macOS-specific troubleshooting steps and log file locations, such as where Service Fabric logs certificate errors on Linux nodes.
  • When referencing certificate stores (e.g., LocalMachine\My), always mention the Linux equivalent path (e.g., /var/lib/sfcerts) in parallel, not as an afterthought.
  • Include examples of how to inspect, install, and manage certificates on Linux (e.g., using OpenSSL or Linux-native tools) alongside Windows methods.
  • Reference Linux/macOS error messages and common issues, and provide guidance for resolving them.
  • Avoid referencing only Windows APIs (e.g., Win32 CryptoAPI) without mentioning the equivalent mechanisms or libraries used on Linux.
  • If certain features or troubleshooting steps are Windows-only, explicitly state so and provide alternative guidance for Linux/macOS where possible.
GitHub Create Pull Request
Service Fabric Configure or modify a Service Fabric managed cluster node type ...vice-fabric/how-to-managed-cluster-modify-node-type.md
Medium Priority View Details →
Scanned: 2026-02-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation consistently provides PowerShell examples for command-line operations (add, remove, scale, configure node types), but does not offer equivalent examples for Linux/macOS users (e.g., Azure CLI, Bash). All scripting/automation examples outside ARM templates use PowerShell, which is primarily a Windows tool. There is no mention of Azure CLI or cross-platform scripting alternatives, creating friction for non-Windows users.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all command-line operations (add, remove, scale, configure node types).
  • Explicitly mention that PowerShell examples require Azure PowerShell module and are best suited for Windows, and provide guidance for Linux/macOS users.
  • Consider adding Bash or cross-platform scripting examples where appropriate.
  • In sections where only PowerShell is supported (e.g., removing a primary node type), clarify if this is a platform limitation or just a documentation gap.
GitHub Create Pull Request
Service Fabric Deny assignment policy for Service Fabric managed clusters ...cles/service-fabric/managed-cluster-deny-assignment.md
Medium Priority View Details →
Scanned: 2026-02-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias by prioritizing Azure PowerShell examples and references, listing PowerShell before Azure CLI, and not providing explicit Linux/macOS command-line examples for key operations. While ARM templates, Bicep, and Azure CLI are mentioned (which are cross-platform), the only concrete example links for deleting, restarting, and reimaging node types use Azure PowerShell, with no equivalent Azure CLI or REST API examples. This may create friction for Linux/macOS users who prefer CLI or scripting over PowerShell.
Recommendations
  • Add Azure CLI examples and links for all key operations (deleting, restarting, reimaging node types) alongside PowerShell examples.
  • Explicitly mention that Azure CLI and ARM templates are cross-platform and suitable for Linux/macOS users.
  • Where PowerShell is referenced, provide equivalent CLI or REST API documentation links.
  • Consider ordering examples and tool references so that cross-platform options (CLI, ARM, Bicep) appear before Windows-specific tools.
GitHub Create Pull Request
Service Fabric RunToCompletion semantics and specifications ...blob/main/articles/service-fabric/run-to-completion.md
Medium Priority View Details →
Scanned: 2026-02-02 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation page for RunToCompletion semantics in Service Fabric demonstrates a notable Windows bias. All code examples use Windows containers (nanoserver:1809) and Windows-specific commands (cmd, echo, set, ping), with no mention of Linux container equivalents. PowerShell is the only CLI example given for querying deployment status, and Windows tools/patterns are referenced exclusively. There is no guidance or parity for Linux-based Service Fabric clusters or Linux containers.
Recommendations
  • Add Linux container examples (e.g., using Ubuntu or Alpine images) with equivalent shell commands.
  • Provide instructions and examples for querying deployment status using Linux tools (e.g., Bash, Service Fabric CLI on Linux).
  • Clarify in the introduction whether RunToCompletion semantics are supported for Linux containers and clusters, and if not, explicitly state this limitation.
  • If supported, include cross-platform code samples and highlight differences or requirements for Linux users.
GitHub Create Pull Request
Service Fabric Learn about Azure Service Fabric application security ...ric/service-fabric-application-and-service-security.md
Medium Priority View Details →
Scanned: 2026-02-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides a general overview of Service Fabric application security, but several sections show subtle Windows bias. Examples and references often prioritize Windows tools or features (e.g., Active Directory, BitLocker, gMSA) and mention Windows-specific patterns before Linux equivalents. Some security features (like disk encryption) link only to Windows/PowerShell guides, and Linux options are left as TODOs or not described. Linux users may need to search elsewhere for parity.
Recommendations
  • Provide Linux-specific examples and links for disk encryption and other security features where only Windows/PowerShell instructions are given.
  • Ensure that references to OS-specific features (e.g., gMSA, AD accounts) are clearly marked as Windows-only, and offer Linux alternatives or clarify their absence.
  • Include Linux-first or cross-platform examples in sections about running services under different accounts, managing secrets, and securing containers.
  • Complete TODOs regarding Linux disk encryption and other missing Linux documentation.
  • Balance the order of presentation so that Linux and Windows approaches are given equal prominence where both are supported.
GitHub Create Pull Request
Service Fabric Monitor Azure Service Fabric ...main/articles/service-fabric/monitor-service-fabric.md
Medium Priority View Details →
Scanned: 2026-02-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation generally covers both Windows and Linux clusters for Azure Service Fabric monitoring, but there are several instances of Windows bias. Windows-specific tools (Event Viewer, ETW, Diagnostics Agent) are mentioned and explained in detail, sometimes before their Linux equivalents (LTTng, Syslog). Some examples and tutorials focus on .NET applications (which are cross-platform, but the tutorial is Windows-oriented), and configuration steps for Linux are referenced but not shown inline. In a few places, Windows monitoring solutions are described first or in more detail, and Linux alternatives are only briefly mentioned or deferred to other pages.
Recommendations
  • Provide Linux-specific examples and configuration steps inline, not just as links to other pages.
  • Ensure that Linux monitoring tools (LTTng, Syslog, Azure Monitor agent) are described with equal detail and prominence as Windows tools (ETW, Event Viewer, Diagnostics Agent).
  • Include sample code and tutorials for Linux-based Service Fabric applications (e.g., using Application Insights or logging frameworks on Linux).
  • When listing monitoring solutions or workflows, present Windows and Linux options side-by-side, or clearly indicate which steps are OS-specific.
  • Add explicit PowerShell and Bash/CLI equivalents for automation examples.
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-02 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page primarily describes Service Fabric application and service manifests in a platform-neutral way, focusing on XML schema and concepts. However, there is a notable Windows bias in the tooling recommendations: the warning box suggests using Visual Studio and a local Windows file path to validate the manifest schema, with no mention of Linux/macOS alternatives. Additionally, the PowerShell module is referenced for service creation before mentioning other methods, which may imply Windows-first workflows.
Recommendations
  • Include instructions or tooling recommendations for Linux/macOS users, such as using VS Code, JetBrains Rider, or other XML schema validation tools available cross-platform.
  • Provide equivalent Linux/macOS file paths or clarify how to obtain the ServiceFabricServiceModel.xsd schema on non-Windows systems.
  • Mention cross-platform CLI tools (e.g., Azure CLI, Service Fabric CLI) for service creation and management alongside PowerShell.
  • When referencing PowerShell, explicitly note alternative approaches for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Advanced Application Upgrade Topics ...-fabric/service-fabric-application-upgrade-advanced.md
Medium Priority View Details →
Scanned: 2026-02-02 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 advanced Service Fabric application upgrades is heavily focused on PowerShell-based workflows, with all command-line examples using PowerShell cmdlets. There is no mention of Linux/macOS equivalents, such as Service Fabric CLI (sfctl), nor are there bash or shell script examples. The documentation assumes users are operating in a Windows/PowerShell environment, creating friction for Linux/macOS users who may use different tools.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl) for Linux/macOS users alongside PowerShell examples.
  • Explicitly mention that PowerShell cmdlets are for Windows environments and provide links or references to Linux/macOS documentation.
  • Include bash or shell script snippets where appropriate, especially for common upgrade tasks.
  • Clarify which features or commands are cross-platform and which are Windows-only.
GitHub Create Pull Request
Service Fabric Application upgrade: upgrade parameters ...abric/service-fabric-application-upgrade-parameters.md
Medium Priority View Details →
Scanned: 2026-02-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page presents PowerShell and Visual Studio (Windows-centric tools) parameters and examples before introducing SFCTL (cross-platform CLI) and REST options. The parameter tables and explanations are heavily focused on PowerShell and Visual Studio, with detailed examples and descriptions, while SFCTL (the main Linux/macOS tool) is covered in a separate, shorter section with less detail and no explicit Linux/macOS command examples. There are no Linux/macOS-specific usage examples or parity in parameter explanation order, which may create friction for non-Windows users.
Recommendations
  • Reorder sections so SFCTL (cross-platform CLI) is presented before or alongside PowerShell/Visual Studio, emphasizing its use for Linux/macOS users.
  • Provide explicit SFCTL command-line examples for common upgrade scenarios, similar to the PowerShell examples.
  • Include a table mapping PowerShell/Visual Studio parameters to their SFCTL/REST equivalents for clarity.
  • Add notes or callouts indicating which tools are recommended for Linux/macOS users.
  • Ensure parameter descriptions for SFCTL are as detailed as those for PowerShell/Visual Studio, including example values and usage patterns.
GitHub Create Pull Request
Service Fabric Application upgrade: data serialization ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-application-upgrade-data-serialization.md
Medium Priority View Details →
Scanned: 2026-02-02 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides next steps that highlight upgrading applications using Visual Studio and PowerShell, both of which are primarily Windows-centric tools. No equivalent Linux/macOS upgrade instructions or tooling (such as Azure CLI or Service Fabric CLI) are mentioned or linked. The main content is focused on C# and .NET serialization, which is cross-platform, but the upgrade workflow guidance is Windows-first.
Recommendations
  • Add links or sections for upgrading Service Fabric applications using cross-platform tools such as Azure CLI or Service Fabric CLI (sfctl), which are supported on Linux and macOS.
  • Provide examples or tutorials for application upgrades on Linux/macOS environments.
  • Clarify which steps are Windows-only and offer Linux/macOS alternatives where possible.
GitHub Create Pull Request
Service Fabric Architecture of Azure Service Fabric ...articles/service-fabric/service-fabric-architecture.md
Medium Priority View Details →
Scanned: 2026-02-02 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page on Azure Service Fabric architecture references PowerShell cmdlets as a primary management interface and mentions Windows security as an option for transport security before X509 certificates. No Linux-specific management tools or examples (such as Bash, CLI, or Linux security mechanisms) are mentioned, and Windows-centric tooling is presented first in relevant sections.
Recommendations
  • Explicitly mention cross-platform management options, such as Azure CLI or REST APIs, alongside PowerShell cmdlets.
  • Clarify that PowerShell is available on Linux/macOS, or provide Bash/CLI examples where appropriate.
  • When discussing security, highlight X509 certificates as the default cross-platform mechanism and note any Windows-specific options as alternatives.
  • Add notes or links to Linux/macOS management documentation for Service Fabric clusters.
GitHub Create Pull Request
Service Fabric Restoring backup in Azure Service Fabric ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-backup-restore-service-trigger-restore.md
Medium Priority View Details →
Scanned: 2026-02-02 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 for restoring backups in Azure Service Fabric is heavily focused on PowerShell-based workflows, with all command-line examples using PowerShell syntax and modules. There is no mention of Linux/macOS equivalents, nor are cross-platform REST API invocation examples (e.g., curl, Python) provided. The prerequisite steps and all automation instructions assume the use of Windows tools and environments, which may create friction for users managing Service Fabric clusters from Linux or macOS.
Recommendations
  • Add equivalent examples using cross-platform tools (e.g., curl, Python requests) for REST API calls.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is required or if REST API calls can be made directly from any OS.
  • Provide guidance for Linux/macOS users on authentication (e.g., certificate handling) and cluster connection.
  • Explicitly state OS requirements or limitations if PowerShell is mandatory, or provide alternatives where possible.
  • Reorder or balance examples so that REST API usage is shown before or alongside PowerShell, emphasizing platform neutrality.
GitHub Create Pull Request
Service Fabric Capacity planning and scaling for Azure Service Fabric ...bric/service-fabric-best-practices-capacity-scaling.md
Medium Priority View Details →
Scanned: 2026-02-02 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 detailed step-by-step instructions for scaling Service Fabric clusters, but the manual scaling procedures rely heavily on PowerShell commands (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState) without offering equivalent Linux CLI or REST API examples. There is no mention of Service Fabric CLI (sfctl) or bash scripting, and the only command-line examples are Windows PowerShell. This creates friction for Linux users, who must find their own way to perform these operations. Additionally, the documentation references Windows tools first and does not provide parity for Linux environments in critical operational steps.
Recommendations
  • Add equivalent Linux instructions using sfctl (Service Fabric CLI) for all PowerShell-based steps, including node disabling, querying, and removal.
  • Provide bash or shell script examples alongside PowerShell for manual scaling operations.
  • Explicitly mention REST API alternatives for cluster management where applicable.
  • Clarify which commands are cross-platform and which are Windows-only, and provide links to Linux-specific documentation where available.
  • Ensure that all operational guidance (not just cluster creation) is platform-neutral or has Linux parity.
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-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page presents several examples and references that are Windows-centric, such as defaulting to Windows-style file paths (e.g., D:\SvcFab), referencing RDP port changes and admin credential updates (Windows remote access patterns), and linking to PowerShell scripts for cluster VM management. There is minimal coverage or examples for Linux users, and Linux-specific patterns (like SSH access or Linux file paths) are not mentioned or are secondary.
Recommendations
  • Include Linux-specific examples for file paths (e.g., /var/svcfab) in the Service Fabric extension settings.
  • Add guidance and links for SSH-based remote connection to Linux nodes, alongside or before RDP/PowerShell instructions.
  • Provide parity in script references, such as Bash/CLI scripts for changing admin credentials and port ranges on Linux VMs.
  • Clarify which instructions or examples apply to Windows, Linux, or both, to help users navigate platform differences.
GitHub Create Pull Request
Service Fabric Service Fabric application upgrade ...s/service-fabric/service-fabric-application-upgrade.md
Medium Priority View Details →
Scanned: 2026-02-02 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 Service Fabric application upgrade demonstrates a notable Windows bias. PowerShell is the only command-line example provided, and Windows-specific tools (PowerShell cmdlets, http.sys) are referenced exclusively. There are no Linux or cross-platform CLI examples, and the upgrade process is described using Windows-centric terminology and APIs. The 'Next steps' section also prioritizes Visual Studio and PowerShell, both primarily Windows tools, with no mention of Linux equivalents or Service Fabric CLI usage.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • Include notes or sections clarifying differences in upgrade procedures for Linux clusters, if any.
  • Reference Linux-compatible tools and workflows in the 'Next steps' section, such as upgrading via sfctl or REST API.
  • Where Windows-specific APIs (e.g., http.sys) are mentioned, clarify their applicability and provide Linux alternatives or caveats.
  • Ensure that code samples and walkthroughs are available for both Windows and Linux environments.
GitHub Create Pull Request
Service Fabric On-demand backup in Azure Service Fabric ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-backup-restore-service-ondemand-backup.md
Medium Priority View Details →
Scanned: 2026-02-02 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 on-demand backup in Azure Service Fabric demonstrates a notable Windows bias. All command-line examples use PowerShell and reference the Microsoft.ServiceFabric.Powershell.Http module, which is Windows-centric. There are no CLI, Bash, or cross-platform examples provided, and Linux/macOS users are not given alternative instructions for performing backups or REST API calls. The documentation assumes use of Windows tools and patterns throughout, making it less accessible for users on non-Windows platforms.
Recommendations
  • Add equivalent examples using Azure CLI, Bash, or curl for REST API calls to support Linux/macOS users.
  • Clarify whether the PowerShell module is required or if REST API calls can be made directly from any platform.
  • Provide guidance on authentication and certificate handling for REST API calls from Linux/macOS environments.
  • Indicate platform requirements for each tool or command, and suggest alternatives where possible.
  • Consider reordering examples so that cross-platform methods (e.g., REST API via curl) are presented before or alongside PowerShell examples.
GitHub Create Pull Request
Service Fabric Understanding periodic backup configuration ...-fabric-backuprestoreservice-configure-periodic-backup.md
Medium Priority View Details →
Scanned: 2026-02-02 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page presents backup storage options including Azure Blob Storage and File Share. The File Share examples and instructions are exclusively Windows-centric, referencing Integrated Windows Authentication and UNC paths (\\StorageServer\BackupStore), with no mention of Linux-compatible file sharing methods (e.g., NFS, SMB mounting on Linux, or Linux authentication patterns). There are no examples or guidance for configuring on-premises backup storage for Linux clusters, nor any mention of Linux-specific tools or patterns. The documentation implicitly assumes Windows environments for on-premises scenarios.
Recommendations
  • Add examples and instructions for configuring file share backup storage using Linux-compatible protocols (e.g., NFS, SMB mounts on Linux).
  • Clarify whether Linux Service Fabric clusters can use file share backup storage, and if so, provide authentication and path examples for Linux.
  • Explicitly mention any limitations or differences for Linux clusters in backup configuration and storage options.
  • Where authentication is discussed, include Linux-relevant patterns (e.g., Kerberos, username/password for SMB, NFS exports).
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-02-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Service Fabric clusters, but PowerShell is featured prominently and exclusively for several key operations (e.g., manual cluster upgrade). Windows-specific tools and registry settings are mentioned without Linux equivalents or guidance. Windows configuration details (e.g., disabling Windows Update via registry and template) are given before any Linux-specific advice, and Linux upgrade procedures are not covered in detail.
Recommendations
  • Provide Linux-specific examples for manual cluster upgrades, including equivalent shell commands (e.g., Bash) and package formats (deb, rpm).
  • Include instructions or references for disabling automatic updates and managing upgrades on Linux VMs, such as using apt or yum/dnf.
  • Balance PowerShell and CLI examples by offering Bash or shell script alternatives where possible, especially for cluster management tasks.
  • Clarify which steps are Windows-only and provide Linux alternatives or explicitly state when a step does not apply to Linux.
  • Add links or sections for Linux VM configuration best practices in Service Fabric clusters.
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-02 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides several examples and references that prioritize Windows and PowerShell, such as mentioning PowerShell APIs for client connections, referencing Windows-specific ARM templates, and describing Windows container networking scenarios. Linux equivalents are sometimes mentioned, but often after Windows, and Linux-specific examples or CLI commands are sparse or missing. The documentation also references Windows update orchestration and PowerShell-heavy DevOps tasks without Linux parity.
Recommendations
  • Provide Linux CLI (az, bash) examples alongside or before PowerShell examples, especially for cluster management and networking tasks.
  • Include Linux-specific ARM template samples and links, not just Windows-focused ones.
  • Clarify when features or recommendations apply to both Windows and Linux, and explicitly note any differences.
  • Add Linux container networking scenarios and troubleshooting tips, not just Windows container notes.
  • Reference Linux DevOps workflows (e.g., Azure CLI, bash scripts) in addition to PowerShell for operational tasks.
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-02-02 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, without offering equivalent CLI or script examples for Linux/macOS users. PowerShell is a Windows-centric tool, and its exclusive use in examples creates 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
  • Provide equivalent Azure CLI or REST API examples for each placement policy configuration, as these are cross-platform and widely used on Linux/macOS.
  • Explicitly mention how Linux/macOS users can perform these tasks, including any supported tools or scripts.
  • If PowerShell is required for certain operations, clarify this and provide guidance or alternatives for non-Windows users.
  • Consider reordering examples or providing cross-platform instructions first, followed by Windows-specific details.
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-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides command-line examples exclusively using PowerShell cmdlets for Service Fabric application management tasks, with no mention of Linux shell equivalents or cross-platform CLI tools. This creates friction for Linux/macOS users, as PowerShell is traditionally a Windows-centric tool and not the default shell on Linux. There is no guidance on using Azure CLI, REST API, or Service Fabric CLI (sfctl), which are cross-platform options.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and supported on Linux/macOS.
  • Include Azure CLI or REST API examples for application management tasks where possible.
  • Explicitly note PowerShell examples are for Windows users, and provide links or instructions for Linux/macOS users to perform the same actions.
  • Consider reordering examples so that cross-platform options are presented before or alongside PowerShell.
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-02-02 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 managing node tags and service tag requirements, but does not offer equivalent command-line examples for Linux/macOS users (e.g., Bash, Azure CLI, or REST API usage). PowerShell is presented first and exclusively as the shell-based method, which may create friction for users managing Service Fabric clusters from non-Windows environments.
Recommendations
  • Add equivalent examples using Azure CLI or REST API for managing node tags and service tag requirements, as these are cross-platform.
  • If PowerShell is required, clarify whether PowerShell Core (pwsh) is supported on Linux/macOS and provide usage notes.
  • Consider including Bash script examples or direct REST API calls for common operations.
  • Explicitly state platform compatibility for each method (PowerShell, C#, REST API) to guide users on Linux/macOS.
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-02 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 demonstrates a Windows bias by exclusively referencing PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) and linking to Windows Server-specific instructions for scaling. There are no examples or guidance for Linux-based clusters, nor are Linux-native tools or commands mentioned.
Recommendations
  • Add equivalent Linux instructions for scaling standalone clusters, including examples using Bash, CLI, or REST API if available.
  • Clarify whether standalone clusters can be run on Linux, and if so, provide parity in documentation for Linux environments.
  • Reference Linux-native tools or commands (e.g., sfctl, Service Fabric CLI) where appropriate.
  • If scaling standalone clusters is Windows-only, explicitly state this limitation early in the documentation.
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-02-02 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 for configuring auto scaling policies in Azure Service Fabric using application manifests, C# APIs, and PowerShell. However, the PowerShell examples are Windows-specific, and there are no equivalent Linux CLI or bash examples. The documentation does not mention Linux tooling or provide guidance for Linux users on how to perform these operations, despite Service Fabric supporting containerized workloads on Linux. Windows/PowerShell examples are presented first and exclusively, which may create friction for Linux users.
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 Linux users where applicable.
  • Explicitly mention how Linux users can perform auto scaling configuration, especially for containerized workloads.
  • Clarify any Windows-only limitations for PowerShell commands and point Linux users to alternative tooling.
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-02 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 the Cluster Resource Manager integration with Service Fabric cluster management. However, the only concrete example given for interacting with health reports uses a PowerShell cmdlet (Get-ServiceFabricPartitionHealth), with no mention of Linux/macOS equivalents or cross-platform CLI tools. 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.
  • Add a note clarifying that PowerShell examples are for Windows, and provide guidance for Linux/macOS users.
  • Where possible, show both Windows (PowerShell) and Linux/macOS (sfctl or REST API) commands side-by-side for parity.
GitHub Create Pull Request
← Previous Page 81 of 99 Next →