Service Fabric

810
Total Pages
600
Linux-Friendly Pages
210
Pages with Bias
25.9%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

718 issues found
Showing 151-175 of 718 flagged pages
Service Fabric Manage certificates in an Azure Service Fabric cluster ...https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-security-update-certs-azure.md
High Priority View Details →
Scanned: 2026-01-09 19:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. All command-line examples for deploying and managing certificates use PowerShell, with no mention of Linux shell equivalents (such as Bash or Azure CLI). The instructions assume use of Windows tools (PowerShell, certificate stores like 'Cert:\CurrentUser\TrustedPeople'), and there are no examples or guidance for Linux users. The workflow and troubleshooting steps are written from a Windows-centric perspective, and Linux patterns are omitted entirely.
Recommendations
  • Provide equivalent Azure CLI and Bash examples for all PowerShell commands, especially for template deployment and certificate management.
  • Include instructions for importing certificates on Linux, such as using 'openssl' or Linux certificate stores.
  • Mention platform differences explicitly, and offer guidance for both Windows and Linux administrators.
  • Reference cross-platform tools and patterns (e.g., Azure CLI, REST API) before or alongside Windows-specific tools.
  • Add troubleshooting notes for Linux environments, such as common certificate store locations and access methods.
GitHub Create Pull Request
Service Fabric Set up monitoring with Azure Monitor logs ...service-fabric/service-fabric-diagnostics-oms-setup.md
High Priority View Details →
Scanned: 2026-01-09 19:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a Windows bias by prioritizing Windows-specific solutions (Service Fabric Analytics), providing PowerShell-heavy deployment examples, referencing Windows tools (WAD), and omitting equivalent Linux-focused examples or instructions. Linux users are redirected to separate documentation, and the main workflow and examples are tailored for Windows environments.
Recommendations
  • Include Linux-specific deployment steps and examples directly in this page, not just as a redirect.
  • Provide equivalent Bash/CLI examples for deploying and configuring Azure Monitor logs and Log Analytics workspaces.
  • Clarify which features or solutions are Windows-only and offer Linux alternatives or workarounds.
  • Mention Linux diagnostic tools (e.g., syslog, OMS agent) alongside Windows tools like WAD, and explain how to connect Linux cluster logs to Log Analytics.
  • Ensure parity in instructions and screenshots for both Windows and Linux clusters.
GitHub Create Pull Request
Service Fabric Migrate from Azure Cloud Services to Service Fabric ...ic/cloud-services-to-service-fabric-migration-guide.md
High Priority View Details →
Scanned: 2026-01-09 19:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a clear Windows bias. PowerShell is the only command-line tool shown for cluster and application deployment, with no Azure CLI or Bash examples. Visual Studio (Windows-only) is the only development environment mentioned for creating Service Fabric applications, and the setup instructions reference preparing the development environment on Windows, with no mention of Linux or cross-platform alternatives. The documentation does not provide Linux-specific guidance or parity for common tasks, and Windows tools and patterns are consistently mentioned first or exclusively.
Recommendations
  • Add Azure CLI and Bash examples for all PowerShell deployment and management commands, including cluster creation, application packaging, and deployment.
  • Include instructions for setting up a development environment on Linux and macOS, such as using VS Code, JetBrains Rider, or the Service Fabric CLI (sfctl).
  • Provide explicit guidance for cross-platform development, including .NET Core/ASP.NET Core usage on Linux.
  • Mention and link to Linux-compatible tools and workflows (e.g., sfctl, Azure CLI, Docker for container scenarios) alongside or before Windows-specific tools.
  • Ensure all code and configuration migration steps include notes or examples relevant to Linux environments (e.g., file paths, environment variables, packaging).
  • Clarify any platform-specific limitations or differences, such as container support or deployment targets, and provide Linux alternatives where possible.
