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 376-400 of 718 flagged pages
Service Fabric Azure Service Fabric container image management .../articles/service-fabric/container-image-management.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page shows bias toward Windows environments by referencing Windows-specific container images (microsoft/windowsservercore, microsoft/nanoserver) as defaults to skip during cleanup, with no mention of Linux equivalents. The examples and descriptions prioritize Windows images, and there are no Linux-specific examples or guidance. This may cause confusion or extra effort for Linux/macOS users managing Service Fabric clusters.
Recommendations
  • Include Linux container images (e.g., Ubuntu, Alpine, CentOS) in the 'ContainerImagesToSkip' examples and documentation.
  • Clarify whether the cleanup logic applies equally to Linux-based images and provide explicit examples for those platforms.
  • Add notes or sections addressing Linux/macOS environments, including any differences in behavior or configuration.
  • Ensure that examples and defaults do not exclusively reference Windows images, or present Linux and Windows examples side by side.
GitHub Create Pull Request
Service Fabric Configure maintenance control for Service Fabric managed cluster ...e-fabric/how-to-managed-cluster-maintenance-control.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exclusively provides PowerShell-based examples and commands for configuring maintenance control on Service Fabric managed clusters. There are no CLI, Bash, or Linux/macOS-specific instructions, and all command-line steps assume the use of PowerShell and Azure PowerShell modules, which are most commonly used on Windows. This creates friction for Linux/macOS users who typically use Azure CLI or Bash scripts.
Recommendations
  • Add equivalent Azure CLI (az) command examples for all PowerShell steps, including resource group creation, cluster deployment, and maintenance configuration assignment.
  • Include Bash script snippets for Linux/macOS users where appropriate.
  • Explicitly mention cross-platform alternatives and clarify which tools are supported on each OS.
  • Reorder examples so that CLI/Bash and PowerShell are presented together or in parallel, rather than PowerShell-only.
GitHub Create Pull Request
Service Fabric Configure autoscaling for Service Fabric managed cluster nodes ...les/service-fabric/how-to-managed-cluster-autoscale.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
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 notable Windows bias. All command-line examples use PowerShell cmdlets (e.g., New-AzResourceGroup, New-AzResourceGroupDeployment, Remove-AzResource), which are native to Windows and require either a Windows environment or installation of PowerShell Core on Linux/macOS. There are no equivalent examples using Azure CLI, Bash, or other cross-platform tools. The troubleshooting section also references PowerShell modules (Get-AzMetric) exclusively. Windows terminology and tools are presented first and exclusively, with no mention of Linux/macOS alternatives or parity.
Recommendations
  • Provide equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that PowerShell Core can be installed on Linux/macOS, but recommend Azure CLI for native experience.
  • Add Bash script examples for resource group and cluster deployment steps.
  • Include troubleshooting steps using Azure CLI or REST API, not just PowerShell.
  • Clarify any OS-specific limitations (e.g., the note about Windows OS image and Hyper-V) and provide Linux-specific guidance where relevant.
GitHub Create Pull Request
Service Fabric Upgrading Azure Service Fabric managed clusters ...cles/service-fabric/how-to-managed-cluster-upgrades.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by only listing Windows-based cluster versions in its REST API example output, with no mention of Linux equivalents. There are no explicit Linux-specific instructions, examples, or references to Linux cluster versions, which may lead Linux users to believe that only Windows clusters are supported or relevant for these upgrade operations.
Recommendations
  • Include examples of Linux cluster versions in the REST API output, showing both Windows and Linux entries.
  • Explicitly mention that Service Fabric managed clusters can be Linux-based, and clarify any differences in upgrade procedures or supported versions.
  • Add references or links to documentation about Linux cluster management and upgrade processes.
  • Where OS-specific properties or behaviors exist, document them for both Windows and Linux clusters.
