← Back to Dashboard
268
Pages Scanned
89
Pages Flagged
268
Changed Pages
33.2%
% Pages Flagged

Scan Information

Started At: 2026-02-10 00:00:07

Finished At: 2026-02-10 18:44:36

Status: completed

Target Repo: Azure Compute

Current Phase: discovery

Files Queued: 268

Files Completed: 268

Problematic Pages

89 issues found
Service Fabric Initializer CodePackages in Service Fabric ...in/articles/service-fabric/initializer-codepackages.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation page for Initializer CodePackages in Service Fabric presents only Windows container examples, exclusively references Windows container images (nanoserver), and uses Windows-specific paths and commands (cmd, C:\ paths, echo, type, ping). There are no Linux container examples or instructions, and the ApplicationManifest and ServiceManifest are tailored to Windows environments. The 'Next steps' section does not link to Linux-specific guidance.
Recommendations
  • Add examples using Linux container images (e.g., Ubuntu, Alpine) and Linux shell commands.
  • Show how to specify Initializer CodePackages for Linux containers, including appropriate volume mounts and file paths.
  • Clarify whether Initializer CodePackages are supported for Linux containers, and if not, state this explicitly.
  • Provide parity in documentation by including both Windows and Linux container scenarios, or clearly indicate platform limitations.
  • Link to Linux container getting started guides if available.
GitHub Create Pull Request
Service Fabric Upgrade an Azure Service Fabric standalone cluster ...ce-fabric/service-fabric-cluster-upgrade-standalone.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation page on upgrading an Azure Service Fabric standalone cluster exhibits a Windows bias. References and links are primarily to Windows Server-specific documentation (e.g., 'service-fabric-cluster-upgrade-windows-server.md', 'service-fabric-cluster-config-upgrade-windows-server.md'). The Patch Orchestration Application is only discussed for Windows, and there are no explicit Linux examples or references to Linux clusters or tools. There is no mention of Linux-specific upgrade guidance or parity in examples.
Recommendations
  • Clarify early in the article whether standalone clusters and upgrade processes are Windows-only, or provide equivalent Linux guidance if Linux standalone clusters are supported.
  • If Linux standalone clusters are supported, add Linux-specific upgrade instructions, examples, and references.
  • For features like the Patch Orchestration Application, explicitly state if Linux is unsupported, or provide Linux alternatives if available.
  • Where possible, use OS-neutral language and link to both Windows and Linux documentation, or clearly indicate OS-specific sections.
GitHub Create Pull Request
Service Fabric Azure Service Fabric reverse proxy ...articles/service-fabric/service-fabric-reverseproxy.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation explicitly states that the Service Fabric reverse proxy is not available for Linux clusters, and all examples and guidance are Windows-centric. There are no Linux-specific instructions, examples, or workarounds provided. The feature is fundamentally unavailable on Linux, and the documentation does not offer alternatives or guidance for Linux users.
Recommendations
  • Clearly state at the top that reverse proxy is Windows-only, and link to any Linux alternatives or workarounds if available.
  • Provide guidance or references for Linux users on how to achieve similar functionality, if possible (e.g., using other proxy solutions or patterns).
  • Add a section explaining why the feature is unavailable on Linux and any roadmap or plans for parity, if relevant.
  • Ensure that navigation or 'Next steps' links do not mislead Linux users into thinking they can use reverse proxy on Linux clusters.
GitHub Create Pull Request
Service Fabric Standalone Service Fabric clusters overview ...-fabric/service-fabric-standalone-clusters-overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ missing_linux_example ⚠️ windows_first
Summary
The documentation page initially claims Service Fabric clusters can run on Windows Server and Linux, but the 'Supported operating systems' section states that Linux isn't yet supported for standalone clusters. Security sections focus on Windows authentication and Windows security options, with no Linux-specific guidance or examples. Windows terminology and features are mentioned first and exclusively, with no Linux parity.
Recommendations
  • Clarify at the top that standalone clusters are currently Windows-only, despite the initial mention of Linux.
  • Remove or revise the description to avoid implying Linux support where it does not exist.
  • Add a section explaining Linux support status and roadmap, if applicable.
  • If Linux support is planned, provide equivalent Linux examples and guidance alongside Windows instructions.
  • Ensure that security and scaling sections explicitly state Windows-only applicability, or add Linux-specific content when available.
GitHub Create Pull Request
Service Fabric RunToCompletion semantics and specifications ...blob/main/articles/service-fabric/run-to-completion.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation page provides RunToCompletion semantics for Service Fabric, but the code examples and guidance are exclusively focused on Windows containers (using Windows NanoServer images and Windows-specific commands). Querying deployment status is described only with PowerShell and C# APIs, with no mention of Linux tooling or Bash equivalents. There are no examples or guidance for Linux containers or cross-platform scenarios, despite Service Fabric supporting Linux containers.
Recommendations
  • Add equivalent examples for Linux containers, using a Linux base image (e.g., Ubuntu or Alpine) and Linux shell commands.
  • Clarify whether RunToCompletion semantics are supported for Linux containers, and if so, provide guidance and code samples.
  • Include instructions for querying deployment status using Bash/CLI tools on Linux, such as Azure CLI or REST API.
  • Avoid using Windows-specific terminology (e.g., 'cmd', 'set', 'exitCode') in generic sections; provide cross-platform alternatives.
  • Explicitly state any limitations or differences for Linux users if certain features are Windows-only.
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 →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example ⚠️ windows_first
Summary
The documentation page for restoring backup in Azure Service Fabric is heavily biased toward Windows and PowerShell usage. All command-line examples use PowerShell, including REST API calls, with no mention of Linux/macOS alternatives (such as Bash, curl, or Azure CLI). The prerequisite section requires installation of a PowerShell module, and the workflow assumes the use of Windows tools. There are no Linux/macOS-specific instructions or parity examples, which creates friction for non-Windows users.
Recommendations
  • Add equivalent Bash/curl examples for REST API calls, showing how to trigger backup and restore operations from Linux/macOS.
  • Mention Azure CLI commands if available for relevant operations.
  • Clarify whether the PowerShell module is cross-platform or Windows-only; if Windows-only, provide alternative guidance for Linux/macOS users.
  • Include notes or sections for Linux/macOS users, outlining any differences or limitations.
  • Consider providing sample scripts or guidance for using Service Fabric REST APIs directly from non-Windows environments.
GitHub Create Pull Request
Service Fabric On-demand backup in Azure Service Fabric ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-backup-restore-service-ondemand-backup.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation is heavily focused on PowerShell-based workflows and the Microsoft.ServiceFabric.Powershell.Http module, with all code examples using PowerShell. There are no CLI, Bash, or cross-platform examples, nor is there guidance for Linux/macOS users on how to perform on-demand backups. The REST API is only demonstrated via PowerShell, not with curl or other cross-platform tools.
Recommendations
  • Add equivalent examples using Azure CLI or Bash scripts where possible.
  • Demonstrate REST API usage with curl or HTTPie for Linux/macOS users.
  • Clarify whether the PowerShell module is supported on PowerShell Core (pwsh) on Linux/macOS, and provide installation instructions if so.
  • Explicitly mention if certain features are Windows-only, or provide alternative guidance for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Service Fabric Explorer blocking operations ...ged-cluster-service-fabric-explorer-blocking-operation.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation page primarily references PowerShell cmdlets (Az PowerShell, AzSF PowerShell) for managing Service Fabric resources, with no mention of Linux/macOS equivalents or Azure CLI commands except a single reference to 'az resource'. The examples and instructions are PowerShell-centric, which may create friction for Linux/macOS users who typically use Azure CLI or REST APIs.
Recommendations
  • Include Azure CLI examples for all operations (e.g., deleting resources, creating applications/services) alongside PowerShell cmdlets.
  • Clarify which commands are cross-platform and which are Windows-only.
  • Reference REST API options where available for platform-agnostic management.
  • Add notes or links for Linux/macOS users on how to perform equivalent operations.
GitHub Create Pull Request
Service Fabric Service sensitivity ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-sensitivity.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation provides PowerShell examples for configuring service sensitivity and maximum load, but does not offer equivalent Linux/macOS CLI or scripting examples (such as Bash or Azure CLI). PowerShell is presented before C# API examples, and there is no mention of cross-platform tools or commands, creating friction for Linux/macOS users who may not have access to PowerShell or prefer other tools.
Recommendations
  • Add Azure CLI or REST API examples for configuring service sensitivity and maximum load, as these are cross-platform and accessible from Linux/macOS.
  • Clarify whether PowerShell examples are usable on Linux (via PowerShell Core), or provide Bash script equivalents if possible.
  • Mention any limitations or prerequisites for Linux/macOS users, such as required SDKs or tools.
  • Consider including sample commands for cluster configuration using cross-platform tools (e.g., Azure CLI, Bash, Python SDK).
GitHub Create Pull Request
Service Fabric Azure Service Fabric dynamic node tags ...tps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-node-tagging.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation provides PowerShell examples for managing node tags and service tag requirements, but does not offer equivalent examples for Linux/macOS users (e.g., Bash, CLI, or REST API usage). PowerShell is primarily a Windows tool, and its exclusive use creates friction for non-Windows users. The C# API examples are cross-platform, but scripting and command-line operations are only shown for Windows.
Recommendations
  • Add Azure CLI or Bash examples for managing node tags and service tag requirements.
  • Include REST API sample calls for tag operations, as REST is platform-neutral.
  • Explicitly mention whether PowerShell cmdlets are available cross-platform (PowerShell Core) or only on Windows.
  • Reorder examples so that platform-neutral methods (REST, CLI) are shown before or alongside PowerShell.
GitHub Create Pull Request
Service Fabric Learn more about Azure Service Fabric ...icles/service-fabric/service-fabric-content-roadmap.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation provides a broad overview of Azure Service Fabric, covering both Windows and Linux support. However, there are several instances of Windows bias: Windows services and executables (e.g., FabricHost.exe) are described in detail before Linux equivalents are mentioned, and some examples (such as standalone clusters) are Windows-only. PowerShell is frequently referenced as a management tool, with Linux CLI alternatives mentioned but not emphasized equally. There are missing Linux-specific examples, especially for cluster creation and management, and some features are described as Windows-only without Linux parity.
Recommendations
  • Provide Linux-specific examples and workflows alongside Windows ones, especially for cluster creation, management, and standalone deployment.
  • When describing Service Fabric node architecture, clarify Linux equivalents or note differences more explicitly.
  • Ensure CLI (sfctl) and REST API usage are shown equally with PowerShell, and highlight Linux-friendly tooling where available.
  • Where features are Windows-only (e.g., standalone clusters), clearly state the limitation and link to Linux alternatives or roadmap.
  • In 'Next steps', add links to Linux cluster creation and management guides if available.
