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 76-100 of 718 flagged pages
Service Fabric Set up a Windows development environment .../articles/service-fabric/service-fabric-get-started.md
High 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 is heavily focused on Windows, with all examples and instructions tailored exclusively to Windows environments. PowerShell commands are used throughout, and Windows-specific tools (Visual Studio, Docker for Windows) are referenced without Linux/macOS alternatives or parity. Linux and Mac are only mentioned in navigation, with no actual instructions or examples provided for those platforms.
Recommendations
  • Add equivalent installation and setup instructions for Linux and macOS, including shell commands and package managers (e.g., apt, yum, Homebrew).
  • Provide examples using Bash or other common Linux/macOS shells alongside PowerShell.
  • Reference Linux/macOS-compatible tools (e.g., VS Code, Docker for Linux/macOS) and provide guidance for their setup.
  • Clearly indicate platform-specific steps and link to corresponding Linux/macOS documentation sections where appropriate.
  • Avoid assuming Visual Studio or PowerShell as the default; mention cross-platform alternatives.
Service Fabric Create an Azure Service Fabric container application ...ervice-fabric/service-fabric-get-started-containers.md
High 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 is heavily biased toward Windows environments. All examples, prerequisites, and instructions are specific to Windows, including the use of Windows containers, Windows Server, Visual Studio, PowerShell, and Windows-specific Docker images. There is no guidance for Linux/macOS users, and the article explicitly states it applies only to Windows development environments. Linux equivalents, tools, and workflows are missing, and the documentation does not provide parity for non-Windows users.
Recommendations
  • Add equivalent Linux/macOS instructions and examples, including Dockerfile and deployment steps for Linux containers.
  • Provide guidance for using cross-platform tools (e.g., VS Code, CLI) instead of only Visual Studio.
  • Include Linux-specific prerequisites, such as Docker for Linux, Service Fabric SDK for Linux, and relevant OS compatibility notes.
  • Offer PowerShell alternatives using Bash or other Linux-native tools.
  • Clearly link to the Linux version of the guide at the top and throughout, ensuring users can easily find Linux-specific documentation.
Service Fabric Create and Publish a .NET Core app to a remote Linux Cluster ...e-fabric/service-fabric-how-to-publish-linux-app-vs.md
High 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 is heavily focused on Visual Studio, a Windows-centric tool, and all instructions assume usage of Windows (e.g., launching Visual Studio as administrator, .exe file references). There are no examples or guidance for Linux-native development workflows (such as using VS Code, CLI, or Linux-based build/publish steps). Linux users are expected to use Windows tooling to target Linux clusters, with no parity for Linux/macOS development environments.
Recommendations
  • Add instructions for creating and publishing .NET Core Service Fabric apps using cross-platform tools like VS Code or the .NET CLI.
  • Provide Linux/macOS-specific examples for project creation, build, and publish steps.
  • Clarify which steps are Windows-only and offer alternatives for Linux/macOS users.
  • Include screenshots and walkthroughs for Linux-native development environments.
  • Mention and link to Service Fabric CLI or PowerShell alternatives for Linux users.
Service Fabric Deploy a .NET app in a container to Azure Service Fabric ...rvice-fabric/service-fabric-host-app-in-a-container.md
High 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 is heavily biased towards Windows environments. All command-line examples are provided in PowerShell, with no Bash or Linux equivalents. The workflow is built around Visual Studio (Windows-only), Docker Desktop for Windows, and Service Fabric clusters running Windows containers. There is no mention of Linux/macOS alternatives, nor guidance for users on those platforms. Critical steps (containerization, debugging, deployment) rely on Windows-specific tools and patterns.
Recommendations
  • Provide equivalent Bash/Azure CLI scripts for all PowerShell commands, especially for Azure resource creation and management.
  • Include instructions for containerizing and deploying .NET Core/ASP.NET Core applications in Linux containers, using cross-platform tools like VS Code, Docker CLI, and Azure CLI.
  • Clarify early in the prerequisites and introduction that the tutorial is Windows-specific, and link to Linux/macOS alternatives if available.
  • Add guidance for users on Linux/macOS for local development, debugging, and deployment, or explicitly state limitations.
  • Mention and provide examples for using Service Fabric clusters with Linux nodes and containers, if supported.