GitHub Create Pull Request
Service Fabric Deploy a Service Fabric cluster using the Azure portal ...es/service-fabric/quickstart-classic-cluster-portal.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively guides users to deploy a Service Fabric cluster using Windows Server 2019-Datacenter virtual machines, with no mention of Linux-based clusters or instructions for deploying on Linux. The operating system selection is hardcoded to Windows, and there are no examples, notes, or alternatives for Linux users. This creates friction for users who prefer or require Linux environments.
Recommendations
  • Include instructions and screenshots for deploying a Service Fabric cluster using Linux-based VM images (e.g., Ubuntu).
  • Add a section or note explaining the differences and considerations between Windows and Linux clusters.
  • Provide parity in certificate management steps for Linux (e.g., how to import and use certificates on Linux systems).
  • Ensure that the operating system dropdown selection is discussed, and both Windows and Linux options are shown.
  • Clarify any limitations or feature differences between Windows and Linux clusters.
GitHub Create Pull Request
Service Fabric Create clusters on Windows Server and Linux ...rvice-fabric/service-fabric-azure-clusters-overview.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page describes Service Fabric clusters on both Windows Server and Linux, but the technical details and examples are heavily skewed toward Windows. The only runtime process mentioned is FabricHost.exe and related Windows executables, with no mention of Linux equivalents or processes. There are no Linux-specific examples, commands, or operational notes, and Windows terminology and tooling are presented first and exclusively.
Recommendations
  • Include Linux-specific details, such as the names of equivalent Service Fabric processes and how they are managed on Linux (e.g., systemd services, process names).
  • Provide examples or notes for both Windows and Linux environments, especially in sections describing node setup and runtime behavior.
  • Add guidance or links for Linux users regarding cluster creation, management, and troubleshooting.
  • Ensure parity in operational instructions, such as how to start/stop Service Fabric services on Linux.
  • Explicitly mention any differences or considerations for Linux deployments, including supported distributions and configuration nuances.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Central Secret Service ...vice-fabric/service-fabric-application-secret-store.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exhibits a notable Windows bias. All command-line examples for interacting with the Central Secret Service REST API use PowerShell and Windows-specific tooling (Invoke-WebRequest, CertificateThumbprint), with no equivalent Linux/macOS examples (e.g., curl, openssl). Windows paths (C:\secrets) are shown first and in mainline examples, while Linux paths (/mnt/secrets) are relegated to comments. There is no guidance for Linux authentication or certificate handling, and no mention of Linux/macOS shell usage for API calls.
Recommendations
  • Provide REST API usage examples using curl for Linux/macOS, including authentication with client certificates.
  • Document how to obtain and use certificate thumbprints or equivalents on Linux/macOS.
  • Show Linux file paths and container mount points in main examples, not just as commented alternatives.
  • Clarify any OS-specific requirements or differences in Service Fabric cluster setup and secret management.
  • Ensure all critical workflows (create, set, examine secrets) have both Windows and Linux/macOS instructions.
GitHub Create Pull Request
Service Fabric Differences between Cloud Services (extended support) and Service Fabric ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cloud-services-migration-differences.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation references Service Fabric running on both Windows and Linux, but examples and tool mentions (e.g., Connect-WindowsFabricCluster) are Windows-centric. There is no mention of Linux-specific tools, commands, or migration considerations, and Windows tools are referenced before any Linux alternatives. No Linux/macOS command-line examples or parity notes are provided.
Recommendations
  • Include Linux/macOS equivalents for any Windows-specific tools or commands mentioned (e.g., reference Service Fabric CLI or REST APIs usable on Linux).
  • Add explicit examples or notes for Linux deployments, such as package management, cluster setup, and service management.
  • Where Windows tools are mentioned, provide Linux alternatives in parallel and clarify any platform-specific differences.
  • Ensure that API usage and migration steps are described in a cross-platform manner, highlighting any OS-specific considerations.