GitHub Create Pull Request
Service Fabric Health monitoring in Service Fabric ...s/service-fabric/service-fabric-health-introduction.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation provides a PowerShell-only example for reporting and evaluating application health in Service Fabric, without offering equivalent Linux/macOS CLI or REST API examples. The main walkthrough for health reporting is Windows-centric, creating friction for non-Windows users.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl) for Linux/macOS environments.
  • Include REST API examples for health reporting and querying, which are cross-platform.
  • Clearly indicate which tools are available on each platform and link to relevant installation guides.
  • Where PowerShell is used, provide alternative commands for Bash or other common Linux shells.
GitHub Create Pull Request
Service Fabric Azure Service Fabric image store connection string ...fabric/service-fabric-image-store-connection-string.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation repeatedly references PowerShell for cluster manifest retrieval and application deployment, and links primarily to PowerShell-based workflows. There is no mention of Linux/macOS equivalents (such as Bash, Azure CLI, or cross-platform Service Fabric SDK usage), nor are examples provided for non-Windows environments. The focus on Visual Studio and PowerShell further reinforces a Windows-centric approach, despite Service Fabric supporting Linux clusters.
Recommendations
  • Include examples for retrieving the cluster manifest and deploying applications using Azure CLI and Bash scripts.
  • Reference cross-platform Service Fabric SDK tools and workflows, clarifying which steps apply to Linux clusters.
  • Add links to documentation or guides for Linux/macOS users, especially for local development and deployment.
  • Mention any differences or limitations when configuring ImageStoreConnectionString on Linux clusters.
GitHub Create Pull Request
Service Fabric Manage apps for multiple environments ...e-fabric-manage-multiple-environment-app-configuration.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides examples for managing application parameters in Service Fabric, with a notable emphasis on PowerShell and Visual Studio workflows. PowerShell is mentioned first for application creation, and Visual Studio parameter files are discussed in detail. Linux-friendly tools like sfctl and Jenkins are referenced, but Windows-centric tools and patterns are prioritized.
Recommendations
  • Present Linux-native tools (sfctl, install.sh) before or alongside PowerShell examples.
  • Expand examples for Jenkins and other Linux/macOS CI/CD tools, including sample scripts.
  • Clarify which steps are cross-platform and which are Windows-specific.
  • Add explicit guidance for Linux/macOS users, including command-line examples and parameter file handling outside Visual Studio.
GitHub Create Pull Request
Service Fabric Azure Service Fabric hosting activation and deactivation life cycle ...les/service-fabric/service-fabric-hosting-lifecycle.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation is largely OS-agnostic in its technical explanations, but the 'Next steps' section and some linked references focus on PowerShell for deployment and management tasks, which can create a perception of Windows bias. There are no explicit Linux examples or mentions of Linux-specific tools or workflows, and PowerShell is referenced before any cross-platform alternatives.
Recommendations
  • Include equivalent Linux/bash examples or references alongside PowerShell, especially in the 'Next steps' section.
  • Clarify when PowerShell commands are cross-platform (PowerShell Core) or Windows-only.
  • Add links to documentation for deploying and managing Service Fabric applications on Linux clusters using CLI or bash scripts.
  • Where possible, mention both Windows and Linux management workflows to ensure parity.
GitHub Create Pull Request
Service Fabric Azure Service Fabric container application manifest examples ...abric/service-fabric-manifest-example-container-app.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation page demonstrates a notable Windows bias. The manifest examples are explicitly based on a Windows Server 2016 container sample, and Windows-specific tools (e.g., 'winver' for OS build detection) are referenced without Linux equivalents. The certificate handling section does mention both Windows (PFX) and Linux (PEM) formats, but Linux-specific instructions and examples are missing. The volume mount paths use Windows-style paths (e.g., 'c:\VolumeTest\Data'), and there are no Linux path examples or guidance. Overall, Linux parity is not achieved, and Linux users may encounter friction or confusion.
Recommendations
  • Provide equivalent Linux-based manifest examples, referencing Linux container samples.
  • Include instructions for obtaining OS build/version on Linux (e.g., 'cat /etc/os-release' or 'uname -r') alongside 'winver'.
  • Show Linux-style volume mount paths (e.g., '/mnt/volume/data') in examples.
  • Clarify which manifest settings and features are cross-platform and which are Windows-only.
  • Add links or references to Linux container documentation and samples for Service Fabric.
GitHub Create Pull Request
Service Fabric Define Service Configuration in StartupServices.xml for a Service Fabric Application ...service-fabric/service-fabric-startupservices-model.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation is heavily focused on Visual Studio workflows, referencing Windows-centric concepts such as F5/Ctrl+F5/Publish and right-click actions. There are no examples or guidance for Linux/macOS users or CLI-based workflows, and all deployment instructions assume the use of Visual Studio, which is primarily a Windows tool.
Recommendations
  • Add explicit guidance for Linux/macOS users, including how to manage service configuration outside Visual Studio.
  • Provide CLI-based examples (e.g., using Azure CLI, Service Fabric CLI, or PowerShell Core) for defining and deploying StartupServices.xml.
  • Clarify whether StartupServices.xml is supported or relevant for non-Windows environments, and if not, suggest alternatives.
  • Mention cross-platform tools and workflows where applicable, or explicitly state Windows-only limitations.
GitHub Create Pull Request
Service Fabric Learn Azure Service Fabric terminology ...es/service-fabric/service-fabric-technical-overview.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools
Summary
The documentation page is mostly neutral and conceptual, but some sections show Windows bias. The 'Node' definition references an 'auto-start Windows service, FabricHost.exe', and describes node startup in Windows-centric terms, without mentioning Linux equivalents or patterns. Executable examples (EXE/DLL) are Windows-first, and Windows containers are mentioned before Linux containers. However, the page does acknowledge Linux support and guest executables, and Service Fabric's cross-platform nature.
Recommendations
  • In the 'Node' section, clarify how Service Fabric nodes operate on Linux (e.g., what processes/services are involved, and whether FabricHost.exe is relevant).
  • When mentioning executable formats (EXE/DLL), add Linux equivalents (e.g., ELF binaries, .so files) to ensure parity.
  • When discussing containers, mention Linux container support before or alongside Windows containers.
  • Where Windows-specific tools or terminology are used, provide Linux/macOS equivalents or note differences.
GitHub Create Pull Request
Virtual Machines Create a VM from a specialized image version ...icles/virtual-machines/vm-specialized-image-version.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for creating VMs from specialized images, but PowerShell examples are notably more verbose and detailed, including full network setup and VM configuration. CLI examples are shorter and less comprehensive. PowerShell is a Windows-centric tool, and its prominence and depth in the documentation may create friction for Linux/macOS users. Additionally, PowerShell examples are often shown immediately after CLI, which can subtly reinforce Windows-first patterns.
Recommendations
  • Expand Azure CLI examples to include full VM/network setup, matching the detail level of PowerShell examples.
  • Explicitly mention that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Consider including Bash scripts or references to native Linux tools where relevant.
  • Ensure that CLI and PowerShell examples are equally comprehensive and placed with equal prominence.
  • Add a note clarifying that PowerShell examples are primarily for Windows users, while CLI is suitable for all platforms.
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 →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation is largely OS-neutral in its conceptual explanations, but when it comes to practical details, there is a notable Windows bias. Windows-specific certificate store paths and troubleshooting tools (e.g., LocalMachine\My, CAPI2 logging, Win32 CryptoAPI references) are mentioned first or exclusively, with Linux equivalents only briefly referenced or omitted. Troubleshooting and operational guidance focus on Windows event logs and tools, with little to no Linux-specific instructions or examples.
Recommendations
  • For every mention of Windows certificate store paths (e.g., LocalMachine\My), provide the Linux equivalent (e.g., /var/lib/sfcerts) consistently and with equal prominence.
  • Include Linux-specific troubleshooting steps, such as where to find Service Fabric logs on Linux nodes, and how to diagnose certificate issues using Linux-native tools (e.g., openssl, journalctl, or SF log locations).
  • When referencing Windows tools like CAPI2 logging or Win32 CryptoAPI, add Linux alternatives or clarify which steps are Windows-only and provide Linux guidance where possible.
  • In code/configuration examples, ensure both Windows and Linux paths/formats are shown side-by-side, especially for certificate loading and management.
  • Explicitly mention any differences in certificate handling or requirements between Windows and Linux clusters, if applicable.
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 →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides examples for modifying Service Fabric managed cluster node types using Azure Portal, ARM templates, and PowerShell. PowerShell is the only CLI example provided, with no mention of Azure CLI or Bash scripting. PowerShell is a Windows-centric tool, and its exclusive use in CLI examples creates friction for Linux/macOS users. Additionally, PowerShell examples are given equal prominence to ARM templates and Portal, rather than being secondary or accompanied by cross-platform alternatives.
Recommendations
  • Add Azure CLI examples for all operations currently demonstrated with PowerShell (add, remove, scale, configure placement properties, etc.).
  • Explicitly mention that PowerShell examples are Windows-centric and provide guidance for Linux/macOS users (e.g., using Azure CLI or REST API).
  • Where possible, show Azure CLI examples before or alongside PowerShell to ensure Linux parity.
  • Clarify if any operations are only possible via PowerShell and, if so, explain why and suggest alternatives for Linux users.
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 →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page provides PowerShell examples for configuring MoveCost, but does not offer equivalent Linux CLI or Bash examples. PowerShell is primarily a Windows tool, and its exclusive use creates friction for Linux/macOS users. Additionally, PowerShell examples are presented before C# code, reinforcing Windows-first bias. There is no mention of Linux-native tools or Service Fabric CLI usage for these operations.
Recommendations
  • Add examples using Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • Include Bash or shell script snippets where applicable.
  • Clarify whether PowerShell commands can be run on Linux (via PowerShell Core), or provide guidance for Linux users.
  • Present CLI examples before or alongside PowerShell to avoid Windows-first ordering.
GitHub Create Pull Request
Service Fabric Manage certificates in a Service Fabric cluster ...vice-fabric/cluster-security-certificate-management.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ windows_tools
Summary
The documentation provides extensive PowerShell examples and references Windows-specific tools and behaviors (such as Key Vault VM extension for Windows, S-channel, and certificate linking), with little to no mention of Linux/macOS equivalents or cross-platform alternatives. Windows terminology and mechanisms are presented first and in detail, while Linux-specific guidance is largely absent.
Recommendations
  • Add equivalent Bash/CLI examples for certificate enrollment and management, especially for Key Vault operations.
  • Clarify which steps and tools are Windows-only and provide Linux/macOS alternatives where possible (e.g., for certificate provisioning and VM extensions).
  • Explicitly state platform limitations and supported OSes for each mechanism (e.g., Key Vault VM extension for Windows vs. Linux).
  • Include references or links to Linux/macOS documentation for Service Fabric certificate management.
  • Where PowerShell is used, offer Azure CLI or REST API alternatives for cross-platform users.