Service Fabric Quickly create a .NET app on Service Fabric in Azure ...les/service-fabric/service-fabric-quickstart-dotnet.md
High 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 is heavily biased towards Windows, with all setup, cluster creation, and debugging instructions assuming the use of Windows tools (Visual Studio, PowerShell, Windows-specific SDK paths). There are no instructions or examples for Linux or macOS users, and critical steps (such as cluster creation and debugging) rely on Windows-only tools and scripts.
Recommendations
  • Add equivalent instructions for Linux/macOS users, including how to install the Service Fabric SDK and create a local cluster using CLI tools.
  • Provide examples using cross-platform editors (e.g., VS Code) and .NET CLI commands for building and debugging.
  • Document how to deploy and debug Service Fabric applications on Linux clusters, including any differences in configuration or tooling.
  • List Linux prerequisites and provide parity in step-by-step guides for non-Windows platforms.
  • Clearly indicate platform-specific limitations and link to Linux/macOS documentation where available.
Service Fabric Use Patch Orchestration Application ...bric/service-fabric-patch-orchestration-application.md
High Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation for Patch Orchestration Application (POA) is heavily focused on Windows environments. All examples, configuration parameters, and operational details are specific to Windows Update and Windows NT services. Deployment, upgrade, and removal instructions exclusively use PowerShell scripts and cmdlets. There is no guidance or parity for Linux clusters, except for a brief FAQ link redirecting Linux users elsewhere. The documentation does not mention Linux equivalents for patch orchestration, nor does it provide any examples or instructions for Linux Service Fabric clusters.
Recommendations
  • Add a dedicated section for Linux clusters, including supported patch orchestration methods and integration with Service Fabric Repair Manager.
  • Provide Linux-specific deployment, upgrade, and removal instructions, including sample scripts (e.g., Bash, systemd, apt/yum integration).
  • Include examples of configuring patch orchestration for Linux nodes, such as using package managers or OS-native update tools.
  • Clarify POA's applicability and limitations for Linux clusters early in the documentation.
  • Where possible, present examples for both Windows and Linux side-by-side, or clearly indicate when content is Windows-only.
Service Fabric Create a Windows container application on Service Fabric in Azure ...service-fabric/service-fabric-quickstart-containers.md
High 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 is heavily focused on Windows, with all examples, tools, and instructions tailored to Windows environments. Visual Studio and PowerShell are required, and only Windows container images are discussed. Linux equivalents are mentioned only as a link to a separate quickstart, with no Linux instructions or parity in the main content.
Recommendations
  • Provide Linux/macOS equivalents for each major step, including cluster creation, certificate management, and deployment.
  • Include CLI or Bash examples alongside PowerShell scripts.
  • Reference cross-platform tools (e.g., Azure CLI, Docker CLI) where possible.
  • Show Linux container image packaging and deployment steps, or link to them more prominently.
  • Clarify which steps are Windows-specific and offer alternatives for non-Windows users.
Service Fabric Create an actor-based service on Azure Service Fabric ...e-fabric/service-fabric-reliable-actors-get-started.md
High 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 is heavily oriented toward Windows development, specifically using Visual Studio and PowerShell. All examples and instructions assume a Windows environment, with no guidance for Linux/macOS users on how to create, build, or debug actor-based services in C#. Linux equivalents (such as using VS Code, CLI tools, or Bash) are not mentioned, and the only NuGet installation example uses PowerShell. The page does not provide parity for Linux/macOS users wishing to follow the C# workflow.
Recommendations
  • Add instructions for creating and managing Service Fabric actor projects using cross-platform tools like .NET CLI and VS Code.
  • Include Linux/macOS-specific steps for installing dependencies (e.g., using 'dotnet add package' instead of PowerShell).
  • Provide alternative debugging and deployment instructions for non-Windows environments.
  • Explicitly state platform requirements and link to Linux/macOS documentation where available.
  • Present examples for both Windows and Linux/macOS side-by-side, or clearly indicate which steps are platform-specific.