GitHub Create Pull Request
Service Fabric Use Azure DDoS Protection in a Service Fabric managed cluster ...rvice-fabric/how-to-managed-cluster-ddos-protection.md
High Priority View Details →
Scanned: 2026-01-09 19: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 Windows bias by providing only PowerShell command examples for key steps (such as obtaining service principal IDs and assigning roles), referencing Azure PowerShell before Azure CLI, and omitting equivalent Linux shell or Azure CLI commands for these operations. There is no mention of Linux-specific tools or cross-platform alternatives, making the instructions less accessible to Linux users.
Recommendations
  • Include Azure CLI examples alongside PowerShell for all command-line steps, especially for service principal and role assignment operations.
  • Present Azure CLI and PowerShell options together, or list Azure CLI first to avoid implicit Windows-first ordering.
  • Add notes clarifying that all steps can be performed on Linux, macOS, or Windows, and provide links to cross-platform tool documentation.
  • Review and update sample scripts and templates to ensure they are platform-agnostic and do not assume a Windows environment.
GitHub Create Pull Request
Service Fabric Add Azure Dedicated Host to a Service Fabric managed cluster (SFMC) ...rvice-fabric/how-to-managed-cluster-dedicated-hosts.md
High Priority View Details →
Scanned: 2026-01-09 19: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 Windows bias by providing only PowerShell-based command-line examples for resource creation, role assignment, and deployment. There are no equivalent examples for Linux users (e.g., Bash/CLI), and the use of PowerShell is assumed throughout. Additionally, administrative access is described in terms of RDP, which is a Windows-centric remote access method, with no mention of SSH for Linux VMs.
Recommendations
  • Add Azure CLI (az) command examples alongside PowerShell for all resource creation, role assignment, and deployment steps.
  • Include instructions and examples for Linux users, such as using SSH for VM access instead of only RDP.
  • Clearly indicate that both Windows and Linux VMs are supported, and provide guidance for both platforms where relevant.
  • Where templates or scripts are referenced, specify any platform requirements or provide cross-platform alternatives.
GitHub Create Pull Request
Service Fabric Deploy app with a user-assigned managed identity ...vice-fabric-application-user-assigned-managed-identity.md
High Priority View Details →
Scanned: 2026-01-09 19:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation references PowerShell for managing user-assigned managed identities and links to PowerShell-specific guides, without mentioning or providing examples for Linux tools or CLI equivalents. There are no Linux-specific instructions or examples, and the only management tool referenced is PowerShell, which is traditionally associated with Windows environments.
Recommendations
  • Include Azure CLI examples and references alongside or before PowerShell, as Azure CLI is cross-platform and widely used on Linux.
  • Provide links to Linux-friendly documentation for managing user-assigned managed identities.
  • Explicitly mention that the steps can be performed on Linux, and clarify any platform-specific requirements or differences.
  • Add a section or note for Linux users, highlighting equivalent commands and tools.
GitHub Create Pull Request
Service Fabric Configure autoscaling for Service Fabric managed cluster nodes ...les/service-fabric/how-to-managed-cluster-autoscale.md
High Priority View Details →
Scanned: 2026-01-09 19: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 demonstrates a strong Windows bias. All command-line examples use PowerShell and Azure PowerShell modules, with no mention of equivalent Linux or cross-platform CLI commands (e.g., Azure CLI). Windows-specific scenarios (such as Hyper-V/nested virtualization) are discussed, while Linux equivalents are omitted. The documentation assumes the use of Windows tooling and patterns, and does not provide parity for Linux users.
Recommendations
  • Provide equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Explicitly mention that autoscaling and Service Fabric managed clusters are supported on both Windows and Linux node types, and clarify any OS-specific limitations.
  • Include troubleshooting steps and metric collection examples using Azure CLI and/or Bash scripts, not just PowerShell.
  • Discuss Linux-specific considerations (e.g., memory metrics, VM configuration) alongside Windows-specific notes.
  • Review and update all sample templates and deployment instructions to ensure they are OS-agnostic or provide both Windows and Linux variants.
