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 276-300 of 718 flagged pages
Service Fabric Monitor a Service Fabric cluster in Azure ...vice-fabric/service-fabric-tutorial-monitor-cluster.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a notable Windows bias. It repeatedly references creating and monitoring a 'Windows cluster' without mentioning Linux clusters or providing Linux-specific instructions. Performance counter monitoring is described exclusively for Windows, and PowerShell cmdlets are used for health queries with no Linux or cross-platform CLI alternatives shown. Windows tools and references (e.g., Windows Performance Counters, PowerShell, Windows-specific articles) are mentioned exclusively or before any Linux equivalents, and there are no Linux/macOS examples or guidance for users of those platforms.
Recommendations
  • Add explicit instructions and examples for monitoring Service Fabric clusters running on Linux, including how to set up diagnostics, collect performance counters, and view health reports.
  • Include Azure CLI and REST API examples for health queries, not just PowerShell cmdlets.
  • Reference Linux performance counter collection methods and provide links to relevant documentation.
  • Clarify which steps and tools are Windows-only and provide Linux/macOS alternatives where possible.
  • Update prerequisites to mention Linux clusters and provide links to Linux cluster creation tutorials.
GitHub Create Pull Request
Service Fabric Visualizing your cluster using Azure Service Fabric Explorer ...vice-fabric/service-fabric-visualizing-your-cluster.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits several instances of Windows bias. While Service Fabric Explorer is described as cross-platform, key features such as EventStore APIs are explicitly stated to be available only for Windows clusters on Azure, with Linux support still in development. Automation examples reference PowerShell and REST API, but do not mention Linux-native tools or provide equivalent Linux/macOS command-line examples. The 'Next steps' section prioritizes Windows-centric tools (Visual Studio, PowerShell) and omits Linux/macOS alternatives. There is also a lack of explicit Linux/macOS usage instructions or screenshots.
Recommendations
  • Provide Linux/macOS command-line examples (e.g., using Bash, CLI tools) alongside PowerShell references.
  • Clarify feature parity and availability for Linux clusters, and update documentation as Linux support improves.
  • Include Linux/macOS-specific troubleshooting and setup instructions where relevant.
  • Add references to cross-platform deployment/management tools (such as Azure CLI, or Service Fabric CLI) in the 'Next steps' section.
  • Ensure screenshots and UI walkthroughs reflect usage on all supported platforms.
GitHub Create Pull Request
Service Fabric Learn about Azure Service Fabric application security ...ric/service-fabric-application-and-service-security.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a moderate Windows bias. Windows-specific tools and patterns (Active Directory, gMSA, BitLocker) are mentioned explicitly, often before or without Linux equivalents. Examples and guidance for running services under specific accounts are detailed for Windows (domain accounts, gMSA), while Linux options are referenced only briefly or left as TODOs. Disk encryption is described with a Windows PowerShell link, but Linux disk encryption is not covered. Some sections (e.g., securing containers) mention Linux support, but details and examples are sparse compared to Windows.
Recommendations
  • Add explicit Linux examples for running services under different user accounts, including how to configure principals and policies on Linux clusters.
  • Provide guidance and examples for encrypting disks on Linux clusters, such as using dm-crypt or Azure Disk Encryption for Linux.
  • Include Linux/macOS equivalents for Windows-specific tools (e.g., alternatives to Active Directory, gMSA) or clarify cross-platform options.
  • Balance examples and walkthroughs so that Linux instructions are presented alongside Windows, not as afterthoughts or TODOs.
  • Where possible, use platform-agnostic language and highlight cross-platform features.