Service Fabric Create your first Service Fabric application in C# ...fabric/service-fabric-reliable-services-quick-start.md
High Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily focused on Windows development, specifically using Visual Studio and PowerShell scripts. All examples and instructions are for C# on Windows, with no Linux/macOS equivalents shown. The use of Windows-specific tools (Visual Studio, ETW, Diagnostic Events window) and deployment scripts (PowerShell) further reinforces the bias. There is a mention of a Java on Linux guide, but this page provides no Linux/macOS instructions or parity for C# developers.
Recommendations
  • Provide equivalent instructions and examples for developing Service Fabric applications in C# on Linux/macOS, including supported IDEs (e.g., VS Code, JetBrains Rider) and command-line workflows.
  • Include Linux/macOS deployment steps, using bash scripts or Service Fabric CLI instead of PowerShell.
  • Mention and demonstrate cross-platform diagnostic and debugging tools, such as sfctl, Service Fabric Explorer, or container logs.
  • Avoid assuming Visual Studio is the only development environment; offer alternatives and clarify platform requirements.
  • Ensure that all critical steps (project creation, deployment, debugging) have Linux/macOS equivalents or clear guidance.
Service Fabric Run a script when an Azure Service Fabric service starts ...fabric/service-fabric-run-script-at-service-startup.md
High 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 is heavily biased towards Windows environments. All example scripts use Windows batch files (.bat), and PowerShell is the only scripting language demonstrated. Visual Studio is referenced for project setup, and all file paths and debugging instructions use Windows conventions. Linux is mentioned only briefly in a note about AccountType, with no concrete Linux shell script or deployment examples provided.
Recommendations
  • Add equivalent Linux examples using shell scripts (e.g., MySetup.sh) and demonstrate how to set environment variables and output files in bash.
  • Provide instructions for including startup scripts in non-Visual Studio workflows, such as using CLI tools or editing files directly.
  • Show Linux file paths and locations for output and log files, not just Windows paths.
  • Include PowerShell alternatives for Linux (e.g., bash, sh) and demonstrate how to run those scripts from the SetupEntryPoint.
  • Clarify any differences in user/account configuration for Linux clusters, with concrete manifest examples.
Service Fabric Scale up an Azure Service Fabric primary node type ...ce-fabric/service-fabric-scale-up-primary-node-type.md
High 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 strong Windows bias. All step-by-step examples use Windows-centric tools (PowerShell, Windows file paths, Windows certificate stores) and reference Windows Server OS upgrades. Linux is mentioned only briefly, with minimal guidance and no concrete Linux shell commands or examples. There are no bash/CLI equivalents for certificate management, cluster connection, or resource deployment, and the workflow assumes a Windows environment throughout.
Recommendations
  • Provide parallel Linux/macOS examples for all PowerShell commands, using Azure CLI and bash scripting.
  • Include instructions for certificate generation and management on Linux (e.g., using openssl, Azure CLI, and Linux file paths).
  • Show how to connect to Service Fabric clusters from Linux/macOS, including certificate import and cluster health checks.
  • Explicitly document differences in OS image parameters for Linux clusters, with concrete ARM template snippets and deployment commands.
  • Reorder or balance examples so Linux and Windows are presented with equal prominence.
  • Clarify which steps are OS-agnostic and which require platform-specific handling.
Service Fabric Azure Service Fabric reverse proxy ...articles/service-fabric/service-fabric-reverseproxy.md
High 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 a strong Windows bias. The reverse proxy feature is explicitly stated as unavailable for Linux clusters, making the entire functionality Windows-only. All examples, configuration instructions, and referenced tools (such as http.sys-based servers and Windows-specific environment variables) are tailored to Windows environments. There are no Linux equivalents or workarounds provided, and Linux users are unable to utilize the reverse proxy feature or follow the documented steps.
Recommendations
  • Clearly indicate the lack of Linux support at the top of the documentation and in the prerequisites.
  • Provide alternative guidance or recommended approaches for Linux clusters, such as using other proxy solutions or service discovery mechanisms.
  • If possible, prioritize development of Linux support for the reverse proxy feature and update documentation accordingly.
  • Include links to Linux-specific documentation for related networking and service communication patterns in Service Fabric.
  • Offer sample code and configuration for Linux environments where feasible, or explicitly state when features are Windows-only.