GitHub Create Pull Request
Service Fabric Introduction to the Service Fabric Infrastructure Service .../articles/service-fabric/infrastructure-service-faq.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides a PowerShell-only example for bypassing Infrastructure Service throttling, without mentioning equivalent Linux/macOS command-line options or tools. Service Fabric Explorer is referenced, but no cross-platform alternatives or clarifications are given. While Service Fabric clusters can run on both Windows and Linux, the guidance and tooling examples are Windows-centric.
Recommendations
  • Add equivalent Linux/macOS command-line instructions (e.g., using sfctl or REST API) for cluster operations.
  • Clarify whether the PowerShell cmdlet is available on Linux (via PowerShell Core) or provide alternatives.
  • Mention cross-platform tools like sfctl or REST endpoints for managing Service Fabric clusters.
  • Explicitly state if certain operations are Windows-only, or provide guidance for Linux users.
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 →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation page provides best practice examples primarily using Azure PowerShell, with PowerShell cmdlets referenced before Azure CLI or other cross-platform tools. While the table lists Azure CLI and ARM/Bicep as ARM-backed utilities, the narrative and example links focus on PowerShell, which is more native to Windows environments. No explicit Linux/macOS examples or command syntax are provided.
Recommendations
  • Include Azure CLI examples alongside PowerShell cmdlets for key operations (e.g., deleting NodeTypes, restarting/reimaging scale sets).
  • Explicitly mention cross-platform compatibility of Azure CLI and Bicep, and provide sample commands for Linux/macOS users.
  • Clarify that PowerShell is available on Linux/macOS, but highlight Azure CLI as the default cross-platform tool.
  • Consider showing Azure CLI examples before or alongside PowerShell examples to avoid Windows-first bias.
GitHub Create Pull Request
Service Fabric Monitor Azure Service Fabric ...main/articles/service-fabric/monitor-service-fabric.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation provides monitoring guidance for Azure Service Fabric clusters on both Windows and Linux, but there are several areas where Windows tools and examples are mentioned first or exclusively. Windows-specific tools (e.g., Event Log/Event Viewer, Diagnostics Agent) are referenced before Linux equivalents, and some features (like EventStore APIs) are noted as Windows-only without Linux alternatives or workarounds. Linux monitoring is addressed, but often as an afterthought or with less detail, and some example/tutorial links are Windows/.NET-focused.
Recommendations
  • Ensure Linux monitoring tools and workflows are described with equal prominence and detail as Windows equivalents.
  • Provide Linux-specific examples and tutorials (e.g., instrumenting applications, configuring monitoring agents, querying logs).
  • Where features are Windows-only, clearly state Linux alternatives or workarounds, or link to relevant Linux documentation.
  • Avoid listing Windows tools or workflows first unless they are more widely used; alternate order or group by OS.
  • Expand references to Linux logging frameworks and monitoring solutions beyond Syslog and LTTng, including practical examples.
GitHub Create Pull Request
Service Fabric Describing Azure Service Fabric apps and services ...ic/service-fabric-application-and-service-manifests.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first
Summary
The documentation contains a notable Windows bias in its tooling recommendations. It explicitly suggests opening the Service Fabric XSD schema in Visual Studio using a Windows file path ("C:\Program Files\Microsoft SDKs\Service Fabric\schemas\ServiceFabricServiceModel.xsd") for schema validation and IntelliSense. There is no mention of equivalent tools or workflows for Linux or macOS users, nor are cross-platform editors (e.g., VS Code) or alternative validation methods referenced. Additionally, the only explicit tooling guidance is Windows/Visual Studio-centric and appears early in the article.
Recommendations
  • Provide instructions for validating and editing manifest XML files on Linux and macOS, such as using VS Code with XML extensions, or command-line tools like xmllint.
  • Mention the location of the Service Fabric XSD schema on non-Windows installations, or provide a download link.
  • Avoid referencing only Windows file paths; include cross-platform alternatives or clarify when instructions are Windows-specific.
  • If Visual Studio is not available, suggest other editors or IDEs that support XML schema validation on Linux/macOS.
GitHub Create Pull Request
Service Fabric Advanced Application Upgrade Topics ...-fabric/service-fabric-application-upgrade-advanced.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page provides numerous PowerShell cmdlet examples (e.g., New-ServiceFabricService, Update-ServiceFabricService, Start-ServiceFabricApplicationUpgrade) without mentioning or demonstrating equivalent CLI or scripting approaches for Linux/macOS users. The PowerShell-centric instructions and examples are presented throughout, with no clear guidance for Linux users on how to perform these tasks using cross-platform tools. This creates friction for non-Windows users, especially since Service Fabric supports Linux clusters and the Azure CLI.
Recommendations
  • Add Azure CLI examples for all PowerShell cmdlet usage, especially for service creation, updates, and application upgrades.
  • Explicitly mention which PowerShell cmdlets are available cross-platform (via PowerShell Core) and which are Windows-only.
  • Provide guidance or links for Linux/macOS users on managing Service Fabric applications, including references to REST APIs and Azure CLI.
  • Where possible, show XML/ARM template snippets alongside CLI commands, not just PowerShell.
  • Clarify any limitations or differences for Linux clusters in relevant sections.
GitHub Create Pull Request
Service Fabric Application upgrade: upgrade parameters ...abric/service-fabric-application-upgrade-parameters.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation page presents Windows/PowerShell and Visual Studio parameters and examples before Linux equivalents (SFCTL), and provides more detailed parameter tables and explanations for PowerShell/Visual Studio. SFCTL (the cross-platform CLI) is covered in a separate section with less detail and fewer examples. The 'Next steps' section also lists Windows upgrade tutorials before Linux ones.
Recommendations
  • Present SFCTL (Service Fabric CLI) parameters and examples alongside PowerShell/Visual Studio, rather than in a separate section, to emphasize parity.
  • Provide equally detailed parameter tables and usage examples for SFCTL as for PowerShell.
  • Include sample upgrade commands for SFCTL in the main parameter tables.
  • In the 'Next steps' section, list Linux/SFCTL tutorials before or alongside Windows tutorials.
  • Clarify that SFCTL is the recommended cross-platform tool for Linux/macOS users.
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 →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation covers Azure Service Fabric application security in a generally cross-platform manner, but several sections show Windows bias. Windows-specific tools and features (e.g., BitLocker, Active Directory, gMSA) are mentioned without Linux equivalents or with Linux information relegated to brief mentions. Examples and guidance often focus on Windows scenarios first or exclusively, with Linux alternatives missing or referenced only in passing.
Recommendations
  • Provide explicit Linux examples and guidance for securing disks (e.g., using Azure Disk Encryption for Linux, dm-crypt, or other supported methods).
  • When discussing running services under different accounts, clarify Linux options (e.g., running as custom users, systemd service accounts) and provide relevant examples.
  • For certificate management and access in containers, include step-by-step Linux container guidance alongside Windows instructions.
  • Ensure parity in coverage for Linux clusters, including links to Linux-specific documentation where available.
  • When referencing Windows tools (e.g., BitLocker, Active Directory), add notes or links for Linux alternatives or clarify if a feature is Windows-only.
GitHub Create Pull Request
Service Fabric Application lifecycle in Service Fabric ...service-fabric/service-fabric-application-lifecycle.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ windows_first
Summary
The documentation frequently references PowerShell cmdlets and Windows-specific tools for managing the Service Fabric application lifecycle. While REST API and .NET methods are also mentioned, PowerShell examples and terminology are prominent and often listed first. There is little explicit mention of Linux-native tools or CLI examples (such as sfctl or Azure CLI), and no Linux/macOS-specific guidance is provided. This creates friction for Linux/macOS users, who must infer their workflow or consult external resources.
Recommendations
  • Add explicit examples using sfctl (Service Fabric CLI) and Azure CLI for each lifecycle operation, alongside PowerShell.
  • Where PowerShell cmdlets are referenced, provide equivalent Linux/macOS commands or links to relevant documentation.
  • Clarify which tools are cross-platform and which are Windows-only, to help users select appropriate methods.
  • Consider listing REST API, sfctl, or Azure CLI examples before PowerShell to avoid implicit Windows-first bias.
  • Add a section or note summarizing Linux/macOS support and recommended tooling for Service Fabric operations.
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 →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ windows_first
Summary
The documentation page primarily references Windows-centric tools and patterns, such as Visual Studio and PowerShell, in its 'Next steps' section. These tools are mentioned first and exclusively as upgrade walkthroughs, with no Linux/macOS equivalents or CLI examples provided. The content also assumes C# and .NET serialization, which, while cross-platform in .NET Core/.NET 5+, is historically Windows-centric. There are no explicit Linux/macOS examples or guidance.
Recommendations
  • Add equivalent upgrade walkthroughs using Azure CLI or Service Fabric CLI (sfctl), which are cross-platform.
  • Mention cross-platform development environments (such as VS Code or JetBrains Rider) alongside Visual Studio.
  • Clarify that PowerShell examples can be run on Linux/macOS using PowerShell Core, or provide Bash examples where possible.
  • Explicitly state .NET Core/.NET 5+ support and cross-platform compatibility for serialization.
  • Provide links or references to Linux/macOS-specific documentation for Service Fabric application upgrades.
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 →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation provides several manual scaling instructions using PowerShell cmdlets (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState) without offering equivalent Linux/CLI/Bash examples or alternatives. This creates friction for Linux users, as Service Fabric clusters can be run on both Windows and Linux, and the page is not Windows-specific. The focus on PowerShell and lack of cross-platform command examples is a notable bias.
Recommendations
  • For every PowerShell command or workflow, provide equivalent Azure CLI, Bash, or REST API examples where possible.
  • Explicitly note if certain operations (e.g., Disable-ServiceFabricNode) are only available via PowerShell, and suggest alternative approaches for Linux users.
  • Add links to Linux-specific Service Fabric management documentation or tools.
  • Clarify in each section whether the instructions apply to both Windows and Linux clusters, or if there are differences.
GitHub Create Pull Request
Service Fabric Service Fabric application upgrade ...s/service-fabric/service-fabric-application-upgrade.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page for Service Fabric application upgrade demonstrates a notable Windows bias. The only code example provided is in PowerShell, which is a Windows-centric tool. References to Service Fabric PowerShell cmdlets and Windows-specific technologies (such as http.sys and Windows HTTP Server API) are present, with no equivalent Linux or cross-platform CLI examples. The 'Next steps' section prioritizes Visual Studio and PowerShell tutorials, both of which are primarily Windows tools, and does not mention Linux-compatible alternatives (such as Azure CLI, REST API, or Service Fabric CLI). This creates friction for Linux/macOS users, who may not have access to PowerShell or Visual Studio environments.
Recommendations
  • Provide equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • Include references and links to Linux/macOS-compatible upgrade workflows, such as using Azure CLI or REST API.
  • Clarify which features or commands are Windows-only, and offer guidance for Linux users where possible.
  • Reorder or balance 'Next steps' to include Linux/macOS upgrade tutorials alongside Windows/PowerShell options.
