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 526-550 of 718 flagged pages
Service Fabric Azure Service Fabric disaster recovery ...les/service-fabric/service-fabric-disaster-recovery.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. It references Windows-specific tools and APIs (e.g., PowerShell cmdlets like Repair-ServiceFabricPartition), links to cluster creation instructions for Windows Server, and omits explicit Linux or cross-platform command examples. Troubleshooting and recovery actions are described with Windows-centric terminology and tooling, and there is no mention of Linux equivalents or guidance for Linux-based Service Fabric clusters.
Recommendations
  • Provide Linux-specific examples and instructions for key recovery and troubleshooting steps, such as using Service Fabric CLI (sfctl) or REST APIs.
  • Include links to documentation for creating and managing Service Fabric clusters on Linux, not just Windows Server.
  • Mention cross-platform tools and patterns (e.g., sfctl, REST API) alongside or before Windows PowerShell equivalents.
  • Clarify which procedures and APIs are available and supported on Linux clusters, and note any differences.
  • Add troubleshooting guidance relevant to Linux environments (e.g., systemd, journalctl, Linux process management).
GitHub Create Pull Request
Service Fabric Start and stop cluster nodes .../service-fabric/service-fabric-node-transition-apis.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. PowerShell commands are referenced alongside managed API calls, but there is no mention of Linux CLI equivalents or cross-platform tooling. All code samples are in C# and reference .NET APIs, which are primarily used on Windows. There are no bash, Linux CLI, or cross-platform examples, and Windows/PowerShell tools are mentioned before any Linux alternatives (which are absent).
Recommendations
  • Add equivalent Linux CLI or bash examples for node management tasks, such as using Azure CLI, REST API, or Service Fabric CLI (sfctl) where applicable.
  • Explicitly mention cross-platform tools and how Linux/macOS users can perform the same operations.
  • Include sample commands and scripts for Linux environments, and clarify any platform-specific limitations or requirements.
  • Reorder references so that cross-platform or platform-neutral APIs are mentioned before platform-specific tools like PowerShell.
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-12 00:00
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 instructions and caveats are presented before Linux equivalents, and certain features (such as mixing networking modes) are only supported on Windows. Windows-only configuration steps (e.g., NSG for UDP/53, network reset on reboot) are described in detail, while Linux-specific guidance is minimal or absent. There are no Linux-specific configuration examples, and limitations for Linux clusters are mentioned only as notes.
Recommendations
  • Add explicit Linux configuration examples, including ARM template snippets and service manifests tailored for Linux clusters.
  • Clarify which steps apply to both Windows and Linux, and which are Windows-only, using clear sectioning or callouts.
  • Provide Linux-specific troubleshooting tips and caveats, similar to the Windows notes.
  • Present Linux and Windows instructions in parallel where possible, rather than focusing on Windows first.
  • Expand on Linux networking mode limitations and offer guidance or alternatives 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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows-specific tools (PowerShell, Visual Studio) are referenced first and exclusively in key sections (e.g., viewing the cluster manifest, configuring via Visual Studio templates). Configuration file examples use Windows-style paths (e.g., 'f:\SharedLog.Log') without Linux equivalents. There is only a brief mention of Linux in the context of certificate formats, with no Linux/macOS-specific configuration or tooling examples provided.
Recommendations
  • Provide equivalent Linux/macOS commands for viewing and editing the cluster manifest (e.g., using CLI tools or text editors).
  • Include Linux-style path examples (e.g., '/var/sharedlog/SharedLog.Log') alongside Windows paths.
  • Add instructions for configuring Reliable Services using cross-platform tools (e.g., Azure CLI, VS Code) rather than only Visual Studio.
  • Clarify any platform-specific differences in configuration file locations or formats.
  • Ensure that all code and configuration samples are platform-neutral or provide both Windows and Linux/macOS variants.