Service Fabric Run an Azure Service Fabric service under a gMSA account ...s/service-fabric/service-fabric-run-service-as-gmsa.md
High 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 is heavily biased toward Windows environments, focusing exclusively on Windows Server standalone clusters and gMSA accounts, which are a Windows/Active Directory-specific feature. All examples use PowerShell cmdlets and Windows tools, with no mention of Linux or cross-platform alternatives. There are no instructions or guidance for Linux or macOS users, nor is it clarified whether Service Fabric clusters on Linux can use similar security models.
Recommendations
  • Clarify whether gMSA and RunAsPolicy are supported on Linux clusters, and if not, explicitly state this limitation.
  • If Linux support exists, provide equivalent instructions and examples for configuring service accounts on Linux clusters, including relevant tools and commands (e.g., systemd, Linux user management).
  • If only Windows is supported, add a prominent note at the top indicating that the procedure is Windows-only.
  • Consider providing alternative security recommendations for Linux clusters, such as using managed identities or local service accounts.
Service Fabric Scale up an Azure Service Fabric non-primary node type ...abric/service-fabric-scale-up-non-primary-node-type.md
High 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 is heavily biased towards Windows environments, with all command-line examples provided in PowerShell, Windows file paths, and Windows-centric tooling. There are no equivalent instructions or examples for Linux/macOS users, nor any mention of cross-platform alternatives (e.g., Azure CLI, Bash). The VM upgrade scenario exclusively references Windows Server SKUs, further reinforcing the Windows focus.
Recommendations
  • Provide Azure CLI (az) command equivalents for all PowerShell commands, as Azure CLI is cross-platform.
  • Include Linux/macOS-specific instructions for certificate generation, file paths, and resource management.
  • Mention and demonstrate how to perform Service Fabric cluster operations from Bash or other non-Windows shells.
  • Reference Linux VM SKUs and show how to upgrade node types running Linux, not just Windows Server.
  • Add notes or links to cross-platform tooling and documentation for users on non-Windows systems.
Service Fabric Standalone Service Fabric clusters overview ...-fabric/service-fabric-standalone-clusters-overview.md
High 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 presents Service Fabric clusters as supporting both Windows Server and Linux, but the details and examples are almost exclusively focused on Windows environments. Security sections reference Windows authentication and Active Directory, and the 'Supported operating systems' list only includes Windows Server versions, with a note that Linux isn't yet supported. There are no Linux-specific instructions, examples, or references to Linux tools or patterns.
Recommendations
  • Add explicit Linux support status and roadmap, if Linux support is planned.
  • Include Linux-specific examples and instructions for cluster setup, security, and management.
  • Reference Linux authentication and security mechanisms (e.g., PAM, certificate management tools) where relevant.
  • List supported Linux distributions and versions when Linux support becomes available.
  • Ensure parity in documentation structure and depth for both Windows and Linux environments.
Service Fabric Monitor and diagnose Windows containers ...ic/service-fabric-tutorial-monitoring-wincontainers.md
High 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 is heavily focused on Windows containers and clusters, with all examples, templates, and instructions tailored to Windows environments. Windows-specific tools and patterns (e.g., PowerShell deployment, Windows Diagnostics agent, Windows performance counters) are mentioned exclusively, and Linux equivalents are only referenced briefly at the end, without concrete examples or walkthroughs.
Recommendations
  • Provide parallel, step-by-step instructions and Resource Manager template examples for Linux clusters and containers.
  • Include Linux-specific agent installation and configuration details (e.g., OMS agent for Linux, Linux performance counters).
  • Show how to deploy templates using cross-platform tools (e.g., Azure CLI, Bash) in addition to PowerShell.
  • Add screenshots and dashboard examples from Linux container monitoring.
  • Ensure that all referenced sample templates for Linux are linked and described in the main tutorial flow, not just in 'Next steps'.