GitHub Create Pull Request
Service Fabric Understanding periodic backup configuration ...-fabric-backuprestoreservice-configure-periodic-backup.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation page is generally platform-neutral, focusing on Service Fabric's backup configuration concepts and REST APIs. However, in the 'File share' backup storage section, only Windows-style UNC paths (\\StorageServer\BackupStore) and Windows authentication mechanisms are described, with no mention of Linux-compatible file share paths (e.g., SMB/CIFS mounts) or authentication methods. There are no Linux-specific examples or guidance for configuring file shares, which may create friction for Linux cluster administrators.
Recommendations
  • Add examples for configuring file share backup storage using Linux-compatible paths and authentication (e.g., SMB/CIFS mounts, NFS, or guidance on mounting Azure Files on Linux nodes).
  • Clarify whether file share backup storage is supported on Linux clusters, and if so, provide instructions for Linux environments.
  • If file share backup is Windows-only, explicitly state this limitation to avoid confusion for Linux users.
  • Consider including a table or section comparing storage options and their platform compatibility.
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 →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Service Fabric clusters, but PowerShell is featured prominently and exclusively for certain operations (e.g., cluster upgrades). Windows-specific tools and registry keys are mentioned without Linux equivalents. Windows configuration details are presented before Linux, and some upgrade instructions are Windows-centric.
Recommendations
  • Add Linux-specific examples for cluster upgrade operations, such as using Bash or relevant Linux tools.
  • Include instructions for disabling automatic updates on Linux VMs (e.g., using cloud-init or systemd), not just Windows registry keys.
  • Provide parity in PowerShell and Bash/CLI examples throughout, especially for critical operations.
  • When referencing VM configuration, mention both Windows and Linux properties, or clarify if a property is Windows-only.
  • Ensure upgrade instructions (manual and automatic) are available for both OS types, or clearly state if a step is Windows-only.
GitHub Create Pull Request
Service Fabric Azure Service Fabric networking best practices ...ice-fabric/service-fabric-best-practices-networking.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation page covers Azure Service Fabric networking best practices for both Windows and Linux clusters, but exhibits several Windows biases. PowerShell and Windows-specific tools are referenced more frequently and prominently (e.g., Client API endpoint described as 'used by PowerShell', Azure DevOps section focuses on classic PowerShell tasks, and Windows container networking is discussed in detail). Windows examples and terminology often appear before Linux equivalents, and some sample links and templates are Windows-centric. Linux-specific guidance is less detailed, and Linux command-line examples are missing.
Recommendations
  • Provide Linux CLI (az CLI, bash) examples alongside PowerShell examples, especially for cluster management and networking tasks.
  • Clarify when guidance applies to both Windows and Linux, and highlight any Linux-specific differences or requirements.
  • Include links to Linux-focused ARM templates and sample clusters, not just Windows ones.
  • Expand Linux container networking guidance, including best practices and troubleshooting.
  • Balance references to Windows tools (e.g., PowerShell) with Linux equivalents (e.g., bash, az CLI).
GitHub Create Pull Request
Service Fabric Azure Service Fabric security best practices ...rvice-fabric/service-fabric-best-practices-security.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation provides both Windows and Linux guidance for most security best practices, but there is a notable tendency to present Windows-specific examples, tools, and recommendations first. PowerShell commands and Windows Defender are discussed in detail, while Linux equivalents are sometimes less prominent or referenced after Windows. Some sections (e.g., Windows Defender, Windows security baselines) are Windows-only, but this is appropriate given the context. Overall, Linux users can complete all tasks, but may encounter friction due to Windows-centric ordering and tool emphasis.
Recommendations
  • Ensure Linux examples are presented alongside Windows examples, or in parallel sections, rather than after Windows.
  • Where possible, provide Linux-first or equally prominent Linux command examples (e.g., bash/openssl) for certificate generation and secret encryption.
  • Clarify Windows-only sections (e.g., Windows Defender, Windows security baselines) as intentionally platform-specific, and provide links or notes about Linux alternatives (e.g., mention common Linux security tools or practices).
  • Review ordering of examples and guidance to avoid implicit prioritization of Windows.
  • Add explicit notes about parity and limitations for Linux clusters where relevant.
GitHub Create Pull Request
Service Fabric Change Azure Service Fabric cluster settings ...rvice-fabric/service-fabric-cluster-fabric-settings.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ powershell_heavy
Summary
The documentation page provides a comprehensive reference for Service Fabric cluster settings, covering both Azure-hosted and standalone clusters. However, there is evidence of Windows bias: Windows terminology and tools (such as certificate store names like 'My', 'LocalMachine', and references to NTLM authentication) are used throughout, and Windows-specific configuration options (e.g., Windows Update, Windows-only log file settings) are mentioned without always providing Linux equivalents or clarifying platform differences. Some parameters default to Windows patterns or mention Windows-only behaviors first. While Linux is referenced in some settings, parity is inconsistent and Linux-specific guidance is limited.
Recommendations
  • For each configuration parameter, explicitly state platform applicability (Windows, Linux, or both) and provide Linux-specific guidance where relevant.
  • Where Windows certificate store names or NTLM authentication are referenced, clarify Linux equivalents (e.g., file paths, OpenSSL usage) and provide Linux-specific examples.
  • Add Linux-specific configuration examples and highlight any differences in behavior or default values.
  • Ensure that Linux tools, paths, and patterns are mentioned alongside Windows ones, not only as afterthoughts.
  • Where Windows-only features are described (e.g., Windows Update integration), clearly mark them as such and provide alternative approaches for Linux if possible.
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 →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation provides general information about Azure Service Fabric node types and virtual machine scale sets, but several sections and examples show a Windows bias. The JSON snippet uses a Windows-style file path (D:\SvcFab) for 'dataPath', and the 'Next steps' section links to PowerShell scripts for RDP port changes and admin credential updates, which are Windows-centric tasks. There are no explicit Linux/macOS examples, and Windows tools (RDP, PowerShell) are referenced without Linux alternatives.
Recommendations
  • Provide Linux/macOS equivalents for remote connection (e.g., SSH instructions alongside RDP/PowerShell).
  • Show Linux-style file paths (e.g., /var/svcfab) in JSON snippets when 'type' is 'ServiceFabricLinuxNode'.
  • Add links or guidance for managing Linux node types, including credential changes and port updates using Linux tools.
  • Clarify which steps are Windows-only and which apply to Linux, to help users navigate platform-specific instructions.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager - Application Groups ...ice-fabric-cluster-resource-manager-application-groups.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation page provides only PowerShell and C# examples for managing Application Groups in Service Fabric, with no mention of Linux-compatible tools or CLI equivalents. PowerShell is a Windows-centric tool, and its exclusive use creates friction for Linux/macOS users who may prefer or require cross-platform alternatives such as Azure CLI or REST APIs.
Recommendations
  • Add Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used by Linux/macOS users.
  • Mention REST API endpoints for managing Application Groups, with example requests.
  • Explicitly state if certain features or commands are only available via PowerShell, and provide guidance for Linux users.
  • Consider referencing Service Fabric SDK tools or scripts that work on Linux, if available.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager - Placement Policies ...ce-manager-advanced-placement-rules-placement-policies.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page provides code examples in C# and PowerShell for configuring Service Fabric placement policies, but does not include equivalent Linux/macOS CLI examples (e.g., Azure CLI or Bash). PowerShell is featured prominently, and Windows-centric tools are referenced before any cross-platform alternatives. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other tools.
Recommendations
  • Add Azure CLI or Bash script examples for each placement policy configuration, ensuring Linux/macOS users can follow along without PowerShell.
  • Explicitly mention cross-platform alternatives to PowerShell, such as Azure CLI, and link to relevant documentation.
  • Clarify which configuration steps are platform-agnostic and which are Windows-specific, if any.
  • Consider reordering examples so that cross-platform tools are presented alongside or before Windows-specific tools.
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 →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides both Windows and cross-platform (JSON-based) configuration examples, but there is a notable tendency to present Windows-specific formats (ClusterManifest.xml with <WindowsServer> blocks) and PowerShell commands before or more prominently than Linux equivalents. While standalone (non-Azure) deployments are shown using JSON, the XML examples are explicitly for Windows, and all imperative command-line examples use PowerShell, with no Bash/CLI equivalents. This may create friction for Linux users, especially those running Service Fabric on Linux or in cross-platform environments.
Recommendations
  • Add explicit Linux configuration examples (e.g., show ClusterManifest.xml for Linux clusters, or clarify if the JSON config is the preferred cross-platform method).
  • Provide Azure CLI or Bash script equivalents for all PowerShell command examples, or clarify if only PowerShell is supported for imperative operations.
  • When showing both XML and JSON, clarify which is for Windows and which is for Linux, and ensure Linux-first or parity in ordering.
  • Where possible, use neutral language and ordering (e.g., 'For Windows, use... For Linux, use...'), and avoid implying Windows is the default unless it is for Service Fabric.
  • If certain features are Windows-only, explicitly state this to avoid confusion.
GitHub Create Pull Request
Service Fabric Manage Azure Service Fabric app load using metrics ...ric/service-fabric-cluster-resource-manager-metrics.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page provides code examples for managing Service Fabric metrics primarily in C# and PowerShell. PowerShell is a Windows-centric tool, and no equivalent Linux/macOS CLI examples (such as Azure CLI or Bash scripts) are given. The PowerShell examples are presented alongside C# code, but there is no mention of cross-platform tools or how Linux users can accomplish the same tasks. The documentation implicitly assumes a Windows environment for scripting and service management.
Recommendations
  • Add Azure CLI examples for service creation and metric management, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Mention Bash scripting or REST API usage for managing Service Fabric services and metrics, providing sample commands or links to relevant documentation.
  • Clarify whether PowerShell Core (pwsh), which is cross-platform, can be used for these commands, and provide guidance for Linux/macOS users.
  • Where possible, provide equivalent instructions for Linux/macOS users, or explicitly state if certain operations are Windows-only.
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 →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation provides code examples for configuring auto scaling in Azure Service Fabric using C#, application manifests, and PowerShell. The PowerShell examples are Windows-specific, and there are no equivalent CLI or shell script examples for Linux/macOS users. The documentation references Windows tools and patterns (e.g., PowerShell cmdlets) without offering Linux alternatives or guidance, despite Service Fabric supporting Linux containers for auto scaling.
Recommendations
  • Add equivalent examples using Azure CLI or Bash scripts for Linux/macOS users where PowerShell is currently used.
  • Explicitly state which management operations (such as updating scaling policies) can be performed from Linux environments, and provide guidance or references for those.
  • Clarify any limitations or differences in auto scaling support between Windows and Linux clusters, especially for resource monitoring and governance.
  • Where possible, provide cross-platform instructions or note when a given example is Windows-only.
GitHub Create Pull Request
Service Fabric Cluster Resource Manager - Management Integration ...fabric-cluster-resource-manager-management-integration.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides a PowerShell example for querying Service Fabric partition health, using a Windows-style prompt and cmdlet (Get-ServiceFabricPartitionHealth). No equivalent Linux or cross-platform CLI example is given, and the example is presented early in the page. The rest of the content is platform-neutral, but the only practical example is Windows-centric.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl) for Linux/macOS users, e.g., 'sfctl partition health --partition-id <id>'.
  • Mention that PowerShell examples are for Windows and provide alternative commands for other platforms.
  • Consider showing cross-platform examples first, or side-by-side, to improve parity.