GitHub Create Pull Request
Service Fabric Deploy and upgrade with Azure Resource Manager ...vice-fabric/service-fabric-application-arm-resource.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
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 notable Windows bias. PowerShell is the only command-line example provided for resource removal, with no equivalent Bash, Azure CLI, or Linux/macOS instructions. Windows tools and terminology (PowerShell, Remove-AzResource) are referenced exclusively or before alternatives. The 'Next steps' section lists PowerShell before CLI, and the page lacks explicit Linux/macOS guidance for key operations.
Recommendations
  • Provide Azure CLI and Bash examples alongside PowerShell for all command-line operations, especially for resource removal.
  • Explicitly mention that all ARM template operations can be performed from Linux/macOS using Azure CLI or REST API, and link to relevant documentation.
  • In 'Next steps', list cross-platform tools (CLI, REST API) before or alongside PowerShell.
  • Add notes or sections clarifying platform parity and any differences in workflow for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Application lifecycle in Service Fabric ...service-fabric/service-fabric-application-lifecycle.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
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 by consistently referencing PowerShell cmdlets and Windows-centric tools for Service Fabric management tasks. While REST API and .NET methods are mentioned, PowerShell examples are given for almost every operation, with no explicit Linux or cross-platform CLI (sfctl, Azure CLI) usage shown in examples or step-by-step instructions. The PowerShell cmdlets are often listed before REST or .NET alternatives, and there are no bash, Linux shell, or macOS-specific instructions or examples. This creates friction for Linux/macOS users, who must infer or seek out equivalent commands.
Recommendations
  • Add explicit examples using sfctl (Service Fabric CLI) and Azure CLI for all major lifecycle operations (deploy, upgrade, remove, test, etc.), alongside PowerShell.
  • Where PowerShell cmdlets are referenced, provide the Linux/macOS equivalent command immediately after or in parallel, not just as a footnote.
  • Include bash or shell script snippets for common tasks, especially in sections about automation and cleanup.
  • Clearly indicate which tools are cross-platform and which are Windows-only, and recommend cross-platform tools for general usage.
  • Reorder examples so that REST API, sfctl, and Azure CLI are shown first or equally with PowerShell, to avoid implicit prioritization of Windows tools.
GitHub Create Pull Request
Service Fabric Application upgrade: data serialization ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-application-upgrade-data-serialization.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily in the 'Next steps' section, where upgrade tutorials are provided for Visual Studio and PowerShell—both Windows-centric tools—without mention of Linux/macOS equivalents or cross-platform CLI options. The main body of the article is platform-neutral, focusing on C# and Service Fabric concepts, but the actionable guidance for upgrades is Windows-first and omits Linux-friendly alternatives.
Recommendations
  • Add explicit guidance and tutorials for upgrading applications on Linux/macOS, such as using Azure CLI, Service Fabric CLI (sfctl), or REST APIs.
  • Include links to cross-platform tools and documentation in the 'Next steps' section, ensuring parity with Windows instructions.
  • When listing upgrade methods, present cross-platform options before or alongside Windows-specific tools to avoid implicit prioritization.
  • Clarify which instructions are platform-specific and provide alternatives where possible.
GitHub Create Pull Request
Service Fabric Application upgrade: upgrade parameters ...abric/service-fabric-application-upgrade-parameters.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
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 notable Windows bias by presenting PowerShell and Visual Studio (Windows-only tools) as primary methods for application upgrade, with their parameters described in detail and listed before the cross-platform SFCTL CLI. Examples and parameter tables are heavily focused on PowerShell and Visual Studio, with Linux/macOS equivalents (SFCTL) relegated to a later section and described less thoroughly. There are no direct Linux shell examples, and the structure implies Windows tools are the default or preferred approach.
Recommendations
  • Present SFCTL (cross-platform CLI) examples and parameter tables before or alongside PowerShell/Visual Studio sections to avoid implying Windows-first workflows.
  • Include explicit Linux/macOS shell command examples for SFCTL, demonstrating parity with PowerShell workflows.
  • Add a summary table comparing PowerShell, Visual Studio, and SFCTL parameters to clarify cross-platform equivalence.
  • Reference Linux/macOS upgrade workflows in introductory sections, not only in 'Next steps'.
  • Clarify that PowerShell and Visual Studio are Windows-only, and SFCTL is recommended for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Service Fabric application upgrade ...s/service-fabric/service-fabric-application-upgrade.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
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 notable Windows bias. The only code example provided uses PowerShell, a Windows-centric tool, with no equivalent Bash, CLI, or Linux-native example. Windows-specific tools and APIs (e.g., http.sys, PowerShell cmdlets) are referenced exclusively or before any cross-platform alternatives. The troubleshooting and next steps sections also prioritize Windows tools (Visual Studio, PowerShell) without mentioning Linux/macOS workflows or tools. There is no guidance for Linux users on how to perform the same upgrade tasks.
Recommendations
  • Add equivalent examples using Azure CLI, Bash scripts, or Service Fabric REST API for Linux/macOS users.
  • Clearly indicate which steps or tools are Windows-only and provide alternatives for Linux/macOS.
  • Reference Linux-native concepts (e.g., Kestrel instead of http.sys) where appropriate.
  • Include links to Linux/macOS-specific documentation or tutorials for Service Fabric application upgrades.
  • Ensure that upgrade instructions and troubleshooting steps cover both Windows and Linux environments.