GitHub Create Pull Request
Service Fabric Describe a cluster by using Cluster Resource Manager ...ce-fabric-cluster-resource-manager-cluster-description.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
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 moderate Windows bias. Configuration examples and code samples frequently use Windows-centric formats (ClusterManifest.xml with <WindowsServer>), and PowerShell is the only CLI shown for service creation and updates. There are no Linux-specific examples, nor is there mention of Linux tools or shell commands. The documentation assumes familiarity with Windows constructs and does not provide parity for Linux/macOS users, especially in operational scenarios.
Recommendations
  • Add explicit examples for Linux clusters, such as configuration snippets using <Linux> infrastructure in ClusterManifest.xml.
  • Provide equivalent Bash/CLI commands for service creation and updates, using Service Fabric CLI (sfctl) or REST API, alongside PowerShell.
  • Clarify which configuration formats and tools are cross-platform, and note any differences or requirements for Linux/macOS clusters.
  • Include notes or links to Linux/macOS setup guides for standalone Service Fabric clusters.
  • Ensure that all operational instructions (service creation, updates, cluster configuration) have Linux/macOS equivalents.
GitHub Create Pull Request
Service Fabric Update a cluster to use certificate common name ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-change-cert-thumbprint-to-cn.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
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 deployment examples, referencing Windows-style file paths, and omitting equivalent Linux/macOS command-line instructions. There are no Bash, Azure CLI, or cross-platform examples for deploying the updated ARM template, which may create friction for users on non-Windows platforms.
Recommendations
  • Add Azure CLI examples for deploying ARM templates, which work on Linux, macOS, and Windows.
  • Include Bash shell command examples for template deployment.
  • Use platform-neutral file path examples or clarify usage for different OSes.
  • Explicitly mention that all steps can be performed from Linux/macOS using Azure CLI or other supported tools.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager: Movement cost ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-movement-cost.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides PowerShell and C# examples for configuring Service Fabric move cost, but does not include equivalent Linux/macOS command-line examples (such as Bash, Azure CLI, or REST API). PowerShell is Windows-centric, and its exclusive use in examples creates friction for Linux/macOS users. The page also presents PowerShell before C#, reinforcing a Windows-first approach.
Recommendations
  • Add Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform.
  • Include REST API examples for service creation and updates, which are platform-agnostic.
  • Explicitly mention Linux/macOS support for Service Fabric management tasks and link to relevant cross-platform tooling.
  • Reorder examples to present cross-platform options (CLI, REST) before or alongside PowerShell.
  • Clarify any platform-specific limitations or requirements for Service Fabric management.
GitHub Create Pull Request
Service Fabric Create a Service Fabric cluster in the Azure portal ...e-fabric/service-fabric-cluster-creation-via-portal.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation describes creating a Service Fabric cluster in Azure using the portal, which supports both Linux and Windows clusters. However, the examples and instructions consistently reference Windows-centric concepts (e.g., Remote Desktop username/password for VMs, PowerShell for management operations) and do not provide Linux-specific guidance (e.g., SSH access, Linux CLI commands). There are no explicit Linux management or connection examples, and Windows terminology appears first or exclusively in key sections.
Recommendations
  • Include explicit instructions for connecting to Linux-based cluster nodes, such as SSH access, and clarify differences in authentication (e.g., SSH keys vs. RDP credentials).
  • Provide Linux/macOS CLI examples for cluster management alongside PowerShell examples.
  • When mentioning VM access, specify both Windows (RDP) and Linux (SSH) scenarios, and offer guidance for setting up SSH keys in the portal.
  • Ensure that screenshots and terminology are inclusive of both OS types, or clearly indicate when steps differ for Linux clusters.
  • Add notes or sections for Linux-specific troubleshooting and operational patterns.