Service Fabric Install Service Fabric standalone client ...bric-tutorial-standalone-create-service-fabric-cluster.md
High 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 is heavily biased towards Windows, with all examples, scripts, and tools (such as PowerShell scripts, Windows file paths, and Windows-specific configuration) tailored exclusively for Windows environments. There are no Linux or macOS instructions, examples, or references, despite the initial claim of 'any OS, any cloud'. This makes it difficult or impossible for Linux/macOS users to follow the tutorial.
Recommendations
  • Provide equivalent instructions and examples for Linux (and macOS) environments, including how to download, extract, and configure the Service Fabric standalone client on those platforms.
  • Include bash or shell script alternatives to the PowerShell scripts, or clarify if Linux is unsupported for standalone clusters.
  • Mention Linux-specific tools and file paths where relevant.
  • Explicitly state OS limitations if the standalone client is Windows-only, to avoid misleading users.
Service Fabric Configure the upgrade of a Service Fabric application ...abric/service-fabric-visualstudio-configure-upgrade.md
High 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 is heavily focused on Windows-centric tools and workflows, specifically Visual Studio and PowerShell. All upgrade instructions and examples reference Visual Studio dialogs and PowerShell cmdlets, with no mention of Linux/macOS alternatives such as CLI commands, cross-platform editors, or Bash scripts. There is no guidance for users who do not have access to Visual Studio or PowerShell, making it difficult for Linux/macOS users to follow the documented procedures.
Recommendations
  • Add instructions for upgrading Service Fabric applications using the Service Fabric CLI (sfctl), which is cross-platform.
  • Provide examples for configuring upgrade parameters and health policies using CLI commands or editing manifest files directly.
  • Include guidance for performing manual upgrades on Linux/macOS, such as using Bash or shell scripts.
  • Reference cross-platform editors (e.g., VS Code) for editing manifest files, not just Visual Studio.
  • Clearly indicate which steps are Windows-specific and offer Linux/macOS alternatives where possible.
Service Fabric Create infrastructure for a cluster on Azure VMs ...fabric-tutorial-standalone-azure-create-infrastructure.md
High 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 is heavily biased toward Windows environments. All VM creation instructions specify Windows Server, connection steps use RDP (Windows Remote Desktop), and configuration commands are exclusively PowerShell and Windows Command Prompt. There are no examples or guidance for Linux VM images, SSH connectivity, or Linux firewall/network configuration. This creates significant friction for users wishing to deploy Service Fabric clusters on Linux VMs.
Recommendations
  • Add parallel instructions for creating Linux VM instances, including recommended images (e.g., Ubuntu, CentOS).
  • Provide SSH-based connection steps for Linux VMs instead of only RDP.
  • Include Linux equivalents for firewall and SMB configuration (e.g., using ufw, firewalld, Samba).
  • Show Linux command-line examples (bash, shell) for connectivity checks (e.g., ping, smbclient, mount).
  • Clarify which steps are Windows-specific and which are required for Linux, or provide separate sections for each OS.
Service Fabric Enable Disk Encryption for Service Fabric managed cluster nodes ...abric/how-to-managed-cluster-enable-disk-encryption.md
High Priority View Details →
Scanned: 2026-01-12 00:00
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 strong Windows bias. All step-by-step instructions, deployment, and verification commands are provided exclusively using PowerShell and Windows-centric Azure tools. There is minimal mention of Linux, and no Linux-specific guidance or examples are given for Service Fabric managed cluster disk encryption. Even though Azure Disk Encryption supports Linux (via DM-Crypt), the documentation focuses on Windows and BitLocker, and all verification steps use PowerShell cmdlets without Linux alternatives.
Recommendations
  • Add explicit Linux instructions and examples, including how to enable and verify disk encryption on Linux-based Service Fabric managed cluster nodes.
  • Provide Azure CLI examples for all deployment and verification steps, not just for Key Vault creation.
  • Reference Linux documentation and tools (e.g., DM-Crypt usage, Linux VM extension details) alongside Windows/BitLocker equivalents.
  • Clarify which steps are OS-agnostic and which require OS-specific actions, and organize content so Linux and Windows parity is clear.
  • Include sample ARM templates and verification commands for Linux clusters.