GitHub Create Pull Request
Service Fabric Azure Service Fabric standalone cluster scaling ...ce-fabric/service-fabric-cluster-scaling-standalone.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation page for scaling Azure Service Fabric standalone clusters demonstrates Windows bias by exclusively referencing Windows tools and PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) without mentioning Linux equivalents or providing Linux-specific guidance. There are no examples or instructions for Linux-based standalone clusters, even though Service Fabric standalone clusters can theoretically run on Linux. This creates friction for Linux users attempting to scale clusters.
Recommendations
  • Add Linux-specific instructions and examples for scaling standalone Service Fabric clusters, including relevant CLI commands and configuration steps.
  • Mention and link to Linux tools or documentation where applicable, such as using sfctl or REST APIs for cluster management.
  • Clarify whether certain steps or tools are Windows-only, and provide alternative guidance for Linux users.
  • Ensure parity in example order and visibility for both Windows and Linux environments.
GitHub Create Pull Request
Service Fabric Scalability of Service Fabric services .../service-fabric/service-fabric-concepts-scalability.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation provides code examples for scaling Service Fabric services using C# and PowerShell, but does not include equivalent Linux-native or cross-platform CLI examples (e.g., Azure CLI, Bash, or REST API). PowerShell is a Windows-centric tool, and its exclusive use in examples may create friction for Linux/macOS users. Additionally, the documentation references Windows-specific implementation details (e.g., kernel driver for logging) before discussing Linux differences, but does not provide Linux-oriented operational guidance or examples.
Recommendations
  • Add Azure CLI or REST API examples for service scaling operations alongside PowerShell and C#.
  • Explicitly mention Linux/macOS-compatible tools and workflows for managing Service Fabric clusters.
  • Where PowerShell is referenced, clarify if PowerShell Core (cross-platform) is supported, or provide Bash equivalents.
  • Expand the 'Choosing a platform' section with more Linux-specific operational advice and best practices.
  • Consider reordering or balancing the presentation of Windows and Linux details to avoid implicit prioritization of Windows.
GitHub Create Pull Request
Service Fabric Secure an Azure Service Fabric cluster ...cles/service-fabric/service-fabric-cluster-security.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page discusses security for Azure Service Fabric clusters, including both Azure-hosted and standalone clusters. However, it consistently provides detailed guidance and links for Windows Server standalone clusters, while omitting equivalent instructions or links for standalone Linux clusters. Windows security (Kerberos) is discussed, but no Linux authentication mechanisms are mentioned. Windows-specific certificate creation tools and services are referenced, with no mention of Linux alternatives. The structure and examples are Windows-first, and Linux standalone scenarios are not covered.
Recommendations
  • Add explicit guidance and links for securing standalone Linux Service Fabric clusters, including certificate setup and authentication options.
  • Mention Linux-compatible certificate creation tools (e.g., OpenSSL) alongside Windows tools.
  • Clarify which security features and recommendations apply equally to Linux clusters, and provide Linux-specific instructions where needed.
  • Include examples or references for Linux authentication mechanisms if supported (e.g., integration with Linux user accounts or other identity providers).
  • Ensure parity in documentation structure, so Linux users can easily find relevant information.
GitHub Create Pull Request
Service Fabric Upgrading Azure Service Fabric clusters ...icles/service-fabric/service-fabric-cluster-upgrade.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation page provides general guidance for upgrading Azure Service Fabric clusters, but it demonstrates Windows bias in several areas. References to PowerShell are made without equivalent Linux/bash examples, and the section on OS image upgrades links only to Windows-specific patching guidance. The mention of 'Patch Orchestration Application' is tied to Windows OS patching, with no mention of Linux node patching or upgrade procedures. Additionally, Windows tools (PowerShell) are mentioned before Azure CLI, and Linux-specific workflows are not described.
Recommendations
  • Include Linux-specific guidance for OS image upgrades, such as linking to documentation about patching Linux nodes in Service Fabric clusters.
  • Provide examples for managing certificates, opening application ports, and other cluster operations using bash/Azure CLI, not just PowerShell.
  • Clarify whether Service Fabric clusters can run on Linux nodes and, if so, provide parity in upgrade instructions and references.
  • When mentioning PowerShell, always mention Azure CLI/bash alternatives alongside or before it.
  • Add a section or links for Linux node patching and upgrade best practices.
GitHub Create Pull Request
Service Fabric Azure Service Fabric application resource model ...ervice-fabric/service-fabric-concept-resource-model.md
Medium Priority View Details →
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. All deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource), with no equivalent Azure CLI or Linux/macOS shell instructions. The application packaging step references Visual Studio (a Windows-centric tool), and the directory paths use Windows-style notation. There are no Linux/macOS alternatives or guidance, and Windows tools are mentioned first and exclusively.
Recommendations
  • Add Azure CLI examples for deployment and deletion tasks alongside PowerShell examples.
  • Provide instructions for packaging the application using cross-platform tools (e.g., dotnet CLI, SF SDK, or manual zip commands) instead of only Visual Studio.
  • Use platform-neutral directory paths or clarify the location for Linux/macOS users.
  • Mention that all steps can be performed from Linux/macOS, and provide any necessary prerequisites or differences.
  • Include screenshots or references for Linux/macOS environments where appropriate.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Events ...es/service-fabric/service-fabric-diagnostics-events.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ missing_linux_example ⚠️ windows_first
Summary
The documentation page for Azure Service Fabric Events demonstrates a Windows bias by primarily referencing Windows Event logs, ETW, and the Windows Azure diagnostics agent as the default mechanisms for event access and monitoring. There are no explicit Linux or cross-platform examples or instructions, and Windows tools are mentioned first and exclusively in the 'How to access events' section. This creates friction for Linux/macOS users, as Service Fabric supports Linux clusters but the documentation does not address their event access or monitoring workflows.
Recommendations
  • Add explicit guidance for accessing Service Fabric events on Linux clusters, including supported logging mechanisms (e.g., stdout, syslog, Azure Monitor integration).
  • Provide examples or references for configuring diagnostics and event collection on Linux nodes.
  • Mention cross-platform tools and APIs (such as EventStore REST APIs) earlier and highlight their applicability to both Windows and Linux clusters.
  • Clarify which instructions are Windows-specific and offer Linux alternatives where possible.
GitHub Create Pull Request
Service Fabric Azure Service Fabric DNS service ...n/articles/service-fabric/service-fabric-dnsservice.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation provides PowerShell examples for setting DNS names, references ApplicationManifest.xml (a Windows-centric workflow), and does not offer Linux CLI or scripting equivalents. Windows portal workflows are described in detail, while Linux-specific limitations are mentioned but not accompanied by alternative instructions or parity examples. The ARM template approach is platform-neutral, but practical Linux workflows (e.g., Bash, Azure CLI) are missing.
Recommendations
  • Add Linux-specific examples for setting DNS names, such as using Bash scripts, Azure CLI, or REST API.
  • Clarify how Linux users can configure DNS service, especially since portal workflows are unavailable for Linux clusters.
  • Provide guidance for containerized Linux services, including Docker Compose or Kubernetes YAML examples for DNS integration.
  • Where PowerShell is used, offer equivalent Azure CLI or Bash commands for Linux users.
  • Explicitly note which steps are Windows-only and provide Linux alternatives where possible.
GitHub Create Pull Request
Service Fabric Azure Service Fabric hosting model ...rticles/service-fabric/service-fabric-hosting-model.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page for Azure Service Fabric hosting model presents PowerShell examples exclusively for service creation and management, with no equivalent Linux CLI (e.g., Azure CLI or Bash) examples. Windows/PowerShell tools are referenced first and most prominently, while Linux-native workflows are not mentioned. This creates friction for Linux/macOS users, who may need to adapt instructions or search for alternative tooling.
Recommendations
  • Add Azure CLI examples for service creation and management, especially for specifying ServicePackageActivationMode.
  • Explicitly mention cross-platform management options (e.g., REST API usage from Bash/curl, Azure CLI, or SDKs usable on Linux/macOS).
  • Clarify which PowerShell commands are available on PowerShell Core (cross-platform) versus Windows PowerShell.
  • Provide links or references to Linux/macOS-specific documentation or tooling where applicable.
GitHub Create Pull Request
Service Fabric Package an existing executable to Azure Service Fabric ...abric/service-fabric-guest-executables-introduction.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first
Summary
The documentation shows a moderate Windows bias. It references the Service Fabric SDK schema file using a Windows path (C:\Program Files\Microsoft SDKs\Service Fabric\schemas\...), and does not mention Linux/macOS equivalents or installation paths. There is also an implicit assumption of Windows environments (e.g., use of .exe in examples), and Visual Studio is mentioned as a primary tool before command-line utilities, which may suggest Windows-first orientation. However, the content does not explicitly exclude Linux/macOS, and Service Fabric supports Linux clusters.
Recommendations
  • Add Linux/macOS paths for the Service Fabric SDK schema file, or clarify if it is only available on Windows.
  • Provide examples using Linux-compatible executables (e.g., .sh or ELF binaries) in the directory structure.
  • Mention cross-platform tools (such as VS Code or CLI tools) alongside Visual Studio, or clarify which steps are Windows-only.
  • Explicitly state platform support and any limitations for Linux/macOS clusters.
GitHub Create Pull Request
Service Fabric Networking patterns for Azure Service Fabric ...s/service-fabric/service-fabric-patterns-networking.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page provides only PowerShell-based deployment examples and command-line instructions, with no mention of Azure CLI, Bash, or Linux/macOS-compatible workflows. Windows-specific tools (PowerShell, RDP) are referenced exclusively and shown before any cross-platform alternatives. This creates friction for Linux/macOS users, who must translate instructions or find their own equivalents.
Recommendations
  • Add Azure CLI examples alongside PowerShell commands for template deployment and resource management.
  • Mention Bash scripting or cross-platform shell options where appropriate.
  • Clarify that Azure Resource Manager templates can be deployed from any OS, and link to relevant cross-platform documentation.
  • Provide guidance for accessing Service Fabric clusters from Linux/macOS (e.g., SSH instead of RDP, using Service Fabric Explorer via browser).
  • Where ping or other commands are shown, use generic syntax or note platform differences.