GitHub Create Pull Request
Service Fabric Create a Service Fabric managed cluster (SFMC) with Ephemeral OS disks for node types ...ce-fabric/how-to-managed-cluster-ephemeral-os-disks.md
High Priority View Details →
Scanned: 2026-01-09 19:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by exclusively providing deployment instructions using PowerShell cmdlets and referencing RDP (Remote Desktop Protocol) for VM administration, both of which are Windows-centric. There are no examples or guidance for Linux users, such as using Azure CLI, Bash, or SSH for administration or deployment. The order of presentation also places Windows tools and patterns first, with no mention of Linux alternatives.
Recommendations
  • Add equivalent deployment instructions using Azure CLI (az deployment group create) with Bash examples.
  • Include guidance for Linux users on connecting to VMs via SSH, rather than only mentioning RDP.
  • Present both Windows and Linux administration options side-by-side, or alternate their order to avoid implicit prioritization.
  • Reference cross-platform tools and patterns (e.g., Azure CLI, REST API) before or alongside Windows-specific tools.
  • Explicitly state that the process is platform-agnostic where possible, and provide links to both Windows and Linux documentation for related tasks.
GitHub Create Pull Request
Service Fabric Initializer CodePackages in Service Fabric ...in/articles/service-fabric/initializer-codepackages.md
High Priority View Details →
Scanned: 2026-01-09 19:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a strong Windows bias. All code examples use Windows containers (mcr.microsoft.com/windows/nanoserver:1809), Windows-specific paths (C:\WorkspaceOnHost), and Windows shell commands (cmd, type, ping). The example explicitly assumes familiarity with creating Windows container applications and references Windows container compatibility. There are no examples or guidance for Linux containers, Linux paths, or Linux shell commands, nor is there mention of Linux equivalents for the demonstrated patterns.
Recommendations
  • Add parallel examples using Linux containers (e.g., mcr.microsoft.com/ubuntu or other Linux images) and Linux shell commands (bash, echo, cat, etc.).
  • Include Linux-specific path examples (e.g., /workspace/log.txt) and volume mounts.
  • Reference documentation for creating Linux container applications in Service Fabric alongside Windows examples.
  • Clarify whether Initializer CodePackages are supported for Linux containers and provide any platform-specific considerations.
  • Present both Windows and Linux examples in each section, or alternate their order to avoid implicit prioritization.
GitHub Create Pull Request
Service Fabric Use a Public IP address prefix in a Service Fabric managed cluster ...vice-fabric/how-to-managed-cluster-public-ip-prefix.md
High Priority View Details →
Scanned: 2026-01-09 19:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page presents Azure CLI and Azure PowerShell examples for deploying a public IP prefix in a Service Fabric managed cluster. PowerShell, a Windows-centric tool, is given a dedicated section, and references to PowerShell appear before any mention of Linux-specific tools or workflows. There are no explicit Linux shell (bash) examples, nor are Linux-specific deployment patterns (such as using Bash scripts or cloud-init) discussed. The documentation implicitly assumes familiarity with Windows tooling and does not provide parity for Linux users.
Recommendations
  • Add explicit Bash shell examples for each step, especially for ARM template deployment (e.g., using az CLI from Bash).
  • Clarify that Azure CLI is cross-platform and provide Linux-specific instructions or notes where relevant.
  • Include references to Linux-native tools or workflows, such as using cloud-init or bash scripting for deployment.
  • Reorder sections so that cross-platform or Linux-friendly tools (Azure CLI, Bash) are presented before Windows-centric tools (PowerShell).
  • Explicitly state platform compatibility for each tool and example, helping users choose the best workflow for their OS.
GitHub Create Pull Request
Service Fabric Create a Service Fabric cluster using Bicep ...in/articles/service-fabric/quickstart-cluster-bicep.md
High Priority View Details →
Scanned: 2026-01-09 19:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily biased toward Windows environments. All examples use PowerShell, including certificate creation and deployment steps. The Service Fabric cluster is specified as a Windows cluster, and certificate creation references Windows Server certificate services for production. There are no Linux-specific instructions, examples, or alternatives for certificate creation, deployment, or cluster configuration. The use of Windows tools and PowerShell is pervasive, and Linux equivalents (such as Bash, OpenSSL, or Azure CLI for all steps) are missing or only mentioned as an afterthought (e.g., CLI for resource deletion).
Recommendations
  • Provide parallel instructions and examples for Linux environments, including Bash and Azure CLI commands for all steps.
  • Include instructions for creating self-signed certificates using OpenSSL, and uploading them to Azure Key Vault from Linux.
  • Clarify how to deploy a Linux-based Service Fabric cluster, or note if only Windows clusters are supported.
  • Ensure all scripts and helper tools (such as New-ServiceFabricClusterCertificate.ps1) have Linux-compatible equivalents.
  • Present CLI and Bash examples before or alongside PowerShell, not only in the clean-up section.
  • Explicitly state platform requirements and alternatives at the start of the documentation.