GitHub Create Pull Request
Service Fabric Migrate from Azure Cloud Services to Service Fabric ...ic/cloud-services-to-service-fabric-migration-guide.md
Medium Priority View Details →
Scanned: 2026-01-12 00: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 exhibits a notable Windows bias. PowerShell is the only command-line example provided for cluster setup and application deployment, with no Azure CLI or Bash equivalents. Visual Studio (Windows-only) is the sole development environment mentioned for creating Service Fabric applications, and the 'Prepare your development environment' link points to Windows-specific instructions. Linux/macOS tooling and workflows are not discussed, and Windows-centric migration scenarios (IIS, Windows Containers) are detailed, while Linux alternatives are omitted.
Recommendations
  • Add Azure CLI and Bash examples for cluster creation, application packaging, and deployment alongside PowerShell.
  • Include instructions for developing Service Fabric applications using cross-platform tools such as VS Code, .NET CLI, and Docker.
  • Provide explicit guidance for Linux/macOS users, including environment setup, certificate management, and troubleshooting.
  • Mention Linux container support and migration strategies for non-Windows workloads.
  • Ensure that examples and tool recommendations are presented in a platform-neutral order, or grouped by OS.
GitHub Create Pull Request
Service Fabric Manage certificates in a Service Fabric cluster ...vice-fabric/cluster-security-certificate-management.md
Medium Priority View Details →
Scanned: 2026-01-12 00: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 demonstrates a notable Windows bias. PowerShell is used exclusively for scripting examples, and Windows-specific tools and patterns (such as the Key Vault VM extension for Windows and S-channel APIs) are referenced without Linux equivalents. The Key Vault VM extension documentation and examples are Windows-centric, and there are no Linux or cross-platform alternatives provided for certificate provisioning, management, or automation. Troubleshooting and FAQ sections also use PowerShell, with no mention of Bash, Azure CLI, or Linux-native approaches.
Recommendations
  • Provide equivalent examples using Azure CLI and Bash scripts for certificate enrollment and management.
  • Reference and document the Key Vault VM extension for Linux, if available, or clarify Linux support and alternatives.
  • Include cross-platform guidance for certificate provisioning, especially for clusters running on Linux VMs.
  • Mention Linux-specific certificate stores and access control mechanisms where relevant.
  • Ensure that all automation and scripting examples have both Windows (PowerShell) and Linux (Bash/Azure CLI) versions.
  • Clarify any Windows-only features (such as S-channel linking) and provide Linux alternatives or workarounds.
GitHub Create Pull Request
Service Fabric X.509 Certificate-based Authentication in a Service Fabric Cluster ...ticles/service-fabric/cluster-security-certificates.md
Medium Priority View Details →
Scanned: 2026-01-12 00: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 demonstrates a moderate Windows bias. Windows terminology, tools, and APIs (e.g., Win32 CryptoAPI, Windows certificate store paths, Windows event logs, CAPI1/CNG provider types) are referenced first and in detail, with Linux equivalents mentioned only briefly or not at all. Troubleshooting and configuration examples focus on Windows-specific paths and error codes, and there is a lack of explicit Linux/macOS troubleshooting guidance or examples.
Recommendations
  • Provide explicit Linux/macOS equivalents for all Windows-specific instructions, such as certificate store paths, error codes, and troubleshooting steps.
  • Include Linux/macOS event log locations and diagnostic procedures alongside Windows event log guidance.
  • Reference Linux certificate management tools (e.g., OpenSSL, certtool) and Service Fabric's Linux certificate handling mechanisms.
  • Clarify how configuration settings map to Linux environments, especially for certificate storage and retrieval.
  • Add Linux/macOS-specific error codes and troubleshooting scenarios.
  • Ensure examples and explanations are presented in a platform-neutral order, or alternate which platform is shown first.
GitHub Create Pull Request
Service Fabric Azure Service Fabric container image management .../articles/service-fabric/container-image-management.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates bias towards Windows by referencing Windows-specific container images (microsoft/windowsservercore, microsoft/nanoserver) as default exclusions in cleanup settings, and mentioning them before Linux equivalents. There are no explicit Linux container image examples or discussion of Linux-specific considerations, which may leave Linux/macOS users unclear about best practices or defaults for their platforms.
Recommendations
  • Include examples of Linux container images (e.g., ubuntu, alpine, centos) in the 'ContainerImagesToSkip' setting and documentation.
  • Clarify whether the default exclusions apply to Linux images, and if not, provide guidance for Linux users.
  • Add a section discussing platform-specific behaviors or considerations for both Windows and Linux container images.
  • Ensure parity in examples and explanations for both Windows and Linux container scenarios.