GitHub Create Pull Request
Service Fabric Understanding periodic backup configuration ...-fabric-backuprestoreservice-configure-periodic-backup.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation exhibits a moderate Windows bias, particularly in the backup storage section. File share examples exclusively use Windows UNC paths (\\StorageServer\BackupStore) and reference Integrated Windows Authentication, with no mention of Linux-compatible storage options (e.g., NFS, SMB mounting on Linux, or Linux authentication methods). The examples and instructions for file share access are Windows-centric and do not provide parity for Linux/macOS users. Additionally, Windows authentication patterns are described first and in detail, while Linux alternatives are absent.
Recommendations
  • Add examples for configuring backup storage using Linux-compatible file shares (e.g., NFS paths, SMB mounts on Linux).
  • Describe how to authenticate to file shares from Linux nodes, including relevant credential formats and mount commands.
  • Clarify whether Service Fabric on Linux supports file share backup, and if so, provide explicit instructions and examples.
  • Present Windows and Linux options side-by-side or indicate platform-specific differences clearly.
  • Reference Linux documentation or tools where applicable.
GitHub Create Pull Request
Service Fabric Restoring backup in Azure Service Fabric ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-backup-restore-service-trigger-restore.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily biased toward Windows and PowerShell usage. All command-line examples use PowerShell, including REST API calls, and require installation of Windows-specific modules. There are no Linux/macOS shell examples (e.g., Bash, curl), nor are cross-platform alternatives mentioned. Windows tools and patterns are referenced exclusively and first, creating friction for Linux/macOS users.
Recommendations
  • Provide equivalent Bash/curl examples for all REST API interactions.
  • Document how to install and use Service Fabric CLI (sfctl) or REST calls on Linux/macOS.
  • Clarify which steps are Windows-only and offer Linux/macOS alternatives where possible.
  • Mention cross-platform authentication and certificate handling approaches.
  • Add notes or sections for Linux/macOS users, including troubleshooting and environment setup.
GitHub Create Pull Request
Service Fabric Capacity planning and scaling for Azure Service Fabric ...bric/service-fabric-best-practices-capacity-scaling.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits a notable Windows bias, particularly in the scaling procedures. PowerShell commands (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState) are referenced exclusively for manual scaling operations, with no equivalent Linux CLI or bash examples. The step-by-step instructions for scaling in/out are written as if PowerShell is the only available tool, and no mention is made of Service Fabric CLI (sfctl) or REST API alternatives. Windows tools and patterns are assumed, and Windows-centric terminology appears before Linux equivalents. While there are links to Linux cluster creation, the operational guidance is Windows-focused.
Recommendations
  • Provide equivalent Linux examples using Service Fabric CLI (sfctl), bash scripts, or REST API calls for all PowerShell commands.
  • Explicitly mention cross-platform tools and workflows, and clarify which steps apply to both Windows and Linux clusters.
  • Reorder or parallelize instructions so that Linux and Windows approaches are presented side-by-side, rather than Windows-first.
  • Add notes or tables summarizing command equivalence between Windows (PowerShell) and Linux (sfctl/REST).
  • Ensure that all manual and programmatic scaling instructions are accessible to Linux users.
GitHub Create Pull Request
Service Fabric Azure Service Fabric networking best practices ...ice-fabric/service-fabric-best-practices-networking.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
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 terminology, tools, and examples (such as PowerShell and Windows-specific networking commands) are mentioned before or more prominently than Linux equivalents. Some sections, like API access and DevOps, reference PowerShell and Windows update processes without Linux parity or examples. ARM template and networking references often link to Windows samples first. Linux support is acknowledged but less detailed, and Linux-specific instructions or examples are missing in several areas.
Recommendations
  • Provide Linux CLI (az, bash) examples alongside or before PowerShell examples.
  • Include Linux-specific networking commands (e.g., how to view dynamic port ranges on Linux).
  • Add links to Linux ARM template samples and Linux-focused cluster setup guides where Windows ones are referenced.
  • Clarify when instructions or features differ for Linux clusters, and offer explicit guidance for Linux users.
  • Ensure DevOps and API access sections mention Linux-compatible tools and workflows.
  • Balance references to Windows and Linux containers and their networking modes.