GitHub Create Pull Request
Service Fabric Service communication with the ASP.NET Core ...vice-fabric-reliable-services-communication-aspnetcore.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation provides thorough coverage of both Kestrel (cross-platform) and HTTP.sys (Windows-only) web servers for ASP.NET Core integration with Azure Service Fabric. However, Windows-specific tools and patterns (such as HTTP.sys, netsh, and Windows HTTP Server API) are discussed in detail, often before or alongside Kestrel. The HTTP.sys section is Windows-only, but this is clearly noted. Some example configurations and endpoint setup instructions reference Windows tools (e.g., netsh) without Linux equivalents or alternatives. Visual Studio debugging is mentioned in 'Next steps,' which is Windows-centric, and there are no explicit Linux/macOS development environment instructions or troubleshooting guidance.
Recommendations
  • Add explicit Linux/macOS development environment setup instructions, including recommended tools and troubleshooting.
  • Provide examples for configuring and running Service Fabric Reliable Services with Kestrel on Linux, including endpoint and port management.
  • Clarify when Windows-only features (like HTTP.sys) are not available on Linux/macOS and suggest alternatives (e.g., always use Kestrel on Linux).
  • Include links or references to Linux/macOS-specific Service Fabric documentation or tutorials.
  • Mention cross-platform debugging tools or alternatives to Visual Studio for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Replica soft delete for enhanced data protection in Service Fabric ...s/service-fabric/service-fabric-replica-soft-delete.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation page for 'Replica soft delete for enhanced data protection in Service Fabric' heavily references PowerShell cmdlets (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica, Get-ServiceFabricReplica) as the primary means of interacting with the feature. There are no examples or explicit instructions for Linux/macOS users, such as using Service Fabric CLI (sfctl) or REST APIs, even though Service Fabric supports cross-platform management. The documentation assumes PowerShell as the default administrative interface, which may create friction for non-Windows users.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl) for all PowerShell cmdlet operations (remove, restore, get replica).
  • Mention REST API alternatives where available for managing replicas.
  • Clarify in the introduction that PowerShell is one option and that cross-platform tools are available.
  • Provide links to cross-platform tooling documentation (sfctl, REST API) alongside PowerShell references.
  • Where screenshots or command output are shown, consider including sfctl or REST API output as well.
GitHub Create Pull Request
Service Fabric Specifying Service Fabric service endpoints ...ce-fabric/service-fabric-service-manifest-resources.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ windows_tools
Summary
The documentation page shows a moderate Windows bias. PowerShell is the only CLI example given for deploying applications, and the documentation references Windows file paths and certificate stores before mentioning Linux equivalents. The Service Fabric SDK schema path is given in a Windows format, and PowerShell is used for deployment commands without Bash or Linux CLI alternatives. Linux-specific information is present but less prominent and often appears after Windows details.
Recommendations
  • Provide equivalent Bash or Azure CLI examples for Linux/macOS users alongside PowerShell commands.
  • Mention Linux file paths and certificate store locations at the same time as Windows paths, not after.
  • Clarify when instructions or tools are cross-platform, and explicitly note any Windows-only steps.
  • Add a section or callouts for Linux/macOS deployment workflows, especially for common tasks like application deployment.
GitHub Create Pull Request
Service Fabric Add custom Service Fabric health reports ...rticles/service-fabric/service-fabric-report-health.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page provides detailed examples for reporting health in Service Fabric using PowerShell, with explicit PowerShell commands and Windows-style prompts (e.g., 'PS C:\>'). API examples are given in C#, but there are no Linux/macOS shell (bash) or cross-platform CLI examples. The PowerShell approach is presented before REST, and REST is only briefly mentioned without concrete examples. There is no mention of Linux equivalents (such as Azure CLI, bash scripts, or cross-platform tools), nor guidance for Linux users on how to perform similar tasks.
Recommendations
  • Add Azure CLI examples for reporting health, if supported, or clarify if only PowerShell is available.
  • Provide bash shell script examples for REST calls (using curl or similar) to demonstrate health reporting from Linux/macOS.
  • Explicitly state platform requirements for PowerShell commands, and offer alternatives for Linux/macOS users.
  • Ensure REST examples include concrete sample requests (e.g., curl commands) for cross-platform parity.
  • Mention any limitations or differences for Linux-based Service Fabric clusters, if applicable.
GitHub Create Pull Request
Service Fabric Fault Analysis Service overview .../service-fabric/service-fabric-testability-overview.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation provides explicit PowerShell instructions for using the Fault Analysis Service but does not mention or provide examples for Linux/macOS users (e.g., Bash, CLI, or REST API usage). This creates friction for non-Windows developers who may not use PowerShell.
Recommendations
  • Add instructions or examples for using the Fault Analysis Service from Linux/macOS environments, such as via Azure CLI, Bash scripts, or REST API.
  • Clarify whether the Fault Analysis Service can be managed using cross-platform tools, and provide links or references if so.
  • If PowerShell is required, explicitly state this limitation and suggest workarounds or alternatives for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Configure the upgrade of a Service Fabric application ...abric/service-fabric-visualstudio-configure-upgrade.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation is heavily focused on Windows tooling, specifically Visual Studio and PowerShell, for configuring and upgrading Service Fabric applications. All examples and instructions reference Windows tools, with no mention of Linux/macOS equivalents or cross-platform CLI options. Linux users are not provided guidance for performing upgrades outside of PowerShell or Visual Studio.
Recommendations
  • Add instructions and examples for upgrading Service Fabric applications using Azure CLI or REST API, which are cross-platform.
  • Mention and link to any Linux/macOS compatible tools for Service Fabric application management.
  • Clarify whether PowerShell Core (cross-platform) is supported, and provide examples if so.
  • Provide guidance for editing application manifest files and performing upgrades from Linux/macOS environments.
GitHub Create Pull Request
Virtual Machine Scale Sets Migrate deployments and resources to Virtual Machine Scale Sets in Flexible orchestration ...lexible-virtual-machine-scale-sets-migration-resources.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation references Azure CLI, Azure PowerShell, and ARM templates for creating and migrating resources, but does not provide explicit Linux/bash examples or mention Linux tools. Azure PowerShell is mentioned alongside Azure CLI, but CLI examples are not shown. Windows-specific scenarios (activation, updates) are listed before Linux (package managers) in outbound connectivity requirements. No explicit Linux/macOS guidance or parity is provided, and PowerShell is referenced as a primary scripting option.
Recommendations
  • Add explicit bash/Linux shell examples for key operations (e.g., az CLI commands for VM creation, migration, querying, etc.).
  • Mention Linux/macOS compatibility for Azure CLI and ARM templates, and clarify that PowerShell is optional for Windows users.
  • Provide Linux-specific migration considerations, such as package manager connectivity, and list Linux scenarios alongside Windows ones.
  • Ensure that Linux tools and workflows (e.g., bash scripts, cloud-init) are referenced where relevant.
  • Consider alternating the order of Windows and Linux scenarios/examples to avoid 'windows_first' bias.