GitHub Create Pull Request
Service Fabric Create an Azure Load Balancer rule for a cluster ...n/articles/service-fabric/create-load-balancer-rule.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for creating a load balancer rule, but PowerShell (a Windows-centric tool) is given a dedicated section with a detailed, step-by-step example. The CLI example is presented first, but the PowerShell section is more elaborate. No Linux-specific tools or shell examples (e.g., Bash) are provided, and there is no mention of Linux/macOS-specific considerations or parity in the PowerShell section.
Recommendations
  • Add explicit Bash shell examples for Azure CLI usage on Linux/macOS, including environment setup and command execution.
  • Clarify that Azure CLI works cross-platform and is recommended for Linux/macOS users.
  • Mention that PowerShell Core is available on Linux/macOS, or provide a brief note about its cross-platform support.
  • Ensure that any advanced configuration steps shown in PowerShell are also covered for Azure CLI users.
  • Consider adding a table or section comparing CLI and PowerShell approaches, highlighting platform compatibility.
GitHub Create Pull Request
Service Fabric Deploy an application to a managed cluster using Azure Resource Manager ...bric/how-to-managed-cluster-app-deployment-template.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. All command-line deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzServiceFabricManagedClusterApplication), with no Azure CLI, Bash, or cross-platform alternatives provided. The application packaging workflow is described using Visual Studio, a Windows-centric IDE, with no mention of Linux/macOS equivalents or command-line packaging. Windows tools and patterns are referenced exclusively and presented first, leaving Linux/macOS users without direct guidance for completing key steps.
Recommendations
  • Add Azure CLI examples for deployment and deletion alongside PowerShell commands.
  • Provide instructions for packaging the application using cross-platform tools (e.g., dotnet CLI, zip utilities) instead of or in addition to Visual Studio.
  • Include screenshots or descriptions for Linux/macOS workflows where relevant (e.g., uploading to Azure Storage via CLI or portal).
  • Explicitly state platform requirements and offer parity guidance for non-Windows users.
  • Reorder or balance examples so that Windows and Linux/macOS approaches are presented equally.
GitHub Create Pull Request
Service Fabric Configure managed identity support in an existing Service Fabric cluster ...existing-cluster-enable-managed-identity-token-service.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation references Service Fabric Explorer and the Azure portal for cluster management and troubleshooting, both of which are primarily Windows-centric tools. It also mentions PowerShell as a method for viewing upgrade policies, without providing equivalent Linux/macOS CLI (e.g., Azure CLI or REST API) instructions or examples. No Linux-specific tools, commands, or examples are provided, and the documentation implicitly assumes the user is operating in a Windows environment.
Recommendations
  • Add Azure CLI examples for viewing and managing cluster upgrade policies, as Azure CLI is cross-platform.
  • Mention REST API alternatives for cluster management tasks, which are OS-agnostic.
  • Include instructions or references for accessing Service Fabric Explorer from non-Windows environments (e.g., via browser).
  • Clarify which steps are platform-independent and which require Windows-specific tools, and provide Linux/macOS alternatives where possible.
GitHub Create Pull Request
Service Fabric Deploy a Service Fabric managed cluster across Availability Zones ...ce-fabric/how-to-managed-cluster-availability-zones.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides command-line examples exclusively using PowerShell (Az Module), and references PowerShell commands for cluster node management. There are no CLI/bash examples for Linux/macOS users, nor are cross-platform alternatives mentioned. This creates friction for non-Windows users, who must translate or research equivalent commands.
Recommendations
  • Add Azure CLI (az) command examples for all PowerShell commands, especially for resource actions and cluster node management.
  • Explicitly mention that Azure CLI is cross-platform and provide usage instructions for Linux/macOS.
  • Where PowerShell is referenced, offer equivalent bash/CLI syntax side-by-side.
  • Clarify which tools are available on which platforms, and link to installation guides for Azure CLI on Linux/macOS.