GitHub Create Pull Request
Service Fabric Quickly deploy an existing app to a cluster ...b/main/articles/service-fabric/quickstart-guest-app.md
High Priority View Details →
Scanned: 2026-01-09 19:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation is heavily oriented toward Windows development environments, specifically Visual Studio. All instructions and screenshots reference Visual Studio on Windows, with no mention of Linux or cross-platform alternatives. PowerShell scripts are referenced as the default deployment tooling, and Windows-specific issues (such as path length limits) are discussed without Linux equivalents. There are no examples or guidance for deploying from Linux or using Linux-native tools.
Recommendations
  • Add instructions for deploying a Node.js app to Service Fabric using Linux or macOS, including required SDKs and command-line tools.
  • Provide examples using cross-platform tools such as Azure CLI, Service Fabric CLI (sfctl), or VS Code.
  • Include Linux-specific guidance for project setup, deployment, and troubleshooting (e.g., file permissions, path conventions).
  • Reference Bash scripts or other Linux-native automation options alongside PowerShell.
  • Address Linux-specific considerations, such as service manifest editing and cluster connection, where relevant.
GitHub Create Pull Request
Service Fabric Describing Azure Service Fabric apps and services ...ic/service-fabric-application-and-service-manifests.md
High Priority View Details →
Scanned: 2026-01-09 19:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily through references to Windows-specific tools (Visual Studio, file paths like C:\Program Files\...), and by suggesting Windows workflows (using Visual Studio for XML schema validation) without mentioning Linux alternatives. There are no Linux-specific examples, tools, or instructions provided, and the only command-line reference is to the ServiceFabric PowerShell module, which is Windows-centric.
Recommendations
  • Add instructions for validating XML schema on Linux, such as using xmllint or other open-source editors (e.g., VS Code, Kate, or command-line tools).
  • Include Linux file path equivalents and clarify where Service Fabric SDK files are located on Linux systems.
  • Mention cross-platform editors (e.g., VS Code) and how to enable XML schema validation/intelli-sense on both Windows and Linux.
  • Provide examples or references for managing Service Fabric applications using Linux command-line tools (e.g., Azure CLI, sfctl) alongside PowerShell.
  • Ensure that any references to Windows-specific workflows are paired with Linux alternatives, or clarify platform limitations where applicable.
GitHub Create Pull Request
Service Fabric Advanced Application Upgrade Topics ...-fabric/service-fabric-application-upgrade-advanced.md
High Priority View Details →
Scanned: 2026-01-09 19:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias, primarily by providing only PowerShell-based examples and references to Windows-centric tools and workflows (e.g., Visual Studio, PowerShell cmdlets). There is no mention of Linux equivalents, such as CLI commands, Bash scripts, or cross-platform Service Fabric tools. The ordering and language also prioritize Windows tools and patterns, with no guidance for Linux users.
Recommendations
  • Add equivalent examples using Azure CLI, Bash scripts, or REST API calls for all PowerShell cmdlet usage.
  • Explicitly mention and demonstrate how to perform Service Fabric upgrades on Linux clusters, including any differences in configuration or tooling.
  • Include cross-platform instructions and clarify which steps or tools are Windows-only, providing alternatives for Linux.
  • Reference Linux-compatible editors and deployment workflows (e.g., VS Code, command-line tools) alongside Visual Studio.
  • Ensure that ARM template examples and service manifest configuration steps are shown with cross-platform context, not assuming a Windows environment.