GitHub Create Pull Request
Service Fabric Azure Service Fabric infrastructure as Code Best Practices ...tps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-best-practices-infrastructure-as-code.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
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 several forms of Windows bias. PowerShell examples are provided for critical operations (such as cluster upgrades) without equivalent Linux/bash commands. Windows-specific tools and registry settings are mentioned for update management, while Linux alternatives are omitted. Windows configuration examples (e.g., disabling Windows Update) are shown in detail, but there is no parity for Linux VM configuration. In some sections, Windows instructions or references appear before Linux ones.
Recommendations
  • Provide bash or Linux shell command equivalents for all PowerShell examples, especially for cluster upgrades.
  • Include Linux-specific configuration guidance for VM update management, such as disabling automatic updates or patch orchestration on Linux VMs.
  • Add Linux-focused examples for deploying and managing Service Fabric clusters, not just referencing them in 'Next steps'.
  • Ensure that references to Windows and Linux resources are presented with equal prominence and detail.
  • Mention Linux tools and patterns (e.g., apt/yum, systemd) where relevant alongside Windows registry and configuration settings.
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-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation mentions Service Fabric running on both Windows and Linux, but examples, tool references, and API mappings are either Windows-centric or ambiguous. The API comparison table references Windows-specific tools (e.g., Connect-WindowsFabricCluster) without Linux equivalents, and there is no explicit guidance or examples for Linux users. Windows is often mentioned first, and Linux support is stated but not demonstrated.
Recommendations
  • Add explicit Linux examples and workflows, especially for cluster management and API usage.
  • Include Linux-specific tools or commands (e.g., Service Fabric CLI, REST API usage) alongside Windows tools like Connect-WindowsFabricCluster.
  • When listing platforms, alternate or balance the order (e.g., 'Windows or Linux' vs. 'Linux or Windows') to avoid subtle prioritization.
  • Clarify any platform-specific differences in deployment, management, or troubleshooting.
  • Provide links to Linux/macOS documentation and migration guides.
GitHub Create Pull Request
Service Fabric Service Fabric cluster capacity planning considerations ...cles/service-fabric/service-fabric-cluster-capacity.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. References to Windows-specific tools and patterns (such as Patch Orchestration Application for Windows updates and standalone clusters hosted in Windows) are present, and instructions for standalone cluster configuration are only provided for Windows. Linux equivalents (e.g., patch orchestration, configuration file locations, upgrade procedures) are missing or not mentioned. Windows scenarios are described before or instead of Linux ones, and PowerShell is referenced for cluster upgrade monitoring without mentioning Linux CLI alternatives.
Recommendations
  • Add explicit instructions and examples for Linux-based Service Fabric clusters, including configuration, upgrade, and patch orchestration procedures.
  • Mention Linux equivalents for standalone cluster management, such as configuration file locations and update automation tools.
  • When referencing tools (e.g., Patch Orchestration Application), clarify their applicability to both Windows and Linux, or provide Linux alternatives.
  • Include cross-platform CLI commands (e.g., Azure CLI, Service Fabric CLI) alongside PowerShell examples.
  • Ensure that Linux/macOS scenarios are described with equal prominence and detail as Windows scenarios.
GitHub Create Pull Request
Service Fabric Create an Azure Service Fabric cluster template ...ric/service-fabric-cluster-creation-create-template.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
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 exclusively providing PowerShell examples for testing the Resource Manager template, referencing Windows-centric sample templates, and omitting equivalent Linux/macOS CLI instructions. The only mention of Linux is a brief note about Microsoft Entra tenant creation, without actionable guidance or examples for Linux users.
Recommendations
  • Add Azure CLI examples for testing and deploying Resource Manager templates, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include links to Linux-specific Service Fabric sample templates, if available, or clarify Windows-specific aspects in referenced templates.
  • Explicitly state any platform limitations or differences (e.g., certificate store handling) and provide Linux/macOS alternatives where possible.
  • Reorder examples so that cross-platform tools (Azure CLI, REST API) are shown before or alongside PowerShell.
  • Provide guidance for Linux/macOS users on prerequisite setup and troubleshooting.