GitHub Create Pull Request
Service Fabric Set up IP tags on a Service Fabric managed cluster ...icles/service-fabric/how-to-managed-cluster-ip-tags.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation references provisioning IPTags using a PowerShell module (Az.Network), which is a Windows-centric tool, and does not provide equivalent instructions or examples for Linux/macOS users (e.g., Azure CLI or REST API). This creates friction for non-Windows users who may not use PowerShell.
Recommendations
  • Add instructions and examples for provisioning IPTags using Azure CLI, which is cross-platform.
  • Include REST API example for IPTags provisioning for users who prefer direct API calls.
  • Clarify that PowerShell is one option and link to Linux/macOS alternatives.
  • Ensure all prerequisite steps are covered for both Windows and Linux/macOS environments.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation 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 guidance assumes use of PowerShell and Windows tools. This creates friction for users on Linux or macOS, who must translate or adapt the instructions themselves.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell commands, as Azure CLI is cross-platform and works on Linux/macOS.
  • Include Bash script snippets for resource group and cluster deployment steps.
  • Explicitly mention cross-platform alternatives and provide links to relevant Azure CLI documentation.
  • Reorder examples so that cross-platform (CLI) instructions appear before or alongside PowerShell commands.
GitHub Create Pull Request
Service Fabric Use Application Gateway in a Service Fabric managed cluster ...e-fabric/how-to-managed-cluster-application-gateway.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides step-by-step instructions for configuring Azure Application Gateway with Service Fabric managed clusters, but all command-line examples use PowerShell (specifically Azure PowerShell cmdlets), which are native to Windows. There are no Bash, Azure CLI, or Linux/macOS shell equivalents provided, and PowerShell is referenced before any other tooling. This creates friction for Linux/macOS users who may not have PowerShell installed or prefer Azure CLI.
Recommendations
  • Add equivalent Azure CLI (az) commands for all PowerShell examples, especially for authentication, service principal lookup, and role assignment.
  • Include notes or links on how to install and use Azure PowerShell on Linux/macOS, or recommend Azure CLI as a cross-platform alternative.
  • Present both PowerShell and CLI examples side-by-side, or default to Azure CLI for broader platform compatibility.
  • Explicitly mention that ARM templates are platform-agnostic and can be deployed via Azure CLI, PowerShell, or the portal.
GitHub Create Pull Request
Service Fabric Deploy application secrets to a Service Fabric managed cluster ...e-fabric/how-to-managed-cluster-application-secrets.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
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-specific tools and patterns, such as the 'KeyVault extension' (linked to a Windows-only page), and by mentioning certificate store names like 'MY' (which are Windows conventions) without providing Linux equivalents or guidance. There are no Linux/macOS-specific instructions, examples, or references to Linux certificate stores or VM extensions. The examples and links focus on Windows tooling and do not address how Linux users should perform equivalent tasks.
Recommendations
  • Add explicit instructions and examples for Linux clusters, including how to install certificates and manage secrets using Linux-compatible VM extensions (e.g., Key Vault extension for Linux).
  • Reference Linux certificate stores (such as /etc/ssl/certs or other relevant paths) and provide guidance on how to specify them.
  • Ensure that all linked documentation (such as VM extension guides) includes both Windows and Linux options, or link to Linux-specific documentation where appropriate.
  • Include sample ARM templates or CLI commands for Linux clusters, and clarify any differences in process or parameters.
  • Present examples for both platforms side-by-side, or clearly indicate platform-specific steps.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits 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 Windows or PowerShell Core on other platforms. There are no CLI examples using cross-platform tools like Azure CLI (az), nor are there bash or Linux/macOS-specific instructions. Windows terminology and tools are referenced first and exclusively throughout the step-by-step sections, with no mention of Linux alternatives or parity.