GitHub Create Pull Request
Service Fabric Troubleshooting application upgrades ...https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-application-upgrade-troubleshooting.md
High Priority View Details →
Scanned: 2026-01-09 19: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 demonstrates a strong Windows bias. All command-line examples use PowerShell cmdlets (e.g., Get-ServiceFabricApplicationUpgrade), with no mention of Linux/Unix equivalents such as the Service Fabric CLI (sfctl) or REST API. The tools and troubleshooting patterns described are specific to Windows environments, and the 'Next steps' section lists Visual Studio and PowerShell tutorials before any mention of cross-platform or Linux tools. There are no Linux-specific instructions or examples, and no guidance for users managing Service Fabric clusters from Linux or macOS.
Recommendations
  • Add equivalent examples using the Service Fabric CLI (sfctl), which is cross-platform, alongside or in place of PowerShell examples.
  • Explicitly mention REST API options for troubleshooting upgrades, which are platform-agnostic.
  • Include troubleshooting steps and command examples that can be run from Linux or macOS environments.
  • In the 'Next steps' section, add links to tutorials for upgrading applications using sfctl or REST API, and ensure these are listed alongside PowerShell/Visual Studio options.
  • Clarify in the introduction that the documented commands are PowerShell-specific and provide guidance for Linux users.
  • Where possible, use neutral language (e.g., 'use your preferred tool such as PowerShell or sfctl') rather than assuming a Windows environment.
GitHub Create Pull Request
Service Fabric Learn about Azure Service Fabric application security ...ric/service-fabric-application-and-service-security.md
High Priority View Details →
Scanned: 2026-01-09 19:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias in several areas: Windows-specific tools and patterns (Active Directory, gMSA, BitLocker) are mentioned explicitly and often before or instead of Linux equivalents. Examples and instructions for running services under security accounts focus on Windows (domain accounts, gMSA), with Linux alternatives either missing or referenced only briefly. Disk encryption is discussed with a PowerShell/BitLocker focus, while Linux disk encryption is left as a TODO. There are no Linux-specific code samples or detailed instructions for Linux security features.
Recommendations
  • Add explicit Linux examples for running services under local/system accounts and securing resources, including references to Linux user/group management.
  • Provide parity for disk encryption: include instructions and references for encrypting disks on Linux clusters (e.g., using dm-crypt/LUKS), not just BitLocker/PowerShell.
  • When mentioning Windows-specific features (Active Directory, gMSA), also describe Linux equivalents or alternatives (e.g., LDAP, local users/groups, systemd service accounts).
  • Ensure code samples and walkthroughs are available for both Windows and Linux environments, especially for certificate management, service startup scripts, and endpoint security.
  • Review and update the documentation to avoid Windows-first ordering; present cross-platform options side-by-side or in parallel sections.
GitHub Create Pull Request
Service Fabric Capacity planning and scaling for Azure Service Fabric ...bric/service-fabric-best-practices-capacity-scaling.md
High Priority View Details →
Scanned: 2026-01-09 19: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 demonstrates a Windows bias in several ways: PowerShell commands are used exclusively for manual scaling operations, with no equivalent Linux shell or cross-platform CLI examples provided. Windows-centric tools and patterns (such as PowerShell cmdlets like Disable-ServiceFabricNode and Remove-ServiceFabricNodeState) are referenced without mention of Linux alternatives. The step-by-step instructions for scaling in and out begin with PowerShell commands, and there is no guidance for users managing Service Fabric clusters from Linux environments. While links to Linux cluster creation are present in 'Next steps', the operational guidance throughout the page is Windows-first and omits Linux parity.
Recommendations
  • Provide equivalent Linux shell (bash) or Azure CLI examples for all PowerShell commands, especially for node management and scaling operations.
  • Explicitly mention cross-platform tools and workflows where possible, and clarify which commands are OS-specific.
  • Include guidance or references for managing Service Fabric clusters from Linux environments, such as using Azure CLI, REST API, or Service Fabric SDK for Linux.
  • Balance the order of examples and instructions so that Linux and Windows approaches are presented equally, or clarify when an example is Windows-specific.
  • Add a table or section summarizing available management tools for both Windows and Linux, including PowerShell, Azure CLI, REST API, and Service Fabric Explorer.