GitHub Create Pull Request
Service Fabric Set up Microsoft Entra ID for client authentication in the Azure portal ...vice-fabric-cluster-creation-setup-azure-ad-via-portal.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page is heavily focused on Windows and PowerShell for client authentication and cluster connection examples. All code samples for connecting to Service Fabric clusters use PowerShell, with no equivalent Linux/macOS CLI or SDK examples provided. Troubleshooting and workflow guidance also reference PowerShell scripts and patterns, with no mention of Linux-native tools or cross-platform alternatives. While the prerequisites and portal steps are platform-neutral, the operational and connection instructions create friction for Linux/macOS users.
Recommendations
  • Add equivalent connection examples using Azure CLI, REST API, or Service Fabric SDK for Linux/macOS.
  • Explicitly document how Linux users can connect to clusters using Microsoft Entra ID, including required tools and authentication flows.
  • Include troubleshooting steps relevant to Linux environments, such as common errors with Linux Service Fabric nodes and authentication.
  • Clarify any platform-specific limitations (e.g., portal visibility issues for Linux clusters) and provide workarounds or alternatives.
  • Where scripts are referenced (e.g., SetupApplications.ps1), provide or link to cross-platform alternatives.
GitHub Create Pull Request
Service Fabric Set up Microsoft Entra ID for client authentication ...ce-fabric/service-fabric-cluster-creation-setup-aad.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on Windows and PowerShell tooling, with all setup and troubleshooting examples using PowerShell scripts (.ps1) and commands. There are no Linux-native or cross-platform CLI examples, and the only automation path provided is via PowerShell. The documentation references Windows-specific tools and patterns (e.g., PowerShell, Azure Cloud Shell with PowerShell, Windows script files) and does not mention or provide parity for Linux alternatives (such as Bash scripts, Azure CLI, or REST API usage). Linux users are left to run Windows-centric scripts in Cloud Shell or manually adapt them, creating friction and barriers.
Recommendations
  • Provide Linux-native setup instructions using Azure CLI, Bash scripts, or REST API calls for all major steps (app registration, user assignment, cluster configuration).
  • Include explicit Linux/macOS examples for authentication, troubleshooting, and cluster connection, not just PowerShell.
  • Document any limitations or workarounds for Linux users up front, and link to cross-platform helper tools if available.
  • Where PowerShell scripts are referenced, offer equivalent Bash/CLI/REST alternatives or note how to run them in a cross-platform way.
  • Reorder examples so that Linux and Windows instructions are presented with equal prominence, or in parallel sections.
GitHub Create Pull Request
Service Fabric Create an Azure Service Fabric cluster ...vice-fabric/service-fabric-cluster-creation-via-arm.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits several Windows-centric biases. PowerShell is consistently presented as the primary automation tool, with examples and instructions given before Azure CLI. Windows-specific patterns (e.g., file paths like 'c:\certificates', 'WindowsServer2016DatacenterwithContainers' as default OS) are used in both PowerShell and CLI examples, even when the CLI is cross-platform. While Ubuntu templates are mentioned, the majority of examples and variable names default to Windows conventions, and Linux/macOS-specific guidance (e.g., file paths, certificate handling) is missing. There is little to no discussion of Linux/macOS shell usage or platform-specific considerations, which may create friction for non-Windows users.
Recommendations
  • Provide Linux/macOS-specific examples, including shell commands (bash/zsh) and file paths (e.g., '/home/user/certificates').
  • Alternate the order of PowerShell and CLI examples, or present CLI first to emphasize cross-platform support.
  • Explicitly mention platform requirements and differences (e.g., certificate formats, file system paths, OS parameter values) for both Windows and Linux clusters.
  • Include troubleshooting or setup notes for Linux/macOS users (e.g., how to install Azure CLI, handle certificates, or run commands).
  • Use neutral variable names and examples that do not default to Windows conventions.
GitHub Create Pull Request
Service Fabric Node types and virtual machine scale sets ...les/service-fabric/service-fabric-cluster-nodetypes.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific tools and patterns (such as RDP port changes and admin credential updates) are referenced in the 'Next steps' section, with links to PowerShell scripts and RDP-related guidance, but there are no equivalent Linux/macOS instructions or SSH examples. The JSON extension snippet uses a Windows-style data path (D:\\SvcFab) and certificate store references, with no Linux path or store examples. Linux is mentioned as a possible node type, but practical guidance and examples are Windows-centric.
Recommendations
  • Add Linux/macOS-specific examples for remote connection (e.g., SSH instructions alongside RDP).
  • Provide guidance and scripts for updating SSH port ranges and admin credentials on Linux VMs.
  • Include Linux-style data paths (e.g., /var/svcfab) in extension configuration examples.
  • Clarify certificate store handling for Linux nodes.
  • Ensure that Linux instructions are presented alongside or before Windows instructions where relevant.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Programmatic Scaling ...-fabric/service-fabric-cluster-programmatic-scaling.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by providing PowerShell cmdlet examples for scaling operations, referencing Windows-centric tools and libraries (e.g., PowerShell, .NET SDKs), and omitting equivalent Linux/macOS command-line or scripting examples. PowerShell is mentioned as an alternative for scripting, but no Bash, Azure CLI, or cross-platform scripting examples are provided. The order of presentation also favors Windows tools first.
