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 2126-2150 of 2475 flagged pages
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by focusing on custom Windows images, presenting PowerShell commands for role assignment, and referencing Windows/PowerShell resources before Linux equivalents. While it mentions Linux custom images and provides a link to Linux instructions, all concrete examples and command-line instructions are Windows-centric. No Linux CLI or shell examples are provided for key steps like role assignment.
Recommendations
- Provide equivalent Azure CLI or Bash examples for role assignment and other operations alongside PowerShell commands.
- Include explicit Linux-focused examples for deploying custom images, not just links to external Linux documentation.
- Clarify which steps are OS-agnostic and which are Windows-specific, to help Linux/macOS users navigate the process.
- Ensure that references to Windows and Linux documentation are balanced and presented together when relevant.
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 →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Summary
The documentation provides examples for managing Service Fabric managed cluster node types using the Azure Portal, ARM templates, and PowerShell. However, all command-line examples are exclusively in PowerShell, with no equivalent examples for Bash, Azure CLI, or other Linux/macOS-friendly tools. This creates friction for users on Linux or macOS who may not have access to PowerShell or prefer using Azure CLI.
Recommendations
- Add Azure CLI examples alongside PowerShell for all command-line operations (adding, removing, scaling node types, etc.).
- Explicitly mention that PowerShell examples can be run cross-platform using PowerShell Core, or provide guidance for Linux/macOS users.
- Where possible, provide Bash scripting examples for ARM template deployments, or reference Azure CLI documentation for template deployment.
- Clarify in each section that the ARM template approach is platform-agnostic and can be used from any OS.
Service Fabric
Initializer CodePackages in Service Fabric
...in/articles/service-fabric/initializer-codepackages.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page for Initializer CodePackages in Service Fabric demonstrates a notable Windows bias. All examples use Windows containers (mcr.microsoft.com/windows/nanoserver:1809), Windows file paths (C:\...), and Windows command syntax (cmd, echo, type, ping). There is no mention of Linux containers, Linux file paths, or Linux shell commands. The example explicitly references Windows container compatibility and assumes familiarity with Windows container development, with no Linux equivalent provided.
Recommendations
- Add parallel examples using Linux containers (e.g., mcr.microsoft.com/ubuntu or other Linux images) to demonstrate Initializer CodePackages for Linux workloads.
- Show Linux file path conventions (e.g., /workspace/log.txt) and Linux shell commands (e.g., bash, echo, cat, sleep) in the example manifests.
- Clarify whether Initializer CodePackages are supported for Linux containers and, if so, provide guidance and examples for Linux users.
- If there are limitations or differences for Linux containers, explicitly document them to help users understand platform parity.
Service Fabric
Monitor Azure Service Fabric
...main/articles/service-fabric/monitor-service-fabric.md
Medium Priority
View Details →
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 where Windows tools (such as Event Log/Event Viewer, Diagnostics Agent) are mentioned first or exclusively, and Linux equivalents are referenced later or require additional navigation. Some example/tutorial links are Windows/.NET-focused, and Linux-specific configuration is often described in less detail or deferred to other pages. PowerShell is referenced as an automation option, but Linux CLI or shell alternatives are not explicitly highlighted.
Recommendations
- Ensure that Linux monitoring tools and workflows (such as Syslog, LTTng, Linux-specific agents) are described with equal prominence and detail as Windows tools.
- Provide Linux-specific examples and step-by-step guides alongside Windows/PowerShell examples, especially for cluster monitoring and event collection.
- When referencing automation, mention Linux CLI/bash alternatives in addition to PowerShell.
- In tutorial links, offer parity for Linux (e.g., a tutorial for monitoring .NET Core apps on Linux clusters, not just .NET Framework/.NET on Windows).
- Where Windows tools are mentioned (Event Viewer, Diagnostics Agent), immediately follow with Linux equivalents and configuration steps.
Service Fabric
Architecture of Azure Service Fabric
...articles/service-fabric/service-fabric-architecture.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Summary
The documentation references PowerShell cmdlets and administrative APIs as primary management tools for Service Fabric, without mentioning Linux equivalents (such as CLI or REST API usage). The transport subsystem notes security via 'Windows security' alongside X509 certificates, but does not clarify Linux support or alternatives. No explicit Linux management examples or parity are provided.
Recommendations
- Add references to Linux-compatible management tools, such as Azure CLI or REST APIs, for cluster and application lifecycle operations.
- Clarify whether PowerShell cmdlets are cross-platform or provide Linux-specific instructions/examples where appropriate.
- Expand on security mechanisms in the transport subsystem to specify how Linux nodes authenticate and communicate (e.g., clarify X509 certificate usage for Linux).
- Ensure examples and tooling references include both Windows and Linux options, or note platform limitations explicitly.
Service Fabric
Service Fabric Explorer blocking operations
...ged-cluster-service-fabric-explorer-blocking-operation.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page predominantly references PowerShell cmdlets (Az PowerShell, AzSF PowerShell) for managing Service Fabric resources, with no explicit mention of equivalent Azure CLI commands or Linux/macOS workflows. While az resource is mentioned once, the majority of examples and guidance are PowerShell-centric, which may create friction for Linux/macOS users.
Recommendations
- Provide equivalent Azure CLI examples for all management operations (e.g., creating/deleting applications, services, and application type versions).
- Clearly indicate when both PowerShell and Azure CLI can be used, and provide syntax for both where possible.
- Add notes or links for Linux/macOS users on how to perform these operations using the Azure CLI.
- Review the use of 'Az PowerShell cmdlet' as the default recommendation and balance with CLI alternatives.
Service Fabric
RunToCompletion semantics and specifications
...blob/main/articles/service-fabric/run-to-completion.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page for RunToCompletion semantics in Service Fabric demonstrates a notable Windows bias. All code examples use Windows containers (nanoserver:1809), Windows-specific commands (cmd, set, exit), and reference Windows-only container compatibility. Query instructions are provided only for PowerShell and C#, with no mention of Linux CLI or cross-platform alternatives. There are no Linux container examples, nor guidance for Linux-based Service Fabric clusters.
Recommendations
- Add equivalent examples using Linux containers (e.g., Ubuntu images) and Linux shell commands.
- Clarify whether RunToCompletion semantics are supported for Linux containers and Service Fabric clusters running on Linux.
- Provide instructions for querying deployment status using Linux tools (e.g., Service Fabric CLI, sfctl) or REST API.
- Present examples for both Windows and Linux platforms, or explicitly state platform limitations if Windows-only.
- If RunToCompletion is Windows-only, add a clear note at the top to inform Linux users.
Service Fabric
Application lifecycle in Service Fabric
...service-fabric/service-fabric-application-lifecycle.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page for the Service Fabric application lifecycle consistently references PowerShell cmdlets and Windows-centric tooling as primary examples for operational tasks (deploy, upgrade, remove, cleanup). While REST API and .NET SDK methods are mentioned, PowerShell is given equal or greater prominence, and there is little to no mention of Linux/macOS-specific CLI tools (such as sfctl) or shell scripting examples. This creates friction for Linux/macOS users, who may not have access to PowerShell or may prefer native CLI tools.
Recommendations
- Add Linux/macOS-friendly examples using sfctl and Azure CLI for all operational tasks (deploy, upgrade, remove, cleanup).
- Explicitly mention cross-platform alternatives wherever PowerShell cmdlets are referenced.
- Reorder examples so that REST API, sfctl, and Azure CLI are presented before or alongside PowerShell, to avoid Windows-first bias.
- Provide sample shell scripts or command lines for common lifecycle operations on Linux/macOS.
- Clarify which tools are cross-platform and which are Windows-only, to help users choose the right approach.
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 →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates moderate Windows bias. It references Visual Studio and PowerShell as primary upgrade tools in the 'Next steps' section, both of which are traditionally Windows-centric. No Linux/macOS equivalents (such as CLI or cross-platform IDEs) are mentioned, and Windows tools are listed before alternatives. The content focuses on C# and .NET serialization, which are cross-platform, but the upgrade guidance is Windows-oriented.
Recommendations
- Include instructions or links for upgrading Service Fabric applications using Azure CLI or Service Fabric CLI (sfctl), which are cross-platform.
- Mention cross-platform IDEs (such as VS Code) or provide guidance for non-Visual Studio users.
- Add explicit notes or sections for Linux/macOS users, clarifying supported upgrade workflows and tools.
- Ensure that PowerShell examples are supplemented with CLI or bash equivalents where possible.
Service Fabric
Learn about Azure Service Fabric application security
...ric/service-fabric-application-and-service-security.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page generally covers Service Fabric application security in a cross-platform manner, but there are several sections where Windows-specific patterns, tools, or examples are mentioned first or exclusively. For example, running services under Active Directory domain accounts and group managed service accounts (gMSA) is described only for Windows clusters, with no Linux equivalents or alternatives suggested. Disk encryption is referenced with a link to a PowerShell-based Windows guide, while Linux disk encryption is only mentioned as a TODO. Some examples and terminology (e.g., NetworkService, BitLocker) are Windows-centric, and Linux-specific security practices are not equally represented.
Recommendations
- Add Linux-specific examples and instructions where Windows-only features are described (e.g., disk encryption, service accounts).
- Where features are Windows-only (e.g., AD DS integration, gMSA), explicitly state that Linux alternatives are not available, and suggest best practices for Linux clusters.
- Ensure that cross-platform features (such as certificate management, container security, and API gateway usage) include both Windows and Linux usage patterns and examples.
- Update TODOs (such as 'Encrypt disks on Linux clusters?') with actual guidance or links to relevant documentation.
- Where possible, provide Linux-first or side-by-side examples to improve parity and reduce friction for non-Windows users.
Service Fabric
Application upgrade: upgrade parameters
...abric/service-fabric-application-upgrade-parameters.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page on Service Fabric application upgrade parameters demonstrates a moderate Windows bias. PowerShell and Visual Studio (Windows-centric tools) are presented first and in greater detail, with explicit parameter tables and examples. SFCTL (cross-platform CLI, especially for Linux) is covered later and with less depth. There are no explicit Linux/macOS command examples or screenshots, and the parameter tables for PowerShell/Visual Studio are more extensive and detailed than those for SFCTL. The 'Next steps' section lists Windows upgrade tutorials before Linux equivalents.
Recommendations
- Present SFCTL (Service Fabric CLI) examples and parameter tables alongside PowerShell/Visual Studio, not after them.
- Provide explicit Linux/macOS command-line examples using SFCTL, including sample upgrade commands.
- Balance parameter documentation so SFCTL coverage matches PowerShell/Visual Studio in detail and clarity.
- In 'Next steps', list Linux/SFCTL tutorials before or alongside Windows tutorials.
- Add notes clarifying cross-platform applicability where relevant.
Service Fabric
Service Fabric application upgrade
...s/service-fabric/service-fabric-application-upgrade.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page for Service Fabric application upgrade displays a notable Windows bias. The only code example provided uses PowerShell cmdlets, which are native to Windows and not directly usable on Linux/macOS. References to Windows-specific tools (PowerShell, http.sys) are present, and alternative Linux/macOS workflows or CLI examples are missing. The 'Next steps' section prioritizes Visual Studio and PowerShell tutorials, both Windows-centric, with no mention of cross-platform tools like Azure CLI or Service Fabric CLI (sfctl).
Recommendations
- Add equivalent examples using Service Fabric CLI (sfctl), which is cross-platform, alongside PowerShell examples.
- Explicitly mention Linux/macOS support and provide guidance for those environments where applicable.
- Where Windows-specific APIs or tools (e.g., http.sys) are referenced, clarify their platform limitations and suggest alternatives for Linux clusters.
- Include links to Linux/macOS upgrade tutorials or documentation if available.
- Reorder or balance 'Next steps' to include cross-platform tools before or alongside Windows-centric ones.
Service Fabric
Understanding periodic backup configuration
...-fabric-backuprestoreservice-configure-periodic-backup.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page describes periodic backup configuration for Azure Service Fabric, including options for Azure Blob Storage and file shares. While Azure Blob Storage is cross-platform, the file share backup storage examples and instructions are exclusively Windows-centric, referencing Integrated Windows Authentication and UNC paths (\\StorageServer\BackupStore), with no mention of Linux-compatible file share options (such as NFS or SMB mounting on Linux). There are no Linux/macOS-specific examples or guidance for configuring file share backups, which may create friction for users running Service Fabric clusters on Linux.
Recommendations
- Add examples and instructions for configuring file share backup storage using Linux-compatible protocols (e.g., NFS, SMB/CIFS) and authentication methods.
- Clarify whether file share backup storage is supported on Linux clusters, and if so, provide sample configuration and troubleshooting steps for Linux environments.
- If file share backup is Windows-only, explicitly state this in the documentation to avoid confusion for Linux users.
- Ensure that any references to authentication methods (e.g., Integrated Windows Authentication) are accompanied by Linux alternatives or a note about platform support.
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 →
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 and Windows-centric tooling (e.g., Microsoft.ServiceFabric.Powershell.Http Module, PowerShell cmdlets, and certificate thumbprint usage). All command-line examples use PowerShell syntax, with no mention of Linux/macOS equivalents (such as Bash, curl, or cross-platform Service Fabric CLI tools). There is no guidance for users on non-Windows platforms, which may create friction for those managing Service Fabric clusters from Linux or macOS.
Recommendations
- Add equivalent examples using Bash, curl, or other cross-platform tools for REST API calls.
- Document how to authenticate and interact with Service Fabric REST APIs from Linux/macOS, including certificate management.
- Mention and provide guidance for using Service Fabric CLI (sfctl), which is cross-platform, where applicable.
- Clarify any platform limitations (if certain modules/tools are Windows-only) and suggest alternatives for non-Windows users.
- Ensure that prerequisites and installation steps include Linux/macOS options where possible.
Service Fabric
Capacity planning and scaling for Azure Service Fabric
...bric/service-fabric-best-practices-capacity-scaling.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation frequently references PowerShell commands (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState) for cluster scaling operations, but does not provide equivalent Linux CLI or REST API examples. The instructions for manual scaling are PowerShell-centric, which may create friction for users managing Linux-based Service Fabric clusters. There is also an implicit assumption that users will use Windows tooling for cluster management, with no mention of Linux-native alternatives.
Recommendations
- Provide equivalent Linux CLI (e.g., sfctl) or REST API examples for all PowerShell commands used in scaling operations.
- Clarify which commands and procedures are applicable to both Windows and Linux clusters, and note any differences.
- Add explicit instructions or links for managing Service Fabric clusters on Linux, including how to perform node disablement and removal.
- Where possible, show both Windows (PowerShell) and Linux (sfctl/CLI/REST) examples side-by-side.
- Reference Linux management tools earlier in relevant sections, not only in 'Next steps'.
Service Fabric
Service Fabric Cluster Resource Manager - Placement Policies
...ce-manager-advanced-placement-rules-placement-policies.md
Medium Priority
View Details →
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 mention of Linux/macOS CLI equivalents (such as Azure CLI, Bash, or REST API). 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
- Add equivalent examples using Azure CLI, Bash scripts, or REST API calls for each placement policy configuration.
- Explicitly mention cross-platform management options for Service Fabric clusters, including links to relevant documentation for Linux/macOS users.
- Clarify whether PowerShell examples are applicable on Linux/macOS (via PowerShell Core), and provide guidance if there are platform-specific limitations.
- Consider reordering or balancing example order so that cross-platform options are not always shown after Windows-centric ones.
Service Fabric
Service Fabric Cluster Resource Manager - Application Groups
...ice-fabric-cluster-resource-manager-application-groups.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page for Service Fabric Cluster Resource Manager - Application Groups provides command-line examples exclusively using PowerShell cmdlets, which are native to Windows environments. There are no equivalent examples for Linux/macOS users, such as Bash scripts, Azure CLI, or REST API usage. This creates friction for users managing Service Fabric clusters from non-Windows platforms, as they must translate PowerShell commands or rely on C# code samples.
Recommendations
- Add Azure CLI examples for all PowerShell cmdlet usage, as Azure CLI is cross-platform and commonly used on Linux/macOS.
- Include REST API request examples for relevant operations (e.g., creating/updating applications, querying load information), which can be used from any OS.
- Explicitly mention cross-platform management options and link to documentation for Service Fabric management from Linux/macOS.
- Clarify whether PowerShell Core (pwsh) is supported on Linux/macOS for these cmdlets, and provide installation guidance if so.
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 →
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 given a dedicated section and is used for cluster upgrade commands, which are Windows-centric. Windows-specific configuration details (e.g., registry keys, Windows Update settings) are discussed without Linux equivalents or parity. The upgrade instructions use PowerShell and reference MSI packages, with no Linux shell or DEB package examples. Windows VM configuration is described in detail, while Linux VM configuration is not covered. However, links to both Windows and Linux cluster creation guides are provided.
Recommendations
- Include Linux shell (bash) examples for cluster upgrades, especially for operations currently shown only in PowerShell.
- Provide Linux VM configuration best practices alongside Windows-specific registry and update settings.
- Add DEB package upgrade instructions and Linux-specific commands where MSI/PowerShell are referenced.
- Ensure that configuration snippets (e.g., disabling automatic updates) have Linux equivalents or clarify when they are Windows-only.
- Balance example order so Linux and Windows are presented equally, or clarify when a section is Windows-specific.
Service Fabric
Azure Service Fabric security best practices
...rvice-fabric/service-fabric-best-practices-security.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation generally covers both Windows and Linux scenarios for Service Fabric security, but Windows-specific tools and examples (such as PowerShell commands and Windows Defender) are often presented first or exclusively. Some sections, like Windows Defender configuration, are Windows-only by nature and are correctly flagged as such. However, in other areas, Windows commands (PowerShell) are shown before Linux equivalents, and Windows-centric tools (e.g., Azure Desired State Configuration, Windows security baselines) are emphasized without mentioning Linux alternatives.
Recommendations
- Present Windows and Linux examples side-by-side or in parallel sections, rather than listing Windows first.
- Where Windows-specific tools are mentioned (e.g., Desired State Configuration, Windows Defender), add notes or links to equivalent Linux approaches (such as Ansible, Chef, or Linux-native security baselines).
- Ensure that Linux users are provided with clear guidance and examples for all major security tasks, not just links to separate documents.
- Add explicit statements when a feature or recommendation is Windows-only, to clarify intent and avoid confusion.
- Consider including more Linux-focused best practices, such as SELinux/AppArmor, Linux firewall configuration, and Linux-native monitoring/antimalware solutions.
Service Fabric
Node types and virtual machine scale sets
...les/service-fabric/service-fabric-cluster-nodetypes.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page generally describes Service Fabric node types and VM scale sets in a cross-platform manner, but there are signs of Windows bias. The JSON extension snippet uses a Windows-style data path (D:\\SvcFab) without showing a Linux equivalent. The 'Next steps' section links to PowerShell scripts for changing RDP port ranges and admin credentials—these are Windows-centric tasks and tools, with no mention of Linux/SSH equivalents. Linux-specific guidance is minimal or absent, and Windows patterns (RDP, PowerShell, Windows file paths) are presented first or exclusively.
Recommendations
- Include Linux-specific examples for configuration, such as showing a Linux-style dataPath (e.g., /var/svcfab) alongside the Windows example.
- Add links or guidance for Linux users on how to connect to cluster nodes (e.g., SSH instructions) and manage credentials, not just RDP/PowerShell.
- Balance the 'Next steps' section by providing equivalent Linux management tasks and scripts, or clarify which steps are Windows-only.
- Explicitly state when a feature or example is Windows-specific, and provide Linux alternatives where possible.
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 →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides PowerShell examples for creating and updating Service Fabric services, but does not offer equivalent Linux CLI (sfctl) or Bash examples. PowerShell is a Windows-centric tool, and its exclusive use in examples creates friction for Linux/macOS users. There is no mention of Linux-native tooling or cross-platform command-line alternatives for these operations.
Recommendations
- Add equivalent examples using sfctl (Service Fabric CLI), which is cross-platform and works on Linux/macOS.
- Include Bash or shell script snippets for common operations where possible.
- Explicitly mention that PowerShell examples are for Windows, and provide guidance for Linux/macOS users on how to perform the same tasks.
- Consider adding a table or section comparing PowerShell and sfctl usage for key Service Fabric operations.
Service Fabric
Manage Azure Service Fabric app load using metrics
...ric/service-fabric-cluster-resource-manager-metrics.md
Medium Priority
View Details →
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 only PowerShell is shown for command-line usage, with no Linux/macOS CLI equivalents (such as Azure CLI or REST API). PowerShell is a Windows-centric tool, and its exclusive use in examples creates friction for Linux/macOS users. The documentation does not mention or demonstrate how to perform these tasks using cross-platform tools, nor does it clarify whether PowerShell Core is supported on non-Windows platforms.
Recommendations
- Add equivalent Azure CLI or REST API examples for service creation and metric management, which are cross-platform.
- Clarify whether PowerShell Core is supported for these commands on Linux/macOS, and provide installation guidance if so.
- Explicitly mention any platform limitations for Service Fabric management tools.
- Consider reordering examples so that cross-platform options are shown before or alongside PowerShell.
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 →
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 include equivalent CLI/bash or Linux-native examples. PowerShell is primarily a Windows tool, and its usage is presented before C# API examples. There is no mention of Linux/macOS command-line alternatives for these tasks, despite Service Fabric supporting Linux clusters.
Recommendations
- Add examples using Azure CLI or REST API calls for managing node tags and service tag requirements, which are cross-platform.
- If Service Fabric supports Linux-native management tools (e.g., bash scripts, SFCTL), include those examples alongside PowerShell.
- Explicitly state whether PowerShell commands can be run on Linux/macOS (e.g., via PowerShell Core), or provide guidance for non-Windows users.
- Reorder examples so that cross-platform or API-based approaches are presented before or alongside PowerShell.
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 →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation provides configuration examples using XML, JSON, PowerShell, and C# APIs. However, all command-line examples use PowerShell cmdlets (e.g., New-ServiceFabricService, Update-ServiceFabricService), which are Windows-centric tools. There are no CLI (e.g., Azure CLI, sfctl) or bash examples for Linux/macOS users, nor is there guidance for cross-platform management. This creates friction for non-Windows users who may not have access to PowerShell or prefer other tools.
Recommendations
- Add equivalent examples using cross-platform tools such as Azure CLI or sfctl where possible.
- Explicitly document whether PowerShell cmdlets are supported on Linux/macOS (e.g., via PowerShell Core), and provide installation guidance if so.
- If only PowerShell is supported, clearly state this limitation and suggest alternatives or workarounds for Linux/macOS users.
- Include bash or shell script examples for common operations, or reference cross-platform Service Fabric management documentation.
Service Fabric
Secure an Azure Service Fabric cluster
...cles/service-fabric/service-fabric-cluster-security.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation covers security for both Azure-hosted and standalone Windows Service Fabric clusters, but examples and links for standalone clusters are exclusively Windows-focused. There are no instructions or references for securing standalone Linux clusters, and Windows terminology and links are presented first or exclusively in several sections.
Recommendations
- Add explicit guidance and links for securing standalone Service Fabric clusters running on Linux, if supported.
- Include Linux-specific examples for certificate creation, installation, and configuration (e.g., using OpenSSL, Linux file paths, and permissions).
- Clarify in each section whether the instructions apply to both Windows and Linux, or only Windows, to avoid confusion.
- If standalone Linux clusters are not supported, state this clearly to set expectations for Linux users.