GitHub Create Pull Request
Service Fabric Service Fabric cluster capacity planning considerations ...cles/service-fabric/service-fabric-cluster-capacity.md
High Priority View Details →
Scanned: 2026-01-09 19:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools and configuration files (e.g., 'AzureDeploy.json', 'Remove-ServiceFabricNodeState', and 'service-fabric-cluster-config-upgrade-windows-server.md') without providing equivalent Linux examples or mentioning Linux-specific tools. Instructions for standalone clusters are only given for Windows, and automation of updates is discussed only in the context of Windows. Linux scenarios, tools, or configuration patterns are not mentioned or illustrated.
Recommendations
  • Add explicit examples and instructions for Linux-based Service Fabric clusters, including configuration, scaling, and upgrade procedures.
  • Reference Linux equivalents for configuration files and management tools (e.g., provide guidance for cluster config changes using Linux paths and tools).
  • Include automation and update strategies for Linux clusters, such as using cron jobs or Linux-native patch orchestration tools.
  • When mentioning Windows-specific commands or files, provide parallel Linux commands or configuration file formats.
  • Ensure that documentation for standalone clusters covers both Windows and Linux environments equally, with clear sectioning and parity in depth.
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
High Priority View Details →
Scanned: 2026-01-09 19: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 demonstrates a Windows bias by providing only PowerShell command examples for managing node tags and service requirements, without any equivalent examples for Linux environments (e.g., Bash, CLI). The use of PowerShell and Windows-centric tools is emphasized, and there is no mention of Linux-specific workflows or cross-platform command-line alternatives. This may hinder Linux users from easily following the documentation or applying the feature in non-Windows environments.
Recommendations
  • Add Azure CLI or Bash examples for all PowerShell commands shown, demonstrating how to manage node tags and service requirements from Linux environments.
  • Explicitly mention cross-platform support and provide guidance for Linux administrators, including any prerequisites or differences in workflow.
  • Reference REST API usage with curl or similar tools to show platform-agnostic approaches.
  • Ensure that examples and instructions are presented in a way that does not assume a Windows environment by default.
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
High Priority View Details →
Scanned: 2026-01-09 19: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 demonstrates a strong Windows bias by exclusively providing PowerShell-based examples and instructions, which are native to Windows environments. All command-line operations, REST API calls, and module installation steps are shown using PowerShell syntax and Windows-centric tools (e.g., Microsoft.ServiceFabric.Powershell.Http). There are no equivalent examples or instructions for Linux users (such as Bash, curl, or Azure CLI), nor is there mention of cross-platform alternatives. The documentation implicitly assumes the user is operating in a Windows environment, making it less accessible to Linux or macOS administrators.
Recommendations
  • Add Linux/Bash examples for all PowerShell commands, using curl or wget for REST API calls.
  • Provide Azure CLI equivalents for Service Fabric operations where possible.
  • Include instructions for installing and using Service Fabric tools on Linux and macOS.
  • Explicitly state cross-platform support and limitations for Service Fabric backup operations.
  • Reorganize examples to present both Windows and Linux approaches side-by-side, or clarify platform-specific sections.
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
High Priority View Details →
Scanned: 2026-01-09 19:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides command-line examples exclusively using PowerShell for service creation and update, which is primarily a Windows tool. There are no Linux shell (bash/CLI) equivalents or references to Linux-native tools. The ordering and presence of examples suggest a Windows-first approach, and Linux users are left without guidance for equivalent operations.
Recommendations
  • Add equivalent Linux CLI examples using Azure CLI or Service Fabric CLI (sfctl) for all PowerShell commands.
  • Explicitly mention platform compatibility for each example, clarifying which commands are for Windows and which are for Linux.
  • Include notes or sections for Linux users, detailing how to perform the same tasks on Linux clusters.
  • Ensure that documentation does not assume PowerShell as the default, and present cross-platform options side-by-side where possible.
GitHub Create Pull Request
Service Fabric Roll over an Azure Service Fabric cluster certificate ...vice-fabric/service-fabric-cluster-rollover-cert-cn.md
High Priority View Details →
Scanned: 2026-01-09 19:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides only a Windows PowerShell script for rolling over an Azure Service Fabric cluster certificate, with no equivalent Bash, CLI, or Linux-based example. The instructions and file paths are Windows-centric, and there is no mention of Linux tooling or cross-platform alternatives.
Recommendations
  • Add equivalent instructions and examples using Azure CLI and Bash scripts suitable for Linux environments.
  • Include notes on how to perform certificate management tasks on Linux-based Service Fabric clusters.
  • Use platform-neutral file paths and commands where possible, or provide both Windows and Linux variants.
  • Explicitly mention cross-platform support and link to relevant documentation for Linux users.