Recommendations
  • Add equivalent Azure CLI (az) command examples for all PowerShell cmdlets, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that PowerShell Core can be used on Linux/macOS, or provide installation guidance for non-Windows users.
  • Include bash script examples or instructions for Linux/macOS users where appropriate.
  • Reorder or parallelize examples so that Windows and Linux/macOS instructions are presented together, or clarify platform applicability at the start of each section.
  • Reference Linux-specific considerations (e.g., VM images, metric availability) where relevant.
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
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by exclusively providing PowerShell examples for all command-line operations, such as authentication, resource group creation, deployment, and role assignment. There are no CLI (az), Bash, or Linux/macOS-specific instructions or examples. Windows tools and patterns (e.g., RDP, PowerShell) are mentioned first and exclusively, which may create friction for Linux/macOS users who typically use Bash or Azure CLI.
Recommendations
  • Add equivalent Azure CLI (az) command examples for all PowerShell steps, including authentication, resource group creation, deployment, and role assignment.
  • Include Bash script snippets or instructions for Linux/macOS users.
  • Clarify that all steps can be performed from any OS using Azure CLI, not just PowerShell.
  • Mention SSH as an alternative to RDP for VM access where appropriate.
  • Consider reordering examples so that cross-platform tools (Azure CLI) are shown first or side-by-side with PowerShell.
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
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides explicit instructions and code samples for deploying the ARM template using PowerShell cmdlets, which are primarily Windows-centric. There are no examples or guidance for deploying via Azure CLI, Bash, or other Linux/macOS-friendly tools. The admin credentials are described in terms of RDP (a Windows protocol), and the PowerShell method is listed before any mention of cross-platform alternatives. No Linux/macOS-specific instructions or parity examples are provided.
Recommendations
  • Add equivalent deployment instructions and code samples using Azure CLI (az deployment group create), which works on Linux, macOS, and Windows.
  • Include Bash script examples for template deployment.
  • Mention SSH as an alternative to RDP for admin access, and clarify how Linux/macOS users can connect to VMs.
  • Explicitly state that the ARM portal and Azure CLI methods are cross-platform.
  • Reorder examples so that cross-platform methods (Azure CLI, portal) are listed before Windows/PowerShell-specific instructions.
GitHub Create Pull Request
Service Fabric Configure or modify a Service Fabric managed cluster node type ...vice-fabric/how-to-managed-cluster-modify-node-type.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation consistently provides PowerShell examples for command-line operations (add, remove, scale, configure placement properties), but does not mention or provide equivalent examples for Linux/macOS users (e.g., Azure CLI, Bash). PowerShell is a Windows-centric tool, and its use is assumed throughout, creating friction for users on other platforms. Additionally, PowerShell instructions are given before any mention of cross-platform alternatives, and no Linux/macOS-specific tooling or guidance is offered.
Recommendations
  • Add Azure CLI examples for all command-line operations (add, remove, scale, configure placement properties, etc.), as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly state that PowerShell examples are for Windows, and provide Bash/Azure CLI equivalents for Linux/macOS users.
  • Where possible, mention cross-platform tools first or alongside PowerShell, to avoid implying Windows is the default or only supported platform.
  • Include notes or links to installation guides for Azure CLI on Linux/macOS.
  • Review all sections for other Windows-specific assumptions (e.g., drive letter conventions) and clarify their applicability to Linux-based clusters.
GitHub Create Pull Request
Service Fabric Configure network settings for Service Fabric managed clusters ...es/service-fabric/how-to-managed-cluster-networking.md
Medium Priority View Details →
Scanned: 2026-01-12 00: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 exhibits several Windows biases. Most command-line examples use PowerShell cmdlets (New-AzResourceGroup, New-AzResourceGroupDeployment, Login-AzAccount, etc.) with no mention of Linux/macOS equivalents (e.g., Azure CLI, Bash). Remote Desktop (RDP) instructions and screenshots are Windows-centric, with no guidance for SSH access to Linux nodes. The public IP verification step uses a PowerShell command, and there are no alternative instructions for Linux users. Throughout, Windows tools and patterns are referenced exclusively or before any cross-platform alternatives.
Recommendations
  • Provide Azure CLI and Bash examples alongside PowerShell for all command-line steps, especially resource group creation, deployment, and querying resources.
  • Include SSH instructions and screenshots for connecting to Linux nodes, not just RDP for Windows.
  • Clarify which steps are OS-agnostic and which require Windows-specific tools, and offer alternatives where possible.
  • Explicitly mention Linux/macOS support for Service Fabric managed clusters and link to relevant documentation.
  • For public IP verification, show equivalent Azure CLI commands usable on Linux/macOS.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exhibits a Windows bias by only listing Windows cluster versions in the REST API example output and omitting any mention or example of Linux cluster versions. There are no Linux-specific instructions, examples, or references to Linux Service Fabric managed clusters, despite Service Fabric supporting both Windows and Linux environments.