GitHub Create Pull Request
Service Fabric Upgrade an Azure Service Fabric standalone cluster ...ce-fabric/service-fabric-cluster-upgrade-standalone.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias by referencing Windows-specific upgrade guides and tools, such as the Patch Orchestration Application for Windows, and by linking only to Windows Server-specific upgrade instructions. There is no mention of Linux equivalents or examples, and all upgrade/configuration references point to Windows-focused documentation.
Recommendations
  • Include explicit instructions, examples, and links for upgrading and configuring Service Fabric clusters on Linux.
  • Reference or create documentation for Linux patch orchestration and OS management within Service Fabric clusters.
  • Ensure that all major sections (upgrade, configuration, patching) provide parity between Windows and Linux, with side-by-side examples or clear navigation to Linux-specific guides.
  • Avoid using 'Windows Server' in link titles unless a Linux equivalent is also provided.
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-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation provides code examples for configuring auto scaling policies using application manifests, C# APIs, and PowerShell. PowerShell is a Windows-centric tool, and no equivalent Linux/macOS CLI examples (such as Bash, Azure CLI, or REST API) are provided. The use of PowerShell is shown in every example section, and there is no mention of Linux-native tools or workflows. Additionally, resource monitoring for noncontainerized applications is explicitly stated as Windows-only, with Linux support limited to containerized workloads.
Recommendations
  • Add Linux/macOS-friendly examples using Azure CLI, Bash scripts, or REST API for configuring scaling policies.
  • Clarify cross-platform support for Service Fabric management tools and provide links to Linux-compatible alternatives.
  • Explicitly document any feature limitations for Linux clusters and suggest workarounds or alternatives where possible.
  • Present examples in a platform-neutral order (e.g., manifest, CLI, then PowerShell), or group by OS to avoid Windows-first bias.
GitHub Create Pull Request
Service Fabric Upgrading Azure Service Fabric clusters ...icles/service-fabric/service-fabric-cluster-upgrade.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits moderate Windows bias. While most upgrade concepts are platform-neutral, specific operational examples and linked resources (such as OS patching) focus on Windows, and PowerShell is mentioned as a management tool without equivalent Linux/macOS command examples. The section on OS image upgrades links only to Windows patching guidance, omitting Linux. References to PowerShell/Azure CLI do not clarify parity or provide Linux-specific instructions.
Recommendations
  • Add explicit Linux/macOS examples for cluster management tasks, including Azure CLI and bash commands.
  • Include links to Linux patching guidance for Service Fabric clusters alongside Windows patching documentation.
  • Clarify that Azure CLI is cross-platform and provide sample commands for both Windows (PowerShell) and Linux/macOS (bash).
  • Ensure that all operational sections (e.g., certificate management, port opening) show both Windows and Linux workflows.
  • Review linked documents to ensure Linux parity and update cross-references as needed.
GitHub Create Pull Request
Service Fabric Manage Service Fabric cluster upgrades ...fabric/service-fabric-cluster-upgrade-version-azure.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides PowerShell-only instructions for validating upgrade paths, with no equivalent CLI, Bash, or Linux-native examples. Windows environments are listed first in cluster version outputs, and the only upgrade path validation steps are Windows-centric. Linux users are left to infer or research their own approach, creating friction for non-Windows administrators.
Recommendations
  • Add Azure CLI and/or Bash examples for upgrade path validation alongside PowerShell.
  • Explicitly mention Linux/macOS compatibility for all steps, especially scripting and automation.
  • Provide example outputs and instructions for both Windows and Linux environments in all relevant sections.
  • Ensure that Linux cluster version information is presented with equal prominence to Windows.
GitHub Create Pull Request
Service Fabric Deploy an existing executable to Azure Service Fabric ...s/service-fabric/service-fabric-deploy-existing-app.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows tooling (Visual Studio, PowerShell) is described first and in greater detail, with step-by-step instructions and feature explanations. Linux alternatives (Yeoman, shell) are mentioned later and with less detail. The deployment section provides only PowerShell scripts for deploying the application, with no Linux CLI or Bash equivalents. Examples and screenshots are Windows-centric, and batch/PowerShell scripts are referenced without Linux shell script alternatives.
Recommendations
  • Provide Linux/Bash equivalents for all PowerShell deployment scripts, using Service Fabric CLI (sfctl) or REST API.
  • Include step-by-step instructions for Yeoman that match the detail given for Visual Studio.
  • Add examples of Linux shell scripts for setup and initialization, alongside batch/PowerShell examples.
  • Ensure screenshots and file paths include Linux variants (e.g., /home/user/app instead of C:\Dev\...).
  • Present Linux and Windows tooling in parallel, rather than Windows-first ordering.
  • Clarify any platform-specific limitations or differences in Service Fabric Explorer and related tools.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Events ...es/service-fabric/service-fabric-diagnostics-events.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows Event logs, ETW, and the Windows Azure diagnostics agent as primary mechanisms for accessing Service Fabric events. There are no explicit examples or guidance for accessing events on Linux-based clusters, nor are Linux-native tools or logging channels mentioned. The order and emphasis favor Windows approaches, potentially leaving Linux/macOS users without clear instructions.