GitHub Create Pull Request
Service Fabric Scale a Service Fabric cluster in or out .../service-fabric/service-fabric-cluster-scale-in-out.md
High Priority View Details →
Scanned: 2026-01-09 19:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a Windows bias by predominantly featuring PowerShell commands and Windows-centric tools (e.g., Remove-ServiceFabricNodeState cmdlet, Get-ServiceFabricNode), with most examples and instructions given in PowerShell before CLI or sfctl equivalents. There is little to no mention of Linux-specific workflows, and Linux-friendly alternatives are not highlighted or explained. The documentation assumes familiarity with Windows tooling and omits guidance for Linux users, such as bash scripting or Linux-native Service Fabric management patterns.
Recommendations
  • Provide Linux-specific examples and workflows alongside PowerShell, such as bash scripts or equivalent commands using sfctl and Azure CLI.
  • Clearly indicate which commands and tools are platform-specific (Windows vs. Linux) and offer parity in instructions for both environments.
  • Where PowerShell is used, offer the same step-by-step guidance using Azure CLI and sfctl, with explicit notes for Linux users.
  • Add a section or callouts for Linux administrators, including troubleshooting tips and best practices for Service Fabric management on Linux.
  • Review references to Windows-only features (e.g., Hyper-V, dynamic memory driver) and clarify their relevance or alternatives for Linux clusters.
GitHub Create Pull Request
Service Fabric Azure Service Fabric standalone cluster scaling ...ce-fabric/service-fabric-cluster-scaling-standalone.md
High Priority View Details →
Scanned: 2026-01-09 19: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 demonstrates a Windows bias by exclusively referencing Windows-specific tools and patterns, such as PowerShell cmdlets (Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade), and linking to guides that focus on Windows Server. There are no examples or instructions for scaling Service Fabric standalone clusters on Linux, nor are Linux tools or commands mentioned. The documentation implicitly assumes a Windows environment for standalone clusters, which may exclude or confuse users deploying Service Fabric on Linux.
Recommendations
  • Provide equivalent Linux instructions and examples, including relevant shell commands and configuration steps.
  • Reference Linux-compatible tools (e.g., Service Fabric CLI, REST API) alongside or before Windows-specific tools.
  • Add links to documentation for scaling Service Fabric clusters on Linux, if available.
  • Clarify which instructions are Windows-specific and offer Linux alternatives where possible.
  • Ensure that terminology and examples do not assume a Windows-only environment for standalone clusters.
GitHub Create Pull Request
Service Fabric Standalone Cluster Deployment Preparation ...rvice-fabric-cluster-standalone-deployment-preparation.md
High Priority View Details →
Scanned: 2026-01-09 19:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page exhibits strong Windows bias: all instructions, requirements, and examples are exclusively for Windows Server environments. Only Windows OS versions are mentioned, with no reference to Linux. All tooling (e.g., PowerShell scripts, Windows services, NTFS, SMB, RemoteRegistry, Windows Firewall) is Windows-specific, and there are no Linux equivalents or alternative instructions. The configuration validation uses a PowerShell script with no mention of a cross-platform or Linux-compatible tool.
Recommendations
  • Add equivalent instructions and requirements for deploying Service Fabric clusters on Linux machines, including supported distributions and prerequisites.
  • Provide Linux-specific examples for configuration, environment setup, and validation, such as shell scripts or CLI commands.
  • Mention Linux file system requirements and alternatives to Windows services (e.g., systemd, firewalld, etc.).
  • Include download links and instructions for Service Fabric standalone packages for Linux.
  • Document how to validate cluster configuration and environment on Linux, possibly with Bash scripts or cross-platform tools.
  • Ensure parity in troubleshooting and next steps for Linux deployments.
GitHub Create Pull Request
← Previous Page 7 of 29 Next →