GitHub Create Pull Request
Virtual Machines Create and upload an Ubuntu Linux VHD in Azure ...rticles/virtual-machines/linux/create-upload-ubuntu.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation, while focused on Ubuntu Linux VHD creation for Azure, frequently references Windows-specific tools (Hyper-V, PowerShell's Convert-VHD cmdlet) and provides Windows-centric instructions (e.g., Hyper-V Manager steps, Convert-VHD usage) without offering Linux-native alternatives or parity. Windows tools and workflows are mentioned first and in detail, while Linux equivalents (such as qemu-img or VirtualBox) are missing, creating friction for Linux/macOS users.
Recommendations
  • Add instructions for creating and converting VHDs using Linux-native tools (e.g., qemu-img, VBoxManage) alongside Hyper-V/PowerShell examples.
  • Provide guidance for extracting and preparing VHDs on Linux/macOS, not just Windows/WSL.
  • Include steps for shutting down and managing VMs using Linux virtualization platforms (e.g., KVM, VirtualBox) in addition to Hyper-V.
  • Ensure that Linux-native workflows are presented before or alongside Windows-specific ones, not only as an afterthought.
  • Clarify which steps are platform-agnostic and which are Windows-specific, and offer alternatives where possible.
GitHub Create Pull Request
Virtual Machines Resize a virtual machine ...blob/main/articles/virtual-machines/sizes/resize-vm.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation page for resizing an Azure virtual machine exhibits several forms of Windows bias. PowerShell is given extensive, detailed coverage with multiple scripts and explanations, while Linux-native tools (such as Bash or cloud-init) are not mentioned. The CLI section uses Bash syntax but is not explicitly labeled as a Linux example, and the Terraform section references only a Windows VM quickstart. There are no explicit Linux-specific examples or guidance, and PowerShell is presented before CLI or Terraform, reinforcing a Windows-first perspective.
Recommendations
  • Add explicit Linux/Bash examples for resizing VMs, including using the Azure CLI from a Linux shell and mentioning any Linux-specific considerations.
  • In the Terraform section, include both Linux and Windows VM resource block examples, or link to both quickstarts.
  • Balance the order of examples: consider presenting Azure CLI (cross-platform) before PowerShell, or clarify that PowerShell is available on Linux/macOS as well.
  • Where possible, mention that Azure CLI commands can be run natively on Linux/macOS, and provide any relevant troubleshooting tips for those platforms.
  • If there are Linux-specific limitations or best practices (e.g., for cloud-init, SSH, etc.), include them.
GitHub Create Pull Request
Virtual Machines Create a VM from a generalized image in a gallery ...icles/virtual-machines/vm-generalized-image-version.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ windows_tools
Summary
The documentation provides both Linux and Windows examples for VM creation, but PowerShell examples are heavily Windows-centric, with explicit use of Windows-specific parameters and patterns (e.g., Set-AzVMOperatingSystem -Windows, RDP port configuration). In several PowerShell sections, Windows VM creation is the default, and Linux-specific instructions are missing or only briefly referenced. Windows terminology and tooling (PowerShell, RDP, Windows credential prompts) are used more extensively and often appear before Linux equivalents. CLI and REST examples are more balanced, but PowerShell sections lack Linux parity.
Recommendations
  • Add explicit Linux PowerShell examples, including Set-AzVMOperatingSystem -Linux and SSH configuration.
  • When showing PowerShell code, provide both Windows and Linux VM creation flows, or clarify which OS is being targeted.
  • Ensure network security group examples include both SSH (22) and RDP (3389) rules, not just RDP.
  • Where possible, avoid defaulting to Windows in PowerShell examples; instead, present OS-agnostic or dual examples.
  • Clarify in text when an example is Windows-specific, and provide links or code for Linux equivalents.
GitHub Create Pull Request
Service Fabric Custom Image .../articles/service-fabric/how-to-deploy-custom-image.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation page is generally cross-platform, referencing both Windows and Linux custom images and linking to Linux image creation tutorials. However, the narrative and examples are Windows-centric: 'Custom windows images' are discussed first and most prominently, and the only CLI example provided is in PowerShell, with no equivalent Linux/bash example. Windows terminology and tools are mentioned before Linux equivalents, creating a subtle Windows-first bias.
Recommendations
  • Add explicit Linux/bash CLI examples alongside PowerShell for role assignment and image management.
  • Clarify that custom images can be Linux-based and provide examples or links for Linux-specific workflows.
  • Balance the narrative to mention Linux and Windows images equally, avoiding Windows-first phrasing.
  • Include references to Linux tools and commands (e.g., Azure CLI bash usage) where relevant.
GitHub Create Pull Request
Service Fabric Overview of Service Fabric and containers ...s/service-fabric/service-fabric-containers-overview.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools
Summary
The documentation provides a balanced overview of Service Fabric container support for both Linux and Windows, but there are minor signs of Windows bias. Windows container runtimes and tools are listed in detail, and Windows scenarios (such as IIS lift-and-shift) are described before Linux equivalents. Windows tutorials and references are often placed before Linux ones, and Windows-specific tools (Mirantis Container Runtime, DockerEE) are mentioned, while Linux only lists Docker. However, Linux support is clearly acknowledged, and Linux tutorials are linked.
Recommendations
  • Ensure Linux and Windows examples/tutorials are presented in parallel or alternate order to avoid 'windows_first' bias.
  • Expand Linux-specific scenarios (e.g., NGINX, Apache) to match the detail given to Windows/IIS scenarios.
  • List Linux container runtimes and tools with equal detail as Windows (e.g., mention containerd, Podman if supported).
  • Provide explicit Linux command-line examples or references where Windows tools are mentioned.
  • Clarify parity and limitations for Linux vs Windows containers in Service Fabric, if any.
GitHub Create Pull Request
Virtual Machine Scale Sets Attach or detach a virtual machine to or from a Virtual Machine Scale Set ...le-sets/virtual-machine-scale-sets-attach-detach-vm.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all major operations (attach, detach, move VMs), but consistently includes PowerShell examples alongside CLI, and sometimes gives PowerShell examples more parameters or detail. The PowerShell examples are Windows-centric, and the documentation refers to Azure PowerShell as a primary tool, which is mainly used on Windows. However, Azure CLI examples are present and use Linux-friendly syntax (e.g., Ubuntu image), and all operations are possible via CLI. The order of examples (portal, CLI, PowerShell) is neutral, but the presence of PowerShell in every section may subtly signal Windows as a primary platform.
Recommendations
  • Clarify that Azure PowerShell can be used cross-platform (via PowerShell Core), or explicitly mention Linux/macOS compatibility.
  • Add notes or links for Linux/macOS users about installing and using Azure CLI and PowerShell Core.
  • Ensure CLI examples are as detailed as PowerShell ones, especially regarding networking and advanced parameters.
  • Consider including Bash or shell script snippets for common Linux workflows, or referencing them where appropriate.
  • If PowerShell is included for completeness, explicitly state that Azure CLI is recommended for Linux/macOS users.
GitHub Create Pull Request
Virtual Machine Scale Sets Orchestration modes for Virtual Machine Scale Sets in Azure ...sets/virtual-machine-scale-sets-orchestration-modes.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation provides Azure CLI and Resource Graph examples, which are cross-platform, but does not include any OS-specific commands or tools. However, there is a minor bias in the order and phrasing: Windows and Linux are mentioned together, but Windows is sometimes listed first (e.g., 'Mix operating systems: Yes, Linux and Windows can reside in the same Flexible scale set'). Additionally, the Azure Site Recovery feature is noted as 'Yes (via PowerShell)' for Flexible orchestration, but no Linux equivalent or cross-platform CLI example is provided. Overall, the documentation is largely neutral and cross-platform, but could improve Linux parity by ensuring examples and feature descriptions explicitly mention Linux support and alternatives where relevant.
Recommendations
  • When referencing Azure Site Recovery, provide cross-platform CLI examples or clarify if PowerShell is required for all OS types.
  • Ensure that Linux is mentioned equally or first in mixed OS contexts to avoid subtle Windows-first bias.
  • Explicitly state when features or extensions are supported for Linux VMs, not just Windows.
  • Add sample commands for Linux users where possible, especially for VM extension installation and monitoring.
GitHub Create Pull Request
Virtual Machines vCPU quotas ...ute-docs/blob/main/articles/virtual-machines/quotas.md
Low Priority View Details →
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 checking vCPU quotas. However, the PowerShell example is given equal prominence as the CLI, and the CLI example is not explicitly labeled as Linux/macOS-friendly. The PowerShell section may imply a Windows-centric approach, and the CLI example is shown first, but overall, Linux users can fully complete the task using the CLI instructions.
Recommendations
  • Explicitly state that Azure CLI works on Linux, macOS, and Windows, and is the recommended cross-platform tool.
  • Add a note clarifying that PowerShell examples are primarily for Windows users, while CLI is for all platforms.
  • Consider mentioning Bash or shell scripting for advanced quota checks, if relevant.
  • Ensure future examples do not assume PowerShell as the default unless the topic is Windows-specific.
GitHub Create Pull Request
Virtual Machines Share VM images in a compute gallery ...in/articles/virtual-machines/shared-image-galleries.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation covers both Windows and Linux VM images, but there are several signs of Windows bias. PowerShell examples and references are frequent and often shown alongside or before CLI equivalents. Windows-specific tools (Sysprep) are mentioned before Linux equivalents (waagent), and links to Windows upload instructions are listed before Linux. Some references and examples default to Windows terminology or patterns, even though the feature is cross-platform.
Recommendations
  • Ensure that Linux examples (Azure CLI, waagent, Linux upload instructions) are presented with equal prominence and order as Windows/PowerShell examples.
  • Where PowerShell and CLI examples are shown, alternate their order or group them together to avoid always showing Windows first.
  • Add explicit Linux-focused sections or examples where only Windows/PowerShell is currently referenced.
  • Review links and references to ensure Linux documentation is as accessible as Windows documentation.
  • Where possible, use neutral language and avoid defaulting to Windows terminology when the feature is cross-platform.
GitHub Create Pull Request
Service Fabric Azure Service Fabric container image management .../articles/service-fabric/container-image-management.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools
Summary
The documentation page for Azure Service Fabric container image management exhibits mild Windows bias. Windows container base images (microsoft/windowsservercore, microsoft/nanoserver) are referenced exclusively in the 'ContainerImagesToSkip' setting, and the default behavior is to not delete these Windows images. No Linux container base images (such as Ubuntu, Alpine, or other common Linux distributions) are mentioned, nor are Linux-specific examples provided. The examples and descriptions focus on Windows images first, and there is no guidance for Linux container image management or parity.
Recommendations
  • Add examples and references for common Linux container base images (e.g., 'docker.io/library/alpine', 'ubuntu', etc.) in the 'ContainerImagesToSkip' setting.
  • Clarify whether the cleanup and deletion features apply equally to Linux containers and images, and provide explicit guidance for Linux-based Service Fabric clusters.
  • Include a note or section on Linux container image management, including any differences or considerations for Linux VMs in Service Fabric clusters.
  • Ensure that examples and descriptions are balanced between Windows and Linux container scenarios.
GitHub Create Pull Request
Service Fabric Architecture of Azure Service Fabric ...articles/service-fabric/service-fabric-architecture.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation references PowerShell cmdlets as a primary management interface in the Management subsystem section, suggesting a Windows-centric approach. No Linux or cross-platform CLI tools (such as Azure CLI or Bash) are mentioned, and Windows security is referenced before X509 certificates in the Transport subsystem. These patterns indicate a mild Windows bias, though the overall architectural description is platform-neutral.
Recommendations
  • Mention and provide examples of cross-platform management tools, such as Azure CLI or REST APIs, alongside PowerShell cmdlets.
  • Clarify that Service Fabric management can be performed from Linux/macOS using Azure CLI or other APIs.
  • Reference Linux-compatible security mechanisms (e.g., X509 certificates) before or alongside Windows security in the Transport subsystem.
  • Add links or notes about Linux/macOS support for Service Fabric where relevant.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Docker Compose Deployment Preview ...ticles/service-fabric/service-fabric-docker-compose.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides both PowerShell and Service Fabric CLI (sfctl) examples for deploying Docker Compose files to Azure Service Fabric. However, PowerShell examples are presented first and in greater detail, which may imply a Windows-centric workflow. The CLI examples are present and suitable for Linux/macOS users, but the prominence and depth of PowerShell instructions suggest a Windows-first bias.
Recommendations
  • Present CLI (sfctl) examples before or alongside PowerShell examples to signal equal support for Linux/macOS users.
  • Expand CLI example explanations to match the detail given to PowerShell commands.
  • Explicitly state that sfctl is cross-platform and suitable for Linux/macOS environments.
  • Add a short section clarifying that all deployment tasks can be completed on Linux/macOS using sfctl, and PowerShell is optional for Windows users.
GitHub Create Pull Request
Service Fabric Reliable services app manifest examples ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-manifest-example-reliable-services-app.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation page provides Service Fabric application and service manifest examples, but exhibits mild Windows bias. It references Windows concepts (e.g., 'NetworkService', 'Administrators' group, 'Setup.bat', '.exe' files) and mentions using the ServiceFabric PowerShell module to create service instances. There are no explicit Linux or cross-platform examples (e.g., shell scripts, Linux user/group patterns), and Windows-specific tools and terminology are used throughout. However, the manifest XML itself is platform-neutral, and Service Fabric supports Linux, so Linux users can adapt the examples with some effort.
Recommendations
  • Add Linux-specific examples, such as using shell scripts (.sh) for SetupEntryPoint and EntryPoint, and referencing Linux user/group equivalents.
  • Mention Linux-compatible tools for managing Service Fabric applications (e.g., Azure CLI, sfctl) alongside or before PowerShell.
  • Clarify which concepts (e.g., user accounts, system groups) map to Linux equivalents, and provide guidance for Linux deployments.
  • Ensure examples and explanations are platform-neutral where possible, or provide parallel examples for both Windows and Linux.
GitHub Create Pull Request
Service Fabric Overview of Azure Service Fabric ...ain/articles/service-fabric/service-fabric-overview.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ windows_first
Summary
The documentation mentions both Windows and Linux support for Service Fabric, and provides parity in describing development environments and cluster deployment. However, in the 'Any OS, any cloud' section, Windows development is described first, with Visual Studio and PowerShell highlighted, while Linux development is described second. The quickstart link also points to a .NET (likely Windows-focused) guide, rather than a Linux or cross-platform example.
Recommendations
  • Present Windows and Linux development environments in parallel or alternate the order to avoid Windows-first bias.
  • Include quickstart links for both Windows (.NET) and Linux (Java/.NET Core) development, or a cross-platform quickstart.
  • Explicitly mention cross-platform tooling and provide links to Linux/macOS guides alongside Windows guides.
  • Highlight that Service Fabric supports containerized workloads in any language, and provide example links for Linux scenarios.
GitHub Create Pull Request
Service Fabric Reliable Collection object serialization ...c-reliable-services-reliable-collections-serialization.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ windows_first
Summary
The documentation provides conceptual and code examples for Reliable Collection object serialization in Azure Service Fabric. While the main content is platform-neutral, the 'Next steps' section lists 'Upgrading your Application Using Visual Studio' and 'Upgrading your Application Using PowerShell' before mentioning any Linux/macOS-compatible upgrade methods. This ordering subtly prioritizes Windows tooling, but does not exclude Linux users from completing the tasks described.
Recommendations
  • Reorder the 'Next steps' links so that platform-neutral or Linux-compatible upgrade methods are listed before Windows-specific tools like Visual Studio and PowerShell.
  • Explicitly mention Linux/macOS-compatible upgrade methods (such as Azure CLI or REST API) if available, to ensure parity.
  • Add a note clarifying that Service Fabric supports both Windows and Linux clusters, and that serialization concepts apply equally to both.
GitHub Create Pull Request
Virtual Machine Scale Sets Networking for Azure Virtual Machine Scale Sets ...ne-scale-sets/virtual-machine-scale-sets-networking.md
Low Priority View Details →
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 most tasks, but PowerShell (a Windows-centric tool) is often presented before CLI, and some sections (such as querying public IPs) show PowerShell examples first or exclusively. Portal instructions are platform-neutral, but there is a slight tendency to favor Windows/PowerShell patterns in example ordering and coverage.
Recommendations
  • Ensure CLI and PowerShell examples are presented side-by-side or with CLI first, as CLI is cross-platform.
  • Where PowerShell is used, always provide equivalent CLI commands, especially for querying and updating resources.
  • Explicitly note that Azure CLI works on Linux/macOS and Windows, and encourage its use for cross-platform scenarios.
  • Review example ordering to avoid consistently placing PowerShell before CLI.
  • Add bash scripting examples where relevant for Linux users.
GitHub Create Pull Request
Virtual Machine Scale Sets Configure rolling upgrades on Virtual Machine Scale Sets ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-configure-rolling-upgrades.md
Low Priority View Details →
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 all operations, but PowerShell examples are always shown after CLI and are present for every task. There are no Linux-specific examples or mentions of Linux tools, but the CLI examples are cross-platform. The documentation does not show explicit Windows bias in critical sections, but the presence of PowerShell examples for every operation and lack of explicit Linux/macOS shell examples (e.g., Bash) may create minor friction for Linux users.
Recommendations
  • Clarify that Azure CLI examples are cross-platform and suitable for Linux/macOS users.
  • Consider adding Bash shell script examples for common tasks, or explicitly mention that CLI commands can be run in Bash, Zsh, etc.
  • Where PowerShell is mentioned, note that it is available on Linux/macOS, or provide links to installation instructions for PowerShell Core on non-Windows platforms.
  • Ensure parity in example ordering: consider showing CLI (cross-platform) examples first, or note their cross-platform nature more prominently.
GitHub Create Pull Request
Virtual Machine Scale Sets Custom metrics for rolling upgrades on Virtual Machine Scale Sets ...tual-machine-scale-sets-rolling-upgrade-custom-metrics.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation provides both Linux (Bash/Python) and Windows (PowerShell) examples for configuring the application health extension response and for extension installation. However, there are several signs of Windows bias: PowerShell examples are often shown alongside or before Bash, and Windows-specific extension types ('ApplicationHealthWindows') are used in several code snippets and REST examples, sometimes without clear Linux equivalents. The PowerShell tab is present for nearly every example, and Windows tools (PowerShell, Windows extension type) are referenced frequently. While Linux parity is mostly present, Windows terminology and tools are often prioritized or shown first.
Recommendations
  • Ensure Linux and Windows extension types are both shown in REST and JSON examples, or clarify when to use each.
  • Alternate the order of Bash and PowerShell examples, or show Bash first where possible.
  • Explicitly mention Linux-specific instructions and tools where relevant, such as using 'ApplicationHealthLinux' in extension configuration.
  • Add clarifying notes about OS-specific extension types and settings.
  • Review sample outputs to ensure both Linux and Windows variants are represented.
GitHub Create Pull Request
Virtual Machine Scale Sets Create an Azure scale set that uses Availability Zones ...s/virtual-machine-scale-sets-use-availability-zones.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for creating and updating scale sets with Availability Zones. However, PowerShell examples are given equal prominence to CLI, and in some sections (such as 'Use Azure PowerShell'), PowerShell is presented before ARM template examples. The CLI examples are cross-platform, but PowerShell is Windows-centric. There is minor bias in the ordering and prominence of PowerShell, but Linux users can complete all tasks using the CLI or ARM templates. No Linux-specific shell examples (e.g., Bash) are provided, but the CLI covers Linux needs.
Recommendations
  • Ensure Azure CLI examples are always presented before PowerShell, as CLI is cross-platform.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
  • Consider adding Bash shell script examples for Linux users, especially for automation scenarios.
  • Clarify that PowerShell examples are primarily for Windows users.
  • Add a note that all tasks can be completed on Linux/macOS using Azure CLI and ARM templates.
GitHub Create Pull Request
Virtual Machines Create a Gallery for Sharing Resources .../blob/main/articles/virtual-machines/create-gallery.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ windows_first
Summary
The documentation provides cross-platform examples for creating an Azure Compute Gallery, including Azure CLI, REST API, Portal, and PowerShell. However, PowerShell examples are presented alongside CLI and REST, and the PowerShell section is given equal prominence. The CLI examples use Bash-style syntax and variables, which are Linux/macOS-friendly. The only minor bias is that PowerShell is included as a primary example, which may be unnecessary for Linux/macOS users, but there are no missing Linux examples or Windows-only tools.
Recommendations
  • Clarify in the PowerShell section that PowerShell is primarily for Windows users, and suggest Azure CLI as the preferred cross-platform tool.
  • Consider listing Azure CLI examples before PowerShell to reinforce Linux/macOS parity.
  • Explicitly state that Azure CLI works on Windows, Linux, and macOS, making it the recommended option for non-Windows environments.
GitHub Create Pull Request
Virtual Machines Azure Key Vault VM Extension for Linux ...rticles/virtual-machines/extensions/key-vault-linux.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation is focused on Linux, as indicated by the title and content. However, there is a mild Windows bias in the ordering and prominence of deployment examples: Azure PowerShell instructions and examples are presented before Azure CLI, even though Linux users are more likely to use Azure CLI. Additionally, troubleshooting instructions reference Azure PowerShell before Azure CLI. There are no Windows-only tools or missing Linux examples; all technical steps and paths are Linux-specific.
Recommendations
  • Present Azure CLI deployment instructions before Azure PowerShell, as CLI is the primary tool for Linux users.
  • Highlight Azure CLI as the recommended method for Linux deployments.
  • Ensure troubleshooting sections reference Azure CLI first, followed by PowerShell.
  • Consider adding a note clarifying that PowerShell is optional and primarily for cross-platform or Windows users.
GitHub Create Pull Request
Virtual Machines Deprovision or generalize a VM before creating an image ...docs/blob/main/articles/virtual-machines/generalize.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides clear, parallel instructions for both Linux and Windows VM generalization. However, the Windows section includes more detailed prerequisites and troubleshooting steps, and Windows PowerShell/Command Prompt examples are shown before their Linux equivalents in some places. The Linux section is concise and relies heavily on waagent, while the Windows section uses multiple Windows-specific tools and registry edits. Both OSes are covered, but Windows examples and tools are somewhat more prominent.
Recommendations
  • Ensure Linux prerequisites are as detailed as Windows prerequisites, including troubleshooting tips and common pitfalls.
  • Provide Linux CLI alternatives for all Azure CLI and PowerShell commands (e.g., show az CLI usage for both OSes, not just in Linux section).
  • Consider presenting Linux and Windows sections in parallel structure, or alternate which OS is shown first in examples.
  • Expand Linux section to include more context about potential issues, similar to the Windows section.
  • Where possible, avoid using Windows-specific terminology (e.g., 'Command Prompt') without Linux equivalents (e.g., 'Terminal').
GitHub Create Pull Request
Virtual Machines Time sync for Linux VMs in Azure ...blob/main/articles/virtual-machines/linux/time-sync.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ windows_first
Summary
The documentation is focused on Linux VM time synchronization in Azure and provides comprehensive Linux-specific guidance. However, the introductory section discusses Windows Server 2016 time sync improvements and references Windows documentation before Linux-specific details. All configuration examples, tools, and commands are Linux-centric, with only a single PowerShell command shown for base64 encoding cloud-init (which is relevant for Azure ARM templates, not VM configuration). There are no missing Linux examples or Windows tools used for core tasks.
Recommendations
  • Move or minimize the Windows Server 2016 discussion in the introduction, emphasizing Linux relevance first.
  • Add a brief explanation for the PowerShell base64 example, noting that Linux users can use 'base64' command instead.
  • Consider linking to Linux time sync concepts/documentation before Windows references in the intro and 'Next steps'.
GitHub Create Pull Request
Virtual Machines Deploy a Trusted Launch VM ...ain/articles/virtual-machines/trusted-launch-portal.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation covers both Linux and Windows VM deployment with Trusted Launch, but PowerShell examples are Windows-centric and Windows examples are often presented first. Linux parity is generally good, especially in CLI and template sections, but PowerShell sections focus on Windows images and configurations, and Windows terminology appears before Linux in some places.
Recommendations
  • Provide PowerShell examples for Linux VM deployment, including using Set-AzVMOperatingSystem with -Linux and Linux image parameters.
  • When listing examples, alternate or parallelize Windows and Linux instructions, rather than defaulting to Windows first.
  • Clarify in PowerShell sections that Linux VMs can also be deployed and provide sample scripts for Linux.
  • Ensure that terminology and screenshots are inclusive of both OS types, or explicitly state when a step is OS-specific.
GitHub Create Pull Request
Virtual Machines Enable Trusted launch on existing Gen2 VMs ...rticles/virtual-machines/trusted-launch-existing-vm.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides parity for both Linux and Windows VMs, but there is a mild Windows bias in the ordering and tooling. PowerShell examples are given equal prominence to Azure CLI, but PowerShell is a Windows-centric tool. In the ARM template section, PowerShell is used for deployment commands rather than CLI or cross-platform alternatives. Windows terminology (RDP) is mentioned before Linux (SSH) in verification steps. However, Linux-specific guidance (such as SBInfo for Secure Boot validation) is included, and all procedures are applicable to both OS types.
Recommendations
  • In ARM template deployment steps, provide Azure CLI examples alongside PowerShell to ensure cross-platform usability.
  • Where possible, mention SSH (Linux) and RDP (Windows) together or alternate their order to avoid Windows-first bias.
  • Consider clarifying that PowerShell commands can be run on Linux/macOS via PowerShell Core, or provide CLI alternatives.
  • Continue to highlight Linux-specific tools and validation steps as done with SBInfo.
GitHub Create Pull Request
Virtual Machines VM vCore Customization ...lob/main/articles/virtual-machines/vm-customization.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ minor_windows_tools
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring VM vCore customization. The CLI example uses Ubuntu as the image, showing Linux parity, but the PowerShell section is more detailed and appears before ARM template automation. The PowerShell example uses Windows-centric SDK objects and terminology. The ordering of sections (CLI, then PowerShell) is reasonable, but the PowerShell example is more verbose and technical. No Linux-specific tools (like Bash scripts or cloud-init) are mentioned, but the CLI example covers Linux use cases. There is minor bias in the depth and detail of Windows/PowerShell instructions.
Recommendations
  • Add Bash or shell script examples for Linux users, especially for automation scenarios.
  • Clarify that Azure CLI works equally well for both Linux and Windows, and provide explicit Linux/macOS usage notes.
  • Balance the detail between PowerShell and CLI sections, ensuring CLI instructions are as comprehensive as PowerShell.
  • Mention Linux-specific automation tools (e.g., cloud-init) if relevant.
  • Consider adding a table or summary comparing CLI, PowerShell, and ARM template approaches for both OS types.
GitHub Create Pull Request