Recommendations
  • Add explicit instructions and examples for accessing Service Fabric events on Linux clusters, including references to Linux-native logging systems (e.g., journald, syslog).
  • Mention cross-platform tools and APIs (such as REST APIs and the Service Fabric Client Library) as primary options, and clarify their applicability to both Windows and Linux clusters.
  • Reorder sections to present platform-neutral or cross-platform methods first, followed by platform-specific guidance.
  • Provide parity in diagnostic agent configuration instructions for Linux clusters, referencing the Linux diagnostics agent and its integration with Azure Monitor.
  • Include a comparison table or section outlining differences and similarities in event access between Windows and Linux clusters.
GitHub Create Pull Request
Service Fabric Azure Service Fabric hosting activation and deactivation life cycle ...les/service-fabric/service-fabric-hosting-lifecycle.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page exhibits a moderate Windows bias. PowerShell is referenced as the primary tool for deploying and removing applications, and the only explicit tooling example for downloading a ServicePackage in advance links to a PowerShell cmdlet. No Linux or cross-platform CLI examples are provided, and Windows-centric tools are mentioned before any Linux alternatives (which are absent).
Recommendations
  • Include equivalent Linux/macOS instructions using Azure CLI, Service Fabric CLI (sfctl), or REST API where applicable.
  • Provide examples for deploying, removing, and managing applications on Linux clusters.
  • Add references to Linux-specific documentation, tools, or scripts alongside PowerShell links.
  • Clearly indicate which steps or tools are platform-specific and offer alternatives for other platforms.
GitHub Create Pull Request
Service Fabric Report and check health with Azure Service Fabric ...ric-diagnostics-how-to-report-and-check-service-health.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a notable Windows bias: all setup, deployment, and health-check examples rely on Windows-specific tools (Visual Studio, PowerShell, Local Cluster Manager in the notification area). There are no Linux/macOS equivalents or instructions, and the examples and screenshots exclusively reference Windows environments and workflows. This creates friction for non-Windows users, who must find alternative tools and approaches not documented here.
Recommendations
  • Add instructions for setting up a local Service Fabric dev cluster on Linux/macOS, including required tools and commands.
  • Provide deployment and health-check examples using cross-platform tools (e.g., Azure CLI, REST API, Service Fabric CLI (sfctl)), and show how to use them on Linux/macOS.
  • Include Linux/macOS-specific prerequisites (e.g., .NET SDK, VS Code, or JetBrains Rider) and alternative project creation steps.
  • Show how to access Service Fabric Explorer from browsers on Linux/macOS, rather than relying on Windows notification area icons.
  • Present PowerShell and Windows examples alongside Linux/macOS equivalents, or use cross-platform commands first.
GitHub Create Pull Request
Service Fabric Overview of Azure Service Fabric ...ain/articles/service-fabric/service-fabric-overview.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows development tools (Visual Studio, PowerShell, .NET SDK) are mentioned first and in more detail than Linux equivalents. Linux tooling is referenced briefly (Eclipse, Yeoman, Java SDK), but without examples or parity in explanation. The quickstart link points to a .NET (Windows-centric) guide, with no visible Linux or cross-platform quickstart alternative. No Linux-specific examples or walkthroughs are provided.
Recommendations
  • Add Linux/macOS quickstart links alongside the Windows/.NET quickstart.
  • Provide example workflows and tooling for Linux (e.g., command-line deployment, SDK installation, cluster management) with equal detail.
  • Mention Linux tools (Eclipse, Yeoman, Java SDK) before or alongside Windows tools, and provide example usage.
  • Ensure all critical steps (deployment, management, monitoring) have both Windows and Linux/macOS instructions and examples.
  • Highlight cross-platform parity in the introduction and throughout the page.