Service Fabric Initializer CodePackages in Service Fabric ...in/articles/service-fabric/initializer-codepackages.md
High 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 strong Windows bias: all examples use Windows containers, Windows-specific images, and Windows file paths. The only complete example references Windows container images and uses Windows command syntax (cmd, C:\ paths, type, ping). There is no mention or example of Linux containers, Linux file paths, or Linux command syntax, nor any guidance for Linux/macOS users.
Recommendations
  • Add equivalent examples for Linux containers, using Linux-based images (e.g., Ubuntu, Alpine) and Linux command syntax (sh, /bin/bash, /workspace/log.txt, cat, sleep).
  • Clarify whether Initializer CodePackages are supported for Linux containers and, if not, explicitly state this limitation.
  • If supported, provide ApplicationManifest and ServiceManifest snippets for Linux containers, including volume mounts with Linux paths.
  • Rephrase introductory and example sections to be platform-neutral or to present both Windows and Linux options side-by-side.
  • Add a note about cross-platform compatibility and any differences in behavior between Windows and Linux container support.
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 is entirely focused on PowerShell, a tool most commonly used on Windows. All code samples and instructions use PowerShell cmdlets, with no mention of Bash, Azure CLI, or cross-platform alternatives. Windows-specific concepts (such as certificate stores like LocalMachine\My) are referenced without Linux equivalents. There are no examples or guidance for Linux/macOS users, making it difficult for them to follow the steps.
Recommendations
  • Add equivalent Azure CLI or Bash examples for each step, ensuring Linux/macOS users can follow along.
  • Explicitly mention cross-platform options and note any differences in certificate handling between Windows and Linux.
  • Provide guidance on how to install and use Azure PowerShell on Linux/macOS, or link to relevant resources.
  • Include notes or sections addressing certificate store locations and management on Linux systems.
Service Fabric Performance monitoring with Azure Diagnostics .../service-fabric/service-fabric-diagnostics-perf-wad.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page is heavily focused on Windows clusters, specifically using the Windows Azure Diagnostics (WAD) extension. All configuration examples, counter specifiers, and deployment instructions are tailored to Windows environments. Linux clusters are mentioned only briefly, with a link to a separate page, and no Linux-specific configuration or deployment examples are provided. The use of PowerShell for deployment further reinforces the Windows bias.
Recommendations
  • Provide equivalent Linux examples for configuring performance counter collection using the Log Analytics agent, including sample configuration files and deployment commands.
  • Include side-by-side or clearly separated instructions for both Windows and Linux clusters throughout the document.
  • Offer CLI or ARM template deployment examples that work on Linux/macOS, such as using Azure CLI instead of PowerShell.
  • Clarify which performance counters are available on Linux and how to specify them.
  • Link to or summarize the Linux documentation within this page for easier cross-reference.
Service Fabric Remove a node type in Azure Service Fabric | Microsoft Docs ...rvice-fabric/service-fabric-how-to-remove-node-type.md
High 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 exclusively uses PowerShell commands and Windows-centric tools for all operational steps, with no mention of Linux/macOS equivalents or cross-platform alternatives. There are no Bash, Azure CLI, or REST API examples, and the workflow assumes a Windows environment for cluster management.
Recommendations
  • Provide equivalent Azure CLI commands for each PowerShell example, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include Bash script examples for cluster operations where possible.
  • Mention REST API alternatives for resource management tasks.
  • Explicitly state platform requirements and offer guidance for Linux/macOS users on how to perform these tasks.
  • Reorder examples to present cross-platform solutions first, or side-by-side with PowerShell.
Service Fabric How to migrate to TLS (Transport Layer Security) 1.3 for Service Fabric ...vice-fabric/how-to-migrate-transport-layer-security.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows Only Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation is explicitly Windows-centric, stating that the steps are for Windows machines and that Linux isn't supported at this time. All prerequisites and upgrade instructions reference Windows Server, PowerShell, and Windows compatibility modes, with no mention of Linux equivalents or guidance for Linux/macOS users. There are no examples, instructions, or notes for Linux clusters, and the page does not address how or if TLS 1.3 migration is possible on non-Windows platforms.
Recommendations
  • Clearly state Linux support status and roadmap for TLS 1.3 in Service Fabric clusters.
  • Provide equivalent instructions or callouts for Linux clusters where possible, or link to relevant Linux documentation.
  • Include Linux-specific prerequisites, upgrade steps, and configuration examples if/when support is available.
  • If Linux is not supported, offer alternative security recommendations for Linux users.
  • Avoid using Windows tools (e.g., PowerShell) exclusively; mention cross-platform alternatives if applicable.