Recommendations
  • Include REST API example output that shows both Windows and Linux cluster versions, or alternate between them.
  • Explicitly mention that Service Fabric managed clusters can run on Linux, and provide guidance or links for Linux-specific upgrade scenarios.
  • Add examples of Resource Manager templates and upgrade settings for Linux clusters, including relevant OS type values.
  • Reference documentation or sections that address Linux operating system support and differences in upgrade procedures, if any.
GitHub Create Pull Request
Service Fabric Add a virtual machine scale set extension to a Service Fabric managed cluster node type ...ervice-fabric/how-to-managed-cluster-vmss-extension.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits a notable Windows bias. The only CLI example provided is for PowerShell (Add-AzServiceFabricManagedNodeTypeVMExtension), with no mention of Azure CLI, Bash, or Linux/macOS alternatives. The main extension example uses 'KeyVaultForWindows' as the type, and there is no discussion of Linux-specific VM extensions or cross-platform considerations. Windows tools and patterns are referenced exclusively and appear first, with no parity for Linux users.
Recommendations
  • Add equivalent Azure CLI and/or Bash examples for adding VM extensions to Service Fabric managed cluster node types.
  • Include documentation and examples for Linux-specific VM extensions (e.g., KeyVaultForLinux) and clarify when to use each.
  • Provide guidance for macOS users, especially for scripting and automation tasks.
  • Reorder examples or add parallel examples so that Windows and Linux approaches are presented equally.
  • Explicitly mention cross-platform support and limitations for Service Fabric managed cluster extensions.
GitHub Create Pull Request
Service Fabric Deny assignment policy for Service Fabric managed clusters ...cles/service-fabric/managed-cluster-deny-assignment.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page shows a moderate Windows bias. PowerShell is referenced repeatedly as a primary tool for managing Service Fabric clusters, with direct links to PowerShell cmdlets and examples. While Azure CLI and sfctl (cross-platform tools) are mentioned in the utility table, the best practices section exclusively highlights PowerShell for key operations (delete, restart, reimage), and does not provide equivalent Azure CLI or sfctl command examples. This may create friction for Linux/macOS users who do not use PowerShell.
Recommendations
  • Add equivalent Azure CLI and sfctl command examples for all PowerShell cmdlets referenced, especially in the best practices section.
  • Explicitly mention that Azure CLI and sfctl are cross-platform and suitable for Linux/macOS users.
  • Reorder examples so that cross-platform tools (Azure CLI, sfctl) are shown before or alongside PowerShell.
  • Clarify which tools are recommended for Linux/macOS users in the best practices section.
GitHub Create Pull Request
Service Fabric Monitor Azure Service Fabric ...main/articles/service-fabric/monitor-service-fabric.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page generally covers both Windows and Linux clusters, but there are several instances of Windows bias. Windows-specific tools and patterns (Event Log, ETW, Diagnostics Agent) are mentioned first or exclusively, with Linux equivalents referenced less prominently or as afterthoughts. Some tutorials and examples focus on .NET/Windows, and Linux configuration steps are often deferred to linked pages rather than explained inline. The EventStore API is noted as Windows-only, and some monitoring setup recommendations are Windows-centric.
Recommendations
  • Provide Linux-specific examples and configuration steps inline, not just as links.
  • Ensure that Linux tools (e.g., LTTng, Syslog) are described with equal detail and prominence as Windows tools (e.g., ETW, Event Log).
  • Add tutorials and sample code for Linux clusters, including non-.NET applications.
  • Clearly indicate feature parity or limitations for Linux vs. Windows (e.g., EventStore API availability).
  • When listing monitoring tools or agents, present Windows and Linux options side-by-side.
  • Avoid using Windows-centric language or examples as the default; alternate or balance ordering.
GitHub Create Pull Request
← Previous Page 22 of 29 Next →