GitHub Create Pull Request
Service Fabric Remove a node type in Azure Service Fabric | Microsoft Docs ...rvice-fabric/service-fabric-how-to-remove-node-type.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively uses PowerShell commands and Windows-centric tooling for all operational steps, with no mention of Linux/macOS equivalents or cross-platform alternatives. All code examples and instructions assume a Windows environment, creating friction for users on Linux or macOS who may not have access to PowerShell or the same command-line tools.
Recommendations
  • Provide equivalent instructions and examples using Azure CLI, which is cross-platform and widely used on Linux/macOS.
  • Explicitly mention how Linux/macOS users can perform each step, including any required setup (e.g., installing Azure CLI, using Bash scripts).
  • Add notes or sections clarifying platform requirements and offering guidance for non-Windows environments.
  • Where PowerShell is required, link to instructions for installing PowerShell Core on Linux/macOS, or offer alternative approaches.
  • Ensure that resource management steps (such as removing VM scale sets) are shown with both PowerShell and Azure CLI commands.
GitHub Create Pull Request
Service Fabric Service Fabric Backup and Restore ...ric/service-fabric-reliable-services-backup-restore.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. The only explicit tooling example for testing backup/restore uses the PowerShell cmdlet 'Start-ServiceFabricPartitionDataLoss', with no mention of Linux/macOS alternatives. References to .NET APIs and kernel32 (Windows-specific) for file operations further reinforce the Windows-centric approach. There are no examples or guidance for Linux/macOS users, such as using Service Fabric CLI (sfctl) or Bash scripts, and Windows tools are mentioned exclusively and first.
Recommendations
  • Add equivalent Linux/macOS instructions for testing backup/restore, such as using the Service Fabric CLI (sfctl) or REST API.
  • Provide Bash or cross-platform script examples alongside PowerShell.
  • Clarify which APIs and file operations are cross-platform, and offer alternatives for Linux/macOS (e.g., using standard Unix file utilities instead of kernel32).
  • Explicitly mention platform compatibility for all tools and APIs.
  • Reorder examples to present cross-platform or platform-neutral options first, or side-by-side.
GitHub Create Pull Request
Service Fabric Configure networking modes for container services ...cles/service-fabric/service-fabric-networking-modes.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows-specific instructions (such as NSG rules for UDP/53 and network recreation on VM reboot) are provided in detail, while Linux-specific guidance is minimal or absent. The ability to mix networking modes is highlighted for Windows clusters, but Linux clusters are explicitly limited without further explanation or workaround. Most examples and configuration snippets are generic, but Windows-specific scenarios are called out and explained, whereas Linux equivalents are not.
Recommendations
  • Provide explicit Linux-specific instructions for networking setup, including any required NSG rules or configuration differences.
  • Clarify limitations for Linux clusters and suggest possible workarounds or alternatives.
  • Include Linux-focused examples and troubleshooting steps, especially where Windows-specific behavior is described.
  • Balance documentation by presenting Linux and Windows scenarios side-by-side where differences exist.
  • Expand on the implications of not supporting mixed networking modes on Linux, and offer guidance for Linux users.
GitHub Create Pull Request
Service Fabric Configure Azure Service Fabric Reliable Services ...bric/service-fabric-reliable-services-configuration.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by referencing Windows tools (PowerShell, Visual Studio) and providing examples and instructions that assume a Windows development environment. Linux-specific instructions are minimal and only mentioned in passing (e.g., certificate format), with no Linux/macOS equivalents for key tasks like viewing the cluster manifest or editing configuration files. The use of Windows-style file paths and reliance on Visual Studio further reinforces the bias.
Recommendations
  • Provide Linux/macOS equivalents for commands such as viewing the cluster manifest (e.g., using sfctl or REST API).
  • Include examples of editing configuration files on Linux (e.g., using nano/vim and Linux file paths).
  • Offer guidance for configuring and deploying Service Fabric applications from Linux/macOS environments, including references to cross-platform tools.
  • Ensure parity in instructions for certificate management, debugging, and configuration, with clear Linux/macOS steps.
  • Avoid assuming the use of Visual Studio; mention alternatives such as VS Code or command-line workflows.
GitHub Create Pull Request
← Previous Page 16 of 29 Next →