Recommendations
  • Add Linux/macOS examples for scaling operations using Azure CLI and Bash scripts.
  • Include cross-platform SDK usage, such as Python or Java, for programmatic scaling.
  • Present Azure CLI commands alongside or before PowerShell examples to emphasize platform neutrality.
  • Explicitly note that PowerShell cmdlets are available on Linux/macOS (via PowerShell Core), or clarify platform requirements.
  • Reference and link to documentation for Linux/macOS users where relevant.
GitHub Create Pull Request
Service Fabric Remote connect to an Azure Service Fabric cluster node ...ce-fabric-cluster-remote-connect-to-azure-cluster-node.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page shows a moderate Windows bias: Windows (RDP) examples and screenshots are presented first and in more detail, with Linux (SSH) mentioned briefly and only as a secondary note. The 'next steps' section links to PowerShell scripts for Windows VM management, with no Linux alternatives. Windows tools (Remote Desktop Connection) are visually emphasized, while Linux connection methods are described only in text.
Recommendations
  • Provide Linux SSH connection screenshots alongside Windows RDP examples.
  • Include step-by-step Linux/macOS instructions for connecting to cluster nodes, not just a single SSH command.
  • Add links to Linux-specific management scripts or CLI documentation in the 'next steps' section.
  • Present Windows and Linux instructions in parallel, rather than Windows-first.
  • Mention cross-platform tools (e.g., Azure CLI, SSH clients for Windows) where relevant.
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-14 01:31
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, with no mention of Linux shell equivalents or cross-platform CLI usage. PowerShell is Windows-specific, and its examples are presented before C#. There are no bash, Azure CLI, or REST API examples, which limits accessibility for Linux/macOS users.
Recommendations
  • Add equivalent bash or Azure CLI examples for service creation and updates, demonstrating how Linux/macOS users can configure move cost.
  • Explicitly mention cross-platform tools (e.g., Azure CLI, REST API) where available, and provide usage instructions.
  • Clarify which commands are Windows-only and offer alternatives for non-Windows environments.
  • Reorder examples so that cross-platform options are shown first or side-by-side with Windows-specific ones.
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-14 01:31
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 in Azure Service Fabric using PowerShell and C# APIs, both of which are primarily Windows-centric. There are no equivalent Linux shell or CLI examples, and PowerShell is featured prominently. The documentation also references Windows-specific activation models and resource monitoring features, with only brief mention of Linux support for containerized applications. Windows tools and patterns are presented first and exclusively, creating friction for Linux/macOS users.
Recommendations
  • Add equivalent Linux CLI (e.g., Bash, Azure CLI) examples for configuring scaling policies.
  • Clarify which features and APIs are supported on Linux and macOS, especially for non-containerized services.
  • Include instructions for using Service Fabric REST APIs or cross-platform tools where available.
  • Reorder examples to present cross-platform or Linux options alongside or before Windows/PowerShell examples.
  • Explicitly note any limitations or differences in feature support between Windows and Linux clusters.
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-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Configuration examples for clusters and nodes are shown using Windows-centric constructs (ClusterManifest.xml with <WindowsServer>), and PowerShell is the only command-line example provided for service creation and updates. There is no mention of Linux-specific configuration, tools, or command-line examples (such as Bash or CLI), nor is there any reference to Linux node setup or parity in standalone deployments. The documentation implicitly assumes a Windows environment for local/development clusters and omits Linux-specific guidance.
Recommendations
  • Include explicit Linux configuration examples for standalone clusters, such as using <Linux> infrastructure in ClusterManifest.xml.
  • Provide Bash or Azure CLI equivalents for all PowerShell commands shown.
  • Clarify how node properties, placement constraints, and capacities are configured for Linux nodes, including any differences in file formats or deployment steps.
  • Add notes or sections describing Linux/macOS development and deployment workflows, especially for local clusters.
  • Ensure that examples and code snippets are presented for both Windows and Linux environments, or at least indicate when an example is Windows-specific.
GitHub Create Pull Request
← Previous Page 12 of 29 Next →